Skip to content

Phase 1 Execution Brief – Consensus Network Foundation

This living brief documents the concrete deliverables completed during Phase 1 so engineering, governance, and mobilization teams remain synchronized while the DATU validator network comes online.

Validator Configuration Snapshot

Validator Tier Public Key History Archive Role Notes
datu-tier0-foundation Tier 0 (foundation steward) GBVHRGLHPCZHHP47DY7WKOAFLKJEIF67O7L7O42OGWIJDITCSOXWEINY s3://history.datu.foundation/core-foundation/ Custodian for the passphrase, anchors quorum intersection, and funds emergency recovery.
datu-tier1-east Tier 1 (government agency) GBHV6GP2UPHIQ27T5ANAU6ZQ23L7JFQLWZTIXEV4VXJT32J7Z6X7QR7E s3://history.datu.foundation/core-east/ Primary operator responsible for day-to-day ledger management and release coordination.
datu-tier1-west Tier 1 (government agency) GDUMHIOUG57CUX3BNBTWTNL5C7TBZO3N5LA4H4S67YHKYBNO22RKWPQ7 s3://history.datu.foundation/core-west/ Provides geographic redundancy and hosts the first production-grade Horizon endpoint.
datu-tier1-south Tier 1 (civil society) GD7KIZSLIA6Z5GXJW3I64DWTN7PX7TYVMY4PDLVXS53ANN253SXVJJCK s3://history.datu.foundation/core-south/ Operated by the civic-oversight coalition to guarantee public transparency.
datu-tier2-audit Tier 2 (independent auditor) GDPCADHCULMM34TAB54G2CUC7K26ID7DNKSCK76DQY2QBTY2E7BUMJGL s3://history.datu.foundation/core-audit/ Mirrors ledgers for compliance review and crisis recovery without voting weight during normal operations.

The validator roster is encoded in infrastructure/stellar-fork/config/quorumsets.toml and infrastructure/stellar-fork/config/stellar-core.cfg. Failure safety has been raised to 1 and UNSAFE_QUORUM disabled so consensus now requires supermajority agreement across independent operators.

Soroban Enablement

  • Execution budgets now reflect production needs: the Soroban config raises CPU instructions to 240,000,000, memory to 12 MB, and ledger read/write limits accordingly. These values match the MAX_SOROBAN_INVOKE_HOST_FUNCTIONS override in stellar-core.cfg to avoid runtime mismatches. See infrastructure/stellar-fork/config/soroban.toml.
  • Diagnostics are fully enabled with JSON and Prometheus export, plus 14-day event retention and 30-day metric retention to support the observability program tracked in Phase 6.
  • Cost multipliers (compute=1.0, io=1.2) are documented so CI can reproduce production execution caps during contract testing.

Initial Testnet Deployment Plan

Milestone Target Date Owner Key Outputs
Local quorum rehearsal 2025-10-15 Consensus engineering Launch additional compose profiles to simulate Tier 1/2 validators and validate quorum behaviour.
Remote archive dry run 2025-10-17 DevOps + validator operators Stand up S3 buckets per operator and test catchup from archival history.
Public RPC preview 2025-10-21 Horizon team Publish Horizon + Soroban RPC endpoint backed by datu-tier1-west, integrate Friendbot funding from integration account.
DATU Testnet v1 announcement 2025-10-24 Steering committee Release validator onboarding packet, publish public documentation, and open civic-feedback channels.

Pre-funded accounts supporting the rollout (Friendbot, QA scenarios, validator bonds, compliance reserve) are listed in config/accounts.json with their controlling signers. The deployment remains in the local-only phase until the history archives and onboarding packet tasks in the checklist are marked complete.

Mobilization Backlog Alignment

Technical Deliverable Mobilization Owner Dependency Description
Validator roster & quorum policy Governance working group chair Requires steering committee ratification and publication to fulfill Phase 0 charter commitments.
Soroban execution budget Compliance liaison Needs privacy impact and procurement review to confirm resource usage stays within approved envelopes.
Pre-funded account catalogue Treasury controller Supports financial oversight and anti-corruption reporting obligations captured in the mobilization backlog.
Testnet deployment milestones Project coordinator Drives cross-team updates in weekly status reports until Phase 0 exit criteria close.

Owners have acknowledged these dependencies in the shared backlog, and twice-weekly syncs are scheduled every Tuesday/Friday to clear any regulatory or tooling blockers before the public testnet announcement.

Risk Register Touchpoints

  • History archive readiness – Remote S3 buckets are not yet provisioned. Mitigation: DevOps to prototype archive automation by 2025-10-17 and document retention policies before remote validators join.
  • Validator onboarding packet – Drafting in progress. Mitigation: steering committee communications lead owns the packet and will circulate a review draft alongside the DATU Testnet v1 announcement prep on 2025-10-21.
  • Soroban cost drift – Changes to execution budgets require compliance sign-off. Mitigation: compliance liaison participates in Phase 1 syncs and tracks approvals in the mobilization backlog tracker.

Progress updates will continue to be captured in this brief and the running Project Progress changelog as additional checklist items close.