<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>pokke-web3のブログ</title>
<link>https://ameblo.jp/pokke-web3/</link>
<atom:link href="https://rssblog.ameba.jp/pokke-web3/rss20.xml" rel="self" type="application/rss+xml" />
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
<description>ブログの説明を入力します。</description>
<language>ja</language>
<item>
<title>4 facts about TRON resource recovery</title>
<description>
<![CDATA[ <p>Consumed Energy returns gradually over 24 hours, as long as your account still has the stake or delegation that supplies its quota. The recovery clock moves with use: each smart contract call adds to the amount recovering, so a new USDT transfer can use Energy that has already returned while earlier Energy is still coming back.</p><ul><li>Energy recovers over a rolling 24-hour window, not at midnight.</li><li>A new contract call uses available Energy and starts more recovery.</li><li>If you need Energy sooner, you can obtain a delegation or let TRX cover the shortfall.</li></ul><h2>What does account resource recovery restore?</h2><p>Recovery restores the Energy quota your account used when running smart contracts. Energy pays for the computation a contract performs; Bandwidth covers transaction data, so it is a separate resource with its own usage and recovery.</p><p>Think of your quota like a bucket that refills at the same rate water drains away. If you use 600 Energy from a 1,000 Energy quota, that 600 does not return all at once after a day; it gradually becomes available over the next 24 hours. The account’s maximum quota remains tied to its stake or delegated resources.</p><p>TRON energy is commonly discussed in connection with USDT transfers because USDT on TRON is a smart contract token. A transfer uses Energy to run the token contract. If available Energy is insufficient, the network can burn TRX from the sender’s balance to pay for the uncovered Energy, subject to the transaction’s fee limit.</p><h2>How does the 24-hour recovery clock work?</h2><p>The clock is rolling, so it starts from each period of resource use rather than resetting once per day. For example, if a call uses 600 Energy at 10:00, that amount recovers progressively until about 10:00 the following day, assuming the quota backing it stays in place.</p><p>Suppose your account has a 1,000 Energy quota and spends 600 at 10:00. At 16:00, roughly 150 of that Energy has returned after six hours, leaving about 450 of the original use still recovering. If another call spends 200 Energy at 16:00, it begins its own recovery period, ending around 16:00 the next day.</p><p>This example shows the basic timing, not a promise of an exact balance at every moment. The network merges new use with recovery already underway, and the quota generated by staked TRX can change as total network staking changes. A USDT contract call can also consume a different amount of Energy depending on its execution.</p><h2>How can you check how much Energy has returned?</h2><p>Check the account’s current resource information in a wallet or block explorer that displays TRON resources. For a direct network query, TRON’s <em>GetAccountResource</em> endpoint reports fields such as <em>EnergyLimit</em> and <em>EnergyUsed</em>; the difference indicates the available portion of the account’s Energy quota at that point.</p><p>After a transfer, compare the figures again later rather than relying on the time shown in your local calendar. If EnergyUsed falls while EnergyLimit is steady, previously consumed Energy has recovered. If EnergyLimit changes, the amount of Energy your stake or delegation supports has also changed, so a simple countdown from one transaction may not explain the whole balance.</p><p>Look at the transaction’s resource details too: they help distinguish Energy consumed by the contract from TRX burned to cover a resource shortfall. A failed or pending transfer is a separate issue; waiting for recovery will not fix a wrong recipient address, a contract error, or an inadequate fee limit.</p><h2>What can you do if you need Energy before recovery finishes?</h2><p>You can wait for some Energy to return, stake TRX for your own Energy quota, receive Energy delegated by another account, or pay the shortfall in TRX when the transaction executes. Staking ties up your TRX and the quota depends on your share of network staking; delegation gives your wallet access to another account’s staked resource without requiring you to stake TRX yourself.</p><p>A service that rents or sells TRON energy can arrange a delegation to your wallet, which may help lower the TRX burned on USDT transfers without you staking TRX. Check the wallet address carefully before arranging any resource delegation, and never share your private key or recovery phrase.</p><p>In practice, I’d check the available Energy first, then compare waiting with obtaining a delegation for a time-sensitive transfer. If the transaction still fails, see <a href="https://cryptotalk.justblogged.com/tron-energy-4-checks-before-retrying-usdt-transfer">checks before retrying with TRON energy</a> for the checks that answer what to do before another USDT attempt.</p><h3>Does Energy recover if I pay the fee in TRX?</h3><p>No. TRX burned to cover a resource shortfall pays the transaction cost; it does not create Energy in your account or start a recovery period for that burned amount. Recovery applies to Energy quota consumed from stake or delegation. If a later transaction has enough quota available, it can use that quota instead of burning as much TRX.</p><h3>Does Energy recover after a delegation ends?</h3><p>It can, but ending a delegation may also reduce the recipient’s quota and reclaim a proportional share of its unrecovered Energy. That means the recipient may see less available Energy immediately, even though some earlier use was partway through its 24-hour recovery. Resource recovery and delegation changes can overlap, so check the account’s updated resource figures after the change.</p>
]]>
</description>
<link>https://ameblo.jp/pokke-web3/entry-12980265014.html</link>
<pubDate>Thu, 01 Oct 2026 02:09:06 +0900</pubDate>
</item>
<item>
<title>Why Manta Pacific Withdrawals Take Days</title>
<description>
<![CDATA[ <p>A withdrawal from Manta Pacific to Ethereum releases your funds through several on-chain steps. The main delay is the challenge period: for Manta Pacific’s native bridge, it is three days, and the process can take longer if a withdrawal is not yet ready to prove.</p><ul><li>A deposit to Manta Pacific is usually much faster than a native withdrawal back to Ethereum.</li><li>The first withdrawal transaction starts the process; it does not mean ETH is ready on Ethereum.</li><li>Plan for Ethereum gas and several days before you need the funds on mainnet.</li></ul><h2>Why does a withdrawal take longer than a deposit?</h2><p>Manta Pacific is an Ethereum Layer 2, or L2: a network that processes transactions separately and settles them back to Ethereum. A deposit sends ETH to the bridge on Ethereum, which then credits the matching balance on Manta Pacific. A withdrawal must prove that the L2 transfer happened before Ethereum releases the funds.</p><p>Manta Bridge follows this native L2 process. It is designed to let you move ETH and supported tokens between Ethereum and Manta Pacific, but withdrawals include extra checks. In an optimistic rollup, a type of L2 that allows time to challenge incorrect records, the challenge period gives the system time to dispute a withdrawal record.</p><p>That is why sending funds back is not like withdrawing from a centralised exchange. An exchange controls its own balance and can process an internal transfer; here, Ethereum must accept proof of the activity on Manta Pacific.</p><h2>What happens after the first transaction?</h2><p>First, your wallet submits a withdrawal transaction on Manta Pacific. That transaction starts the bridge message, which is an instruction to release the matching funds on Ethereum. It may appear complete on the L2 while the Ethereum side is still pending.</p><p>Next, the L2 transaction is included in data that Ethereum can check. A proof is evidence that the withdrawal is part of Manta Pacific’s recorded activity. The bridge submits that proof to Ethereum, where the challenge period applies. For Manta Pacific’s native route, allow about three days for this period.</p><p>After the period ends, a final transaction releases the funds on Ethereum. You may need to sign this step from your wallet, and it uses Ethereum gas: the network fee paid to process a transaction. So keep some ETH available on Ethereum for the proof and final release steps.</p><p>For example, if Lina sends 0.2 ETH from Manta Pacific on Monday, she should not plan to spend it from her Ethereum wallet that evening. She should watch for the proof and final release stages, then check that the ETH has arrived on Ethereum. The three-day period is a planning guide, not a promise of an exact arrival time.</p><h2>What should you check before withdrawing?</h2><p>Check which network holds the funds you need and when you need them. If you need ETH on Ethereum soon, start the native withdrawal several days ahead and leave extra time for proof availability, network delays, and the final Ethereum transaction.</p><p>Also account for costs on both networks. The Manta Pacific transaction uses L2 gas, while proof and release transactions use Ethereum gas; fees vary with network demand. Confirm the destination is your own Ethereum wallet, and keep the withdrawal transaction details so you can follow its status.</p><p>If you are moving ETH or a supported token between Ethereum and Manta Pacific, the <a href="https://graph.org/Manta-Bridge-which-transfer-route-fits-your-move-09-29">official Manta Bridge</a> is the route to handle that transfer. Choose the native withdrawal when you can wait through its proof and challenge stages; if timing is tight, keep the funds on Manta Pacific until you can allow several days for the return.</p>
]]>
</description>
<link>https://ameblo.jp/pokke-web3/entry-12980254766.html</link>
<pubDate>Wed, 30 Sep 2026 22:49:01 +0900</pubDate>
</item>
<item>
<title>Why USDT Swaps Need TRX</title>
<description>
<![CDATA[ <p>You may need TRX to swap USDT if the transaction uses smart contracts and your wallet lacks Energy. The amount depends on the contract, your available network resources, and whether the swap service covers any costs.</p><h2>TRX can pay the network cost of a USDT swap</h2><p>TRX is the network’s native token, and it can pay for the work needed to process a transaction. USDT on TRON is a TRC-20 token, meaning it follows rules set by a program on the TRON network.</p><p>A swap usually asks a smart contract—a program on the network—to exchange one token for another. That program uses Energy, TRON’s measure of the computing work a transaction requires. Transactions also use Bandwidth, which covers the data recorded on the network.</p><p>Think of a wallet as holding both your assets and your means of paying the network. TronLink can hold your USDT and TRX together, but having USDT alone does not guarantee you have enough resources to send a contract transaction.</p><h2>The amount depends on the transaction and your resources</h2><p>TRON uses available Bandwidth and Energy first. If you do not have enough, the network can burn TRX from your wallet to cover the shortfall. Some services may cover part of the Energy cost, so check the transaction details shown by your wallet.</p><p>Here is an example of why costs vary: an ordinary USDT transfer can use about 64,000 Energy when the receiving address already holds USDT, or about 130,000 when it holds none. At a network price of 100 sun per Energy—one TRX is one million sun—that would equal 6.4 or 13 TRX if paid entirely by burning TRX.</p><p>Those figures illustrate a token transfer, not a swap quote. A swap may do more work, and a service may cover some of it. The network’s Energy price and the contract’s current workload can also change.</p><h2>A first swap may need an extra transaction</h2><p>Some contracts need permission to use your token before they can swap it. This permission is called an allowance: it sets how much of a token the contract may move from your wallet. If the contract needs approval, your wallet may ask you to sign one transaction for that permission and another for the swap.</p><p>That matters because each on-network transaction can use resources. An approval does not exchange your USDT, and it does not mean the swap has completed. Check that you understand what each wallet request will do before you sign.</p><h2>Check the fee before signing</h2><p>Before you swap, check the transaction preview for the network cost and make sure your wallet has enough TRX to cover any amount it shows. Keep in mind that a displayed Energy limit is a cap, not necessarily the amount the transaction will use. If the transaction runs out of Energy, it can fail, and some Energy may still be charged.</p><p>If your first attempt fails for lack of Energy, pause before trying again. Check the failure message and the new cost estimate; the contract may need more Energy than your wallet had available. Sending more USDT does not solve a shortage of TRX or Energy.</p><p>In short, keep some TRX available when swapping USDT, unless the transaction preview makes clear that the network cost is covered. The cost depends on the contract and your resources, so check the estimate each time; the <a href="https://prestonbcfz405430.bleepblogs.com/43030433/tron-swap-how-to-exchange-trx-and-trc-20-from-a-wallet">TRON swap</a> service is one way to exchange TRX or TRC-20 tokens from a wallet.</p>
]]>
</description>
<link>https://ameblo.jp/pokke-web3/entry-12980239720.html</link>
<pubDate>Wed, 30 Sep 2026 20:08:20 +0900</pubDate>
</item>
</channel>
</rss>
