Skip to content
New issue

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

Add genesis address in Validation Stamp #1562

Open
Neylix opened this issue Sep 30, 2024 · 0 comments · May be fixed by #1588
Open

Add genesis address in Validation Stamp #1562

Neylix opened this issue Sep 30, 2024 · 0 comments · May be fixed by #1588
Assignees
Labels
DB Involve database enhancements transaction Involve transactions

Comments

@Neylix
Copy link
Member

Neylix commented Sep 30, 2024

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

@Neylix Neylix added transaction Involve transactions DB Involve database enhancements labels Sep 30, 2024
@bchamagne bchamagne self-assigned this Oct 30, 2024
@bchamagne bchamagne linked a pull request Nov 4, 2024 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DB Involve database enhancements transaction Involve transactions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants