See RELEASE for workflow instructions.
-
#5118 reduce number of tortoise results returned after recovery.
this is hotfix for a bug introduced in v1.2.0. in rare conditions node may loop with the following warning:
2023-10-02T15:28:14.002+0200 WARN fd68b.sync mesh failed to process layer from sync {"node_id": "fd68b9397572556c2f329f3e5af2faf23aef85dbbbb7e38447fae2f4ef38899f", "module": "sync", "sessionId": "29422935-68d6-47d1-87a8-02293aa181f3", "layer_id": 23104, "errmsg": "requested layer 8063 is before evicted 13102", "name": "sync"}
-
#5091 Separating PoST from the node into its own service.
-
#5061 Proof generation is now done via a dedicated service instead of the node.
-
#5154 Enable TLS connections between node and PoST service.
PoST proofs are now done via a dedicated process / service that the node communicates with via gRPC. Smapp users can continue to smesh as they used to. The node will automatically start the PoST service when it starts and will shut it down when it shuts down.
-
#5138 Bump poet to v0.9.7
The submit proof of work should now be up to 40% faster thanks to code optimization.
-
#5143 Select good peers for sync requests.
The change improves initial sync speed and any sync protocol requests required during consensus.
-
#5109 Limit number of layers that tortoise needs to read on startup.
Bounds the time required to restart a node.
-
#5171 Set minimal active set according to the observed number of atxs.
It will prevent ballots that under report observed atxs from spamming the network. It doesn't have impact on rewards.
-
#5169 Support pruning activesets.
As of epoch 6 activesets storage size is about ~1.5GB. They are not useful after verifying eligibilities for ballots in the current epoch and can be pruned.
Pruning will be enabled starting from epoch 8, e.g in epoch 8 we will prune all activesets for epochs 7 and below. We should also run an archival node that doesn't prune them. To disable pruning we should configure
"main": { "prune-activesets-from": 4294967295 }
-
#5189 Removed deprecated "Best Provider" option for initialization.
With v1.1.0 (https://github.com/spacemeshos/go-spacemesh/releases/tag/v1.1.0) selecting
-1assmeshing-opts-providerhas been deprecated. This option has now been removed. Nodes that already finished initialization can leave this setting empty, as it is not required any more to be set when no initialization is performed. For nodes that have not yet created their initial proof the operator has to specify which provider to use. For Smapp users this is done automatically by Smapp, users that do not use Smapp may usepostcli -printProviders(https://github.com/spacemeshos/post/releases) to list their OpenCL providers and associated IDs.
This upgrade is incompatible with versions older than v1.1.6.
At the start of the upgrade, mesh data will be pruned and compacted/vacuumed. Pruning takes longer for nodes that joined the network earlier. For 1-week-old nodes, it takes ~20 minutes. for 3-week-old nodes it takes ~40 minutes. The vacuum operation takes ~5 minutes and requires extra disk space to complete successfully. If the size of state.sql is 25 GiB at the beginning of upgrade, the WAL file (state.sql-wal) will grow to 25 GiB and then drop to 0 when the vacuum is complete. The node will resume its normal startup routine after the pruning and vacuum is complete. The final size of state.sql is expected to be ~1.5 GiB.
A new config poet-request-timeout has been added, that defines the timeout for requesting PoET proofs.
It defaults to 9 minutes so there is enough time to retry if the request fails.
Config option and flag p2p-disable-legacy-discovery is dropped. DHT has been the only p2p discovery
mechanism since release v1.1.2.
Support for old certificate sync protocol is dropped. This update is incompatible with v1.0.x series.
- #5031 Nodes will also fetch from PoET 112 for round 4 if they were able to register to PoET 110.
- #5067 dbstat virtual table can be read periodically to collect table/index sizes.
In order to enable provide following configuration:
"main": {
"db-size-metering-interval": "10m"
}- #4998 First phase of state size reduction. Ephemeral data are deleted and state compacted at the time of upgrade. In steady-state, data is pruned periodically.
- #5021 Drop support for old certificate sync protocol.
- #5024 Active set will be saved in state separately from ballots.
- #5032 Ativeset data pruned from ballots.
- #5035 Fix possible nil pointer panic when node fails to persist nipost builder state.
- #5079 increase atx cache to 50 000 to reduce disk reads.
- #5083 Disable beacon protocol temporarily.
It is critical for most nodes in the network to use v1.1.5 when layer 20 000 starts. Starting from that layer active set will not be gossipped together with proposals. That was the main network bottleneck in epoch 4.
- #4969 Nodes will also fetch from PoET 111 for round 3 if they were able to register to PoET 110.
- #4965 Updates to PoST:
- Prevent errors when shutting down the node that can result in a crash
postdata_metadata.jsonis now updated atomically to prevent corruption of the file.
- #4956 Active set is will not be gossipped in every proposal. Active set usually contains list of atxs that targets current epoch. As the number of atxs grows this object grows as well.
- #4993 Drop proposals after generating a block. This limits growth of the state.
- #4765 hare 3 consensus protocol.
Replacement for original version of hare. Won't be enabled on mainnet for now. Otherwise protocol uses significantly less traffic (atlest x20), and will allow to set lower expected latency in the network, eventually reducing layer time.
- #4879 Makes majority calculation weighted for optimistic filtering. The network will start using the new algorithm at layer 18_000 (2023-09-14 20:00:00 +0000 UTC)
- #4923 Faster ballot eligibility validation. Improves sync speed.
- #4934 Ensure state is synced before participating in tortoise consensus.
- #4939 Make sure to fetch data from peers that are already connected.
- #4936 Use correct hare active set after node was synced. Otherwise applied layer may lag slightly behind the rest.
Legacy discovery protocol was removed in #4836.
Config option and flag p2p-disable-legacy-discovery is noop, and will be completely removed in future versions.
With #4893 Nodes are given more time to publish an ATX Nodes still need to publish an ATX before the new PoET round starts (within 12h on mainnet) to make it into the next PoET round, but if they miss that deadline they will now continue to publish an ATX to receive rewards for the upcoming epoch and skip one after that.
- #4845 API to fetch opened connections.
grpcurl -plaintext 127.0.0.1:9093 spacemesh.v1.AdminService.PeerInfoStream
{
"id": "12D3KooWEcgADBR4zHirw7YAt6nUtCNhbPWkB2fnHAemnG5cGf2n",
"connections": [
{
"address": "/ip4/46.4.81.145/tcp/5001",
"uptime": "1359.186975782s",
"outbound": true
}
]
}
{
"id": "12D3KooWHK5m83sNj2eNMJMGAngcS9gBja27ho83t79Q2CD4iRjQ",
"connections": [
{
"address": "/ip4/34.86.244.124/tcp/5000",
"uptime": "1108.414456262s",
"outbound": true
}
],
"tags": [
"bootnode"
]
}- 4795 p2p: add ip4/ip6 blocklists
Doesn't affect direct peers. In order to disable:
{
"p2p": {
"ip4-blocklist": [],
"ip6-blocklist": []
}
}