Staking Guide Hub

If your funds are on another chain and the recipient is on Monad, send directly to a repeat recipient; route to your own wallet first when you need to verify what arrived before handing it over. What changes when you choose direct delivery? Direct delivery removes one Monad transaction, saving time and its network fee. You select the recipient’s Monad address as the destination when setting up the bridge transfer, so the bridged funds arrive there without first passing through your wallet. That means you do not get a chance to inspect the received token or amount before the recipient controls the funds. The address shown as the sender may be a bridge, solver, or mint address—a contract involved in delivering the transfer—not your wallet. If the recipient checks transaction history, they may see that address rather than your name or wallet. For a contract or service address, confirm first that it accepts the specific token you plan to send. A successful delivery to an address does not g...

If you’re returning after months away, the amount you type last is the fixed side: enter a sell amount to lock what you spend, or a receive amount to lock what you get. The other side can move within your slippage tolerance, so the field you edit—and the bound shown beside the quote—tell you what the trade is allowed to do. The last field you edit selects the swap mode Typing into the sell field creates an exact-input swap: the amount of the token you send is fixed, and the amount you receive is estimated. Typing into the receive field creates an exact-output swap: the amount you want to receive is fixed, and the amount needed to buy it is estimated. If you edit the receive field after entering a sell amount, the interface switches modes, even if the screen still looks like the same trade. That switch changes which risk the quote limits. With exact input, the router spends the specified input and requires the output to meet a minimum. With exact output, it aims to deliver the specified...

If your integration selects addresses and native-asset settings from the connected chain ID, it can route swaps on Ethereum and Shibarium without applying Ethereum assumptions to Shibarium. Which settings must change with the chain? Keep a separate configuration for each chain ID, and select it before quoting or building a transaction. At minimum, each entry needs the swap contracts your integration calls, supported token addresses, the wrapped native token, the gas token, and an explorer base URL. These values are network-specific because the same token or contract name does not guarantee the same address on both networks. In particular, do not carry an Ethereum token address into a Shibarium configuration: it may have no code or may refer to a different contract. Native gas is ETH on Ethereum and BONE on Shibarium; each network also has its own wrapped native token address. For each chain, keep token metadata and pool or route availability alongside the configured addresses. A token ...

If your app is considering a SunSwap pool’s current price for collateral, do not treat that price alone as a safe valuation input. A pool reports the exchange rate implied by its reserves at that moment; it does not independently verify what the token is worth across markets. That makes the quote useful for describing a trade in that pool, but a weak default for deciding how much credit to grant. For example, a SunSwap pool’s marginal price—the rate for a very small additional trade—can help estimate what a swap would cost near the current reserves. It does not establish that a large position could be sold at that rate, or that the rate is hard to manipulate. What does a SunSwap V2 pool price tell a collateral app? A V2 pool price tells the app the ratio between the pool’s token reserves, not an independently verified market valuation. A swap changes those reserves, so it also changes the implied price that another contract may read immediately afterward. The sequence matters. A trade...

After you burn teleBTC in TeleSwap, you get a recorded request for a Locker to send native BTC by a deadline; confirmation does not guarantee that Bitcoin has been paid. If the Locker misses the deadline, the fallback is collateral tokens on the destination chain, whose value depends on the collateral and the oracle price when it is slashed. A burn records a request, not a Bitcoin transfer Burning teleBTC commits a Locker to pay the specified amount of BTC to the Bitcoin address recorded in the request before its deadline. The burn transaction destroys the teleBTC and records the amount, address and deadline on the destination chain. That record establishes the obligation; it does not show that a Bitcoin transaction has happened. So if you are asking whether the BTC payout is certain, the answer is no. The burn confirms that your request exists, but the Locker still has to make the Bitcoin payment. A valid proof of that payment must reach the destination chain to close the request. Unt...

