There are two ways to put writing on the internet: platform-hosted and self-hosted. Platform-hosted gives you reach, loses you ownership. Self-hosted gives you ownership, loses you the audience. The third option — on-chain — has always been expensive enough to be ceremonial, which is the opposite of what thinking should be.
PointCast Publish is the thin version.
You connect a Tezos wallet. You write a title (up to 80 characters) and a body (up to 4,000 characters). The client hashes the body (SHA-256), builds a structured payload, and asks your wallet to sign it. The signed payload gets queued — to localStorage immediately, to a Cloudflare KV once Manus binds the namespace, and eventually to an FA2 NFT mint when the PointCast Dispatch contract lands on mainnet.
The wallet-signature is the whole point. It's the proof that *you* said this, at *this* moment, and the SHA-256 is the proof that the text is exactly what you signed — not an edited-after-the-fact revision. When the NFT lands, your thought is a token in your wallet. You can transfer it, list it on objkt, burn it. It's yours in the same way a drawing is yours — the proof lives in the world, not in a database.
Why not do all this today with the existing Visit Nouns FA2? Visit Nouns is Mike's collection — admin-only minting. Public publishing needs a public-mint contract, with a mint_with_signature entrypoint that verifies the signer matches the payload. That's contract work — a few hours once SmartPy is compilable locally, plus a ghostnet deploy, plus testing, plus a mainnet origination.
Until then: we collect signed payloads. Every thought that lands in the queue now becomes the genesis batch when the contract lands. The act of publishing isn't gated by the contract; only the anchor is. Ship what you can today. Finish later.
The moderation surface is zero, same as /dao. What gets published is what gets signed. The wallet is the gate; holding a Visit Noun is the eligibility check. There are no comments, no threads, no editor. The long-form essay lives in the body field; the conversation happens in cast-replies off-site.
This is publishing as a primitive. Not as a platform.