xRoot

Solana infrastructure & token operations.
Deploy · Audit · Manage · Distribute
built by @SulimanMuk

[xRoot @xrootdev]

Solana's 90% rent reduction is being described as “Solana gets cheaper.”

That's true.

But there's a more interesting consequence:

old accounts keep their old SOL deposit.

That creates a finite pool of reclaimable SOL that gets more economically significant as new accounts become 10× cheaper.

I dug into SIMD-0437 and ran the numbers ↓

[xRoot @xrootdev]

Transaction v1 is expected on Solana mainnet at 01:03 UTC tonight.

The loud failure you'll see: -32015 from getTransaction, getBlock, blockSubscribe. One v1 transaction fails the whole getBlock response. The fix is one line — maxSupportedTransactionVersion: 1.

The quiet one is worse. Your indexer keeps reading compute limits and priority fees from ComputeBudget instructions, and in v1 they moved. Priority fee also changed unit: micro-lamports per CU became total lamports.

Nothing errors. The numbers just go wrong from tonight.

Guide: https://t.co/fn7A8wHoi0

[xRoot @xrootdev]

I wrote the whole v1 migration up when it was announced — wire format, the RPC failures, the indexer bugs, Geyser, and the fee-unit change:

https://t.co/1WeWvBaOef

[xRoot @xrootdev]

If you're building on Solana, transaction v1 is a breaking change you should prepare for.

Solana is moving from 1,232 → 4,096 bytes per transaction.

The bigger change isn't the size.

It's the new transaction format — and what it means for code that reads, indexes, streams, or analyzes transactions.

🧵

[xRoot @xrootdev]

Solana's transaction v1 is supposedly landing Tuesday. The gate isn't queued yet, so I'd hold that thought.

But the migration is worth doing today either way. One line:

maxSupportedTransactionVersion: 1

Miss it and getTransaction, getBlock and blockSubscribe start returning -32015. That's the loud failure.

The quiet one is priority fees changing unit — v0 counts micro-lamports per CU, v1 counts total lamports. Nothing errors. The numbers just go wrong.

[xRoot @xrootdev]

@KennyLoaded @fabioberger123 I have the exact same issue, and I really don't think a paid vouch — "I found someone" — helps protect users. A lot of developers like us, doing simple instructions like closing ATA accounts, which most of the time requires multiple transactions, face the same gate. It gives me the impression that @phantom really doesn't support developers.

Anyway, I think trusting a domain isn't really better than trusting a set of instructions. If you trusted the instruction instead of the domain, there would be more security for users — even a newly vouched person couldn't change their mind.

It's really frustrating to work on something with passion and lose all of that to a vouch gate that blocks me, and the development of @solana.

[xRoot @xrootdev]

More of your SOL stops being locked tonight.

Step 2 of Solana's rent cut, around 21:12 UTC: 6,333 → 5,080 lamports per byte. Since step 1 on Sep 4 the requirement is down 27%.

Nothing gets sent to you. The chain just stops requiring it — and it sits in your accounts until you close them.

https://t.co/5sMLnd5vMP

[Anza @anza_xyz]

Transaction V1 activation on mainnet-beta is moving to the start of epoch 1035, expected Sept 15 at ~1:20 AM UTC.

Teams across the ecosystem told us they needed more time to test and integrate V1 support. We listened.

How to get ready:

- V1 is live on devnet, test your integration now.

- Compute budgets in V1 are set using a new transaction config. Compute budget instructions still work on legacy and V0 but no-op in V1.

- App developers: even if you don't plan to send V1 transactions, some changes may impact your app. Review the guide below.

Details: https://t.co/712Ipj8hLu

[xRoot @xrootdev]

There's a date going around for Solana's new transaction format. September 9th.

That's a target, not a timestamp. Solana feature gates switch at fixed epoch boundaries ~38 hours apart — the next is around 17:10 UTC today, then Thursday morning.

So September 9th isn't a guaranteed activation time. And the feature isn't scheduled on-chain yet.

If you send transactions, nothing changes.

If you read them — bots, indexers, dashboards, anything counting fees — that's what breaks. And some of it breaks quietly.

Once it is scheduled, you may get only a day and a half of notice.

Track it live:

https://t.co/N7GRL3Q0Bg

[xRoot @xrootdev]

@Bigkhaos001 your wallet is pretty clean

[xRoot @xrootdev]

Solana's rent cut went live this week. Step 1 of 5: 6,960 → 6,333 lamports per byte.

Nothing was refunded automatically. The chain lowered what your accounts must hold and left the difference sitting there.

On a live account that surplus is ~0.0002 SOL. Small.
On a dead one you get the whole deposit back — ~0.002 SOL. 10× more.

300 dead memecoin accounts: ~0.6 SOL.

Check yours — read-only, no wallet connect:
https://t.co/zieowiyYyn

[xRoot @xrootdev]

@nick_pennie p95 under 30ms is insane

[xRoot @xrootdev]

@SolanaHub_ Can’t see the other way, so Solana it is ☀️

[xRoot @xrootdev]

@solshan_ @solincinerator you might have some if you've old open accounts (even tokens you currently holding)
you can verify here https://t.co/f0dCQr6dru

[xRoot @xrootdev]

@solana_devs And for the non-technical folks, I built a simple way to do this too.
https://t.co/f0dCQr6dru

[xRoot @xrootdev]

Friendly reminder: Solana v1 transactions are coming soon. Make sure your stack is ready.

[xRoot @xrootdev]

If you're building on Solana, transaction v1 is a breaking change you should prepare for.

Solana is moving from 1,232 → 4,096 bytes per transaction.

The bigger change isn't the size.

It's the new transaction format — and what it means for code that reads, indexes, streams, or analyzes transactions.

🧵

[xRoot @xrootdev]

@codefun_xyz On point 👌

[xRoot @xrootdev]

A regulated fund token and a honeypot can have the exact same on-chain shape.

Token-2022.
Default-frozen accounts.
Active freeze authority.

Every scanner I tested sees “honeypot”.

One is a regulated French fund.

So how do you tell them apart? 🧵

[xRoot @xrootdev]

One important warning:

Token ACL proves the freeze mechanism — not that the token is safe.

The issuer may still have powers like pause, permanent delegate, or burn.

For a regulated fund, that can be the product.
For an anonymous team, it is still a red flag.

I shipped this check in xroot’s free audit.

Audit: https://t.co/Cqg86JnqeC
Breakdown: https://t.co/hBgXk47Q7V

[xRoot @xrootdev]

The check I use:

1. Is the mint default-frozen?
2. Who owns the freeze-authority account?
→ It should be the Token ACL program.
3. What gate does the metadata declare?

Structure without the claim can still be verifiably permissioned.

A claim without the structure? 🚩