FAQ

Why not just Bitcoin?

Bitcoin’s work function is conceded outright as the monetarily superior design: the absence of an external buyer for the work is what makes its cost non-negotiable, and nothing here improves on that. This thesis asks a narrower question about different goods — portable attestation of computation and provenance, and verified compute — which Bitcoin was never built to supply. Whether those goods carry a monetary premium of their own, or merely trade as a priced service, remains an open empirical question, not one already claimed as won. See the full concession in Objections & Responses. Longer answer.

Is this a security?

The thesis’s own Howey walk-through does not dodge the exposure: fees routed to holders, returns tied to operators’ efforts, and an expectation of profit are each arguably present, and the stronger the value-capture design reads as economics, the stronger it reads as a securities case. No token currently exists. The escape path under discussion is issuance and fee policy fixed ex ante in a constitution beyond governance’s reach, with no discretionary re-routing ever possible — the only version of value capture that does not depend on anyone’s efforts. See the full walk-through in Legal & Policy Posture.

Who pays for verification, and why doesn’t the free-rider problem bind?

The prover pays: verification is a private good purchased by whoever wants a claim believed, and its public checkability is a by-product the prover cannot withhold without destroying what they bought. Nobody else needs to be compensated for producing it, so the usual free-rider failure — nobody pays, so the information never gets produced — does not bind. The same asymmetry is why the resulting fee stream is ordinary, competitively priced service revenue rather than a source of excess return; any monetary premium has to be found somewhere a discounted-cash-flow valuation cannot follow. See Work Credits. Longer answer.

What would kill it?

Eighteen named red lines retire the monetary claim after sustained breach and failed remediation, covering verification affordability, refund safety, verifier concentration, telemetry capture, fee coverage, value capture, legal compatibility, governance capture, wrapper substitution, and more. Three bear directly on the verification mechanism itself; a single breach that survives remediation is enough to end the claim. A thesis that cannot say what would falsify it is advocacy, not analysis. The full list, with thresholds and current readings, is tracked on Tripwires.

If the price goes up, does that prove it?

No, and a falling price would not falsify it either — the protocol and its price are different machines. Price can rise on ETF, treasury-company, or leveraged-product demand hitting a thin market while native fees, burns, settlement, and proof purchases stay flat, and it can fall while all of those improve. That is why market realization is measured separately from monetary adoption: price is something to explain, not evidence to cite. See Market Realization.

Wouldn’t a state-run stack just do this better?

Possibly, on cost, uptime, and build speed — and that is conceded rather than contested. A state-integrated closed sovereign stack applies the same trust-minimization instinct to energy, industry, compute, payments, and identity, and nothing in the engineering resists it. But capability was never the claim: what makes an asset a store of value under repression is non-custodial settlement, portable identity, checkable receipts, and the practical ability to exit, and a closed stack withholds exactly those, because withholding them is what makes it closed. Two stacks can post identical dashboards and disagree entirely on whether a participant may leave. See The Closed Sovereign Stack.

Where is it weakest?

By its own chain-strength table, six of the nine links in the monetary argument are rated Medium rather than Strong: standardized work and market formation are engineering-maturity risks; stress-deliverable service is unproven at scale; non-bypassability is written as a binary whose magnitude is nowhere estimated; the holder anchor has no demonstrated countercyclical loss-bearing capacity; and the monetary premium itself stays conditional on all of the above. Naming these as the weak links, rather than burying them, is the point of publishing the table. See The Triad and the Monetary Candidate.

Has anyone hostile read it?

Yes. Two adversarial reviews are published verbatim, unedited, alongside the author’s replies; five more are being solicited on the same terms. The standing offer: any reviewer’s response gets published in full, agree or not. See Reviews.

What is being built, and is there a token?

Kardashev Labs: stack first, coin optional. It issues no monetary instrument and holds no protocol treasury; what it sells is measurement and audit services — reference implementations, telemetry, and adversarial testing — to any protocol as one customer among several, under published terms it cannot withdraw. If a base asset is ever issued, a separate protocol issues it, under a constitution the lab may have helped draft but must be able to fail. There are no tokens, because there are none to give. See Kardashev Labs.

How should I cite it?

Use the versioned web edition for section-level citations and the PDF for the fixed printable edition. See Cite.

Can I quote or reuse figures?

Text and original figures are licensed under CC BY 4.0 unless otherwise noted. Trademarks and third-party materials are excluded. See License.

Will it be updated?

Yes. New versions and substantive changes will be logged in Updates. Corrections will be logged in Errata. Every version’s peer review is published in Reviews.