docs: align chains and validation mechanism with current codebase - #17
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Updates docs (and the llms.txt description in astro.config.mjs) to match
what's actually in the go-vsc-node codebase. Eight files, all small
wording corrections.
Why
@LordButterfly flagged that current docs overstate ZK proofs and list
Solana as supported when it isn't yet. Verified against the codebase:
litecoin.go — no solana.go
have deployed mapping contracts on mainnet
signed consensus over native node observation, not ZK proofs
and modules/wasm/sdk/sp1_verifier.go (contract-level SDK helper)
Files changed
Status framing throughout: live = Bitcoin, Ethereum, Hive.
Planned = Litecoin, Dash, Solana.
Verification