-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat!: prevent implicit asset burn #3540
Open
petertonysmith94
wants to merge
33
commits into
master
Choose a base branch
from
ps/feat/prevent-illicit-burn
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
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
petertonysmith94
changed the title
feat: prevent illicit burn
feat: prevent illicit asset burn
Jan 3, 2025
petertonysmith94
changed the title
feat: prevent illicit asset burn
feat: prevent implicit asset burn
Jan 3, 2025
arboleya
previously requested changes
Jan 3, 2025
petertonysmith94
requested review from
digorithm,
Torres-ssf,
Dhaiwat10,
danielbate,
nedsalk and
maschad
as code owners
January 6, 2025 10:35
danielbate
previously approved these changes
Jan 9, 2025
arboleya
previously approved these changes
Jan 9, 2025
arboleya
reviewed
Jan 9, 2025
…els-ts into ps/feat/prevent-illicit-burn
petertonysmith94
dismissed stale reviews from danielbate and nedsalk
via
January 9, 2025 15:31
0179db4
Torres-ssf
requested changes
Jan 9, 2025
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.
Nice job @petertonysmith94 👍
Co-authored-by: Sérgio Torres <[email protected]>
Coverage Report:
Changed Files:
|
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.
Release notes
In this release, we:
sendTransaction
to ensure that we prevent implicit asset burnsSummary
Users can add inputs to a transaction in two ways:
transactionRequest.addCoinInput()
ortransactionRequest.addMessageInput()
transactionRequest.inputs.push({ ... })
transactionRequest.outputs.push({ ... })
.This PR focuses on the second, less safe method and adds a new check to prevent implicit asset burn unless the
enableAssetBurn
flag is set totrue
in the<wallet|provider>.sendTransaction()
method.Breaking Changes
Checklist