<?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[Chain Notes]]></title><description><![CDATA[Chain Notes]]></description><link>https://chainnotesfm.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 18:22:04 GMT</lastBuildDate><atom:link href="https://chainnotesfm.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Which blockchains did RenBridge support? Sources and hosts]]></title><description><![CDATA[RenBridge let people bring coins from one blockchain onto another as tokens they could use in decentralized finance (DeFi). Its supported chains had two…]]></description><link>https://chainnotesfm.hashnode.dev/which-blockchains-did-renbridge-support-sources-and-hosts</link><guid isPermaLink="true">https://chainnotesfm.hashnode.dev/which-blockchains-did-renbridge-support-sources-and-hosts</guid><dc:creator><![CDATA[Mason Carter]]></dc:creator><pubDate>Tue, 17 Nov 2026 15:33:01 GMT</pubDate><content:encoded><![CDATA[<p>RenBridge let people bring coins from one blockchain onto another as tokens they could use in decentralized finance (DeFi). Its supported chains had two roles: a source chain held the native coin, while a host chain received a token representing it. The original service is discontinued, so these are historical routes.</p>
<p>Source chains included Bitcoin for BTC, Bitcoin Cash for BCH, Zcash for ZEC, Dogecoin for DOGE and Filecoin for FIL. Host chains included Ethereum, BNB Chain, Polygon, Avalanche, Fantom, Arbitrum and Solana. A list that mixes them together can be misleading: Bitcoin supplied native BTC, while Polygon could receive renBTC.</p>
<h2>RenBridge source chains, host chains and a BTC transfer</h2>
<p>A source chain held the original asset; a host chain held the minted ren-token. The token’s name identified what it represented: renBTC represented BTC held through RenVM, the distributed node network that powered the bridge. It was a token on its host chain, rather than a Bitcoin transaction in a different wallet.</p>
<p>Take BTC moving from Bitcoin to Polygon. The user sent BTC to a gateway address on Bitcoin. RenVM’s nodes watched for the deposit, then authorized the gateway on Polygon to mint renBTC. The result was visible on Polygon as a renBTC balance, which could be used in applications there. To return to native BTC, the user burned renBTC on Polygon; RenVM then released BTC to a Bitcoin address.</p>
<p>The bridge’s two chain roles describe different ends of that route. In <a href="https://renbridge.net">RenBridge</a>, Bitcoin was the source of BTC, while Polygon was the host for renBTC. That distinction matters when reading a token balance: seeing renBTC on Polygon tells you where the token sits, not where the native BTC originated.</p>
<p>Later versions also let supported tokens move between host chains. Moving renBTC from one host to another still left Bitcoin as BTC’s native chain. The particular asset and destination both mattered, since a chain’s presence in a supported list did not mean every asset used every route.</p>
<h2>Redemption and Solana routes after the shutdown</h2>
<p>RenVM’s original network shut down in December 2022. New transfers through the original bridge are no longer possible.</p>
<h3>Can I still redeem renBTC for bitcoin?</h3>
<p>The original burn-and-release route is no longer available. A renBTC balance alone does not establish that BTC can be released today. Identify the token and its host chain before relying on any claimed redemption route, and verify that the route can actually deliver native BTC to a Bitcoin address.</p>
<h3>What can I use instead of RenBridge to get bitcoin on Solana?</h3>
<p>Look for a currently operating route that accepts native BTC from Bitcoin and states exactly which token it delivers on Solana. Check who holds the backing BTC and how that Solana token can be redeemed. Those details tell you whether you would receive a usable representation of Bitcoin and what it takes to get native BTC back.</p>
]]></content:encoded></item><item><title><![CDATA[KyberSwap Security Checklist for Teams: Six Trade Checks]]></title><description><![CDATA[KyberSwap teams should verify the official URL and spender, approve only the trade amount, review the route and minimum received, meet their multisig…]]></description><link>https://chainnotesfm.hashnode.dev/kyberswap-security-checklist-for-teams-six-trade-checks</link><guid isPermaLink="true">https://chainnotesfm.hashnode.dev/kyberswap-security-checklist-for-teams-six-trade-checks</guid><dc:creator><![CDATA[Mason Carter]]></dc:creator><pubDate>Tue, 17 Nov 2026 12:13:21 GMT</pubDate><content:encoded><![CDATA[<p>KyberSwap teams should verify the official URL and spender, approve only the trade amount, review the route and minimum received, meet their multisig signer threshold, and record the transaction hashes for every trade. Use <a href="https://kyberswap.dev">KyberSwap</a> to find a swap route, then put that proposed trade through the team’s checks before anyone signs. ERC-20 allowances can remain in force after a trade, while a spoofed destination or stale quote can reach signers if the proposal is not checked again.</p>
<h2>KyberSwap Pre-Trade Checks for Every Swap</h2>
<p>KyberSwap Aggregator finds routes across liquidity sources, so the team needs to review both the permission it grants and the trade it will execute. Run these six checks against the proposed transaction and keep the results together.</p>
<ul>
<li><strong>Verify the official URL and spender.</strong> Open the trading site from a team bookmark. Compare the full spender address in the token approval with the current official documentation for the product and network in use. Have a signer compare the address shown by the wallet with the address recorded in the proposal; a familiar token name or contract label is not enough. The check passes when those addresses match. Stop if they differ. Confirm that the proposed route uses active, supported products before approving it. KyberSwap Elastic’s November 2023 exploit affected liquidity pools and showed why contract risk needs attention alongside trade settings.</li>
<li><strong>Approve exactly the planned input amount.</strong> Make the amount in the trade proposal the limit of the ERC-20 approval, and have signers verify that amount in the approval transaction. If a larger allowance already exists, reduce or revoke it before treating the new approval as limited to this trade. An approval gives the spender permission that can survive the swap until it is used, changed or revoked. Say a quote expires after the approval confirms: the swap never spends the tokens, but the permission remains. Mark that trade as unfinished until the team has checked the remaining allowance and revoked it.</li>
<li><strong>Review the route and the output floor.</strong> Put the token pair, input amount, proposed route, quoted output, price impact and minimum received in the proposal. Signers should compare those values with the transaction they are asked to authorize. Price impact reflects what this trade does to the available liquidity; minimum received is the lowest output the team agrees to accept. A route with a better headline quote can still be unsuitable if its impact or output floor falls outside the desk’s limits. Record the accepted values so a later reviewer can see what the signers approved.</li>
<li><strong>Set slippage and a signing deadline.</strong> Choose the maximum slippage the team will accept for this trade and confirm that its minimum received follows from that choice. Set a cut-off for collecting signatures while the quote is still useful. Multisig review takes time, and market prices or available liquidity can change during the wait. If the cut-off passes, request a fresh quote and submit updated terms for review. The visible result is a proposal whose output floor and approval time still fit the team’s decision when it executes.</li>
<li><strong>Meet the multisig threshold on the reviewed transaction.</strong> A Safe transaction requires its configured signer threshold before execution. Ask signers to verify the destination, token, amount and trade terms in the transaction they confirm, including any approval submitted separately. Record who signed and which proposal they reviewed. If a route or amount changes after sign-off begins, circulate the revised proposal and collect signatures for that transaction. This keeps the threshold attached to the trade the team actually intends to make.</li>
<li><strong>Close the record with hashes and allowance status.</strong> Put the confirmed approval hash next to the swap hash in a shared record, along with the signers, token amounts, route, minimum received and execution result. For an Ethereum trade, Etherscan can help the team compare the confirmed transactions with that record. Inspect the remaining token allowance after execution and revoke any leftover permission; record the revocation hash too. If the swap fails or is cancelled, do the same allowance check. The record is complete when another team member can trace the authorization, execution and final permission state.</li>
</ul>
<h2>Related Questions About Approvals and Trade Risk</h2>
<p>Three decisions often need an explicit team rule: how to clear an approval, how to assess product risk, and how to choose slippage.</p>
<h3>How do I revoke a KyberSwap token approval?</h3>
<p>Identify the wallet, token and spender for the approval, then submit a transaction that sets that allowance to zero. Etherscan and revoke.cash are examples of tools teams use to inspect approvals; verify the spender against the original trade record before acting. Wait for confirmation and check the allowance again. Keep the revocation hash beside the approval and swap hashes so the team can see when the permission ended.</p>
<h3>Is KyberSwap safe to use after the 2023 Elastic exploit?</h3>
<p>The November 2023 KyberSwap Elastic exploit was a contract risk affecting certain liquidity pools. A team should assess the active product and route proposed for its current trade, review current official notices, and apply its own contract risk policy before signing. Exact approvals and careful slippage limit particular trade risks; product selection needs its own decision.</p>
<h3>What slippage setting should a team standardise on?</h3>
<p>Standardise a decision rule, then set a limit for each trade’s liquidity, size and timing. Require the proposal to show maximum slippage and the resulting minimum received, with an extra sign-off when either falls outside the desk’s normal tolerance. A single percentage cannot capture every route. When signing runs late, re-quote and review the new output floor before execution.</p>
<p>Make these six checks a required trade proposal template, and close each trade only after its hashes and remaining allowance are reconciled.</p>
]]></content:encoded></item><item><title><![CDATA[What Is Chainlist for EVM Wallet Network Setup?]]></title><description><![CDATA[Chainlist supplies EVM network details for compatible wallets; your wallet saves the settings, an RPC provider handles requests, and the selected…]]></description><link>https://chainnotesfm.hashnode.dev/what-is-chainlist-for-evm-wallet-network-setup</link><guid isPermaLink="true">https://chainnotesfm.hashnode.dev/what-is-chainlist-for-evm-wallet-network-setup</guid><dc:creator><![CDATA[Mason Carter]]></dc:creator><pubDate>Mon, 09 Nov 2026 13:41:42 GMT</pubDate><content:encoded><![CDATA[<p>Chainlist supplies EVM network details for compatible wallets; your wallet saves the settings, an RPC provider handles requests, and the selected blockchain holds balances and executes transactions. Using <a href="https://chainlist.cc">Chainlist</a> configures access; it does not move assets. Chainlist network search helps locate an entry, but the available action depends on wallet support and whether the network is already saved.</p>
<ul>
<li>If your wallet cannot add the intended EVM network, a directory entry cannot make it compatible.</li>
<li>If the chain ID is already saved, switch to that network or review its RPC setting instead of adding a duplicate.</li>
<li>If an RPC endpoint stops responding, the settings may remain saved while balance and block reads fail.</li>
</ul>
<h2>The Directory, Wallet, RPC, and Blockchain Do Different Jobs</h2>
<p>The directory provides network parameters, including a chain ID, native currency and RPC endpoints. The chain ID is the numeric identifier your wallet uses to distinguish one chain from another; a familiar network name alone is less reliable. The currency symbol tells the wallet how to label the asset used for gas, but displaying that symbol does not put any assets in your account.</p>
<p>Chainlist does not operate every endpoint it displays. An RPC provider runs a server that answers wallet queries, such as requests for a balance or the latest block, and broadcasts signed transactions to the selected network. Your wallet stores an RPC URL and displays the data it receives. The blockchain maintains the balances and processes transactions; an unavailable or slow endpoint does not move funds off that chain.</p>
<p>This separation helps explain an apparently empty wallet. You may have selected a different chain, encountered an RPC that is failing to return data, or have no assets on the intended chain. The directory uses the chainlist.org domain; similarly named research sites and independently hosted directories are separate services.</p>
<h2>How Do You Add the Intended Network?</h2>
<p>Start with an installed, compatible wallet and the intended network’s official documentation. You need to know which network your application expects before choosing a search result. Its documentation gives you a reference for the chain ID and currency, and may identify supported RPC options. Once you have that reference, the wallet can save the settings and make network reads.</p>
<ol>
<li>Search for the network by name or numeric chain ID. Choose an entry whose chain ID matches the network you intended; the name alone is insufficient.</li>
<li>Compare the Chainlist network entry with the network’s official documentation. Review the chain ID, native currency symbol and RPC URL. Two valid providers may have different URLs, so establish that the endpoint serves the same chain rather than expecting every URL to match.</li>
<li>Connect the intended wallet and request the addition. Read its approval screen, especially the chain ID and RPC URL, before accepting. If that chain ID is already saved, the wallet may offer to switch networks instead.</li>
<li>Select the saved network if necessary. Confirm that its chain ID is the intended one and that the wallet can retrieve a current block or balance. A saved network name alone does not establish working connectivity.</li>
</ol>
<p>For example, if Arbitrum is already configured in your wallet, a switch request can be the correct result of looking for an add option. The deciding condition is the saved chain ID: if it matches the official specification, use that entry. If it differs, resolve the mismatch before relying on the displayed network name.</p>
<h2>What Costs Money, and How Long Does It Take?</h2>
<p>Directory lookup and saving network settings incur no blockchain gas; setup takes only as long as wallet approval and an RPC response require. Network setup needs no seed phrase, token approval, fund transfer or signed blockchain transaction. A prompt for any of those is asking you to perform another operation, so identify what it requests before proceeding.</p>
<p>RPC service costs are separate. A public endpoint may be usable without an individual subscription, while another provider may require an account or charge for usage. Later on-chain transactions require gas paid in the selected network’s native asset; the directory does not set that fee. Their confirmation time depends on the chosen network’s processing and congestion, not on how quickly you added its settings.</p>
<h2>What Does a Successful Setup Prove?</h2>
<p>Setup is complete when the intended chain ID is selected and ordinary network reads succeed. A balance shown through an RPC is a read from that chain, not evidence that an application is trustworthy. Adding a network also does not bridge assets from another chain or fund your account on this one.</p>
<p>If reads fail, compare the selected chain ID with official documentation, then try another documented RPC endpoint. Once reads work, open the application you intend to use and confirm that it recognizes the selected chain. That establishes the network access you set out to configure before you decide whether to fund the account or make a transaction.</p>
]]></content:encoded></item><item><title><![CDATA[What a Nonce Is and Why Your Transaction Gets Stuck]]></title><description><![CDATA[A nonce is just a counter: the number of transactions an account has already sent. It sounds trivial, but it is the quiet reason a transaction sometimes…]]></description><link>https://chainnotesfm.hashnode.dev/what-a-nonce-is-and-why-your-transaction-gets-stuck</link><guid isPermaLink="true">https://chainnotesfm.hashnode.dev/what-a-nonce-is-and-why-your-transaction-gets-stuck</guid><dc:creator><![CDATA[Mason Carter]]></dc:creator><pubDate>Wed, 04 Nov 2026 14:53:56 GMT</pubDate><content:encoded><![CDATA[<p>A nonce is just a counter: the number of transactions an account has already sent. It sounds trivial, but it is the quiet reason a transaction sometimes hangs for hours.
Transactions are a queue, not a pile
Each transaction must use the next number in order. If nonce 5 is stuck, nonce 6 cannot go through, even if it pays a huge fee. The network waits for the gap to be filled.
How things get stuck
Usually a transaction was sent with a fee too low for current conditions. It sits unconfirmed, and everything behind it waits in line.
How to unstick it</p>
<p>Resend the same nonce with a higher fee to replace it.
Or send a cheap do-nothing transaction on that nonce to clear the slot.
Avoid blasting new transactions on top — they just pile up behind.</p>
<p>The takeaway
A stuck transaction is almost never lost. It is a queue problem, and the fix is replacing the blocker, not panicking about the ones behind it.</p>
]]></content:encoded></item><item><title><![CDATA[What a Block Explorer Actually Shows You]]></title><description><![CDATA[A block explorer looks intimidating the first time you open it: rows of hashes, numbers and timestamps scrolling past. But almost everything on the screen…]]></description><link>https://chainnotesfm.hashnode.dev/what-a-block-explorer-actually-shows-you</link><guid isPermaLink="true">https://chainnotesfm.hashnode.dev/what-a-block-explorer-actually-shows-you</guid><dc:creator><![CDATA[Mason Carter]]></dc:creator><pubDate>Tue, 03 Nov 2026 13:58:53 GMT</pubDate><content:encoded><![CDATA[<p>A block explorer looks intimidating the first time you open it: rows of hashes, numbers and timestamps scrolling past. But almost everything on the screen is noise around a few signals that genuinely matter.
The three things worth reading
Ignore the raw hash strings. Focus on the amount moved, the addresses involved, and the fee paid. Those three tell you what happened and how urgent it was.
Confirmations are just patience
A transaction with one confirmation already happened. More confirmations only mean more blocks were built on top, making a reversal less likely. For small amounts, a handful is plenty.
Addresses are not identities
An address is a mailbox, not a name. The same person can hold hundreds. Treat any label you see as a guess unless the owner confirmed it themselves.
Fees tell a story
When you see someone pay a large fee for a small transfer, they were in a hurry or the network was busy. Fees are the clearest live gauge of how congested a chain is right now.</p>
]]></content:encoded></item></channel></rss>