Skip to content

docs: reframe trust model as run-your-own-node - #201

Merged
TaprootFreak merged 1 commit into
stagingfrom
docs/trust-model-clarify
Jun 4, 2026
Merged

docs: reframe trust model as run-your-own-node#201
TaprootFreak merged 1 commit into
stagingfrom
docs/trust-model-clarify

Conversation

@TaprootFreak

Copy link
Copy Markdown
Contributor

Summary

Reframes the ## Trust model section in CONTRIBUTING.md so the run-your-own-node model is unmistakable.

The previous wording ("node is trusted, wallet is thin" / "the wallet trusts the node") was easily misread as trusting a third party. It now states the actual model: the Bitcoin full-node model — your wallet trusts your node, exactly as a Bitcoin wallet trusts your own bitcoind. "Trusted node" means your node.

Clarifications added:

  • The node↔wallet split is packaging, not a trust boundary.
  • Self-hosting gives trustlessness and privacy at once.
  • A public operator can never steal / forge / double-spend (enforced cryptographically); using one is the same spectrum as an Electrum/SPV server vs. your own bitcoind.
  • The thin wallet/SDK is not a compromise — trustlessness comes from running your own node, not from anti-node logic in the client.

The existing hard rules (thin client, self-hosting easy, thin SDK) are preserved.

This block is mirrored verbatim across zk-coins/node, /sdk, /app, /docs — companion PRs keep all four identical.

Notes

  • Docs-only change, no code paths touched.
  • Prettier-clean; block verified byte-identical across all four repos.

@TaprootFreak
TaprootFreak marked this pull request as ready for review June 4, 2026 13:42
@TaprootFreak
TaprootFreak merged commit 8be44b5 into staging Jun 4, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant