Since AEIP-21, genesis address became a major information used in many places.
Currently the genesis address of a transaction is retrieved from P2P but there is no proof if it's the real genesis address.
Also in term of code, this require to pass the genesis address as a parameter in a lot of functions.
Describe the solution you'd like
We should add the genesis address of the transaction chain in the validation stamp. So all validation nodes will ensure this is the good one, and then whenever this transaction is used, nodes can have the proof of the validity of the genesis address.
Additional context
In term of DB storage, there is a specific encoding system for all transaction field and we could avoid to encode the genesis address since the genesis is the name of the file in DB. So when decoding we could use the filename to fill the genesis address of the stamp.
Is your feature request related to a problem?
Since AEIP-21, genesis address became a major information used in many places. Currently the genesis address of a transaction is retrieved from P2P but there is no proof if it's the real genesis address. Also in term of code, this require to pass the genesis address as a parameter in a lot of functions.
Describe the solution you'd like
We should add the genesis address of the transaction chain in the validation stamp. So all validation nodes will ensure this is the good one, and then whenever this transaction is used, nodes can have the proof of the validity of the genesis address.
Additional context
In term of DB storage, there is a specific encoding system for all transaction field and we could avoid to encode the genesis address since the genesis is the name of the file in DB. So when decoding we could use the filename to fill the genesis address of the stamp.
Epic
No response