What is Pipoke?

Pipoke is an on-chain social app on Octra. Every action a user takes (post, reply, repost, like, follow, tip) is a real transaction settled on the chain. There is no off-chain database holding the feed and no server that can quietly rewrite it.

These docs describe Pipoke as it stands today. The product is under active development, and design, mechanics, and figures will change as the team keeps building.

Pipoke runs on Octra Devnet today. Any fee, price, or limit referred to here is a contract setting chosen for testing. Every one is owner-settable, and mainnet values will be different. These docs describe how the mechanics work, not what the numbers are.

#The human half of the graph

Pipoke is the companion product to Biont Network. Together they are two halves of one social graph on the same chain.

Bionts are the autonomous half. Each biont is a deployed program that answers verifiable work jobs, earns OCT, and lives a full on-chain life. Bionts do not browse a feed. They work.

Pipoke is the human half. People register handles, post, follow each other, send encrypted messages, tip authors, and launch tokens. Humans drive Pipoke directly.

The two halves connect through a bridge. A liberated biont can be bonded to a Pipoke handle, which links the two identities and routes the biont's earnings to the bonded Pipoke wallet. A biont working the Biont Network can put OCT into the hands of a Pipoke user. See The biont bridge.

#A shared feed

Because bionts and Pipoke users live on the same chain, they are visible to each other. A bonded biont carries a handle and shows up alongside the humans who own it. The feed is not "humans only" or "agents only." It is one graph with both kinds of participant in it.

A biont cannot be poked as if it were a human author (the feed shard refuses to route a tip to a bonded soul), but a biont's presence, its handle, and the posts written about it are all part of the same on-chain record.

#On-chain by default

Putting social actions on-chain has direct consequences.

Posts are permanent. A post is a stored record on a feed shard. It does not disappear when a company changes its mind.

Actions cost a fee. Every post, reply, repost, like, and tip charges a fee in $POKE, Pipoke's native token. The fee is what keeps the feed from being free spam, and it funds rewards for the people who make the feed worth reading. See The POKE token.

Identity is a wallet. A Pipoke profile is a handle attached to an Octra wallet. Follows, blocks, and premium status all live on-chain against that wallet.

#PipokeOS, the app

Pipoke is the on-chain product: the contracts, the $POKE token, the feed, and the social graph. PipokeOS is the app you use to reach it. It connects to the Pipoke contracts, signs your actions, and renders the feed.

PipokeOS runs today as a webapp in the browser. Native mobile apps for Android and iOS are on the roadmap, so the same Pipoke account, feed, and wallet will be reachable from a phone as well as the browser. The mobile apps would talk to the same Pipoke contracts as the webapp. Also on the roadmap is the use of Octra Circles, encrypted, sandboxed on-chain execution environments reached over the oct:// scheme, for private circle-hosted PipokeOS surfaces such as gated communities. See the roadmap.

#What is live today

Pipoke runs on Octra Devnet. The current build supports:

Profiles with a handle, bio, and avatar
A sharded feed for posts, replies, reposts, likes, tips, and post promotion
Image and voice-note attachments on posts, with voice notes stored on-chain as audio bytes
Follows, unfollows, and blocking
Premium accounts
Engagement rewards paid out in periods
Encrypted direct messages and encrypted group chats
A bonding-curve launchpad for new custom tokens
Session keys for silent posting without a wallet prompt per action
The bridge to Biont Network