Invalid deploy - The deploy had an excessive size error

[devendran-m]

Condor Release Feedback / Issue

1. Category (Required)

Select the category that best describes your feedback or issue:

• Feedback
• Bug/Issue

---

2. Reported by (Required)

Muhammet Kara - MAKE Services

---

3. Casper Network (Required)

Select the network or environment related to your feedback, bug, or issue:

• Devnet
• Integration-Test
• Testnet
• Mainnet

---

4. Description (Required)

Provide a detailed description of your feedback, bug, or issue.

The reporter is facing an issue with CEP-78 deployment. The reporter mentioned that;

• dev and feat-2.0 branches error out during build
• It builds when he applied the PR Update Feat 2.0 branch #291 on top of feat-2.0
• After building the contracts, when he tried to install the contract by using this command;

casper-client put-deploy --node-address http://52.90.123.125:7777/ --chain-name "dev-net" --payment-amount 500000000000 --secret-key /home/kara/scripts/keys/ACCOUNT_1/secret_key.pem --session-path cep78.wasm \
--session-arg "collection_name:string='enhanced-nft-1'" \
--session-arg "collection_symbol:string='ENFT-1'" \
--session-arg "total_token_supply:u64='10'" \
--session-arg "ownership_mode:u8='0'" \
--session-arg "nft_kind:u8='1'" \
--session-arg "json_schema:string='nft-schema'" \
--session-arg "allow_minting:bool='true'" \
--session-arg "owner_reverse_lookup_mode:u8='0'" \
--session-arg "nft_metadata_kind:u8='2'" \
--session-arg "identifier_mode:u8='0'" \
--session-arg "metadata_mutability:u8='1'"

• He faces the below error;

response for rpc-id -1238620798644402004 account_put_deploy is json-rpc error: {"code":-32008,"message":"Invalid Deploy","data":"the deploy was invalid: The deploy had an excessive size"}

---

5. Date Issue Began (Optional)

When did you first notice this issue? (Format: dd/mm/yyyy)

02/02/2025

---

5. Attachments (Optional)

Include any logs, screenshots, or links that may help with the analysis.

---

[gRoussac]

@devendran-m I had the same issue on NCTL. Ask reporter to increase his chainspec settings for first lane (#3) from 262_144 to like 450_000

install_upgrade_lane = [2, 750_000, 2048, 1_000_000_000_000, 1]
wasm_lanes = [
    [3, 450_000, 1024, 1_000_000_000_000, 1],
    [4, 131_072, 1024, 100_000_000_000, 2],
    [5, 65_536, 512, 5_000_000_000, 80]
]

@mpapierski FYI It seems legacy deploys do take wasm_lane 3 and not install_upgrade_lane as per get_max_serialized_length() for transaction v1

This issue is not related to the CEP it self but casper node. Please close it or move it.

[devendran-m]

The issue reporter has confirmed that the issue is resolved after using the correct parameters.

casper-client put-transaction session --node-address http://18.208.195.207:7777/ --chain-name "integration-test" --secret-key /home/kara/scripts/keys/ACCOUNT_1/secret_key.pem --gas-price-tolerance 10 --pricing-mode classic --transaction-path cep78.wasm --session-entry-point call --install-upgrade --payment-amount 800000000000 --standard-payment true --session-arg "collection_name:string='CEP78-Enhanced-NFT-006 NoReverseLookup'" --session-arg "collection_symbol:string='ENFT-006'" --session-arg "total_token_supply:u64='1000000'" --session-arg "ownership_mode:u8='2'" --session-arg "nft_kind:u8='1'" --session-arg "allow_minting:bool='true'" --session-arg "owner_reverse_lookup_mode:u8='0'" --session-arg "nft_metadata_kind:u8='0'" --session-arg "identifier_mode:u8='0'" --session-arg "metadata_mutability:u8='1'" --session-arg "events_mode:u8='2'"

As a follow-up action, the docs should be updated to list the correct parameters so that the users don't face such issues.

A separate ticket will be created in the Docs repo to address the documentation gap.