Skip to content

DEVNET REHEARSAL

Factory upgrade workspace.

The replacement factory uses immediate reviewed upgrades on Devnet. Track verification and the remaining release gates.

Replacement Devnet factory deployed

The replacement factory starts with the immutable development guard. Future upgrades can execute immediately after two reviewer attestations; no 48-hour migration is required for this new program.

The retired factory and its proposals are preserved but are no longer the active deployment. Production uses a separately reviewed guard with a six-hour challenge. Existing custody notices are separate.

Inspect development guard

Review the factory upgrade

Actual Devnet factory update: 2.1-day releases, scoped milestone agents and governed coin metadata. Mainnet remains disabled. All reviewer wallets are founder-controlled.

Read the exact inspection report

Target
Ez288n8SpxVGkgGbkqHhzBmb1YoXZaAU83rPdsxmyZhU
Proposal
6PLGnTzhmQweYuGx4PF1QCzENNmpAE4arsqH5xzkpNkq
Code SHA-256
2faaa11375b9cb9e912a7851477ca659f679c5ee0b18335586feeceacd034c1a
Report SHA-256
085fd2d1a6706c811930c4dd54b471e6d01fb5ebcafbb6ffd121e25cee476537
Buffer rent refund recipient
92DFCXk28gwHZLzKoBzKj7tCeLZk3EtEdi5WaLBARjHc

Developer creates the proposal; two reviewers approve; then any funded wallet can execute immediately. Each wallet pays its Devnet transaction fee. Creation also pays proposal-account rent.

Network: Solana devnet. Use development-network SOL for fees.

Upgrade the Devnet factory

First initialize the factory’s reviewed development guard, then transfer upgrade authority. Each step requires approval from two existing Squads members and its current 48-hour delay. The factory code upgrade follows this handoff.

  1. Create and approve the guard configuration
  2. Execute after the current vault delay
  3. Create, approve and execute the authority transfer
  4. Review and install the factory artifact under the new guard

Reducing the old vault delay cannot skip this wait: that configuration change also waits under the current delay and would conflict with the factory’s custody checks.

Development only. Repository funds remain governed by the existing custody vault. Public launches stay disabled.

Read the upgrade evidence ↗

Network: Solana devnet. Use development-network SOL for fees.

Two members must approve. Squads enforces the 48-hour delay onchain. This workspace cannot bypass it or enable public trading.

Completed disposable-target rehearsal

First development upgrade

Same-bytecode rehearsal on the disposable Devnet target. No factory release or token transfers.

Read the exact inspection report

Target
H1EKDzq9RsZNXA7XnJfrHgsEed5JfL1ZKYh37d7ziysR
Proposal
BvtrEPPFLsqu2JTRYzjRjqacBfjHvJYGnxztbU8B4cPF
Code SHA-256
c3fddb612283036972b5976bf9c3f18388da3e8f5cfa402d8970876ce029600d
Report SHA-256
e2c0c1bfab4a64c900cae443bd766cd1d8316e1c9b36f712ae71ca3438c95af7
Buffer rent refund recipient
92DFCXk28gwHZLzKoBzKj7tCeLZk3EtEdi5WaLBARjHc

Developer creates the proposal; two reviewers approve; then any funded wallet can execute immediately. Each wallet pays its Devnet transaction fee. Creation also pays proposal-account rent.

Network: Solana devnet. Use development-network SOL for fees.

Reproducible build evidence · Current readiness and recovery steps · Factory validation evidence

The previous immutable seven-day guard is retired from development use. New deposits are paused; existing deposits remain withdrawable when unlocked.

Deposit Devnet voting tokens

Switch your wallet to Solana Devnet. Your wallet has been allocated TESTGOV tokens and 0.02 Devnet SOL for this rehearsal. These are test assets. This legacy guard still requires seven days before deposited tokens can count toward a new proposal; the replacement will require six hours.

Network: Solana devnet. Use development-network SOL for fees.

Wallet-control proof tools

Confirm your wallet

This is a message signature. No SOL is needed. It does not approve an upgrade or give Evangel permission to move funds.

Proofs expire after seven days and are bound to this exact candidate and participant list. They confirm control of keys, not reviewer independence or code review.

Future development upgrades

  1. Stage the inspected factory artifact and publish its exact upgrade report.
  2. Have two configured reviewers attest to that proposal.
  3. Execute the factory upgrade after its required approvals, then test launch, trading and payouts on Devnet before considering public activation.

Wallet-control messages below are bound to the replacement development guard. They do not approve upgrades or replace reviewer transaction signatures.

Candidate: Inspect deployed guard

Reviewed binary SHA-256: c3fddb612283036972b5976bf9c3f18388da3e8f5cfa402d8970876ce029600d