<?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 Matt Day on Medium]]></title>
        <description><![CDATA[Stories by Matt Day on Medium]]></description>
        <link>https://medium.com/@h06183113?source=rss-49867a138cc3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Matt Day on Medium</title>
            <link>https://medium.com/@h06183113?source=rss-49867a138cc3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:44:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@h06183113/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[Should Polygon Bridge Tokens Be Standard or Mintable?]]></title>
            <link>https://medium.com/@h06183113/should-polygon-bridge-tokens-be-standard-or-mintable-9744b3fe3150?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9744b3fe3150</guid>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[layer-2]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 01:24:47 GMT</pubDate>
            <atom:updated>2026-11-12T01:24:47.610Z</atom:updated>
            <content:encoded><![CDATA[<p>If a project issues its token only on Ethereum, standard mapping fits; if it issues tokens on Polygon, mintable mapping lets those tokens reach Ethereum on withdrawal. The deciding factor is where supply originates. Mintable mapping also depends on the Ethereum token granting the bridge predicate permission to mint.</p><h3>How Do Standard and Mintable Mappings Affect Supply?</h3><p>Standard mapping keeps the token’s original supply on Ethereum: Polygon tokens are copies backed by Ethereum tokens locked in the bridge predicate, the contract that holds assets for bridging. As a result, the Polygon-side supply equals the number of tokens held in that predicate.</p><p>That backing relationship is one part of a <a href="https://izcrypto.mataroa.blog/blog/polygon-bridge-one-deposit-test-first-or-move-in-stages/">Polygon bridge transfer</a>: Ethereum tokens are locked, and corresponding tokens become available on Polygon. The mapping describes how the token is represented across the two networks; it does not change the basic role of the transfer itself.</p><p>Mintable mapping allows tokens to be created on Polygon, then minted on Ethereum when they are withdrawn. That means Ethereum supply is no longer limited to the amount originally locked there. A token team choosing this setup is allowing bridge activity to create Ethereum supply under the predicate’s authority.</p><h3>Why Can Ethereum Supply Rise After Polygon Activity?</h3><p>With mintable mapping, a Polygon-issued token can arrive on Ethereum even when there are not enough Ethereum tokens locked in the predicate to release. The predicate mints the shortfall on Ethereum, so Polygon issuance can increase Ethereum’s total supply without a separate mint transaction from the project team.</p><p>For example, imagine a project issues 100 tokens on Polygon and a holder withdraws 30 to Ethereum. If the predicate holds 10 Ethereum tokens available for release, it can release those 10 and mint the remaining 20. The holder receives 30 on Ethereum; the additional 20 supply came from the predicate’s minting authority.</p><p>The key change is where those 30 tokens are represented: the holder moves them from Polygon to Ethereum. The key accounting difference is that some or all of the Ethereum-side amount may be newly minted rather than released from tokens already locked there. When reading supply data, distinguish the destination-chain mint from a new issuance the team made directly.</p><h3>What Must Be True for Mintable Withdrawals to Work?</h3><p>The Ethereum token must grant the mintable predicate permission to mint. Without that permission, the predicate cannot create the shortfall, so a withdrawal that depends on minting can fail even though the Polygon tokens exist.</p><p>This permission is a dependency, not a cosmetic setting in the mapping description. For mintable withdrawals to work, the token contract and predicate must already be set up so the predicate can mint the required amount. When reading token documentation, look for whether the predicate holds that minting role or equivalent authority; a statement that the asset is mintable does not by itself prove the permission is in place.</p><p>That authority also changes what a token team needs to audit. Under standard mapping, the central supply comparison is Polygon supply against tokens locked in the Ethereum predicate. Under mintable mapping, auditors also need to account for Ethereum mints made by the predicate as Polygon-issued tokens exit.</p><h3>Which Mapping Fits the Token’s Issuance Model?</h3><p>Choose based on the chain where the project creates supply. Standard mapping fits a token issued only on Ethereum, where Polygon copies are backed by locked Ethereum tokens. Mintable mapping fits a Polygon-first project whose Polygon-issued tokens need to be withdrawable to Ethereum.</p><ul><li><strong>Standard mapping:</strong> Ethereum remains the source of minted supply; Polygon supply tracks the tokens locked in the predicate.</li><li><strong>Mintable mapping:</strong> Polygon can be a source of issuance; the predicate may mint on Ethereum when those tokens are withdrawn.</li></ul><p>For supply reviews, an Ethereum supply increase with no matching team mint is a clue to investigate mintable exits. Compare the change with bridge withdrawals and predicate mint events before attributing it to new project issuance. That reading follows from the mapping’s mechanics: if Polygon-originated tokens reach Ethereum through predicate mints, Ethereum supply can rise as a result of bridge activity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9744b3fe3150" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Consolidating renBTC Before Selling From Multiple Wallets]]></title>
            <link>https://medium.com/@h06183113/consolidating-renbtc-before-selling-from-multiple-wallets-0b6af9d24543?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b6af9d24543</guid>
            <category><![CDATA[trading]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 00:07:49 GMT</pubDate>
            <atom:updated>2026-11-12T00:07:49.411Z</atom:updated>
            <content:encoded><![CDATA[<p>If you have renBTC in several wallets, consolidate only when the transfers cost less than the extra approval-and-swap pairs, and the combined balance is worth the gas. Selling from every wallet takes two transactions per wallet; consolidating takes one transfer per extra wallet, then two transactions from the wallet that holds the total.</p><h3>Count the transactions and their gas</h3><p>Selling separately takes 2 × N transactions for N wallets: each wallet approves the swap contract to spend renBTC, then submits the swap. Consolidating takes (N − 1) transfers, one approval, and one swap. A plain renBTC transfer usually uses less gas than an approval followed by a swap, so consolidation can save transaction costs as the number of wallets grows.</p><p>Compare current gas costs for each transaction type on the same chain. Multiply the separate route’s approval-and-swap cost by N. For consolidation, add the costs of N − 1 transfers to one approval and one swap. The lower total is the cheaper route, assuming the balances can be sold at similar prices.</p><p>Each sending wallet needs that chain’s native gas token, even for a simple transfer. A wallet with too little gas cannot move its renBTC by itself; funding it just to move a tiny balance may cost more than the balance is worth. Leave balances smaller than the gas for one transfer where they are.</p><h3>Include the swap size and the route</h3><p>One consolidated swap can cost less in gas yet get a worse price. If renBTC liquidity is thin, a larger swap may move the price more than several smaller swaps. Compare the quote for the combined amount with the quotes for each wallet’s amount, including any price impact shown by the swap interface.</p><p>RenBridge is relevant when the question is how BTC became renBTC across chains, rather than how to combine renBTC wallets on one chain. Its Bitcoin-to-renBTC route used RenVM to mint and burn wrapped assets; the <a href="https://www.tumblr.com/atomicgladiatoraltar/832525790495277056/how-did-btc-become-renbtc">RenBridge BTC transfers</a> distinction concerns cross-chain movement, while the calculation here is for ordinary same-chain transfers. RenBridge’s original service was sunset in 2022, so that history does not make a present-day wallet consolidation a cross-chain operation.</p><p>Think of each wallet as a separate checkout: selling separately repeats the approval and swap at each one, while consolidation pays a smaller transfer cost to bring the items to one checkout. The analogy stops at the fees, because a bigger combined swap can change the price you receive. You can now judge the cheaper route by comparing transaction gas, balance value, and the quote for the actual swap size.</p><h3>Questions about applying the choice</h3><h3>Can a smart contract wallet batch the approval and swap into one transaction?</h3><p>Sometimes. A smart contract wallet may bundle both actions into one submitted transaction if its software and the swap route support batching. The approval and swap still happen as separate contract actions, and the batch may use more gas than either action alone. Compare the wallet’s quoted total with the ordinary two-transaction route before choosing.</p><h3>Does moving renBTC between my own wallets create a taxable event?</h3><p>That depends on the tax rules where you file and your circumstances. A transfer between wallets you control may be treated differently from a sale, but keep records showing both addresses, the amount, date, and transaction ID. The later swap is a separate event to assess under your local rules.</p><h3>What can I do with renBTC in a wallet that holds no gas token?</h3><p>That wallet cannot normally send renBTC until it has the chain’s native gas token. You can send a small amount of native token from another wallet you control, then compare its cost with the renBTC’s value. If the swap service and wallet support a relayer or sponsored transaction, that may cover gas, but check its fee and supported assets before relying on it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b6af9d24543" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What does a reverted Matcha swap error mean?]]></title>
            <link>https://medium.com/@h06183113/what-does-a-reverted-matcha-swap-error-mean-250ff4c75499?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/250ff4c75499</guid>
            <category><![CDATA[yield-farming]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 02:26:03 GMT</pubDate>
            <atom:updated>2026-11-11T02:26:03.301Z</atom:updated>
            <content:encoded><![CDATA[<p>If the explorer shows a reverted status, the message usually identifies which route condition failed: output minimum, allowance or balance, token transfer, gas, or deadline. The contract stops when a required check fails, so the swap does not complete and its token transfers are rolled back. Wording varies by contract, and some failures expose no readable reason.</p><h3>What does the explorer actually tell me?</h3><p>A failed status confirms that the transaction was included but its execution did not finish successfully. Look for the revert message and gas used: the message may name the failed condition, while gas used helps distinguish an execution limit from other checks. A revert does not mean the swap happened partially; token transfers made within that failed transaction are undone.</p><p>Some explorers show a plain sentence, while others show a contract error name or encoded data that is not immediately readable. If no useful message appears, the status still tells you the transaction failed, but it may not identify why. Error wording also differs between contracts, so the same underlying cause can appear under different names.</p><h3>Which common causes match the message?</h3><p>Match the wording and gas pattern to the condition that stopped execution. The common clues are:</p><ul><li><strong>Output below minimum:</strong> the route could not deliver the minimum amount set by the slippage tolerance. The market price or available liquidity moved before execution, pushing the expected output below that floor.</li><li><strong>Allowance or balance:</strong> the contract was not approved to spend enough of the input token, or the wallet no longer held enough when the transaction ran. A balance can change between signing and confirmation.</li><li><strong>Transfer failed:</strong> the token refused or altered a transfer. Possible reasons include a blacklist, transfer restrictions, or a transfer tax that makes the route’s expected amount fail.</li><li><strong>Gas limit reached:</strong> gas used close to the transaction’s limit points to execution running out of gas. That differs from a price check failing, which normally stops at a contract condition.</li><li><strong>Deadline or expiry:</strong> the transaction arrived after the time limit encoded when it was signed, so the contract rejected it as too late.</li></ul><p>These are alternatives, but a transfer tax can also lead to an output check failing: the token delivers less than the route expects, and the minimum-output condition then stops the swap. The decisive clue is the actual failure message when it is available; gas usage is especially useful when it points to the execution limit.</p><h3>Am I looking at the right network’s transaction?</h3><p>Use the explorer for the chain where the transaction was submitted; an explorer on another network cannot show the relevant transaction. For a Matcha swap, <a href="https://crypto-news-acxov85we3jlc7qno0wii.justblogged.com/matcha-swap-how-retry-reverted-trade">Matcha swap supported networks</a> relates to identifying the network context before interpreting an explorer result. Network identity matters because each chain has its own transactions and token contracts.</p><p>Once you have the right transaction, compare its message with the clues above. An output-minimum error points to price movement relative to slippage settings; an allowance error points to approval or available balance; a transfer error points toward token behavior. Gas near the limit or an expiry message narrows the cause in a different direction.</p><h3>Does a revert mean my tokens or settings changed?</h3><p>For the failed swap transaction itself, the token exchange did not complete, and its in-transaction transfers were rolled back. That is why the input tokens can still appear in the wallet. A separate approval transaction, if one was made earlier, is independent and may remain in effect even though the swap reverted.</p><p>The error can therefore point either to a setting or to the token. Minimum-output and allowance messages describe checks the route could not satisfy; a transfer failure may reflect a restriction or tax in the token; gas and deadline messages describe execution conditions. Identify which condition failed first, because that is what explains the reverted transaction and what stayed unchanged.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=250ff4c75499" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Do I Share Chainlist Settings Without My RPC Key?]]></title>
            <link>https://medium.com/@h06183113/how-do-i-share-chainlist-settings-without-my-rpc-key-857bfb5eaf51?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/857bfb5eaf51</guid>
            <category><![CDATA[wallet]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[metamask]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 00:25:00 GMT</pubDate>
            <atom:updated>2026-11-11T00:25:00.164Z</atom:updated>
            <content:encoded><![CDATA[<p>Share the public network metadata and replace any credential-bearing RPC URL with a clearly labelled placeholder; each recipient must supply an endpoint they are authorized to use. The network settings identify where a wallet connects, while the provider credential can grant access against your account, so copying the whole configuration may share more than you intend.</p><h3>Which network settings can colleagues reuse?</h3><p>Colleagues can reuse the fields that describe the network itself, provided those values match the network you intend them to add. Typical public metadata includes:</p><ul><li><strong>Network name:</strong> A label that helps people recognize the network in their wallet.</li><li><strong>Chain ID:</strong> The identifier a wallet uses to distinguish the network; it is public, but should still be copied accurately.</li><li><strong>Currency symbol:</strong> The symbol displayed for the network’s native currency. It describes the network and does not authenticate a connection.</li><li><strong>Block explorer details:</strong> Public information that can help users view addresses and transactions, when included in the configuration.</li></ul><p>These fields do not give someone control of your wallet. A JSON-RPC URL serves a different role: it tells the wallet where to send requests to read network data or submit transactions. The URL may include a provider key, token, or other account-specific credential, so treat the entire URL as sensitive until you know it contains no personal access details.</p><h3>When does a Chainlist setup include personal access?</h3><p>When you use <a href="https://www.tumblr.com/volcaniccosmosworm/832830948655644672/approval-can-leave-an-existing-rpc-in-place">Chainlist</a> to find EVM network settings or add them to a compatible wallet, the network metadata and the RPC endpoint belong to different parts of the setup. The metadata describes the network; the endpoint connects the wallet to infrastructure that serves it. A provider URL containing your key can therefore be personal even when the network details beside it are public.</p><p>Consider two colleagues documenting the same network with the same chain ID and currency symbol. One uses a public endpoint that does not contain an account credential; the other uses a provider URL with a personal key. The shared metadata is identical, but publishing the second URL may let readers send requests under its owner’s account. Those requests can use up quota or encounter the owner’s usage limits. That exposure does not, by itself, reveal the wallet’s signing key or authorize someone to sign transactions as the owner.</p><h3>How should you prepare reusable instructions?</h3><p>Start with access to the provider configuration for the endpoint you use, and make sure recipients can obtain their own authorized RPC URL. Then separate the public network fields from endpoint authentication details before preparing the material.</p><ol><li><strong>Keep the public metadata:</strong> Copy the network name, chain ID, currency details, and other non-secret fields needed to identify the network.</li><li><strong>Replace the full RPC URL:</strong> Use a clear label such as <em>[Insert your own authorized RPC URL]</em>. Remove the whole credential-bearing URL rather than trying to edit out only a key; credentials may appear in different parts of a URL, and leaving part behind can still expose access.</li><li><strong>Tell recipients what to do:</strong> Explain where they should insert their own working endpoint in the wallet’s network form before saving. The placeholder documents which value is needed; it is not a functioning endpoint and cannot connect a wallet.</li><li><strong>Clean supporting material:</strong> Remove real credentials from screenshots, example requests, and attached logs as well as from the written settings. A key visible outside the main instructions is still exposed.</li></ol><p>For example, a screenshot that shows public metadata but replaces the RPC field with the placeholder is reusable. A screenshot of the same form with your provider URL visible is not, even if the surrounding instructions tell readers to use their own URL. People often copy examples literally, so make the example safe on its own.</p><h3>What should you review before sharing?</h3><p>Review every place the endpoint could appear and confirm that shared material contains public metadata and placeholders, with no live credentials. Look at the main instructions, screenshots, sample requests, and attached logs; search the text for recognizable provider URL patterns or key fragments if those are available. The decisive check is whether a reader could copy any shared value and send requests using your provider access.</p><p>If a credential has already been published, deleting the visible copy does not invalidate it. Use the provider’s configuration to revoke or rotate that credential, then update any remaining private setup that depended on it. Afterward, publish the cleaned instructions with a placeholder so each recipient connects through an endpoint tied to their own authorization and usage limits.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=857bfb5eaf51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Reconcile a Completed Bridge Transfer in Your Ledger]]></title>
            <link>https://medium.com/@h06183113/how-to-reconcile-a-completed-bridge-transfer-in-your-ledger-074766303fcc?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/074766303fcc</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum-blockchain]]></category>
            <category><![CDATA[dex]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 11:09:37 GMT</pubDate>
            <atom:updated>2026-11-10T11:09:37.597Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*87fn_MBFyD_Eqs4F.jpg" /></figure><p>To reconcile a completed cross-chain transfer, link its source debit and destination credit as one movement, then reconcile each wallet by chain and asset. The destination receipt is the asset arriving in another wallet; it does not mean you acquired additional holdings overall. Keep the source and destination receipts so the ledger shows both real legs.</p><h3>Identify Each Leg By Chain And Asset</h3><p>Match each entry using the wallet, chain, token contract, amount and transaction evidence. A ticker alone is not enough: tokens with the same ticker on different chains or at different contract addresses may be different assets. Record each amount in that asset’s own units, alongside the source and destination transaction receipts.</p><p>The transfer mechanics explain why the two amounts may differ. For background on the rate and fees that affect a transfer, <a href="https://policyledger.pages.dev/how-to-use-cbridge-to-move-tokens-between-chains/">cBridge</a> is relevant: the destination credit can be lower than the source debit. That difference is evidence to explain, not a reason to invent a matching amount or treat the receipt as a second acquisition.</p><h3>Link The Entries And Record Costs Once</h3><p>Use one reference for the completed movement, keeping both entries in the ledger:</p><ul><li><strong>Source leg:</strong> Record the actual amount debited, its chain and token contract, and its transaction evidence.</li><li><strong>Destination leg:</strong> Record the actual amount credited, its chain and token contract, and its receipt.</li><li><strong>Costs:</strong> Record actual bridge costs and explain the sending–receiving difference. Record gas as a debit from the wallet and native asset that paid it, including gas for an approval transaction.</li></ul><p>These entries describe different parts of the same movement. If the destination receipt is already net of a bridge cost, subtracting that cost from it again understates your holdings. Preserve the source debit and destination credit when removing duplicate imports; delete only the duplicate copy, not either genuine leg.</p><h3>Reconcile Closing Balances By Wallet</h3><p>For each chain and asset, calculate closing balance as opening balance plus credits minus debits. Include the transfer leg belonging to that wallet and chain, plus its other activity; count gas in the native asset used to pay it. The completed transfer is reconciled when those ledger balances match the corresponding wallet balances.</p><p>If the transfer is still pending, leave the movement unresolved until the destination receipt arrives. A swap or unrelated transaction needs its own entry, since it is not the other leg of this transfer. With both receipts linked, costs recorded once and balances checked separately, a difference between sent and received amounts can be explained without counting the destination receipt twice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=074766303fcc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Happens to a Matcha Swap After You Submit?]]></title>
            <link>https://medium.com/@h06183113/what-happens-to-a-matcha-swap-after-you-submit-84e6965401a8?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/84e6965401a8</guid>
            <category><![CDATA[dogecoin]]></category>
            <category><![CDATA[dex]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 09:22:51 GMT</pubDate>
            <atom:updated>2026-11-10T09:22:51.603Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gMGpA9sIVTY9UCTk.jpg" /></figure><p>If your wallet signed and submitted the swap, closing the tab will not stop it; the trade continues without the page open. The important distinction is whether the wallet actually approved and sent something, not whether the website is still showing progress.</p><h3>What Wallet Approval Changes</h3><p>Clicking the swap button on the site prepares the trade, but approving the wallet prompt is the step that authorizes it. If you clicked the site button and then closed the tab without approving the wallet prompt, nothing was sent, so there is no trade continuing in the background.</p><p>For a <a href="https://dev.to/earlene_feil/matcha-swap-who-holds-your-tokens-when-you-trade-41i6">Matcha swap</a>, the wallet is the useful checkpoint because the interface can assemble and display a trade, but the wallet approval is what lets it leave your device. After approval, a regular swap is submitted as a transaction to the network, such as Ethereum or Base, depending on the network you chose.</p><p>Once broadcast, the transaction waits for the network to process it. The open page can display that progress, but it does not keep the transaction alive. Closing the tab only removes that status display; it does not retract a transaction already sent.</p><h3>What Happens After You Close the Tab</h3><p>After a signed transaction has been broadcast, the network handles its confirmation whether or not your browser remains open. For a gasless order, the sequence differs: your wallet signs an order and, once that signature is submitted, execution happens off your device. In either case, the site is not required to stay open for the submitted trade to proceed.</p><p>This is why a vanished status is not evidence that the swap stopped. If the page closes before it shows a result, the transaction may still be pending, may have completed, or may have failed. The status display is useful, but the wallet activity or transaction record is the evidence to follow.</p><h3>How to Check the Result Safely</h3><p>Use your wallet’s activity list or the block explorer for the selected network to find the submitted transaction. A pending status means it has not finished processing; confirmed means it completed; failed means the network did not complete the swap. A transaction hash, when available, identifies the submission you are tracking.</p><p>If the activity is still pending, wait for that same transaction to resolve. Starting another Matcha swap just because the site no longer shows the first one can submit a second trade; the first may still confirm later. If no wallet approval occurred, there is no submitted transaction to track, and you can begin again when ready.</p><p>So, if by “confirming” you mean approving the wallet prompt and the submission appears in wallet activity, it is safe to close the browser. Reopen the site only if you want its status display; check the wallet or explorer to learn the actual outcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84e6965401a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Does Each cBridge Transfer Status Mean?]]></title>
            <link>https://medium.com/@h06183113/what-does-each-cbridge-transfer-status-mean-c386c2449a0b?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c386c2449a0b</guid>
            <category><![CDATA[altcoins]]></category>
            <category><![CDATA[dex]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 12:13:47 GMT</pubDate>
            <atom:updated>2026-11-09T12:13:47.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Op6StG_MKTWKKm6Z.jpg" /></figure><p>If your cBridge transfer has not reached completed, its history status tells you whether the transfer is still moving toward delivery or has entered a refund path. Most stages need time rather than action; the key exception is “To be refunded,” because delivery will not happen unless you request the refund from the sending wallet. A delay alone does not mean failure.</p><h3>What The Delivery Statuses Mean</h3><p>The delivery statuses follow the transfer from the source chain to the destination chain. “Submitting” means the source-chain transaction has not yet been confirmed, so the transfer has not moved on to the later bridge stages. The next status, “Waiting for SGN confirmation,” means cBridge is waiting for confirmation from the State Guardian Network (SGN), its validator network.</p><p>After validator confirmation, “Waiting for fund release” means the transfer is awaiting release of funds on the destination chain. “Completed” means the transfer finished. While you see either waiting status, the work is proceeding through cBridge’s delivery process; there is no refund request to make at that point.</p><p>The cBridge gateway API documentation’s “GetTransferStatus” feature defines these stages and exposes details such as the source and destination transaction links. That distinction matters: “Waiting for SGN confirmation” and “Waiting for fund release” describe different steps, even though both usually call for waiting.</p><h3>When A Transfer Moves To The Refund Path</h3><p>“To be refunded” means the transfer failed and should enter a refund flow instead of being delivered. This is the point where the sender must request a refund from their wallet. Do not treat the status as proof that the funds have already returned: until the claim is submitted and confirmed, the refund is still unfinished.</p><p>The later refund labels show what happens after that request. “Requesting refund” means the gateway is preparing refund information. “Refund to be confirmed” means the sender needs to submit the on-chain refund transaction using the information provided. “Confirming your refund” means cBridge is monitoring that transaction on the source chain; “Refunded” means the refund is complete.</p><p>The API documents this handoff explicitly: its status list assigns refund-information preparation to the gateway and says the user should submit the on-chain transaction at “Refund to be confirmed.” In its response, refund-specific fields include the serialized withdrawal request and validator signatures. This shows why the refund path is not one automatic status change: the gateway prepares the claim, but the sender submits it.</p><h3>How To Read “Delayed” And “Failed”</h3><p>“Delayed” means the transfer has been placed in a delayed execution queue. It is a processing condition, not a declaration that delivery failed, so wait for the status to progress rather than starting a refund based on that label alone.</p><p>“Failed” is a separate status. The GetTransferStatus documentation defines it as a failed transfer that does not need a refund. That differs from “To be refunded,” which specifically triggers the refund flow. Read the exact label before deciding whether to wait or act; a delay does not send funds back, and a refund-path status does not mean funds are already back.</p><h3>What To Do Next</h3><p>Use the status as your decision point: wait on “Submitting,” either delivery waiting stage, “Delayed,” or “Confirming your refund”; request the refund when the status says “To be refunded”; and submit the on-chain refund transaction when it says “Refund to be confirmed.” A completed or refunded status indicates the corresponding path has finished.</p><p>If your history is on a refund path, the distinction between gateway preparation and sender submission determines whether you still have a task: the gateway can prepare refund data, but the sender’s wallet must initiate the claim. For <a href="https://dailycryptonews.github.io/what-to-do-when-a-cbridge-transfer-is-pending/">cBridge</a> transfer history, read “To be refunded” as the point to request that claim, not as confirmation that the refund has already arrived.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c386c2449a0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Berachain Bridge Pending Transfer With No Source Transaction]]></title>
            <link>https://medium.com/@h06183113/berachain-bridge-pending-transfer-with-no-source-transaction-42dd76e190ba?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/42dd76e190ba</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[arbitrum]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 11:37:16 GMT</pubDate>
            <atom:updated>2026-11-09T11:37:16.747Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bI7kagTKyrEHB5FW.jpg" /></figure><p>A pending label from the Berachain bridge does not prove the source chain accepted the transfer, and no explorer result does not prove it was never broadcast. A wrong network, an approval mistaken for the transfer, a submission problem, or delayed indexing can produce the same screen. Until a source receipt appears, establish what the wallet actually submitted before sending again.</p><h3>What Does a Missing Explorer Result Establish?</h3><p>A missing result establishes only that the explorer did not find the identifier on the network you searched. A visible pending transaction shows that the wallet has a transaction record, but it does not show that the network included it. An included receipt, by contrast, records the transaction’s outcome on that chain.</p><p>Start in the submitting wallet’s activity and open the entry for the asset transfer itself. A token approval has its own transaction hash; it gives a contract permission to use tokens, but does not show that the later transfer was submitted. Copy the transfer’s identifier, then compare the wallet’s transaction details with the explorer for the intended source network. A correct hash on the wrong network can look just as absent as an unbroadcast transaction.</p><p>The <a href="https://paragraph.com/@vijiweb966/berachain-bridge-pending-when-to-wait-and-when-to-act">Berachain bridge route</a> is the cross-chain path for the transfer, while the source explorer shows whether the wallet’s transaction was accepted on its origin network. Treat those as separate checks: a route’s pending label cannot replace source-chain evidence, and one explorer’s empty search does not prove global absence or justify a fresh payment.</p><h3>Could a Replacement Explain the Missing Transaction?</h3><p>Yes. On an EVM network, a sender’s transactions use sequential numbers called nonces. If the wallet submits a replacement with the same sender and nonce, and that replacement is included, it consumes the nonce. The original transaction then cannot later confirm on the canonical chain, even if its hash still has no receipt.</p><p>Look in the wallet for a sped-up or cancelled transaction, then compare its sender and nonce with the transfer entry. If the included replacement was a different action, such as a cancellation, it does not establish that the asset transfer occurred. If you find no replacement, that absence still does not prove the original was broadcast.</p><h3>What Should You Do Before Resubmitting?</h3><p>If the wallet shows a pending transfer hash, follow that transaction on the intended source network and inspect it for a receipt. Once a receipt is available, use its recorded success or failure as the source state; the missing-transaction diagnosis no longer applies. This establishes only the source outcome, not whether assets arrived on the destination.</p><p>If the wallet has no transfer hash, or the hash remains absent from the correct explorer, use the wallet’s submission diagnostics to determine whether the request was sent and accepted. Record the network, wallet entry, hash if available, and any replacement with the same nonce. If acceptance remains unverified, give that evidence to wallet support before making another transfer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42dd76e190ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why a renBTC contract transfer did not pay out Bitcoin]]></title>
            <link>https://medium.com/@h06183113/why-a-renbtc-contract-transfer-did-not-pay-out-bitcoin-4f04a6b7de55?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f04a6b7de55</guid>
            <category><![CDATA[bitcoin-trading]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Sat, 07 Nov 2026 03:37:00 GMT</pubDate>
            <atom:updated>2026-11-07T03:37:00.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OOSd-GkKEFu4S9LV.jpg" /></figure><p>A successful transfer to the renBTC token contract did not, by itself, redeem Bitcoin. Start with your friend’s transaction hash and the correct network explorer; read the call and full receipt to see whether it was a token transfer or a gateway burn. That evidence explains what happened, though it cannot promise a payout or recovery.</p><h3>A successful receipt confirms the call, not the intended payout</h3><p>A transaction receipt marked successful means the submitted call executed on that network. It does not mean the sender’s reason for making the call was fulfilled. If your friend expected Bitcoin, the key question is what function the transaction called — not what they meant to do or what a wallet activity label suggests.</p><p>Open the transaction on the explorer for the network where it was sent. Read the “To” address and the decoded method, if available. A plain ERC20 transfer commonly calls <em>transfer</em> on the token contract, passing a recipient address and an amount. The token contract then updates balances and emits a <em>Transfer</em> event. Ethereum’s ERC20 documentation describes this token movement; a receiving contract’s own application workflow is a separate matter.</p><p>Identify the token contract from the transaction details or a trusted record for the network, rather than assuming every token named renBTC is the same contract. In the receipt’s logs, find the <em>Transfer</em> event emitted by that contract. Its “from” address, “to” address and amount show which balance was debited and which was credited. If the credited address is the token contract itself, the tokens went to the contract’s balance.</p><h3>A gateway burn is the condition that changes the result</h3><p>Historically, redeeming renBTC for Bitcoin required the gateway’s burn operation. A burn reduces the token supply; a plain transfer changes who holds tokens without reducing that supply. The destination can therefore be the token contract in both cases, while the decisive difference is whether the transaction executed the gateway’s burn logic.</p><p>That distinction also explains why <a href="https://dev.to/robert_defi/renbridge-redemption-tracing-a-renbtc-burn-to-bitcoin-3coa">RenBridge renBTC minting</a> is relevant: minting renBTC through a gateway workflow is a contract operation, while sending existing renBTC to the token contract is only a transfer unless the receipt shows the separate burn operation. To tell these cases apart, inspect the called contract and decoded method, then examine the complete receipt for gateway activity. Do not infer a burn from the wallet’s label or from the fact that the contract received tokens.</p><p>For example, suppose two transactions use the same network, token, amount and apparent destination. In the first, the token contract’s <em>transfer</em> method emits a <em>Transfer</em> event crediting the token contract; that establishes a token movement, not a Bitcoin redemption. In the second, the transaction invokes the gateway’s burn operation and the receipt records that burn. Only the second has evidence of the redemption step, so its Bitcoin payout needs a separate investigation.</p><h3>A contract balance does not create an automatic reversal</h3><p>If the receipt shows only a transfer, the confirmed result is that renBTC was credited to the token contract. ERC20 transfers have no general undo function: once confirmed, they are not automatically reversed because the recipient was unintended. Whether anyone can return the tokens depends on the recipient contract’s code and on who, if anyone, has authorised control to recover them.</p><p>Look for documented recovery functions and establish who is authorised to call them. A token contract may offer no method to withdraw tokens mistakenly sent to its own address; a method’s existence would still not prove that your friend can use it. Treat recovery as possible only if the contract’s documented capabilities and permissions support it. If they do not, the transaction record cannot provide a path to a payout.</p><h3>Explain the recorded action before discussing recovery</h3><p>Show your friend the method, the token contract’s <em>Transfer</em> event and the address credited. If those details show a plain transfer and no gateway burn in the complete receipt, explain that the transaction moved renBTC into the token contract’s balance but did not request Bitcoin redemption. Then assess any documented recovery capability separately; do not describe a possible recovery as a confirmed payout.</p><p>If the receipt does show a gateway burn, the answer changes only on that point: a redemption step occurred, so investigate the gateway’s payout records and the Bitcoin destination associated with that operation. A burn is evidence of the gateway action, not proof that Bitcoin arrived. The transaction hash and receipt establish what executed; separate payout evidence establishes whether the expected Bitcoin was sent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f04a6b7de55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When to Bundle Small Berachain Bridge Deposits]]></title>
            <link>https://medium.com/@h06183113/when-to-bundle-small-berachain-bridge-deposits-cf86ffa28e99?source=rss-49867a138cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf86ffa28e99</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[Matt Day]]></dc:creator>
            <pubDate>Sat, 07 Nov 2026 01:52:15 GMT</pubDate>
            <atom:updated>2026-11-07T01:52:15.573Z</atom:updated>
            <content:encoded><![CDATA[<p>If your receipts can wait until your next spending date and a combined transfer gives you more net funds on Berachain, accumulating them can reduce repeated gas payments and wallet interactions. If you need the funds sooner, or the larger transfer has an unfavorable quote, bridge earlier.</p><ul><li><strong>Result:</strong> Fewer transfers can mean less repeated gas and signing effort.</li><li><strong>Requirement:</strong> Compare net destination amounts for the same total input.</li><li><strong>Limit:</strong> Your spending date and comfortable source balance determine how long to wait.</li></ul><h3>Should I bridge each receipt or wait?</h3><p>Wait when the funds are not needed yet and consolidation improves the amount you expect to receive after costs. Bridge each receipt when it arrives if it is needed for an upcoming Berachain purchase or the delay would disrupt your routine.</p><p>Accumulating means sending several receipts together in one later transfer. It does not require a contract to batch separate transactions: you simply make fewer transfers yourself. That can avoid paying a separate gas fee for every send and reduce the number of wallet prompts and transfers to track. It does not automatically reduce charges based on the amount transferred.</p><p>These choices assume the receipts collect in one wallet on the same source network and in the same token. If you receive different tokens or use different networks, compare each route separately; a single combined transfer may not be possible or comparable.</p><h3>How can I tell whether combining saves money?</h3><p>Compare the net destination amount for one transfer of the combined receipts with the total net amount from transferring them individually. Use quotes for the same total input and the same route, at roughly the same time, since prices and fees can change.</p><p>For a clear calculation, subtract separately paid gas from the combined transfer’s quoted output, then compare that result with the sum of the individual quoted outputs after their gas costs. Express gas in the destination token’s units so the amounts can be compared. Do not subtract a fee again if the quote already includes it in the displayed output.</p><p>Knowing <a href="https://graph.org/Berachain-Bridge-Transfers-Where-Your-Crypto-Goes-11-05">what Berachain bridge fees include</a> helps you separate repeated gas from charges that may vary with the amount. A larger transfer can receive different pricing, so fewer transactions alone do not prove that you save. A combined quote may deliver less than expected if amount-dependent charges rise or the route changes; compare the actual net outputs rather than assuming a fixed saving per transfer.</p><h3>How long can receipts stay on the source chain?</h3><p>Your next Berachain spending deadline sets the practical limit. Pick a date far enough ahead to allow for the transfer to complete and any routine delay you would want to absorb. If you will need the funds before the next scheduled transfer, send earlier rather than letting a small saving leave you short.</p><p>The right buffer depends on your spending routine and how quickly you need funds available after bridging. A transfer quote is a snapshot, not a promise about future receipts: later network conditions, available routes, or pricing may change the net amount. Compare again when you are ready to send.</p><h3>Which transfer cadence fits my routine?</h3><p>Choose among three workable habits: bridge every receipt as it arrives; accumulate receipts until a scheduled funding date; or accumulate until a balance threshold is reached, with a deadline that triggers an earlier transfer if needed.</p><p>A scheduled date is easy to remember and ties funding to a known spending cycle. A threshold can avoid frequent small transfers when receipts arrive irregularly, but set a maximum source balance you are comfortable holding and a latest send date. A threshold without a deadline can leave funds waiting past the moment you need them.</p><p>Use the next spending date, comparable net destination amounts, your maximum comfortable source balance, and the effort of signing and tracking as your criteria. If funds can wait and consolidation improves comparable net proceeds, accumulate; otherwise transfer when needed. This gives you a cadence that reduces avoidable repetition without delaying access beyond your own spending needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf86ffa28e99" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>