Resilience Network
Pre-mainnet research network No public testnet yet Protocol manifest r28 Shielded transfers experimental Current status
Status

Current status

Resilience Network is pre-mainnet and has no public testnet. The next milestone is a transparent-only public testnet with shielded transfers off. It launches only after its release gates close, and we will not publish a date until they do.

Status as of 2026-10-13, reference implementation c3acec4, protocol manifest r28.

§1Capability matrix#

CapabilityStateActivationFirst public testnet
BFT consensus, ECVRF leader electionImplementedAlways onOn
Forced evidence inclusion, slashing, jailingImplementedAlways onOn
Transaction V2 with DIRECT, ROOT and SESSION authorityImplementedAlways onOn
P-256 session keys and the P256VERIFY precompileImplementedAlways onOn
EIP-1559-style fee marketImplementedAlways onOn
EVM, Shanghai semantics with documented deviationsImplementedAlways onOn
Sponsored transactionsImplementedAlways onOn
Guardian recoveryImplementedAlways on, opt-in per accountOn
.rsc namesImplementedname_service_activation_heightTo be decided
Delegation share transfers and vault readsImplementedliquid_staking_activation_heightTo be decided
Orchard shielded transfersExperimentalActivation height plus an explicit acknowledgmentOff
Remote signer over mutual TLS; encrypted keystoreImplementedOperator choiceAvailable; open key-custody finding on the remote signer
Certified snapshot bootstrapImplementedOperator choiceAvailable
Unbiasable threshold randomness beaconProposedNo
EVM randomness precompileBlocked on the beaconNo
Encrypted mempool or other MEV protectionDeferred by decisionNo
Hardware-wallet supportNot implementedNo
HSM or KMS validator signingNot implementedNo

§2Release gates#

Before a public transparent testnet

  • Close or contain the open availability and key-custody findings from the 2026-10-12 internal review.
  • Measure sustained load again after the 2026-10-08 liveness fix, on uncontended hardware.
  • Run the full native story suite and a mixed fault campaign of at least four hours on the exact public profile.
  • Exercise multi-host seed discovery, restart on retained storage, storage-failure recovery, and clock and network behavior.
  • Deliver a test alert end to end through the intended notification route.
  • Complete the robustness re-review.

Before mainnet or any network that carries value

  • Independent external audits of the protocol and, separately, of the shielded cryptography, with their findings fixed.
  • Gas and authorization schedules frozen after measurement on the minimum supported validator hardware.
  • A reviewed production custody path for validator keys.
  • A public genesis ceremony with a published commitment and allocation.
  • An adversarial public testnet period and a bug bounty.

§3Known limits today#

  • The planning ceiling is 20 TPS sustained until load is measured again.
  • Slot duration is a target. Finality time under load is measured, not guaranteed.
  • Pending transactions are public and block ordering is a local convention, so front-running is possible.
  • Light clients trust the validator set on first contact.
  • A withholding proposer can bias the randomness beacon, so contracts cannot read it.
  • A snapshot file carries no trust until it is certified against a live peer.
  • A protocol change requires a coordinated fresh genesis; there are no in-place migrations.

Sources: Feature reference; public testnet launch procedure; configuration reference; internal security review of 2026-10-12.