docs.shibariumtech.com Open in urlscan Pro
172.64.147.209  Public Scan

Form analysis
0 forms found in the DOM

Text Content

SHIBARIUM



SearchCtrl + K
 * Welcome To Shibarium
    * Overview
    * Shibarium PoS chain
    * Building on Shibarium
    * Architecture
       * BOR
       * Heimdall
   
    * Bridge
       * Ethereum to Shibarium
       * Shibarium to Ethereum
       * Deposit Token
       * Withdraw Token
          * PoS Withdrawal
          * Plasma Withdrawal (BONE)
      
       * Ethereum + Shibarium Bridge
   
    * Node Setup
       * Add new Node using Ansible (Testnet)
       * Heimdall and Bor Snapshots
       * Start the node
       * Add new Node using ansible (Mainnet)
   
    * Security models
    * Staking - Validators and Delegators
    * Delegate
       * Delegators - FAQ
   
    * Validate
       * Validator Responsibilities
       * Maintaining your validator node
       * How to Become a Validator (Testnet)
   
    * Staking Manager
    * Burns
    * Deploy smart contracts
    * MetaMask Installation & Set up Web3 RPC URL

 * Blockchain
    * Ethereum
    * What is a Blockchain?
    * Types of Blockchain
    * What is a Side-chain?
    * Consensus Mechanism
    * Proof of Stake
    * Solidity
    * Transactions
    * Gas
    * Accounts

Powered by GitBook


BRIDGE

INTRODUCTION

Welcome to the documentation for our Token Bridge, a vital infrastructure
component of our Shibarium blockchain. This guide aims to provide an overview of
what the Token Bridge is, its significance, and a summary of how users can
interact with it.

WHAT IS THE TOKEN BRIDGE?

The Token Bridge is a functionality that allows for the secure and seamless
transfer of tokens between our Ethereum and Shibarium blockchain. By using this
bridge, users can enjoy the benefits of the scalability, low fees, and fast
transactions offered by the Shibarium network while remaining connected to the
broader Ethereum ecosystem.

Access the Token Bridge here.

WHY USE THE TOKEN BRIDGE?

    

 1. Scalability: Migrating tokens to the Shibarium network lets users benefit
    from higher throughput and low latency.

    
    

 2. Reduced Transaction Costs: Transaction fees on the Shibarium network are
    generally much lower, making it a more cost-effective platform for trading
    and yield farming activities.

    
    

 3. Speed: Faster Shibarium network block times allow quicker transaction
    confirmations.

    
    

 4. Interoperability: Keep the utility and functionality of your tokens across
    different layers of the blockchain.

    
    

 5. Accessibility: Transferring tokens to Shibarium allows users to participate
    in Shibarium-specific decentralized applications (dApps), services, and
    protocols unavailable on the Ethereum network.

    
    

 6. Security: The Token Bridge employs state-of-the-art cryptographic techniques
    to ensure that transactions are secure and tokens are transferred safely
    between Ethereum and Shibarium.

    

PLASMA AND POS TOKENS

In Shibarium infrastructure, we support two types of tokens: Plasma tokens and
Proof-of-Stake (PoS) tokens.

BONE Token (Plasma)

The BONE token operates under the Plasma framework, which ensures high
scalability and security. Plasma tokens like BONE allow for rapid and low-cost
transactions and can be securely withdrawn to the Ethereum network via the
Plasma Bridge.

PoS Tokens

All other supported tokens on our Token Bridge are PoS tokens. These tokens
leverage our Proof-of-Stake consensus mechanism, balancing efficiency with
security. PoS tokens can be quickly and securely transferred between Ethereum
and Shibarium through the Token Bridge.

SUPPORTED TOKENS

At present, the Token Bridge supports only a curated list of tokens. This list
is continuously updated to ensure security and compatibility with our networks.

PreviousHeimdallNextEthereum to Shibarium

Last updated 2 months ago

On this page
 * Introduction
 * Supported Tokens



This site uses cookies to deliver its service and to analyse traffic. By
browsing this site, you accept the privacy policy.

AcceptReject