A few people have started talking about HivePredict and using it for real, and the feedback has been incredible so far. I genuinely appreciate every bit of it. Whether it's bug reports, feature suggestions, or just letting me know something feels off, that kind of input is what keeps this project moving in the right direction. Thank you.

You can check the app out here: https://hivepredict.app

With real users now on the platform, the last stretch of work has been focused on making HivePredict more transparent, more reliable, and more aligned with what Hive is actually about. Here is what has been shipped (some of it based on user feedback).

Transparency first

Lol, so I built the app and didn't realise that I didn't put who built the app so it looked faceless and that kinda made people a little hesitant (I was too focused on shipping, haha).

You can now see exactly who built this thing and how it operates. Builder attribution is visible across the site with links back to my Hive profile (@beggars). The homepage, How It Works page, and market detail pages all clearly explain the platform mechanics, fee structure, and burn model. No hidden behavior.

There is also a brand new public Activity Feed at /activity. Every market creation, bet placement, refund, and resolution is logged and visible. You can filter by event type, market, or account. Every entry links directly to the on-chain transaction on HiveBlocks so you can verify everything yourself. The whole point is that you should not have to trust me. You can check.

Thank you @stayoutoftherz for pointing out the lack of any person on the app, lol.

5% burn on every resolved market

This is now live and built into the actual payout math. When a market resolves, 5% of the pool is burned by sending it to @null, which is the standard Hive burn mechanism. This is not just a promise on a landing page. It is real, it runs on every resolution, and you can see the burn records on resolved markets.

Thank you to @yecier for suggesting this.

Creator opening bet model

Market creation has changed. Instead of paying a flat creation fee to create markets, creators now place an opening bet on their own market when they create it. Your transfer becomes your first prediction on the side you believe in. This means every market starts with skin in the game from the person who made it. So the only fee is the tiny platform fee now, zero creation fees.

The old fee-based markets still work as they were. This change only applies to new markets going forward.

Losing bet notifications

Nobody likes losing, but at least now you will know about it right away. When a market resolves and you are on the losing side, the platform sends a dust transfer (0.001 HIVE) to your account with a memo that tells you the outcome, who won, and how much you lost. No more checking back on the dashboard to find out what happened. The notification comes to you on-chain.

Market activation clarity

Markets now require a minimum of 3 participants before they activate. While a market is still gathering participants, it shows as "forming" instead of "pending," along with a progress indicator showing how many more people need to join. This should make it much clearer what is happening with a market that has not kicked off yet.

I also made it so markets can no longer be one sided. It seemed strange to me that markets could technically have 3 participants and all be on the same side, so markets to be valid need to have participants on both sides or if the market ends, it is voided and everyone is refunded.

Reliability and backend improvements

A lot of work went into making the backend more resilient. Payout processing, market resolution, and prediction placement all got hardened against edge cases like duplicate processing, race conditions, and partial failures. The platform also gained a full integration test suite running against real Postgres to catch issues that mocked tests would miss. Several real bugs were found and fixed through this process.

I also added in a bunch of resilience and data integrity checks, including some disaster recovery tooling incase of anything happening to the Postgres database and other potential issues the app could face, allowing everything to be restored and replayed for 100% data integrity.

What is next

HivePredict is still early and I am building it in public. If you have ideas, complaints, or want to see something specific, hit me up on Hive. The feedback so far has shaped a lot of what shipped here and I want to keep that going.

There will be responsible betting features also coming as well, thanks to @davideownzall for his comment around this. The plan is to have caps, the ability to self-exclude and more due to the gambling nature of the app.