<?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 Tommy Defi on Medium]]></title>
        <description><![CDATA[Stories by Tommy Defi on Medium]]></description>
        <link>https://medium.com/@josepatrick5u?source=rss-959029d079a3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WwuPdGgL5NrzmfqsDoTguQ.jpeg</url>
            <title>Stories by Tommy Defi on Medium</title>
            <link>https://medium.com/@josepatrick5u?source=rss-959029d079a3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:36:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@josepatrick5u/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[SunSwap swap failed and TRX fell? Read the charge]]></title>
            <link>https://medium.com/@josepatrick5u/sunswap-swap-failed-and-trx-fell-read-the-charge-9128e524a6a1?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9128e524a6a1</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto-exchange]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 15:16:05 GMT</pubDate>
            <atom:updated>2026-11-13T15:16:05.832Z</atom:updated>
            <content:encoded><![CDATA[<p>If a SunSwap transaction was included on TRON and failed, the TRX spent on Energy or Bandwidth is not refunded; the swap tokens remain in your wallet. The network charges for execution that already happened, even when a contract call ends unsuccessfully. The amount depends on whether the call reverted at a check or exhausted its Energy limit.</p><h3>Why did the failed swap still cost TRX?</h3><p>A failed swap still costs resources because TRON processes the contract call before it can know whether the swap will succeed. Energy pays for smart contract computation, while Bandwidth pays for transaction data. If your account’s available resources do not cover the amount used, TRON burns TRX to pay the shortfall.</p><p>The transaction runs until a contract check fails or the call runs out of Energy. On a revert, the contract’s state changes are rolled back, so the tokens being swapped stay in your wallet. But the Energy and Bandwidth already used are still charged. TRON Developer Hub’s Resource Model explains how resource consumption, the Energy fee limit, and charges for failed execution fit together.</p><p>The fee limit caps how much TRX can be burned for Energy on the transaction; it does not make a failed transaction free. A revert may use only part of the available Energy, while an out-of-Energy failure uses the Energy allowed for that call. The actual TRX cost also depends on how much Energy and Bandwidth your account had available from resources.</p><h3>How can I tell whether it reverted or ran out of Energy?</h3><p>The transaction details in a TRON explorer show the result, Energy used, and TRX burned. Those fields help distinguish a contract check that failed from a call that hit its Energy limit, and show how much resource use caused the wallet deduction.</p><p>Consider two otherwise identical swaps with the same token pair, amount, and fee limit. If the first reverts at a price or allowance check, it stops there and pays for the Energy used up to that point. If the second keeps executing but reaches its Energy limit, it consumes the Energy allowed for that call and fails there instead. The difference is where execution stopped, so the charges can differ even though neither swap completes.</p><p>A revert often points to a condition that was no longer true when the transaction ran: the price moved beyond your tolerance, the contract lacked sufficient token allowance, or the deadline expired. Reading the explorer’s result alongside Energy used helps identify which kind of failure to address before submitting again.</p><h3>What should I change before retrying?</h3><p>Fix the condition indicated by the failure before sending another swap. If the price moved past your tolerance, review the quoted output and tolerance; if allowance was insufficient, approve the needed amount; if the deadline expired, submit with a valid deadline. The relevant choice is the one that addresses the failed check, rather than simply repeating the same transaction.</p><p>Knowing <a href="https://note.com/clear_phlox4159/n/n4d06266dbd42">how to use SunSwap</a> can help you judge which swap settings to revisit, especially whether the quoted trade still fits your tolerance and deadline. If the explorer instead reports out of Energy, consider whether the fee limit allowed enough Energy for that call. Raising it may permit more computation, but it cannot fix a price, allowance, or deadline problem.</p><p>Retrying unchanged can repeat the same failure and charge. After making the relevant correction, submit again only when the transaction details and swap conditions match what you intend. If the first transaction failed, the swap tokens should still be in your wallet; the resource charge for that processed attempt will not be refunded.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9128e524a6a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where Your Tokens Go After a Failed Destination Swap]]></title>
            <link>https://medium.com/@josepatrick5u/where-your-tokens-go-after-a-failed-destination-swap-0b32a3ba475c?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b32a3ba475c</guid>
            <category><![CDATA[token]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin-mining]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 01:34:52 GMT</pubDate>
            <atom:updated>2026-11-12T01:34:52.938Z</atom:updated>
            <content:encoded><![CDATA[<p>To locate your tokens after a failed destination swap, read the swap transaction’s destination-chain outcome separately from the completed bridge delivery. If cBridge already delivered the tokens and a later swap transaction reverted, that revert does not undo the earlier delivery: the swap’s token changes roll back, but gas used by the failed transaction is still charged.</p><h3>Why a failed swap does not undo delivery</h3><p>A completed bridge delivery and a destination swap are separate transactions, so each has its own result. A confirmed delivery puts the tokens at your destination address; a later swap can attempt to spend them, but it cannot reverse the earlier transaction simply by failing.</p><p>A reverted transaction rolls back its state changes within that transaction. EIP-140, the Ethereum specification for the REVERT instruction, establishes that execution changes are discarded while unused gas is returned; gas already consumed remains charged. In practical terms, a failed swap should not leave its attempted token transfers in place, but the transaction fee is still paid.</p><p>A confirmed delivery is a completed transaction on the destination chain; <a href="https://telegra.ph/cBridge-What-to-Know-Before-Your-First-Transfer-11-06">cBridge transfers</a> therefore leave the delivered tokens at that address before a separate swap can spend them. Find the destination-chain address and token balance to establish where the bridged assets are now.</p><h3>How can you tell what happened to the swap?</h3><p>The swap transaction’s receipt and token movements show whether it completed, reverted, or is still unresolved. Use the destination chain’s transaction hash for the swap itself, not the earlier bridge delivery hash or an approval hash. An approval allows a contract to spend tokens; it is not the swap.</p><p>Ethereum’s JSON-RPC method eth_getTransactionReceipt returns a receipt once a transaction has been included in a block. Its status reports top-level success or failure. If there is no receipt, that alone proves neither outcome: the transaction may still be pending, may have been replaced by another transaction using the same account nonce, or may be unknown to the node you queried. Resolve that status before submitting another swap, since an uncertain transaction could still execute.</p><p>A wallet rejection or failed simulation can happen before broadcast. In that case, there is no on-chain swap transaction to revert and no swap gas charge. If you did broadcast the transaction, a receipt with failure status means the top-level transaction reverted; compare the destination token balances and transaction details to confirm the assets remain available.</p><p>A prior successful approval remains effective if the later swap reverts, unless it was separately changed or revoked. You may not need another approval, but confirm the allowance before retrying.</p><h3>What if the router transaction says success?</h3><p>A successful top-level receipt does not always mean the intended swap completed. Some router contracts catch an internal failure and continue, so the outer transaction can succeed even though the swap did not. Inspect the actual token flows and resulting balances: look for the expected input leaving your address and the expected output arriving. A success status without those movements is not enough to establish that you received the swap output.</p><h3>When is a retry justified?</h3><p>Retry only after the transaction outcome and token location are clear. For a confirmed revert, use the reported failure cause to correct the issue, then obtain a fresh quote before sending a new swap. The quote can change while you investigate, and the transaction may also have failed because its conditions were no longer met.</p><p>A failed later swap does not create a cBridge refund entitlement: the bridge delivery already succeeded, and the swap is a separate destination-chain action. Focus on the destination address and the swap’s own result rather than treating the swap failure as a bridge failure.</p><p>You have established the outcome when the destination address’s token balance and the swap receipt’s status agree with the transaction’s actual token movements. Together, those details confirm whether the assets remain available for a corrected retry or whether the intended swap output arrived.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b32a3ba475c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eigen Layer Deallocation Leaves a Slashing Window]]></title>
            <link>https://medium.com/@josepatrick5u/eigen-layer-deallocation-leaves-a-slashing-window-97461960a71d?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/97461960a71d</guid>
            <category><![CDATA[bitcoin-news]]></category>
            <category><![CDATA[litecoin]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 00:16:40 GMT</pubDate>
            <atom:updated>2026-11-12T00:16:40.408Z</atom:updated>
            <content:encoded><![CDATA[<p>When an operator deallocates your stake from a service in eigen layer, it remains slashable until the protocol-wide deallocation delay passes. That window lets the service report faults committed while the stake was assigned to it; exposure ends when the pending deallocation becomes effective, not when the operator submits it.</p><h3>Deallocation starts a waiting period</h3><p>A deallocation request does not immediately free the stake. The operator submits the request, and the affected amount remains pending and slashable during the delay. Once the delay elapses, that amount is freed from the service and its exposure to new slashing claims from that allocation ends.</p><p>Without this window, an operator could remove stake just after a fault and leave the service unable to slash it. The delay preserves the service’s opportunity to report a fault committed while the stake was allocated. For you, the key distinction is between the request being submitted and the deallocation taking effect.</p><p>Pending deallocations show an effective block in the allocation data. That block is the point at which the stake is due to become free after the delay. If you are deciding whether to exit or reassess your position, understanding <a href="https://jack-web3-news.mataroa.blog/blog/what-is-eigen-layer-delegation-to-an-operator/">what eigen layer delegation commits you to</a> helps clarify why an operator change does not by itself settle your existing exposure.</p><h3>Allocation and deallocation delays work differently</h3><p>A new allocation also takes time to become slashable, but its delay is set by the operator. The stake is not exposed to that service for slashing until the allocation delay has passed. By contrast, the deallocation delay is protocol-wide, so the operator cannot choose a shorter waiting period when removing stake.</p><p>These delays govern opposite transitions. Allocation timing determines when a service can begin relying on stake; deallocation timing determines how long the service retains a claim on stake already assigned to it. For example, if an operator allocates stake to a new service and later removes it after a reported fault, the service’s slashing window for that stake does not close at the moment of removal. The pending amount remains available for a claim until its effective block.</p><p>That timing matters when interpreting service news. A newly announced risk may justify reassessing an operator, but redelegating does not erase exposure to faults that occurred while your stake was assigned. The relevant question is whether the old allocation’s deallocation has taken effect, not simply whether your stake now appears headed elsewhere.</p><h3>Use the effective block to judge exposure</h3><p>To tell whether the old service can still slash the allocation, read the pending deallocation’s effective block and compare it with the current block. If the effective block has not passed, treat that amount as still exposed. Once it has passed, the deallocation delay has elapsed and the stake is freed from that service.</p><p>Use that status to time an exit or decide when to reassess the service risk: the effective block establishes whether the old allocation is still within its slashing window. Then review any new allocation separately, since it becomes slashable only after the operator-set allocation delay.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97461960a71d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tracking Fraxswap long-term order state]]></title>
            <link>https://medium.com/@josepatrick5u/tracking-fraxswap-long-term-order-state-b74338939846?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b74338939846</guid>
            <category><![CDATA[trading]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 02:46:28 GMT</pubDate>
            <atom:updated>2026-11-11T02:46:28.578Z</atom:updated>
            <content:encoded><![CDATA[<p>If you know which wallets or order IDs to monitor, combine pair event indexing with live contract reads to show each order’s progress without relying on an explorer. The events tell you when an order was placed, withdrawn, or canceled; pair reads reveal its current accounting, including proceeds available to claim.</p><h3>Discover pairs and index order events</h3><p>Start with the Factory address and RPC endpoint for each network you support, then use the Factory’s pair-creation records to find relevant pairs. For wallet-based tracking, identify the pairs those wallets use; for known orders, resolve each order ID to its pair. Long-term order state is held by the pair, so an order ID alone is not enough to make the right view call.</p><p>For every relevant pair, index long-term order placement, withdrawal, and cancellation events. Keep the pair address, order ID, owner, sell direction, sell rate, start and end information when available, and the latest event type and block. These records establish which orders to query and explain how their lifecycle changed.</p><p>Pair-level indexing matters because <a href="https://graph.org/How-Does-Fraxswap-Trading-Differ-From-an-Exchange-Account-11-06">how Fraxswap works</a> depends on AMM pair contracts for pool operations, including long-term orders. A Factory record helps you find the pair, while that pair’s events and view functions provide the order-level data your dashboard needs.</p><h3>Read current state and estimate progress</h3><p>Query each pair’s order view by order ID to get its stored accounting, such as sold amount, bought amount, and claimable proceeds. Treat these values as the contract’s stored state at the read block. Virtual fills can accrue continuously between transactions, but the pool updates its stored order state only when someone triggers virtual order execution. As a result, a view read may not include all progress since the last trigger.</p><p>Events alone cannot fill that gap: a running order does not emit an event for every virtual fill. If you display only the last placement event, its sold amount can remain unchanged even while the order’s expected sales grow. You can estimate expected sales as sell rate multiplied by elapsed time, using the order’s active interval. This estimate helps show progress between state updates; it is not a substitute for the pair’s accounting because execution timing and contract arithmetic affect the stored result.</p><ul><li><strong>Running:</strong> current time is before the order’s end, and its sell rate is active.</li><li><strong>Expired:</strong> the order’s end has passed; the rate has stopped, but proceeds may remain claimable.</li><li><strong>Withdrawn or canceled:</strong> use the event history and latest pair state to show the order’s lifecycle and any remaining claimable amount.</li></ul><p>These statuses describe different things: expiry ends selling, while withdrawal collects proceeds. Cancellation records a lifecycle change, so read the pair’s resulting order state rather than assuming the event alone gives final amounts.</p><h3>Reconcile claimable proceeds</h3><p>Use a proceeds-withdrawal simulation to verify the amount your dashboard labels claimable. Read the order state and simulate the relevant withdrawal against the same pair at the same block context; the simulation tests what the contract would return under that state. For example, if a monitored wallet’s order has expired but it has not withdrawn, the dashboard should show it as expired and display the proceeds the simulation indicates are available, not treat expiry as an automatic withdrawal.</p><p>Update stored state when new events arrive, and refresh pair reads as needed to account for virtual execution. The dashboard is ready when each order’s sold, bought, and claimable figures agree with a manual proceeds-withdrawal simulation, while its status distinguishes a stopped order from one whose proceeds have actually been withdrawn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b74338939846" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polygon bridge: what changes when you return with MATIC?]]></title>
            <link>https://medium.com/@josepatrick5u/polygon-bridge-what-changes-when-you-return-with-matic-0b3f61c89edd?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b3f61c89edd</guid>
            <category><![CDATA[bitcoin-news]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto-trading]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 00:50:30 GMT</pubDate>
            <atom:updated>2026-11-11T00:50:30.580Z</atom:updated>
            <content:encoded><![CDATA[<p>If you last bridged before the POL upgrade and still hold MATIC, first identify which network holds it: keep using POL for Polygon PoS gas, and migrate MATIC held on Ethereum if you want POL there. Polygon upgraded its native token, while Ethereum ERC-20 balances remain unchanged until you submit a migration transaction. Exchange balances follow each exchange’s conversion process.</p><h3>Does MATIC in my Polygon wallet need to be converted?</h3><p>No action is needed for the native gas balance on Polygon PoS: it upgraded automatically to POL. The wallet may still display “MATIC,” though, because its network settings can retain the old currency symbol. That label is display information; changing it does not convert a token or move funds.</p><p>Update the Polygon network’s currency symbol in your wallet to POL. In a custom network entry, this is usually an editable setting alongside the network name and chain details. Use the network’s existing settings and change only the symbol. Your balance should then be identified as POL, matching the token used to pay transaction fees on Polygon PoS.</p><p>This distinction matters when you resume a <a href="https://www.tumblr.com/calculatinggladiator/832518903122018304/which-bridge-route-sets-your-assets-wait">Polygon bridge</a> transfer: the network you are sending from determines which asset pays the gas. A stale MATIC label on Polygon may simply be a wallet display issue, while MATIC shown on Ethereum is still an ERC-20 token that has not been converted. The symbol alone cannot tell you which case you have.</p><h3>What should I do with MATIC held on Ethereum?</h3><p>Ethereum MATIC stays MATIC until you migrate it through Polygon’s official migration feature in Polygon Portal. The migration is one-to-one: it converts each eligible MATIC to POL, but requires an Ethereum transaction. Keep ETH in the wallet to pay that transaction’s gas; having POL on Polygon does not cover an Ethereum fee.</p><p>Use this order if you are preparing to bridge again:</p><ol><li>Change the Polygon PoS network’s currency symbol in your wallet to POL.</li><li>Look at your Ethereum wallet balance for MATIC held as an ERC-20.</li><li>If you want that balance in POL, open Polygon Portal yourself and use its migration feature. Review the transaction in your wallet before signing.</li><li>Bridge as usual, keeping some POL on Polygon for gas after the transfer.</li></ol><p>Be wary of unsolicited “migrate now” messages. Open Polygon Portal through a source you trust instead of following a message’s link, and confirm the transaction details in your wallet. If your MATIC is held on an exchange, the exchange controls whether and when it converts that balance; check its status and instructions before sending anything.</p><h3>Will the bridge steps or withdrawals work differently?</h3><p>The token upgrade does not by itself change the familiar bridge sequence: connect your wallet, choose the supported asset and direction, approve the token if prompted, then confirm the deposit. Approval is a separate permission transaction that lets the bridge contract use the token. Ethereum-side steps still need ETH for gas; Polygon PoS transactions now use POL for gas.</p><p>For a withdrawal from Polygon PoS to Ethereum, the usual checkpoint process still applies. A checkpoint records Polygon transactions so the withdrawal can be completed on Ethereum; it can take time before the next withdrawal step is available. The POL migration does not remove that wait or change the need to complete the withdrawal through the bridge flow.</p><p>Once your wallet shows POL for Polygon PoS and your Ethereum balance has no MATIC you intend to migrate, your labels and holdings are aligned for this routine. Revisit this advice if Polygon changes the native gas token or its official migration process: that would affect which token to keep for fees or how to convert an Ethereum balance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b3f61c89edd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can a teammate submit a cBridge refund without receiving it?]]></title>
            <link>https://medium.com/@josepatrick5u/can-a-teammate-submit-a-cbridge-refund-without-receiving-it-10b3edcd6583?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/10b3edcd6583</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[xrp]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 11:32:11 GMT</pubDate>
            <atom:updated>2026-11-10T11:32:11.139Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gE1r_9-BZI7llqlk.jpg" /></figure><p>If a pool-based transfer is ready for refund, assign one teammate to submit it and keep the refund receiver set to the account authorized in the refund data. The pool contract checks the signed withdrawal request and pays its encoded receiver; the account that pays source-chain gas does not become the recipient. This applies at contract level, though the frontend may limit which account can submit.</p><h3>Does the gas payer receive the refund?</h3><p>No. The submitter, the receiver named in the signed refund request, and the intended destination recipient can be different addresses. For a pool-based refund, the contract verifies the authorized withdrawal data, then transfers the tokens to the receiver encoded in that data. The operator’s wallet pays transaction gas, but that payment does not change the receiver.</p><p>That separation matters when a team uses <a href="https://dune.com/fansell_well/why-does-my-cbridge-transfer-show-a-refund-instead-of-delivery">cBridge</a> liquidity pools: the refund follows the authorized request, while an operator can handle the on-chain transaction. The operator still needs valid refund data and enough gas on the source chain. Treasury ownership by itself does not authorize a withdrawal, and the operator cannot change the receiver without changing the signed data.</p><p>For example, suppose a transfer’s refund data names the treasury wallet, but a teammate’s wallet is chosen to submit. If that teammate submits the valid request, the contract pays the treasury wallet. If someone edits the receiver to the teammate’s address, the request no longer matches the signed data and will fail verification. The gas payer has no way to redirect an already authorized refund just by submitting it.</p><h3>How should the team divide refund responsibilities?</h3><p>Separate review, execution, and receipt confirmation so each person checks a different part of the task:</p><ul><li><strong>Reviewer:</strong> Match the refund request to the original transfer and verify that its receiver is the expected treasury address.</li><li><strong>Operator:</strong> Submit the authorized request through a supported execution method, using an account funded for source-chain gas.</li><li><strong>Asset controller:</strong> Confirm the designated receiver obtained the tokens, or identify a queued release before closing the task.</li></ul><p>For instance, a reviewer can compare the transfer record and refund details before the operator sends the transaction. After submission, the controller checks the receiver’s balance or transaction status. A large withdrawal may be queued for delayed release under contract rules, so a successful submission does not always mean tokens appear immediately; the team should track that release before marking the refund complete.</p><h3>Can the operator always use a teammate’s account in the frontend?</h3><p>No. Contract-level permission to submit a valid request does not guarantee the cBridge interface will let an operator connect a different account from the original user. The team should confirm that its chosen execution method supports the operator’s wallet. Aggregator transfers and application-contract transfers can also have their own refund handling, so this process applies specifically to ready pool-based refunds.</p><p>When valid refund data is available and the execution method supports the operator, the team can delegate submission without handing over entitlement to the assets. The signed receiver determines where the contract sends tokens; the gas payer determines who pays to execute the transaction.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10b3edcd6583" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Does My App Keep Its Old RPC After Chainlist?]]></title>
            <link>https://medium.com/@josepatrick5u/why-does-my-app-keep-its-old-rpc-after-chainlist-1aec532f02bf?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1aec532f02bf</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[digital-currency]]></category>
            <category><![CDATA[trading]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 09:46:29 GMT</pubDate>
            <atom:updated>2026-11-10T09:46:29.885Z</atom:updated>
            <content:encoded><![CDATA[<p>Changing the wallet’s RPC changes an app read only when that read is sent through the wallet provider; a separately configured application client keeps its own route. The deciding detail is which component sends the request, not which network the wallet displays. A prototype using one provider can hide this split until reads and transactions use separate clients.</p><h3>Which connection sends the balance request?</h3><p>The balance request follows the transport configured on the client that makes it. For example, your app may ask a public client to read an address’s balance on Arbitrum, while a wallet client handles transaction signing. The public client’s transport could be an HTTP URL; the wallet client sends requests through the browser wallet’s provider.</p><p>Chainlist can help configure the wallet’s network connection, which matters for requests delegated to that wallet. The <a href="https://qiita.com/felixblevi/items/059539a5f103466d4dfe">Chainlist wallet connection</a> is the wallet side of this arrangement; it does not automatically replace the URL in your app’s separate HTTP client.</p><p>A single-provider prototype can make the distinction easy to miss: both reads and transactions appear to go through the same connection. Once you create separate public and wallet clients, their roles become explicit. Viem’s “Introduction to Clients and Transports” describes clients with explicit transports and distinguishes public-client actions from wallet-client actions.</p><h3>What changes when the wallet uses a new RPC?</h3><p>The wallet’s endpoint change affects requests sent through its provider. EIP-1193, the Ethereum Provider JavaScript API specification, defines the provider interface applications use to submit requests to a wallet. If your balance read uses that interface, it can follow the wallet’s changed connection.</p><p>But if your app calls its own HTTP client, that client continues calling its configured URL. The wallet may show the expected network and successfully read a balance through its provider while the app’s public client still queries an old endpoint. Each request goes where the component that initiated it sends it.</p><p>Here is the boundary case: suppose the balance read works when routed through the wallet provider, but fails when the app makes a direct HTTP request. The wallet’s RPC setting cannot fix that direct route; the app’s client transport is the connection to inspect. If the read instead goes through the provider, the wallet’s connection is relevant.</p><h3>How do I find the connection responsible for a failed read?</h3><p>Trace the balance call from the code that initiates it to its client and transport. If it invokes a public client, find that client’s configured HTTP URL and determine whether the request reaches the intended network. If it invokes the wallet provider, inspect the wallet’s selected network and provider connection.</p><p>This distinction also rules out two common false leads. A wallet RPC change does not update an independent indexer that serves app data, or refresh data already held in a cache. If the balance call reads from either, identify that source and its own route or refresh behavior. The responsible connection is the one used by the component producing the failed value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1aec532f02bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Does SGN Confirmation Prove In A cBridge Transfer?]]></title>
            <link>https://medium.com/@josepatrick5u/what-does-sgn-confirmation-prove-in-a-cbridge-transfer-ed57a1241ad4?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed57a1241ad4</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[staking]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 12:56:05 GMT</pubDate>
            <atom:updated>2026-11-09T12:56:05.663Z</atom:updated>
            <content:encoded><![CDATA[<p>In a cBridge transfer, SGN confirmation means enough staked validator voting power has signed an attestation that your source-chain deposit occurred, authorising the destination contract to release funds. The contract checks those signatures rather than reading the source chain itself, so confirmation is validator-backed agreement, not independent proof of the deposit.</p><h3>What happens while SGN confirms the deposit?</h3><p>Your transfer starts with a deposit on the source chain. That deposit emits an event recording the transfer; SGN validators observe it and sign a transfer record. SGN is a separate proof-of-stake network, where validators stake CELR. Their signatures attest that the event occurred and identify the transfer the destination should process.</p><p>Once the signatures carry enough voting power to meet the required threshold, they can be accepted by the destination contract. The threshold is about the validators’ stake behind the signatures, not simply a headcount. Until that condition is met, the transfer remains at the confirmation stage: the destination has not yet accepted the attestation and released the funds.</p><h3>Does confirmation prove the source deposit happened?</h3><p>No. It says that enough SGN voting power attests to the deposit; it does not mean the destination independently verified the source-chain event. The source-side situation is unchanged: the deposit happened there, and its event is what validators report. What changes after threshold signatures are accepted is the destination contract’s decision to release funds.</p><p>That distinction helps when interpreting the status message. “Waiting for SGN confirmation” means the destination is waiting for qualifying validator signatures, not that delivery has already happened. For practical context about the other roles involved, <a href="https://telegra.ph/cBridge-Transfer-Participants-and-Who-Handles-Your-Tokens-11-06">who does what in a cBridge transfer</a> relates this validator step to the user, source and destination chains, and the liquidity used to complete a transfer. Confirmation is one part of that process, not the whole transfer.</p><h3>What are you trusting when signatures pass?</h3><p>You are trusting that the validators controlling enough staked voting power observed the deposit and signed its record honestly. The destination relies on that signed record because it checks validator signatures rather than source-chain state directly. A valid set of signatures therefore establishes that the SGN threshold was met; it does not, by itself, establish that the deposit is true.</p><p>The key security condition is that a supermajority of validator stake behaves honestly. If a colluding supermajority signed a false transfer record, it could authorise a release without the deposit the record claims. This is the limit of the attestation model: the security of the destination decision depends on the honesty of the stake behind the signatures.</p><h3>Why do validators have a reason to sign honestly?</h3><p>Validators stake CELR, which gives them an economic reason to report deposits accurately. Slashing can put that stake at risk when validators violate the network’s rules. That consequence is a deterrent, not a mathematical proof that every signature is truthful; it cannot remove the risk posed by a supermajority that chooses to collude.</p><p>So, when confirmation completes, you rely on a threshold of staked SGN validators attesting to your deposit, and on the destination contract accepting their signatures. The release follows from that attestation, not from the destination independently checking the source chain. Knowing this tells you both what confirmation commits to and the condition its security depends on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed57a1241ad4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flashbots Protect as Default, Except for Urgent Transfers]]></title>
            <link>https://medium.com/@josepatrick5u/flashbots-protect-as-default-except-for-urgent-transfers-744c964268d6?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/744c964268d6</guid>
            <category><![CDATA[crypto-mining]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 11:47:19 GMT</pubDate>
            <atom:updated>2026-11-09T11:47:19.518Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xmogwkIysI1rHX2e.jpg" /></figure><p>If you are switching RPCs before each wallet transaction, keep Protect as your default for routine Ethereum mainnet activity. Ordering risk matters most when a transaction’s result can be improved by getting ahead of it, as with a swap or mint; fixed transfers and approvals usually offer little to extract. For a time-critical transfer, a public RPC may confirm sooner.</p><h3>Ordering risk comes from someone else’s profit</h3><p>MEV, or maximal extractable value, is value someone can gain by changing the order of transactions or including or excluding them in a block. The ethereum.org entry “Maximal extractable value (MEV)” identifies DEX trades and liquidations as examples where transaction ordering can expose value. The practical test is whether another party could profit by acting before, after, or around your transaction.</p><p>A swap with slippage or a minimum-output limit has a result that depends on what trades happen around it. A searcher may profit by placing a trade before yours and another after, changing the price you receive. Mints can also be sensitive to ordering when access or price changes as transactions land. Protecting these transactions can reduce exposure to that kind of front-running.</p><p>Protect is one transaction-routing choice within the broader question of <a href="https://note.com/cute_snipe8938/n/nc067f7b322c4">what Flashbots does for Ethereum users</a>. The article’s broader subject is the project and its uses; here, the relevant part is whether a particular transaction benefits from private routing.</p><h3>Transfers and approvals usually have little to extract</h3><p>A fixed-amount transfer to a known address normally sends the same amount regardless of transaction order. A token approval grants a spender permission up to a specified allowance; by itself, it usually does not create a profitable trade for someone to place around your transaction. These actions generally have less ordering-dependent value than swaps or liquidations.</p><p>That does not make them a reason to switch back and forth. Flashbots Protect can remain enabled for routine transfers and approvals too, and private routing costs nothing extra. If the goal is fewer wallet decisions, the small chance of slower inclusion is often easier to live with than remembering to change RPCs before the next swap.</p><h3>Choose a routine you can follow</h3><p>If you swap or mint regularly, keeping Protect as the default is the lowest-effort routine: it covers the transactions most exposed to ordering risk without requiring a choice each time. Switching only for swaps can save a little time on some simple transactions, but it adds a step and creates a chance you forget to switch back before a risky transaction.</p><ul><li><strong>Protect as the permanent default:</strong> lowest effort per transaction and less risk of forgetting; private routing may occasionally take longer to include a transaction.</li><li><strong>Protect only for swaps:</strong> may suit someone who rarely makes ordering-sensitive transactions and is comfortable changing RPCs; it requires a decision before each relevant action.</li></ul><p>In your wallet, look for the RPC or network endpoint setting and leave the Protect endpoint selected for ordinary mainnet activity. When a transaction has a slippage tolerance or minimum received amount, that is a useful sign the outcome depends on surrounding trades and deserves protection.</p><h3>Use public routing when timing matters most</h3><p>Private routing sends transactions to a narrower set of builders than public-mempool broadcasting. That can reduce who sees a pending transaction, while also limiting the routes through which it can reach a block; inclusion can occasionally take longer. The same privacy that helps with ordering risk therefore comes with a possible speed trade-off.</p><p>For an urgent transfer where confirmation time matters more than front-running protection, a public RPC may confirm sooner. Otherwise, leaving Protect on avoids per-transaction switching and covers swaps, mints, and other actions whose outcomes can change with transaction order.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=744c964268d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Small Test’s Limits Before a Larger Swap]]></title>
            <link>https://medium.com/@josepatrick5u/a-small-tests-limits-before-a-larger-swap-f2a7e4a27117?source=rss-959029d079a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2a7e4a27117</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Tommy Defi]]></dc:creator>
            <pubDate>Sat, 07 Nov 2026 04:18:43 GMT</pubDate>
            <atom:updated>2026-11-07T04:18:43.028Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GSpSspVUVgcV5A9y.jpg" /></figure><p>A small test can confirm that your wallet and a particular trade path worked for a modest amount at that moment, if your concern is completing the workflow; it cannot prove that a larger trade will be safe or execute at the same rate.</p><h3>A test receipt confirms one transaction, not the whole plan</h3><p>Before sending a larger amount, decide what you need the test to answer. If you have not used the wallet or network before, a small swap can show that you selected the intended tokens, approved the transaction, and received the output in the expected wallet. The receipt gives you evidence that those steps worked together for that transaction.</p><p>For example, imagine you are using Matcha swap to exchange a small amount of a token you already hold for an unfamiliar token. If the transaction settles and the output appears in your wallet, you have confirmed that this route worked at that time. You have not confirmed that the token is safe, that its contract will behave as expected later, or that the same path will be available for a larger trade.</p><h3>A larger amount can change the price and execution</h3><p>The test and the intended trade differ in size, and size can change the exchange rate. A larger order may use up more of the favorable liquidity available along its route, so the average execution price can move. This difference is called price impact. A small test’s rate is therefore a poor promise of what the larger trade will return.</p><p>Buying successfully also does not prove you can sell later. When you try to sell, liquidity, available routes, token rules, or market conditions may differ. A receipt proves that the buy completed; it does not establish that a sell will be possible at a price you accept. A receipt also does not resolve <a href="https://dailyblockchainnews.github.io/matcha-swap-how-routing-turns-a-token-trade-into-a-transaction/">how Matcha swap risks arise</a>, so contract behavior and future execution remain open questions even after the first transaction succeeds.</p><p>That makes a test useful as workflow evidence, but weak evidence about scale. If your uncertainty is whether you can operate the wallet and verify the received tokens, the test can answer it. If your concern is the larger trade’s price, the test’s smaller size leaves that question unanswered.</p><h3>Choose a test only when its information is worth its cost</h3><p>A test adds another transaction cost and briefly exposes funds to the market. The cost can include network fees and any applicable swap fees; the amount varies with the network and transaction conditions. Its value depends on whether the result would change your decision. If a successful receipt would settle a genuine wallet-operation concern, that information may be worth the extra transaction. If you already know the workflow and are worried about liquidity or a token’s contract, the test does little to resolve the concern.</p><p>For an unfamiliar wallet flow, keep the test small enough that the cost and exposure are acceptable, then verify the transaction receipt and the token balance before deciding what to do next. For an identity or contract concern, seek evidence about the token itself before trading. For liquidity, assess the intended amount and its expected execution conditions; a small test cannot stand in for that evidence.</p><p><strong>Would a small test trade make my larger Matcha swap safer?</strong> It can reduce uncertainty about the workflow, but it cannot establish safety or predict larger-trade execution. If workflow is the issue, a test may be useful; if the concern is token safety or scale, look for evidence that directly addresses it before committing more.</p><p>The test is worth making when it answers a specific operational question at an acceptable cost. Because amount and timing affect what the receipt can demonstrate, treat success as confirmation of that one transaction — not as assurance about the larger trade.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2a7e4a27117" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>