#Failed to upload wasm using soroban-cli on futurenet.

1 messages · Page 1 of 1 (latest)

steel briar
#

How to reproduce:

cargo install --locked --version 0.9.1 soroban-cli
git clone https://github.com/stellar/soroban-examples
cd soroban-examples
git checkout v0.9.2
make
soroban contract install \
    --wasm hello_world/target/wasm32-unknown-unknown/release/soroban_hello_world_contract.wasm \
    --source SAACPZRWQNLRZ6AVCN56KV6ZDRIKKQ6X4HXDDMLNYAHUWYCCCEKJH22B \
    --rpc-url https://rpc-futurenet.stellar.org:443 \
    --network-passphrase 'Test SDF Future Network ; October 2022'

What did I get?

error: transaction submission failed: GetTransactionResponse {
    status: "FAILED",
    envelope_xdr: ...,
    ),
    result_xdr: Some(
        "AAAAAAAAikP////1AAAAAA==",
    ),
    result_meta_xdr: Some(
        "AAAAAwAAAAAAAAACAAAAAwAAmj8AAAAAAAAAAJrqwJCPZUfSJwWbyaKVSu08Or36GbMl4/XIkDcPUpATAAAAF0hvgakAAJhIAAAADQAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAAACaPQAAAABktLtQAAAAAAAAAAEAAJo/AAAAAAAAAACa6sCQj2VH0icFm8milUrtPDq9+hmzJeP1yJA3D1KQEwAAABdIb4GpAACYSAAAAA4AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAAmj8AAAAAZLS7XAAAAAAAAAAAAAAAAgAAAAMAAJo/AAAAAAAAAACa6sCQj2VH0icFm8milUrtPDq9+hmzJeP1yJA3D1KQEwAAABdIb4GpAACYSAAAAA4AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAAmj8AAAAAZLS7XAAAAAAAAAABAACaPwAAAAAAAAAAmurAkI9lR9InBZvJopVK7Tw6vfoZsyXj9ciQNw9SkBMAAAAXSG+CLgAAmEgAAAAOAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAwAAAAAAAJo/AAAAAGS0u1wAAAAAAAAAAA==",
    ),
}
#

envelope_xdr:```
AAAAAgAAAACa6sCQj2VH0icFm8milUrtPDq9+hmzJeP1yJA3D1KQEwAAjHUAAJhIAAAADgAAAAAAAAAAAAAAAQAAAAEAAAAAmurAkI9lR9InBZvJopVK7Tw6vfoZsyXj9ciQNw9SkBMAAAAYAAAAAgAAAhsAYXNtAQAAAAEPA2ACfn4BfmABfgF+YAAAAgcBAXYBRwAAAwMCAQIFAwEAEAYZA38BQYCAwAALfwBBgIDAAAt/AEGAgMAACwcxBQZtZW1vcnkCAAVoZWxsbwABAV8AAgpfX2RhdGFfZW5kAwELX19oZWFwX2Jhc2UDAgrIAQLCAQECfyOAgICAAEEgayIBJICAgIAAAkACQCAAp0H/AXEiAkEORg0AIAJBygBHDQELIAEgADcDCCABQo7o8di6AjcDAEEAIQIDQAJAIAJBEEcNAEEAIQICQANAIAJBEEYNASABQRBqIAJqIAEgAmopAwA3AwAgAkEIaiECDAALCyABQRBqrUIghkIEhEKEgICAIBCAgICAACEAIAFBIGokgICAgAAgAA8LIAFBEGogAmpCAjcDACACQQhqIQIMAAsLAAALAgALAB4RY29udHJhY3RlbnZtZXRhdjAAAAAAAAAAFAAAADMAbw5jb250cmFjdG1ldGF2MAAAAAAAAAAFcnN2ZXIAAAAAAAAGMS43MS4wAAAAAAAAAAAACHJzc2RrdmVyAAAALjAuOS4yI2JmZGRiYzM4MGUyYjIzYzcxMDY5YmQ2MTJiODkxNzc0MDA0MzdhODAAAABDDmNvbnRyYWN0c3BlY3YwAAAAAAAAAAAAAAAFaGVsbG8AAAAAAAABAAAAAAAAAAJ0bwAAAAAAEQAAAAEAAAPqAAAAEQAAAAAAAAAAAQAAAAAAAAAAAAAAAQAAAAd8h5wHnoyd3mug/5MLyMkMiZH0XiFebmBvzGPLm4HVggAAAAAAAWafAAAAKAAAAoAAAAKoAAAAAAAAAIUAAAABD1KQEwAAAEDdrLa2Ss9cV0RtXpxMCtuuF+wrugVlFW9fdQTHV/9qGvvBTHGA8caj3lnE+Xi2hHXQtxXvTju/I4pE8oInyasG

#

It's strange that when I upload soroban_timelock_contract.wasm, I can get the wasm id.

soroban contract install \
    --wasm timelock/target/wasm32-unknown-unknown/release/soroban_timelock_contract.wasm \
    --source SAACPZRWQNLRZ6AVCN56KV6ZDRIKKQ6X4HXDDMLNYAHUWYCCCEKJH22B \
    --rpc-url https://rpc-futurenet.stellar.org:443 \
    --network-passphrase 'Test SDF Future Network ; October 2022'
70579ee1a70fc72b649930194b12b2faefe63a3e1bcdb9fe9db7289ee771984e
proper folio
#

it does not seem related but @hardy dock talked about "internal error" in this other topic: #1129538311929733131 message

Due to a bug in the core version used in preview 10, trying to overwrite an entry that has expired, will result in txINTERNAL_ERROR, not a soroban-specific error. So if you encounter an 'internal error', it most likely means that some ledger entry used in transaction has expired.

mortal saddle
#

Did some digging. I edditted the hello world contract and then it could be installed. So the most likely guess is that the bytes are the same (good news for contract compilation reproducibility), the contract was install previously and is now expired.