<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by J Tools on Medium]]></title>
        <description><![CDATA[Stories by J Tools on Medium]]></description>
        <link>https://medium.com/@Jtools_Official?source=rss-d6313b8497c1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rEYj67ByY7Ryv1UGEpULzQ.png</url>
            <title>Stories by J Tools on Medium</title>
            <link>https://medium.com/@Jtools_Official?source=rss-d6313b8497c1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:17:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Jtools_Official/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Solana Transactions Just Got 3x Bigger: What Transaction V1 Changes for Token Creators]]></title>
            <link>https://medium.com/@Jtools_Official/solana-transactions-just-got-3x-bigger-what-transaction-v1-changes-for-token-creators-f7d11ae36ec4?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7d11ae36ec4</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[solanas]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Wed, 30 Sep 2026 11:44:28 GMT</pubDate>
            <atom:updated>2026-09-30T11:44:28.494Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FQXzHahh52l_jfqCjXM9WQ.jpeg" /></figure><p><em>For years, 1,232 bytes was the invisible wall every Solana builder designed around. On September 15 it moved to 4,096. Most of the coverage focused on the number. The more interesting part is what the upgrade quietly removed.</em></p><p>On September 15, 2026, at the start of epoch 1035, the txv1 feature gate activated on Solana mainnet. The maximum transaction size went from 1,232 bytes to 4,096 bytes, roughly 3.3 times more room, and it went live across mainnet, testnet, and devnet at the same time.</p><p>The change comes from two improvement proposals: SIMD-0296 defines the size increase, and SIMD-0385 introduces the v1 transaction format that carries it. The new 4,096 byte ceiling is not an arbitrary number, it aligns with the standard memory page size validator hardware already uses.</p><p>If you launch tokens, run multi-wallet operations, or bundle transactions on Solana, this matters more than the headline suggests.</p><h3>Why 1,232 Bytes Was the Number That Shaped Everything</h3><p>The old limit was not a soft guideline. It was a hard ceiling that quietly determined the architecture of almost every serious Solana workflow.</p><p>Every account a transaction touches costs 32 bytes just to reference. Every signature costs 64. Add the instruction data on top, and 1,232 bytes disappears faster than most people expect. Anything that needed to touch many accounts, carry a proof, or run several operations atomically simply did not fit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DE-xSOWjR2O_QPzhWJNyhQ.jpeg" /></figure><p>So builders worked around it. Operations that logically belonged together got split into chained transactions. Things that needed to happen atomically got wrapped in bundles. Address Lookup Tables were introduced specifically so transactions could reference more accounts than would otherwise fit, by pointing at a stored table instead of listing addresses inline.</p><p>To make it concrete: a transaction with 10 signers spends 640 bytes on signatures alone before a single instruction is written. Reference 15 accounts and another 480 bytes are gone. That is more than 1,100 of your 1,232 bytes consumed by overhead, leaving almost nothing for the actual work.</p><p>Most of the complexity in multi-wallet tooling on Solana exists because of that ceiling.</p><h3>What Fits Now That Did Not Before</h3><p>The official upgrade documentation is specific about the workloads this unlocks: ZK proofs such as those used by Confidential Transfers, large multisigs, and some on-chain signature schemes.</p><p>The key phrase in the announcement is that these can now fit in single atomic transactions “rather than requiring chained operations or bundles.”</p><p>That sentence is doing a lot of work. A meaningful class of operations that previously had to be split across multiple transactions, and then stitched back together with a Jito bundle to preserve atomicity, can now be one transaction. One signature flow, one atomic unit, no bundle required for the atomicity itself.</p><p>Bundles do not become obsolete. You still need them when separate transactions must land in the same block, or when you need block-position guarantees against snipers. But the specific case where a bundle existed purely because the work did not fit in 1,232 bytes has a simpler answer now.</p><h3>The Part Most Coverage Skipped: ALTs Are Gone in V1</h3><p>This is the detail worth knowing before anyone migrates.</p><p>The v1 format does not support Address Lookup Tables at all. They were removed. Instead, v1 transactions place up to 64 accounts directly inline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-wrf6YtuMkAEzgb3Cqnf4g.jpeg" /></figure><p>The reasoning is straightforward once you see the math. At 32 bytes per address, 64 accounts is 2,048 bytes, which sits comfortably inside the 4,096 byte envelope. The entire reason ALTs existed was to reference more accounts than would fit inline. With the bigger envelope, inline addressing covers the cases ALTs were invented to solve, so the format drops the indirection.</p><p>For a team currently relying on lookup tables, this is a fork in the road rather than a break. Legacy and v0 transactions continue to work exactly as before, ALTs included. Nothing you have running today stops working. But you cannot take v1’s larger size and keep your lookup tables at the same time. It is one or the other.</p><p>If your workflow needs more than 64 accounts in a single transaction, v0 with ALTs is still the path. If you need bigger instruction payloads and 64 accounts is enough, v1 is the upgrade.</p><h3>What This Means for Token-2022 Confidential Transfers</h3><p>Confidential Transfers is the Token-2022 extension that encrypts transfer amounts on-chain. The transaction stays public, the participants stay visible, the amount is hidden.</p><p>It has always been the extension with the narrowest practical support, and transaction size was a real part of why. The zero-knowledge proofs that make confidential transfers work are large, and fitting them inside 1,232 bytes alongside everything else a transfer needs was the constraint.</p><p>The upgrade documentation names Confidential Transfers directly as a workload the larger envelope unlocks. For teams that wanted amount privacy for payroll, treasury operations, or business settlement and found the tooling immature, the underlying constraint just loosened considerably.</p><p>Whether integration support follows is a separate question, and it will take time. But the technical blocker moved.</p><h3>What Multi-Wallet Operators Should Take From This</h3><p>If you run distributions, coordinated buys, or batch transfers across many wallets, the practical effect is headroom.</p><p>More instructions fit in a single transaction. More accounts can be referenced inline without lookup table setup. Operations that previously required splitting into several transactions have more room to stay as one.</p><p>One honest caveat: none of this is automatic. Tooling has to explicitly adopt v1 to benefit. Developers need to upgrade SDK dependencies and pass maxSupportedTransactionVersion: 1 on the relevant RPC calls. Wallets have a stricter obligation, they must only advertise a transaction version they can actually sign, so dapps do not send them something they cannot process.</p><p>Until a tool migrates, it keeps operating on v0 with the old limit, and everything works exactly as it did before. The benefit arrives as the ecosystem adopts the format, not the moment the feature gate flipped.</p><p>Today, tools like <a href="https://j.tools/en/tools/pumpfun-create-and-bundle-buy">Pump.fun Create &amp; Bundle Buy</a>, <a href="https://j.tools/en/tools/multi-sender">Multi Sender</a>, and <a href="https://j.tools/en/tools/bundled-trade">Bundled Trade</a> handle the packing and sequencing that the old limit made necessary. The upgrade does not change what they do for you. It changes what becomes possible underneath as the format spreads.</p><h3>The Other September Upgrade</h3><p>Transaction V1 was not the only network change this month. On September 18, Solana reduced slot time to 250ms, with 200ms as the stated target, cutting confirmation times further.</p><p>For anyone whose operations are timing sensitive, launches, coordinated entries, anything where landing in a specific block matters, faster slots compress the window in both directions. Your transaction confirms sooner, and so does everyone else’s. Speed advantages that came from raw latency shrink when the whole network gets faster.</p><h3>What You Actually Need to Do</h3><p><strong>If you are a regular user:</strong> nothing. Legacy and v0 transactions work as they always have. Your wallet, your swaps, your transfers are unaffected.</p><p><strong>If you build on Solana:</strong> upgrade your SDK dependencies, and expect breaking changes when reading transactions. You need maxSupportedTransactionVersion: 1 on RPC calls that should return v1 transactions.</p><p><strong>If you maintain a wallet:</strong> only advertise versions you can genuinely sign in your supportedTransactionVersions field. Claiming v1 support you have not implemented means dapps will send you transactions you cannot process.</p><p><strong>If you use Address Lookup Tables:</strong> decide deliberately. Staying on v0 keeps ALTs and the old size limit. Moving to v1 gets the larger envelope and 64 inline accounts, and gives up lookup tables entirely.</p><h3>The Bottom Line</h3><p>The headline is that Solana transactions got 3.3 times bigger. The more useful read is that a constraint which shaped years of Solana tooling architecture just moved, and the workarounds built around it are now optional in a specific set of cases.</p><p>ZK proofs, large multisigs, and complex atomic operations fit in one transaction. Confidential Transfers has more room than it has ever had. Address Lookup Tables are no longer the answer to the account limit in the new format, because the new format does not need them.</p><p>Nothing breaks, nothing is forced, and everything you run today keeps running. What changes is the ceiling everyone has been building under.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7d11ae36ec4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Burn Tokens on Solana (And Why Projects Actually Do It)]]></title>
            <link>https://blog.blockmagnates.com/a-holographic-terminal-showing-token-balances-queued-for-burning-with-full-partial-and-specific-5795f5d77328?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5795f5d77328</guid>
            <category><![CDATA[solanas]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[token]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Sun, 13 Sep 2026 14:01:02 GMT</pubDate>
            <atom:updated>2026-09-18T12:22:37.371Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Most people who say they burned tokens actually just sent them to a wallet nobody controls. That is not burning, and the difference shows up in every supply number anyone checks afterward.</em></p><figure><img alt="A glowing token disintegrating into embers with a supply counter ticking downward behind it" src="https://cdn-images-1.medium.com/max/1024/1*W9382rJKu8Stu5o4SR-EgQ.jpeg" /></figure><p>Burning tokens is one of the most commonly announced actions in crypto and one of the most commonly done wrong. A project posts “we burned 10% of supply,” someone checks the token on an explorer, and total supply is exactly what it was yesterday. The tokens moved, but nothing was destroyed.</p><p>This guide covers what burning actually does on Solana, the mistake that makes most burns fake, the legitimate reasons projects burn, and how to run a real burn across one wallet or hundreds.</p><h3>What Burning Actually Means</h3><p>Burning on Solana uses a specific instruction in the token program. When you burn an amount, the token program permanently removes it from existence and reduces the mint’s total supply on-chain. It is not a transfer. There is no destination. The tokens stop existing.</p><p>Once a burn transaction confirms, that supply cannot be restored. Not by you, not by the token program, not by any tool. It is one of the few genuinely irreversible actions on the chain.</p><p>The important consequence: a real burn changes the number that every explorer, wallet, and price aggregator reads as total supply. That is why it is verifiable, and that is why it carries weight when a project announces one.</p><h3>The Mistake That Makes Most Burns Fake</h3><p>Here is what a lot of projects do instead: they send tokens to a dead address, usually something like an all-ones or all-zeros wallet that nobody holds the private key for.</p><figure><img alt="Split image comparing a token truly burning away against an identical token sitting intact inside a sealed dead wallet" src="https://cdn-images-1.medium.com/max/1024/1*NHXMPh_-xJgty57joEkyxA.jpeg" /></figure><p><strong>Transfer, not burn</strong>Total supply stays exactly the same. The tokens still exist, they just sit in an address nobody can spend from. Anyone checking the mint sees the original supply number, and the holder list now shows a large balance parked in a strange wallet.</p><p>The practical effect on circulating supply is similar, since those tokens are unreachable. But the on-chain record does not support the claim, and anyone who checks will see that. If your announcement says “burned” and the mint’s supply is untouched, that is the first thing a skeptical reader finds.</p><p>If you want the claim to hold up, use the burn instruction. It costs the same and produces a permanent, verifiable record.</p><h3>How to Check a Burn Claim</h3><p>This works in both directions, whether you are verifying someone else’s announcement or making sure your own is defensible.</p><p>Pull up the token’s mint address on a block explorer and look at total supply. If a real burn happened, the current supply is lower than what the project originally minted, and the burn transactions appear in the mint’s history with the amount destroyed.</p><p>Then check the holder list. If you see a large balance sitting in an address like one made entirely of ones or zeros, that is the dead-wallet pattern. The tokens were moved, not burned, and total supply will confirm it.</p><p>The whole point of burning is that it produces evidence. If the evidence is not there, the claim is just a post.</p><h3>Why Projects Burn Tokens</h3><p><strong>Reducing supply as part of tokenomics.</strong> The most common reason. A project commits to a deflationary model and removes supply at set intervals or milestones.</p><p><strong>Buyback and burn.</strong> Revenue is used to buy the token on the open market, and those tokens are then burned. This is one of the few burn narratives that carries real economic logic, since actual capital is deployed to acquire the supply being removed.</p><p><strong>Removing unsold allocation.</strong> A presale or public sale ends with tokens unsold. Burning them is cleaner than holding them, and it removes any future overhang concern from holders.</p><p><strong>Milestone or vesting burns.</strong> A team allocation that goes unclaimed, or a portion of a treasury committed to be destroyed at a specific point.</p><p><strong>Cleaning up your own wallets.</strong> Less glamorous but very common at an operational level. Old test tokens, dust balances, leftover positions from wallets used once. Burning them clears the wallet and, combined with closing the emptied accounts, recovers locked rent.</p><p><strong>Locking liquidity.</strong> Burning LP tokens permanently locks a pool’s liquidity so it can never be withdrawn. This is a distinct use case with its own mechanics, covered separately.</p><h3>What Burning Does Not Do</h3><p>Worth being honest about, because burn announcements often imply more than they deliver.</p><p>Burning does not create value on its own. Reducing supply only matters if there is demand for what remains. Removing 10% of a token nobody wants leaves you with a smaller amount of a token nobody wants. The arithmetic is real, the price impact is not automatic.</p><p>Burning also does not fix a distribution problem. If one entity controls most of the supply, burning from the public float changes the ratio in the wrong direction. What matters is whose tokens got burned, not just how many.</p><p>Treat a burn as a supply-management action with a verifiable record, not as a growth strategy.</p><h3>How to Run a Burn</h3><p><a href="https://j.tools/en/tools/burn-tokens">Token Burner</a> handles burns across one wallet or many, and it is free to use. There is no platform fee, the only cost is the Solana network fee, which is shown before you execute.</p><figure><img alt="A holographic terminal showing token balances queued for burning with full, partial, and specific burn modes" src="https://cdn-images-1.medium.com/max/1024/1*Ekw9vdF2o7UIsAffWcnIYw.jpeg" /></figure><p><strong>Pick a scan mode.</strong></p><p><em>Wallet Scan</em> reads the balances in your connected wallet and lists every token you hold. This is the mode for cleaning up a single wallet or burning from your main holdings.</p><p><em>Multi Wallet + Single CA</em> targets one specific mint across many wallets. You paste the private keys and set the target mint address, and the tool loads that token’s balance from every wallet in one table. This is the mode for a project-level burn where supply is spread across an operation.</p><p><strong>Pick a burn mode.</strong></p><p><em>Full Burn</em> empties the entire balance for each selected row.</p><p><em>Partial Burn</em> burns a percentage you set, leaving the rest untouched.</p><p><em>Specific Burn</em> burns an exact amount per row, for when the number matters and needs to match a public commitment.</p><p><strong>Review before executing.</strong> Every row shows the wallet, the token, the available balance, the planned burn amount, and a USD estimate. The summary panel totals the planned burn and the estimated transaction count. Nothing executes until you confirm.</p><p><strong>Filter if needed.</strong> An <em>Only LP Tokens</em> toggle narrows the table to liquidity pool token rows, useful when you are specifically doing an LP burn rather than a general cleanup.</p><p><strong>Token-2022 works too.</strong> The tool handles both classic SPL and Token-2022 balances from the same terminal, so a token with extensions enabled burns the same way.</p><p><strong>Retry what failed.</strong> After a run, any rows that failed can be rerun on their own with Retry Failed, without rebuilding the batch or touching rows that already succeeded.</p><h3>After the Burn</h3><p><strong>Reclaim the rent.</strong> Burning empties a token account but does not close it. That account still holds roughly 0.002 SOL locked as rent. <a href="https://j.tools/en/tools/close-account">Close Account</a> closes emptied accounts and returns that SOL. Across a large multi-wallet burn this adds up.</p><p><strong>Lock the supply if that is the point.</strong> Burning reduces supply, but if mint authority is still active, new tokens can be created later. A burn announcement means much less when the mint can simply reissue. <a href="https://j.tools/en/tools/revoke-mint">Revoke Mint</a> permanently removes that ability, which is what makes a reduced supply actually final.</p><p><strong>Publish the transaction.</strong> A burn is only useful as a signal if people can verify it. Share the transaction signature so anyone can confirm the burn on a block explorer and see the supply change for themselves.</p><h3>The Bottom Line</h3><p>A real burn uses the burn instruction, permanently destroys the amount, and reduces total supply in a way anyone can verify on-chain. Sending tokens to a dead wallet is not the same thing, and the difference is visible to anyone who checks.</p><p>If you are burning for tokenomics reasons, pair it with revoking mint authority so the reduced supply is actually permanent. If you are burning to clean up wallets, close the emptied accounts afterward and recover the rent.</p><p><a href="https://j.tools/en/tools/burn-tokens">Token Burner</a> covers both cases, single wallet or hundreds, with full, partial, or exact amounts, and a row-by-row preview before anything is destroyed. It is free, and given that burns are irreversible, that preview step is the part worth slowing down for.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools/"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5795f5d77328" width="1" height="1" alt=""><hr><p><a href="https://blog.blockmagnates.com/a-holographic-terminal-showing-token-balances-queued-for-burning-with-full-partial-and-specific-5795f5d77328">How to Burn Tokens on Solana (And Why Projects Actually Do It)</a> was originally published in <a href="https://blog.blockmagnates.com">Block Magnates</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Token 2022 Extensions Explained: Transfer Fees, Metadata Pointers, and When to Actually Use Them]]></title>
            <link>https://medium.com/@Jtools_Official/token-2022-extensions-explained-transfer-fees-metadata-pointers-and-when-to-actually-use-them-d7375d9409c1?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7375d9409c1</guid>
            <category><![CDATA[token]]></category>
            <category><![CDATA[solanas]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Tue, 08 Sep 2026 15:22:22 GMT</pubDate>
            <atom:updated>2026-09-08T15:22:22.286Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Token-2022 lets you build behavior directly into a token that classic SPL simply cannot do. It also runs on a different program ID, which is the part most guides forget to mention until it becomes your problem.</em></p><figure><img alt="A glowing token core with modular extension blocks docking onto it, representing Token-2022 extensions attaching to a mint" src="https://cdn-images-1.medium.com/max/1024/1*DaSKVj7a2_1MvW8XHj8FYQ.jpeg" /></figure><p>Most tokens on Solana are classic SPL tokens. They hold a supply, they transfer, and everything past that is handled by whatever contracts you build around them. Token-2022 changes that by letting you attach behavior to the token itself, fees that collect automatically on every transfer, metadata stored inside the mint, transfers that hide their amounts, or custom logic that runs on each move.</p><p>The trade-off is real and worth understanding before you launch anything. This guide covers what the extensions actually do, the compatibility catch nobody warns you about, and how to decide whether your project needs Token-2022 at all.</p><h3>What Token-2022 Actually Is</h3><p>Token-2022 is the upgraded Solana token program. It sits alongside the classic SPL Token program rather than replacing it, and it introduces a system of extensions that can be enabled when a mint is created.</p><p><strong>The compatibility catch</strong>Token-2022 uses a different program ID than classic SPL. Modern wallets and indexers recognize it, but every DEX, aggregator, bridge, and integration has to have explicitly updated its code to handle Token-2022 mints. Support is broad now but not universal, and it varies by venue and by which specific extensions your token uses.</p><p>This is the single most important thing to understand before choosing Token-2022. You are trading some integration certainty for capabilities that classic SPL cannot provide.</p><h3>The Extensions That Matter</h3><h3>Transfer Fee</h3><p>The most widely used extension. A transfer fee is defined at the mint level, so a percentage of every transfer is automatically withheld, regardless of which wallet, DEX, or contract executes it. Nobody can route around it, because it is enforced by the token program itself rather than by a contract wrapped around the token.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ehwCscZ7HlqPksivUoMOBw.png" /></figure><p>Two values define it:</p><p><strong>Basis points.</strong> The fee rate, expressed in hundredths of a percent. 100 basis points is 1%. 500 basis points is 5%. This is the percentage taken from every transfer amount.</p><p><strong>Maximum fee cap.</strong> An absolute ceiling on how much any single transfer can be charged, expressed in token units. Without a cap, a 2% fee on a very large transfer becomes a very large fee. The cap is what keeps whale-sized transfers from paying disproportionately.</p><p>Here is the part that surprises people: <strong>the fee is not sent to you automatically.</strong> It is withheld inside the recipient’s token account, sitting there until someone with the withdraw withheld authority claims it. That authority is a separate role you assign at creation, and it determines who can eventually sweep accumulated fees out of all those token accounts.</p><p>This is why a “fee token” is an ongoing operational thing rather than a passive income stream. Fees accumulate across potentially thousands of token accounts, and collecting them is an action someone has to actually take.</p><h3>Metadata Pointer</h3><p>Classic SPL tokens store their name, symbol, image, and links in a separate Metaplex metadata account derived from the mint. The metadata pointer extension lets Token-2022 store that information inside the mint itself, no separate account required.</p><p>The practical effect is fewer moving parts. The token’s identity travels with the mint rather than living in an adjacent account that a tool has to know how to find and update.</p><h3>Confidential Transfers</h3><p>This extension hides transfer amounts on-chain. The transaction is still public, the participants are still visible, but the amount moved is encrypted.</p><p>The use cases are mostly institutional: payroll, treasury operations, business-to-business settlement, anywhere the fact of a payment is fine to reveal but the size of it is not. It is a genuinely powerful capability and also the extension with the narrowest integration support, since venues have to specifically handle encrypted amounts.</p><h3>Transfer Hooks</h3><p>A transfer hook lets you attach a custom program that runs on every transfer of the token. Whitelist enforcement, compliance checks, on-chain royalty logic, transfer limits, anything you can express as a program.</p><p>This is the most flexible extension and the most demanding, since it requires writing and deploying that hook program yourself. It is the one place where Token-2022 stops being a no-code decision.</p><h3>The Broader Family</h3><p>The Token-2022 standard includes more extensions beyond these: non-transferable tokens (soulbound), interest-bearing tokens that accrue value against a stated rate, permanent delegates that retain transfer rights over every account, and others. Which ones matter depends entirely on what the token is for.</p><h3>The Thing That Trips People Up</h3><p>Extensions are configured at mint creation. Most of them cannot be added to a token that already exists, and several cannot be removed once set.</p><p>This means the decision is front-loaded in a way most token launches are not. With a classic SPL token, you can create it first and figure out the surrounding mechanics later. With Token-2022, the extension stack is part of the mint’s permanent structure from the first transaction.</p><p>Decide what the token needs to do before you create it, not after.</p><h3>When Token-2022 Is the Right Call</h3><p><strong>A fee is central to the token’s design.</strong> If a percentage of every transfer needs to route somewhere, whether that is a treasury, a buyback program, or a revenue share, doing it at the mint level is far more reliable than trying to enforce it through contracts that people can route around.</p><p><strong>Metadata simplicity matters.</strong> For teams who want token identity handled inside the mint rather than in a separate Metaplex account.</p><p><strong>You have a compliance or control requirement.</strong> Confidential transfers for amount privacy, transfer hooks for whitelist enforcement, non-transferable for credentials or soulbound assets. Classic SPL has no answer for any of these.</p><h3>When to Stick With Classic SPL</h3><p><strong>A meme coin or a straightforward community token.</strong> If the token just needs to exist, trade, and be held, classic SPL has zero compatibility questions anywhere on Solana. Adding extensions you do not need buys you integration risk in exchange for nothing.</p><p><strong>Maximum DEX and aggregator reach from day one.</strong> Classic SPL is the default assumption for every venue on the chain. Nothing has to have been updated for it.</p><p><strong>You are not sure yet.</strong> Extensions are permanent. Uncertainty is a reason to stay with the standard that has no permanent decisions attached to it.</p><h3>Creating a Token-2022 Mint</h3><p><a href="https://j.tools/en/tools/token2022-creator">Token-2022 Creator</a> runs the whole thing as one flow with one signature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bc5fY1WEcN714WD36o2Lwg.png" /></figure><p><strong>Token details.</strong> Name, symbol, description, total supply, and decimals (9 by default). Upload a logo (PNG, JPG, GIF, or WEBP, up to 5MB, 200x200 recommended) and add website, X, Telegram, and Discord links.</p><p><strong>Transfer fee settings.</strong> Set the fee in basis points and the maximum fee cap, then assign the withdraw withheld authority, the wallet that will be able to claim accumulated fees later.</p><p><strong>Advanced extension settings.</strong> The additional Token-2022 extension options, including metadata pointer configuration, live in their own panel.</p><p><strong>Standard authority controls.</strong> Revoke mint, freeze, and update authority toggles work here exactly as they do for a classic SPL token, each as an optional add-on inside the same transaction.</p><p><strong>Optional branding.</strong> A custom mint address, or a vanity address that starts with a prefix you choose, both available as add-ons in the same flow.</p><p><strong>Review and mint.</strong> The cost breakdown shows the platform fee plus estimated network cost for initializing your chosen extensions before you sign. The base is 0.15 SOL plus roughly 0.02 SOL in network fees, with each optional add-on shown separately. One signature initializes the mint with every selected feature active.</p><p>The live preview panel shows how the mint will appear in wallets and explorers, including which extensions are enabled, before anything is signed.</p><h3>After Launch</h3><p>A transfer fee changes how downstream operations behave, so it is worth knowing what still works normally. <a href="https://j.tools/en/tools/multi-sender">Multi Sender</a> distributes a Token-2022 asset to many wallets even with the transfer fee active, so airdrops and community distributions work as expected.</p><p>If you used the metadata pointer extension and need to refresh the logo, name, or links later, <a href="https://j.tools/en/tools/update-metadata">Update Metadata</a> handles that, as long as update authority has not been revoked.</p><h3>The Bottom Line</h3><p>Token-2022 is the right choice when the token needs to do something classic SPL cannot: collect fees at the protocol level, hide transfer amounts, run custom logic on every move, or carry its metadata inside the mint. Those are real capabilities with no equivalent on the classic standard.</p><p>It is the wrong choice when you are launching something straightforward and reaching for extensions because they sound advanced. Classic SPL has universal support and no permanent structural decisions to get wrong.</p><p>Pick based on what the token actually has to do. If it needs a transfer fee or a compliance control built in, Token-2022 is genuinely the only path. If it does not, the standard token creator is the simpler and safer answer.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools/"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7375d9409c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meme Coin Maker: How to Create Your Own Solana Meme Coin (No Code)]]></title>
            <link>https://medium.com/@Jtools_Official/meme-coin-maker-how-to-create-your-own-solana-meme-coin-no-code-95423b40b165?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/95423b40b165</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[solanas]]></category>
            <category><![CDATA[memecoins]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Fri, 28 Aug 2026 11:12:13 GMT</pubDate>
            <atom:updated>2026-08-28T11:12:13.695Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A meme coin is just an SPL token with a good story attached. The technical part, the part that actually intimidates people, takes about three minutes and zero code once you know what each field on the form actually does.</em></p><figure><img alt="Two glowing coins forming side by side, one with a liquidity pool beneath it, the other riding a rising bonding curve beam" src="https://cdn-images-1.medium.com/max/1024/1*LKHB5_6z6bwvcKdMWFyX_g.jpeg" /></figure><p>Every meme coin on Solana, from the ones that made headlines to the ones nobody remembers, started as the same technical object: an SPL token with a name, a symbol, a supply, and a set of authorities. The meme part is marketing and timing. The token part is a form.</p><p>There are two ways to actually create that object. One is a standard SPL token with a fixed supply you set yourself, which needs a liquidity pool before anyone can trade it. The other is a bonding curve launch through Pump.fun, where price discovery is built in from the first buy and no separate liquidity step is required. This guide walks through both, field by field, including the decisions that actually matter for a token meant to build a community around it.</p><p><strong>Path 1</strong></p><h3>Standard SPL Token</h3><p>This path gives you full control over supply, decimals, and starting price. It’s the slower route to a live market, since it needs a liquidity pool afterward, but it’s the one to pick if you want the token’s economics designed exactly the way you want them from the start.</p><h3>What You’re Actually Creating</h3><p>An SPL token is a fungible asset issued through the Solana Program Library standard, the same standard every wallet, DEX, and explorer on Solana already knows how to read. Every token has a unique mint address that defines its decimals, supply, and authorities. Mint authority controls whether more supply can ever be created. Freeze authority can lock individual holders’ balances. Update authority controls the token’s metadata, its name, logo, and description.</p><p>A meme coin maker tool exists to generate this object without you writing a program or touching the Solana CLI. You fill out a form, sign one transaction, and the token exists on-chain with metadata already attached.</p><h3>Step 1: Name, Symbol, and Description</h3><p>Start with the basics. The name is the full token name, the symbol is the short ticker (usually 3 to 6 characters) that shows up in wallets and on charts, and the description is optional but worth writing anyway, since it’s often the first text someone reads when they click into your token on an explorer or DEX page.</p><figure><img alt="J Tools Token Creator Page" src="https://cdn-images-1.medium.com/max/1024/1*uMwlvURG_9JxFL0sTu286Q.png" /></figure><p>For a meme coin specifically, the name and symbol are doing more work than they would for a utility token. This is the entire pitch in most cases, so it’s worth spending real time here rather than treating it as a placeholder step.</p><h3>Step 2: Decimals and Supply</h3><p>Decimals control how divisible your token is. The default is 9, matching SOL itself, and most meme coins stick with either 6 or 9 unless there’s a specific reason to deviate.</p><p>Supply is where meme coin culture actually differs from a typical utility token. Meme coins commonly launch with very large supplies, often in the billions or trillions, because a low per-token price with a huge supply count is part of the appeal for a lot of meme coin buyers. There’s no technical requirement here, it’s purely a design decision based on how you want the token to feel to a new holder checking the price for the first time.</p><h3>Step 3: Logo and Social Links</h3><p>Upload a logo (PNG, JPG, GIF, or WEBP, typically recommended around 200x200 pixels) or paste a URL to one. This is the image every wallet, explorer, and DEX chart will display, so it’s worth using the actual final version here rather than a placeholder you plan to swap later.</p><p>Add your website, X/Twitter, Telegram, and Discord links if you have them ready. These get saved on-chain as part of the token’s metadata. A meme coin with no social links attached at launch reads as unfinished to anyone checking it in the first hour, which is often the highest-traffic window a new token gets.</p><h3>Step 4: Decide on Authorities</h3><p>This is the step most first-time creators skip past without thinking, and it’s the one that shapes how your token is perceived by everyone who checks it afterward.</p><p>Three authorities get created by default when you mint a token: mint authority, freeze authority, and update authority. You can choose to revoke any of them right in the same creation flow, as part of the same transaction, rather than doing it as a separate step afterward.</p><p><strong>Revoking mint authority</strong> proves total supply can never increase. For a meme coin with a fixed, marketed supply number, this is close to a default expectation from holders at this point. Tools like DexScreener and most chart aggregators flag whether mint authority is still active, and an active mint authority on a meme coin is one of the first things a cautious buyer checks.</p><p><strong>Revoking freeze authority</strong> proves nobody, including you, can lock a holder’s balance. For a community-driven meme coin, there’s rarely a reason to keep this.</p><p><strong>Revoking update authority</strong> locks the metadata, the name, logo, description, and social links, permanently. This one is worth holding off on until you’re fully confident everything is correct, since there’s no path back once it’s revoked. A separate <a href="https://j.tools/en/tools/update-metadata">Update Metadata</a> tool exists for fixing details after launch, but only while this authority is still active.</p><p>Doing this at creation time rather than as a follow-up step means one signature covers the whole setup instead of running four separate transactions after the fact.</p><h3>Step 5: Optional Branding, Custom and Vanity Addresses</h3><p>Two optional add-ons exist specifically for branding. A custom mint address lets you pre-generate the token’s keypair before creation. A vanity address goes further, searching in-browser for a mint address that starts with a specific prefix you choose, so the contract address itself carries part of your brand.</p><figure><img alt="J Tools Token Creator vanity adrees create same window" src="https://cdn-images-1.medium.com/max/1024/1*2p2hyz5NbuiLwZ-FTAr4cw.png" /></figure><p>Neither is required, but for a meme coin where the ticker and identity are the whole point, a mint address that visibly matches the project name is a small detail that reads as more deliberate than a random 44-character string.</p><h3>Step 6: Review and Sign</h3><p>Before signing, the live preview panel shows exactly how the token will appear once it’s live, name, symbol, supply, decimals, and which authorities are active or revoked. Confirm everything matches what you intended, then sign once. The base cost is a small platform fee plus the Solana network fee, with each optional add-on (authority revokes, custom address, vanity address) adding its own small fee shown before you commit.</p><h3>After Creation: You Still Need a Market</h3><p>Creating the token through a standard SPL token creator gives you the token, not a market for it. There’s no built-in trading curve. To make it tradable, you need to seed a liquidity pool.</p><p><a href="https://j.tools/en/tools/create-lp">Create LP</a> sets up a pool on Raydium, Meteora, or Orca, pairing your new token against SOL so people can actually buy and sell it. This is the trade-off for Path 1: full control over supply, decimals, and starting price, in exchange for one extra step before the token is actually tradable.</p><p><strong>Path 2</strong></p><h3>Bonding Curve via Pump.fun</h3><p>This path skips the liquidity pool entirely. Price discovery is built into the bonding curve from the first buy, and the token is tradable the instant it’s created. The trade-off is that supply, curve mechanics, and pricing follow Pump.fun’s format rather than one you design yourself.</p><figure><img alt="J Tools Pumpfun Create Page" src="https://cdn-images-1.medium.com/max/1024/1*viBXZb3fzCJwJw92ap2lOA.png" /></figure><p><a href="https://j.tools/en/tools/pumpfun-create">Pump.fun Create</a> runs this as a single guided flow from one wallet.</p><p><strong>Token basics.</strong> Name, ticker, and an optional description, plus a logo (minimum 1000x1000, up to 15MB, square) and an optional banner image (up to 15MB, 3:1 ratio). Social links are optional here too.</p><p><strong>Buy on launch.</strong> This toggle is on by default, meaning your creator wallet picks up the first bag in the same transaction as the token’s creation. Set a buy amount in SOL (minimum 0.02 SOL) and the tool shows an estimated token amount you’ll receive before you sign.</p><p><strong>Speed.</strong> Normal, Fast, Turbo, or Custom, controlling how aggressively the transaction is prioritized on the network.</p><p><strong>Custom token address.</strong> For an extra fee, you can preview and lock in a custom contract address before signing, one that ends in “pump” to match the platform convention.</p><p><strong>Mayhem mode.</strong> An optional setting that amplifies price action for the first 24 hours after launch, for projects that want a more volatile opening window.</p><p><strong>USDC launches.</strong> An option to launch on a stablecoin-denominated bonding curve instead of SOL, if dollar-priced entry matters more than SOL-priced entry for your audience.</p><p>Everything, the token creation and your first buy, goes out as one signature. There’s no separate liquidity step, because the bonding curve is the market from block one.</p><p><strong>Which path fits which goal.</strong> Path 1 makes sense when you want to set your own supply and decimals and you’re prepared to seed liquidity yourself. Path 2 makes sense when you want the token live and tradable in one transaction with zero extra setup. Both produce a real token on Solana, the difference is entirely in how the market gets built underneath it.</p><h3>Common Mistakes to Avoid</h3><p><strong>Launching with no description or social links.</strong> The first hour after launch is when the most eyes land on a new token, and an empty profile reads as unfinished.</p><p><strong>Revoking update authority before checking everything.</strong> Once it’s gone, a typo in the name or a low-resolution logo is permanent. Review everything twice before that step.</p><p><strong>Picking decimals or supply without a plan.</strong> These aren’t purely cosmetic, they shape how the price displays and how the token feels to a new buyer checking it for the first time.</p><p><strong>Forgetting that a standard token needs a liquidity pool.</strong> Without one, the token exists on-chain but nobody can trade it.</p><p><strong>Treating the mint address as an afterthought.</strong> If branding matters to the project, a random 44-character address undercuts a name and logo that were otherwise carefully chosen. Both paths offer a custom address option to fix this in the same flow, rather than requiring a separate tool afterward.</p><p><strong>Setting the buy amount on a bonding curve without checking the estimate.</strong> On Pump.fun, the buy amount field shows an estimated token receipt before you sign. Skipping that check means finding out how much of the supply you actually picked up only after the transaction lands.</p><h3>The Bottom Line</h3><p>Making a meme coin on Solana is a form, not a coding project, whichever path you pick. Name, symbol, logo, and a decision on authorities or curve settings, all in one flow, one signature.</p><p>The technical part was never the hard part. What actually determines whether a meme coin gets attention is everything that happens after the token exists: the liquidity, the community, the timing. <a href="https://j.tools/en/tools/token-creator">Token Creator</a> handles the standard SPL path, and <a href="https://j.tools/en/tools/pumpfun-create">Pump.fun Create</a> handles the bonding curve path, so either way the setup takes minutes and your attention can go where it actually matters.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools/"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95423b40b165" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Check and Update Solana Token Metadata (Before You Lock It Down)]]></title>
            <link>https://medium.com/@Jtools_Official/how-to-check-and-update-solana-token-metadata-before-you-lock-it-down-88ca87c5873a?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/88ca87c5873a</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[solanas]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Mon, 24 Aug 2026 12:08:03 GMT</pubDate>
            <atom:updated>2026-08-24T12:08:03.689Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The logo, name, and social links you see on every token page come from one small off-chain file. Get it wrong, fix it later. Lock the authority that controls it, and whatever’s there stays there forever.</em></p><figure><img alt="A glowing holographic token identity badge with editable name, logo, and social fields, an open padlock hovering above it" src="https://cdn-images-1.medium.com/max/1024/1*W7d7ulDGhlSl4Blyv5rwnA.jpeg" /></figure><p>Every Solana token has a face: a name, a symbol, a logo, a description, a set of social links. None of that lives inside the token’s core on-chain data. It comes from a separate metadata file, and whether you can still edit it depends entirely on one authority most people forget to think about until it’s too late.</p><p>This guide covers what token metadata actually is, how to check what’s currently set for any token, how to update it, and the one sequencing mistake that turns a five-minute fix into a permanent problem.</p><h3>What Is Token Metadata on Solana?</h3><p>Token metadata is the off-chain JSON file that wallets, explorers, and DEX listings read from to display a token’s name, symbol, description, image, and social links. It lives in a Metaplex metadata account derived from the token’s mint address, separate from the token’s core supply and decimals data.</p><p>This is what every explorer, wallet interface, and trading terminal actually shows people. When someone pulls up your token on a DEX chart or in their wallet, the name, the logo, and the links they see all come straight from this metadata record, not from the mint itself.</p><p>While the wallet holding update authority for a token is still active, that wallet can change any of these fields. Once update authority is revoked, or the token is made fully immutable, none of it can ever be changed again.</p><h3>Why This Matters More Than It Seems</h3><p>A token’s metadata is often the first and only impression a potential holder gets. Someone finds a chart, clicks through, and the first things they see are the logo and the name. If the logo is missing, low resolution, or the description still reads like a placeholder, that’s the signal they walk away with, regardless of how solid the actual project is.</p><p>The social links matter just as much. A Twitter link pointing to a dead account or a Telegram link that expired makes a token look abandoned even if the team is actively building. These are small details, but they’re the details a first-time visitor judges instantly.</p><p>There’s also a supply-side reason this matters. Every explorer and every DEX charting tool caches or displays metadata as it reads it on-chain. If you launch with a placeholder logo and never update it, that placeholder is what shows up across every platform your token appears on, indefinitely, until someone with update authority actually goes in and fixes it.</p><h3>How to Check What’s Currently Set</h3><p>Before changing anything, check what’s actually on-chain for a given token. <a href="https://j.tools/en/tools/update-metadata">Update Metadata</a> starts with exactly this: paste the token’s mint address (CA) and click Load, and the tool pulls the current name, symbol, description, image, and social links directly from on-chain metadata.</p><p>This matters even if you’re not planning to change anything yet. Confirming what’s currently set is the useful first step whenever you need to verify a token’s actual on-chain identity rather than trusting a screenshot or an old announcement.</p><h3>How to Update It</h3><p>Once you’ve loaded the current values, updating is a matter of editing only what needs to change.</p><figure><img alt="A holographic form panel showing editable token metadata fields being updated with a beam of light" src="https://cdn-images-1.medium.com/max/1024/1*91PceCZcNlPsAjsak9zzKA.jpeg" /></figure><p><strong>Name and Symbol.</strong> Fix a typo, adjust branding, whatever the field needs.</p><p><strong>Description.</strong> Update it to reflect where the project actually is now, not where it was at launch.</p><p><strong>Logo.</strong> Upload a replacement image (PNG, JPG, GIF, or WEBP, up to 1MB). Wallets, Solscan, and DEX listings all pull the display image from this field, so this is the single highest-leverage edit if the current logo is missing or low quality.</p><p><strong>Website, Twitter/X, Telegram.</strong> Update or add social links. Fields you don’t touch stay exactly as they were, so you’re never forced to re-enter everything just to fix one line.</p><p>Once the fields look right, connect the wallet that holds update authority and submit. One on-chain transaction writes the new metadata. The platform fee is 0.2 SOL, shown upfront before you submit anything. Only the wallet holding update authority can make this change, so there’s no risk of someone else altering your token’s metadata.</p><h3>Can You Update It More Than Once?</h3><p>Yes, as many times as needed, for as long as update authority is still active. There’s no limit on how many separate updates you can run. A common pattern is updating once right after launch to fix any last-minute details, then again later when the project adds a new social channel, launches a website, or wants to refresh the description as the project matures.</p><p>Each update is its own transaction and its own 0.2 SOL fee, so it’s worth batching changes into one pass rather than submitting a separate update for every small edit. The Load step at the start of each session means you’re always editing from the current on-chain state, not an outdated local copy.</p><h3>The Sequencing Mistake That Locks You Out</h3><p>Here’s the part that catches people off guard. Update authority is also what lets you revoke authorities or make a token fully immutable, and both of those actions are permanent.</p><figure><img alt="A token identity badge permanently sealed inside a crystallized block, a flawed detail frozen and unreachable inside" src="https://cdn-images-1.medium.com/max/1024/1*BNt60ecKwRapt7C2ouHddg.jpeg" /></figure><p><strong>How it goes wrong</strong>Someone launches a token, revokes update authority right away because it feels like the responsible, trust-building move, and a week later notices the logo is the wrong resolution or the Twitter link points to the wrong handle. At that point, there’s no fixing it. The metadata is frozen exactly as it was the moment authority was revoked, permanently, with no tool or workaround that can change it after the fact.</p><p>The fix is sequencing, not a different tool. Review and finalize metadata first. Confirm the name has no typos, the logo is the actual final version at good resolution, the description is accurate, and every social link is live and correct. Only after all of that is confirmed should you move on to revoking authorities or locking the token down.</p><h3>A Quick Pre-Lock Checklist</h3><p>Before you revoke update authority or use Make Immutable, confirm:</p><p><strong>Name and symbol</strong> have no typos and match what you’ve been marketing under.</p><p><strong>Logo</strong> is the final version, correct resolution, and actually uploaded (not a placeholder or missing image).</p><p><strong>Description</strong> reflects the current state of the project, not launch-day copy.</p><p><strong>Website, Twitter, and Telegram links</strong> are all live and point to the right accounts.</p><p>Five minutes spent on this checklist is the difference between a token that looks finished and one that looks abandoned to anyone checking it for the first time.</p><p>Run this same checklist again any time you’re about to take an irreversible action tied to update authority, not just once at launch. A team preparing to go immutable six months into a project should run through it exactly as carefully as a team launching today, since the same permanence applies either way.</p><h3>What to Do After</h3><p>If you’re starting completely fresh rather than editing an existing token, <a href="https://j.tools/en/tools/token-creator">Token Creator</a> sets up metadata correctly from the first step. If you want to replicate an existing token’s setup as a starting point, <a href="https://j.tools/en/tools/token-clone">Token Clone</a> handles that.</p><p>Once your metadata is confirmed correct and you’re ready to commit to it permanently, <a href="https://j.tools/en/tools/make-immutable">Make Immutable</a> locks all remaining authorities in one step, metadata included. This is the strongest trust signal available, but only worth using once everything above has actually been checked.</p><h3>The Bottom Line</h3><p>Token metadata is what everyone actually sees, the name, the logo, the links, and none of it lives in the same place as the token’s supply or decimals. It stays editable for exactly as long as you hold update authority, and not one transaction longer.</p><p>Check what’s currently set before you assume it’s right. Fix what needs fixing while you still can. And treat revoking update authority or going immutable as the last step in the process, not an early one, since there’s no undo once it’s done.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools/"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88ca87c5873a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Reclaim SOL Locked in Empty Token Accounts on Solana]]></title>
            <link>https://blog.blockmagnates.com/how-to-reclaim-sol-locked-in-empty-token-accounts-on-solana-8de751172b92?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8de751172b92</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[solanas]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Thu, 20 Aug 2026 13:07:47 GMT</pubDate>
            <atom:updated>2026-09-11T07:08:41.229Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Every token you’ve ever held on Solana left something behind. A small deposit, sitting in an account you probably forgot exists. Across enough wallets, that forgotten SOL adds up to a real amount sitting completely idle.</em></p><figure><img alt="Dozens of small glowing capsules cracking open and releasing locked SOL that streams into one collected pool" src="https://cdn-images-1.medium.com/max/1024/1*4_6JWgA2LtRBQBOEcZZ_CQ.jpeg" /></figure><p>If you’ve been active on Solana for any length of time, whether trading, testing tools, launching tokens, or managing multiple wallets, you almost certainly have SOL locked away in empty token accounts you’re not using anymore. It’s not lost. It’s not at risk. It’s just sitting there, unclaimed, because closing these accounts isn’t something most people think to do.</p><p>This guide covers what token account rent actually is, why it accumulates, and how to reclaim it, individually or across hundreds of wallets at once.</p><h3>Why Solana Token Accounts Lock SOL</h3><p>Every SPL token account on Solana requires a small SOL deposit to exist on-chain. This is called rent, and it’s roughly 0.002 SOL per account. It’s not a fee you pay and lose, it’s a refundable deposit that covers the account’s storage cost on the network.</p><p>Here’s where it becomes relevant: every time you receive a new token for the first time, whether you bought it, someone sent it to you, or a tool created a token account on your behalf, Solana creates a new token account for that specific token in your wallet, and that 0.002 SOL gets locked into it. If you later sell the entire balance or transfer it all out, the token balance goes to zero, but the account itself, and the SOL locked inside it, stays exactly where it is unless you explicitly close it.</p><p>Nobody closes these automatically. Wallets don’t prompt you to clean them up. So they just accumulate.</p><h3>Where This Adds Up Fastest</h3><p>For a casual trader who’s bought a handful of tokens over the years, this might be a few dozen empty accounts and a fraction of a SOL. Not urgent, but not nothing either.</p><p>For anyone operating at scale, it adds up much faster:</p><p><strong>Multi-wallet operators.</strong> If you run trading or distribution strategies across dozens or hundreds of wallets, every wallet that touched a token even once has a token account for it. Wallets used for a single bundle buy, a one-time airdrop claim, or a test transaction all leave rent behind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fMk0VdU64IlKT4bEu_Ka5w.jpeg" /></figure><p><strong>Token testers and builders.</strong> Anyone experimenting with token creation, minting test tokens on devnet-adjacent workflows, or trying multiple token configurations accumulates empty accounts fast.</p><p><strong>Bundle and launch wallets.</strong> Wallets used once for a coordinated buy at a token launch, then never touched again, are a common source of dozens of stranded token accounts across an operation.</p><p><strong>Airdrop recipients and community reward claimants.</strong> If you’ve ever claimed a token from a large community airdrop, checked out a new meme coin that went nowhere, or interacted with a project that later abandoned its token, that account is still sitting in your wallet holding rent, indistinguishable from any other dead balance until you actually go looking.</p><p><strong>200 empty accounts × 0.002 SOL each = 0.4 SOL reclaimable.</strong></p><h3>Is Closing an Account Safe?</h3><p>The short answer is yes, as long as the account is genuinely empty or you’ve deliberately chosen to burn its remaining balance.</p><p>Closing a token account doesn’t affect your wallet’s SOL balance, your other token holdings, or any active positions elsewhere. It only removes the specific account record for that one token and returns the rent deposit tied to it. If you ever receive that same token again in the future, Solana simply creates a fresh account for it, with a new rent deposit, exactly as it did the first time.</p><p>The only thing to be careful about is closing an account that still holds a meaningful token balance you actually wanted to keep. This is why Close Account defaults to <strong>Only Empty</strong>, so a zero-balance account is the only thing selected unless you explicitly switch to Burn &amp; Close and confirm the dialog that comes with it.</p><h3>How to Reclaim It</h3><p><a href="https://j.tools/en/tools/close-account">Close Account</a> is built specifically for this. It scans your wallet (or many wallets at once), finds every SPL and Token-2022 account eligible for closure, and reclaims the locked rent in batched transactions.</p><p><strong>Choose a scan mode.</strong> Wallet Scan loads every closable account in your connected wallet. Multi Wallet lets you paste up to 1,000 private keys and scans across all of them in one terminal, which is the relevant mode if you’re cleaning up an operation spread across many wallets rather than just your main one.</p><figure><img alt="A holographic terminal showing token accounts closing one by one and releasing reclaimed SOL into a collection vessel" src="https://cdn-images-1.medium.com/max/1024/1*mc25zMMF3_AkQr-EHRnigw.jpeg" /></figure><p><strong>Review the scanned rows.</strong> Each row shows the token, its balance, the reclaimable rent, and the owning wallet’s SOL. Empty accounts (zero token balance) are pre-selected automatically, since those are the straightforward closures.</p><p><strong>Handle accounts that still hold a token balance.</strong> Some token accounts aren’t empty, they hold a small dust balance from an old position or a failed sell. By default, the tool only closes accounts with a zero balance. If you want to close accounts that still have tokens sitting in them, switch to <strong>Burn &amp; Close</strong>, which burns the remaining balance and closes the account in one pass, behind a confirmation dialog so it doesn’t happen by accident.</p><p><strong>Pick who pays gas.</strong> The connected wallet sponsors gas by default, meaning wallets with zero SOL can still be closed. You can also have each wallet pay its own gas, or route everything through a dedicated fee payer wallet, useful when you’re closing accounts across many low-balance wallets that couldn’t otherwise afford the transaction fee themselves.</p><p><strong>Choose where the rent goes.</strong> You can consolidate all reclaimed SOL to your connected wallet, return each account’s rent to its original owner wallet, or send everything to a single custom address of your choosing.</p><p><strong>Execute and retry failures.</strong> Click Close Selected Accounts. If any rows fail, Retry Failed reruns just those rows without touching the ones that already succeeded.</p><h3>What It Costs</h3><p>The tool charges a 5% fee on the rent actually reclaimed, and only on success. If a row fails to close, there’s no fee on that row, since nothing was recovered. There’s no charge for scanning or for accounts you choose not to close.</p><p>For the earlier example, closing 200 empty accounts at 0.002 SOL each reclaims 0.4 SOL, and the fee on that batch is 0.02 SOL, leaving 0.38 SOL back in your control.</p><p>Scanning is free and shows the exact reclaimable amount before you commit to anything, so there’s no downside to running a scan just to see what’s sitting in a wallet you haven’t cleaned up in a while.</p><h3>Verifying What Happened</h3><p>Every closed account produces a transaction, and the tool shows a per-row status as each one confirms. If you want to double-check on-chain, the transaction signature for any closed row is enough to look it up on a block explorer like Solscan, where you’ll see the account closure and the SOL transfer back to wherever you routed the rent.</p><p>If a handful of rows fail while the rest succeed, that’s normal for large batches, usually a timing issue or a temporary RPC hiccup rather than anything wrong with the account itself. Retry Failed reruns exactly those rows without re-scanning or re-selecting everything from scratch.</p><h3>If You’re Cleaning Up an Operation, Not Just One Wallet</h3><p>For anyone managing multiple wallets as part of a token launch, trading operation, or testing process, closing accounts is usually one step in a broader cleanup pass, not a standalone task.</p><p>If some of those wallets still hold small leftover token balances you want to preserve rather than burn, move them out first with <a href="https://j.tools/en/tools/batch-collector">Batch Collector</a>, which sweeps SOL or tokens from many wallets into one, before running Close Account on what’s left behind.</p><p>If the leftover balances are dust you don’t need, <a href="https://j.tools/en/tools/burn-tokens">Token Burner</a> reduces the supply first, which pairs naturally with a Burn &amp; Close pass afterward.</p><h3>The Bottom Line</h3><p>Token account rent isn’t a fee you lose, it’s a deposit that sits locked until you explicitly reclaim it, and most wallets never prompt you to do that. If you’ve been on Solana for any length of time, especially across multiple wallets, there’s a reasonable chance you have SOL sitting idle in accounts you haven’t touched in months.</p><p><a href="https://j.tools/en/tools/close-account">Close Account</a> scans for exactly this, whether it’s your main wallet or a batch of a thousand, and reclaims it in a few clicks. Given the fee only applies to what’s actually recovered, running a scan costs nothing to find out what’s there.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools/"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8de751172b92" width="1" height="1" alt=""><hr><p><a href="https://blog.blockmagnates.com/how-to-reclaim-sol-locked-in-empty-token-accounts-on-solana-8de751172b92">How to Reclaim SOL Locked in Empty Token Accounts on Solana</a> was originally published in <a href="https://blog.blockmagnates.com">Block Magnates</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is a Bundler in Crypto? How Bundle Buying Works on Solana (And How to Spot One)]]></title>
            <link>https://medium.com/@Jtools_Official/what-is-a-bundler-in-crypto-how-bundle-buying-works-on-solana-and-how-to-spot-one-977b9add3b04?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/977b9add3b04</guid>
            <category><![CDATA[memecoins]]></category>
            <category><![CDATA[solanas]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Mon, 17 Aug 2026 11:30:00 GMT</pubDate>
            <atom:updated>2026-08-17T11:30:00.213Z</atom:updated>
            <content:encoded><![CDATA[<p><em>“Bundled” shows up in almost every meme coin post-mortem thread. Half the time it means a smart launch. The other half it means the supply was quietly controlled from block one. Here’s how to tell the difference.</em></p><figure><img alt="A glowing bundle of transaction blocks fusing together into one atomic Solana block, representing bundle buying" src="https://cdn-images-1.medium.com/max/1024/1*euh5LME6gYT00r2S_bJ2lQ.jpeg" /></figure><p>If you’ve spent any time in Solana meme coin chat, you’ve seen someone accuse a token of being “bundled” right after it crashed. The word gets thrown around as an accusation, but bundling itself is not inherently bad. It’s a specific technical mechanism, and whether it’s a legitimate launch protection or a setup for a rug depends entirely on who controls the bundle and what they do with it.</p><p>This guide covers what a bundler actually is, how bundling works on Solana specifically, why creators use it legitimately, how it gets abused, and how to check whether a token you’re looking at was bundled at launch.</p><h3>What Is a Bundler in Crypto?</h3><p>A bundler is a tool or service that groups multiple transactions together so they execute as a single atomic unit, landing in the same block. Instead of transactions racing independently through the mempool where anyone can see them and react, a bundle submits everything at once, and either the whole bundle succeeds or none of it does.</p><p>On Solana, this is done through Jito, a block engine that lets you submit a bundle of transactions with a tip to validators for priority inclusion. The bundle lands in one slot, atomically. If any transaction in the bundle fails, the entire bundle reverts. Nothing partially executes.</p><p>That atomicity is the entire point. It’s what separates a bundle from just sending a bunch of transactions quickly one after another.</p><h3>What Does “Bundled” Mean for a Meme Coin Launch?</h3><p>When people say a meme coin was “bundled,” they usually mean one of two things, and the distinction matters a lot.</p><figure><img alt="Split visualization comparing a transparent, orderly wallet cluster against a concealed, tangled ownership network" src="https://cdn-images-1.medium.com/max/1024/1*Fb5nus51X_FBszM16WM7DA.jpeg" /></figure><p><strong>Legitimate bundling</strong>The token creator uses a bundler to launch the token and buy into it from multiple wallets in the same block as creation. The creator’s own buys land at the same instant the token goes live, before any external trader can front-run the creator’s own purchase. The wallets are typically disclosed or at least traceable to the launch, and the goal is protecting the launch from snipers.</p><p><strong>Manipulative bundling</strong>A bundler is used to quietly split a large ownership stake across many wallets that look unrelated on a basic holder list. Ten wallets each holding 2% of supply looks like healthy distribution if you only check the holder count. If those ten wallets were all funded from the same source and bought in the same bundle, it’s actually one entity holding 20% of supply, capable of dumping it all at once.</p><p>The mechanism is identical in both cases. What differs is transparency and intent.</p><h3>How Bundling Actually Works on Solana</h3><p>Here’s the technical sequence for a typical bundled launch:</p><ol><li>The creator prepares a token creation transaction and a set of buy transactions from multiple wallets.</li><li>All of these transactions get packaged into a single Jito bundle.</li><li>A tip is attached to the bundle to incentivize the validator to include it with priority.</li><li>The bundle is submitted. If it’s accepted, token creation and every buy in the bundle land in the same slot, in the same block, atomically.</li><li>If any single transaction in the bundle would fail (for example, a wallet doesn’t have enough SOL), the entire bundle reverts. There’s no partial launch where some buys go through and others don’t.</li></ol><p>This is fundamentally different from a creator manually creating a token, then rushing to buy it themselves a few seconds later. In that gap, a sniper bot watching new token creations can beat the creator to the first buy, front-run the entry, and extract value that should have gone to the person actually launching the project.</p><h3>Why Creators Use Bundling Legitimately</h3><p>The primary legitimate use case is sniper protection. Without bundling, the moment a token is created on Pump.fun, automated bots scanning for new mints can buy in before the creator’s own transaction lands, sometimes within the same second. Bundling closes that gap entirely by making creation and the creator’s buy inseparable.</p><p><a href="https://j.tools/en/tools/pumpfun-create-and-bundle-buy">Pump.fun Create &amp; Bundle Buy</a> is built around this exact workflow. You configure the token (name, symbol, description, image), set a creator buy amount, and add up to 16 bundle wallets with their own buy amounts. Everything, including the token creation and every wallet’s buy, submits as one deterministic Jito bundle. If any wallet in the bundle can’t complete its buy, the whole launch reverts, so there’s no scenario where the token goes live with a broken or partial bundle.</p><p>The tool also includes a Jito tip preset (Default, High, Ultra, or custom), which determines how much priority the bundle gets during validator block production. A higher tip increases the odds the bundle lands exactly where intended.</p><p>This is meaningfully different from bundling used to disguise ownership concentration. A creator buy through a transparent tool, at a known amount, from a launch wallet, is a normal part of managing a launch. The problem starts when the same mechanism is used to hide who actually controls the supply.</p><h3>How to Check If a Token Was Bundled at Launch</h3><p>Given that bundling can go either way, the practical question is: how do you check?</p><p>A standard holder list won’t tell you. It shows wallet addresses and balances, not which wallets are connected. Ten wallets holding 2% each look identical to a healthy distribution whether they’re ten independent buyers or one entity split across ten wallets.</p><figure><img alt="A holographic sphere showing linked wallet clusters on a token holder map, with the creator wallet marked in red" src="https://cdn-images-1.medium.com/max/1024/1*HFNEtoMlplOKcSDczfXpZw.jpeg" /></figure><p><a href="https://j.tools/en/tools/j-map">J Map</a> is built to answer exactly this question. Paste a token’s mint address and it maps the top holders as clusters, sized by their share of supply. Wallets that funded each other or moved tokens between each other get colored the same, so a coordinated group stands out visually instead of hiding inside a flat list. The creator wallet is marked in red, and its outgoing flow is traced separately so you can see exactly where the dev’s tokens went after launch.</p><p>The read is straightforward: if you see one large single-color cluster sitting near the top of the holder list, that’s the signal to look closer. Ten unrelated wallets holding 2% each is a distribution. Ten linked wallets holding 2% each is one holder with 20%, and that’s the concentration that actually matters for risk, not what the raw holder count suggests.</p><p>J Map is free to use and requires no wallet connection. You paste an address or pick a token from the trending rail, and the scan runs against on-chain data with no signing involved. The scan covers up to the top 500 holders, and because the token stays in the URL, you can share the exact map with someone else just by sending the link.</p><p>A large cluster by itself doesn’t automatically mean a token is a scam. Some clusters are teams managing shared treasury wallets, or a single early buyer who split their position for tax or risk reasons. What the cluster map gives you is the information to ask the right question, rather than being blind to concentration that a plain holder list conceals.</p><h3>If You’re Launching: How to Bundle Correctly</h3><p>If you’re the one launching a token and want the sniper-protection benefit without the reputational risk of an opaque bundle, the setup matters.</p><p><strong>Keep the creator buy proportional.</strong> A creator buy that takes an excessive share of supply looks identical to malicious bundling from the outside, even if your intent was just protecting the launch. Set it at a level you’d be comfortable disclosing.</p><p><strong>Use a small, disclosed set of wallets rather than dozens of disconnected ones.</strong> Pump.fun Create &amp; Bundle Buy supports up to 16 bundle wallets. Using that capacity to disguise a large concentrated position across many wallets is the exact pattern that shows up red on a cluster map later. Using it to protect a reasonable, transparent launch buy is the intended use.</p><p><strong>Expect to be checked.</strong> Tools like J Map are public and free. Anyone can map your launch after the fact. Launching in a way that would look fine under that scan is a good practical filter for whether your bundle setup is reasonable.</p><h3>The Bottom Line</h3><p>A bundler is a mechanism, not a verdict. On Solana, it means grouping token creation and multiple wallet buys into one atomic Jito bundle that lands in the same block, protecting a launch from snipers who would otherwise front-run the creator’s own buy.</p><p>Whether a specific bundle was a smart launch or a setup for a dump depends on transparency and proportion, not on the fact that bundling happened at all. The only way to actually check is to look past the holder list and at the connections between wallets, which is exactly the gap a cluster map closes.</p><p>If you’re launching, <a href="https://j.tools/en/tools/pumpfun-create-and-bundle-buy">Pump.fun Create &amp; Bundle Buy</a> gives you the sniper-protection mechanism with transparent, deterministic execution. If you’re evaluating a token someone else launched, <a href="https://j.tools/en/tools/j-map">J Map</a> shows you whether the holder base is actually distributed or quietly concentrated in a coordinated cluster.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools/"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=977b9add3b04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Route Funds from Many Solana Wallets to Many Destinations Through Relay Hops]]></title>
            <link>https://medium.com/@Jtools_Official/how-to-route-funds-from-many-solana-wallets-to-many-destinations-through-relay-hops-edefd2ac5f9b?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/edefd2ac5f9b</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[solanas]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Wed, 12 Aug 2026 19:26:55 GMT</pubDate>
            <atom:updated>2026-08-12T19:26:55.585Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Every direct transfer on Solana leaves a clear on-chain link between sender and receiver. When you’re managing dozens of wallets, those links add up fast. Multi-to-Multi Relay breaks each connection into a chain of intermediate hops, automatically, for every pair in the same run.</em></p><figure><img alt="Multiple parallel relay chains routing funds through glowing intermediate hop nodes from source wallets to destinations on Solana" src="https://cdn-images-1.medium.com/max/1024/1*C3j2MvHUH92oR23pyG1b8g.png" /></figure><p>Running multiple wallets on Solana means dealing with a problem that gets worse as your operation grows. Every direct transfer from wallet A to wallet B creates a permanent, public record of that exact connection. For token teams managing launch wallets, operational wallets, and treasury wallets, those direct links can expose your full structure to anyone reading the chain.</p><p>The standard workaround is routing funds through intermediate wallets before they reach the final destination. Each intermediate step is called a hop. Instead of A sending directly to B, A sends to an intermediate wallet, which sends to another, which eventually reaches B. The path is still on-chain, but the direct link between origin and destination is replaced by a chain of smaller, unrelated-looking transfers.</p><p>Doing this manually for one pair is tedious. Doing it for ten or twenty pairs simultaneously is impractical. <a href="https://j.tools/en/tools/multi-to-multi-relay">Multi to Multi Relay</a> handles the whole setup automatically: you define the source and destination pairs, set the hop depth and delay, and the tool generates the intermediate relay wallets, routes each pair through its own chain, and shows you every hop live as it executes.</p><h3>What “Relay” Actually Means</h3><p>A relay on Solana is a transfer that travels through one or more intermediate wallets before reaching its destination. Each intermediate wallet is generated fresh, receives the funds, and immediately passes them forward. The wallet exists only for that relay run.</p><p>The number of intermediate steps is the relay depth. A depth of 10 means the funds touch 10 intermediate wallets before arriving at the destination. A depth of 100 means 100 steps. More hops means a longer path between origin and destination, but also more transactions and more fees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_jXcAP2220v65_Qzj2U_Q.png" /></figure><p>Multi to Multi Relay extends this concept to multiple pairs in a single run. Each source-destination pair gets its own independent relay chain. The sources don’t share intermediates with each other. Pair one runs its own route. Pair two runs a separate route. They execute in parallel inside the same session.</p><h3>How It Compares to the Other Transfer Tools</h3><p>Before setting anything up, it helps to know where Multi to Multi Relay fits alongside the other transfer tools.</p><p><a href="https://j.tools/en/tools/many-to-many">Many to Many</a> sends directly from N source wallets to N destination wallets with no intermediate hops. One transaction per pair. Fast, transparent, useful when you don’t need the relay path.</p><p><a href="https://j.tools/en/tools/relay-transfer">Relay Transfer</a> routes a single source through a configurable hop chain to a single destination. One pair, one route.</p><p><a href="https://j.tools/en/tools/multi-to-multi-relay">Multi to Multi Relay</a> combines both: multiple pairs, each with its own relay route running in the same session. If you need relay routing for more than one source-destination pair at the same time, this is the tool.</p><h3>Setting Up: Source Wallets</h3><p>Click <strong>+ Add Source Wallets</strong> to import the wallets you’re sending from.</p><p>Each source row follows this format:</p><pre>privateKey,amountMode,amountValue</pre><p><strong>Amount modes:</strong></p><ul><li><strong>All:</strong> sweeps the full available balance from that wallet. Leave the amount field empty or set to 0.</li><li><strong>Fixed:</strong> sends an exact amount you specify. Set amountValue to the number of SOL or tokens.</li><li><strong>Percentage:</strong> sends a percentage of the current balance. Set amountValue to a number between 1 and 100.</li></ul><p>Once imported, each wallet shows its current SOL balance and token balance in the row. Warnings appear immediately if a row has a missing private key, an invalid amount, or a format error.</p><p>The source count and destination count must match exactly. The tool pairs them by index: source row 1 goes to destination row 1, source row 2 goes to destination row 2, and so on. If the counts don’t match, a warning shows before you can execute.</p><h3>Setting Up: Destination Wallets</h3><p>Click <strong>+ Add Destinations</strong> to import the receiving wallet addresses.</p><p>These are public keys only, not private keys. One address per row. The tool matches them to source wallets by position in the list, so order matters. If you have 20 source wallets, you need exactly 20 destination addresses, in the intended pairing order.</p><p>The pair statistics panel shows the source row count, destination row count, total matched pairs, and any unmatched warnings. Confirm this panel before moving to the next step.</p><h3>Relay Depth: How Many Hops</h3><p>The relay depth controls how many intermediate wallets each pair travels through before reaching its destination. Preset options are 10, 50, 100, 250, 500, 1k, and 2.5k. You can also set a custom value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXmq0bYtEk23fOsAaSiSsw.png" /></figure><p>The global depth applies to all pairs in the run. If you want different depths for specific pairs, you can override per row using the input next to each source wallet after importing.</p><ul><li><strong>10 hops</strong> is fast and cheap. Each pair takes 10 transactions to complete. Useful for routine operational transfers where you want some separation without high cost.</li><li><strong>50–100 hops</strong> adds meaningful distance between origin and destination. Suitable for most use cases.</li><li><strong>500–1k+ hops</strong> creates a long, complex route. Cost increases proportionally since the platform fee is charged per hop across all pairs.</li></ul><p>The summary panel shows the total operation count (pairs multiplied by relay depth) and the estimated platform fee before you execute. Check this before starting.</p><h3>Timing: Delay Between Hops</h3><p>The delay setting controls how long the tool waits between each hop within a pair’s route.</p><p><strong>Fixed Delay</strong> waits the same number of seconds between every hop. Predictable pacing, straightforward to reason about.</p><p><strong>Random Delay</strong> adds a variable wait between each hop. The randomness means no two hops in a run have identical timing, which makes the transfer pattern less regular when viewed on-chain.</p><p>For most runs, a small fixed delay (1–2 seconds) is enough to avoid congestion issues. Increase the delay if you’re running deep relay chains and want to pace the load on the network.</p><h3>Priority Fee</h3><p>Priority fee is the tip you pay Solana validators to prioritize your transactions during network congestion.</p><ul><li><strong>None:</strong> no tip. Fine during low-activity periods, may slow down or stall during high congestion.</li><li><strong>Normal / Fast / Express:</strong> progressively higher tips. Express makes sense when you need every hop to land quickly and you’re running a large number of pairs.</li><li><strong>Custom:</strong> set your own tip amount.</li></ul><p>For large runs with high relay depth during active market periods, Fast or Express reduces the chance of individual hops stalling mid-chain.</p><h3>Executing the Run</h3><p>When your sources, destinations, depth, delay, and priority fee are configured:</p><ol><li>Review the <strong>Summary panel</strong>: total pairs, relay depth, total operations, estimated send amount, network fee, platform fee, and total cost.</li><li>Click <strong>Execute Multi Relay</strong>.</li></ol><p>The progress table updates live as the run proceeds. Each row shows the pair number, hop number, the sending wallet, the receiving wallet, the amount, the status, the transaction signature, and any error. You can see exactly where each pair is in its route at any moment.</p><p>If a specific hop fails, the error column shows the reason. The pair may stall at that hop while others continue.</p><h3>The Recovery File</h3><p>When execution starts, the tool automatically downloads a recovery wallet file. This file contains the private keys of all the intermediate relay wallets generated for the run.</p><p>Keep this file. If a pair gets stuck mid-chain because of a failed transaction or network issue, the intermediate wallet holds the funds at that point in the route. The recovery file is the only way to access those intermediate wallets and retrieve any stranded funds.</p><p>The file is downloaded once, at the start of the run. If you close the tab before saving it, you lose access to the recovery keys.</p><h3>Fee Structure</h3><p>The platform fee is <strong>0.00023 SOL per hop</strong>. Total cost depends on three numbers: number of pairs, relay depth per pair, and priority fee.</p><p>Example: 10 pairs, 100 hops each = 1,000 total hops × 0.00023 SOL = 0.23 SOL in platform fees, plus network fees for each transaction. The summary panel calculates this for you before execution.</p><p>For deep relay runs with many pairs, review the total cost estimate carefully before starting.</p><h3>When to Use Multi to Multi Relay</h3><p><strong>Managing multi-wallet project operations:</strong> If your token project uses separate wallets for different functions (launch, marketing, team, treasury) and you need to move funds between those sets without creating obvious direct links between each pair, Multi to Multi Relay handles all the routing in one session.</p><p><strong>Separating incoming and outgoing wallets:</strong> When you’ve used a set of wallets publicly and want to move their balances to a fresh set without direct transfers connecting the two groups, relay routing breaks those direct links.</p><p><strong>Consolidating after a multi-wallet trading run:</strong> After a <a href="https://j.tools/en/tools/multi-swap">Multi Swap</a> session across many wallets, routing proceeds to destination wallets through relay chains rather than direct sweeps.</p><p><strong>Running large batches that would be impractical one at a time:</strong> If you need relay routing for 20 or 50 pairs, doing each one individually in Relay Transfer would take 20 or 50 separate sessions. Multi to Multi Relay runs them all together.</p><h3>The Bottom Line</h3><p>Multi to Multi Relay is the bulk version of relay routing on Solana. You define the pairs, set the depth and delay, and the tool handles the intermediate wallet generation, the hop sequencing, and the live tracking for every pair simultaneously.</p><p>The key things to confirm before executing: pair counts match, relay depth and total cost are within your plan, and the recovery file is saved as soon as the run starts. Everything else is visible in the progress table as each hop lands.</p><p>If you only need to relay one pair, use <a href="https://j.tools/en/tools/relay-transfer">Relay Transfer</a>. If you need direct paired transfers without hops, use <a href="https://j.tools/en/tools/many-to-many">Many to Many</a>. If you need relay routing across multiple pairs in a single run, this is the tool for it.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools/"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edefd2ac5f9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 5 Solana Token Creation Tools Ranked (2026)]]></title>
            <link>https://medium.com/@Jtools_Official/top-5-solana-token-creation-tools-ranked-2026-5d291d209c2f?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d291d209c2f</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[solanas]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Sat, 08 Aug 2026 13:00:59 GMT</pubDate>
            <atom:updated>2026-08-08T13:00:59.167Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Not every token creation tool on Solana does the same thing. Some stop at minting. Some stop at launch. One covers everything that comes after. Here’s how they actually compare.</em></p><figure><img alt="Five ranked medals floating in space representing the top 5 Solana token creation tools, with the #1 medal glowing brightest" src="https://cdn-images-1.medium.com/max/1024/1*x1bp27tAS8-Qt1SkdX-X4w.png" /></figure><p>Launching a token on Solana in 2026 takes about two minutes. The harder question is not how to launch it. It’s what happens next. Which tool handles the liquidity pool? Which one lets you manage your holder distribution? Which one gives you wallet analytics, multi-wallet trading, and authority management after launch? Most tools answer one of those questions. A few answer two. Only one answers all of them.</p><p>This ranking covers five of the most widely used token creation tools on Solana today. Each is evaluated on what it actually does, what it does well, and where it runs out of road.</p><p>★ Best Overall</p><h3>J Tools</h3><p>J Tools is the only platform on this list that covers the entire token lifecycle: creation, launch, liquidity, distribution, analytics, and wallet management, all in one place, all non-custodial.</p><figure><img alt="jtools website" src="https://cdn-images-1.medium.com/max/1024/1*EpQTmYiGS7mhQw2XY0nbGQ.png" /></figure><p>The tool count alone tells part of the story: over 40 tools available across the full range of on-chain operations. But the more meaningful difference is what those tools let you do in combination.</p><h3>Token Creation</h3><p><a href="https://j.tools/en/tools/token-creator">Token Creator</a> handles standard SPL token creation with full metadata support. <a href="https://j.tools/en/tools/token2022-creator">Token2022 Creator</a> adds the Token-2022 extension features: Transfer Fees, Interest-Bearing, Non-Transferable, Permanent Delegate, and more. <a href="https://j.tools/en/tools/token-clone">Token Clone</a> lets you replicate an existing token’s structure as a starting point. <a href="https://j.tools/en/tools/vanity-token">Vanity Token</a> generates a token address that starts with a custom prefix, which no other tool on this list offers.</p><h3>Launch</h3><p><a href="https://j.tools/en/tools/pumpfun-create">Pumpfun Create</a> launches a token directly to Pump.fun’s bonding curve. <a href="https://j.tools/en/tools/pumpfun-create-and-bundle-buy">Pumpfun Create and Bundle Buy</a> does the same while simultaneously executing coordinated buys from multiple wallets in the same transaction bundle, providing frontrun protection at launch. This combination is not available anywhere else.</p><h3>Liquidity</h3><p><a href="https://j.tools/en/tools/create-lp">Create LP</a> sets up liquidity pools on Raydium, Orca, and Meteora. <a href="https://j.tools/en/tools/liquidity-add-remove">Liquidity Add/Remove</a> manages existing positions. <a href="https://j.tools/en/tools/my-pools">My Pools</a> gives you a consolidated view of all your active LP positions. No other tool on this list has LP creation or management.</p><h3>Distribution</h3><p><a href="https://j.tools/en/tools/multi-sender">Multi Sender</a> sends tokens to thousands of addresses in one run. <a href="https://j.tools/en/tools/token-snapshot">Token Snapshot</a> exports your full holder list with balances for any token. <a href="https://j.tools/en/tools/holder-booster">Holder Booster</a> increases genuine holder count through controlled distribution.</p><h3>Trading</h3><p><a href="https://j.tools/en/tools/multi-swap">Multi Swap</a> executes buy or sell orders across hundreds of wallets simultaneously with auto venue routing across Pump.fun, PumpSwap, Raydium, Orca, and Meteora. <a href="https://j.tools/en/tools/bundled-trade">Bundled Trade</a> packages multiple swap instructions into a single atomic bundle. <a href="https://j.tools/en/tools/swap">Swap</a> covers single-wallet trading with the same venue routing.</p><h3>Wallet Management</h3><p><a href="https://j.tools/en/tools/wallet-generator">Wallet Generator</a> and <a href="https://j.tools/en/tools/vanity-wallet-generator">Vanity Wallet Generator</a> create new wallets with custom prefixes. <a href="https://j.tools/en/tools/batch-collector">Batch Collector</a> sweeps SOL or tokens from many wallets into one. <a href="https://j.tools/en/tools/many-to-many">Many to Many</a> handles complex multi-wallet transfers. <a href="https://j.tools/en/tools/close-account">Close Account</a> shuts down empty token accounts and reclaims the rent deposit.</p><h3>Analytics</h3><p><a href="https://j.tools/en/tools/wallet-scope">Wallet Scope</a> runs balance checks, PnL analysis, and wallet classification across hundreds of addresses simultaneously. <a href="https://j.tools/en/tools/j-map">J Map</a> visualizes funding connections between wallets and detects coordinated groups. These features are not available on any other token creation or management platform.</p><h3>Authority Management</h3><p><a href="https://j.tools/en/tools/revoke-mint">Revoke Mint</a>, <a href="https://j.tools/en/tools/revoke-freeze">Revoke Freeze</a>, <a href="https://j.tools/en/tools/revoke-update-authority">Revoke Update Authority</a>, and <a href="https://j.tools/en/tools/make-immutable">Make Immutable</a> handle authority cleanup at every level. <a href="https://j.tools/en/tools/update-metadata">Update Metadata</a> lets you correct token metadata before revoking that authority. <a href="https://j.tools/en/tools/burn-tokens">Burn Tokens</a> and <a href="https://j.tools/en/tools/token-mint">Token Mint</a> cover supply adjustments for tokens where those authorities are still active.</p><h3>What None of the Others Have</h3><p>Every other tool on this list requires you to leave the platform the moment you need something beyond their core function. CreateMyCoin creates the token, then you’re done. Streamflow locks it, then you’re done. Pump.fun launches it on a bonding curve, then you’re done. Bitbond creates the token with extension features, then you’re done.</p><figure><img alt="Four holographic panels displaying token creation interfaces for the four runners-up in the Solana tool comparison" src="https://cdn-images-1.medium.com/max/1024/1*_rBKRXHLeP4LKDGjYbvFMw.png" /></figure><p>J Tools is the only platform where you can go from token creation to LP creation, to holder snapshot, to multi-wallet trading, to wallet analytics, without switching tools or platforms at any point. Everything is non-custodial. Private keys used in multi-wallet tools never leave the browser tab. No accounts required. No custody of your tokens or SOL at any point.</p><h3>Pump.fun</h3><p>Pump.fun is the dominant token launch platform on Solana. It processes more daily token launches than any other platform on the chain and has generated over $834 million in lifetime revenue. The mechanism is simple and effective: create a meme coin, launch it on a bonding curve, and if it reaches $69,000 market cap it migrates to PumpSwap with locked liquidity.</p><p>The fair launch model removes pre-mines, team allocations, and private sales from the equation, which is a meaningful protection for early buyers. For meme coin launches specifically, Pump.fun is fast, widely used, and deeply integrated with discovery feeds and trading terminals.</p><p>The limitations are structural. Pump.fun is designed for bonding curve meme coin launches and nothing else. You cannot create a utility token with custom supply and authorities. You cannot create a Token-2022 token. There is no LP management, no wallet analytics, no snapshot tooling, no multi-sender, no authority revocation workflow for SPL tokens. The bonding curve determines your token’s entire price discovery phase. Once a token graduates to PumpSwap, Pump.fun’s direct involvement ends.</p><p>If your use case is a meme coin launch and you understand the bonding curve model, Pump.fun does that extremely well. If your use case is anything more structured than that, it’s the wrong tool.</p><h3>Streamflow</h3><p>Streamflow occupies a different part of the stack than a typical token creator. Its focus is token distribution: vesting schedules, token locks, airdrops, staking, and payments. Token minting is available but it’s the entry point, not the main event.</p><p>The vesting tooling is genuinely strong. Streamflow supports linear, cliff, graded, milestone, and price-based vesting, covering almost any allocation structure a project might need. Token locks are immutable once deployed and produce a public proof link verifiable on Solscan. Large-scale airdrops are supported up to one million recipients simultaneously. The platform is used by over 1.3 million users and 40,000 projects, with contracts audited by FYEO and OPCODES.</p><p>For projects that need serious tokenomics infrastructure (multi-tranche vesting for investors, locked team allocations, staking pools), Streamflow is purpose-built for that. The trade-off is that it’s not a trading tool, a wallet tool, or a liquidity tool. If you need to create a liquidity pool after you’ve locked your team allocation, Streamflow sends you somewhere else. It handles distribution of tokens you already have, not the broader lifecycle of operating a token on-chain.</p><h3>Token Tool by Bitbond</h3><p>Bitbond’s Token Tool takes a broader technical approach. It supports SPL Token and Token-2022 on Solana and brings in advanced token features that most no-code tools don’t touch: Transfer Fees, Interest-Bearing Tokens, Non-Transferable Tokens, Permanent Delegates, Transfer Hooks, and Enhanced Metadata. These Token-2022 extension features open up use cases around compliance, fee-generating tokens, and controlled distribution.</p><p>The multi-chain angle is Bitbond’s main selling point. Token Tool supports 11 blockchains including Ethereum, Polygon, BNB Chain, Avalanche, Base, Arbitrum, XRPL, and Solana. For teams that need to deploy on multiple chains from a single interface, this is a real advantage.</p><p>Where Token Tool falls short is on the Solana-specific side of post-launch operations. Airdrop and multi-sender functionality is listed as “coming soon” for Solana. Liquidity pool creation is not available. There are no trading tools, no wallet analytics, no holder management features. If your project is Solana-only and you need more than token creation, Token Tool gets you started but leaves the rest to other platforms.</p><h3>CreateMyCoin</h3><p>CreateMyCoin is a no-code token creator that does one thing cleanly: it gets a basic SPL token live on Solana mainnet in under 60 seconds. You connect a browser wallet, fill out a form with name, symbol, supply, and decimals, and the token is created. IPFS metadata hosting is handled automatically, social links are supported, and one-click authority revocation is available after launch.</p><p>The flat fee is 0.1 SOL with no hidden charges, which makes it one of the more transparent options for simple launches. Devnet testing is also available, which is useful for first-time creators.</p><p>The limitations are significant though. CreateMyCoin covers only token creation, nothing else. There is no liquidity pool creation. No token distribution tooling. No wallet management, no analytics, no trading. Once the token is minted, you’re on your own for everything that follows. For a team that just needs a token address and has separate tools for everything else, that’s fine. For anyone building a full launch workflow, it’s only the first step of a much longer process.</p><h3>The Bottom Line</h3><p>The right tool depends on what you actually need to do.</p><p>If you want to launch a meme coin on a bonding curve fast and reach the widest possible Solana audience on day one, Pump.fun is still the dominant choice for that specific use case. If you need vesting schedules and locked allocations for investors and team, Streamflow is built for that. If you need to deploy the same token across multiple blockchains, Bitbond’s multi-chain approach makes that straightforward. If you just need a token address created quickly with no additional requirements, CreateMyCoin does that cleanly and cheaply.</p><p>If you need to do any two of those things together, or any of them plus LP management, plus wallet analytics, plus multi-wallet trading, plus holder management, J Tools is the only platform that covers the full scope without sending you somewhere else.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools/"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d291d209c2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Buy or Sell a Solana Token From Hundreds of Wallets at Once]]></title>
            <link>https://medium.com/@Jtools_Official/how-to-buy-or-sell-a-solana-token-from-hundreds-of-wallets-at-once-ac70090868a4?source=rss-d6313b8497c1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac70090868a4</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[solanas]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[J Tools]]></dc:creator>
            <pubDate>Mon, 03 Aug 2026 17:11:43 GMT</pubDate>
            <atom:updated>2026-08-03T17:11:43.093Z</atom:updated>
            <content:encoded><![CDATA[<p><em>If you manage more than one wallet on Solana, you already know the problem. Every swap is a separate tab, a separate confirmation, a separate wait. Multi Swap runs all of them in one go.</em></p><figure><img alt="Hundreds of Solana wallets executing simultaneous token swaps through a central routing system" src="https://cdn-images-1.medium.com/max/1024/1*MqXF2yfsgjOsn_YWVcGHIQ.png" /></figure><p>Managing a single Solana wallet is easy. Managing ten is annoying. Managing fifty is a part-time job.</p><p>Token creators often end up with more wallets than they planned: a launch wallet, a team allocation wallet, a marketing wallet, wallets from earlier test runs, wallets used for bundle buys at launch. Traders who run multi-wallet strategies face the same thing. Every time you need to buy or sell a token across that whole set, you’re doing it one wallet at a time.</p><p><a href="https://j.tools/en/tools/multi-swap">Multi Swap</a> changes how that works. You load your wallets, pick a token, set your parameters, and execute across all of them simultaneously. Auto venue routing covers Pump.fun bonding curves, PumpSwap, Raydium, Orca, and Meteora, so the tool finds the right DEX for each swap automatically. Everything runs in one session, with a live terminal showing each transaction as it lands on-chain.</p><p>This guide walks through every part of the tool so you know what each setting does before you run anything.</p><h3>What Multi Swap Actually Does</h3><p>The core function is simple: execute a buy or sell of the same token across multiple wallets at the same time, without having to touch each wallet individually.</p><p>You bring your own wallets by importing private keys directly into the browser. The keys never leave your browser tab. There is no server-side key storage, no account required, no custody. Each transaction is signed locally and broadcast directly to the Solana network.</p><p>The auto venue setting means you don’t have to know whether a token lives on a Pump.fun bonding curve, a PumpSwap pool, or a Raydium AMM. The tool figures that out and routes each swap to the right venue. If you already know where the liquidity is, you can override and pick a specific venue manually.</p><h3>Setting Up: Operator Wallet and Wallets</h3><h3>Operator Wallet</h3><p>The first thing you’ll see at the top is the Operator Wallet field. This is the wallet that anchors your session for fee records and referral credit. It pays nothing here, it just identifies the session. Connect via Phantom or another browser wallet, or use Local Signer if you’re working with a keypair directly.</p><h3>Importing Wallets</h3><p>Click “Import Wallets” to bring in the wallets you want to trade from. Private keys are accepted here. Once imported, each wallet appears as a row in the table with its SOL balance and token balance displayed. You can refresh balances at any point.</p><p>The filter row gives you quick selection options: All, None, Invert, and Failed. If a previous run had some wallets fail, the Failed filter lets you isolate just those and retry without touching the successful ones.</p><p>Status tags update live during execution: Ready, Blocked, Confirming, Success, Failed. You can see exactly where each wallet is in the process at any moment.</p><h3>Token and Side</h3><h3>Buy or Sell</h3><p>The toggle at the top of this section switches between Buy and Sell. For a buy, you’re spending SOL to acquire the token. For a sell, you’re moving the token back to SOL.</p><h3>Selecting the Token</h3><p>Type a token name or paste the mint address directly into the field. The mint address is the most reliable way to make sure you’re targeting the right token, especially for newer tokens that might share similar names.</p><h3>Venue</h3><p>Leave this on Auto unless you have a specific reason to override it. Auto venue routing checks where liquidity actually exists for your token and routes accordingly. Manual venue selection makes sense when you know a token is exclusively on one platform and want to skip the routing check.</p><h3>Amount Settings</h3><p><strong>Fixed:</strong> Every wallet trades the exact same amount. Set to 0.05 SOL and every wallet in your selection buys with 0.05 SOL.</p><p><strong>Range:</strong> Each wallet trades a randomly selected amount within a minimum and maximum you set. Useful when you want variation across wallets rather than identical transaction sizes.</p><p><strong>% of Balance:</strong> Each wallet uses a set percentage of its current SOL balance. If you want every wallet to spend 50% of whatever it holds, this is the mode to use.</p><p><strong>Max:</strong> Each wallet uses its full available balance, minus the reserve held back for fees.</p><p><strong>The Reserve:</strong> Each wallet automatically keeps back approximately 0.009 SOL to cover the platform fee, network fees, and token account rent. You don’t set this manually. It’s held back automatically so transactions don’t fail due to insufficient fee funds.</p><h3>Execution Settings</h3><h3>Speed</h3><p>Three options: Careful, Normal, Turbo. Careful spaces out transactions and is more conservative with timing. Normal is the standard balanced setting. Turbo pushes transactions out faster and is suited for volatile moments when you want execution speed over caution.</p><figure><img alt="Holographic trading terminal showing Multi Swap execution settings including speed, slippage and priority fee controls" src="https://cdn-images-1.medium.com/max/1024/1*w707oqk9NilGkkiiTqTosQ.png" /></figure><h3>Slippage</h3><p>Auto lets the tool calculate appropriate slippage based on the current pool depth and price movement. Fixed options are 0.5%, 1%, and 3%. Custom lets you set any value. For most tokens with reasonable liquidity, Auto or 0.5% is fine. For low-liquidity tokens or large trade sizes relative to the pool, you may need to set a higher slippage tolerance to avoid failed transactions.</p><h3>Priority Fee</h3><p>Auto, Fast, Turbo, Ultra. This is the tip you’re paying Solana validators to prioritize your transactions during network congestion. Turbo costs approximately 0.001 SOL per transaction. Ultra makes sense during peak network activity when you need your transactions to land ahead of others.</p><h3>Interval</h3><p>Off by default. When enabled, Fixed adds a set delay between transactions. Random adds a variable delay. Intervals are useful when you want to spread execution over time rather than hitting all wallets at once, for example if you’re distributing buys across a window to avoid obvious clustering.</p><h3>Relay (Jito Tip)</h3><p>Off by default. Jito is a block engine on Solana that bundles transactions and offers MEV protection. Enabling a Jito relay tip routes your transactions through Jito’s infrastructure. This adds a small extra tip but can improve landing rates during congested periods and reduces the risk of sandwich attacks on your swaps.</p><h3>Running the Swap</h3><p><strong>Simulate First.</strong> Before running a live swap, use the Simulate button. Simulation runs through the logic without broadcasting real transactions. It shows you which wallets would succeed, which would be blocked, and what the expected output would be per wallet. Running a simulation before a real execution is the best way to catch issues before any SOL moves.</p><p><strong>Start Multi Swap.</strong> Once you’re satisfied with the simulation, hit Start Multi Swap. The button shows the number of selected wallets in brackets. The terminal at the bottom updates in real time as each transaction is submitted and confirmed. Every transaction includes a Solscan link so you can verify each one on-chain as it lands.</p><p><strong>Pause and Stop.</strong> Pause halts new transactions while letting in-flight ones finish. Stop cancels the queue entirely. Both are available mid-run if something doesn’t look right.</p><p><strong>Retry Failed.</strong> After a run, any wallets with a Failed status can be retried in isolation using the Retry Failed button. This avoids re-running the entire set when only a few wallets had issues.</p><p><strong>Export CSV.</strong> When the run is complete, Export CSV generates a full record of the session: wallet addresses, transaction hashes, amounts, statuses, and Solscan links. Useful for record-keeping or for sharing results with a team.</p><h3>Cost</h3><p>The platform fee is 0.0035 SOL per transaction. DEX fees and price impact from the swap itself are separate and depend on the venue and pool conditions. The cost section shows you the platform fee per transaction before you run, so you can estimate total cost based on how many wallets you’re executing across.</p><h3>When to Use Multi Swap</h3><figure><img alt="Split scene showing a token creator and a trader both using multi-wallet swap execution on Solana" src="https://cdn-images-1.medium.com/max/1024/1*imAWXsuQ-7k3YUb-C4kPKQ.png" /></figure><p><strong>Token creators managing a multi-wallet launch:</strong> If you launched with bundle buys across multiple wallets and those wallets now hold a position you want to exit or adjust, Multi Swap runs the full set at once.</p><p><strong>Coordinated buy campaigns:</strong> If you want to accumulate a position across multiple wallets before a specific moment, set them all up, run a simulation, then execute when ready.</p><p><strong>Selling across a distributed holder set:</strong> If supply is spread across many wallets you control and you want to consolidate or exit, Multi Swap handles the full sell in one run rather than manually selling wallet by wallet.</p><p><strong>Testing before a real run:</strong> The Simulate function makes it useful even for smaller setups where you just want to verify that every wallet will execute cleanly before committing.</p><h3>The Bottom Line</h3><p>Multi Swap is built for anyone operating at a scale where single-wallet tools stop being practical. The combination of bulk execution, auto venue routing, simulation mode, and live terminal output covers the full workflow: check before you run, watch as it executes, verify on-chain after it finishes.</p><p>The private keys never leave your browser. The operator wallet pays nothing. Platform fee is 0.0035 SOL per transaction. Everything else depends on the settings you choose and the conditions at execution time.</p><p>If you’re managing more than a handful of wallets and executing the same swap across all of them, this is the tool that makes that practical.</p><p><em>This content is for educational purposes only and does not constitute financial advice. Always do your own research.</em></p><p><em>Tools referenced in this article are available at </em><a href="https://j.tools/"><em>j.tools</em></a><em>. Non-custodial, no private keys required.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac70090868a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>