Skip to content

Safe to Send 1.0.3

Latest

Choose a tag to compare

@Anirudh-712 Anirudh-712 released this 15 Nov 07:34
· 3 commits to main since this release

Safe to Send 1.0.3: warns before you send crypto to an address that can't be reached on the destination chain. Keyless, read-only, MIT.

What's in Milestone 1

  • Library: npm install @cryppit/safe-to-send (zero dependencies), plus the npx @cryppit/safe-to-send command.
  • Security reports: use GitHub private vulnerability reporting on this repository (see SECURITY.md).
  • Hosted API: https://safe-to-send-api.station-wheres-my-swap.workers.dev/v1/check?address=0x…&chain=56. Keyless, CORS open, no storage or logs, 60 checks a minute per IP.
  • Conformance board: 21/21 real-address vectors pass, at https://cryppit.github.io/safe-to-send/conformance/
  • Frozen Abstract archive: every Abstract Global Wallet, frozen 25 Oct 2026, attached here. Verify it with node scripts/verify-archive.mjs <dir>.

Since 1.0.0

  • 1.0.1: one retry when the RPCs rate-limit a request, and Tenderly fallbacks for Base, Arbitrum, OP and Ink.
  • 1.0.2: Blast, Lisk and Polygon zkEVM have shut down. They are no longer read, and choosing one as the destination is a stop. If the destination chain doesn't answer, it is read once more.
  • 1.0.3: the API serves /.well-known/security.txt, the command's help names npx @cryppit/safe-to-send, and the page's card for a shut-down chain no longer claims anything was read.

Archive asset SHA-256: bda09229c9cb72b9469294ed43f9a86d74f4a13fd891aabe9d5462a7cc4f14d7