Releases: singnet/snet-daemon
Releases · singnet/snet-daemon
SingularityNET Daemon v3.1.0
Releasing Daemon version v3.1.0
- Support to track free-call usage as part of Daemon storage
- New commands to view the usage of a user and also ability to reset the used calls to zero for a given user
- Feature to restrict access only to certain users
- Improved messages on errors and logging
- Ability to allow service provider to access details of state service
- Increased code coverage through test cases
SingularityNET Daemon v3.0.0
Releasing Daemon version v3.0.0
SingularityNET Daemon v2.0.2
Release Daemon version with v2.0.2
SingularityNET Daemon v2.0.1
Release Daemon version with v2.0.1
SingularityNET Daemon v2.0.0
Release Daemon version v2.0.0
SingularityNET Daemon v1.1.2
Released Daemon Version v1.1.2
SingularityNET Daemon v1.1.1
Released Daemon Version v1.1.1, Disabling BlockChain
SingularityNET Daemon v1.1.0
Released Daemon version v1.1.0
SingularityNET Daemon v1.0.0
Released v1.0.0
Version Stamping on the Daemon
- CLI support to determine the current version of Daemon
- If there is a newer version of the Daemon available, then a message is logged accordingly advising you to consider upgrading to the latest.
- Version is now also stored as part of metrics collected from the Daemon
Support claims on older group ID
- Service provider will now be able to claim their funds even if the group-id changes.
Improved Authorisation checks on state Service
- Abstracting the authorisation logic out of control service and use it as a common piece across control service and state service
- Add block number and MPE Address, pre defined names as part of message signed.
Support for Stateless logic
- Refer to the Documentation
Support for Support cross compilation with xgo
- Refer to the [xgo Documentation] (https://github.com/karalabe/xgo)
Auto determine the registry address from platform-contracts based on the network selected
- Daemon will auto determine the Registry address, Block chain end point based on the network type you specify in the configuration , for more details refer to the configuraiton blockchain_network_selected
Protos from Daemon are now part of the Release aritifcats
- All protos are available under the proto directory on the latest release from git
Keeping the max message size received a config key and defaulting it to 4MB
- refer to the configuration max_message_size_in_mb
Clean up of claim command from Daemon
- With Control service now introduced , Daemon does not require the private key anymore . All Block chain transactions are done through snet-cli
Improved Logging
- Removed unwanted logging on heartbeat checks
- Improved language on error messages
SingularityNET Daemon v0.1.10
Release Notes
- Optimizing the check on Group ID.
- Ensure claim works for the change in Group ID.