-
Notifications
You must be signed in to change notification settings - Fork 59
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
Comments
@Holt666 @xrdavies |
@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. |
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. |
@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. |
After mainnet upgrade, will the Remark data on the chain be deleted? Some data comes from snapshot:
![image](https://private-user-images.githubusercontent.com/5663556/265417636-7ceaed2a-8329-45a5-b7a8-bedcfa84e4d2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwNTMyOTUsIm5iZiI6MTcyNDA1Mjk5NSwicGF0aCI6Ii81NjYzNTU2LzI2NTQxNzYzNi03Y2VhZWQyYS04MzI5LTQ1YTUtYjdhOC1iZWRjZmE4NGU0ZDIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MTlUMDczNjM1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZWEwODBmMjM2ZTc4ZTBkMzQzZTU3Y2I5NzBiYTY1NmRkZDczODBjNjE3OTdlMjIzMjQ5NzI4Njg0Y2FkOGJlNyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.-OLxpHXBxXcrB5S4oWLOQWA2F7YHu-Y63iYMN95Dw9c)
The text was updated successfully, but these errors were encountered: