-
Notifications
You must be signed in to change notification settings - Fork 316
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
SEP-41: add mint and clawback event #1588
Open
chowbao
wants to merge
6
commits into
stellar:master
Choose a base branch
from
chowbao:sep-41-add-mint-event
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
05cc3b5
add mint event to sep-41
chowbao 095dc41
Update sep-0041.md
chowbao 6b1057f
Update sep-0041.md
chowbao a14bae4
Merge branch 'master' into sep-41-add-mint-event
chowbao 5f29fdf
Update sep-0041.md
chowbao b8aa496
Update sep-0041.md
chowbao File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,13 +3,13 @@ | |
``` | ||
SEP: 0041 | ||
Title: Soroban Token Interface | ||
Authors: Jonathan Jove <@jonjove>, Siddharth Suresh <@sisuresh> | ||
Authors: Jonathan Jove <@jonjove>, Siddharth Suresh <@sisuresh>, Simon Chow <@chowbao> | ||
Track: Standard | ||
Status: Draft | ||
Status: Final | ||
Created: 2023-09-22 | ||
Updated: 2023-10-18 | ||
Updated: 2025-01-08 | ||
Version 0.2.0 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This version should be bumped There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch. Updated in 5f29fdf |
||
Discussion: https://discord.com/channels/897514728459468821/1159937045322547250 | ||
Discussion: https://discord.com/channels/897514728459468821/1159937045322547250, https://github.com/stellar/stellar-protocol/discussions/1584 | ||
``` | ||
|
||
## Simple Summary | ||
|
@@ -208,10 +208,37 @@ The event has data: | |
|
||
- `i128` the amount burned. | ||
|
||
#### Mint Event | ||
|
||
The `mint` event is emitted when an amount of the token is minted. | ||
|
||
The event has topics: | ||
|
||
- `Symbol` with value `"mint"` | ||
- `Address` the address to hold the newly minted tokens. | ||
|
||
The event has data: | ||
|
||
- `i128` the amount minted. | ||
|
||
#### Clawback Event | ||
|
||
The `clawback` event is emitted when an amount of the token is clawed back. | ||
|
||
The event has topics: | ||
|
||
- `Symbol` with value `"clawback"` | ||
- `Address` The address holding the balance from which the clawback will take tokens. | ||
|
||
The event has data: | ||
|
||
- `i128` the amount clawed back. | ||
|
||
## Changelog | ||
|
||
- `v0.1.0` - Initial draft based on [CAP-46-6]. | ||
- `v0.2.0` - Remove `spendable_balance`. | ||
- `v0.3.0` - Add `mint` and `clawback` event | ||
leighmcculloch marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
## Implementations | ||
|
||
|
Oops, something went wrong.
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.
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.
I don't think this update should change the status. Changing the status is unnecessary and hasn't been discussed.
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.
Do we want to leave it in
Draft
still? That seems weird if custom tokens are actively using the SEP (and will use the updated SEP with mint/clawback)How do we decide if a SEP should be
active
/final
?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.
Lets have that discussion, but not bundle a status change with a functional change. The fact we're making a functional change is an indicator it still belongs in Draft, because Draft is the state that functional changes occur in.
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.
There's some discussion about SEP statuses in https://github.com/stellar/stellar-protocol/blob/master/ecosystem/README.md#draft-merging--further-iteration
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.
Hmm that's fair it should have already been updated from
Draft
toActive
/Final
before these functional changes. But it's just lucky happenstance that it is still inDraft
and we can keep it in draft for these changesUpdated in b8aa496
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.
I think it's debatable. While the SAC implements SEP-41 there are not a significant number of custom tokens, and given the ecosystem around events is still developing (unified events work as evidence) SEP-41 still has some room to prove itself before we flag it as Final.