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

CIP to introduce authored blobs #147

Merged
merged 10 commits into from
Jun 4, 2024
Merged

Conversation

cmwaters
Copy link
Contributor

This CIP is in reference to this issue: celestiaorg/celestia-app#3316

Note that there is a diagram so when changing the name of the file and folders, make sure to change the name of the folder in the assets directory and update this CIP that references it

Copy link
Member

@evan-forbes evan-forbes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still chewing but otherwise LGTM!

cips/cip-blob-verified-signer.md Outdated Show resolved Hide resolved
@nashqueue
Copy link
Member

Maybe we should add the fact that you need versioning for the CreateCommitment function. As we might be adding other things in the future which will change the shares and therefore the share commitment.

Create commitment will now have to be aware of the signer.

Copy link
Collaborator

@rootulp rootulp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for including the diagram!

cips/cip-blob-verified-signer.md Outdated Show resolved Hide resolved
cips/cip-blob-verified-signer.md Outdated Show resolved Hide resolved
cips/cip-blob-verified-signer.md Outdated Show resolved Hide resolved
@cmwaters
Copy link
Contributor Author

Maybe we should add the fact that you need versioning for the CreateCommitment function. As we might be adding other things in the future which will change the shares and therefore the share commitment.

Create commitment will now have to be aware of the signer.

The CreateCommitment function has the following signature:

func CreateCommitment(blob *blob.Blob, merkleRootFn MerkleRootFn, subtreeRootThreshold int) ([]byte, error) 

As it includes the blob, which has the signer as well as the share version, I don't think anything will need to change to the function signature. Of course within the function, the commitment construction will depend on whether the signer is present in the blob or not

Given the current specification change, the new loop is simplified:

- Retrieve all blobs in the subscribed namespaces
- Verify the blobs inclusion by namespace

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Disclaimer: I'm a newb) what do you mean? Aren't the blobs returned guaranteed to be included?

@cmwaters cmwaters requested a review from rootulp May 25, 2024 21:05
cips/cip-blob-verified-signer.md Outdated Show resolved Hide resolved
Copy link
Member

@jcstein jcstein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but would like to resolve the open discussions before merging

@cmwaters
Copy link
Contributor Author

cmwaters commented Jun 3, 2024

@jcstein all comments should be resolved now

@cmwaters cmwaters requested a review from jcstein June 3, 2024 10:14
@rootulp
Copy link
Collaborator

rootulp commented Jun 4, 2024

Assigned this CIP-21. FYI @jcstein

cips/cip-21.md Show resolved Hide resolved
@jcstein jcstein merged commit e0c8863 into celestiaorg:main Jun 4, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants