Today is a big day for HivePredict. While constant updates from @beggars have been shipped on an almost daily basis, this feature has been in the works since the beginning.
We now support Hive Engine token markets.
That means markets are no longer limited to HIVE and HBD. Communities can now create and participate in prediction markets using their own Hive Engine tokens, with the same core market mechanics HivePredict was built on.
If you’ve been waiting to run markets around your own ecosystem, your own community events, and your own token economy, this launch is for you.
What’s Live Right Now
1. Native + Hive Engine token market support
You can now create and bet in markets using supported Hive Engine tokens in addition to HIVE/HBD.
2. Dedicated market segmentation
Markets are now easier to browse with distinct groupings:
- Core markets (HIVE/HBD)
- Hive Engine markets
- All markets
These are router-backed tabs, so they are reload-safe and directly linkable.
3. Full-screen token picker (with search)
The create-market flow now includes a full-screen token selection modal with search, so finding the right token is fast even as token lists grow. As you can see, there are 848 custom tokens on Hive Engine.
4. SWAP.* token exclusion
Hive Engine SWAP.* symbols are intentionally excluded from market token selection. They are transitional cash-out bridge symbols and not ideal as long-horizon market settlement units.
5. Pre-bet and pre-create balance checks
Before users place a bet (or create a market with an opening bet), HivePredict now performs balance preflight checks for custom tokens. This helps prevent failed attempts and unnecessary transaction churn.
6. Hive Engine transfer verification layer
We added a second verification gate for non-native token transfers using Hive Engine API transaction info and transfer event matching, rather than relying only on base-chain op parsing.
Why This Matters
Prediction markets are most powerful when they are local, composable, and native to the communities that use them.
Hive Engine token support unlocks that:
- Token communities can run markets in their own unit of account.
- Incentives can stay inside each community economy.
- Users can participate without constantly bridging behavior back to only HIVE/HBD markets.
In short: HivePredict is becoming a broader market infrastructure layer for the Hive ecosystem, not just a single-token venue.
Fee and Burn Behavior for Hive Engine Markets
Secondary (Hive Engine) markets follow the same economic model:
- Fees are accounted in the market token.
- Burn payouts are executed in the market token.
- Non-native token payouts are sent through Hive Engine
tokens.transfer(custom_json) flow.
So if a market is denominated in an HE token, settlement remains fully consistent in that token.
A Note on Rollout Philosophy
This launch balances expansion and safety:
- More token access.
- Better UX for token discovery.
- Stronger transfer validation for non-native assets.
- Clear exclusions for transitional token classes (
SWAP.*).
We’ll keep iterating from here with performance improvements, better token discovery UX, and deeper ecosystem integrations.
Thank You
This feature happened because users asked for it clearly and repeatedly: support community tokens, make secondary markets first-class, and keep the trust model tight.
Keep the feedback coming. The next set of improvements will be shaped the same way this one was: directly by real usage and real constraints.
Go check it out: https://hivepredict.app if you also want to participate in the test HE market I've created, let me know so I can send you some BEGGARS tokens to play. I've already sent some of the regulars tokens, but if anyone wants any to test, just drop a comment.