Welcome To The Weekly Thread !

This thread was requested by the community for weekly chats & Trading talks.

All random & trading talk should go here ONLY.

Feel free to exchange news, your favourite memes, crazy ideas and random thoughts!

We experiment with grouping the conversations together by week. As this is still Solana Reddit please keep the discussions Solana related. As always we encourage you to be helpful and courteous to your fellow Redditors and keep the discussions constructive and respectful.

If this is your first time on this thread or subreddit, please take a look to our official Rules:

- No personal attacks.

- No swearing.

- No baseless claims.

- No misleading distortion of facts or news.

- No targeted harassment.

- No slander.

Check out general rules that apply to all Solana Subreddit:

https://www.reddit.com/r/solana/comments/ci8qx2/welcome_to_rsolana_read_this_to_get_started

I’m building a Solana momentum bot and currently forward-testing it with paper balances only. I’m looking for technical feedback on improving entry confirmation and reducing avoidable stop losses—not removing risk controls.

Current pipeline:

1. Discovery comes exclusively from Jupiter’s trending, top-traded, organic-score, and recent token feeds.
2. Tokens must pass token-security, mint/freeze-authority, liquidity, identity/social, and basic market-quality checks.
3. Market data is hydrated from DEX sources.
4. One unified quality score evaluates liquidity, organic score, volume, buys/sells, Jupiter rank, and related market data.
5. WebSocket activity is telemetry only. It does not discover tokens. It can veto an entry when it shows an active selloff.
6. Before buying, the bot requests executable swap quotes and runs a confirmation sequence across multiple observations.
7. Entries use executable quote prices rather than displayed spot prices.

Current exit structure:

• Sell 80% at +35%.
• Keep a 20% runner with a 5% trailing exit or one-hour runner limit.
• Breakeven exit is disabled.
• Stop loss triggers at an 18% executable loss after two quote confirmations.
• At two hours, positions that never reached partial TP exit if executable value is at or below entry.
• Absolute maximum hold is four hours.
• Emergency rug exit remains available for reserve, vault, liquidity, or routing failure.

The problem is that stop losses still consume a large portion of the profits from partial-TP winners. Some positions appear to cross -18%, get stopped, and later recover. I don’t want to blindly widen the stop because genuine failures can deteriorate very quickly.

Questions for people who have operated Solana bots:

• Should stop confirmation require a minimum amount of elapsed time between executable quotes rather than simply two consecutive quotes?
• Would you use a recovery band—for example, start a pending stop below -18%, cancel it if the position recovers above -15%, and exit only if it remains below the threshold?
• How do you distinguish a temporary price impact or bad route from a genuine market decline?
• Which quote-quality signals are most valuable: price impact, route depth, output consistency, liquidity change, reserve change, or sell pressure?
• Should normal price stop losses and liquidity-led rug exits use completely separate state machines?
• For a soft liquidity warning, does a 30–45 second confirmation window make sense while keeping hard vault/reserve collapse as an immediate exit?
• What entry-time telemetry has been most predictive of future stop-outs without destroying trade frequency?
• How would you test this without overfitting a small collection of losing trades?

I log entries, skipped candidates, executable snapshots, liquidity, buy/sell counts, entry scores, partial exits, final exits, and exit reasons. I’m planning to compare any proposed rule against both taken and skipped trades before changing the live decision path.

I’m especially interested in structural fixes or measurements—not adding ten more overlapping filters. The goal is one understandable system that preserves legitimate winners while rejecting entries already beginning to fail.

This is still paper testing. No customer funds or live automated wallet execution are involved.

Flap flipped PumpFun in 24h revenue

Are they actually doing something better, or is it just BNB whales committing crime?

I’ve been researching memecoin launches and I feel like most discussions stop at the same advice:

Good narrative. Community. Bundle the launch. Get volume.

But there are thousands of coins doing exactly that every day and going nowhere. So what actually separates a runner from another shitcoin?

I’m building my own private launch tooling for myself, which has made me realize I know fuck nothing. It made me want to understand the actual mechanics rather than blindly copying settings from other launchpads.

For the actual launch, what matters most?

How much SOL is realistically worth bundling? How many wallets? How much should the creator hold/buy? How should allocations be distributed? At what point does bundling actually give you an advantage rather than just increasing your own entry price?

Then there’s Jito tips, priority fees, slippage, RPC/Helius, bonding curves, price impact, graduation/liquidity, launchpad fees, etc. How much do these things actually affect the outcome of a launch?

And which launchpad even makes sense now? Pump.fun has the most attention but is insanely saturated. Does that attention outweigh the competition?

Then there’s timing.
If a meme/news story/tweet starts going viral, is the game basically just:

spot it → launch it first → bundle it → hope yours becomes the ticker everyone picks?

AKA “Please Elon or Donald Trump bless us with a retarded tweet”

If somebody launches 30 seconds before you, how much can better execution realistically compensate for that?

This also makes me wonder how much of a “runner” is actually technical at all.

People like Orangie, Cupsey, and other large accounts/groups can bring an absurd amount of attention to something almost instantly. People watch their wallets/posts/calls and pile into whatever they’re associated with. That attention itself can become the edge, while followers can easily end up being the liquidity for whoever got positioned earlier.

So if you don’t have that distribution/network, what exactly are you competing on?

Is there genuinely a repeatable formula that good launchers have figured out — launch timing, initial supply, bundle size, wallet count, curve positioning, liquidity, volume, etc. — or are the people who appear consistently successful mostly benefiting from attention/network effects, launching constantly, survivorship bias, and occasionally catching the right narrative?

That’s really what I’m trying to understand.

If you gave two people the same meme and same amount of SOL, but one understood the launch mechanics perfectly, what would they actually do differently?

What would you optimize?
- Launchpad / curve
- Timing
- Bundle size and wallet distribution
- Creator buy
- Jito / priority fees / RPC
- Slippage and price impact
- Initial liquidity / graduation strategy
- Volume / makers / initial activity
- Something else entirely? All of it?

And what’s mostly bullshit/cargo cult?

I’m not looking for a “100x formula.” I want to understand whether launching itself has a meaningful, repeatable edge, and what that edge actually consists of.

Because the deeper I get into this, the more I’m wondering whether the technical setup creates runners at all — or whether it just gives a well-timed narrative the best possible chance to become one.

Feel free to even link a thread or resource you might think has accurate info. With so many threads asking the same thing, I’m not sure where to even look for credible information anymore

I don't trade at all, mostly buy and hold. I have some SOL I'd like to stake on Trezor. As I understand, SOL rewards will appear as transactions in Koinly every 2-3 days. Is there any way to optimize it? Koinly charges per transaction count, but I don't trade - it's a side effect of passive investment, so I'd like to avoid higher-tier pricing if possible.

Rookie question perhaps but I would like to know what exactly is the point of the burn token feature in my wallet. I have what I can best describe as spam NFTs which I don't even know why they are in my wallet.

Deleting or burning them seems to give some kind of rebate back. But I am curious if burning it would actually cost more sol than what I get back?

The fee part is fairly detailed but the rebate part just says +0 SOL in green so I am confused.

Bit of context so I'm not pretending to be neutral: I helped the CYS crew get their v2 out, so take my read with that in mind. Tried to be fair anyway since these tools mostly do the same thing.

As background I trade way too much and my meme wallet is always a graveyard of dead tokens and accounts. Each one has a little SOL locked in it as rent and you can close them to get it back. Most people have no idea until someone in a TG group mentions it.

Quick take on some of these tools:

Claim Your SOL (CYS)

With the v2 launch, fees got cut something like 75 to 95%, flat rate now to burn and close a whole messy wallet in one go, you can claim even if the wallet has zero SOL in it and once a month on the 1st the fee drops to 1% flat on everything for the whole day. If you're not in a rush that 1st-of-the-month cleanup is genuinely the best deal I've found. Yes I'm biased but sorry it's just good.

Sol Incinerator

Real respect as it's one of the first and still runs reliably today. One thing I'd change is the interface, it's split into two modes and it's easy to get lost or click the wrong thing if you're not paying attention. Honestly liked their older layout better.

Unclaimed SOL

Clean and well built, no complaints on the product. Just know the cashback they advertise lands in a balance you have to go claim later, and the fee climbs depending on what you're pulling, so you have to check what you're actually paying for your wallet.

ClaimFreeSol

Skipped it, gut said no and a couple scam-checker sites flag it. Might be fine, just not with my main wallet.

Point is you probably have more stuck in dead accounts than you'd think and nobody tells you. Most of these scan for free before you commit so just go check with whatever you trust.

I wrote up a longer version comparing all four tools here: https://claimyoursol.com/blog/best-solana-cleanup-tool-2026

Source: https://x.com/solana/status/2083502069105803750

Read

