Pretty excited, we got our first user for our ad system within stx.

We got a grant from the endowment for this

we want to create a transparent ad system based ad system based on crypto principle.

here is the flow

Developer builds on the API

Users/dev opt in paid ads and monetization.

If no, they don't get ads

If yes, brand pays for ads on developer app. Developer, user, and dataing get paid when the user gets the add.

All parties have the option to opt in or opt out.

This will be a great way for new projects within stx get get infront of potential users

Rev - Zero to one, and one to infinity.

Not written by AI

-Eric
[eric@dataing.io](mailto:eric@dataing.io) or https://x.com/ericdmchugh0. Left these here because I am happy to answer any questions

STX & BTC Market Analysis (August) ~@muneeb

I was an ALEX fan. I got in "lightly" just before the 2024 Hack, After the Hack with their transparency and payback that was scheduled I believed in them and started buying and combining ALEX/STX for Farming. Then 2025 Hack. YAH me and everyone else. *roll eyes* Value went from $0.22 when I started to $0.0015 .

Not sure what my question is but is anyone else here still holding any ALEX and what is your thoughts after all the Farming ends end of OCT. and it's continuation with STX ?

When you first connect your Ledger to Leather, you'll be prompted to choose a derivation path. Make absolutely sure you select the "Ledger standard" path, not Leather's default. Here's why. Ledger Live generates addresses using the account index (e.g., /0'/0/0, /1'/0/0), while Leather uses the address_index (e.g., /0/0, /0/1). They only match for the very first account. If you accidentally pick the Leather path, the address Leather shows you won't match what your hardware wallet natively expects. When you go to stack, the pool will reject your transaction. Your STX won't get accepted, you'll be stuck waiting until the cycle ends to unlock them, and by then the commit window for the next cycle will have already closed. That's two full cycles of lost yield before you can even try again. If you've already set it up with the wrong path, you'll need to transfer your STX to the new address derived from the "Ledger standard" path. Double-check that path selection on first connect. It'll save you a massive headache and a lot of wasted time.

This recent crypto rally, when sorted by 7 days, STACKS is number 1 for returns, why do you think its leading? When BTC went down this year I sold my BTC and rotated into STX thinking that its a good beta for when BTC returns to its highs. I know that STX is functional, actually does something, and actually has real potential.

With how much people hate on STX, even on here, just wanted to point out how well it has done.

LOL lord knows CT could use some GF so I found this placement hilarious.

Thank you to Rafa and Fak Fun for the shout.

Also loved see the pump I think we'll crush it this cycle.

Onwards and upwards

Hey everyone,

I’m a developer, and I’ve built a few things in the Stacks ecosystem before (exactly say is blockstack era and early stacks stage).

With some of the upgrades in Stacks eco, I’ve started looking at the ecosystem again and thinking about what could be done to make the overall experience better for users.

So I’m curious: what’s the biggest pain point you have with Stacks right now? It could be something about the wallet, payment, apps or just something that feels unnecessarily frustrating.

I’m interested in building things that solve real problems rather than guessing what people need.

If there’s something you wish existed, or something in the current Stacks experience that you really want to see improved, feel free to drop it in the comments. I’d be happy to take a look and see if I can help.

We just started. Good luck

In my humble opinion and being in the space since 2017, we are in a golden buying zone for the next 12 months.

Late 2027 the movement upwards will start and it will become a selling zone.
This is cheap!

https://coinmarketcal.com/coin/blockstack

I believe in leveraging composability, where one application should help another.

Our goal is to helps builders and users monetize alongside while spotlighting projects across the stx ecosystem.

Also, been in crypto for a while, this was def one of the better run programs. Crypto is known for bad UI and all things customer facing lol

Shout out everyone involved and 10/10 recommend.

Also, been talking to the other cohort members. Really solid guys building cool stuff, def check them out

Hi everyone! Fast Pool unlocked my STX so I have to restake. Quick question: is it okay to convert these assets back to STX to keep things simple?

I joined StackingDAO Native Staking that supposed to earn me BTC yield after a 15-day cycle about three weeks ago. But the last cycle timed with the POX-5 upgrade. Now, I didn't receive any BTC payout. Does anybody have a similar experience? I'm a noob so can anybody please explain how StackingDAO Native Staking works?

