Verification
Summary
Section titled “Summary”This section tracks MoreBC2 evidence records, open questions, test plans, review coordination, and verification queues.
Start with the Verification evidence index. It is the canonical evidence summary for MoreBC2.
The dated records contain the detailed evidence. Plans are not completed results. Private review readiness is not public launch readiness.
1. Evidence index
Section titled “1. Evidence index”Canonical current evidence summary:
Older navigation/status pages:
- Older verification index - retained as a superseded/historical navigation page.
- Verification dashboard - retained as a legacy manually maintained dashboard concept.
2. Dated evidence records
Section titled “2. Dated evidence records”Local runtime and RPC:
- Local BitcoinII node inspection - 2026-07-10
- Read-only RPC smoke test - 2026-07-10
- Local RPC enablement plan
Developer platform and public infrastructure:
Project identity:
3. Open questions and known unknowns
Section titled “3. Open questions and known unknowns”Unresolved items stay in these queues until a dated record or source review resolves them:
4. Test plans and testing status
Section titled “4. Test plans and testing status”Plans are not completed results. They describe safe order, scope, or test coverage until a dated execution record exists.
- Command testing status
- Command smoke-test plan
- Command example scan
- Network test coverage map
- Network test run plan
- Codex task prompts
- Stale wording scan
5. Release verification
Section titled “5. Release verification”Release records are carefully bounded. Asset inventory is not binary verification, and maintainer roadmap context is not cryptographic proof.
- Release asset inventory attempt
- Release artifact checklist
- Release source comparison notes
- Network release comparison
- First review packet: release verification wording
6. Ecosystem checks
Section titled “6. Ecosystem checks”Ecosystem records and plans should distinguish reachable services from reliable, official, synced, or recommended services.
- Ecosystem direct check plan
- Public API, WebSocket, and Electrum smoke test - 2026-07-12
- Explorers
- APIs
- Exchanges
- Mining pools
- Infrastructure service directory
- Infrastructure status policy
7. Private review coordination
Section titled “7. Private review coordination”Private review pages are for narrow invite-only review. They do not make MoreBC2 public-ready.
- Private review readiness
- Narrow private review assignments
- Review feedback buckets
- First review packet: command safety
- First review packet: release verification wording
8. Project identity and status evidence
Section titled “8. Project identity and status evidence”Use these pages to keep canonical-source, naming, contact, and status claims scoped to the evidence.
- Project identity source check - 2026-07-10
- Verification evidence index
- Project status
- Known unknowns
- Open questions backlog
How to use this section
Section titled “How to use this section”- Check the Verification evidence index first.
- Follow the linked dated record for detailed evidence.
- Keep unresolved items in Open questions or Known unknowns.
- Keep plans separate from completed records.
- Keep private review coordination separate from public launch readiness.
- Do not upgrade a page or claim without the required evidence record.
- Do not move an item out of verification until the evidence is strong enough for the target page.
- Keep current facts, historical facts, research ideas, and discussion proposals separate.
- Record the source type used: source code, release artifact, official website, archive, maintainer statement, local test, or current direct check.
- Command examples should remain unverified until run locally with environment details.
- Release artifact claims should remain unverified until assets and hashes are checked directly.
- Ecosystem claims should remain unverified until checked directly and dated.
- Developer test-suite plans should remain separate from user-facing command smoke tests.
Verification
Section titled “Verification”Status: Draft Primary sources checked: Current verification section structure, verification evidence index, dated records, open-question queues, test plans, release records, ecosystem records, and private-review coordination pages Notes: This page is a router for verification material. It does not verify BitcoinII protocol behavior, service reliability, release binaries, or ecosystem claims.