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

will the Remark data on the chain be deleted? #276

Open
luojiandan opened this issue Sep 4, 2023 · 4 comments
Open

will the Remark data on the chain be deleted? #276

luojiandan opened this issue Sep 4, 2023 · 4 comments
Labels
documentation Improvements or additions to documentation

Comments

@luojiandan
Copy link

After mainnet upgrade, will the Remark data on the chain be deleted? Some data comes from snapshot:
image

@luojiandan luojiandan added the documentation Improvements or additions to documentation label Sep 4, 2023
@luojiandan
Copy link
Author

@Holt666 @xrdavies
Why is there no remarks in snapshot data after the upgrade? Can this problem be avoided? Because when we write some information to the main network, it is deleted after upgrading, which will very affect the application scenario of the main network.

@yyajphd
Copy link
Contributor

yyajphd commented Sep 5, 2023

@luojiandan Thank you for your question. This upgrade modifies the amount data structure of XDAG in the block. The previous block data cannot be compatible with the upgraded data. So we did a snapshot. At present, XDAG is still in the stage of rapid development. In the future, we will fully consider this and reduce the times of snapshots as much as possible. I appreciate your support of XDAG.

@luojiandan
Copy link
Author

hi,@yyajphd, thanks for your reply. Can you keep remark data in snapshot? If users want to write data on XDAG chain, this Remark is very important.

@LucasMLK
Copy link
Contributor

LucasMLK commented Sep 7, 2023

@luojiandan The snapshot feature is intended to speed up upgrades as xdag is still evolving rapidly. If it is compatible with the old data format, developers will need to spend more than twice the time to be compatible with the old transaction structure, and the possibility of errors is high. Therefore, the developer will do its best to ensure the correct amount of XDAG for each address and the fairness of the entire game, and will also do its best to keep XDAG updated and iterated. I hope everyone can understand the trade-off between development difficulty and efficiency. Thanks for your feedback. Each transaction in the transaction history has a comment field. As a snapshot, saving too much information will lose the meaning of the snapshot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants