SOLUSDT
Solana / Tether USD
crypto Composite

Pouring one out for you brotha. Your token burn will be legendary when 1 SOL = $500.

It's a classic SPL token account with mint authority revoked since it was created on stonkfun. Not even the token creator can withdraw it since it's revoked. If it wasnt revoked they might have been able to withdraw excess lamports from the new solana upgrade, but yeah. Sorry mate. You're SOL (shitoutaluck)

A fully on-chain perp DEX with cross-margin sounds pretty interesting 👀 But the real test is gonna be during some absolute SOL candle from hell 😂 That's when you find out whether the execution and oracle setup actually holds up.

I know how this sub feels about presales, and most of the time that skepticism is earned. The usual playbook is VCs in at a discount, retail buys the listing, the unlocks hit, and retail ends up as the exit liquidity.

The launches that have actually worked out for regular people flip that. The network needs liquidity before it goes live, so it pays the users who bring it. I've had good luck with these, like what I've shared about Katana or some of the opportunities on Turtle. The hard part is catching them early, so I share them when I find one I believe in.

Reps from the Wire team reached out and asked me to check out what they're building. After digging in, I think it's a great opportunity for folks, and I'm excited to see the network get off the ground.

Three things separate this from the presales this sub usually roasts.

First, you keep a claim on your assets. You stake ETH or SOL through Wire's Ethereum or Solana Outposts and get liqETH or liqSOL back. The staking rewards go into Wire's liquidity, & you earn pre-launch $WIRE instead. Basically you're buying WIRE with your yield, not your principal.

Second, the money stays in the network. 100% of LCO proceeds go to protocol-owned liquidity and 0% go to the company. Wire has investors like any project, but none of this money goes to them or the team, and liquidity the protocol owns can't pack up and leave after launch the way rented TVL does.

Third, you know what you're getting. Pre-tokens convert 1:1 into $WIRE once the network hits its launch threshold, & if you'd rather just buy, the price steps up through tranches, so earlier is cheaper. There are no mystery points that get priced at the airdrop (blast, bera, sonic all gave a terrible user experience with their points).

As for the product, Wire is building a Universal Transaction Layer so apps and assets work across chains without bridges, for people and AI agents. Bridges have been behind some of the biggest hacks in crypto, so I'm all for anything that gets us off them. It runs on Ethereum and Solana, so if you hold either one, you can participate.

Mainnet is targeted for later in 2026. I'm participating myself and hoping for a nice cook here.

DYOR & NFA, this is based on what the team shared with me & my own research. Eligibility and details are on the official hub: hub\[.\]wire\[.\]network

