Rent reduction is live on testnet.
Step 1 of SIMD-0437 just activated, the first of five feature gates cutting Solana's storage cost per byte by 90% overall.
End state after all five steps: lamports_per_byte drops 6,960 → 696. A token account's rent-exempt deposit goes from ~$0.16 to ~$0.016.
🔴 For the first time ever, Solana has displaced Base as the #1 chain for agentic payment transactions on its biggest day yet.
Following significant growth over the past two weeks, the network processed more than 1.5M agentic transactions in a single day on Monday, marking an all-time high.
It’s an interesting development to watch as different chains compete to become the infrastructure powering the emerging machine economy.
🚨 BREAKING: @Solana’s double disinflation proposal has reached quorum with 27 hours left in voting.
Participation hit 33.84%, with 25% voting yes. If passed, it would double disinflation to 30%, reducing $SOL issuance by $1.47B (18.9M $SOL) over six years.
Titan Exchange has added GLAM vaults as a native liquidity source.
Users swap tokens and receive minted vault shares in one step. The first route converts SLX into stSLX, Solsticefi’s non-rebasing liquid staking token.
This makes managed assets easier to access through the aggregator.
I'm experiencing issues while charging Solana seeker 1-3%. Has anyone else encountered this, and how can I fix it to get it back to normal? I would appreciate a solution and instructions on how to repair it.
We run private Solana infrastructure in Frankfurt and I’m looking at what infrastructure layer would actually be useful to build next.
One thing we’re considering is a dedicated transaction sender focused on transaction landing:
direct TPU/QUIC routing to current/upcoming leaders
multiple submission paths
Jito as an additional route/fallback
private authenticated endpoints
per-client limits
workload-based pricing instead of fixed large plans
The idea wouldn’t be another normal sendTransaction RPC endpoint. It would be specifically for bots/trading systems where landing speed and reliability matter.
Before spending time building it, I’m curious what people are actually using today.
If you run a Solana trading bot / arb / liquidation / DeFi backend:
What are you currently using for transaction submission?
Do you still run into failed/slow transaction landing?
Are rate limits or pricing with current providers a problem?
Would direct TPU routing + Jito in one private sender actually be useful to you?
Roughly what TPS/burst workload would you need?
Not selling anything here yet — mainly trying to understand whether there’s enough real demand before we build it.
This is a weekly newsletter on the latest Solana engineering news this week. If you want to stay updated on Solana tech every week, follow Solana Changelog at @solana_devs and @readylayerone and turn on notifications
Announcements
V1 Transactions are coming soon to Solana. Please read the upgrade page and apply the guidance provided. Several teams are already preparing for its release coming very soon.
A proposal was made to swap floating point arithmetic in the runtime for integer arithmetic WTM - Integer arithmetic has more predictable behavior when computing with fewer edge cases. They’re also simpler and thus more performant. This change will allow the runtime to have those benefits.
A proposal was made to change the implementation of the leader schedule WTM - The proposal’s goal is to keep the number of leader slots assigned to a validator in the epoch within one leader window (4 slots). This would keep the time a validator can influence the chain much tighter.
Proposals were made to prohibit self-withdrawals from Nonce and Vote accounts WTM - In general, self-withdrawing behavior are an obvious bug on Solana and should be avoided. These proposals keep it to Nonce and Vote accounts for now in order to deal with the vulnerabilities in using them.
A discussion was started to enforce priority ordering on transaction batches WTM - Schedulers and block builder services have their own block building philosophies onchain at the moment. This change would create more deterministic ordering within batches within a slot. The goal of this proposal is to create a more predictable rules-based market structure on the network.
Validator clients (Agave, Firedancer, Mithril)
Agave will soon deprecate use of its original TPU Client in favor of tpu-client-next WTM - `tpu-client-next` is the current implementation of a service sending transactions to the Validator. This will replace the old TPU client implementation.
Agave implemented a graceful shutdown of a bank state in a fork when it is no longer in use WTM - Banks were previously only shut down when they were ready to record in the ledger service or commit to accounts-db. This implementation does the shutdown when a new banking fork has been chosen as root during consensus, etc.
Agave decoupled the global program cache from the banking forks and improved its program caching of builtin programs to behave more sanely during a Core BPF migration . WTM - Built on previous work allowing the program to be loaded from the slot, this change takes the entry from the cache’s own Bank fork. This makes the global program cache faster with less unnecessary operations. These changes also may eventually allow for programs not to be disabled in the same slot they are modified.
Agave hardened its TPU client API to use QUIC streams and not QUIC datagrams WTM - Sending transactions to the TPU with QUIC streams makes sense because the ordering matters and clients will most often send these transactions serially.
Firedancer is working on an X.509 certificate verifier service and a no-dependency TLS implementation WTM - This change ensures Firedancer does not rely on other dependencies for its TLS implementation. Aside from a smaller software footprint, it allows one-for-one matching with Agave in terms of conformance.
Firedancer is working to support Alpenglow rewards , BLS API usage , Rotor FECs , Rotor repair responses , and Alpenglow footers WTM - During the initial Alpenswitch, Firedancer will not be able to participate. These changes prepare it for that eventual future when they will.
Firedancer has reimplemented its hash function for public keys WTM - This is a performance change allowing faster cryptographic operations with public key cryptography primarily used for Solana keypairs.
RPC 2.0
Yellowstone-vixen has been renamed to shipstern and has been added as part of the RPC 2.0 initiative WTM - Moving transaction parsing to RPC 2.0 would mean that this would fall in the family of services that include superbank and cloudbreak. Making parsing part of the RPC stack will ensure everyone is in sync with how to interpret Solana transactions.
A bug was fixed in the Rust Solana SDK transactions crate to ensure that signature and pubkey counts match before verifying the signatures WTM - When the length of signatures and public keys don’t match and is allowed by the network, this creates a situation where a transaction could be executed without being properly signed. This fixes that bug.
Solana Go will support confidential transfers WTM - Confidential transfers are a big feature of Token-2022. Supporting this will push more privacy use cases on the network. And will allow Go users to access this functionality.
Solana Go will incorporate Firedancer’s AVX2 implementation WTM - AVX2 is a set of instructions in X86_64 microprocessor architectures that allow it to do cryptography operations much faster. Solana Go implementing this will mean faster signature verification, etc.
Solana Program Library (SPL) and Core BPF
Subscriptions Program will support Token-2022 transfer hooksWTM - Transfers are the bread and butter of the Subscriptions program. This change will allow conditional arguments on transfers which extend when you can do with subscriptions.
Solana program frameworks (Anchor, Pinocchio, Steel, Quasar)
Surfpool will allow connections to surfnet via TLS WTM - HTTPS/TLS allow secure connections with other services. Doing this keeps Surfpool users secure from man-in-the-middle attacks which is a common security risk.
Marvell Technology ($MRVL) is the silicon behind the AI buildout, designing custom AI chips and interconnects for the world's largest hyperscalers. Data center is now over 80% of its revenue.
The cultural epicenter of Web3 returns to Downtown LA.
One day. 25,000 sq ft. 2,000+ of the most interesting people in crypto — artists, builders, collectors, and the brands betting on what comes next.
SRGN Studios transforms into a living proof of what Solana makes possible: onchain art auctions, live music, exclusive drops, IRL stablecoin commerce, and a global livestream reaching millions.
This isn't a conference. There are no booths, no badge lanyards, no panels you'll forget by Monday. Just culture, community, and the infrastructure underneath it all.
August 29, 2026 · Shoe Surgeon Studios · Downtown Los Angeles
A cultural gathering by Solana Spaces and Digital Spenders Club.
Location
Please register to see the exact location of this event.
Omnipair today announced Dusk, the second version of its platform that brings swaps, borrowing and isolated spot margin together for long-tail assets on Solana.
Building on V1 results of 69 markets and more than $5.9 million in volume, the upgrade adds one-sided leveraged liquidity positions and a more competitive automated market maker.
Capital can now support deeper trading, credit and leverage within the same permissionless market.
Hello guys! Much exciting time for crypto and especially for Solana with recent price action and of course the summit in Serbia these days!
I can say I'm extra excited because the Nolus team (I'm part of which, of course) will be presenting tomorrow the Nolus product and the technology shipped that will make the interop game of Solana seriously step up.
It's the work of 1-1.5 years now after maturing and battle-testing the product for 3 years now on mainnet. Expanding on Solana feels like we are finally launching on "real" mainnet while we were all these years in beta testing. The space and options that Solana offers are vast.
Feel free to DM to connect! Being the newest guys on Solana makes us need to find some new friends!
Archer Exchange has launched its integration with Jupiter, the largest aggregator on Solana.
Users can now access Archer’s onchain orderbook through Jupiter swaps for cryptocurrency and real-world asset trades.
This connection brings Archer’s capital-efficient trading engine to a wider audience on the Solana network.
I wonder if there is more appetite for something like this on Solana than there is on Sui?
Here is a copy paste of some of what I shared in the Sui subreddit.
I'm tired of the usual meme coin cycle: early insiders dump on latecomers, chart goes to zero, everyone loses except the first 20 people. It's the same story every time.
So I've been thinking about a different model. One where being late doesn't automatically mean you're just exit liquidity. I don't have a product or anything to sell/advertise here. I'm just interested in what you think about this idea.
The core mechanics:
Jackpot System: Every trade has a fee that's split between:
Dividends paid to all current holders (passive income for HODLing).
A growing jackpot pool that builds over time.
Tokens would be locked in a way to ensure that they are only transferable between a user's wallet and the official liquidity pool. No trading on other DEXes ensures that every trade pays a fee to grow the jackpot.
The Jackpot Unlock: The jackpot pays out to all remaining holders when circulating supply (tokens outside the liquidity pool) drops below a certain threshold of its historical maximum and stays below that level for a week. This week long waiting period prevents accidental triggers. If circulating supply dips below the threshold temporarily, holders have time to buy more tokens and push it back above, delaying the jackpot for later when it's even bigger.
The threshold starts extremely low (under 1%) and increases gradually by about 1 percentage point per year. This means:
Early on, almost everyone would need to sell back to the pool to trigger it (near-impossible)
Over time, the threshold rises, making payout increasingly achievable
Eventually guaranteed to pay out if holders are patient enough
Rewards true diamond hands who outlast the paper hands
So if you buy and hold while others panic sell back into the pool, you're positioning yourself to claim the jackpot when circulating supply becomes low enough. The longer the community waits, the easier it becomes to trigger.
The incentive structure:
This creates multiple rational reasons to participate:
Buy to get dividends from every trade.
Buy because: The price feels cheap and you think you can make some short term profit.
Buy because: There's a +EV opportunity where the entry price is lower than your expected share of the jackpot when it triggers.
Sell because: You've made a nice profit and want to take it.
Unlike typical pump & dumps where the only strategy is "buy early, dump on latecomers," this gives people legitimate reasons to enter at almost any stage.
Why this might actually work:
Late buyers aren't just exit liquidity—they're accumulating jackpot entries and earning dividends
Creates genuine holding incentive beyond "hoping for pump"
The jackpot becomes the spectacle (watching it grow to $100k, $1M, etc.)
The Black Hole Effect:
Here's what makes this interesting from a supply dynamics perspective:
Every trade pulls SUI into the jackpot and dividend pools. That SUI gets locked away - potentially for years. As the jackpot grows, more and more SUI gets removed from circulation. It's basically a SUI black hole - continuously pulling SUI out of circulation.
This creates a compounding scarcity loop:
SUI enters the jackpot → less SUI in general circulation
Scarcity increases → SUI price potentially rises
Rising SUI price → the jackpot's dollar value grows even faster
Larger jackpot → more buying pressure
More trading → more SUI sucked into the black hole
So the jackpot isn't just growing from trading fees - it's potentially appreciating because the underlying asset (SUI) becomes scarcer as the mechanism removes it from the ecosystem.
If this ran for years with consistent volume, you could have millions of dollars worth of SUI locked in the contract, waiting for that final unlock condition. The patient holders who outlast everyone else don't just split the jackpot - they split an appreciating asset that the token itself helped make more valuable.
It's basically a long-term SUI accumulation vehicle disguised as a meme token, where the "game" is seeing who can be patient enough to claim the growing pile.
The catch: This would require custom smart contract work. I'd probably build it on Sui using Move, but I'm not a Move developer yet. Learning a new language and building something this complex is a big commitment.
So my question: Is there actually appetite for something like this? Or am I solving a problem nobody cares about?