<?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"><channel><title><![CDATA[Blockwire Notes]]></title><description><![CDATA[Blockwire Notes]]></description><link>https://blockwirenotes.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 16:53:03 GMT</lastBuildDate><atom:link href="https://blockwirenotes.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Matcha swap: Why is my swap failing and how do I fix it?]]></title><description><![CDATA[Matcha swap usually fails when price movement exceeds slippage tolerance, approval or gas is missing, or a token restricts transfers. A Matcha crypto swap…]]></description><link>https://blockwirenotes.hashnode.dev/matcha-swap-why-is-my-swap-failing-and-how-do-i-fix-it</link><guid isPermaLink="true">https://blockwirenotes.hashnode.dev/matcha-swap-why-is-my-swap-failing-and-how-do-i-fix-it</guid><dc:creator><![CDATA[Layim Hales]]></dc:creator><pubDate>Thu, 19 Nov 2026 01:37:51 GMT</pubDate><content:encoded><![CDATA[<p>Matcha swap usually fails when price movement exceeds slippage tolerance, approval or gas is missing, or a token restricts transfers. A Matcha crypto swap through <a href="https://matchaswap.pro">Matcha swap</a> routes trades across decentralized liquidity sources. Find the transaction hash, inspect an Ethereum trade on Etherscan, correct the cause, and retry. Confirmation and a higher bought-token balance mean it worked.</p>
<h2>Matcha swap failures: causes, signs and fixes</h2>
<p>Price movement can make a submitted swap revert. The contract rejects output below minimum received; the <a href="https://docs.0x.org/docs/introduction/quickstart/swap-tokens-with-0x-swap-api">0x Swap API documentation</a> shows the minBuyAmount field behind this check. Refresh a stale quote, compare its minimum received, and retry promptly. Raise slippage slightly only if the lower minimum remains acceptable: wider tolerance permits a worse fill.</p>
<p>Missing approval or funds can prevent submission or fail gas estimation. Confirm the sell-token allowance and balance, selected network, and native-token gas balance. Approve the sell token when required, wait for confirmation, then retry. Leave gas when selling a native token. A wallet rejection before broadcast has no transaction hash; review the request before signing again.</p>
<p>Transfer-tax tokens can deliver less than the route expects. Say 100 tokens leave your wallet but a sell tax reduces what reaches the route: output may fall below minimum received and revert. A buy tax can cut final delivery too. Identify the tax before raising slippage; cover only an acceptable tax and price movement. If the token blocks selling through the route, or usable liquidity is absent, slippage cannot help. Some restricted tokens cannot be sold through any aggregator.</p>
<p>After a fresh quote, confirmed approval, adequate balances, and a tax check, repeated failure calls for support. Provide any transaction hash, the network, token addresses, and error message. Retry only when you can identify a fix.</p>
<h2>Answers to the next transaction questions</h2>
<h3>Do I get my gas back if a Matcha crypto swap fails?</h3>
<p>No. A reverted on-chain transaction consumes gas, but your sold tokens remain. Rejection before broadcast costs no on-chain gas.</p>
<h3>Why is my Matcha token exchange stuck on pending?</h3>
<p>Pending means broadcast but unconfirmed. Low gas fees or an earlier pending nonce can delay it. Inspect an Ethereum trade on Etherscan; use your wallet's speed-up option if available.</p>
<h3>What slippage should I set for a Matcha DEX swap?</h3>
<p>Use the lowest tolerance that allows an acceptable minimum received. Volatile or taxed tokens may need more; stop if the minimum becomes too low.</p>
<h3>How do I cancel a pending Matcha crypto swap?</h3>
<p>Use your wallet's cancel function to replace the transaction with the same nonce and a higher gas fee. Cancellation works only if the replacement confirms first.</p>
]]></content:encoded></item><item><title><![CDATA[Custodial vs Non-Custodial Bitcoin Bridges: Choose by Redemption]]></title><description><![CDATA[Choose a custodial bitcoin bridge when you trust its custodian and need liquid markets; choose a threshold-signer bridge when direct redemption matters…]]></description><link>https://blockwirenotes.hashnode.dev/custodial-vs-non-custodial-bitcoin-bridges-choose-by-redemption</link><guid isPermaLink="true">https://blockwirenotes.hashnode.dev/custodial-vs-non-custodial-bitcoin-bridges-choose-by-redemption</guid><dc:creator><![CDATA[Layim Hales]]></dc:creator><pubDate>Tue, 17 Nov 2026 15:50:31 GMT</pubDate><content:encoded><![CDATA[<p>Choose a custodial bitcoin bridge when you trust its custodian and need liquid markets; choose a threshold-signer bridge when direct redemption matters more. Who can return native BTC is the deciding difference, so review <a href="https://renbridge.net">RenBridge</a> to see how an earlier signer-based bridge worked and why continued operation matters to your exit. Your choice also depends on which wrapper has usable liquidity on your target chain.</p>
<h2>Compare Custody, Redemption, and Chain Support</h2>
<p>The best bridge is one whose BTC redemption route you can use when you need to exit. Holding a wrapped token in your own wallet does not, by itself, give you the right to redeem it directly.</p>
<ul>
<li><strong>WBTC:</strong> Institutions custody the BTC; BitGo remains involved in the custody infrastructure. Approved merchants handle minting and redemption, so a holder seeking native BTC must use a merchant that accepts them. A merchant or custodian can decline that service. WBTC spans many chains, but trading depth varies by chain. The <a href="https://www.wbtc.network/whitepaper">WBTC whitepaper</a> describes the merchant-only burn and BTC release steps.</li>
<li><strong>cbBTC:</strong> Coinbase issues the token and holds its backing BTC. Conversion to native BTC runs through an eligible Coinbase account, and Coinbase can restrict an account or freeze cbBTC transfers at the token level. Confirm that cbBTC exists on your target chain and that your Coinbase account can receive it.</li>
<li><strong>tBTC:</strong> A threshold signer set controls the backing BTC. Any holder can request redemption to a Bitcoin address without a custodian account, subject to bridge requirements and fees. Signer or bridge interruptions can delay the request. The Threshold Network tBTC documentation explains the shared-signing mechanism; check support on the chain where you hold tBTC.</li>
<li><strong>sBTC:</strong> A signer set controls its BTC peg wallet. Holders can request withdrawals directly from Stacks to a Bitcoin address. Signers must process the request, so signer availability affects timing. sBTC is the relevant option when your destination is Stacks.</li>
</ul>
<p>Say you receive cbBTC in an external wallet but cannot use a Coinbase account. You can look for a market trade, yet you cannot use Coinbase’s direct unwrap route yourself. For WBTC, ask an approved merchant whether it will redeem for you and what identity checks it requires. If direct redemption without an account is essential, choose tBTC or sBTC on a supported chain.</p>
<p>RenBridge is a reminder to examine service continuity as well as signer design. Its Ren 1.0 operators began shutting the bridge down in 2022. Distributed signing did not keep that redemption route open.</p>
<p>Choose WBTC or cbBTC when you accept their redemption gate and their market has the liquidity your trade needs. Choose tBTC or sBTC when an open holder-initiated exit matters more. Before sending BTC, verify the exact wrapper, target chain, live redemption route, and trade depth; that tells you whether your planned exit is usable.</p>
<h2>Related Questions</h2>
<h3>Is WBTC safe?</h3>
<p>WBTC’s safety depends on its BTC custody, merchant redemption process, and the token’s contract. Its reserves can be checked, but a holder still relies on an approved merchant to obtain native BTC.</p>
<h3>What is the difference between tBTC and WBTC?</h3>
<p>tBTC uses threshold signers and lets holders request BTC redemption directly. WBTC uses institutional custody and routes redemption through approved merchants.</p>
<h2>Questions Before You Bridge</h2>
<p>Confirm the exit route and controls for the specific token you will receive.</p>
<h3>How do I redeem tBTC for bitcoin?</h3>
<p>Use a supported tBTC redemption route, provide a Bitcoin address, and submit the required tBTC. Check its minimum amount, fees, and signer status before confirming.</p>
<h3>Can Coinbase freeze cbBTC?</h3>
<p>Yes. Coinbase’s token controls can restrict transfers from specified addresses, and Coinbase can restrict access to its account-based redemption service.</p>
<h3>Which wrapped bitcoin has the most liquidity?</h3>
<p>It depends on the chain, venue, and trade size. Compare available pool depth and expected slippage where you intend to trade, rather than relying on a token’s total supply.</p>
<h3>What happened to renBTC holders after the shutdown?</h3>
<p>Ren urged holders to burn renBTC for native BTC during the 2022 shutdown window. RenBridge is no longer a live redemption route; anyone still holding renBTC should identify their exact token and chain before assuming recovery is possible.</p>
]]></content:encoded></item><item><title><![CDATA[How Suibridge Settlement Differs by Transfer Direction: ETH]]></title><description><![CDATA[Suibridge settlement has two different completion points: Ethereum-to-Sui locks ETH before minting bridged ETH, while Sui-to-Ethereum burns that…]]></description><link>https://blockwirenotes.hashnode.dev/how-suibridge-settlement-differs-by-transfer-direction-eth</link><guid isPermaLink="true">https://blockwirenotes.hashnode.dev/how-suibridge-settlement-differs-by-transfer-direction-eth</guid><dc:creator><![CDATA[Layim Hales]]></dc:creator><pubDate>Tue, 17 Nov 2026 12:28:25 GMT</pubDate><content:encoded><![CDATA[<p>Suibridge settlement has two different completion points: Ethereum-to-Sui locks ETH before minting bridged ETH, while Sui-to-Ethereum burns that representation before releasing ETH through a claim on Ethereum.</p>
<ul>
<li>Outward: look for the bridged asset in the Sui recipient’s balance.</li>
<li>Return: complete the Ethereum claim, then wait for its transaction to confirm.</li>
</ul>
<p>On this Sui Bridge route, ETH enters Ethereum custody before a matching asset appears on Sui. The <a href="https://suibridge.cc">Suibridge</a> cross-chain bridge is a concrete lock-and-mint example: custody on the source chain precedes delivery on the destination chain.</p>
<p>suibridge.cc is a cross-chain bridge for moving supported crypto assets between Ethereum and Sui.</p>
<h2>When Is an Ethereum-to-Sui or Sui-to-Ethereum Transfer Settled?</h2>
<p>Ethereum-to-Sui settlement ends with destination delivery; Sui-to-Ethereum settlement needs a further claim and Ethereum confirmation. In either direction, the bridge waits for source finality, authorization by Sui validators’ voting power, and execution on the destination chain.</p>
<p>For the outward trip, Ethereum locks ETH first. The bridge waits for a configurable depth of Ethereum block confirmations before validators authorize the Sui-side mint. The result is a bridged ETH representation in the recipient’s Sui balance. The confirmation depth can change because the validator committee sets it.</p>
<p>Take an illustrative round trip with one ETH. Before the outward transfer, the asset is ETH on Ethereum. After delivery, the holder has bridged ETH on Sui, while the original ETH remains in bridge custody. The <a href="https://www.sui.io/blog/sui-bridge-launches-on-mainnet">Sui Foundation launch guide</a> describes delivery without a manual Sui claim in most Ethereum-to-Sui cases and an Ethereum-account claim for the return direction.</p>
<p>On the way back, the holder sends the bridged ETH from Sui. That representation is burned, and the bridge waits for Sui transaction finality before validator authorization of the Ethereum release. The <a href="https://github.com/MystenLabs/sui/blob/main/crates/sui-framework/packages/bridge/sources/bridge.move">bridge implementation</a> records a message, verified signatures and claim status per transfer key across supported routes; its Sui send path burns or escrows the outgoing coin.</p>
<p>A finalized Sui burn therefore leaves an outstanding Ethereum claim. The Sui balance has changed, but ETH has not yet reached the Ethereum recipient. The user must submit the claim with the Ethereum account and wait for that destination transaction to confirm. For a return transfer, treat the confirmed Ethereum release—not the Sui burn—as completion.</p>
<h2>Related Questions</h2>
<h3>Does Bridging ETH Turn It Into SUI?</h3>
<p>Bridging ETH produces a bridged ETH representation on Sui. ETH remains the asset being represented; SUI is a different token.</p>
<h3>Is Suibridge Wormhole Portal Bridge?</h3>
<p>Suibridge and Wormhole Portal Bridge use separate bridge infrastructure. A bridged asset’s origin matters when identifying what a wallet or DeFi app holds.</p>
<h2>What Should You Ask Before the Next Transfer?</h2>
<h3>What Determines Suibridge Fees?</h3>
<p>Fees depend on the route and the transactions required on each chain. Review the current quote before submitting.</p>
<h3>Which Tokens Does Suibridge Support?</h3>
<p>Supported tokens depend on the current route. Confirm the asset on both chains before sending it.</p>
<h3>Which Wallets Work With Suibridge?</h3>
<p>You need access to the source account and the destination account. A return claim also requires the Ethereum account.</p>
<h3>How Do I Track a Delayed Suibridge Transfer?</h3>
<p>Follow the source transaction, validator authorization and destination transaction separately. On a return, look for an outstanding Ethereum claim after the Sui burn finalizes.</p>
]]></content:encoded></item><item><title><![CDATA[Monad bridge slippage for routes with swaps]]></title><description><![CDATA[On a Monad bridge route with a swap, choose slippage tolerance from the minimum destination output you can accept; widening it permits worse swap…]]></description><link>https://blockwirenotes.hashnode.dev/monad-bridge-slippage-for-routes-with-swaps</link><guid isPermaLink="true">https://blockwirenotes.hashnode.dev/monad-bridge-slippage-for-routes-with-swaps</guid><dc:creator><![CDATA[Layim Hales]]></dc:creator><pubDate>Mon, 09 Nov 2026 13:47:35 GMT</pubDate><content:encoded><![CDATA[<p>On a Monad bridge route with a swap, choose slippage tolerance from the minimum destination output you can accept; widening it permits worse swap execution, not faster confirmation. When you return to a <a href="https://monad-bridge.org">Monad bridge</a> quote, compare its displayed minimum with the amount you need. This choice applies only where a swap has adjustable tolerance.</p>
<h2>What does slippage change on a Monad bridge route?</h2>
<p>Slippage tolerance sets how far the swap price may move against you between the quote and execution before the swap fails. Price impact is different: it is the effect of the trade on the available liquidity and is already reflected in the quoted output. A bridge fee is a separate charge. Read the route’s fee treatment to see whether the displayed destination amounts include that charge.</p>
<p>Suppose an illustrative quote, with no fees, shows 100 destination tokens. At 0.5% tolerance, its minimum might be 99.5 tokens; at 1%, it might be 99. The quoted output remains 100. What changed is the worst swap execution you agreed to accept. A real route may calculate its minimum across fees and multiple swaps, so rely on the amount it displays.</p>
<h2>How should I choose the setting?</h2>
<p>Use the displayed minimum, in token units, as your output floor. In the example, someone who needs at least 99.2 tokens could accept the 0.5% setting but not the 1% setting. I would keep the tighter setting when worse output defeats the transfer’s purpose. Widen it only while the displayed minimum still covers what you need.</p>
<p>Lower tolerance narrows the acceptable execution range, so price movement can cause a swap to fail. Higher tolerance can let that swap complete despite more adverse movement; it cannot shorten blockchain confirmation. Consider the price impact already in the quote and how quickly the swap price is moving. If a bridge to Monad route has multiple swaps, inspect the tolerance available for each one.</p>
<p>Failure also depends on where the swap happens. A source-side swap may fail before assets cross; a destination-side swap may fail afterward. The route’s failure handling determines whether assets remain on the source chain, arrive as an intermediate asset, or require recovery. That consequence matters when deciding whether a tighter output range is worth a possible failed attempt.</p>
<h2>How does this apply to related transfers?</h2>
<p>The output-floor rule applies to an adjustable swap in either direction; a route without one may offer no slippage choice.</p>
<h3>Can I bridge USDC to Monad?</h3>
<p>If an available route supports your source USDC and intended destination asset, look for a swap in its steps. Apply the minimum-output test if there is one. A direct transfer may show fees and a minimum amount without offering swap tolerance.</p>
<h3>Why do I need MON after bridging to Monad?</h3>
<p>MON pays for transactions on Monad. If your intended next action needs MON and the route swaps into it, make the minimum MON output cover that need. Receiving another asset alone does not establish that floor.</p>
<h3>How can I bridge assets from Monad to another chain?</h3>
<p>For a transfer crypto from Monad route, inspect any source or destination swap the same way: its tolerance governs acceptable adverse price movement, while the displayed minimum tells you whether the final amount still serves your purpose.</p>
]]></content:encoded></item><item><title><![CDATA[Reading a Contract Approval Before You Sign It]]></title><description><![CDATA[Most wallet drains do not come from a stolen key. They come from a signature the owner approved without reading. The approval screen is the last line of…]]></description><link>https://blockwirenotes.hashnode.dev/reading-a-contract-approval-before-you-sign-it</link><guid isPermaLink="true">https://blockwirenotes.hashnode.dev/reading-a-contract-approval-before-you-sign-it</guid><dc:creator><![CDATA[Layim Hales]]></dc:creator><pubDate>Wed, 04 Nov 2026 14:54:41 GMT</pubDate><content:encoded><![CDATA[<p>Most wallet drains do not come from a stolen key. They come from a signature the owner approved without reading. The approval screen is the last line of defense, so it is worth slowing down for.
What an approval really grants
When you approve a token for an app, you are letting its contract move that token on your behalf. Some approvals are for a fixed amount; many ask for unlimited access.
Unlimited is the dangerous default
Unlimited approvals are convenient and risky. If that contract is ever exploited, it can drain the whole balance it was approved for, long after you forgot about it.
Habits that protect you</p>
<p>Read which token and what amount the approval covers.
Prefer a capped amount over unlimited when offered.
Revoke old approvals you no longer use.</p>
<p>The point
A signature is an instruction, not a formality. Ten seconds reading the approval beats weeks regretting it.</p>
]]></content:encoded></item><item><title><![CDATA[Hot Wallets and Cold Wallets, Explained Plainly]]></title><description><![CDATA[Every wallet is either connected to the internet or it is not. That single difference is the whole idea behind hot and cold storage, and it decides how you…]]></description><link>https://blockwirenotes.hashnode.dev/hot-wallets-and-cold-wallets-explained-plainly</link><guid isPermaLink="true">https://blockwirenotes.hashnode.dev/hot-wallets-and-cold-wallets-explained-plainly</guid><dc:creator><![CDATA[Layim Hales]]></dc:creator><pubDate>Tue, 03 Nov 2026 14:32:47 GMT</pubDate><content:encoded><![CDATA[<p>Every wallet is either connected to the internet or it is not. That single difference is the whole idea behind hot and cold storage, and it decides how you should use each one.
Hot wallets are for spending
A hot wallet lives on your phone or browser. It is convenient and fast, which also means it is exposed. Keep only what you are comfortable losing in it, the way you would with cash in a pocket.
Cold wallets are for keeping
A cold wallet stays offline. Moving funds requires physical access, so a remote attacker cannot drain it with a stolen password alone.
A simple split that works</p>
<p>Daily - a small amount in a hot wallet for actual use.
Savings - the bulk in cold storage you touch rarely.
Backup - the recovery phrase written on paper, stored away from both.</p>
<p>The mistake to avoid
People lose funds not because cold storage failed, but because they kept everything hot for convenience. Convenience and security pull in opposite directions; decide the split on purpose.</p>
]]></content:encoded></item></channel></rss>