Argyle, in public.

Argyle mirrors recent incoming Bitcoin outputs for lightweight checkouts, access passes, tips, and other low-stakes integrations.

There is no address-query endpoint and no server-side watch list. A client derives one coarse bucket locally, verifies its content hashes, and exact-matches its address inside the downloaded rows.

No account. No callback. No address query.

The feed

Base

/v1/btc/mainnet/

Shape

One signed manifest and immutable content-addressed JSON

Coverage

Standard mainnet receive scripts: 1…, 3…, and bc1…

Window

Declared by the manifest; production target 48 hours

Cadence

Best effort every 20 seconds

The current 20-minute slice receives a new hash only when its observations change. Finished slices become hourly objects. New objects and indexes arrive first; one atomic manifest replacement makes the complete snapshot visible.

Use it

The tiny Argyle v1 module handles address decoding, signature and hash verification, bounded fetching, caching, and deduplication. Vendor it with your application and pin the Yacht Club authority key in the application build.

Read the short guide or the exact plain-text contract. The live snapshot begins at /v1/btc/mainnet/manifest.json.

The wire format is public and deliberately product-neutral, so small applications can reuse the mirror without inheriting a payment backend.

YCR