Open · O3

Reproducible self-host

Can a stranger reach a working deployment from the README?

Why it matters

Code you cannot run is documentation. A recorded self-host attempt is the only evidence that the walkaway option exists in practice.

Scoring anchors

3 Strong	A stranger can reach a working deployment from the README (build steps, env vars, ABIs, addresses, schemas), shown either by a recorded attempt (trace) or by a deploy script in the repo that completes a test payment and has a recorded successful run.
2 Partial	Reproducible with minor undocumented steps, recorded.
1 Weak	Docs exist; reproduction not attempted, or failed with blockers listed.
0 Fails	No path.
No evidence	No admissible evidence submitted yet. Counts as 0 in the pillar.

Admissible evidence

The reproduction attempt with steps documented (trace)
README at a pinned commit, for presence of each required element verified

Common failures

Scoring 3 from a README without attempting it. Without a recorded attempt the cap is 1.

Current ratings

Provider	Score	Finding
Aleo (credits.aleo private transfers)	1 Weak	Build and run documentation exists for the node. Reproduction not attempted, so the score is capped at 1.
AnomaPay	0 Fails	A stranger can deploy the contracts (pa-evm has deploy scripts) but cannot stand up the transaction, proving and indexing services the client flow needs, because their code is not published. Judgment call: 0, no path, rather than 1, since the missing pieces are code, not documentation.
Avalanche Card	No evidence	No admissible evidence yet.
Avici Card	No evidence	No admissible evidence yet.
Aztec (Alpha mainnet private token transfers)	1 Weak	Node setup documentation exists in the repo. Reproduction not attempted, so the score is capped at 1.
Bitget Wallet Card	No evidence	No admissible evidence yet.
Blanksquare (Shielder)	1 Weak	Build and run documentation exists for the relayer, SDK and a quickstart app. Reproduction not attempted, so the score is capped at 1.
COCA Card	No evidence	No admissible evidence yet.
Coinbase Commerce (Onchain Payment Protocol)	1 Weak	The docs are enough to operate the deployed contract as your own operator, though you would have to write the signing and frontend code yourself. They are not enough to rebuild Coinbase Commerce. Reproduction not attempted, so the cap is 1.
Curvy	1 Weak	Contract deployment is documented. The backend services needed to operate the rail are not published. Reproduction not attempted. Scored 1.
Daimo Pay	0 Fails	Re-assessed under the updated anchor; the score is unchanged. No README can get a stranger to a working deployment, because the relayer, the price signer, the indexer, and the API are closed required components (see `components` and O2). The relayer slot is also owner-gated (see C1). The repo has no deploy script that completes a test payment. We did not attempt a reproduction. Anchor 1 ("docs exist; reproduction not attempted") would apply if the docs described a path; judgment call: we score 0 ("No path"), because the documented steps only build and test contracts and stop short of anything that settles a payment.
Deblock Card	No evidence	No admissible evidence yet.
Ethena Pay	0 Fails	There is no README, repo or deploy script, and the factory that wires the wallets together is unverified, so no self-host path exists. Reproduction not attempted.
ether.fi Cash	1 Weak	Contract build and deploy docs exist; reproduction was not attempted. Blockers visible from the repo alone: a working card product also needs the closed app, the card backend, a BIN sponsor and an issuer, and none of these can be self-hosted.
Exa Card	1 Weak	Build docs exist. Reproduction not attempted. Visible blockers: the server needs Rain, Persona and Sardine API keys, and a working card needs an issuer key that the deployed IssuerChecker accepts.
Fluidkey	0 Fails	There is no path to a self-hosted Fluidkey deployment: the app and backend are closed. SARA recovers funds but does not issue addresses or receive payments. Judgment call: 0, since recovery is not a working payment deployment.
Fuse Card	1 Weak	Self-host docs exist for a generic v4 client, not for Fuse. Reproduction not attempted, and the card cannot be self-hosted. 1.
Gnosis Pay	1 Weak	Re-assessed against the revised anchor: a 3 needs a recorded attempt or a deploy script with a recorded successful test payment, and a 2 needs a recorded reproduction. Build docs exist for the frontend and SDK. Reproduction not attempted. Known blockers from the README alone: a working deployment needs a Gnosis Pay-issued PSE app id and the hosted Gnosis Pay API. No deploy script in any gnosispay repo completes a test card payment, and one could not, because the spend delegate, relayer, issuer and network are closed. Stays 1.
HesabPay	No evidence	No admissible evidence yet.
Hinkal	0 Fails	No published path leads to a working self-hosted deployment. The contracts repo has no build or deploy scripts, the proving keys are not published, and the relayer and indexing servers are closed. Reproduction was not attempted. Scored 0: the README itself states the path is absent.
Holyheld Card	0 Fails	There is nothing to self-host: no contracts, backend or app are public, and the README only explains installing the client SDK. No path, so 0. Reproduction not attempted.
Houdini Swap	No evidence	No admissible evidence yet.
Hyperbeat Card	0 Fails	There is no public code, so no self-host path. Reproduction not attempted.
Jupiter Card	No evidence	No admissible evidence yet.
M-Pesa	No evidence	No admissible evidence yet.
MetaMask Card	1 Weak	Build docs exist for the client. Reproduction not attempted. The README alone shows blockers: card features need a Baanx-issued client key and Baanx's hosted API, and there is no self-host path for the card backend.
Opera MiniPay	No evidence	No admissible evidence yet.
Monero	1 Weak	Build and run documentation exists for the node and wallets. Reproduction not attempted, so the score is capped at 1.
Nullmask	0 Fails	No public code, so no path to self-host. Scored 0.
Oobit Card	No evidence	No admissible evidence yet.
Payy Card	1 Weak	Build docs exist for the rollup stack. Reproduction not attempted. A self-hosted node cannot settle against the deployed contract, which accepts only Payy's prover, and the card path needs closed services.
Phantom Cash	No evidence	No admissible evidence yet.
Plasma One	0 Fails	There is no self-host path: no repo or README, and the card cannot run without Rain's keys and Plasma's backend. Reproduction not attempted.
Privacy Pools (0xbow)	1 Weak	Build and deploy documentation exists for contracts, relayer and website. A self-hosted deployment would still need its own ASP, for which no code is published. Reproduction not attempted, so capped at 1.
Railgun	1 Weak	Minimal build documentation exists. Reproduction not attempted, so capped at 1.
Request Network	1 Weak	The documentation needed to self-host exists: Request Node setup, the IPFS swarm image, the storage subgraph, a Helm chart, and the template's env table. We did not attempt a reproduction, so under the brief the score is capped at 1. A self-hosted node also needs xDAI to pay the per-hash storage fee, which read 0.0999 xDAI on Gnosis at block 48631765.
Rizon Card	No evidence	No admissible evidence yet.
SafePal Card	No evidence	No admissible evidence yet.
Solayer Card (Emerald Card / Solayer Pay)	No evidence	No admissible evidence yet.
Tongo (confidential ERC-20 on Starknet)	1 Weak	Docs exist for using the SDK and deploying ledgers. Reproduction not attempted, so capped at 1.
Tornado Cash (Classic pools)	1 Weak	Build and run documentation exists for the UI and the core client. Reproduction not attempted, so the score is capped at 1.
Tria	0 Fails	No self-host path. Reproduction not attempted.
Tuyo Card	No evidence	No admissible evidence yet.
Umbra Cash	1 Weak	Build and run documentation exists, with an .env.example. Reproduction not attempted, so capped at 1.
Wirex One	0 Fails	There is no self-host path: no deployable code is public. Reproduction not attempted.
Wise	No evidence	No admissible evidence yet.
WORM (BETH proof-of-burn)	1 Weak	Build and run instructions exist for the CLI and prover server. Reproduction not attempted, so capped at 1.
XPlace Card	0 Fails	There is no path for a third party to run the XPlace product. Kamino's program can be built, but the card product around it cannot. 0.
Zcash (shielded transfers)	1 Weak	Build and run documentation exists for the node, the light-wallet server and the wallets. Reproduction not attempted, so the score is capped at 1.
zERC20 (zBNB on BNB Chain)	0 Fails	The documented path to a working deployment starts from a repository that is not public, so a stranger cannot follow it. We made no reproduction attempt. Even with code, a self-hosted prover could not post roots to the deployed Verifier without being allowlisted. Scored 0, because no published path exists.