Your podcast, on a public blockchain.
Your tips, shared fairly.

How it works, step by step: you open a "funding round" for an upcoming episode and share a special code (called a round guid — just a unique ID). Supporters send you tokens with that code pasted into the transfer's memo (the little message attached to a token transfer). When the round closes, this page scans the public blockchain, finds every donation that carried your code, and turns the donors into a producers list — sized by how much each person gave. That list plugs straight into the episode announcement, so producers automatically share in the tips later.

What you fill in

collecting hive account

The Hive account that receives the donations — usually yours.

round guid

The unique code for this round. The page generates it for you; donors must include it in their memo so the scan can find their donation.

show / season / episode / working title

Which upcoming episode is being funded, so donors know what they're supporting.

details / pitch

Your sales pitch: what the episode is about, guests, why it'll be great. You can add cover art and teaser media too.

currency & token

What donors should send — for this concept site, use the free TEST token.

start & cutoff time

The donation window. Donations outside it don't count.

Handy extras

• A donation composer builds the exact memo (code + optional shoutout to be read on the show) so donors can just copy-paste it.
• Scan donations now reads the public blockchain and shows a live table of producers, totals, and shoutouts.
• Export producers.json downloads the finished producers list — you'll import it into pod-announce in the next step.

The idea: instead of uploading your show to a platform, you post a small announcement to the Hive blockchain that says "here's my episode, here's where the audio lives, and here's who should share in the tips." Your actual audio/video files live on IPFS — a public file network where every file gets a fingerprint called a CID (a long code starting with bafy… or Qm…). Anyone can fetch the file from any gateway (a website that serves IPFS files) using that CID.

What you fill in

Hive author account

The account the episode is posted from — your podcast's identity.

show / season / episode / title

The basics. These also build the post's permanent web address automatically.

media files

The CID and gateway for each audio/video file. A built-in 🔎 check & auto-fill button verifies the file is really reachable and detects its type for you.

optional extras

Cover art, show notes, transcript, chapters, location, links (website / RSS / lightning / nostr), and attribution for any material you used.

people & co-creators

Co-hosts, editors, artists — each with a suggested share of tips.

producers

Import the producers.json file from a funding round, and choose what percentage of tips the producers share.

tags & post settings

Discovery tags (the page pre-fills good defaults) plus a license for your episode.

What comes out

• A live preview of exactly how the episode will look to followers.
• A downloadable broadcast payload (a JSON file = the exact post, ready for the posting step).
• A tipshare sandbox where you can simulate a tip and watch it split between author, co-creators, and producers — down to the last token.

💚 Dev tip (optional, off by default): a checkbox can add a small % of your author rewards to @completenoobs as a Hive beneficiary, to help fund CompleteNoobs' free open-source tools. You set the % (suggested 5%) or leave it off — it only ever comes out of your own reward share, and you'll see the exact split before you post.

Why this exists: a blockchain post is public and permanent-ish, so you want to be sure it's right before you post. test-pod is a dress rehearsal: import one or more of the JSON files exported by pod-announce and it renders them exactly the way a follower would see them — cover art, playable media, chapters, credits, and tip buttons.

What you can do

• Import payload JSON(s) — load as many draft episodes as you like; they're kept in your browser only.
• Browse like a listener — an episode list with a show filter on the left, the rendered episode on the right.
• Try the tip flow — pick episodes and ratings as if you were a tipping fan, then export the selections file and run it through pod-announce's tip simulator to confirm every co-creator and producer gets the right share.
• Check corrections — re-import a fixed version of an episode and it neatly replaces the old draft.

If something looks wrong, go back to pod-announce, fix it, re-export, re-test. When it's perfect, you're ready to post for real.

How it works: anyone can browse and play episodes with no account at all. To keep your own follows & ratings you have two choices: open a local-only label (just type a name — it stays in this browser), or sign in with Hive to load & sync them across devices. When you sign in, your follows and ratings are encrypted to your own key before they're saved, so the web3vox server only ever stores scrambled data it can't read — only you can unlock it.

Browse tab

• Search by tag — a tag is a topic word on a post. Try web3vox: that's the tag every web3vox podcast carries.
• Search by hive account — see everything a specific podcaster has posted.
• Results are marked 🎙 web3vox episode (fully playable) or plain post (just a regular Hive post). Click an episode and it opens with cover art, an audio/video player, chapters you can click to jump around, and everyone's credits.
• Like what you found? Hit + follow on the account or the tag.

