Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Conversation

@gavofyork
Copy link
Member

@gavofyork gavofyork commented Jan 30, 2019

Instead of the encoded items that make up the signing payload, it's the Blake2/256 of the encoded items whenever the payload length is greater than 256 bytes. This keeps the data needed to craft a signature nice and short.

@gavofyork gavofyork added A0-please_review Pull request needs code review. B1-releasenotes labels Jan 30, 2019
@gavofyork gavofyork added this to the 1.0gamma milestone Jan 30, 2019
@gavofyork
Copy link
Member Author

CC @jacogr

@rphmeier
Copy link
Contributor

why? ed25519 signing is already hashing these items to the curve

@rphmeier
Copy link
Contributor

also I think this will break some tests where things are signed manually

@gavofyork gavofyork merged commit 3f0c601 into master Jan 31, 2019
@gavofyork gavofyork deleted the gav-tx-hash-payload branch January 31, 2019 17:39
MTDK1 pushed a commit to bdevux/substrate that referenced this pull request Apr 12, 2019
* Transaction signing payload is hashed first

* Fix tests

* Rebuild wasm

* Fix tests

* Only take payload hash when payload.len > 256 bytes.

* Fix tests
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

A0-please_review Pull request needs code review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants