On this page
Shiba Inu is an Ethereum token with the ticker SHIB, surrounded by a larger collection of trading, governance and blockchain products. Those products share a community, but they do not share one interchangeable token. SHIB is not the gas currency of Shibarium, and holding it does not make someone a validator of that network.
That distinction explains much of the project. A development involving BONE, LEASH or a bridge can matter to the ecosystem without changing the original SHIB contract. Understanding which asset and which network an announcement concerns is more useful than treating every Shiba Inu headline as a change to SHIB itself.
From Ryoshi's community experiment to a wider ecosystem
SHIB launched on Ethereum in 2020 under the pseudonymous founder Ryoshi. In an August 2, 2020 statement, Ryoshi described an experiment in community ownership, with an initial distribution involving a Uniswap trading pool and tokens sent to Ethereum co-founder Vitalik Buterin. Sending tokens to a known person's wallet did not make that person the project's founder or imply an endorsement.
The project subsequently developed beyond its meme-token origins. Its products include the ShibaSwap decentralized exchange, Shibarium, governance tools and digital collectibles. Contributors have used public pseudonyms, including Shytoshi Kusama and developer Kaal Dhairya. Product development, community voting and control of particular contracts should be assessed separately; a community-led identity does not establish that every operational decision is decentralized.
Shibarium's mainnet launch on August 16, 2023 added a network on which developers could run applications. The Shib Magazine's retrospective records that launch, while current documentation describes a broader collection of tools rather than a replacement for the original Ethereum token.
How SHIB transfers differ from Shibarium transactions
On Ethereum, SHIB follows the ERC-20 token standard. A smart contract records balances, transfers and spending permissions. Ethereum's validators secure the chain using proof of stake, with ETH rather than SHIB staked at the protocol level. A normal SHIB transfer on Ethereum also needs ETH to pay its network fee. The Ethereum profile explains that underlying network.
SHIB has no independent block interval or separate mining process. Its transaction inclusion depends on the network carrying the transfer. Fees vary with demand and the operation being performed: moving tokens and executing a swap involve different computational work. A token's low unit price does not mean its transaction fee will be low.
Shibarium has its own proof-of-stake validator system, inspired by Polygon PoS. Its documentation describes two cooperating layers: Heimdall manages validators and checkpoints, while Bor produces blocks and executes Ethereum-compatible smart contracts. BONE is used for validator staking and network fees. Checkpoints are submitted to Ethereum.
The project markets Shibarium as a Layer 2, but its separate validator and bridge arrangements matter. Posting checkpoints to Ethereum does not erase those additional trust assumptions. The guide to Layer 2 networks explains why networks described with the same broad label can offer different security properties.
Shibarium is designed for faster, cheaper application activity than Ethereum mainnet. That is a design aim, not a fixed delivery time for every transaction. A local confirmation, a checkpoint and completion of a bridge withdrawal are different milestones. A short block interval alone says little about how quickly funds become available on another chain.
What SHIB, BONE and LEASH actually do
SHIB can be transferred, traded and used by applications that support it. ShibaSwap allows wallet-based trading and liquidity provision on Ethereum and Shibarium. Providing liquidity means supplying assets to a trading pool; the resulting exposure and contract risks differ from simply holding SHIB. The decentralized exchange guide covers those mechanics.
BONE's role is more directly connected to Shibarium operations through gas and validator staking. LEASH is a separate ecosystem token associated with access and governance features. TREAT is another token, described by the project as serving rewards and utility functions. None should be assumed to confer the same rights as SHIB.
Governance adds another distinction. The Shib DAO documentation describes participation involving all four tokens. As checked on October 31, 2026, the more specific Bury 2.0 instructions describe a beta system in which users lock supported tokens to obtain voting power, with no staking rewards currently offered. The instructions also specify an early-withdrawal penalty. Locking SHIB for governance is therefore not the same activity as staking BONE to help secure Shibarium.
Supply and burns require careful accounting
SHIB began with one quadrillion tokens in 2020. The original contract's deployment arguments and 18-decimal setting support that figure. Its published code creates the initial supply during deployment and exposes no ongoing public mint function. SHIB does not issue new tokens as block rewards.
Burning also needs a precise definition. The contract includes a burn function that reduces its supply counter. Sending tokens to an address treated as inaccessible can instead remove them from practical circulation while leaving them in the contract's accounting. Consequently, a raw total-supply figure, an adjusted post-burn figure and a circulating-supply estimate need not match.
ShibTorch connects network fees with another burn mechanism. The project's June 5, 2025 explanation says accumulated BONE base fees fund purchases of SHIB on Ethereum for burning, with initiation subject to a threshold. That mechanism should not be confused with every ordinary SHIB transfer automatically destroying part of the sender's tokens.
A percentage increase in the daily burn rate is not the percentage of all SHIB destroyed. Its significance depends on the absolute amount, the measurement period and the supply used for comparison. Burns alone do not establish future demand or a price outcome. No undated running burn total is used here.
Security history and the limits of current status
The ecosystem's own reporting identifies reasons to examine individual products closely. On September 22, 2025, The Shib Daily reported developer Dhairya's account of a September 12 bridge exploit involving compromised validator signing power. Its report described restrictions on bridge operations and changes to keys and contract protections. This was a bridge incident, not evidence that the original Ethereum SHIB contract had started issuing unauthorized tokens.
LEASH has a separate complication. The project's publications reported a rebase problem in August 2025 and a proposed migration to LEASH v2. A rebase changes token supply and balances. Older descriptions presenting LEASH's original supply as permanently fixed therefore need qualification. An announced migration plan is not evidence that every holder or exchange has completed it.
As of the October 31, 2026 review, the official site and documentation continue to present SHIB and the surrounding ecosystem as active. This does not independently establish uninterrupted operation of every bridge, completion of LEASH migration or compensation for every affected user. Those are separate status questions.
For SHIB holders, the main risks include volatile demand, custody failures, malicious approvals, bridge vulnerabilities and changes to application rules. A familiar ticker does not identify a contract across different chains. The crypto wallet guide explains custody and recovery responsibilities. Before signing a transaction, identify the network, token contract, recipient and permission being granted; those details determine what the action actually does.