-
Notifications
You must be signed in to change notification settings - Fork 44
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
move cip 21 into last call #209
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reference implementation still needs to be filled out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Add reference implementation
- Add last call deadline
+1 to @rootulp's review
Co-authored-by: Rootul P <[email protected]>
bytes data = 2; | ||
uint32 share_version = 3; | ||
uint32 namespace_version = 4; | ||
+ // Signer is sdk.AccAddress that paid for this blob. This field is optional |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[question] can this feature be used with feegrant? If yes, and we have:
- celestiaA agrees to pay gas for all message for celestiaB
- celestiaB submits an authored blob and uses gas from celestiaA.
- Whose address goes in the signer field?
If it's celestiaB then should we stop using the term "that paid for this blob" and instead use something like:
// Signer is sdk.AccAddress that submitted this blob.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After reading through this CIP again recently, I'm a little confused how this would handle blobs submitted with feegrant as described in this thread. cc: @cmwaters as well for review
bytes data = 2; | ||
uint32 share_version = 3; | ||
uint32 namespace_version = 4; | ||
+ // Signer is sdk.AccAddress that paid for this blob. This field is optional |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+ // Signer is sdk.AccAddress that paid for this blob. This field is optional | |
+ // Signer is sdk.AccAddress that signed this blob. This field is optional |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So even though the fee granter paid for the blob to be included on-chain, the MsgPayForBlobs submitter (celestia1rgj3z5rfydj3xulhm6glqr0zs7j8rr9rfh6ekw) is the authored blob "signer".
@rootulp - So in this case shouldn't it be // Signer is sdk.AccAddress that signed this blob
?
Callum is OOO, maybe we should merge this as-is and we can edit it after the fact if that comment about "paid for" vs "submitted" is confusing for anyone else. cc: @jcstein thoughts? |
I think we can implement this feedback after it's in Last Call. However, here's some food for thought: IIRC, the fee Granter/Payer account does not show any messages when blobs are posted. So If I had blob X with Grantee/Signer A and Granter/Payer B, it would only show on chain for Grantee/Signer A
Accounts used in demo: |
Thanks for the links! That seems like expected behavior because the fee granter didn't submit a |
No description provided.