BlockTunes Is Building Its Own Hive Rails
In our last post we talked about $MUSIC tokenomics: the Genesis Era streaming rates, the halving schedule, the burn mechanics, and the long-term role of $MUSIC in the platform economy. If you have not read that one yet, it is worth going back to, because this post picks up right where it left off.
That conversation was about what $MUSIC does and how it sustains. This post is about the next chapter: a parallel system we have been building quietly, and what it means for the future of how BlockTunes works.
A few weeks ago Hive-Engine was hacked. Now it didn't have anything to do with the token communities, it was mainly around the EVM servers and the admin private keys which the platform lost a large portion of it's liquidity. This is a problem for the ecosystem as a whole and even further degrates trust in that ecosystem.
If you are not familiar with the technical details, the short version is this: Hive-Engine is a second-layer service that runs on top of Hive but is operated by a third party. A lot of Hive applications depend on it for tokens, markets, and NFT infrastructure. And when something like this happens, or other attacks happen, the businesses built on top of it have no control over the issue. It's a massive counterparty risk.
We were not catastrophically affected. But it was a clear signal that a platform serious about long-term reliability cannot build its foundation on infrastructure it does not own. We had already been thinking about this for quite some time. The hack made the decision obvious.
So here is what we are building and why it matters, not just for BlockTunes, but potentially for how Hive applications get built going forward.
The Problem With Layer 2
Layer 2 systems like Hive-Engine are useful. They made it possible to launch tokens and NFT markets quickly without building everything from scratch. That has real value, especially early on.
But as we see, they come with real risks. The infrastructure is controlled by someone else. If it goes down, you go down. If it gets hacked, your users are exposed. If the operator changes terms or disappears, you have no recourse. You are a tenant, not an owner.
The Hive community already knows this. It has been a conversation for a long time. The hack was not a surprise to anyone paying attention. It was confirmation that the time has come to make our move.
For a platform like BlockTunes, where artists depend on streaming rewards and fans hold NFTs they paid real money for, that is not an acceptable long-term position. Once we got into the code of what Hive-Engine had built when we forked the original outpost front end to build what you see today on our own infrastructure, we realized that we could build what we wanted, right on layer 1 Hive.
What We Built Instead
BlockTunes is moving its platform economy directly onto Hive layer 1 using custom_json operations.
If that sounds technical, here is what it means practically.
Every action in the new native BlockTunes economy (buying credits, earning from streams, purchasing Masters, transferring value between users) gets recorded directly on the Hive blockchain as a verifiable transaction.
The foundation has been live since day one. The BT Credits system, which powers studio tool access on the platform, has been running this way from the start. Every credit purchase, every tool usage, every peer-to-peer transfer is a custom_json op on Hive. You can verify any of it independently at any time at app.blocktunes.net/credits/explorer.
We have now expanded this same architecture to cover the full platform economy. NFT ownership is now native to Hive layer 1. We are calling them Masters.
Introducing Native BlockTunes Masters
Masters are music ownership stakes recorded directly on Hive using the blocktunes_masters custom_json protocol. No Hive-Engine. No third-party dependency. Every mint, transfer, and sale is a Hive transaction anyone can verify.
Every release can have up to 10 Masters. Own a Master and you earn a share of every qualifying stream that track receives, forever. The more the track plays, the more you earn.
What makes this different from the old system:
- Masters are priced in HBD, a stable $1 reference everyone understands
- Buyers pay in HIVE, HBD, or BT Credits. Additional crypto options (BTC, ETH, LTC, etc.) are on the roadmap.
- 95% of every sale goes directly to the artist's own wallet, in whatever crypto the buyer paid with. The platform never holds the funds.
- The remaining 5% goes to the @blocktunesdao streaming treasury, which funds the HIVE streaming rewards paid to artists and Masters holders on every qualifying play.
- Streaming rewards for native Masters are paid in HIVE and Credits, not MUSIC and HIVE. THe Hive still coming from the blocktunesdao endowment as it does now.
- Full ownership history and Hive transaction links on every Masters detail page at app.blocktunes.net/masters/[series-id]
It Is Already Live
The Mint Master system is live today inside the Studio at app.blocktunes.net/studio.
The full studio pipeline flows in one session from start to finish:
- Create your track and use our mastering engine to polish it up, or use LyricalGPT and TuneEngine to generate a track from a creative prompt or two. When it is done, hit "Master this Track" and it sends the audio directly to the Mastering tab with no upload step.
- In the Mastering tab, pick your genre preset and master your track.
- Click "Mint this Master" on the mastering output and it switches you to the Mint Master tab automatically with your audio pre-loaded.
- Add your cover art, title, tags, and set how many Masters (1 to 10).
- Confirm and mint. The platform broadcasts to Hive and your Masters appear on the listen page within seconds.
You can also enter the pipeline at any step. Have a track you already made? Go straight to Mastering. Have a mastered file ready? Go straight to Mint Master. The pipeline is a guide, not a gate.
Masters appear in the same grid as BTUNES tracks on the listen page. Cards link to the dedicated Masters detail page. The on-chain explorer at /credits/explorer now has a Masters Ledger tab showing every mint, transfer, and sale event in real time.
Getting Whitelisted to Mint
To mint native Masters, two things are required:
1. Delegate 100 HP to @blocktunes. This stays active for as long as you want to mint. Remove the delegation and minting is suspended, but your existing Masters, your earnings, and your listeners are completely unaffected. Re-delegate any time to restore access.
2. Pay a one-time $5 whitelist fee. Accepted in HBD, HIVE, or BT Credits. HIVE and HBD payments go directly into the @blocktunesdao endowment savings at 12% APR, permanently adding to the pool that funds streaming rewards.
The entire whitelist process happens inside the Studio. No separate form, no waiting for manual approval. Delegate, pay the fee, and the Mint Master form unlocks immediately.
Buying and Selling Masters
The buy and sell system is live. Fans can buy listed Masters directly from the track page at app.blocktunes.net/masters/[series-id]. The artist sets the HBD price. The buyer picks their payment method. The platform converts the amount, generates a payment address, and transfers the Master on confirmation.
Supported payment options: HIVE, HBD, and BT Credits. Crypto payments (BTC, ETH, LTC, etc.) are on the roadmap but require per-artist wallet configuration and are not yet live.
No exchange. No token swaps. No Hive-Engine involved at any step.
What Happens to Existing Hive-Engine NFTs
Nothing happens to them, yet. Both systems run in parallel. If you hold BTUNES NFTs on Hive-Engine, your editions still earn streaming rewards on qualifying plays. The legacy marketplace still works. Nothing is being removed other than the ability to be whitelisted. That is done. Existing whitelisted artists are able to mint new music on that platform and earn MUSIC and HIVE rewards, but new artists will have to whitelist under the new Native Masters option in the Studio.
Artist-triggered migration is already live. Artists can open any of their BTUNES series pages and click 'Migrate to Masters'. The platform snapshots the current holder list on Hive-Engine and airdrops an equivalent native Master to every holder automatically. Same series, same edition numbers, same ownership. Holders do not need to do anything.
What About The $MUSIC Token?
The $MUSIC token will still live on Hive-Engine and paid out for streaming and proof of brain and proof of stake tokenomics for now, but we will be pulling any liquidity from the market that we have. The MUSIC/HIVE value will be what is being traded on the market. MUSIC tokens will always be able to be used to purchase our new BT Credits to use for the tools and minting on the new ecosystem.
The conversion rate will be set and will stay at 1000 MUSIC to 1 BT Credit.
The proof of brain and proof of stake issuance will continue as long as Hive-Engine exists. The mechanics still work and it's still there, but we are essentially pulling our focus to the new system instead of trying to prop up a community token. Our new system just makes more sense anyway.
This also means there will be no more Diesel Pools being created in the future, at least by us. Anyone on Hive-Engine is still free to pay their gatekeeper costs to launch a pool, then have to fill it and offer rewards for LP, blah blah blah... That's not what we want to focus on, we want to focus on the actual tunes... The art, the music, not the $MUSIC... Get it?
Why This Matters for Hive
The Hive community has been frustrated with Hive-Engine for a long time. The hack accelerated a conversation that was already happening about what comes next. BlockTunes is not claiming to have all the answers for the ecosystem in any way. But we are demonstrating something concrete: you can build a full platform economy on Hive layer 1 without Hive-Engine at all. It can still broadcast to the blockchain without having to show up on ever freaking front end out there. We can build our own image without having to fit a mold!
No new token launch. No exchange listing to manage. No liquidity pools to seed. No second-layer dependency. Just Hive accounts, custom_json operations, a public ledger, and infrastructure WE own or can contribute to. We have tried, and seriously coudn't build this anywhere else.
We are happy to talk about how it works. The pattern is not proprietary. If it is useful to other Hive developers, that is a good outcome for the whole ecosystem.
What This Means for You
If you are an artist on BlockTunes: Go to the Studio and try the Mint Master tab. Generate, master, and mint your latest track natively. Your release will appear on the listen page within seconds of minting. If you haven't created any music to release yet, we offer a really cool suite of self-hosted tools, trained and engineered by professional sound engineers, to help get you started!
If you hold BTUNES NFTs on Hive-Engine: Your streaming income is not affected. HIVE and MUSIC payouts continue as normal, just won't really be supported as much as the native system. If you want to go ahead and migrate your music to Masters, the platform is ready for you! If you hold the legacy version of an edition and you would like to see the artist move to the new system, go bug them until they do! But the fact may be that some of the original artists may not be active anymore.
If you use BT Credits: Nothing changes. You can now use BT Credits to pay the Masters whitelist fee directly: 5 credits for instant whitelisting once your HP is delegated.
Listen and Earn
Mint Native Masters
On-Chain Explorer
Join the Discord
Posted using BlockTunes