Speak freely.
Own everything.
A social app is usually a feed over a database, with a moderator on top. Pipoke is a feed over a chain, with you on top. The difference shows up in every interaction.
Speak freely.
Anonymous posting is a primitive, not a feature flag. Groth16 zero-knowledge proofs let you prove membership without revealing identity. Nullifiers stop replay attacks. The Merkle root republishes on a short cadence. The social app sits on top of anonymity, the other way around from how most apps treat it.
Own everything.
Your posts, your handle, your followers, your coins, your votes, every social signal is an on-chain artifact under your wallet. We cannot delete you. We cannot deplatform you. We cannot censor you. The contracts are the rules; the rules are formally verified.
The wallet is the app.
You should never have to leave Pipoke to swap, send, trade, claim, or stake. POKE balances, launched-coin positions, P&L cost-basis, creator allocations, and gasless session keys are all native. Octra session keys mean you sign once and the app handles everything else for ninety days.
Built for real-time.
Octra Network finalizes blocks in about half a second. The indexer streams eighty-plus event types over Server-Sent Events. The keepers tick every thirty seconds and react to new commits in under five. Pipoke feels live because the chain underneath is.
Formal verification.
Every Pipoke contract carries an FV badge issued by the Octra verifier. We use AML (AppliedML) for invariants like supply conservation, monotonic counters, no-reentrancy. When the contracts pass FV, the social rules pass too.
Censorship-resistant today.
Censorship-free at v1.
Most decentralized social projects host their canonical client on the same centralized infrastructure as Twitter or Reddit. The protocol is open, the website is not. Pipoke's posture is different.
No admin delete method exists on any Pipoke contract. Posts, pokes, follows, rooms, auctions and trades are signed by your wallet, written to Octra, and permanent. The team cannot remove them. DMs and groups are end-to-end encrypted with keys we do not hold. Anonymous posts go through zero-knowledge proofs, so the team does not learn who made them.
This is the only soft surface. Today pipoke.chat is served like a normal web app, and like every social platform, we maintain a default-feed flag list for things like CSAM, doxxing and incitement. A flagged post is still on chain. Anyone can fetch it via RPC. Anyone can run their own client. Censorship on Pipoke is provable; the original is always one block-explorer link away.
The client moves into an Octra Circle. Circles are tor-like: encrypted, decentralized, anonymously addressable, no central hosting to refuse to serve. When the Pipoke client itself lives in a circle, there is no DNS to seize, no canonical server to take down, no gateway to refuse traffic. Anyone with the URI fetches the same client. We could not censor if we wanted to. That is the goal. It is also the only credible end state for a social app that promises censorship resistance.
We are building Pipoke because we want a social app we trust. If the network does its job, we should be a thin layer of taste over an open protocol. That is the goal.