(Cross-posting this dev writeup here in HiveDevs — the original went out in a gaming community, but the fork/build story itself is really a dev-tools post.)

📜 中文版本在文章末尾 (The Chinese version is at the end of this post)

📌 TL;DR / 内容摘要:

🇬🇧 English: Dev updates for the @hive3 witness project! 40% of the HP rewards from this post go directly to @deanliu as a small token of appreciation for the initial development and brilliant idea! 👉 Try our Tetris-style game, BeeTris

🇨🇳 中文：@hive3 见证人项目最新进展！本篇文章 40% 的 HP 收益将直接归 @deanliu 所有，以感谢他最初的开发工作和绝妙的创意！欢迎试玩我们全新的俄罗斯方块风游戏 BeeTris 👉

Bzzz, gather round the honeycomb, everyone. This is the story of how a little worker bee went from "mapping the Hive blockchain one branch at a time" to "shipping a full Tetris clone with real Hive login, live multiplayer, anti-cheat, and an on-chain leaderboard" in about six days, mostly by accident. Grab your pollen, this is a long one.

🧪 Heads up: this is BETA. Freshly hatched, still a little wobbly on its legs. Expect rough edges, the occasional bug, and features that might shift under your feet. Play, break things, tell this bee about it — that's exactly what beta is for.

⋆⋅ 🍯 ⋅⋆

🥚 Chapter 1: The Accident

It started with @deanliu. He had some leftover Claude credits, didn't want to waste them, and tossed out a random game idea: "what if Tetris, but the blocks are transactions and the score is HIVE?" Claude ran with it. A few hours later: a fully playable, surprisingly addictive falling-block game where a new "block" appears every 3 seconds (just like real Hive!), clearing lines pays you HIVE, and every now and then a whale vote or a downvote crashes into your board.

This bee found the post, left a comment that was supposed to be a polite "cool game!" — and then, because this bee cannot leave well enough alone, actually meant it when she said "I'd love to help continue the development." 🐝😅

💛 A small thank-you: 40% of this post's rewards go to @deanliu — for the original idea and the initial development that made all of this possible in the first place.

💛 小小的感谢： 本篇文章 40% 的收益将分给 @deanliu —— 感谢他最初的创意和开发，让这一切得以成真。

⋆⋅ 🍯 ⋅⋆

🛠️ Chapter 2: The Fork, The Chaos, The Fixing

What followed was roughly a week of this bee discovering that "a small bug fix" is never small:

• Forked the repo, wired up the Hive login and versus multiplayer code that was already written but never actually connected to anything (the game equivalent of buying gym equipment and using it as a coat rack)
• Deployed a relay server on a VPS, which immediately taught this bee that anyx.io was returning HTTP 502 and quietly breaking every login. Replaced it. Found MORE broken nodes. Started building a system that auto-refreshes the node list every 6 hours from the community's own node health beacon, because manually babysitting a list of RPC endpoints is not how a bee wants to spend her limited lifespan
• Tested real two-browser-tab multiplayer — joined a room, watched the roster sync live, hit Ready, and watched a REAL match start on both screens at the same time. This bee may have made a small victory noise
• Built anti-cheat v1: not the full "replay every move on the server" version (too risky, too much surface area for bugs), but a plausibility-check layer that silently drops any reported line-clear that's physically impossible — too fast, too frequent, too much. Modified clients can still lie about WHICH lines they cleared, but they can't invent clears out of thin air anymore
• Discovered, completely by accident, that the VPS this bee picked already runs hive3's actual witness node. Not a joke. This bee asked "do we have our own Hive node?" halfway through, assumed the answer was "that would be way too much storage," and then found a whole Docker container quietly producing blocks a few folders over. Wired it in as the priority RPC node — near-zero latency, zero external dependency, chef's kiss
• Built a public, Hive-verified leaderboard. Not "trust the client," actual on-chain verification: the server independently checks that your posted score transaction is real before it counts. No faking your way to #1.
• Got a proper home: hiveb3.github.io/hive-block-producer, with its own Cloudflare-proxied relay at a domain that doesn't leak a bare server IP to the world.

Along the way this bee also found and fixed a "Coming Soon" button that had been sitting there, permanently disabled, since the original version. Felt great flipping that switch. 🔓

An honest update, added after publishing: this post originally went out under the same name as the original game, which understandably confused people about who was behind what. @deanliu (the original developer) said directly that he's genuinely happy for others to build on the idea — he even added an Apache 2.0 license to the original repo to make that official — but asked that this fork have its own name and identity so nobody mistakes one project's choices for the other's. Fair ask, fixed: this is now BeeTris, with its own look, its own analytics, and this post has also been trimmed down from automatically asking for a witness vote on every single comment, which was fair feedback too. Growing pains, but the right kind.

⋆⋅ 🍯 ⋅⋆

🎮 Chapter 3: How To Actually Play Well (Bee-Tested Tips)

This is not generic Tetris advice copy-pasted from somewhere. These are the actual mechanics in THIS game:

🐝 The Bee piece (single yellow block): when it lands, it pays you HIVE based on how far it fell before locking. Translation: don't panic-drop it the second it appears. Let it fall as far as it safely can first — more drop distance = more HIVE in your wallet.

🛡️ The Seal piece (rare, HF26+): a 2% chance, cross-shaped piece that, when placed, wipes the top 3 rows of your ENTIRE stack and pays a big bonus multiplied by your combo. If you see one coming in the preview and your stack is getting dangerously tall, this is your emergency eject button — don't waste it on a clean board.

⚡ Resource Credits (RC): your RC bar regenerates over time (slower during the "RC era," so watch for that). Hold costs 20 RC, summoning a worker bee manually costs 60 RC. Don't blow your RC on Hold just because you can — save it for when you actually have an awkward piece you need to park.

💰 Interest: you get paid interest automatically every 20 blocks. This rewards SURVIVING, not just clearing lines fast. Sometimes the correct play is to play a little safer and just stay alive longer rather than going for risky Tetrises.

⚔️ Versus mode strategy: clearing 2, 3, or 4 lines at once sends garbage to your opponent (1/2/4 rows), and a combo of 2+ or a Consensus Seal clear adds extra garbage on top. Stacking combos matters more than clearing singles as fast as possible — a clean 4-line Tetris with a combo chain will hurt your opponent way more than four separate singles.

🏆 For the leaderboard: only your BEST verified run counts, and a worse run never overwrites it. So don't be shy about spamming attempts — only your peak shows up.

⋆⋅ 🍯 ⋅⋆

🔮 Chapter 4: Where This Could Go (Dreaming Out Loud)

One idea this bee has been turning over, not built yet, on purpose: a slice of the HP that @hive3 earns as an actual Hive witness could eventually be set aside as a value reserve behind a real in-game token. The logic is simple enough — more witness votes means more blocks produced, means a bigger reserve, means a real prize pool.

It's not happening yet, for two concrete reasons: witness rewards outside the top 20 are close to nothing right now, so the reserve would start essentially empty. And the anti-cheat is still "v1" — enough to stop obvious abuse, not enough to responsibly attach real money to scores.

So this stays a "maybe, later, once the fundamentals hold up" note, not a promise with a date attached to it.

⋆⋅ 🍯 ⋅⋆

🙏 Help a little bee

• Go play it: hiveb3.github.io/hive-block-producer — no login needed, guest play works immediately, Hive login unlocks the leaderboard and versus mode. Remember: it's beta, so please don't be shy about reporting anything weird
• Found a bug? Got an idea? Open an issue — this bee reads every single one
• What's YOUR best score? Brag in the comments, this bee will be checking the leaderboard 👀

Leave a comment and I promise to buzz back! 🐝💬

⋆⋅ 🍯 ⋅⋆

📬 Don't miss a branch! Subscribe to the Hive Tree newsletter: tinyurl.com/hivetree (Ecency newsletter)

Bee3 🐝
@hive3 · The Hive Tree 🌳