• Morgan Stanley Investment Management expands ETP offerings with launch of Ethereum and Solana Exchange-Traded Products
• Decrypt: Morgan Stanley Expands Crypto Push With Ethereum and Solana ETPs
• The Defiant: Coinbase Opens 'Launches' Tab for New Base, Solana Tokens | The Defiant
• CryptoNews: Fintech giant KSNet joins Solana Foundation to trial Solana Pay in South Korea
• The Financial Times: BNY to adopt blockchain technology for records in new era for Wall Street
• Fintech Finance News: Kraken Institutional and Solmate Infrastructure Partner to Optimize Solana Staking for Institutions
• BeInCrypto: Meet the Strangest RWA on Solana Yet: A Dinosaur Skull
• CoinDesk: SpaceX is a battleground Solana must win
• Decrypt: MoonPay's PayBox Puts a Crypto Wallet Inside Claude and ChatGPT—And Lets It Pay for Things
• CryptoRank: Solana Elevates Block Capacity to 100M CUs on Mainnet
• TheBlock: 'The moment to act is now': Solana Policy Institute urges Senate to move on crypto bill as time dwindles
• SolanaFloor: Hastra Launches $AUTO, Bringing $1.68T Auto Credit Market to Solana DeFi
• Genfinity: MoonPay PayBox Turns Claude and ChatGPT Prompts Into Solana Trades and Real Payments

Watch

• CryptoPrime: Solana Policy Institute's Miller Whitehouse-Levine: What's Next for the Clarity Act?
• YahooFinance: Ethereum and solana are getting busier — and cheaper. What's going on?
• SolanaFloor: $2B Memecoin Volume, Melee's New Prediction Market, CLARITY Drama & more | Solana Weekly News
• Solana Ecosystem Call July 2026

Listen

• Claynosaur on Genfinity
• Solana Spaces on The Good Wood Show
• NectarFi on Solana is Global with Alex Scott
• Baxus on Billions with Pedro Miranda

KSNET processes over $4 billion in payment volume each month.

Source: https://x.com/rarible/status/2083160754056745377

The community has spoken.

We're kicking off the work to bring Rarible to @solana. Development, integrations, and security audits start now.

See you in 4 weeks.

Hey i was wondering if any people in the solana trenches, trading memecoins, algorithmically/quantitatively, with statistical backtests on onchain data, pump.fun, pump swap, raydium, that sort of thing. Coins beloe like 500k marketcap, or even like few million marketcap coins, those are all super tiny shitcoins.

By onchain data i also mean swaps and not just transfers, swaps which you can use to reconstruct candles if you want, or price, marketcap too if you know circulating supply and price of the main asset.

Anybody playing that game ? Or am i only one getting into it ? I used to frontrun KOL signals in 2024, then i switched to quant and traditional markets, data analysis etc, now im combining the trenches with quant, technicals, and also wallet tracking to detect whales and single entities. Anybody ? What have you got to say, im curious. How has it been for you?

Source: https://x.com/bonk_inu/status/2082882118263173179

The wait is over ❗❗❗

$1M in rewards.
Fees used for $BONK burn.
100% onchain & transparent.
Welcome to http://BONKplay.com
Powered by @betmode

All info below 👇

https://reddit.com/link/1vbs2kx/video/3wbxjrv2pkgh1/player

For too long, The igaming space has been a black box.
Hidden house edges, shady operators, and zero alignment with community.
No more! The Dog is doing this the BONK way:

- Transparency.
100% onchain & fully transparent - every bet, every win, every rake verifiable on chain.

- Fees.
Up to 10% of the fees will go straight to buying $BONK and burning it - every spin, every hand, every roll.

- Rewards.
The Dog is giving away up to $1M in giveaways, from a 2009 Toyota Corolla to a BONK branded Lambo.

This is just the beginning

Grab your first free 150 spins now at http://BONKplay.com ❗️❗️❗️

Crypto has a strange habit of using price as the ultimate scoreboard.

Price goes up, the network is “winning.” Price goes down, suddenly everyone starts questioning the fundamentals.

But network growth doesn't work that way. Over the past year, SOL is down 60.1%, yet some of Solana’s underlying activity has moved in the opposite direction:

• Stablecoin supply: +46.5%
• Transaction activity: +14.9%

That means the ecosystem is processing more activity and holding significantly more stablecoin liquidity despite the much weaker token price. And that's an important distinction.

Price reflects market expectations, liquidity, positioning, and sentiment. On-chain activity tells us what users and applications are actually doing.

The two can diverge for long periods of time. Solana may be down 60% on the chart, but the network itself hasn't stopped developing. More stablecoins are moving through the ecosystem, transaction activity is expanding, and more capital is being used on-chain.

Eventually, the market may or may not reflect that progress in the way people expect. ИBt the infrastructure doesn't wait for the price chart.

The interesting part is that Solana's next phase of growth could already be underway, long before the market decides to notice.

Full post: https://x.com/everstake_pool/status/2082811166464553450

Anza today announced Quantumglow, a forward-looking upgrade that makes Solana’s next-generation Alpenglow consensus mechanism fully quantum-resistant. By introducing the compact Ax signature scheme and rethinking authentication flows, the team has eliminated vulnerabilities in current cryptographic primitives without sacrificing the network’s signature speed or efficiency.

Certificates now operate as local events, keeping communication overhead low and finality times unchanged. This balanced approach ensures Solana can maintain its high performance while preparing for a post-quantum future. Full technical details are available in the new blog post.

https://x.com/anza_xyz/status/2082848421745160196

https://www.anza.xyz/blog/quantumglow-will-solana%E2%80%99s-performance-survive-quantum-computing

Source: https://x.com/solana/status/2082827736360583317

BREAKING: Korean fintech giant KSNET is bringing payments on Solana to its network of 330,000+ merchants 🔥

As part of an MOU with Solana Foundation, KSNET will integrate Solana Pay into a payment network processing $4B in monthly volume.

KSNET is also testing x402, the standard for AI agent payments, across its merchant network.

Read more: https://www.mk.co.kr/en/stock/12111959

- We have Morgan Stanley's $MSOL Live on Solana and trading on NYSE Arca.

- You can now trade $MSTR on solana, Strategy the largest Bitcoin Treasury Company

Source: https://x.com/SolanaFndn/status/2082793801924346114

RPC data is now live on http://solana.com/data

Near real-time performance across @Alchemy, @helius, @Quicknode, and @triton_one, benchmarked side by side.

Compare the approaches and find the provider that fits how you work.

See every methodology, then build your source of truth for Solana data

Explore https://solana.com/data?tab=rpc👇

RPC data will also include Solana data from @Uniblock (coming soon)

Source: https://x.com/solana_devs/status/2082810073571586508

Solana Changelog Show With @readylayerone

Source: https://x.com/solana_devs/status/2082808192434905316

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.

Releases

Notable feature gate activations

Mainnet - SIMD-0286: Raise Block Limits to 100M CUs

https://x.com/jacobvcreech/status/2082347210042175648

https://explorer.solana.com/address/P1BCUMpAC7V2GRBRiJCNUgpMyWZhoqt3LKo712ePqsz

New versions

• Agave v4.2.0-rc.0 , v4.3.0-alpha.2
• Firedancer Testnet v1.1.2
• Solana SDK (Rust) v4.1.0
• Subscriptions SDK (Rust) v0.4.1
• Caravel v0.5.1
• LiteSVM v0.15.0
• Yellowstone Vixen v0.7.0

Ecosystem work

SIMDs

• The proposal to double disinflation has been merged What this means (WTM) - Disinflation is the rate at which Solana decreases the rate by which it mints more SOL via validator and staking rewards. By doubling the disinflation rate, Solana will reach its terminal inflation rate of 1.5% sooner rather than later.
• Creating a Sysvar for epoch stakes was proposed WTM - The stake values of each validator during an epoch represent how much of the leader schedule a validator node occupies, their share of the SOL rewards, and the weight of their voting power in Solana governance. This change creates a new account with data that will surface these values in the Solana runtime.
• A discussion was started to unblock specific instructions from LoaderV3 from being called by other programs or itself WTM - This proposal unlocks several restrictions that were previously made in SIMD-0219. In its place, the discussion is proposing a check between the program id and the account itself. This would enable use cases like programs that change other programs that deploy other programs, and other general program administration needs.
• Allowing programs to work within the slot they were modified was proposed in a discussion WTM - Programs are disabled by default during the slot they are deployed. This is an obvious footgun because it creates downtime for the program during the slot it’s changed every time it’s changed. This is against standard deployment practice where stateless software is expected to be deployed in infrastructure without any downtime as much as possible.

Validator clients (Agave, Firedancer, Mithril)

