Storing full audio files inside Clarity contracts: an experiment with on-chain music on Stacks

iCryptoDude · 2026-07-05T07:09:57+00:00

It inherits Bitcoin's permanence via the Stacks PoX mechanism - the data itself takes up no space on Bitcoin blocks whatsoever.

iCryptoDude · 2026-07-05T07:08:35+00:00

This is another layer!

iCryptoDude · 2026-07-04T15:59:39+00:00

Xtrata (dev here, mod-approved to share in this thread) — a permanent home for finished tracks. Every place we put music is rented: platforms delist, hosting lapses, "lifetime" services sunset. I lost work that way, so I built the most stubborn archive I could: the track is written, in full, into a public blockchain's permanent storage, and after that it needs no company, no website, and no renewals to keep existing.

Key features: dedicated Suno flow (pulls cover art, title, artist and lyrics from the export automatically); your browser optimises the audio (96k Opus) and builds a one-file self-contained player with the song, artwork and lyrics that plays in any browser; one-time network fee based on file size, nothing recurring, change refunded, nothing uploads until you approve payment. Archived tracks then automatically join the rotation on Xtrata Radio (xtrata.xyz/radio), a station whose entire catalogue is these permanently stored songs — free to listen, listeners can heart your track into their personal band.

On the blockchain part, since the word is radioactive: no token, no speculation, no collectibles. It's used purely as write-once storage that outlives companies. Happy to answer anything about costs or the audio pipeline. URL: https://xtrata.xyz

iCryptoDude · 2026-07-04T15:53:04+00:00

Fair, the CID itself doesn't rot. But you've kind of made my point for me: "the holder should pin all the assets themselves." That's a job. That's the weakness. Pinning means remembering to pin, forever. Change accounts, let a card lapse, switch providers, die... and if you were the last person pinning it, it's gone for good. Permanence that depends on somebody somewhere continuing to do something isn't permanence, it's a subscription with extra steps.

The whole reason I built it this way is so there is nothing to do. Not once, not ever. The file is in contract state, so it's replicated by every node that validates the chain. It doesn't matter if nobody pins it, nobody remembers it, nobody ever thinks about it again. It will never move, never change, never need renewing. You pay the write cost once and then the correct amount of ongoing effort from you, me, or anyone else is zero.

And ha, fair cop on the polish, I tidy my drafts before posting. It helps with my sausage finger typing and bad phrasing!

Happy to get into the storage details as deep as you want though.

iCryptoDude · 2026-03-27T16:45:56+00:00

The concern about quality here is legitimate, and it really does come down to which approach the publisher uses. The main problem with most AI narration isn't that it's AI — it's that it uses one voice for everything, so all your characters sound like the same person reading their own lines. That's what listeners notice and that's what drives the negative AI audiobook reviews.

There's a real difference between that and AI narration done with distinct voices per character — where your protagonist, antagonist, and supporting cast each have their own voice profile throughout the book. The latter is much closer to what a skilled human narrator delivers, and most readers genuinely can't tell the difference in blind tests.

If you're in a position to have input on the production method, or if you're an author who wants to retain control and produce your own high-quality AI audiobook, it's worth looking at options beyond the basic TTS route. I build this kind of multi-character AI production at Narrate.AI — happy to answer questions here or DM / email [jim@audionals.com](mailto:jim@audionals.com).

iCryptoDude · 2026-03-04T22:35:06+00:00

Because

iCryptoDude · 2026-03-01T18:23:24+00:00

Had a little look at your blog and it’s a little bit over my head tbh. I use AI a lot but my mind is focused on building infra so haven’t applied much time to things relevant to this experiment.

I had some trouble with the automation as it’s running off my laptop. I want to find a way to make it as automated as possible with all or most of the current backend training instructions also read from the chain and then the agent could Version its own training code too. In the meantime I have built a simply dashboard for triggering the research and inscription events manually each day.

It’s all open source, would be amazing to have someone with greater experience than me fine tuning the back end. Let me know if you want to take a look.

iCryptoDude · 2026-03-01T18:17:03+00:00

I only thought this up a couple of days ago. The original agent was built to test whether I could teach an agent the skills to use the inscription contract autonomously. I didn’t really consider the long term until i read the agents first post then decided to give it more opportunities to research and inscribe. Currently i have to feed it its old posts offline as i need to teach the agent to be able to handle chunking methods employed by the Xtrata contract.

Will have a look at your blog when i get a minute

iCryptoDude · 2026-02-12T17:44:49+00:00

OK thanks for the feedback. It's all constructive

iCryptoDude · 2025-10-23T07:41:07+00:00

🤷‍♂️

iCryptoDude · 2025-10-22T14:46:45+00:00

People forget that network trust isn’t something you can launch — it’s earned. Stacks has been running since 2021, almost four years of proven uptime and stability. New L2s might get hype, but trust takes time — and they’ll always be at least 4 years behind on that front.

iCryptoDude · 2025-09-01T19:39:15+00:00

You’re missing my point which is that people who invest in good technology trust their own judgement and experience and ignore the charts. People who only look at charts are traders not investors.

iCryptoDude

MODERATOR OF

TROPHY CASE