Welcome to Skrybit

Skrybit puts your brand on Bitcoin. You pick an audience of Bitcoin wallets, attach your media, and Skrybit inscribes it directly on-chain and delivers it to every wallet in the audience — a real Bitcoin inscription, owned by the recipient, forever.

These docs cover the whole journey:

• For marketers — the full campaign lifecycle in the Skrybit Console: build a collection, choose an audience, estimate the cost, launch, fund the batch from your own wallet, and watch delivery happen on-chain. Start with Running an Airdrop Campaign.
• For recipients — someone airdropped you an inscription and sent you a claim link? Here is what that means and what to do. (Short version: it is already yours; claiming just proves it.)
• Wallets & accounts — how Skrybit thinks about your wallets, and what “verified” vs “watch-only” means. See Wallets & Accounts.
• API — the platform is API-first; everything the console does is available programmatically. See the API Reference.

Networks

Skrybit runs on Bitcoin mainnet and on testnet4. The two are fully separate: separate campaigns, separate wallets, separate funding. Every network-scoped action in the console and the API is explicit about which network it targets — nothing silently crosses over. Use testnet4 to rehearse a campaign end-to-end before spending real sats.

How delivery actually works

Skrybit inscriptions are standard ordinals inscriptions, created with a commit/reveal transaction pair and delivered straight to the recipient’s address. There is no escrow, no wrapped token, no bridge: once the reveal transaction confirms, the recipient’s wallet holds the inscription like any other sat they own. You (the marketer) fund the batch; Skrybit’s engine signs and broadcasts the inscription transactions.