Stories

A story is a post that expires. You publish it, it stays visible for a few days, and it disappears from the app on its own. The bytes are not deleted from the chain (nothing on Octra deletes), but the indexer and the app stop surfacing the story after its TTL.

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.

#What a story can carry

Media	How
Video	Chunked + encrypted, manifest in your Circle.
Image	Single encrypted blob in your Circle.
Voice note	Encrypted audio in your Circle.
Text-only	Just the `text` field on the story tx.

A story attachment uses the same oct:// URI pattern as a regular post. Same 4 MB cap. Same encryption.

#TTL

A story has a fixed time-to-live in epochs. The app sets the default at 3 days. The indexer enforces the TTL: after expiry, the story stops appearing in story trays. The on-chain record stays where it is.

#Privacy

A story can be published with the same four privacy tiers as a regular post: public, followers, mutuals, close friends. The sealing model is identical: a follower-only story ships a sealed wrap of the symmetric key per follower.

#Action fee

A story charges the same kind of POKE action fee as a post. Same 50/40/10 split.

#Why have stories if everything is permanent

A short-form intent. A story signals "this is for now, not forever." The expiry is what makes that signal credible.