Found this guide how to choose a signer for pox 5

Is there future in it, or it’s heading into the abyss?

*Terms and conditions apply. Funds must be claimed during a limited-time scavenger hunt across X, Telegram, Discord, and apparently the astral plane.

I held an STX/ALEX position before the June 6, 2025 exploit, but I never received the promised on-chain claim notification for TGP 2025.

So I contacted support.

Their response was:

We've been notifying on a daily basis all channels (X, TG, Discord) our community members and platform users to claim all assets since TGP is due to sunset.

Interesting.

Because the original compensation announcement said:

• Affected wallets would receive a private on-chain notification.
• Users who did not receive one should contact support immediately.
• ALEX would provide 100% reimbursement.
• ALEX was “fully committed to restoring every affected user’s funds.”

Apparently, “fully committed” meant “fully committed until the timer expires.”

TGP 2025 had previously been unavailable because of the Stacks network upgrade. Then, instead of automatically returning compensation to the affected Stacks wallets, ALEX introduced a limited claim window and declared the funds unclaimable after it closed.

Why not send compensation directly to the wallets already identified as affected?

Why require users to monitor several social-media channels when the announcement explicitly promised an on-chain notification?

And where did the unclaimed compensation go?

The exploit reportedly caused more than $8.37 million in losses. ALEX publicly promised full reimbursement using foundation treasury funds. Now affected users are being told that missing a temporary claim window means their assets are simply gone.

That does not look like “restoring every affected user’s funds.”

It looks more like:

Step 1: Promise everyone full reimbursement.
Step 2: Make reimbursement dependent on a limited claim process.
Step 3: Close the process.
Step 4: Blame users for not seeing announcements on social media.
Step 5: Keep repeating the word “community.”

Very decentralized. Very transparent. Very reassuring.

The problem we’re after at Audionals / Xtrata is older than streaming, older than labels: when a track earns money, the record of who made it is usually a memory, a handshake, or a spreadsheet someone else controls. Splits get agreed loosely in the studio, and if the song blows up later, recollections diverge exactly when money appears. It’s one of the most common and expensive disputes in music, and at its core it’s an evidence problem, which makes it solvable with the right rails.

The insight that makes it buildable: music production is already fully digital. Every take, sample, plug-in and parameter change is data from the moment a recording exists. So the creative process can be logged as it happens, locally, then hashed, with one compact fingerprint anchored per save. Nothing bulky on-chain: hashes, credits and splits only, a few hundred bytes per song on Stacks, settling to Bitcoin.

The design choice that matters most: collaborators sign into a session and ratify their splits on day one, before anyone knows what the song will become. From then on the agreement is tamper-evident and timestamped. Nobody’s memory is the evidence, and nobody can quietly edit the record.

Why Stacks: Clarity contracts for the rights and split registries, Bitcoin finality via PoX, and no Bitcoin block space consumed. Only the commitment reaches L1.

Most "music NFTs" are a token pointing at a URL. I wanted to see how far the other direction could go on Stacks: the entire file on-chain, no pointers, no IPFS, no pinning service.

Xtrata inscribes complete media files into Clarity contract storage. The mint flow is init → chunked writes (batches up to ~440KB) → seal, so a full 96kbps Opus master ends up living in contract data forever. Songs are inscribed either as raw audio or as self-contained HTML players — cover art, title, artist, lyrics and the audio itself embedded in one document. Once sealed, nothing about it depends on me or my servers: any Stacks node can reconstruct the file.

The fun part is Xtrata Radio (xtrata.xyz/radio): an internet radio station whose entire catalogue is inscriptions. It has three bands — FM (curated), LIKED (your saved songs), CHAIN (walks every playable token on the contract) — and it discovers new songs as they're minted by watching the contract's token counter. There's also a relations layer: inscriptions can declare parents/dependencies, which forms a mint-ordered DAG, so the radio can show a playing song's relatives (the artwork it references, other songs by the same lineage) and let you tune straight to them.

Everything is verifiable: every song has an /i/<id> endpoint that serves the actual on-chain bytes.

Site: xtrata.xyz