Test Mint and Burn - #1010
Conversation
|
We all try to stick to this commit message standard (roughly) |
There was a problem hiding this comment.
When I run
RUST_LOG=info CELESTIA_LOG_LEVEL=FATAL CARGO_PROFILE=release CARGO_PROFILE_FLAGS=--release nix develop --extra-experimental-features nix-command --extra-experimental-features flakes --command bash -c "just movement-full-node native build.setup.eth-local.celestia-local.test-lock-mint --keep-tui"
I get
Error: Failed to create dead account
caused by
API error Error(VmError): Invalid transaction: Type: Validation Code: SEQUENCE_NUMBER_TOO_OLD
|
As far I can see there is no |
There was a problem hiding this comment.
Thanks for this. Remove all println!s for tracing::info. Cleanup imports, use tree style imports. The comments you've written right at the bottom are correct but lets remove the comment from the SC. Rename the test to mint_burn.rs and any associated process_compose naming and cmd / pkgs.
Thanks!
|
Merge conflicts will auto-resolve after:
|
ganymedio
left a comment
There was a problem hiding this comment.
Added one change suggestion, to assert dead address balance is 0 at the end.
|
Even when I remove Wrong increment? |
|
Is there a new dependent PR in aptos-core that contains the mint_to function? O |
Same branch and PR add_burn_from |
|
PR number or link? |
|
Ok this is ready to go in can you fix the merge conflicts and add this test to the |
|
Will pull again. |

Summary
protocol-units,networks,scripts,util,cicd, ormisc.#1009
Burn elsa's supply.
Changelog
moved away from native_bridge integration to e2e testing
added burn_from and mint_to methods gated to framework signer
Testing
networks/movement/movement-client/src/bin/e2e/lock_mint.rs
rm -rf .movement/ && RUST_LOG=info CELESTIA_LOG_LEVEL=FATAL CARGO_PROFILE=release CARGO_PROFILE_FLAGS=--release nix develop --extra-experimental-features nix-command --extra-experimental-features flakes --command bash -c "just movement-full-node native build.setup.eth-local.celestia-local.test-mint-burn --keep-tui"Outstanding issues
We might need to add a burn_from entry function on the core_resources_account.