Update ERC-5559: Move to Draft #388
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
makoto
reviewed
Apr 23, 2024
makoto
reviewed
Apr 23, 2024
| type: Standards Track | ||
| category: ERC | ||
| created: 2022-06-23 | ||
| requires: 712 | ||
| created: 2024-04-15 |
There was a problem hiding this comment.
The original creation date should stay as is
There was a problem hiding this comment.
Is that the standard practise? Reference? I didn't know this was the case
There was a problem hiding this comment.
@Arachnid can probably comment on it but I would be very strange that creation date changes as if all the prior specification didn't exist.
There was a problem hiding this comment.
@SamWilsn & @abcoathup can probably clear this up ↑
makoto
reviewed
Apr 23, 2024
makoto
reviewed
Apr 23, 2024
makoto
reviewed
Apr 23, 2024
|
After discussions with other authors of the proposal, we have decided that this draft makes more sense as a standalone ERC, not a PR to EIP-5559, in order to preserve existing users. The new pull request is now here: #404 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following proposal is a superseding version of EIP-5559: Cross Chain Write Deferral Protocol, aka CCIP-Write, replacing Ethereum L1 storage with L2 chains and cryptographically secure databases with an aim to cut gas costs and further privacy while retaining the secure aspects of on-chain storage. Methods in this document specifically target security and cost-effectiveness of write deferrals in context of databases. The cross-chain data written with these methods can be retrieved by generic EIP-3668-compliant contracts completing the cross-chain data life cycle.