End-to-end tests for multitoken transfers between different types of accounts #578
Assignees
Comments
james-chf
changed the title
vp_user should support multitoken transfersvp_user should support authorizing multitoken transfers
|
|
4 tasks
james-chf
changed the title
vp_user should support authorizing multitoken transfers
james-chf
changed the title
vp_user-like VPs should support authorizing multitoken transfers
This was referenced Dec 12, 2022
james-chf
changed the title
vp_user-like VPs should support authorizing multitoken transfers
|
Rescoped this ticket as the transfer functionality was already implemented |
4 tasks
github-project-automation
bot
moved this from Done (testnet)
to Tested in Devnet
in Namada-Old
phy-chain
pushed a commit
to phy-chain/namada
that referenced
this issue
Mar 1, 2024
* feat: release changelog * feat: add newline * feat: changelog for types * feat: release-it for root * fix: bump dependencies versions correctly with jq * feat: always bump packages * fix: readVecU8Pointer import * feat: package bumper in node * feat: release it configs cjs * docs: publish info * feat: release scripts for all packages * feat: release script for namada interface * docs: more accurate tag info * fix: missing comma in json after rebase * fix: yarn.lock after rebase
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
VPs which implement the multitoken interface (#482) must ensure they call the both the sender's and receiver's VPs when a transfer is made (e.g. #114). If the sender's VP is a "user VP" (i.e.
vp_user-like), then the transfer should only be allowed if the sender has signed the transfer - this is how regular token transfers are authorized.vp-user-like VPs are:We should have tests against an example multitoken VP (e.g. the one from https://github.com/anoma/anoma-wasm-multitoken)
The text was updated successfully, but these errors were encountered: