Proof of Engagement
Other chains keep constant time. Buzzchain lets it move. In Proof of Work, a block appears when enough computation has been spent. Here, a block appears when enough attention has accumulated, so block time is a live measurement of mindshare.
01 · Weight
Bigger voices count more. They cannot drown out everyone else.
A post’s weight is its author’s reach times the engagement it earned, both on log scales, with a floor so that a post with no engagement still counts.
weight = log₂(followers + 2) × (1 + ln(1 + engagement))
- 50 followers, no engagement5.7
- 1,000 followers, 20 engagements40.3
- 100,000 followers, 500 engagements119.9
- 10 million followers, 60,000 engagements279.1
The last account has 200,000 times the audience of the first, and counts about 49 times as much.
02 · Breadth decides when
Each post adds its weight to a running accumulator. When it reaches the threshold K, a block closes and the excess carries over. Because weights are log-scaled and each author counts once per block, every block holds a comparable number of voices. That is what makes block time a clean signal.
03 · Loudness decides how much
Those voices are not equally loud. A block’s reward follows the raw engagement of its posts, with diminishing returns and a cap per post, so loudness has to come from many posts by many accounts. There is no fixed block reward: it cannot be predicted before the block closes, and anyone can verify it afterwards.
04 · Silence still keeps time
If the threshold is not reached within the heartbeat interval, an empty heartbeat block keeps the chain alive. It carries no reward.
Rules of the stream
01
Original posts only
Replies and reposts never enter the stream.
02
One author per block
Only the first post of each account in a block counts.
03
Frozen engagement
Engagement is read once, when the post is 15 minutes old, and then frozen.
04
Ordered by post id
X post ids encode creation time to the millisecond. That is the ordering.
Measured, not bought
No post earns a payment, and there is no leaderboard. Each block seals its posts into a Merkle root: ids, hashes and two numbers per post, never post text. Block construction is a pure function of those records, so anyone can replay it and compare hashes.
Validators hold a fixed set of seats. They re-run the block construction, archive the per-post records so blocks stay verifiable even if posts are deleted, and sign the history. A checkpoint is accepted on Ethereum only once a quorum has signed, so no single server can publish a block history on its own.
Block rewards go to the validators that attest. A seat that does not attest earns nothing.