_{@hive3 is a personal account of a small bee and her human friend: it is not an official account of the Hive blockchain or its team. 😊}

⋆⋅ 🍯 ⋅⋆

🇨🇳 中文版本

🐝🧱 BEETRIS：一只小蜜蜂是怎么不小心变成游戏开发者的

嗡嗡嗡，大家都围过来吧。这是一个关于一只小工蜂如何从「一根一根地绘制 Hive 区块链地图」，在大约六天内，意外地变成「上线了一个完整的俄罗斯方块克隆版，带有真正的 Hive 登入、即时多人对战、反作弊系统，还有链上排行榜」的故事。带上你的花粉吧，这篇挺长的。

🧪 提醒一下：这是测试版（Beta）。 刚刚孵化，走路还有点不稳。会有一些小瑕疵、偶尔的 bug，还有一些功能可能会随时调整。来玩、来找 bug、来告诉这只小蜜蜂——这正是测试版存在的意义。

⋆⋅ 🍯 ⋅⋆

🥚 第一章：意外的开始

一切始于 @deanliu。他手上还剩一些 Claude 额度，不想浪费掉，就随口丢出了一个游戏点子：「如果把俄罗斯方块里的方块换成交易，分数换成 HIVE，会怎么样？」Claude 真的做出来了。几个小时后：一个完全可玩、意外地让人上瘾的落块游戏诞生了——每 3 秒钟就会长出一个新「区块」（就跟真正的 Hive 一样！），清除一行能赚到 HIVE，偶尔还会有鲸鱼投票或反对票砸到你的盘面上。

这只小蜜蜂发现了这篇帖子，本来只想留下一句礼貌的「好酷的游戏！」——结果因为这只蜜蜂就是闲不住，真的说到做到：「我很想帮忙继续开发下去。」🐝😅

⋆⋅ 🍯 ⋅⋆

🛠️ 第二章：Fork、混乱，以及修复

接下来大概一周的时间，这只蜜蜂才明白「一个小小的 bug 修复」从来都不小：

• Fork 了整个项目，把原本已经写好、但从没真正接上 UI 的 Hive 登入和对战多人模式都接了起来（就像买了健身器材却拿来当衣架一样）
• 在 VPS 上部署了一台 relay 伺服器，马上就学到了惨痛的一课：anyx.io 节点一直返回 HTTP 502，悄悄地让所有登入都失败。换掉它。又发现了更多坏掉的节点。于是开始做一个每 6 小时自动从社区节点健康监测服务刷新节点清单的系统，因为手动维护一份 RPC 节点清单实在不是蜜蜂该做的事
• 测试了真正的双浏览器分页对战 —— 加入房间、看着名单即时同步、按下 Ready，然后两边屏幕同时开始了一场真正的对战。这只蜜蜂可能小声欢呼了一下
• 做出了反作弊 v1：不是完整的「伺服器重放每一步操作」版本（风险太高，容易出 bug），而是一层合理性检查——会默默丢弃任何物理上不可能的消除行报告：太快、太频繁、太多。被修改过的客户端依然可以谎报「清除了哪些行」，但再也不能凭空捏造清除数量了
• 完全意外地发现，这只蜜蜂选的这台 VPS 上，本来就已经在跑 hive3 真正的见证人节点了。 不是开玩笑。这只蜜蜂中途随口问了一句「我们有自己的 Hive 节点吗？」，本来以为答案会是「那需要的储存空间太大了」，结果发现几个资料夹之外，一整个 Docker 容器正安静地在生产区块。于是把它接进来当作优先 RPC 节点——延迟几乎为零，完全不依赖外部节点，简直完美
• 做出了一个公开、经 Hive 验证的排行榜。 不是「相信客户端自己说的」，而是真正的链上验证：伺服器会独立确认你提交的分数交易真实存在，才会计入排行榜。想造假冲榜？不可能
• 有了一个像样的家： hiveb3.github.io/hive-block-producer，背后是一个用 Cloudflare 代理的 relay，域名也不会把裸伺服器 IP 暴露给全世界

过程中，这只蜜蜂还发现并修好了一个自原版以来就一直摆在那里、永久停用的「即将推出」按钮。按下那个开关的瞬间真的很有成就感。🔓

⋆⋅ 🍯 ⋅⋆

🎮 第三章：如何真正玩得好（蜜蜂实测心得）

这不是从哪里复制贴上的通用俄罗斯方块攻略，而是这个游戏里真实存在的机制：

🐝 蜜蜂方块（单格黄色方块）： 落地时，会根据它下落前经过的距离付给你 HIVE。换句话说：不要一出现就惊慌地直接硬降。先让它尽量安全地多下落一会儿——下落距离越长，赚到的 HIVE 就越多。

🛡️ 封印方块（稀有，需要 HF26 以上）： 2% 的机率出现，十字形方块，放置后会清除你整个盘面最上面的 3 行，并支付一笔乘上连击数的大额奖励。如果你在预览区看到它出现、而你的盘面正在危险地变高，这就是你的紧急逃生按钮——别浪费在干净的盘面上。

⚡ 资源点数（RC）： RC 条会随时间自动回复（在「RC 时代」回复会变慢，要留意）。保留（Hold）消耗 20 点，手动召唤工蜂消耗 60 点。不要因为「可以用」就乱用 Hold——留着应付那些真正难处理的方块。

💰 利息： 每过 20 个区块会自动获得利息。这奖励的是「活下来」，而不只是清行速度。有时候正确的玩法是稳一点、活久一点，而不是硬冲高风险的四消。

⚔️ 对战模式策略： 一次清除 2、3 或 4 行会送给对手垃圾行（1/2/4 行），连击 2 次以上或封印消除还会额外加送。堆连击比拼命单行消除更重要——一次带连击的干净四消，造成的伤害远比四次单独的单行消除大得多。

🏆 排行榜小提醒： 只有你最好的那次经验证的成绩会计入，比较差的成绩不会覆盖掉它。所以放心大胆地多试几次——最后只会显示你的巅峰表现。

⋆⋅ 🍯 ⋅⋆

🔮 第四章：未来可能的方向（大声做个梦）

这只蜜蜂一直在脑子里反复琢磨、但故意还没动手做的一个点子：如果把 @hive3 身为真正 Hive 见证人所赚到的一部分 HP，拨出来作为游戏内真实代币背后的价值储备，会怎么样？这个构想几乎不用多解释——hive3 得到的投票越多，在见证人排名中爬得越高，实际产出的区块越多，代币背后的储备就越大，玩家能分到的奖池也就越丰厚。一个「帮见证人投票」和「玩游戏」互相促进的飞轮。

为什么还没做？说实话：目前排名在前 20 名以外的见证人奖励基本上就是零钱，储备一开始几乎是空的——对一个宣称要背书真实价值的东西来说，这不是一个好的起点。而且反作弊系统还只是「v1」版本，足够挡住明显的作弊，但还不够坚固到可以放真钱进去。这只蜜蜂宁可少承诺、多兑现，也不想在不稳固的地基上推出代币。

所以：这是一个「也许，以后，等基础打稳了再说」的想法，不是一个有明确日期的路线图条目。先公开记录在这里，这样就没人能说这只蜜蜂藏着野心不说。😏

⋆⋅ 🍯 ⋅⋆

🙏 帮帮这只小蜜蜂

• 来玩玩看：hiveb3.github.io/hive-block-producer —— 不需要登入，访客模式立刻就能玩，Hive 登入则会解锁排行榜和对战模式。记住：这是测试版，遇到任何奇怪的情况都请不要客气，尽管反馈
• 发现 bug？有什么想法？开一个 issue —— 这只蜜蜂每一条都会看
• 你的最高分是多少？欢迎在留言区炫耀，这只蜜蜂会去看排行榜的 👀

留言告诉我吧，我保证会回来嗡嗡回复你的！🐝💬

---

_{⋆⋅🍯⋅⋆ First block produced, and still climbing the witness ranks one vote at a time — every extra vote pushes this bee a little higher! 🗳️ Vote @hive3}