Add support for Nimiq Albatross PoS transaction serialization #4110
+9
−7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sisou
requested review from
Milerius,
satoshiotomakan and
ar-g
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The transaction format for both signing and sending changed slightly for Nimiq Albatross PoS, to encode optional sender data and support more signature methods (now also supports ECDSA and WebAuthn).
How to test
To test, connect your wallet to a Nimiq PoS testnet node (provided in our joined Telegram channel). To be valid in the testnet, the
NETWORK_IDhas to be set to5.Types of changes
Checklist
If you're adding a new blockchain