Separate signatures from other passive data - Githubissues

koinos / koinos-types

The Rosetta Stone of the Koinos ecosystem. Allows for the interpretation of Koinos data structures in a multitude of languages. Useful in the development of microservices, clients, and smart contracts.

MIT License

12 stars 3 forks source link

Separate signatures from other passive data #40

Closed theoreticalbts closed 4 years ago

theoreticalbts commented 4 years ago

We had the idea that "signature == passive data." This doesn't quite work because there are actually two design requirements here that are in tension:

(a) Signature data has similar data flow to passive data, it affects validity but not semantics.
(b) Signature cryptographically depends on passive data, but cannot cryptographically depend on itself

So let's resolve this as follows:

Put passive and signature data in the same Merkle root.
When generating a transaction signature, it depends on the transaction passive data
When generating a block signature, it depends on the transaction signatures, block passive data and transaction passive data