THE LEDGER

Chain Fusion

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

PAGE 2
N°0419Chain FusionICP’s Proposed ckDOGE Wind-Down Tests Chain Fusion GovernanceA proposal would retire ICP’s Dogecoin integration and ckDOGE through a staged redemption, custody, and canister-shutdown process. The important engineering lesson is that cross-chain systems need an explicit end-of-life path.—2 MINN°0415Chain FusionGifty Uses ICP Chain Fusion to Rethink Bitcoin GiftingGifty wants to make Bitcoin gifting approachable for people without wallets, using ckBTC, Internet Identity and an education-gated escrow. The proposal’s real challenge is not moving Bitcoin—it is making an unfamiliar claim flow trustworthy enough for first-time users.—2 MINN°0411Chain FusionChain Fusion Signer v0.5.2 Adds Input-Boundary HardeningThe latest Chain Fusion Signer release rejects oversized public-key requests and bounds derivation inputs, turning two seemingly ordinary API parameters into explicit security controls for ICP developers.—2 MINN°0404Chain FusionICP’s All-in-One Release Makes Provenance the Chain Fusion CheckpointThe September 25 IC release is notable less for a feature headline than for the deployment artifact it names: a specific repository tag, commit, and asset set that operators can verify before upgrades affecting Chain Fusion infrastructure.—1 MINN°0400Chain FusionICP GuestOS d26cd03: Why the NNS Election Matters for Chain FusionNNS proposal 144117 would elect IC/GuestOS revision d26cd03, a release whose value lies as much in verifiable build provenance as in its protocol changes.—2 MINN°0396Chain FusionICP September 2026 Base Release: Why Version Provenance Matters for Chain FusionThe dfinity/ic release-2026-09-10_03-28-base is best read as an infrastructure anchor for Chain Fusion builders: a signed, identifiable IC code revision that can be pinned and independently verified.—1 MINN°0392Chain FusionckUSDT Index Proposal Adds 4 GiB Memory AllocationProposal 144039 would move the ckUSDT index canister from best-effort memory allocation to a reserved 4 GiB allocation, reducing the risk that future ledger growth is blocked by reservation limits.—2 MINN°0390Chain FusionDoxa Proposes a Chain Fusion USDY Reserve for DoxaUSDDoxa proposes replacing ckUSDC as DoxaUSD’s ultimate collateral with native USDY held on an EVM network, while retaining ckUSDC as an ICP-side settlement step. The design makes collateral verification—not deposit receipt—the gate for minting.—2 MINN°0386Chain FusionckUSDT Archive Proposal Adds 2 GiB of HeadroomNNS proposal 144040 would reserve 2 GiB for the ckUSDT archive canister, creating headroom ahead of a possible return to block archiving while shifting the canister from best-effort growth to predictable capacity.—2 MINN°0383Chain FusionX-39 Notaría’s Split Trust Model for Bitcoin-Anchored EvidenceX-39 Notaría combines ICP-hosted verification, Bitcoin timestamps, and ML-DSA-87 signatures—but its most interesting design choice is separating online timestamp verification from offline signing authority.—3 MINN°0379Chain FusionICP All-in-One-Node Release: What Chain-Fusion Operators Should VerifyThe September 19 dfinity/ic release is operationally significant but deliberately narrow in what it publicly explains: a tagged all-in-one-node build, 13 assets, and a six-commit distance from master. For chain-fusion teams, the useful story is the verification workflow—not an unsubstantiated feature announcement.—2 MINN°0377Chain FusionICP Base Release 2026-09-18: A Chain Fusion Version AnchorThe dfinity/ic release-2026-09-18_03-28-base provides a signed, reproducible version anchor for infrastructure that Chain Fusion applications depend on. Its public release page does not describe a new cross-chain API, so builders should treat it as a version-control and verification event rather than infer new capabilities.—1 MIN