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

commitment: add asset type field to asset commitment structure #278

Merged
merged 3 commits into from
May 23, 2023

Conversation

ffranr
Copy link
Contributor

@ffranr ffranr commented May 16, 2023

All assets included within a given asset commitment must have the same asset type. This change helps to reinforce that idea.

@ffranr ffranr requested review from jharveyb and guggero May 16, 2023 17:03
@ffranr ffranr mentioned this pull request May 16, 2023
3 tasks
Copy link
Member

@guggero guggero left a comment

Choose a reason for hiding this comment

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

Nice quality of life improvement. But I actually think that we should check on the TapCommitmentKey instead, which includes the asset ID (or group key) which should both already be covered by type checks (or maybe worth taking a quick look at whether we prevent different types of assets being minted into the same group).

commitment/asset.go Outdated Show resolved Hide resolved
All assets included within a given asset commitment must have the same
asset type. This change helps to reinforce that idea.
@ffranr ffranr force-pushed the assetcommitment-type branch from cb41e3d to 1cfb3ae Compare May 17, 2023 17:07
@ffranr ffranr requested a review from guggero May 17, 2023 18:04
@dstadulis
Copy link
Collaborator

quickly funnel assets into their proper commitment space

@dstadulis dstadulis requested a review from Roasbeef May 22, 2023 15:50
Copy link
Contributor

@jharveyb jharveyb left a comment

Choose a reason for hiding this comment

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

LGTM, was originally thinking that we would want to encode the type as well but I now think that's not needed. 🚀

Second commitment message needs to use a different acronym though,

@ffranr ffranr force-pushed the assetcommitment-type branch from 1cfb3ae to 2060e2d Compare May 23, 2023 14:47
@ffranr ffranr enabled auto-merge May 23, 2023 14:49
@ffranr ffranr added this pull request to the merge queue May 23, 2023
Merged via the queue into lightninglabs:main with commit b9564ff May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

4 participants