-
Notifications
You must be signed in to change notification settings - Fork 80
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
Test Lock/Mint #1009
Comments
I feel like this is because you are using the wrong private key. It is not always |
Can you provide the full error message with a stack trace? |
|
0x1 priv key public key is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Attempting to test if current Elsa Mainnet is able to programmatically have the defined funds on the L1 Bridge for supply parity.
Describe the solution you'd like
Using the the movement-client e2e test framework:
Describe alternatives you've considered
Using the CLI instead of the framework which utilized the native bridge tests, but that solution was slow and found a lot of issues.
Additional context
Issues encountered
test-lock-mint-client
.Error: Unknown error Transaction committed on chain, but failed execution: Move abort in 0x1::system_addresses: ENOT_CORE_RESOURCE_ADDRESS(0x50001): The address/account did not correspond to the core resource address
Core Resources Account address: 0xf90391c81027f03cdea491ed8b36ffaced26b6df208a9b569e5baf2590eb9b16
and 0xA550c18 private key:Core Resources Account address: 0x33da451a2e5250c1fbd680a0f49ae7b5bc96fade129781fa3497e4974779bddf
.The text was updated successfully, but these errors were encountered: