[imikushin]

Summary

Adds the scrolls_litecoin canister source and the deploy runbook at scrolls/LITECOIN.md. This pull request does not deploy a canister and does not merge.

The canister follows the Bitcoin scrolls shape with its own constants:

• vetKD domain scrolls_litecoin/derivation_prefix[/v1]
• network labels main (ltc) and test (tltc)
• broadcast URLs on litecoinspace
• empty init (service : () ->), no create-time cycles argument, no fee-address setter
• deposit_cycles minimum 1000000000000

The Litecoin fee addresses are their own values in scrolls/src/scrolls_litecoin/config.yaml. The initial keys are the Bitcoin fee keys in ltc1 and tltc1 encoding. That reuse is intended. A later change edits only that yaml, then rebuilds and upgrades this canister. It does not require editing the Bitcoin fee config.

Every dfx build and every dfx deploy in the runbook unsets NEXT_SCROLLS_LITECOIN_CANISTER_ID. Deploy compiles again, so a shell-exported value is not compiled into the wasm that gets installed, including the fee-address upgrade.

addresses rejects an empty out_is before any signing call. Before sign_with_schnorr, it accepts the caller cycles that cost_sign_with_schnorr quotes for key key_1 and that request. The IC cycle-cost reference lists 26153846153 cycles for the production key. A surplus is not kept as a fee. No cycles attached does not reach the signer.

The runbook wasm check fails when the file is missing. It looks for a canister principal, not the forwarding variable's name.

There is no host caller. Filling scroll outputs needs a canister id, and checking the threshold signature needs a public key. Neither exists until this canister is deployed, so Litecoin scroll outputs stay rejected.

scrolls/Cargo.toml and scrolls/Cargo.lock gain the new package so cargo test --package scrolls_litecoin and --locked CI can see it. The lock diff is only the new scrolls_litecoin package entry.

Pull request 269 stays open and is not merged. This branch does not edit charms-client, guest bytes, scrolls_bitcoin, or the version-16 key.

Test plan

• cargo test --manifest-path scrolls/Cargo.toml --package scrolls_litecoin (15 passed on the parent commit; the runbook check passed again after this edit)
• cargo test --profile=test litecoin_spell_is_one_op_return on the earlier parent commit
• No attached cycles does not call the signer (no_attached_cycles_never_reaches_the_signer)
• Runbook forwarding check fails for a missing wasm and for an embedded principal
• dfx build is intentionally not run in this pull request

  

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.

[greptile-apps]

Confidence Score: 5/5

[High impact] The PR appears safe to merge; the latest runbook change fixes the outstanding forwarding concern.

Summary

Adds the scrolls_litecoin canister source, build registration, and deployment runbook. This PR does not deploy it.

• The Litecoin canister signs selected transaction inputs and broadcasts the transaction.
• Callers can get Litecoin output scripts with a Schnorr signature.
• The Litecoin canister checks spells in Litecoin transactions.
• Operators can build and deploy Litecoin Scrolls as a separate canister.

No new issues were found in the changes since the previous review.

_{Reviews (4) · Last reviewed commit: "docs(scrolls): unset the Litecoin forwar..." · Reviewed by Greptile}