See RELEASE for workflow instructions.
-
#6408 Prevent empty DB connection pool by freeing connections upon errors during DB operations. This mostly fixes issues when a node is under heavy load from the API.
-
#6417 Fix initial post being deleted when the node is restarted or times out before the first ATX is published.
-
#6422 Further improved performance of the proposal building process to avoid late proposals.
-
#6443 Improve eviction of ineffectual transactions in the database which will now show up as ineffectual when querying them from the API.
-
#6431 Fix db-allow-schema-drift handling
-
#6451 Fix a possible deadloop in the beacon protocol.
-
#6470 Fix I/O buffering issue which could be affecting QUIC connections.
The previous version of go-spacemesh introduced a bug into the code that handles incoming ATXs. This bug would cause
the node to store invalid data in the database and could lead to a node disagreeing about the state of the network with
other nodes. This version fixes the bug. If you are running v1.7.5 you should upgrade to v1.7.6 as soon as possible and
rebuild your state.db, either via quicksync, from a backup from before you upgraded or by full syncing from genesis.
- #6398 Fixed a bug where the node would store invalid information about ATXs in the database.
New event types introduced in the API of the node, see API #382 and 2 previously existing events where renamed. Old events were marked as deprecated. Please update your automations to use new event types.
-
#6378 Improved handling of malicious identities. This reduces the number of DB queries needed during ATX validation.
-
#6386 The API of the node now has its own DB connection pool to reduce the load on the main DB connection pool.
-
#6387 Fix an issue were in rare cases invalid proofs for malicious identities were created.
-
#6393 Further improved proposal building process to avoid late proposals in 1:N setups and during cyclegap.
-
#6382 Improve visibility around poet registrations in events.
- #6370 Fix an issue in v2alpha1 account service API.
This release prepares the node for enabling hare4 in the near future. No special upgrade steps are required.
- #6360 Prepare node for hare4.
This version adds new and updates existing v2alpha1 API endpoints and does not require any special upgrade steps.
Additionally performance improvements were made to the node.
-
#6289 Added write coalescing for ballots, reducing the amount of time and CPU we're spending on writing ballots.
-
#6353 Add new malfeasance API.
-
#6357 Add template address to account service.
This version has no code changes to v1.7.0, only the release process was updated to fix a problem with the windows build.
- #6351 Fixed filenames of windows builds.
Ensure you are running v1.6.x before upgrading to v1.7.0, if you skip v1.6.x your node will not be able to fully migrate its local state. Upgrading from v1.6.x to v1.7.0 will require a time consuming database migration that optimizes how the node stores state locally and will not allow you to downgrade to v1.6.x again. The upgrade process requires you to have at least the same amount of free disk space as your current database size for the duration of the migration.
The command line flag --scan-malfeasant-atxs has been removed. All malfeasant ATXs before 1.6.0 have been marked as
such and the node will continue to scan new ATXs for their validity.
Larger database migrations will now be done with a temporary copy of the existing database to speed up the process. This will require up to the same amount of additional disk space as the DB of the node is using for the duration of the migration, after which it will be freed again.
The node will now continue to try to register at all configured PoETs until the end of the registration window instead of giving up on non-responding PoETs after 15-20 minutes.
Various smaller improvements have been made to the node to improve performance and reduce the amount of log spam.
The node is now stricter with detecting DB schema drifts. For most users this gives additional safety to not lose data when upgrading or after a crash. If you are running a node with a custom database schema for instance because you are using tools that also write to the nodes database your node might refuse to start. In this case you can take a look at CODING.md to see how to build a custom node with a modified schema.
The node can also be started with db-allow-schema-drift set to true in the main section of the nodes configuration to
allow the node to start with a different schema. This is not recommended and should only be used if you know what you
are doing.
-
#6116 After a restart the node will now try to register at all PoETs it hasn't registered yet at instead of skipping registration when it already has at least one successful registration in the DB.
-
#6003 Improve database schema handling. This includes schema drift detection which may happen after running unreleased versions.
-
#6136 Fixed an issue where the node retried registering for the PoET round only for 15-20 minutes instead of continuing until the start of the round.
-
#6085 Database migrations now use
VACUUM INTOwith a temporary copy of the existing database to speed up the process. -
#6274 Additional queries to PoETs are now cached to reduce the number of requests made to PoET servers.
-
#6317 Improved the proposal building process. This will reduce the likelihood of nodes publishing proposals late in 1:N setups.
-
#6269 Use sub query instead of left join to speed up transaction list query.
-
#6278 Reduce logging levels of some messages to reduce noise.
-
#6279 Speed up initialization of tortoise by reducing the number of queries to the DB.
-
#6268 Fix incorrect timing collection for proposal builder.
-
#6197 Fix falling back to poet PoW if recertification failed after getting a 401 on registering
-
#6241 Improve speed of ATX cache warmup.
- #6213 Adds
labels_per_unitto the v2alpha1 Network Info API.
- #6248 Fixed node not being able to handle more than 6.55M ATXs per epoch.
-
#6198 Configure default TTL for caching poet's /v1/info
-
#6199 Cache poet's /v1/pow_params to reduce the number of requests made to PoET servers.
-
#6185 Optimize mempool
-
#6187 The merge tool now ignores files that are not
.keyfiles in theidentitiesdirectory when merging two nodes. -
#6128 Reduce logs spam
-
#6107 Cache PoET queries between multiple identities on the same node. This will reduce the number of requests the node makes to the PoET server during the cyclegap.
-
#6152 Fixed a bug where in rare cases the node would panic due to the closing of a closed channel in the fetcher.
-
#6142 Fix node not dropping peers that are broadcasting invalid ATXs.
- #6137 Fix hanging ATX sync.
-
#5793 Reduced hare committee 8x from 400 to 50 to decrease network traffic caused by Hare.
-
#6099 Adds new metrics to the API to provide insights into the performance and behavior of the node's APIs.
-
#6115 Increase the number of supported ATXs to 8.0 Mio.
- #6112 Adds vesting, vault, and drain vault contents to the v2alpha2 Transaction API. Fixes the 'unspecified' transaction type.
- #6053 Fixed an issue where the node could fail to select a positioning ATX during the cyclegap and miss the registration window for the next PoET round.
With this release the minimum supported version for Intel Macs is now macOS 13 (Ventura) and for Apple Silicon Macs it is macOS 14 (Sonoma) or later (#5879).
This update removes migration code for go-spacemesh databases created with versions before v1.5.0. Upgrading to this version requires going through v1.5.x first. Removed migrations for:
- legacy keys in the post data directory (#5907).
- ATX blob separation and always populating nonce column in atxs (#5942)
This update introduces certificate authentication against PoETs. The default values are included in the mainnet preset and changing them is not needed unless you experience connection issues to a certifier:
"main": {
"certifier": {
"client": {
"retry-delay": "1s",
"max-retry-delay": "30s",
"max-retries": 5,
}
}
}The usage of a certifier needs to be supported by the PoET your node is connecting to. If you are using the default PoETs the switch will happen automatically in the near future, so no action is needed from your side. If you are operating your own PoET and want to use certificate authentication please refer to the documentation:
- PoET README for configuration of the PoET.
- certifier README for setting up a certifier.
- #5792 Add hole punching info and data transfer stats to the API.
-
#5863 Identity files are now created with 0600 permissions, to prevent other users on the same system to access the private keys.
-
#5866 Reduce logging levels of some messages to reduce noise.
-
#5877 Fix verifying ATX chain after checkpoint.
-
#5882 Use backoff during routing discovery. This should reduce network load from the peer discovery mechanism when it's enabled.
-
#5888 Handle DHT discovery startup errors properly
-
#5932 Fix caching malfeasance when processing new proofs
-
#5943 Fix timing out querying proof in 1:N in a presence of a broken Poet.
Previously, every identity waited for the full timeout time (~20 minutes) before giving up.
-
#5958 Fix node incorrectly detecting a remote smeshing setup as supervised.
Ensure that your key file in
data/identitiesis namedlocal.keyif you run a supervised node or with the change the node will not start. -
#5965 Start considering ballots that still contain the deprecated inlined activeset as invalid. go-spacemesh references the active set via hash since v1.3.0, and has been pruning the data of old ballots since then as well.
-
#5927 Fixed vulnerability in the way a node handles incoming ATXs. This vulnerability allows an attacker to claim rewards for a full tick amount although they should not be eligible for them.
-
#6031 Fixed an edge case where the storage units might have changed after the initial PoST was generated but before the first ATX has been emitted, invalidating the initial PoST. The node will now try to verify the initial PoST and regenerate it if necessary.
-
#6044 The node will now reuse
blake3hashers in a pool which reduces stress on the garbage collector. -
#6055 Increased limits to support up to 7.0 Mio ATXs per epoch.
- #5999 Increase limits to allow up to 6.0 Mio ATXs per epoch.
-
#5943 Fix timing out querying proof in 1:N in a presence of a broken Poet.
Previously, every identity waited for the full timeout time (~20 minutes) before giving up.
- #5969 Increase ResponseMessage to 183500800
-
#5963 Increase supported number of ATXs to 5.5 Mio.
-
#5952 Optimized searching for a positioning ATX. Instead of a slow database query the ATX builder now uses the in-memory ATX store to pick a positioning ATX.
-
#5929 Fix "no nonce" error when persisting malicious (initial) ATXs.
-
#5930 Check if identity for a given malfeasance proof exists when validating it.
-
#5923 Fix high memory consumption and performance issues in the proposal handler.
This release includes our first CVE fix. A vulnerability was found in the way a node handles incoming ATXs. We urge all node operators to update to this version as soon as possible.
- Fixed a vulnerability in the way a node handles incoming ATXs. This vulnerability allows an attacker to claim rewards for a full tick amount although they should not be eligible for them.
-
#5904 Avoid repeated searching for positioning ATX in 1:N
-
#5911 Avoid pulling poet proof multiple times in 1:N setups
- #5896 Increase supported number of ATXs to 4.5 Mio.
- #5814 Removed in-code local DB migrations. Updating to this version requires going through v1.4 first.
-
#5807 Implement SMIP-0002: remove vesting vault cliff.
-
#5840 Allow vaults to spend received (as well as vested) coins. Fixes an oversight in the genesis VM implementation.
-
#5791 Speed up ATX queries. This also fixes ambiguity of nonces for equivocating identities.
- #5839 Fix a bug where nodes would stop agreeing on the order of TX within a block.
-
#5796 Reject p2p messages containing invalid malfeasance proofs.
-
#5797 Improve logging around ATX building process.
-
#5802 Increase the number of supported ATX per epoch to 3.5 Mio.
-
#5803 Fixed PoST verifiers autoscaling for 1:N setups.
-
#5815 Add spread to the discovery advertisement interval.
-
#5819 The node will now refuse connections from post services if no coinbase account is set.
- #5777 Adjusted GRPC keepalive parameters on node to allow pings every 60 seconds and send keepalive pings every 10 minutes if no activity from the client is observed.
-
#5753 Fix for a possible segmentation fault in setups with remote post services when an identity does their initial proof.
-
#5755 improve efficiency of downloading and applying blocks after ballots were counted.
-
#5761 don't interrupt sync if ballots in a layer were ignored or rejected.
-
#5762 Fix a bug where the node could get stuck in a loop when trying to fetch a block that is not in the mesh.
-
#5730 Fixed a bug where the node behaves incorrectly when first started with supervised smeshing.
-
#5731 The default listen address for
PostServiceis now127.0.0.1:0instead of127.0.0.1:9094. This will ensure that a node binds the post service to a random free port and prevents multiple instances of the post service from binding to the same port. -
#5735 Don't hold database connections for long in fetcher streaming mode
-
#5736 Fixed slow POST initialization on Windows.
-
#5738 sql: fix epoch ATX ID cache deadlock
-
#5707 Fix a race on closing a channel when the node is shutting down.
-
#5709 Prevent users from accidentally deleting their keys, if they downgrade to v1.3.x and upgrade again.
-
#5710 Node now checks the database version and will refuse to start if it is newer than expected.
-
#5562 Add streaming mode for fetcher. This should lessen GC pressure during sync
-
#5684 Use separate fetcher protocol for active sets. This enables separate pacers for active set requests
-
#5718 Sync malfeasance proofs continuously.
The post service now has its own endpoint separate from grpc-private-listener. The default for grpc-post-listener
is 127.0.0.1:9094. In contrast to grpc-tls-listener this endpoint does not require setting up mTLS.
The post service cannot connect to grpc-private-listener anymore. If you are using a remote smeshing setup please
adjust your configuration accordingly. If you are using a remote setup with mTLS over a private network you can switch
to using grpc-post-listener to not require the overhead of mTLS. We however strongly recommend using an mTLS
encrypted connection between the post service and the node over insecure connections (e.g. over the Internet).
Smeshers using the default setup with a supervised post service do not need to make changes to their node configuration.
With this release the node has fully migrated its local state into local.sql. During the first start after the
upgrade the node will migrate the data from disk and store it in the database. This change also allows the PoST data
directory to be set to read only after the migration is complete, as the node will no longer write to it.
NOTE: To ensure a successful migration make sure that the config contains all PoETs your node is using.
Upgrading requires changes in config and in CLI flags (if not using the default).
⚠ Users that use additional poet servers need to add their address and public key to one of the lists below, depending on their configuration method.
This argument was replaced by --poet-servers that take JSON-encoded array of poet server descriptors
(address, public key). The default value is
[
{
"address": "https://mainnet-poet-0.spacemesh.network",
"pubkey": "cFnqCS5oER7GOX576oPtahlxB/1y95aDibdK7RHQFVg="
},
{
"address": "https://mainnet-poet-1.spacemesh.network",
"pubkey": "Qh1efxY4YhoYBEXKPTiHJ/a7n1GsllRSyweQKO3j7m0="
},
{
"address": "https://poet-110.spacemesh.network",
"pubkey": "8Qqgid+37eyY7ik+EA47Nd5TrQjXolbv2Mdgir243No="
},
{
"address": "https://poet-111.spacemesh.network",
"pubkey": "caIV0Ym59L3RqbVAL6UrCPwr+z+lwe2TBj57QWnAgtM="
},
{
"address": "https://poet-112.spacemesh.network",
"pubkey": "5p/mPvmqhwdvf8U0GVrNq/9IN/HmZj5hCkFLAN04g1E="
}
]The existing field poet-server that accepted an array of addresses of poet servers
was replaced by a new field poet-servers that accepts an object containing an address and a public key.
The default configuration was adapted and doesn't need any action on the user's side. Users who
overwrite the poet-server field need to adapt their config accordingly. The default
configuration is as follows:
{
"main": {
"poet-servers": [
{
"address": "https://mainnet-poet-0.spacemesh.network",
"pubkey": "cFnqCS5oER7GOX576oPtahlxB/1y95aDibdK7RHQFVg="
},
{
"address": "https://mainnet-poet-1.spacemesh.network",
"pubkey": "Qh1efxY4YhoYBEXKPTiHJ/a7n1GsllRSyweQKO3j7m0="
},
{
"address": "https://poet-110.spacemesh.network",
"pubkey": "8Qqgid+37eyY7ik+EA47Nd5TrQjXolbv2Mdgir243No="
},
{
"address": "https://poet-111.spacemesh.network",
"pubkey": "caIV0Ym59L3RqbVAL6UrCPwr+z+lwe2TBj57QWnAgtM="
},
{
"address": "https://poet-112.spacemesh.network",
"pubkey": "5p/mPvmqhwdvf8U0GVrNq/9IN/HmZj5hCkFLAN04g1E="
}
]
}
}NOTE: This is a new feature, not yet supported by Smapp and possibly subject to change. Please use with caution.
A node can now manage multiple identities and their life cycle. This reduces the amount of data that is needed to be broadcasted / fetched from the network and reduces the amount of data that needs to be stored locally, because only one database is needed for all identities instead of one for each.
To ensure you are eligible for rewards of any given identity, the associated PoST service must be running and connected to the node during the cyclegap set in the node's configuration. After successfully broadcasting the ATX and registering at a PoET server the PoST services can be stopped with only the node having to be online.
This change moves the private keys associated for an identity from the PoST data directory to the node's data directory
and into the folder identities (i.e. if state.sql is in folder data the keys will now be stored in data/identities).
The node will automatically migrate the key.bin file from the PoST data directory during the first startup and copy
it to the new location as local.key. The content of the file stays unchanged (= the private key of the identity hex-encoded).
To add a new identity to a node, initialize PoST data with postcli and let it generate a new private key for you:
./postcli -provider=2 -numUnits=4 -datadir=/path/to/data \
-commitmentAtxId=c230c51669d1fcd35860131e438e234726b2bd5f9adbbd91bd88a718e7e98ecbMake sure to replace provider with your provider of choice and numUnits with the number of PoST units you want to
initialize. The commitmentAtxId is the commitment ATX ID for the identity you want to initialize. For details on the
usage of postcli please refer to postcli README.
During initialization postcli will generate a new private key and store it in the PoST data directory as identity.key.
Copy this file to your data/identities directory and rename it to xxx.key where xxx is a unique identifier for
the identity. The node will automatically pick up the new identity and manage its lifecycle after a restart.
Setup the post-service binary or
docker image with the data and configure it to connect to your
node. For details refer to the post-service README.
If you have multiple nodes running and want to migrate to use only one node for all identities:
- Stop all nodes.
- Convert the nodes to remote nodes by setting
smeshing-starttofalsein the configuration/cli parameters and renaming thelocal.keyfile to a unique name in the PoST data directory. - Use the
merge-nodesCLI tool to merge your remote nodes into one. Follow the instructions of the tool to do so. It will copy your keys (as long as you gave all of them unique names) and merge yourlocal.sqldatabases. - Start the node that you used as target for
merge-nodesand is now managing the identities. - For every identity setup a post service to use the existing PoST data for that identity and connect to the node. For details refer to the post-service README.
WARNING: DO NOT run multiple nodes with the same identity at the same time! This will result in an equivocation and permanent ineligibility for rewards.
-
#5599 new atx sync that is less fragile to network failures.
new atx sync will avoid blocking startup, and additionally will be running in background to ask peers for atxs. by default it does that every 4 hours by requesting known atxs from 2 peers. configuration can be adjusted by providing
{
"syncer": {
"atx-sync": {
// interval and number of peers determine how much traffic node will spend for asking about known atxs.
// for example in this configuration every 4 hours it will download known atxs from 2 peers.
// with 2_000_000 atxs it will amount to ~128MB of traffic every 4 hours.
"epoch-info-request-interval": "4h",
"epoch-info-peers": 2,
// number of retries to fetch any specific atx.
"requests-limit": 20,
// number of full atxs that will be downloaded in parallel.
// you can try to tune this value up if sync will be slow.
"atxs-batch": 1000,
// atx sync progress will be reported when 10% of known atxs were downloaded, or every 20 minutes.
// if it is too noisy tune them to your liking.
"progress-every-fraction": 0.1,
"progress-on-time": "20m"
}
}
}-
#5293 change poet servers configuration The config now takes the poet server address and its public key. See the Upgrade Information for details.
-
#5390 Distributed PoST verification.
The nodes on the network can now choose to verify only a subset of labels in PoST proofs by choosing a K3 value lower than K2. If a node finds a proof invalid, it will report it to the network by creating a malfeasance proof. The malicious node will then be blacklisted by the network.
-
#5592 Extend node with option to have multiple PoST services connect. This allows users to run multiple PoST services, without the need to run multiple nodes. A node can now manage multiple identities and will manage the lifecycle of those identities. To collect rewards for every identity, the associated PoST service must be running and connected to the node during the cyclegap set in the node's configuration.
-
#5651 New GRPC service
spacemesh.v1.PostInfoService.PostStatesallowing to check the status of PoST proving of all registered identities. It's useful for operators to figure out when post-services for each identity need to be up or can be shutdown.An example output:
{ "states": [ { "id": "874uW9N/y0PwUXxJ8Kb8Q2Yd+sqhpGJYkLbjlkIz5Ig=", "state": "IDLE", "name": "post0.key" }, { "id": "sBq/pHUHtzczY1quuG2muPGkksfVldwnH0M/eUPc3qE=", "state": "PROVING", "name": "post1.key" } ] } -
#5685 A new tool
merge-nodeswas added to the repository and release artifact. It can be used to merge multiple nodes into one. This is useful for users that have multiple nodes running and want to migrate to use only one node for all identities. See the Upgrade Information for details.
-
#5678 API to for changing log level without restarting a node. Examples:
grpcurl -plaintext -d '{"module": "sync", "level": "debug"}' 127.0.0.1:9093 spacemesh.v1.DebugService.ChangeLogLevel grpcurl -plaintext -d '{"module": "*", "level": "debug"}' 127.0.0.1:9093 spacemesh.v1.DebugService.ChangeLogLevel
"*" will replace log level for all known modules, expect that some of them will spam too much.
-
#5612 Add relay command for running dedicated relay nodes
-
#5641 Rename
node_state.sqltolocal.sql.To avoid confusion with the
state.sqldatabase, thenode_state.sqldatabase has been renamed tolocal.sql. -
#5219 Migrate data from
nipost_builder_state.bintolocal.sql.The node will automatically migrate the data from disk and store it in the database. The migration will take place at the first startup after the upgrade.
-
#5418 Add
grpc-post-listenerto separate post service fromgrpc-private-listenerand not require mTLS for the post service. -
#5465 Add an option to cache SQL query results. This is useful for nodes with high peer counts.
If you are not using a remote post service you do not need to adjust anything. If you are using a remote setup make sure your post service now connects to
grpc-post-listenerinstead ofgrpc-private-listener. If you are connecting to a remote post service over the internet we strongly recommend using mTLS viagrpc-tls-listener. -
#5601 measure latency from all requests in sync This improves peers selection logic, mainly to prevent asking slow peers for collection of atxs, which often blocks sync.
-
5602 Optimize client side of fetcher to avoid encoding when not needed.
-
5561 Reuse atxdata in Tortoise to optimize memory usage.
-
#5586 Do not try to publish proofs for malicious ATXs during sync. Publishing is blocked during sync because
Syncer::ListenToATXGossip()returns false, and thus every malicious ATX being synced was causing an error resulting in an interruption of sync. -
#5603 Do not try to sync over transient (relayed) connections. This fixes possible sync issues when hole punching is enabled.
-
#5618 Add index on ATXs that makes epoch ATX requests faster
-
#5619 Updated data structures to support the network with up to 2.2 unique smesher identities.
-
#5564 Use decaying tags for fetch peers. This prevents libp2p's Connection Manager from breaking sync.
-
#5522 Disable mesh agreement sync protocol. It reduces number of requests for historical activation ids.
-
#5571 Adjust to 2.2M ATXs
-
#5530 Adjusted cache sizes for the increased number of ATXs on the network.
-
#5511 Fix dialing peers on their private IPs, which was causing "portscan" complaints.
- #5517
Added a flag
--smeshing-opts-verifying-disableand a config parametersmeshing-opts-verifying-disablemeant for disabling verifying POST in incoming ATXs on private nodes. The verification should be performed by the public node instead.
-
#5441 Fix possible nil-pointer dereference in blocks.Generator.
-
#5512 Increase EpochActiveSet limit to 1.5M to prepare for 1M+ ATXs.
-
#5515 Increase fetcher limit to 60MiB to prepare for 1M+ ATXs.
-
#5518 In rare cases the node could create a malfeasance proof against itself. This is now prevented.
- #5502 Increase limits of p2p messages to compensate for the increased number of nodes on the network.
-
#5479 p2p: make AutoNAT service limits configurable. This helps with AutoNAT dialback to determine nodes' reachability status.
-
#5490 The path in
smeshing-opts-datadirused to be resolved relative to the location of theservicebinary when running the node in supervised mode. This is no longer the case. The path is now resolved relative to the current working directory. -
#5489 Fix problem in POST proving where too many files were opened at the same time.
-
#5498 Reduce the default number of CPU cores that are used for verifying incoming ATXs to half of the available cores.
-
#5462 Add separate metric for failed p2p server requests
-
#5464 Make fetch request timeout configurable.
-
#5463 Adjust deadline during long reads and writes, reducing "i/o deadline exceeded" errors.
-
#5494 Make routing discovery more configurable and less spammy by default.
-
#5511 Fix dialing peers on their private IPs, which was causing "portscan" complaints.
-
#5470 Fixed a bug in event reporting where the node reports a disconnection from the PoST service as a "PoST failed" event. Disconnections cannot be avoided completely and do not interrupt the PoST proving process. As long as the PoST service reconnects within a reasonable time, the node will continue to operate normally without reporting any errors via the event API.
Users of a remote setup should make sure that the PoST service is actually running and can reach the node. Observe the log of both apps for indications of a connection problem.
- #5467 Fix a bug that could cause ATX sync to stall because of exhausted limit of concurrent requests for dependencies. Fetching dependencies of an ATX is not limited anymore.
-
#5442 Limit concurrent requests for ATXs to reduce usage of memory and p2p streams.
-
#5394 Add rowid to tables with inefficient clustered indices. This reduces database size and improves its performance.
-
#5334 Hotfix for API queries for activations. Two API endpoints (
MeshService.{AccountMeshDataQuery,LayersQuery}) were broken because they attempt to read all activation data for an epoch. As the number of activations per epoch has grown, this brute force query (i.e., without appropriate database indices) became very expensive and could cause the node to hang and consume an enormous amount of resources. This hotfix removes all activation data from these endpoints so that they still work for querying other data. It also modifiesLayersQueryto not return any ineffective transactions in blocks, since there's currently no way to distinguish between effective and ineffective transactions using the API. -
#5417 Prioritize verifying own ATX's PoST.
-
#5423 Wait to be ATX-synced before selecting the commitment ATX for initialization. Also, remove unnecessary wait for ATXs to be synced before beginning initialization if the commitment ATX is already selected.
- #5432 Fixed a possible race that is caused by a node processing the same bootstrapped active set twice.
-
#5419 Fixed
0.0.0.0not being a valid listen address forgrpc-private-listener. -
#5424 Further increased limits for message sizes and caches to compensate for the increased number of nodes on the network.
This release is not backwards compatible with v1.2.x. Upgrading will migrate local state to a new database. The migration will take place at the first startup after the upgrade. Be aware that after a successful upgrade downgrading isn't supported and might result in at least one epoch of missed rewards. See change #5207 for more information.
This release is the first step towards separating PoST from the node. Proof generation is now done via a dedicated service. This service is started automatically by the node and is shut down when the node shuts down. In most setups this should work out of the box, but if you are running into issues please check the README.md file for more information on how to configure the node to work with the PoST service.
-
#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.
-
#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. -
#5207 Move the NiPoST state of a node into a new node-local database.
The node now uses 2 databases:
state.sqlwhich holds the node's view on the global state of the network andnode_state.sqlwhich holds ephemeral data of the node.With this change
post.binandnipost_challenge.binfiles are no longer used. The node will automatically migrate the data from disk and store it in the database. The migration will take place during the first startup after the upgrade. If you want to downgrade to a version before v1.3.0 you will need to restorestate.sqlas well aspost.binandnipost_challenge.binfrom a backup and do so before the end of the PoET round in which you upgraded. Otherwise the node will not be able to participate in consensus and will miss at least one epoch of rewards. -
#5209 Removed API to update poet servers from SmesherService.
-
#5276 Removed the option to configure API services per endpoint. The public listener exposes the following services: "debug", "global", "mesh", "transaction", "node", "activation" The private listener exposes the following services: "admin", "smesher", "post" The mTLS listener exposes only the "post" service.
-
#5199 Adds smesherID to rewards table. Historically rewards were keyed by (coinbase, layer). Now the primary key has changed to (smesherID, layer), which allows querying rewards by any subset of layer, smesherID, and coinbase. While this change does add smesherID to existing API endpoints (
GlobalStateService.{AccountDataQuery,AccountDataStream,GlobalStateStream}), it does not yet expose an endpoint to query rewards by smesherID. Additionally, it does not re-index old data. Rewards will contain smesherID going forward, but to refresh data for all rewards, a node will have to delete its database and resync from genesis. -
#5329 P2P decentralization improvements. Added support for QUIC transport and DHT routing discovery for finding peers and relays. Also, added the
ping-peersfeature which is useful during connectivity troubleshooting.static-relaysfeature can be used to provide a static list of circuit v2 relays nodes when automatic relay discovery is not desired. All of the relay server resource settings are now configurable. Most of the new functionality is disabled by default unless explicitly enabled in the config viaenable-routing-discovery,routing-discovery-advertise,enable-quic-transport,static-relaysandping-peersoptions in thep2pconfig section. The non-conditional changes include values/provides support on all of the nodes, which will enable DHT to function efficiently for routing discovery. -
#5367 Add
no-main-overridetoplevel config option and--no-main-overrideCLI option that makes it possible to run "nomain" builds on mainnet. -
#5384 to improve network stability and performance allow the active set to be set in advance for an epoch. This allows the network to start consensus on the first layer of an epoch.
- #5384 to improve network stability and performance allow the active set to be set in advance for an epoch.
-
#5373 automatic scaling of post verifying workers to a lower value (1 by default) when POST proving starts. The workers are scaled up when POST proving finishes.
-
#5382 avoid processing same (gossiped/fetched) ATX many times in parallel
- increased the max response data size in p2p to 40MiB
-
further increased cache sizes and p2p timeouts to compensate for the increased number of nodes on the network.
-
#5329 P2P decentralization improvements. Added support for QUIC transport and DHT routing discovery for finding peers and relays. Also, added the
ping-peersfeature which is useful during connectivity troubleshooting.static-relaysfeature can be used to provide a static list of circuit v2 relays nodes when automatic relay discovery is not desired. All of the relay server resource settings are now configurable. Most of the new functionality is disabled by default unless explicitly enabled in the config viaenable-routing-discovery,routing-discovery-advertise,enable-quic-transport,static-relaysandping-peersoptions in thep2pconfig section. The non-conditional changes include values/provides support on all of the nodes, which will enable DHT to function efficiently for routing discovery.
- increased default cache sizes to improve disk IO and queue sizes for gossip to better handle the increasing number of nodes on the network.
- cherry picked migrations for active sets to enable easier pruning in the future
-
#5289 build active set from activations received on time
should decrease the state growth at the start of the epoch because of number of unique activets.
-
#5291 parametrize queue size and throttle limits in gossip
-
reduce log level for "atx omitted from active set"
-
#5302 improvements in transaction validation
-
#5263 randomize peer selection without this change node can get stuck after restart on requesting data from peer that is misbehaving. log below will be printed repeatedly:
2023-11-15T08:00:17.937+0100 INFO fd68b.sync syncing atx from genesis
-
#5264 increase limits related to activations
some of the limits were hardcoded and didn't account for growth in atx number. this change is not required for node to work correct in the next epoch, but will be required later.
- #5247 exits cleanly without misleading spamming
Fixes a bug that would spam with misleading log on exit, such as below:
2023-11-09T11:13:27.835-0600 ERROR e524f.hare failed to update weakcoin {"node_id": "e524fce96f0a87140ba895b56a2e37e29581075302778a05dd146f4b74fce72e", "module": "hare", "lid": 0, "error": "set weak coin 0: database: no free connection"}
This release enables hare3 on testnet networks. And schedules planned upgrade on mainnet. Network will have downtime if majority of nodes don't upgrade before layer 35117. Starting at layer 35117 network is expected to start using hare3, which reduces total bandwidth requirements.
-
#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"}
-
#5109 Limit number of layers that tortoise needs to read on startup.
Bounds the time required to restart a node.
-
#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.
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 Activeset 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 (at least 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": []
}
}