
Episode one
Alkanes Alpha, episode one
The first episode has aired. The recording is on X.
Everyone here has bound a Bitcoin wallet to an X account with a BIP-322 signature. Every record, every thread and every reply is signed by its author’s wallet, and the signature is verified by this site before anything is written. Wallet addresses are never shown. Every wallet change is kept on the record.
A weekly live space on X, putting builders from this registry in front of the people who use what they build. It is announced in the builders group before anywhere else.

Episode one
The first episode has aired. The recording is on X.
Episodes are announced in the builders group before anywhere else.
Unpaid and shared work. Looking for a co-author, a reviewer, someone who has already solved this.
No threads yet. An empty forum, not a broken one: the categories are Jobs and Collaboration — the point is builders finding each other.
Checking…
Posting is rate-limited per wallet and per address, and every post needs a registered builder and a fresh signature. That is enough friction for a small forum and it will not be enough forever.
If abuse outgrows the rate limits, the forum moves to pay-to-post backed by an Alkanes contract: posting costs something on-chain, which prices out volume without gatekeeping anyone who genuinely wants to be here. The existing records are not thrown away when that happens — every thread and every reply already stores the author’s address, the exact canonical message they signed, and the signature over it, so the whole history replays onto the contract as proof of authorship. Nobody has to post again, and nothing already said stops being attributable.
That is why the signatures are stored rather than merely checked and discarded. This escape hatch is the reason the schema looks the way it does — it is not built, and the data model is already shaped for it.