If your LST is merely trading below its expected ETH value, eigen layer does not guarantee you can recover that value in ETH; the discount affects what a market buyer may pay, while redemption depends on the issuer’s rules and backing. What does an LST discount tell you? A depeg is a market price below the token’s expected ETH value, including exchange-rate growth accumulated by the LST. The gap alone does not prove that the underlying ETH is missing. A buyer may demand a discount because secondary-market liquidity is thin or because issuer withdrawals are delayed. Lido’s Public Risk Disclosure distinguishes protocol withdrawals from secondary-market trades: a withdrawal’s ETH amount follows protocol accounting and may be affected by staking losses, while a market sale depends on the price and liquidity available at execution. So an LST quoted below its expected value can still have backing, but selling immediately may realize the discount. Does eigen layer guarantee ETH when you withd...

If your tokens are on Arbitrum or Base, you cannot send them straight to Polygon through the Ethereum-to-Polygon bridge. Why The Token’s Current Network Matters The deciding factor is where the tokens are now. Polygon bridge is the route for funds already on Ethereum, while an Arbitrum balance needs a route out of Arbitrum first. The same applies to funds on Base. The reason is in the contracts: Polygon’s PoS bridge deposit flow begins at the RootChainManager contract on Ethereum mainnet. Polygon Knowledge Layer’s PoS bridge documentation describes that contract as the Ethereum-side entry point for deposits to Polygon PoS. There is no corresponding entry point on Arbitrum or Base, so changing the destination in a wallet does not make those networks valid sources for this bridge. That leaves two routes to compare: Exit to Ethereum, then deposit. Withdraw from the rollup to Ethereum, then use the Ethereum-to-Polygon bridge. Use a third-party direct route. Services such as Across, Star...

Your share of a service reward depends on the strategies it funds, your operator’s allocation and split, and your weighted share of that operator’s stake; it is claimable only after a reward root is posted. These factors explain why similar positions can earn differently, even when no advertised rate captures the whole calculation. Service strategy choices set which stake counts A service funds rewards for specified tokens or strategies over a stated period, so a position earns from that service only if it includes an eligible strategy. A token can be restaked and still earn nothing from a particular service when that service has not selected its strategy. When a service assigns strategy weights, those weights affect how much stake counts in its distribution. Two tokens with the same market value can therefore contribute different weighted amounts. For example, if two positions have equal value but one is in a strategy receiving greater weight, that position can represent a larger frac...

If your wallet account was created from a standard seed phrase using the same derivation path, restoring that phrase restores its EVM keys and addresses, so funds at those addresses remain accessible across networks. Network entries and display choices are stored separately in the wallet. Accounts imported by private key or derived by another path need separate backups. What The Seed Phrase Restores A seed phrase is the recovery input for keys, not a copy of the wallet app or its settings. In a standard setup, the wallet turns the phrase into a seed and derives one or more private keys and public addresses from it. The private keys authorize transactions; the addresses identify where funds are recorded on a blockchain. BIP-39, the Bitcoin Improvement Proposal for mnemonic codes, specifies in its “From mnemonic to seed” section how a wallet converts a mnemonic phrase, with an optional passphrase, into a cryptographic seed. BIP-44, “Multi-Account Hierarchy for Deterministic Wallets,” spe...

Connecting your wallet to a Berachain bridge site reveals your public address, but it does not let the site move funds unless you separately approve a later wallet request. What Does Connecting Actually Share? Connecting lets the site see the address you choose to share and read public blockchain information associated with it, such as token balances. It gives the site a way to ask your wallet to do things; it does not give the site your private key or let it sign on your behalf. That distinction matters when you are preparing a transfer. For example, the Berachain bridge may need your address to show the assets available for bridging. Seeing a balance helps the site prepare the next step, but it does not authorize a transfer of those assets. EIP-1193, the Ethereum Improvement Proposal that defines the JavaScript provider interface, describes how a site requests accounts and other wallet actions through the provider’s request method. In practice, the wallet presents those requests fo...

