docs: ADR for permissionless NAV attestation#23
Draft
0xgleb wants to merge 3 commits into
Draft
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
0981195 to
93ed007
Compare
f15dceb to
51e8cdc
Compare
This was referenced Jun 18, 2026
36f1fad to
042e034
Compare
Answers ADR 0002's open decision 2 (cross-chain-read trust model) and removes the manager/backend as the attestation authority: an open bonded submitter set, channel-typed evidence (guardian-signed consensus reads, TEE oracles, zkTLS, bare bonds), a diversity quorum with two-sided consumption, and bonded disputes that fail closed into the existing ADR 0002 halt machinery. Grounded in deep research (2026-06-10): HyperCore state is not commitment-anchored anywhere (kills anchorable ZK light clients today, hence diversified observation), Wormhole Queries is permissioned-request but trustless-verify with HyperEVM eth_call support, lzRead reaches neither HyperEVM nor Solana, Switchboard On-Demand is live/permissionless on Solana behind TEE-gated operators, and Solana's Groth16 substrate is production-ready (audited <200K CU verifier). Research-grade claims are labeled and listed for re-verification before implementation.
042e034 to
8a7422c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The MVP is deliberately centralized (Turnkey custody, one execution backend),
which is tolerable only if the one subsystem that prices investor shares is
not: manager-attested NAV is the Stream-Finance failure class, and the
moneymentum SPEC currently has the backend posting NAV attestations to the
vault. ADR 0002 removed the manager from the marking path but left the
cross-chain-read trust model as open decision 2 — and its read rail leans on
gated infrastructure.
Solution
ADR 0003: an open attestation protocol on Solana — anyone can submit
(bonded), dispute (bonded), and verify; the backend becomes one submitter
with no special rights.
consensus reads (Wormhole Queries, trustless-verify even though
permissioned-request), TEE oracle results (Switchboard On-Demand),
zkTLS proofs, and bare bonded observations as the degraded mode.
with two-sided consumption per ADR 0002; cross-channel disagreement is a
data-integrity halt, never a pick-one.
into ADR 0002's stale-read rules.
with a concrete three-step unlock chain (the missing piece is an
Ethereum-consensus ZK verifier on Solana); CEXes stay out permanently.
for guardian-quorum verification, and a pre-specified HyperBFT
light-client ask (blocked today on the verified fact that HyperCore
state is not commitment-anchored anywhere).
Grounded in a deep-research pass (2026-06-10) with verified-primary vs
research-grade labeling inside the ADR; research-grade dependencies are
listed for re-verification before implementation.
Answers ADR 0002 open decision 2. No changes to ADRs 0001/0002 or the
program in this PR.
Closes #24