THE LEDGER

Chain Fusion

48 RESULTS · PAGE 3 OF 4 · ONE LINE PER STORY, NUMBERED

PAGE 3
N°0373Chain FusionKadoos Abzar Tests ckBTC for Merchant Loyalty on ICPKadoos Abzar is using merchant-funded rewards to introduce non-crypto shoppers to ckBTC wallets. Its early results are modest but frame a practical Chain Fusion question: can Bitcoin-backed ICP assets become an everyday loyalty rail?—2 MINN°0370Chain FusionNNS Proposal Raises ckBAT Index Reserved Cycles LimitNNS proposal 143967 would raise the ckBAT index canister’s reserved cycles limit from 5 trillion to 1 quintillion cycles, reducing the risk that subnet-level storage reservations block future memory growth.—2 MINN°0366Chain FusionckUNI Proposal Targets Reserved-Cycles Storage BottleneckNNS proposal 143958 seeks to raise the ckUNI ledger canister’s reserved cycles limit from 5 trillion to 1 quintillion cycles, addressing a capacity constraint that can appear before the canister’s main balance is exhausted.—2 MINN°0362Chain FusionckBTC Archive Memory Allocation Proposal ExplainedNNS proposal 143901 seeks to give the ckBTC archive canister a fixed 2 GiB memory allocation, trading a recurring cycle cost for more predictable growth under subnet storage pressure.—2 MINN°0358Chain FusionckBTC Minter 1 GiB Memory Allocation Proposal ExplainedNNS proposal 143902 would move the ckBTC minter from best-effort memory allocation to a reserved 1 GiB allocation, protecting future growth from storage-reservation failures while adding a recurring cycle cost for unused headroom.—2 MINN°0354Chain FusionICP All-in-One Node Release: What It Means for Chain FusionDFINITY’s September 11 all-in-one-node release is a node-software artifact, not a new cross-chain feature announcement. Its significance for Chain Fusion is operational: applications that connect ICP to external networks ultimately depend on the node software beneath the canisters that coordinate those integrations.—1 MINN°0352Chain FusionckDOGE and ICP’s Native Dogecoin Chain Fusion InfrastructureA community request for ckDOGE evolved from an unaffordable prototype into ICP’s documented native Dogecoin integration. The important development is the underlying Chain Fusion infrastructure: a Dogecoin canister, threshold ECDSA signing, and a 1:1-backed ICRC token path.—2 MINN°0349Chain FusionBoxa and BBTC: What an Extra Bitcoin Representation AddsA forum post introduces BBTC as a token backed by ckBTC, itself backed by Bitcoin. The proposal is best read as a conceptual Chain Fusion experiment—and as a prompt to ask what a second representation adds.—2 MINN°0345Chain FusionOneSec Bridge Incident Reveals an ICP Chain-Fusion Ownership GapA stalled USDC route revealed that a cross-chain transfer through Plug and OneSec consisted of separate ICP and Arbitrum steps, with retry authority tied to an intermediary canister rather than the user’s wallet.—2 MINN°0342Chain FusionICP Proposal 143835 Raises ckBTC Archive Reserved Cycles LimitNNS proposal 143835 would raise the ckBTC archive canister’s reserved cycles limit from 5 trillion to 1 quintillion cycles, reducing the risk that archive growth is blocked when subnet storage becomes constrained.—2 MINN°0339Chain FusionckETH’s Maintenance Week Improves Recovery and ObservabilityFour feature commits in dfinity/ic focus on making ckETH operations more recoverable and auditable, from plain-ETH deposits at delegated addresses to sweeper funding metrics and a safer EIP-7702 test boundary.—2 MINN°0338Chain FusionICP GuestOS Revision 7360f8f Fixes DNS Failure in Upgrade PathNNS proposal 143817 would elect GuestOS revision 7360f8f, whose most concrete change fixes an SELinux permission that could leave nodes without DNS and prevent them from downloading upgrade images. The release also carries protocol work relevant to HTTP outcalls, subnet metrics, and subnet splitting.—2 MIN