SPS Validator v1.3.0 Release Announcement

[sps.dao]

---

This is going to be our biggest update since launch and we're going to provide two snapshots below to help get everyone back online after the recent instability around the HIVE hard fork.

Full snapshot:
https://d33cuc2qlex36c.cloudfront.net/prod-snapshot-2025-11-25.zip

Lite snapshot:
https://d33cuc2qlex36c.cloudfront.net/prod-slim-snapshot-2025-11-25.zip

v1.3.0 (block-hash-breaking)

This is a block-hash-breaking release, which means you have to update before the transition block number to continue to receive rewards.

Please see the update guide in the README for updating your node to the different types of releases.

In addition to the instructions in the README, you MUST run ./run.sh build AFTER updating and BEFORE starting your validator. There are schema changes in this update, but the validator is backward compatible with them until the transition block.

The transition block is 101928051, which should be around 1130am ET on 2025-12-09.

Updates

• new staking rewards formula
• new license rewards formula
• new block validation rewards formula
• double spend protection in token_transfer and token_transfer_multi (pass a "key" field with a unique value, and it will fail any token transfers after that with the same key - scoped to the account)
• missing 5 blocks in a row will automatically disable a node so theyre not chosen for new blocks
• block 101201159 is now spoofed because many nodes read this block from bad hive nodes.
• block 101387262 is now spoofed because many nodes read this block from bad hive nodes.
• BLOCKS_BEHIND_HEAD will work now. The default is now 3. If you have this set in your .env file, you may want to update it to 3.
• Adds a new option to create a "slim" snapshot when using the ./run.sh snapshot command.
• The Validator UI token balances page will sync the filters to the query parameters
• Test suite has been updated to test the reward amounts are correct from block validation rewards and staking rewards
• You can now use ./run {command} - omitting the .sh.

This update changes the database schema, so ./run.sh build will have to be run after updating a node. Node operators do not need to wait until the transition block to run build. They can run it ahead of time and the validator will handle keeping the block hash consistent even with a different schema.