docs: multi-chain trust tiers + scope dossier - #103
Merged
Conversation
Cut implementation exposition (ReadStatus internals, launch-time tier selection, eth_getBalance mechanics) that belongs in the dossier, drop doubled-up sentences, match the surrounding terse declarative voice.
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
1 participant
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.
What
Two docs, no code:
Verifiedtier; every other chain reads NOT VERIFIED via the existingUnsyncedaffordance (no new badge). Tier 2 (opstackDegraded) is reserved for Spike: multi-chain verified reads via helios-opstack (Base/OP) — scope + go/no-go #77; no-native-asset chains (Tempo) are deferred until the portfolio model can represent them.file:linecitation: subsystem coupling maps across all 7 crates, external research (Tempo, Arbitrum, light-client landscape, CoW/Railgun), a feature matrix, risks, phasing, and the open questions to verify before building.Why
Scopes how Deckard adds non-Ethereum chains given that verified reads are structurally mainnet-only. Backs the issues opened from it: #97 (chain registry), #98 (Arbitrum reads+send), #99 (swap), #100 (gas), #101 (privacy), #102 (Tempo spike) — plus the existing #76 (guardrail) and #77 (opstack spike).
Notes
Cargo.toml/ code changes, so the engineering DoD (clippy/tests) is N/A.