Ledger Wasm Too Big

Maxfinity · March 3, 2022, 1:22pm

The current Dfinity Ledger wasm is too large, even after minimisation, to be deployed to the IC for testing purposes. Does anyone have a version of the ledger wasm that is under the 2mb limit? After optimising, I am seeing a file-size of roughly 2.5 mb.

Cheers

roman-kashitsyn · March 4, 2022, 5:40pm

Hi @Maxfinity !

We optimized the size of the Ledger canister in scope of the “Ledger canister fit for dapps” feature (The Internet Computer’s Post-Genesis R&D Roadmap | by DFINITY | The Internet Computer Review | Feb, 2022 | Medium). The Wasm module should now be below 2MiB (this commit did the trick if you’re curious).

Could you please try following the local setup instructions but use a fresh commit from the IC repo in the first step (e.g., export IC_VERSION=c7ec4881cf8db619aab86a148010b74f58e3ef37)?

dpdp · March 4, 2022, 5:53pm

Hello Max,

For canister wasm larger than 2mb (egress message size limit) and smaller than 5mb (intra canister message limit tbc) –
You might be able to deploy the canister via a canister;

Here is an example (not really well documented) about how to achieve this: GitHub - ORIGYN-SA/large_canister_deployer_internal: Install wasm code to a canister larger than 2 mb by chunking it and deploying it via a canister in the same subnet
large_canister_deployer_internal/index.js at master · ORIGYN-SA/large_canister_deployer_internal · GitHub

Make sure that the “larger canister deployer” canister and the target canister are in the same subnet;

Maxfinity · March 6, 2022, 3:14pm

Hi Roman, none of these commits work unfortunately - the first is unfortunately slightly too large and the second has an invalid gz format.

flyq · March 7, 2022, 8:16am

github.com

dfinity/ic/blob/0bf9cb79c3/rs/types/types/src/messages.rs#L39

      
        
            pub use message_id::{MessageId, MessageIdError, EXPECTED_MESSAGE_ID_LENGTH};
            pub use query::UserQuery;
            pub use read_state::ReadState;
            use serde::{Deserialize, Serialize};
            use std::convert::TryFrom;
            use std::mem::size_of;
            pub use webauthn::{WebAuthnEnvelope, WebAuthnSignature};
            
            
/// Same as [MAX_INTER_CANISTER_PAYLOAD_IN_BYTES], but of a primitive type
            /// that can be used for computation in const context.
            pub const MAX_INTER_CANISTER_PAYLOAD_IN_BYTES_U64: u64 = 2 * 1024 * 1024; // 2 MiB
            
            
/// This sets the upper bound on how big a single inter-canister request or
            /// response can be.  We know that allowing messages larger than around 2MB has
            /// various security and performance impacts on the network.  More specifically,
            /// large messages can allow dishonest block makers to always manage to get
            /// their blocks notarized; and when the consensus protocol is configured for
            /// smaller messages, a large message in the network can cause the finalization
            /// rate to drop.
            pub const MAX_INTER_CANISTER_PAYLOAD_IN_BYTES: NumBytes =
                NumBytes::new(MAX_INTER_CANISTER_PAYLOAD_IN_BYTES_U64); // 2 MiB

The data I see is a bit different, did i miss something?

roman-kashitsyn · March 9, 2022, 8:35am

Hi @Maxfinity!

none of these commits work unfortunately - the first is unfortunately slightly too large and the second has an invalid gz format.

I looked into that issue, it turns out that there was recently a refactoring in the CI pipeline that introduced a glitch making the canister larger again.

You can use this commit hash to get a reasonably small ledger canister: 77cecc596216a584174106733b40513645641fef

Thanks for reporting the issue and sorry for the inconvenience.