stacks-network / stacks-network/stacks-core
Do not permit `*-transfer?` and `*-mint?` methods to send to non-standard principals
Open
Nobody has claimed this yet.
clarity-behavior-change
clarity-next-candidate
- Dominant language
- Rust
- Stars
- 3.1k
- Forks
- 762
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 76
Description
Duplicate of https://github.com/stacks-network/stacks-blockchain/issues/3118:
Do not permit the functions stx-transfer? ft-transfer?, nft-transfer? ft-mint? and nft-mint? to transfer tokens to a principal with a non-standard version byte. Make this a runtime error.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the duplicate issue #3118 and trace the implementations of stx-transfer?, ft-transfer?, nft-transfer?, ft-mint?, and nft-mint?. Confirm how principal version bytes are validated and identify the runtime-error path; done means all listed functions reject non-standard principals consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100