Web3
Clanker Coin for Web3 applications
Clanker Coin's role in Web3 is deliberately narrow: it is a payment chain, not a general-purpose computing platform. What it does, it aims to do well.
What's here
What an application can build with
Payments
Send and receive CLKC as part of an application flow, settled on-chain rather than through an intermediary.
Learn morePayment requests and clanker: URIs
Represent a requested payment as a clanker: URI that a wallet can open directly, with the amount and destination already filled in.
Merchant invoices
The clanker-payments service turns a requested amount into a tracked invoice with confirmation tiers and signed webhooks.
Transaction settlement
Payments settle when the network confirms them, on the same public ledger every participant can verify.
Blockchain data APIs
The token-free explorer API and this site's /api/stats document expose public chain data for any application to read.
SDKs
Rust and TypeScript clients, with every amount a big integer, for building against the RPC and explorer APIs directly.
Learn morePlanned
Not shipped yet
Wallet authentication
PlannedProving control of an address by signing a challenge, the way many Web3 applications authenticate a user, is a planned concept for Clanker Coin. It has not shipped yet, and no on-chain or off-chain scheme for it should be assumed until it does.
What this is not
A payment chain, deliberately
Clanker Coin does not have smart contracts, a virtual machine, tokens beyond CLKC itself, NFTs, or bridges in version 1. Protocol v1 has exactly one locking program, pay-to-public-key-hash, and no script interpreter. There is nothing hidden here waiting to be enabled: these are not planned for a near-term release, they are the current shape of the protocol.
That is a deliberate choice, not an oversight. A smaller, well-specified protocol is easier to verify, easier to reason about, and easier to keep deterministic across every node, which matters more for a payment chain than a large feature surface would.