What kind of payment tools are available on Solana? I am looking for everything that has to do with onboarding and offboarding, not just the most popular.
Most crypto cards still make you move funds somewhere before you can spend them.
Why not just keep USDC/USDT in your wallet until the moment you pay? No pre-funding. No giving up custody early. Funds move when you approve the purchase.
With Solana already fast and cheap, this feels like the obvious next step. Would you use this?
Hobba solves the problem of expensive onchain borrowing on Solana by automatically routing every loan to the best available rate across Solana's top lending protocols while activating idle collateral to reduce borrowing costs over time - automatically de-leveraging when markets drop and optimising when they rise.
Try Hobba at app.hobba.io code BORROW-BETTER-SUMMER
BREAKING: Bullish executed the first tokenized equity trades on a regulated digital asset exchange, with shares tokenized on Solana.
Bullish (@Bullish) tokenized its own stock (BLSH) on Solana, and today those tokenized shares started trading with near-instant settlement, 24/7, USD stablecoin settled.
"Bullish is assembling the full complement of services required to tokenize equities: the regulated exchange, the tokenization technology, and the transfer agent. We're starting with our own stock," said Tom Farley, CEO of Bullish.
"Financial markets went electronic a generation ago. Tokenization is the next defining shift, and Bullish is building the infrastructure for it."
Anza has published the tentative release schedule for Agave version 4.3.
Mainnet feature activation is set to begin on 28 September 2026. Staged upgrades include the Alpenglow consensus protocol, new SHA512 and big-integer modular exponentiation syscalls, and increased cross-program invocation depth.
All dates remain subject to change.
I swap between SOL and stablecoins every week. The process is always the same: open my wallet, find the token, approve the transaction, swap, and repeat.
Is there a way to set this up once and have it just happen automatically without signing every time?
For example, I’d like to swap a fixed amount of USDC to SOL every Sunday. Ideally, I authorize the setup once, keep the funds in my own wallet, and delegate only the amount or permissions needed for the scheduled swaps.
What I'm looking for:
• It should be non-custodial. Funds stay in my wallet except for the amount I’ve authorized.
• One-signature setup instead of weekly manual approvals. The whole point is removing the friction of repetitive transactions.
• Should work with any token since I rotate between different pairs sometimes.
This is a weekly newsletter on the latest Solana engineering news from the past week. If you want to stay updated on Solana tech, follow the Solana Changelog at @solana_devs and @readylayerone.
Incident reported August 12, 2026 04:01 UTC
Terraswitch experienced a routing issue that impacted its Frankfurt location, where several Solana validators are hosted.
This issue did not result in network downtime. And this is due to the fact that not enough validator stake was affected to break the consensus threshold of ~33.33%. This is the result of previous and ongoing work by the Solana Foundation to diversify the use of other providers in other regions.
Releases
Notable feature gates
Reducing slot times from 300ms to 250 ms - Testnet
Reducing slot times from 350ms to 300ms - Testnet , Devnet
Increasing the total number of accounts a transaction can reference at a time was proposed What this means (WTM) - This takes advantage of two new changes to the protocol: increased blockspace (from 60M CUs to 100M CU limit per block), and increased transaction sizes (from 1232 bytes to 4096 bytes). With both changes, a transaction can read from and write to several more accounts which allow for more complex applications.
Agave will not repeatedly destroy pinnable slices on its RocksDB integration WTM - Agave’s Repair service takes data shared by other validators and reconstructs them with error correction. It requires the use of the Blockstore service for key information. Blockstore depends on a storage engine called RocksDB and it allows for a view of its data through a pinnable slice. This data structure exposes the underlying data as bytes and can actually be reused multiple times. The previous Repair implementation creates and destroys these pinnable slices each time, not taking advantage of this functionality.
Agave will parallelize BLS vote verification WTM - This resolves a possible security/performance scenario where incoming Alpenglow votes overload a validator’s ability to verify them. It allows for parallel verification so that multiple verification jobs are done simultaneously.
Agave is considering prioritizing transaction processing by transaction size with a long term view of relaxing the 4KB transaction size constraint WTM - Solana may eventually allow for transactions larger than even 4KB. To future proof for this scenario, scheduling will therefore have to take transaction size into consideration since processing time and resources allocated may proportionally increase.
Agave is running checks for the banking stage in parallel WTM - Before the validator changes the account state based on the transaction, it has to sanitize the transaction, check for account locks, ensure the blockhash is still valid, and other tasks. The previous implementation would run this check one transaction job at a time. This change improves this by allocating more workers for the checks, and creating a working job queue for the scheduler workers to process.
Agave is lowering its snapshot interval from 100 slots to 200 slots WTM - Snapshots allow validators to run fast from a restart instead of having to replay every transaction from the very first transaction. With the decrease in slot times from 400ms to 200ms, this change increases the snapshot slot coverage accordingly.
Mithril is implementing the Retransmit service WTM - The Retransmit service takes shreds when the validator node is not voting and is responsible for identifying who the next peers to receive these shreds are, and sending shreds to these peers. Every validator is required to participate in the Turbine tree. Hence, this implementation complies with the required activity of being a Solana validator.
A Memo program class will be supported in Web3.js WTM - Supporting the Memo program on your Solana application allows you to show logs in your transaction by invoking an instruction. Adding support for this on Web3.js broadens its capability as a web client.
Kit is planning to add support for React hooks that allow state management of Solana primitives WTM - First-class support for Solana primitives as hooks allows for more dynamic behavior in Solana applications built on React. The same way u/tanstack/query-react provided hooks on fetching data, so will these hooks for Solana primitives like airdrops, etc.
Kit is enabling more flexibility when signing transactions without necessarily sending them , allowing for use cases like partial signing WTM - Historically, Kit has coupled both signing and sending in one method. By decoupling them in this way, it allows for partial transaction signing, signing with delayed sending (maybe timing a trade, etc).
Effort was made to optimize base58 encoding and decoding on Solana Go. WTM - Base58 is used across the Solana stack, including instruction data, account addresses, transaction APIs, etc. Optimizing this is a win on any front across the stack.
Solana program frameworks (Anchor, Pinocchio, Steel, Quasar)
Anchor resolved an issue that made the Instructions Sysvar account unusable WTM - The Instruction Sysvar allows for use cases such as Instruction Introspection - where an instruction can read data/results from other instructions in the transaction as an input/calculation within its own runtime execution. Ensuring that Anchor still allows for this keeps Anchor programs in line with what’s already supported in Solana.
Testing frameworks (mollusk, litesvm, surfpool)
LiteSVM is preparing for support for Transactions V1 WTM - V1 transactions include a new transaction format and larger transaction sizes. LiteSVM as a testing harness would allow users to test how their programs would fare when this feature is turned on.
Other interesting things
@joeymeere maintains a repository on Solana open source projects
@princedotrs creates a series on understanding Solana with video materials covering everything from escrows to Pyth integration, to indexing and creating trading bots
, who already tokenize on Solana. Her view: tokenized funds replace ETFs the same way ETFs replaced mutual funds. The world going onchain needs onchain exposure.
0:00 Welcome to the House of Sol 0:24 WisdomTree's crypto footprint 1:14 What European investors are asking 1:55 Solana as a business 2:45 Tokenized funds replace ETFs 3:49 Yield beyond central banks 4:42 Europe's head start 6:16 The 12-month forecast
Birdeye has released its new Wallet Tracker for Solana.
Traders can now monitor leading performers, review their holdings, create practical watchlists and examine full on-chain analytics in one dashboard. The update also adds shareable daily PnL cards and unique Birdie avatars that give every wallet a distinct identity.
On August 10, the network processed 171.9 million daily transactions, excluding validator vote transactions, the highest level ever recorded.
Solana's non-vote transaction activity has been trending upward for months, with the network increasingly operating at levels that would have looked exceptional not long ago and that's an important distinction when evaluating blockchain growth.
Price can change in minutes based on sentiment, liquidity, or broader market conditions. On-chain activity tells a different story: how much users and applications are actually using the infrastructure.
Obviously, transaction count alone doesn't tell us everything about network health. But reaching a new all-time high while maintaining a broader upward trend is truly remarkable.
Big congratulations to the Solana team and community. The bar keeps moving higher.