CovenantSQL
A decentralized, trusted, high performance, SQL database with blockchain features
Runs with mockssource: GitHubGoApache-2.0commit fdaa8a4b909f
Go, Apache-2.0 licensed. The project labels itself: bft, blockchain, covenantsql, cql, crypto, database, dbaas and decentralized.
CovenantSQL runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
CovenantSQL builds and runs on Ubuntu 24.04 with Go 1.26.10. All 6 binaries (cql, cqld, cql-minerd, cql-fuse, cql-mysql-adapter, cql-proxy) compile successfully. The cqld Block Producer starts, announces success, and produces blocks using standalone test config. 23 Go package test suites pass. No root packages needed. The cql client generates keys and mines nonces.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 77 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- cql-minerd build requires libicu-dev for sqlite_icu tag; built without that tag3 minutes
- route/ipv6seed_test.go: TestGenTestNetDomain/TestIPv6Seed fail due to external DNS resolution (bp00.testnet.gridb.io etc.) not available in container2 minutes
- proto/proto_test.go: TestEnvelope_GetSet uses goconvey ShouldEqual on context.Context values, which renders as equal but ShouldEqual fails on interface comparison1 minute
- api/service_test.go: TestJSONRPCService websocket server starts in goroutine but test connects before server is ready (timing race)1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 4 hit, 1 fixed with no human help
- How the result was proved
- go test on 23 package suites passed (crypto, consistent, merkle, twopc, utils, conf, types, rpc, pow, storage, blockproducer, chainbus, client, metric, naconn, xenomint, worker, etc.); cqld binary launched with test config, printed 'CovenantSQL Started Successfully' and produced a block
- Model tokens used
- 225,974
- Exact commit tested
- fdaa8a4b909f
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
| worker | pass |
| proto | 1 test failure (goconvey ShouldEqual on context.Context) |
| route | 1 test failure (DNS external dependency) |
| api | 1 test failure (websocket server timing) |
| cmd/cqld | integration test - needs running cluster |
Now let me provide the final structured output.
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 12, "errors": [{"msg": "ro…
tokens used
225,974Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 12 minutes.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Hit 4 errors during setup, 3 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 77.00 | 0.11 |
Topics (from GitHub)
bftblockchaincovenantsqlcqlcryptodatabasedbaasdecentralizedp2pqldbsqlsql-database
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/covenantsql)Questions
- Does CovenantSQL run?
- CovenantSQL runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test CovenantSQL?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fdaa8a4b909f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test CovenantSQL?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does CovenantSQL take to install?
- 12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does CovenantSQL need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing CovenantSQL?
- 4 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for CovenantSQL?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.