1 · Producer round (pre-show funding for an upcoming episode)
⚠ custom Hive-Engine tokens ride in
custom_json ops — Hive allows 5 per account per block, so tipshare payouts to your producers later go out in batches of ≤5, ~3s apart (handled automatically by the drop engine). Native HBD/HIVE have no such limit.
Support the tools (optional)
When you distribute this round to your producers via tipshares, consider adding
@completenoobs at ~5% to fund ongoing free-software development. Optional, comes out of your raise —
nothing is added on-chain here, this is just a reminder.
1b · Pitch preview (optional — show funders what they're funding: cover art + teaser media)
Preview (as a funder would see it)
add a title / cover / media to preview the pitch…
2 · Scan donations
Reads public history (Hive-Engine history API for tokens, Hive RPC for HBD/HIVE) for transfers TO the collecting account whose memo contains the round guid. Re-scan any time; results are provisional until cutoff passes.
Producers
| # | account | donations | total | weight % | tier | shoutout(s) |
|---|
Excluded (matched the guid but don't count)
| account | amount | when (UTC) | reason | memo |
|---|
3 · Export
format
v4call-producers v1 — weights are relative (donation totals), importable into pod-announce's producer section (next build step)
preview
4 · Announce round on Hive (publish the funding call on-chain)
Posts this round as @account using your posting authority, so producers can find it and fund it. The post body is the pitch above (title, details, cover, teasers, tiers); funders send the token to your account with the memo pod-producer:…. Re-posting the same round edits the post. This is a real, public, permanent Hive post — the round itself takes no beneficiary.
no key touches this page — Keychain signs & broadcasts
The posting-key path first checks your key against the account's on-chain posting authority — an active/owner key or a typo stops here before anything is broadcast.