**Source:** [https://x.com/solana\_devs/status/2105586569264706021](https://x.com/solana_devs/status/2105586569264706021)
https://preview.redd.it/zvtsfk3uevsh1.png?width=680&format=png&auto=webp&s=dc992d3bc6be32b785eadae66822e2ff694c67be
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](https://x.com/solana_devs) and [@readylayerone](https://x.com/@readylayerone) and turn on notifications.
# Releases
Notable feature gates
Devnet - [Alpenglow](https://explorer.solana.com/address/A1pengvuM6JEcyNuTnMqepBKhwHE3N6PmUrdATGawhJS?cluster=devnet)
**New versions**
* Agave [v4.4.0-beta.0](https://github.com/anza-xyz/agave/releases/tag/v4.4.0-beta.0)
* Firedancer [Mainnet Release v26.09.5](https://github.com/firedancer-io/firedancer/releases/tag/v26.09.5)
* Superbank [v0.7.1-rc2](https://github.com/solana-rpc/superbank/releases/tag/v0.7.1-rc2) , [v0.7.0](https://github.com/solana-rpc/superbank/releases/tag/v0.7.0)
* Web3.js [v3.0.0-rc.1](https://github.com/solana-foundation/solana-web3.js/releases/tag/v3.0.0-rc.1)
* Kit [v8.4.0](https://github.com/anza-xyz/kit/releases/tag/v8.4.0)
* Stake Program [Rust SDK v5.1.0](https://github.com/solana-program/stake/releases/tag/interface%40v5.1.0)
* Memo Program [Legacy JS SDK v0.3.1](https://github.com/solana-program/memo/releases/tag/js-legacy%40v0.3.1)
* Token 2022 Program [Legacy JS SDK v11.1.0](https://github.com/solana-program/token-2022/releases/tag/program%40v11.1.0)
* LiteSVM [v0.17.0](https://github.com/LiteSVM/litesvm/releases/tag/v0.17.0)
# Ecosystem work
SIMDs
* A discussion was started to modify the Application Binary Interface (ABI) v1 to [use registers r3-r5 as the place to load instruction pointers and metadata](https://github.com/solana-foundation/solana-improvement-documents/discussions/672) WTM (what this means) - An ABI defines where crucial data sits in memory as instructions within your transaction are being processed. The discussion is about using three reserved places in memory (the registers in the proposal) to store crucial data about the size of the instruction accounts and data and where they are located. Doing this allows for programs to do lookups instead of copying data from memory region to memory region, which is the much slower way the runtime does this today.
* A proposal was made to make CPIs on the runtime [saner and more performant](https://github.com/solana-foundation/solana-improvement-documents/pull/670) WTM - Calling other programs on Solana requires a syscall (a specified operation on the runtime with a well-defined behavior and cost) that stores redundant account information in memory and transforms that information only to be transformed back again during processing. The change proposed here removes both the unnecessary transformation step and the duplicated memory allowing for runtime and space allocated to run an instruction.
* An [additional data field in the Vote Account for commission history](https://github.com/solana-foundation/solana-improvement-documents/pull/677) was proposed WTM - Vote Accounts serve as the identity of validator nodes that support the network and contain information about stake, rewards and commissions. Changes will be made during Alpenglow that replace some of this information for the current epoch. This proposal restores that information in the Vote Account.
* Adding [location information to the Vote Account](https://github.com/solana-foundation/solana-improvement-documents/pull/674) and [making the leader schedule take geography into account](https://github.com/solana-foundation/solana-improvement-documents/pull/675) during assignment was proposed WTM - The Leader Schedule defines when each validator node gets to build blocks during an epoch. This is usually determined randomly and the more stake a validator has, the more slots in an epoch it gets allocated to be leader and thus receive rewards. The benefit of making the leader schedule geographically-aware would be that users of the network have a greater chance of sending their transactions to a leader closer to that part of the world. See this visualization by [@TheWattenhofer](https://x.com/@TheWattenhofer) to see how leaders span the globe more broadly once this proposal is implemented:
[https://x.com/solana\_devs/status/2105586569264706021](https://x.com/solana_devs/status/2105586569264706021)
https://preview.redd.it/j3phedv2fvsh1.png?width=556&format=png&auto=webp&s=2e8cc3ce22b67bb0084ba4483041ef8c2a51ba2e
Validator clients (Agave, Firedancer, Mithril)
* Agave plans to [expose the Alpenglow rank map](https://github.com/anza-xyz/agave/pull/15654) in its RPC methods API WTM - The RPC API allows validator operators to peer into the state of the network while operating. This change allows validator operators to serve the read layer (streaming service meant to push events to subscribers) giving them updates on the votes from vote accounts with a given certificate. Vote transactions are being removed from transactions and so votes by individual validators need to be parsed out from the certificates that are onchain.
* [Improvements to shred ingest latency](https://github.com/anza-xyz/agave/pull/15638) are being worked out in Agave WTM - The change described prioritizes shred ingest (receiving block data from the leader) over shred repair (requesting missing or broken block data from other validators). This approach gives more space for blocks to be received by non-leader nodes so that repair becomes more of a last resort.
* Contention on replay hashing and verifying [is being reduced](https://github.com/anza-xyz/agave/pull/15656) in Agave WTM - This change, like in the previous Changelog, is a more judicious use of the jemalloc arenas to allocate memory for easier use again for threads. In this case, it’s for the handoff between the hash and verification threads within the the replay service.
* More work to replace rayon with [custom threadpooling](https://github.com/anza-xyz/agave/pull/15585) is being implemented in Agave’s retransmit service WTM - Rayon is an off-the-shelf Rust crate that allows developers to create worker thread pools. Agave has found this to use more memory and compute than is actually required. A work-stealing pattern where jobs are placed in a queue and threads pick the jobs up on their own was used in other places of the Agave stack and is being used as a performance improvement in the Retransmit service as well.
* Agave is [improving its slot repair service](https://github.com/anza-xyz/agave/pull/14761) WTM - Repair is responsible for requesting missing shreds for a block from other validators in order to complete its own block for replaying and voting. This change is a simple optimization that skips attempting repair on slots whose shreds are already full (i.e. no shreds are missing). This is a relatively low-hanging optimization since it is work that no longer needs to be done.
* Airdrop on the Solana CLI will [link to the Solana web faucet](https://github.com/anza-xyz/agave/pull/15532) WTM - Airdrops are no longer supported on the Solana CLI and are only done today through the [faucet.solana.com](http://faucet.solana.com/) website. This change communicates this to users so that receiving test SOL on Testnet and Devnet becomes understood much more easily.
**RPC 2.0**
* Superbank is preparing its [Alpenglow implementation](https://github.com/solana-rpc/superbank/pull/99) WTM - An RPC is also an interface to validator stake and vote information. This change prepares Superbank as part of the RPC/read layer to serve requests to users related to Alpenglow primitives.
**Solana language clients (Web3.js, Solana Kit, Kit plugins, Solana SDK, Codama, Solana Go)**
* [Seed length validation for PDA derivation](https://github.com/anza-xyz/solana-sdk/pull/971) is being added to the Solana Rust SDK WTM - Seeds serve as inputs to derive a program account address used to hold program state, etc. This change allows for additional checks before seeds are added as input to a helper function that derives a corresponding address.
**Solana Program Library (SPL) and Core BPF**
* The ed25519-programmatic-signer program will [use V1 transactions exclusively](https://github.com/solana-program/ed25519-programmatic-signer/pull/60) WTM - Since the programmatic signer programs use a lot more cryptography, they will require a lot more transaction bytes to store the operations and execute. Using V1 transactions gives them the right space by default.
Solana program frameworks (Anchor, Pinocchio, Steel, Quasar)
* Caravel is [adding token program CPIs helper instructions](https://github.com/joeymeere/caravel/pull/23) WTM - Token Program helpers are standard in every program framework implementation. Caravel supporting these would make it more in line with other program frameworks like Anchor.
# Other interesting things
* [@accretion\_xyz](https://x.com/@accretion_xyz) wrote an essay about bugs program devs miss when upgrading their state accounts
[https://x.com/accretion\_xyz/status/2105338273216221416](https://x.com/accretion_xyz/status/2105338273216221416)
https://preview.redd.it/mgj6h1g7fvsh1.png?width=559&format=png&auto=webp&s=c4d6867b4d8682219be04592c67dc16219d581ba
* [@SteveCleanBrook](https://x.com/@SteveCleanBrook) hosted a Pirates Parley episode with the CEO of [@asymmetric\_re](https://x.com/@asymmetric_re), [@claudijd](https://x.com/@claudijd)
[https://x.com/SteveCleanBrook/status/2105559469375520853](https://x.com/SteveCleanBrook/status/2105559469375520853)
https://preview.redd.it/vyjnu8wafvsh1.png?width=561&format=png&auto=webp&s=af9080460d5c3ccc017c9ef35ed603b223afbe97
* [@TheWatterhoffer](https://x.com/@TheWatterhoffer) published an article about efforts to reduce latency by switching to Alpenglow
[https://x.com/TheWattenhofer/status/2105295508377944454](https://x.com/TheWattenhofer/status/2105295508377944454)
https://preview.redd.it/5p9msleffvsh1.png?width=554&format=png&auto=webp&s=77cdde841ce0917a53d21a40cbf65aa48a7b0993
* [@SolanaFnDn](https://x.com/@SolanaFnDn) and [@anza\_xyz](https://x.com/@anza_xyz) released a whiteboard session explaining how Alpenglow works
[https://x.com/solana\_devs/status/2104577640334278826](https://x.com/solana_devs/status/2104577640334278826)
https://preview.redd.it/ew51megifvsh1.png?width=561&format=png&auto=webp&s=f1f17c6278e24816cc461693dff10cecf9e045a9
* [@clairefxyz](https://x.com/@clairefxyz) published an article on her efforts to optimize compilation using error handling in p-token as an example
[https://x.com/clairefxyz/status/2104220602227655014](https://x.com/clairefxyz/status/2104220602227655014)
https://preview.redd.it/aza8cikkfvsh1.png?width=563&format=png&auto=webp&s=3eec4d7845926d3a6be8eabb53cc77e8fc0d8289
* A new wallet CLI app was open sourced on Github [https://github.com/ax-x2/solx](https://github.com/ax-x2/solx)
https://preview.redd.it/ahpw78dmfvsh1.png?width=680&format=png&auto=webp&s=7bd6486c52146e4b0e9d2b5a1724078db3c89835
* [@0xnaga](https://x.com/@0xnaga) launched a site talking about MEV strategies on Solana
[https://x.com/0xnaga/status/2103126095885390299](https://x.com/0xnaga/status/2103126095885390299)
https://preview.redd.it/uow3datpfvsh1.png?width=559&format=png&auto=webp&s=f66cda54852fc7d222d7d6c5efc735868cb541f1

Nice portfolio. I would move LTC position to SOL. Staking much higher and i just dont know how much growth there is LTC. Thats just my opinion, nothing wrong with your setup if you keep LTC. Keep going, you are doing great

I’ve been trying to get to 100 as well, been stuck at 55 due to having to pay bills but soon I’ll be able to keep stacking BTC and SOL. My only two positions

Don't accept random DMs offering to “activate” or “unlock” the wallet.
Your USDC isn't stuck permanently — you just need a tiny amount of native SOL for transaction fees.
The cleanest option is usually to buy/withdraw the minimum SOL your existing exchange allows to the **same Solana address** holding the USDC.
Double-check that the withdrawal network says Solana before sending it.
Once the SOL arrives, you should have enough gas to move the USDC normally.

openai just released their 6.1 SOL, supposed to be better than opus, i'm very stoked

SOL, TAO, ZEC, NEAR, ENA, HYPE, and CC. Trust me bro……

I don’t think BTC, ETH will pump that much even through EOY but I think SOL and smaller utility alts will in a few weeks and continue through EOY. Not to say BTC, ETH won’t but it will be the lower side of all expectations…I think others will be mid to high expectations

Most of my SOL sits on a Keystone, and I barely touch it. But since I don't want the friction of pulling it up every time I make a small transaction, I keep some crypto balance in a separate hot wallet.
Right now I connect the hardware wallet through the extension, so keys stay offline, and I approve on the device. It is best for security, but the flow is a bit annoying. You would know if you hate scanning QR codes multiple times for every transaction. 😢
Because of this friction, I've caught myself skipping my hot wallet paired with Keystone for some trades. I think this defeats the security practice I bought it for.
I want to know what your wallet setup looks like if you are moving large amounts. Is everything behind a hardware wallet, or do you keep a small balance in hot wallets and accept the security risk?
Also, which browser wallet extensions have worked well with Keystone? I'm using Jupiter right now, and it's working fine. But I've only tried two hot wallets so far.

Lapsecoin: fun new project.
Just stacking. I’ve stacked quite a few of little ones actually. Some listed, some not. But I need a much larger amount of belief to actually buy. Some I’ve bought: BTC, XLM, ETH, SOL

I would drop:
SUI - still got a lot of dilution ahead.
Quant - sell the current pump I don't think it will last.
Cronos - I don't like exchange related coins and it also has a dilution problem.
Would replace them with BTC, SOL, and XLM

Thx but no more SOL for me I will only accumulate BTC from here

Next milestone: 1000 SOL, very happy for you anon

That's huge!

This post made me curious so I pulled some number using AI and the SOL ETF numbers are looking good ngl:
* **Lifetime cumulative net inflows** are about **$1.62–$1.63 billion**.
* **Total AUM** is about **$1.94 billion** (\~2.8% of SOL’s market cap).
* **Bitwise BSOL** still dominates. It took most of September’s money, including \~$128M of the $188M record week and the $5.75M buy on Sep 29.
* A trailing **30-day** total around Sep 29 was reported at **$278M**, which includes some late-August sessions.

JUST IN: Bitwise ETF clients buy $5.75 million worth of SOL

Where u stakin SOL?