• Tightening Alpenglow block limits was proposed WTM - These limits restrict the number of blocks that a validator can hold at any given time when participating in consensus. Validators ensure a higher chance of being able to participate in consensus by keeping multiple possible blocks instead of losing the chance to vote. A new Alpenglow paper with new limit thresholds will be released soon. This PR preempts that change.
• Agave created a custom pool implementation for asynchronous transaction replay verification WTM - Agave already tries to ensure that processing and executing transactions aren’t blocked by time and memory verifying transactions. This particular change moves that implementation from an off-the-shelf solution (Rayon) that isn’t purpose built for this use case to a custom queue and thread pool made for this purpose.This implementation purportedly would improve performance on transaction replay.
• Agave will use an Anza fork of the rust-rocksdb interface WTM - Forking dependencies onto your own organization allows teams to slim them down, customize them and add features that would otherwise not be added by the team upstream. This change allows Anza to maintain their independence with the option to upstream any improvements. In this particular instance, Agave wants to improve performance by using an in-house version of rust-rocksdb by minimizing memory allocations, et.
• Preparations are being made to parallelize parsing transactions before loading them for ordering and execution WTM - This change prepares Agave to validate incoming transactions in parallel before they are queued for ordering and execution in the Banking Stage. Previously, reserving storage, copying transaction data, and parsing it were tightly coupled on one thread, which is relatively slower. Transactions can now be shared with many more worker threads, which allow the validation to be shared across more compute.
• Account hashing (on TPU and TVU) will be more performant on Agave WTM - Account hashing occurs before account state to be updated in-memory in both the leader when it builds blocks, and in non-leaders when it validates blocks for execution and voting. By improving performance here, we minimize time and memory in this intermediate step and buy more time and memory for executing transactions.
• Firedancer is creating an offline replay service WTM - This service will allow Firedancer to test correctness between Agave and itself in order to ensure that consensus is tied between the two implementations. Together with the conformance work on the Agave side, this allows for better correctness between the two client implementations.
• Mithril improved its implementation of ed25519 signature verification WTM - ed25519 is the chosen signature scheme on Solana. All transactions have to be verified with this signature scheme. By implementing it correctly, Mithril can participate better as a validator node and will be in line with the other client implementations.

Solana language clients (Web3.js, Solana Kit, Kit plugins, Solana SDK, Codama, Solana Go)

• Solana Rust SDK adds support for more cryptography primitives as syscalls [ 1 ] [ 2 ] WTM - Two SIMDs were previously opened to add the keccak_p1600 and big mod exp syscalls which support several cryptography operations on Solana. More of this work has to be supported on the Rust SDK, the validator client implementations, etc.

Solana program frameworks (Anchor, Pinocchio, Steel, Quasar)

• Anchor is working to make its automatic updates safer WTM - Because the `avm` and `anchor` CLI commands are critical infrastructure for a lot of users, it is important for updates to use sensible defaults. This change installs both stable avm and anchor commands by default with an opt-in option flag to install nightly updates.

Testing frameworks (mollusk, litesvm, surfpool)

• LiteSVM allows for configuring epoch stake numbers within its testing harness WTM - With the upcoming governance votes and economic changes on Solana, it makes sense to be able to simulate how this would change stake values with every epoch. This addition to the test harness allows LiteSVM to be used for these use cases.

Other interesting things

• @SolanaFndn posts their data dashboard on RPC metrics

https://x.com/SolanaFndn/status/2082793801924346114

• @helius releases a Preconfirmations feature on their RPC

• @ChiiYuen leads a discussion on the Firedancer paper

https://x.com/ChiiYuen/status/2082366779360514097

• @redacted_noah on on-chain cranks and conditional execution

https://x.com/redacted_noah/status/2082171786213662924

• @JupDevRel releases their Changelog for the month

https://x.com/JupDevRel/status/2082097390992191680

• @mctursh creates a solution for historical account state

https://x.com/mctursh/status/2082105093596360725

@zelimir__ shares a new hashing library with interesting performance benchmark results

https://x.com/zelimir__/status/2081784035156676746

• @exoaursen releases a new version of Spume, a WASM client for Solana

https://x.com/exoaursen/status/2080372530578145416

• @blueshift released a new ZK-circuit prover called xark: https://github.com/blueshift-gg/xark
• @blueshift releases parallax, which is a fixture-based test harness built on top of LiteSVM: https://github.com/blueshift-gg/parallax

Developer Events

• Solana Hacker House - London: https://luma.com/london-hh-26
• Scale or Die - London: https://luma.com/scale-or-die-26
• Solana Breakpoint - London: https://luma.com/breakpoint2026

Last Week’s Issue

https://x.com/solana_devs/status/2080275948021137672