Shibainu
Shibainu Shibarium uses BONE for gas while Ethereum mainnet uses ETH
Shibainu Shibarium runs transactions on a separate proof-of-stake network and charges gas fees in BONE. Ethereum mainnet operations use ETH for gas. Bridges connect supported assets between the chains, while Shibarium’s validators process local activity. Matching wallet addresses do not merge balances or remove the bridge’s exit conditions.
Network selection before a Shibarium transaction
A Shibarium transaction requires a wallet connected to its mainnet and enough native BONE for execution, alongside any tokens the operation spends. Mainnet uses chain ID 109. An ordinary transfer or application interaction draws its fee from the sending account’s native balance on that chain. BONE held on Ethereum remains an Ethereum token balance, even when the account address looks identical. Selecting another network in the wallet changes the ledger the wallet reads; it does not move assets. An insufficient-gas message therefore calls for a native-balance check before another attempt.
If the expected balance exists on Shibarium but the wallet does not display it, inspect the network connection and token display settings. A missing display alone does not establish that a bridge deposit failed.
Does Shibarium charge gas in SHIB or BONE?
Shibarium charges ordinary network gas fees in native BONE, including when a transaction transfers SHIB or interacts with a token contract. Gas measures computational work. BONE pays for that work. The amount of SHIB a contract transfers and the BONE fee belong to different parts of the transaction, so a large token balance cannot automatically cover the native fee requirement.
BONE also supports validator staking, a separate function from paying wallet transaction fees. SHIB burns concern removing SHIB from circulation; they do not change the native gas asset. An application’s own trading fee or other contract charge can add another cost, expressed in the asset its rules specify.
Bor execution and Heimdall checkpoints
Shibarium’s Layer 2 architecture separates Bor execution from Heimdall validator coordination. Ethereum contracts handle staking and checkpoint records.
Bor and the Ethereum Virtual Machine
Bor produces blocks and executes smart contracts through the Ethereum Virtual Machine, or EVM. This compatibility supports familiar contract interfaces and development tools. It does not make a contract deployed on Ethereum automatically appear on Shibarium. Each deployment has separate balances and state, even if its address matches one on another chain, and an application must support the selected chain.
Heimdall and Ethereum records
Heimdall coordinates validators and checkpointing. Heimdall submits Shibarium checkpoints to Ethereum. A checkpoint commits a record of Shibarium activity for cross-chain verification. Validators stake BONE through Ethereum contracts to participate in the network’s proof-of-stake system. Ethereum anchoring leaves meaningful dependencies on Shibarium’s validators and bridge contracts; it does not make every local transaction an Ethereum mainnet transaction.
Fee estimates and actual BONE charges
A Shibarium fee estimate describes the expected execution cost of a particular transaction, while its receipt records the gas the transaction actually consumed. The execution fee equals gas used multiplied by the effective gas price. Express both inputs in compatible units to obtain a BONE amount.
The gas limit caps the computational work available to execution. It differs from the gas price, which sets the charge per unit. Contract calls can require more work than a simple native transfer, and the same application action can encounter different contract states.
The maximum network fee a wallet shows can exceed the eventual execution charge.
A percentage trading fee belongs to the application’s pricing rules and uses its stated asset and calculation basis. Comparing it directly with a BONE network fee obscures their different units. A transaction involving Ethereum also brings an ETH-denominated cost, so Shibarium’s local fee estimate does not cover the entire bridge journey.
Application contracts and token permissions
Shibarium applications execute through deployed contracts, whose token permissions and operation-specific conditions govern the action the wallet authorizes. Network compatibility supplies an execution environment, not universal application support.
Allowances for the intended spender
An ERC-20 allowance authorizes a specified spender to use tokens up to the approved amount. The allowance applies to that token contract and network. Ethereum permissions do not automatically carry over to Shibarium. Inspect the spender and amount before granting access, because the permission can enable later spending within its scope.
Application results beyond a receipt
ShibaSwap has deployments on Shibarium, where swaps and liquidity actions incur BONE network fees alongside their own pool rules. A successful contract receipt confirms execution without establishing the economic quality of a trade. Token transfer events, resulting balances, and the application’s recorded position describe what the transaction actually changed.
Ethereum deposits and Shibarium token mappings
Depositing supported assets from Ethereum into Shibarium uses bridge contracts and cross-chain processing, so an Ethereum deposit and a usable Shibarium balance represent different stages. Ethereum-side transactions require ETH.
Mapped tokens and destination balances
For tokens using the bridge’s lock-and-mint model, the bridge locks the Ethereum asset and creates its mapped representation on Shibarium. State synchronization communicates the deposit across the networks. The token mapping identifies the corresponding contracts; a matching ticker alone cannot establish that relationship. ERC-20 compatibility does not automatically provide bridge support for every token.
Available routes and token restrictions
Bridge support depends on the token, direction, and enabled contract path. Shibarium has PoS and Plasma bridge mechanisms with different exit procedures. BONE uses the Plasma route. A token list or general standards description does not establish that every asset can currently use every route. Bridge pauses or token restrictions can prevent the selected deposit or withdrawal.
Gas and completion evidence across network actions
A local BONE transfer and a BONE bridge withdrawal both move value, yet their gas requirements and completion evidence differ. The intended recipient network determines which action fits.
| Action | Network gas asset | Evidence of the intended change | Failure or incomplete state |
|---|---|---|---|
| Native BONE transfer on Shibarium | BONE | Successful receipt and matching recipient credit | Insufficient BONE for the amount plus gas |
| ERC-20 transfer on Shibarium | BONE | Token transfer event and recipient token balance | Wrong token contract or transfer restriction |
| ERC-20 approval on Shibarium | BONE | Allowance for the specified spender | Permission does not establish a token transfer |
| Application contract call on Shibarium | BONE | Successful receipt and intended contract state | Contract revert or unmet operation condition |
| ERC-20 bridge approval on Ethereum | ETH | Allowance for the intended bridge spender | Approval alone does not complete a deposit |
| BONE deposit from Ethereum | ETH for Ethereum transactions | Source deposit and destination native BONE credit | Source confirmation without destination processing |
| BONE withdrawal to Ethereum | BONE on Shibarium and ETH for Ethereum exit | Completed Ethereum exit and recipient BONE credit | Exit restrictions, waiting period, or insufficient ETH |
For the local transfer, a successful receipt and the intended recipient credit establish the balance movement on Shibarium. For the bridge withdrawal, the comparable endpoint is BONE reaching the intended Ethereum address through the completed exit. A Shibarium burn receipt establishes an earlier stage of that withdrawal. Local transfer is appropriate when the recipient needs native BONE on Shibarium; withdrawal serves a recipient who needs its Ethereum representation.
Bridge security and BONE withdrawal restrictions
The Shibarium bridge suffered a security breach on September 12, 2025, involving unauthorized validator signing power and asset withdrawals. BONE Plasma bridging subsequently resumed. The October 2025 relaunch introduced a mandatory withdrawal delay and address-blocking controls for BONE Plasma withdrawals. These restrictions concern that bridge route, rather than every Shibarium transaction. The bridge must accept the withdrawal proof and clear any applicable waiting period before the exit can finish.
A local block confirmation does not shorten a bridge challenge window. Cross-chain movement exposes assets to bridge contracts and validator authorization as well as the source and destination networks. Low local gas charges do not describe that separate exposure.
Shibarium activity and the Ethereum exit boundary
Keeping an application action on Shibarium makes sense when its deployed contracts and accepted token representations satisfy the intended use. Returning an asset to Ethereum adds the bridge’s exit requirements and Ethereum transaction fees. EVM compatibility alone cannot answer which representation a receiving application accepts. The relevant choice changes when the destination requires an Ethereum balance: the Shibarium withdrawal receipt records an intermediate stage, and Ethereum settlement becomes the required endpoint.
Practical questions
Does a reverted Shibarium transaction still consume BONE?
A Shibarium transaction that executes and reverts still charges BONE for the gas it consumes. The revert rolls back its contract state changes, while the execution charge remains. An error before submission or rejection before block inclusion is different and does not itself create an on-chain gas charge. The receipt distinguishes an executed failure from a transaction that never reached execution.
Can WBONE pay an ordinary wallet transaction’s native gas fee?
WBONE does not automatically supply the native BONE balance an ordinary Shibarium wallet transaction needs for gas. Wrapped BONE exists as a token contract balance, separate from the account’s native balance. Unwrapping it changes that representation, and the unwrapping transaction also needs native gas.
Is checking a Shibarium balance a transaction that costs gas?
Reading a Shibarium balance through an ordinary blockchain query does not require a paid on-chain transaction. A wallet or application can request existing state without changing it. Contract view calls made through a read-only query likewise avoid an on-chain gas charge. The same computation can consume gas when another contract performs it during an executing transaction.
Are Puppynet BONE balances valid on Shibarium mainnet?
Puppynet BONE cannot pay Shibarium mainnet transaction fees because the testnet and mainnet maintain separate balances. Puppynet uses chain ID 157, while Shibarium mainnet uses chain ID 109. The shared BONE symbol does not merge those ledgers. A testnet transaction confirms activity in the test environment and does not establish that a mainnet deposit or payment occurred.
Why can a contract call show zero BONE sent and still charge a fee?
A contract call can carry zero native BONE as its transfer value while consuming BONE for execution. The transaction’s native value and its gas charge describe different amounts. A token contract can move ERC-20 balances without sending native BONE as the call’s value. Its token events show that movement, while the receipt’s gas fields describe the network execution cost.
Will a larger gas limit make my Shibarium transaction confirm faster?
Increasing a Shibarium transaction’s gas limit does not directly increase its fee bid or guarantee faster inclusion. The limit sets how much computational work execution may consume. A pending transaction can face a fee setting below network requirements or wait behind an earlier transaction from the same ordinary account. A higher work ceiling does not resolve either condition by itself.
Does staking BONE supply a spendable Shibarium gas balance?
BONE committed to validator staking on Ethereum does not become spendable native BONE in a Shibarium wallet. The staking contract accounts for the committed tokens separately. Staking interactions and reward withdrawals on Ethereum require Ethereum gas, and rewards paid to an Ethereum address remain on that network. The wallet’s native Shibarium balance determines whether it can fund ordinary Shibarium execution.