Test network. No presale. Wallet loss is permanent.

Upgrades and dev council

Every update: submit, approve, wait, take effect.

Contract and node updates are submitted here and wait out a public timelock before they take effect. Until 60 NGOs are first elected, two of the three dev council keys can approve node updates (7 days; each operator chooses to install them). Contract updates, and after the handover every update, need a DAO vote with a majority of the elected NGOs: 7 days for contracts, 14 days for nodes.

No wallet connected. Pages that change state use your browser wallet on chain 87869.
Dev councilactive
Elected NGOs0 / 60
Node version requirednone yet
This node9.0.0

Dev council

active until 60 NGOs are elected for the first time (now 0). Then it retires for good.

The council can never touch the Treasury, balances, the 12 % (DevVesting), the NGO election or its rules, or the handover rule, and it replaces no contract: every system contract holds PSY or feeds the election, the Treasury or the volunteer fund. It can approve node updates, change the committee bond and the role candidacy deposit (48 hours), and pause (at most 7 days in a row before the handover, then 7 days without).
SeatDev Account walletCouncil keyKey change waiting
Dev Account 10x4774424a…10a7a30xaf68682840f502d0c17075b82ed96a964f5c546b–
Dev Account 20x2ddfaa87…f646850x5d99dacaa99f38451450ca6c24a3386e93e88467–
Dev Account 30xb14974d7…54a3830x52b85be446924e63b807d10702e68ae278a86741–

Council actions

#ActionWhatApproved byState
No council actions yet.

Update plans

#UpdateStateApproved by
Nothing submitted yet.

Check an update yourself

  1. Contract update: check out the plan's commit, run cd contracts && forge build, and compare keccak256 of the runtime code with the plan's code hash (cast keccak $(cast code <new code address> --rpc-url https://rpc.psyrob.com)). The node copies the code only if the hash still matches when the timelock ends.
  2. Node update: download the release, run sha256sum SHA256SUMS.txt and compare with the plan; then sha256sum -c SHA256SUMS.txt checks every file. From the activation block, nodes older than the required version stop and say so.

Submit and approve

Submit an update (anyone)

Council: propose an action (first key)

Sent from a council key. A second key approves with the form below; pauses and node update approvals take effect at once (the update then waits its 7 days), parameter changes (committeeBond, candidacyDeposit) after 48 hours.

Council: approve an action (second key)

Run a parameter change after 48 hours (anyone)

Replace a council key (from the Dev Account wallet)

Takes effect after 48 hours. Another seat can cancel it in that time.

Cancel another seat's key change (council key)

Apply a key change after 48 hours (anyone)

After the handover, approve with an Upgrade proposal: target 0x7070000000000000000000000000000000000012, calldata approve(planNumber).