We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue keeps track of considering the idea of adding test vectors for message encoding.
When this idea is implemented, the spec will contain for each message test cases for encoding and decoding.
A test case for encoding would look like:
LockedTransfer(field1=value1, ..., fieldN=valueN) with private key 0x....... is encoded as 0x........
LockedTransfer(field1=value1, ..., fieldN=valueN)
0x.......
A test case for decoding would look like:
The byte sequence 0x...... is decoded as LockedTransfer(field1=vaue1, ..., fieldN=valueN) signed by address 0x.......
0x......
LockedTransfer(field1=vaue1, ..., fieldN=valueN)
@kelsos has a script that's useful for generating the encoding test vectors. https://github.com/kelsos/raiden-protocol-messages/blob/master/messages/messages.py
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This issue keeps track of considering the idea of adding test vectors for message encoding.
When this idea is implemented, the spec will contain for each message test cases for encoding and decoding.
A test case for encoding would look like:
A test case for decoding would look like:
@kelsos has a script that's useful for generating the encoding test vectors. https://github.com/kelsos/raiden-protocol-messages/blob/master/messages/messages.py
The text was updated successfully, but these errors were encountered: