Repository navigation
v1.7.0
Proxima v1.7.0 (released Thursday 2026-11-19): mandatory for every node. Library upgrade 7 activates at slot 283000, Friday 2026-11-20 19:30:59 UTC. A node still on an older version stops following the network at that slot.
Library upgrade 7 changes how sequencers earn the branch bonus and who may issue branches. Like every library upgrade, it switches the new rules on at one slot for all nodes, with no network reset.
1. Sequencers choose their own branch bonus.
- Today the branch bonus is a random amount of up to 5 PROX per slot, decided by the ledger. From the upgrade, each sequencer chooses the bonus its branches mint, from 1 mote (0.000001 PROX) to 5 PROX.
- When branches tie on coverage, each gets a lottery number between 0 and 10 PROX that nobody can choose, and the bonus it asked for is deducted from it. The highest result wins; a result can be negative, only the order counts. Asking for more means a bigger prize but a lower chance; asking for less, a better chance but a smaller prize.
- Bids are sealed: a sequencer commits to its bonus before the slot ends and reveals it in its branch, so nobody can see the others' bids first.
- With N sequencers competing, the bonus settles at about 10 / N PROX. Splitting capital into more sequencers no longer pays: every extra sequencer lowers the bonus for all.
- Set your bonus with
proxi node seq set-params --bonus <motes>(1 to 5000000). Without the setting, the sequencer asks 5 PROX, the most allowed, and will win few ties.proxi node seq infoshows the bonus asked.
2. Who may issue branches and accept new delegations.
- To issue branches and have new delegations frozen, a sequencer needs either 20,000 PROX of its own on its chain or 100,000 PROX of coverage (its own balance plus delegations frozen to it).
- A sequencer below both keeps running: it issues milestones, takes tag-alongs and keeps its frozen delegations until they expire. It does not issue branches and takes no new delegations.
- Starting a new sequencer chain still needs 10,000 PROX, as today.
proxi node seq infoshows where a sequencer stands against both bounds.
3. No sequencer milestones in the last eight ticks of a slot. A sequencer transaction other than a branch may be stamped at tick 119 at the latest; later ones are invalid from the upgrade. The reference sequencer does this by itself. Operators of other sequencer software must change their schedule before the slot.
4. Anyone can top up a delegation, for example a mining pool or an exchange paying straight into a user's delegation: proxi node delegate topup <amount> --delegation <id>. The tokens become the delegation owner's; the owner's rights do not change.
Also:
-
The sequencer version
v2is removed. A node configured withsequencer.version: v2runsv3, the default. -
proxi node delegate amountaccepts a sequencer that qualifies by coverage. -
Nodes apply stricter resource limits to script evaluation, from the release.
-
This release includes every change of v1.6.15 to v1.6.18.
Update every node before Friday 19:30 UTC: build from the tag and restart, one sequencer at a time if you run several, waiting until each is producing again. A node that missed the slot is updated the same way; if it does not catch up, restore it from a snapshot taken after the slot. No config change required. Update proxi as well: the new commands and the consolidator's and miner's choice of delegation targets follow the new bounds. From the slot a new sequencer chain can only be started with proxi v1.7.0: an older proxi node seq init_genesis makes a chain the ledger refuses. Delegators running the consolidator must update it before the slot: an older consolidator does not know the coverage path, treats a sequencer qualifying by coverage alone as unable to freeze, and asks its delegations to stop.