chore: staging ledger and minter init args

[maciejdfinity]

Accounts

• minting_account: Principal ljyxk-riaaa-aaaar-qb5mq-cai (the minter) with no subaccount. Transfers to this account burn tokens; transfers from it mint them.
• fee_collector_account: Same minter principal but with subaccount 0x…0fee. Collected transfer_fee amounts accumulate here instead of being destroyed.

Supply & token metadata

• initial_balances = vec {}: no pre-minted balances at genesis.
• transfer_fee = 50: fee in smallest units (lamports) charged per ICRC-1 transfer.
• decimals = opt 9: 9 decimals, matching SOL (1 SOL = 1e9 lamports).
• token_name / token_symbol = "ckDevnetSOL": display name and ticker.
• metadata: a single icrc1:logo entry with the ckDevnetSOL SVG embedded as a base64 data URI.

Archive

• trigger_threshold = u64::MAX: effectively disables automatic archive spawning for staging.
• num_blocks_to_archive = 10_000: if triggered, move 10k blocks per archive op.
• node_max_memory_size_bytes = 3 GiB: per-archive-node memory cap.
• controller_id = r7inp-6aaaa-aaaaa-aaabq-cai (NNS root): controller set on archive canisters.
• cycles_for_archive_creation = 100 T: cycles attached when spawning a new archive.
• max_message_size_bytes, more_controller_ids, max_transactions_per_response: left defaulted.

Feature flags

• max_memo_length = opt 80: allow ICRC-1 memos up to 80 bytes.
• feature_flags = { icrc2 = true }: enables ICRC-2 (approve/transfer_from).
• index_principal = null: no paired index canister configured yet.

Net effect: a 9-decimal ICRC-1/2 ledger named ckDevnetSOL, minted/burned by the staging minter, fees collected into a dedicated subaccount, archiving effectively disabled by a max-u64
threshold.

[Copilot]

Pull request overview

Adds explicit initialization arguments for the staging deployment of the ckSOL minter and ICRC-1 ledger canisters.

Changes:

• Define init_args for cksol_minter in staging (RPC/ledger principals, key name, Solana network, and fee/threshold parameters).
• Define init_args for cksol_ledger in staging (minting/fee-collector accounts, token metadata/logo, and archive options).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

archive_options.controller_id is set to principal "r7inp-6aaaa-aaaaa-aaabq-cai" (a well-known system/NNS canister principal). This would make newly created archive canisters controlled by that principal rather than by your staging deployment controllers, which typically prevents you from upgrading/managing archives. Set controller_id (and/or more_controller_ids) to principals that should actually control the archive canisters in staging.

Suggested change

	controller_id = principal "r7inp-6aaaa-aaaaa-aaabq-cai";
	controller_id = principal "ljyxk-riaaa-aaaar-qb5mq-cai";

[Copilot]

archive_options.trigger_threshold is set to the maximum nat64 value, which effectively disables archiving. That can lead to unbounded ledger growth and eventual memory/performance issues if staging sees sustained traffic. Consider setting a realistic threshold (and optionally tune num_blocks_to_archive) or document explicitly that archiving is intentionally disabled for staging.

Suggested change

	trigger_threshold = 18_446_744_073_709_551_615 : nat64;
	trigger_threshold = 20_000 : nat64;