Activation notice: block 34,135,466
This page records what changed on chain 114514 at block 34,135,466.
In effect since block 34,135,466. Node 0.9.17 swapped in at block 34,135,465, and every node rule below turned on one block later. Gateway 0.9.17 and the history archive that serves the points reads started in the same window. The gateway rows below shipped with them. The page records what changed at that boundary.
{"type":"account_state","address":"0x…"} returns the current height. Use it to check where the chain is.
Every change below moves at one height, so the chain gains one boundary for the whole release.
The pin is one block above the swap. The outgoing node commits block 34,135,465 and then halts, so that block still ran the old rules. The new rules apply from the first block after it.
Faucet claims are signed
| Surface | Before the height | Now |
|---|---|---|
POST /faucet expires | ignored | required, unix seconds. The node refuses a value in the past and a value more than 600 s ahead of its clock |
POST /faucet signature | ignored | required. An EIP-191 personal_sign by the recipient over a four-line text that names the address, the chain id and expires. See sign the claim |
POST /faucet amount | caps the USDC grant | ignored. The grant is fixed: 3000 USDC and 10 MTF |
POST /faucet with amount: 0 | refused: amount must be positive | accepted. The node ignores amount |
| An unsigned claim | accepted | refused: faucet claim needs expires and signature: sign the claim text with the receiving wallet |
The errors table has each new refusal and its exact text. The rule of one claim per address does not change. There is no Ethereum mainnet balance requirement.
Why: each address can claim once only. Without a signature, any caller can use the one claim of an address that it does not control. The signature does not cover amount. If the node used it, anyone who saw a signed body could send it first with a small amount and use the one claim of that address.
What to do:
- Sign every claim with the receiving wallet. Set
expiresto the current time plus 300. - Send no
amount.
The points reads are served
| Surface | Before the height | Now |
|---|---|---|
points_weeks, points_leaderboard, points_user | 400 UNKNOWN_TYPE | served. Each answers with empty rows until the first week is published |
Why: the history archive computes the weekly points table, and the gateway serves it. The archive publishes weeks only after the operator starts the program. Points count from genesis, so no week is lost.
What to do: read the three types. Treat empty rows as "no week is published yet", not as zero points.