An audit supports a cBridge route only to the extent that its reviewed contracts, version and scope match the route you plan to use. Match the audit to the route’s bridge contracts Start by identifying the route’s source and destination networks, token and bridge model; then find the audit report for the contracts that handle that transfer. The cBridge Audit Reports index separates liquidity-bridge and canonical-bridge reports, so an audit for one model does not automatically apply to the other. A token’s route can depend on which model handles it, not just on the networks involved. Before proceeding, confirm that the token and network pair are currently supported; cBridge supported chains is relevant to that eligibility question. Support alone does not tell you which contracts implement the route or whether those contracts match an audited version. Use the official report links to read the report itself and identify the component, version and stated review scope. A report’s scope is ...

In an eth_callBundle response, each transaction’s results entry tells you whether it reverted and how much gas it used, while coinbaseDiff and bundleGasPrice show what the block’s fee recipient earns. Read the transaction entries even if the RPC call itself returned successfully. These figures describe execution against the state you selected, which can differ from the state when the target block is built. Read each transaction result before judging the bundle Each entry in results reports an individual transaction’s outcome and gas use. Match entries to your submitted transactions using txHash ; gasUsed shows how much gas that transaction consumed, and an error field or revert information signals a failure. A successful JSON-RPC response only means the simulation returned a result. It does not mean every transaction inside the bundle succeeded. This distinction matters because bundles execute transactions in order. If an earlier transaction reverts, a later transaction may no l...

If you bridge from Ethereum and plan to swap on the destination chain, routing the deposit through Flashbots Protect does not automatically protect that later swap. Protect handles the Ethereum transaction submitted to it; bridge delivery and destination execution use separate infrastructure, unless the route provider can show that it separately protects destination submission. A bridge route has separate execution stages A bridge deposit and a destination swap are separate operations, even when one application button presents them as a single route. The Ethereum transaction locks, burns, or otherwise commits the assets on the source chain. After that transaction is confirmed, the bridge’s delivery mechanism processes a message or transfer so the destination chain can release or mint assets. The destination swap then runs through the bridge application’s executor or another destination-side transaction path. That execution may happen automatically, but “automatic” describes how the ap...

For a large cBridge transfer, split only when quotes show that size is worsening the pool rate or triggering a delay or cap; otherwise, send it once. Pool routes can offer a worse rate as they use destination liquidity, while mapped-token routes do not price against pool balance. Compare the amount delivered after all fees, not just the quoted rate. Pool liquidity can make a large transfer less efficient On a pool route, a large transfer can receive a worse rate because it draws more heavily on the destination-side token liquidity. The pool has a finite balance available to fulfill transfers, and using more of it can change the rate applied to the amount. A quote for the whole transfer reflects that size effect. Splitting may improve the rate if each smaller transfer draws less liquidity at once. But the improvement is not guaranteed: it depends on the route, pool balances and the quotes available when each part is sent. If the first transfer changes the pool balance, later parts may ...

You can change the settings for upcoming transactions by replacing the Protect RPC URL in your wallet’s Ethereum mainnet network entry, or by adding a second entry with a different URL. The settings travel in that URL, so each new submission uses whatever the selected entry contains. Transactions already pending keep the settings they were sent with. Where are the settings stored? Flashbots Protect settings are encoded in the RPC URL saved for a network in your wallet. An RPC URL is the address the wallet contacts to submit a transaction; query parameters after a question mark tell Protect which preferences to apply. If the URL has no query parameters, Protect uses its default privacy setting. Privacy hints control what transaction information is shared with searchers through MEV-Share. Sharing fewer hints can improve privacy, while sharing more can make it easier for searchers to identify opportunities that may produce refunds. The URL can also include builder preferences and refund ...

To budget MON when a transaction looks expensive, compare its gas limit and effective gas price, because Monad charges their product rather than the gas it actually uses. Charging by the limit helps protect Monad’s asynchronous execution from work being priced too cheaply. When an app’s estimate is tight, the difference between limit and usage is small. The gas limit sets the fee Your wallet’s gas limit is the maximum amount of gas the transaction is allowed to use. The fee is calculated from that limit and the effective gas price: fee in MON = gas limit × effective gas price. Gas used tells you how much work the transaction consumed; it does not lower the fee. For example, if an explorer shows a limit of 300,000 and an effective price of 50 gwei, the fee is 0.015 MON, whether the transaction used 180,000 gas or nearly all 300,000. Those figures are illustrative. For people funding Monad bridge transfers , the same fee rule applies to the Monad transaction involved; a bridge transfer ...