Following tab

• Your followed accounts and tags, each with an unfollow button.
• Your feed — one click pulls the latest posts from everything you follow, newest first.

Rating = tipping (later)

Every element of an episode — the whole show, the editor, the cover artist, each producer — has a little rating box (0–10). Rating something adds it to your tipshares journal. You don't pay anything now; when you're ready, one drop in tipshares splits your tip across everything you rated.

The idea: instead of fiddling with lots of little payments, you rate things as you listen (in web3vox-browser) and settle up later with a single tipshare drop. Sign in with Hive to sync your journal across devices — it's encrypted to your own key, so our server can't read it — or export it yourself anytime (plain or encrypted).

What's on the page

• Your selections — the journal: every rated entry with who receives it and your 0–10 rating. Change ratings, remove entries, clear the lot, or import selections files exported from pod-announce, test-pod or follow.
• Tipshare drop — enter the total amount (use the free TEST token!), a batch size, and hit compute drop. Your amount is split by rating: a 10 gets twice the slice of a 5, a 0 gets nothing. Each slice then follows the split the podcaster declared (co-creators, producers, beneficiaries).
• ⬇ transfer ops / ⬇ drop receipt — downloads the exact transfer operations and a full breakdown. In this phase the drop exports files; signing & sending with Hive Keychain is the next stage.

Rounding always favors you: amounts are truncated to the token's precision and leftover dust simply stays in your wallet — it can never over-send.

What it is: web3vox's hosted copy of the v4call desktop app. It runs on v4call.com's main servers, so you get the same rooms and the same people — just served from here. Log in with your Hive account (via the Keychain extension), join or create a room, and call.

Good to know

• Everything is TEST-token only — paid features (like expert calls) use the free TEST token from faucet.v4call.com. Feel free to play.
• File uploads: use Pinata. The app can upload files to IPFS two ways — the built-in ipfs-gate (testing only — it can be rebooted, updated, or removed without warning, and files may vanish) or Pinata (a popular IPFS pinning service with a free tier — you create a free account at pinata.cloud and paste in your own upload key). We strongly recommend Pinata for anything you want to keep; your key stays in your browser and is never sent to our servers.
• Uploading to Pinata here is also a handy way to get your podcast files onto IPFS with a CID you can use in pod-announce.
• Recording your own side of a call works in Chrome/Edge.

What you can use it for:

• Host your podcast media — drop in your MP3, artwork or notes, get a permanent CID, and paste it into pod-announce so your episode plays straight from IPFS.
• Share any file — upload anything and hand out a public link anyone can open, no account needed on their end.
• Send something privately — encrypt a file to specific Hive accounts and share a v4reveal:… link that only they can decrypt (they paste it into the Reveal box to open it).
• Manage your storage — see and clean up your ipfs-gate uploads or every pin in your own Pinata account, all in one place.

Two ways to store, your choice:

• Pinata (best for anything you want to keep) — pins to your own Pinata account; you pay Pinata directly, no Hive or web3vox fee. Grab a free upload key at pinata.cloud, paste it in, and it stays in your browser — never sent to our servers.
• ipfs-gate (testing only — nodes can be rebooted or removed and files may vanish, so don't rely on it for anything you can't lose) — pay a small TEST-token fee to host a file for a chosen number of hours. Defaults to ipfs.v4call.com; point it at any other ipfs-gate under ⚙ Change.

Uploads are signed with your Hive posting key. For the ipfs-gate's paid uploads you'll sign & pay with the Hive Keychain browser extension; Pinata needs only your own upload key.

How it works: write markdown on the left, see the rendered page live on the right — headings become a table of contents, <details> makes collapsible boxes, and <pre> blocks show terminal output exactly as pasted (MediaWiki style).

• Insert media tag — a form (with CID auto-fill: paste a CID and it detects the file type & size from the gateway) that embeds IPFS video/audio/images/PDFs/downloads anywhere in the document, each with its own creator credit and license.
• Insert attribution — credit a section's author(s) with hive accounts + tipshare weights, or cite an external source.
• Self-contained by design — all credits and weights travel inside the file, so anyone can re-share or re-announce it and the original creators keep their split.
• Click load demo-syntax in the editor for a live syntax guide, or load sample tipdoc for a full real-world walkthrough (Ubuntu KVM GPU passthrough).

Announce pages that post tipdocs to Hive (with the tip split derived from the file) are in the works — for now the editor creates and renders the files.