___  ___    _ _    _  _ _____   _____
 / __|/ _ \  | | |  | || |_ _\ \ / / __|
| (_ | (_) | |_  _| | __ || | \ V /| _|
 \___|\___/    |_|  |_||_|___| \_/ |___|

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

Hive Swarm Post — 2026-05-23

BY: @swarmpost | CREATED: May 23, 2026, 5:08 p.m. | VOTES: 20 | PAYOUT: $0.65 | [ VOTE ]

Hive Swarm Post — 2026-05-23

[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 3 Active onboarders 48 Trust root voters 5 Trust declarations 54

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

@helenxxo
- Creator: @samostically
- Onboarder trust: 184841.71
- Activity weight: 1.0000
- Score: 184841.7087

Beneficiaries

Account Share @helenxxo 50.0% @samostically 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

@swarmpost | May 23, 2026, 5:08 p.m. | Votes: 1 | [ VOTE ]

🎲 Swarm Post Round 2 — 2026-05-23

Selected Newbies

@sattu6342
- Creator: @sagarkothari88
- Onboarder trust: 170582.80
- Activity weight: 0.8672
- Score: 147928.4646

Beneficiaries

Account Share @sagarkothari88 50.0% @sattu6342 50.0%

Verification

  • Scheduled time: 2026-05-23T02:24:00.000Z
  • Bitcoin block: height 950606, hash 0000000000000000000001f2fd015cfec5a8afd4168ee398cfb42e1c2094540b
  • Block selection rule: latest BTC block at or before the scheduled time
  • Seed: SHA256("0000000000000000000001f2fd015cfec5a8afd4168ee398cfb42e1c2094540bhive-swarm-post2026-05-232")
  • Result: dcc46b247c25474872fecf927efd4683761b07c8804c51a4771e840dda783ddd

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

@swarmpost | May 23, 2026, 5:08 p.m. | Votes: 1 | [ VOTE ]

🎲 Swarm Post Round 3 — 2026-05-23

Selected Newbies

@otomepaixao
- Creator: @blessskateshop
- Onboarder trust: 184841.71
- Activity weight: 0.6712
- Score: 124063.4890

Beneficiaries

Account Share @blessskateshop 50.0% @otomepaixao 50.0%

Verification

  • Scheduled time: 2026-05-23T04:48:00.000Z
  • Bitcoin block: height 950619, hash 00000000000000000000037c23f7b9d83fcd7c1a31864af239e4389af6dde9b0
  • Block selection rule: latest BTC block at or before the scheduled time
  • Seed: SHA256("00000000000000000000037c23f7b9d83fcd7c1a31864af239e4389af6dde9b0hive-swarm-post2026-05-233")
  • Result: 57c1dfab0c7b536bce6aaedc088e7b3b6be46fa3fcd0f72a02fc27218ec12f82

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

@hivebuzz | May 23, 2026, 7:06 p.m. | Votes: 0 | [ VOTE ]

Congratulations @swarmpost! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)

You received more than 100 upvotes.Your next target is to reach 200 upvotes.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

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