No: SunSwap cannot take a TRC-10 asset directly as a TRC-20 swap input, even when both appear in the same TRON wallet. Why a TRC-10 token is not a swap input TRC-10 tokens are identified at the TRON protocol level, while TRC-20 tokens are managed by smart contracts. SunSwap’s token-swap interfaces use token contract addresses, so a TRC-10 token’s numeric identifier cannot fill the same role. Sharing the TRON network does not make the standards interchangeable. A wallet may display and transfer several kinds of TRON assets; the SunSwap token swap is the narrower case of trading assets through token-contract inputs. TRON’s Token Standards Overview explains the protocol-level TRC-10 and contract-based TRC-20 distinction. In SunSwap V2 Main Interfaces, the “Performing Swaps” section shows contract-address paths for token swaps and separate entry points for TRX. What the wallet and explorer can tell you If a wallet token cannot be selected, its standard can explain why before you investig...

If you are about to use your Ethereum Safe address as the recipient, first confirm that a Safe with the same owners is deployed at that address on Berachain. The address alone does not make your Ethereum Safe available on another chain. A Berachain bridge transfer raises two separate questions: whether the destination can receive funds and how the supported asset gets there. Once you have confirmed the recipient, the Berachain bridge service relates to the second question: moving supported assets between chains. An Ethereum Safe works as a Berachain recipient only if it is deployed there A regular wallet address can be used across EVM chains, but a Safe is a smart contract wallet: its contract must be deployed separately on each chain. So, if your Safe app shows an Ethereum Safe at a particular address, that does not mean the same contract exists on Berachain. For example, you might copy your familiar Ethereum Safe address into a bridge recipient field and assume the funds will appear...

A native ETH deposit through Polygon bridge can be rejected even when the estimated fee looks affordable, because your Ethereum balance must cover both the deposit value and the transaction’s maximum gas liability. This calculation applies to a standard Ethereum transaction using EIP-1559 fees. The fee shown as an estimate is not necessarily the amount the transaction must be able to cover before it is submitted. When you are comparing that upfront reserve with the eventual charge, why Polygon bridge fees can be lower is the related question: the fee cap sets the maximum reserve, while execution determines the final fee. A lower eventual charge does not make a transaction affordable if your balance cannot cover its maximum liability at submission. Why the estimated fee can be too low Ethereum checks the ETH value being sent as well as the gas limit multiplied by the maximum fee per gas. The gas limit is the most units of computation the transaction may use; the fee cap is the most ET...

No: a service cannot freely borrow or spend the ETH you restake on eigen layer; your assets provide security backing under defined conditions. That backing can be exposed to slashing, and it may not be immediately withdrawable. Understanding what eigen layer restaking means for your ETH helps separate security commitments from lending: services rely on economic backing for operator work, rather than receiving your principal as treasury funds. Restaking adds security exposure, not another pot of ETH Restaking reuses the economic value already associated with your stake. It does not create a second, spendable copy of the underlying ETH. A service can benefit from having operators backed by committed assets, but that does not mean the service controls those assets or can use them to pay expenses. The distinction is between backing and borrowing. A borrower receives funds and can generally put them to use under a loan agreement. With restaking, the asset remains committed to security con...

If search results show several similar names, use a trusted DefiLlama link and proceed only when your wallet asks to add or switch a network. Start with a trusted route to the directory When you have no bookmark, I’d use a link from DefiLlama’s official channels rather than a search result. Chainlist is maintained by DefiLlama, and its own channels link to the site. That gives you a route tied to the maintainer, while a search listing only shows that a page matched your query. Search results can include sponsored placements, which may appear above ordinary results. A prominent position or familiar-looking name does not prove who operates the site. Phishing copies can imitate a network directory’s layout, so a page that looks right is not enough to establish that it is the intended service. After reaching the directory through a trusted source, bookmark that verified page. On later visits, open the bookmark instead of searching again. This reduces the chance of landing on a lookalike, a...