Skip to content

Gsd/phase 13 close v1 1 trusted peer genesis quorum policy and production - #360

Draft
henriqueaklein wants to merge 148 commits into
developfrom
gsd/phase-13-close-v1-1-trusted-peer-genesis-quorum-policy-and-production
Draft

Gsd/phase 13 close v1 1 trusted peer genesis quorum policy and production#360
henriqueaklein wants to merge 148 commits into
developfrom
gsd/phase-13-close-v1-1-trusted-peer-genesis-quorum-policy-and-production

Conversation

@henriqueaklein

Copy link
Copy Markdown
Contributor

No description provided.

- Define reusable bounded codec and manifest contracts
- Cover golden identity, normalization, malformed inputs, and tampering
- Register the focused genesis manifest test target
- Encode reviewed genesis fields with bounded big-endian canonical bytes
- Normalize and validate fixed-size trusted peer public keys
- Derive and verify domain-separated SHA-256 fingerprints
- register identical patterns in independent registry objects
- prove signer snapshots and owner teardown must remain node-local
- replace process-global registry storage with thread-safe object state
- let SecureCrdt own or accept an injected isolated registry
- route legacy lookups and registry tests through instance access
- register TrustedPeerRegistry and BurnConfig on their supplied SecureCrdt
- preserve owner-token teardown within the same registry instance
- fail factories when a same-node pattern is already registered
- move legacy SecureCrdt fixtures onto their owned registries
- process same-key values under distinct in-process signer policies
- retain one node's registration and quorum after peer teardown
- cover exact membership and burn threshold boundaries
- exercise canonical policy decoding and successor linkage
- prove proposed peers cannot authorize their own policy
- encode and validate versioned policy state with exact hash links
- enforce strict-majority membership and two-thirds burn floors
- bind successor authorization to the confirmed current policy
- Define typed trust snapshot and transition contract
- Cover restart, network mismatch, ancestry, and fork rejection
- Commit genesis, policy, and burn heads in synchronous atomic batches
- Revalidate canonical records, ancestry, and quorum proofs on every load
- Inject before and after batch-commit failures
- Require one stable stale loser under concurrent successors
- Return stale outcomes for competing same-version successors
- Preserve synchronous commit failure and recovery boundaries
- Record verified persistence and race-proof outcomes
- Capture TDD gates, verification, and rollback boundary
- exercise three production nodes with passive successor convergence
- cover PayEscrow provider updates and negative controls
- discover and deterministically activate retained successors on every refresh
- preserve explicit local admin activation while passive nodes consume foreign approvals
- Reopen identical trust and transaction storage after restart
- Require exactly one live manager and current callback ownership
- Retain fresh-client registry recovery as separate coverage
- Serialize lifecycle transitions and reject stale trust-ready posts
- Stop and release manager callbacks before replacement construction
- Track manager construction, start, and callback owner generations
- inject passive policy commit failure after retained quorum
- reconstruct over unchanged CRDT approvals without a new write
- require exact durable policy-v2 convergence and approval stability
- separate policy retry and suppression state from burn candidates
- merge authoritative retained policy candidates on every refresh
- process deterministic current-head winners with typed pending failures
- inspect the historical test and CreateNode helper separately
- prove same-path reuse and single-manager ownership mechanically
- reject policy v2 before deterministic burn v1 peer quorum
- prove production callbacks recover readiness and later policy activation
- add barrier-driven concurrent account generation counterexample
- add before- and after-readiness pinned signer regressions
- require independent reviewed CR-11 and CR-12 RED diagnostics
- publish account and transaction services as one generation-owned snapshot
- drain stale bridge work and reject callbacks from unpublished generations
- pin trusted-peer approval labels and signatures to one node authority
- add four exact no-write and final-owner RED regressions
- add deterministic listing and virtual-delay test seams
- validate each pre-fix diagnostic independently in XML
- classify refresh outcomes and retry only transient discovery failures

- dispatch through weak-owner system executor state with exact capped backoff

- prove autonomous recovery, exhaustion, coalescing, and final-owner release
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