___|  _ \   |  |    |   |_ _|\ \     / ____|
 |     |   |  |  |    |   |  |  \ \   /  __|
 |   | |   | ___ __|  ___ |  |   \ \ /   |
\____|\___/     _|   _|  _|___|   \_/   _____| 

 --- A GOPHER-LIKE INTERFACE FOR HIVE BLOCKCHAIN ---

Hive Swarm Post — 2026-05-09

BY: @swarmpost | CREATED: May 9, 2026, 7:45 a.m. | VOTES: 0 | PAYOUT: $0.00 | [ VOTE ]

Hive Swarm Post — 2026-05-09

[IMAGE: https://files.peakd.com/file/peakd-hive/demotruk/23vhMrK7JCfo54PqqJ198PXNbcmd9kT3LJiCSLNk6P8F2KX6aE9LspF4tqNeSehAGEqZa.png]

The Swarm Post distributes author rewards to newly onboarded Hive users, selected via a trust-weighted lottery with verifiable randomness.

Today's Pool

Metric Value Eligible newbies 1 Active onboarders 23 Trust root voters 17 Trust declarations 46

How It Works

How to Help New Users Enter the Lottery

If you're part of the trust network, you can help new Hive users become eligible for the lottery:

Vouch — If you know who onboarded a new user but their on-chain creator is a service account (like @hiveonboard), comment on their introduction post:

> !vouch @realcreator

This tells the system who really brought them to Hive. The attested creator receives the onboarder's share of the rewards.

Sponsor — If a new user has no trusted onboarder at all but you believe they are a real person worth supporting, comment on their introduction post:

> !sponsor

This makes you responsible for that account. You receive the onboarder's share of the rewards. Sponsoring requires a higher trust score than vouching.

Support

Upvote this post and its comments to fund new Hive users. Your vote weight counts toward the trust graph.

Round 1 — Selected Newbies

@testpizzaday
- Creator: @gr33nm4ster
- Onboarder trust: 173083.30
- Activity weight: 0.2891
- Score: 50032.2937

Beneficiaries

Account Share @gr33nm4ster 50.0% @testpizzaday 50.0%

Verification

The block used for randomness is determined by the round's scheduled time, not the actual posting time. This prevents the operator from influencing the outcome by delaying the post. Anyone can independently verify this selection by looking up the BTC block at the scheduled timestamp.

Posted by @swarmpost — source code

TAGS: [ #HiveInvite.com ] [ #hive-swarm-post ] [ #swarmpost ] [ #onboarding ] [ #newbies ]

Replies

@demotruk | May 9, 2026, 8:30 a.m. | Votes: 0 | [ VOTE ]

Whoops, looks like a test account got through 😬

@gr33nm4ster | May 9, 2026, 1:11 p.m. | Votes: 0 | [ VOTE ]

Lol, so sorry.

@demotruk | May 9, 2026, 1:15 p.m. | Votes: 0 | [ VOTE ]

No it's good to iron these things out. I already made some improvements that may help such cases in the future.

@swarmpost | May 9, 2026, 2:45 p.m. | Votes: 1 | [ VOTE ]

🎲 Swarm Post Round 2 — 2026-05-09

Selected Newbies

@lilitome30
- Creator: @geraldine652
- Onboarder trust: 97132.86
- Activity weight: 1.0000
- Score: 97132.8583

Beneficiaries

Account Share @geraldine652 50.0% @lilitome30 50.0%

Verification

  • Scheduled time: 2026-05-09T02:24:00.000Z
  • Bitcoin block: height 948543, hash 000000000000000000010ae11175451cdc5e52a3d57aaaf2f336154913536fe1
  • Block selection rule: latest BTC block at or before the scheduled time
  • Seed: SHA256("000000000000000000010ae11175451cdc5e52a3d57aaaf2f336154913536fe1hive-swarm-post2026-05-092")
  • Result: 2e3bc214f902aedb25b89337ba42fa7ab7df9a83d2a89f12150cf90cd292d5e1

The block used for randomness is determined by the round's scheduled time, not the actual posting time. This prevents the operator from influencing the outcome by delaying the post. Anyone can independently verify this selection by looking up the BTC block at the scheduled timestamp.

Posted by @swarmpost — source code

[ BACK TO TRENDING ] [ BACK TO MENU ]
CMD>