Archive the repository and decommission the droplet #15

User story / Problem statement

Once carpincho talks to Canton directly and canton-dappbooster stops running this service, nothing consumes it. It still costs a DigitalOcean droplet, a deployment to keep alive, and a published npm package.

Expected outcome

The droplet is gone, the repository is archived, and the npm package says plainly that it is no longer maintained.

Acceptance criteria

• No live consumer remains
• The DigitalOcean droplet is destroyed, with its DNS record and certificate
• The npm package is deprecated, or a decision to leave it is written down here
• The repository is archived

Technical notes

• The package is on npm as @bootnodedev/canton-wallet-service, latest 0.3.0 published 2026-09-09, so archiving the repository breaks no install. Retiring it needs npm deprecate as its own step
• canton-dappbooster depends on ^0.3.0 and resolves it from npm; Remove wallet-service from the dev stack and docs canton-dappbooster#223 removes that
• cn-darkpools keeps its own copy of the source under canton-barebones/wallet-service, which does not depend on this repository
• BootNodeDev/carpincho is a separate, older wallet that also uses this service; confirm it is dead before archiving
• The deployed instance answers over https, so there is a certificate and a DNS record to clean up as well

Additional context

• Blocked by Talk to Canton directly and drop wallet-service carpincho-wallet#36
• Blocked by Remove wallet-service from the dev stack and docs canton-dappbooster#223
• dappbooster-canton-landing still advertises this service; a separate issue covers that