AmuletBackend feasibility on Splice LockedAmulet

[gabitoesmiapodo]

Research question

Can Splice's LockedAmulet back a vesting escrow, and what would an AmuletBackend implementation have to look like? The source repo carries only a stub, so both the semantic fit and the effort are unknown.

Time-box

1 day

Background / What we already know

dapp/frontend has MockBackend and the inert LiteBackend behind a createBackend seam, both satisfying src/backend/VestingBackend.ts. Canton Coin (Amulet) is Splice's native token; LockedAmulet is its time-lock primitive. The source repo's AmuletBackend never got past a stub.

Investigation approach

• Read Splice's LockedAmulet templates and their lock/unlock choices
• Map the VestingBackend interface onto them: createVesting, accept, withdraw, cancel, claimResidual
• Check both curve kinds in src/lib/schedule.ts: linear maps plausibly onto a time-lock, milestone is a step function and may not
• Establish whether cancel to residual-claim semantics survive a lock primitive that knows only one expiry
• Rough-estimate the build effort

Expected output

Decision (go / no-go); Technical recommendation with trade-offs

Next steps

• File an implementation issue if the answer is go