Resource

• https://docs.avax.network/apis/avalanchego/apis/info

• https://docs.avax.network/apis/avalanchego/apis/health

Backup And Restore

How to check avalanchego logs?

tail .avalanchego/logs/main.log

How to check the subnet successfully deployed?

if the logs file contain these lines:

[04-17|15:50:45.332] INFO server/server.go:269 adding route {"url": "/ext/bc/22v7AG7h6qaVxd4bLvAsSsg2LZ4RCn5iVYgFn7a2Fj1LCuYwjv", "endpoint": "/rpc"} [04-17|15:50:45.332] INFO server/server.go:269 adding route {"url": "/ext/bc/22v7AG7h6qaVxd4bLvAsSsg2LZ4RCn5iVYgFn7a2Fj1LCuYwjv", "endpoint": "/ws"}

If you place the subnet-evm in wrong directory or wrong file name, what happens?

You will find this line:

ERROR node/node.go:849 failed to register VM {"vmID": "X5tFvg9JwoXgaYPQbceSzhGoCF6dhwrDm5BnAav6meFp3xxmg", "error": "handshake failed: vm process not found"}

how to get node information?

curl -X POST --data '{ "jsonrpc":"2.0", "id" :1, "method" :"info.getNodeID" }' -H 'content-type:application/json;' 127.0.0.1:9650/ext/info

sample output:

{ "jsonrpc": "2.0", "result": { "nodeID": "NodeID-5mb46qkSBj81k9g9e4VFjGGSbaaSLFRzD", "nodePOP": { "publicKey": "0x8f95423f7142d00a48e1014a3de8d28907d420dc33b3052a6dee03a3f2941a393c2351e354704ca66a3fc29870282e15", "proofOfPossession": "0x86a3ab4c45cfe31cae34c1d06f212434ac71b1be6cfe046c80c162e057...." } }, "id": 1 }

Make sure your node healthy:

curl -X POST --data '{ "jsonrpc":"2.0", "id" :1, "method" :"health.health" }' -H 'content-type:application/json;' 127.0.0.1:9650/ext/health

Your should see the words "healthy": true in the response object.

We Are Game Developers

DOS Alliance - Game Studios & Production

Largest Game Developer Community in Asia

Our Core Team

You can also find the feature roadmap and share your suggestion at:

DOScan.io

Our self-hosted explorer doscan.io offers a suite of powerful tools designed to help you track transactions, analyze DOS usage statistics, and access detailed information about validators.

• Search using address, transaction hash, or block ID

• Delve into detailed transaction information

• Access, verify, and interact with smart contract source codes

A Beam Testnet Explorer is also available: .

Snowtrace.io

Access the Snowtrace Explorer for DOS at , which offers tools for enhanced blockchain interaction:

• View transactions, statistics, and validator details

• Search using an address, transaction hash, or block ID

• Explore details about ERC20, ERC721, and ERC1155 tokens

• Delve into detailed transaction information

DOS Chain: The Future of AI-Powered Web3 Gaming

DOS Chain is more than just a gaming blockchain—it’s a scalable, AI-driven Web3 ecosystem that empowers gamers, developers, and content creators to shape the future of gaming. As a dedicated Avalanche subnet, DOS Chain delivers gasless transactions, sub-second finality, and AI-enhanced security, ensuring seamless Web3 integration for both players and developers.

DOS Chain operates as an independent gaming-focused Layer-1 blockchain while benefiting from the speed, security, and interoperability of Avalanche’s infrastructure. This enables a high-performance, low-latency gaming experience without sacrificing decentralization or accessibility.

NFT Marketplace - OverMint

Built-in Wallet - DOSafe

A blockchain validator is someone who is responsible for verifying transactions on a blockchain. Once transactions are verified, they are added to the distributed ledger. In proof of stake (PoS) systems like DOS Chain, our validators are given as long as they correctly participate in the network. This mechanism helps secure the network by imposing the need to lock up value in the network in order to participate in the consensus decisions.

Validators will form the backbone of our DOS network. Each validator processing transactions and participating in consensus will enable DOS to become the most secure and safe network in the world.

A Subnet requires validators that secure both the Subnet, and the primary network (X,P, and C chain). It is up to the node operator to ensure the optimal health of the node.

Hardware requirements and bandwidth:

Overview

OverMint is DOS's designated marketplace for buying, selling, and discovering unique gaming Non-Fungible Tokens (NFTs). It serves gamers and enthusiasts eager to exchange in-game assets from their favorite titles, including weapons, characters, cosmetics, accounts, and certificates of ownership. Designed with a seamless user experience, OverMint emphasizes its assets, enabling users to acquire their desired items swiftly.

Explore DOS's native marketplace at .

Overview

DOSafe is a white-label solution that offers full control over the developer experience, allowing you to own the npm package a developer installs.

• Efficient User Management: Acts as a gatekeeper ensuring only authorized users gain access.

• Effortless Wallet Setup: Users can create, fund, and use wallets easily.

• Universal Compatibility

Supports browsers, mobile platforms, and Unity for seamless development.

Features

Get Started

Explore these popular guides to begin.

• Integrate an Ecosystem Wallet with Wagmi: Learn how to integrate an ecosystem wallet seamlessly using Wagmi.

• Wallet Connectors: Utilize an ecosystem wallet with popular wallet connectors to enhance your user experience.

• Set Up Your DOSafe Wallet: Follow this step-by-step guide to create your own wallet.

This document serves as a starting point for new users to the DOS Chain ecosystem. General knowledge of cryptocurrency is assumed, and in particular familiarity with the Ethereum or Avalanche ecosystem. If you don't understand something right away, that's OK. Search for an answer online, and if you don't find it, ask on our .

Architecture

DOS Chain utilizes the L1s technology of Avalanche. Before you start developing DApps on the DOS Chain, it is important to learn about its underlying architecture.

An Avalanche L1 is a sovereign network which defines its own rules regarding its membership and token economics. It is composed of a dynamic subset of Avalanche validators working together to achieve consensus on the state of one or more blockchains. Each blockchain is validated by exactly one Avalanche L1, while an Avalanche L1 can validate many blockchains.

DOS ERC-20 Tokens

Mainnet

• Network Name: DOS Chain

• RPC URL:

LayerZero Addresses

DOS Testnet

• chainId: 10162

• endpoint: 0x45841dd1ca50265Da7614fC43A361e526c0e6160

DOS Mainnet

• chainId: 149

• Endpoint: 0x9740FF91F1985D8d2B71494aE1A2f723bb3Ed9E4

Bridging tokens from and to DOS is powered by the . To learn more about it and how to use it in your own project, visit our guide.

LayerZero Bridge Guide

FAQ

Why DOSafe SDK

Developing a user-friendly wallet poses a major challenge. To address this, we've introduced the DOSafe SDK—a toolkit that streamlines the creation, management, and customization of wallet systems. Ideal for games, marketplaces, or social platforms, DOSafe SDK supports

Explore the live demo of our ecosystem wallet!

Why we build this

Developing a smart wallet system from scratch is a complex challenge. Key tasks include:

• Infrastructure Preparation: Set up for transaction sponsorship and bundling.

• Signer Implementation: Incorporate signers to manage ownership.

• Smart Contract Selection: Choose appropriate smart contracts for accounts.

• Authentication Setup: Establish secure authentication processes.

Choosing a third-party provider to manage your system can be a practical decision. However, it is essential for the provider to offer flexibility, allowing adjustments to meet your specific needs and reduce the risk of vendor lock-in. Additionally, prioritize a smooth developer experience to avoid wasting time on implementing complex interactions, like a wallet system.

What's in the box?

Here's the cool stuff you get with the DOSafe SDK:

• Universal Compatibility: Our solution supports development across browsers, mobile platforms, and Unity.

• Effortless Wallet Setup: Users can swiftly create, fund, and start using their wallets.

• Efficient User Management: Acts as a gatekeeper, ensuring only authorized users gain access.

How it all fits together

The DOSafe SDK is structured like a well-organized kitchen featuring three main stations:

1. Developer Integration Layer: Where you set up your integration

2. Client-Wallet Communication: The service window where orders (transactions) are handled

3. Blockchain Interaction: Where the magic occurs blockchainGetting started

DOSafe SDK Architecture

The DOSafe SDK is organized into three main components, each serving a specific purpose, similar to distinct stations in a well-organized kitchen:

1. Developer Integration Layer: This is where you configure your integration, setting up the necessary components for seamless functionality.

2. Client-Wallet Communication: This acts as the service window where transactions are initiated and processed.

3. Blockchain Interaction: This is the core area where blockchain magic happens, managing the intricate operations of

The main ingredients

Custom Wallet SDK Integration

This serves as the main coordinator for your application, managing everything from designing a custom wallet SDK to overseeing pop-ups and transactions. The best part? It operates directly within your app's front end and can be customized with your brand's colors. It also includes built-in security features and integrates seamlessly with

Communication Module

Meet your dedicated maître d', designed to facilitate seamless interactions between clients and their wallets. It assists newcomers with setting up non-custodial wallets and operates smoothly in any browser environment. For more detailed information, please refer to our comprehensive

Framework Prefabs

Similar to ready-to-use recipe cards, our framework prefabs include special helpers for various frameworks, featuring an excellent setup for React. All components are customizable to suit your style.

"But why not just use embedded wallets?"

The Embedded Wallet setup

Imagine this: each app requires a unique setup—installing packages, generating keys in iframes, managing authentication... And then, how do you make it discoverable across different applications?

The Not-So-Fun parts of embedded wallets

1. Authentication gets messy

   • Every app needs its own bouncer (authentication system)

   • OAuth2 providers get confused when trying to share wallet access

   • There's no good way to keep track of who's logged in where

Why the Ecosystem SDK is better

What you get:

• One login system that works everywhere (no more authentication headaches!)

• Control all permissions from one place

• A slick dashboard with your brand to onboard projects

• Paymasters and smart accounts by default

DOS’s tokenomics are designed at the frontier of economic blockchain and gaming research, aiming to deliver an economic ecosystem and financial plumbing at par with DOS’s innovative engineering design.

This page includes a high-level overview of DOS’s economic model.

DOS Token

DOS Chain’s native asset is called DOS and we generally use one-word "DOS" to distinguish the token from the DOS Chain platform.

The total supply of DOS tokens is capped at 1,000,000,000 (i.e. one billion tokens). A share of DOS’s total supply will be liquid at mainnet launch, with the remaining tokens vesting over the coming years or distributed as future stake reward subsidies. Each DOS token is divisible up to a large number of decimal places.

The DOS token serves four purposes on the DOS Chain:

• You can stake DOS to participate in the proof-of-stake mechanism.

• While whitelisted games and DApps are gasless, a small amount of DOS is still required as the gas fee to execute and store transactions on the DOS Chain.

• DOS can be used as a versatile and liquid asset for various applications including the standard features of money – a unit of account, a medium of exchange, or a store of value – and more complex functionality enabled by smart contracts, interoperability, and composability across the DOS ecosystem.

Since the DOS token is available in finite supply, the same amount of tokens will need to be used across more economic activities in the long run if DOS Chain unlocks many use cases and millions of users migrate to the platform.

Token Distribution

Introduction

This article describes how to run a Mainnet node on DOS Chain. The following necessary steps are needed to run your node on the DOS Chain:

1. Install AvalancheGo using the Install Script

2. Download the plugin binary for the DOS Subnet-EVM

3. Track the DOS Subnet

4. Connect to the DOS Subnet!

This install script assumes:

• AvalancheGo is not running and not already installed as a service

• User running the script has superuser privileges (can run sudo)

Official documents from Avalanche:

Install AvalancheGo using the Install Script

First, you need to download and install AvalancheGo (handles the orchestration of running Custom VMs). You can follow to complete this step. For this tutorial, we recommend using the AvalancheGo Installer.

Notes: Some configurations you should notice:

• Enter your connection type [1,2]: 2

• RPC port should be public (this is a public API node) or private (this is a validator)? [public, private]: private

• Detected 'x.x.x.x' as your public IP. Is this correct? [y,n]: y

Notes:

• Your node should now be bootstrapping. Node configuration file is /home/DOS/.avalanchego/configs/node.json

• C-Chain configuration file is /home/DOS/.avalanchego/configs/chains/C/config.json

• Plugin directory, for storing subnet VM binaries, is /home/DOS/.avalanchego/plugins

• To check that the service is running use the following command (q to exit): sudo systemctl status avalanchego

Get the ID, the BLS key, and the proof of possession(BLS signature) of this node

• nodeID Node ID is the unique identifier of the node that you set to act as a validator on the Primary Network.

• nodePOP is this node's BLS key and proof of possession. Nodes must register a BLS key to act as a validator on the Primary Network. Your node's POP is logged on startup and is accessible over this endpoint.

  • publicKey is the 48 byte hex representation of the BLS key.

To get these info:

Install Avalanche CLI

Run a Subnet Node

Option1: Build Subnet Binaries

After building AvalancheGo successfully,

1. Clone

2. Build the Binary and Save as a Plugin

In the Subnet-EVM directory, run the build script, and save it in the “plugins” folder of your .avalanchego data directory. Name the plugin after the VMID of the Subnet you wish to track. The VMID of the DOS Chain is the value beginning with “X5tF...”.

Option 2: Download subnet-evm Binary

For the steps below, we will assume that you completed first step successfully and are now in your AvalancheGo directory (within your $GOPATH).

Next, you will download the DOS-EVM binary (please notice that we use the same Binary file with the Ava Labs repo):

Download and unzip the latest subnet evm at:

The long string X5tFvg9JwoXgaYPQbceSzhGoCF6dhwrDm5BnAav6meFp3xxmg is the CB58 encoded VMID of the DOS Subnet-EVM. AvalancheGo will use the name of this file to determine what VMs are available to run from the plugins directory.

Tracking DOS Chain and Restarting the Node

Joining DOS Subnet

For a node to join a Subnet, there are two prerequisites:

• Primary Network validation

• Subnet tracking

Primary Network validation means that a node cannot join a Subnet as a validator before becoming a validator on the Primary Network itself. So, after you add the node to the validator set on the Primary Network, node can join a Subnet.

To have a node start syncing the Subnet, you need to add the --track-subnets command line option, or track-subnets key to the node config file (found at .avalanchego/configs/node.json for installer-script created nodes). A single node can sync multiple Subnets, so you can add them as a comma-separated list of Subnet IDs.

An example of a node config syncing two Subnets:

But that is not all. Besides tracking the SubnetID, the node also needs to have the plugin that contains the VM instance the blockchain in the Subnet will run.

If you want to inspect the process of Subnet syncing, you can use the RPC call to check for the blockchain status.

Example Call:

Example Response:

Running the Node

First, make sure to shut down your node in case it is still running. Then, you will navigate back into the AvalancheGo directory:

If you went through the steps to set up a config file, then you can launch your node by specifying the config file on the command line:

If you want to track the Subnets through the command-line flag. You can append the other flags or even the --config-file flag as well, according to your need.

Import DOS Chain Subnet

You firstly import DOS Chain using subnet import public since DOS Chain is already live.

To see the Subnet Config:

avalanche subnet describe "DOS Chain"

Config Chain

DOS Chain allows the node operator to provide some custom configurations. The config file for DOS Chain is located at ~/.avalanchego/configs/chains/22v7AG7h6qaVxd4bLvAsSsg2LZ4RCn5iVYgFn7a2Fj1LCuYwjv/config.json

The content of config.json file should be like:

{ "feeRecipient": "0x50B65C1e3206621b6f9A5Ab2950Ae69f20634b82",//input your wallet }

Just Want the Commands? We Got You

And finally, share us your nodeID.

Run Another Node

You can reduce the node boostraping time by copying the database.

Database Copy

Good way to cut down on bootstrap times on multiple nodes is database copy. Database is identical across nodes, and as such can safely be copied from one node to another. Just make sure to that the node is not running during the copy process, as that can result in a corrupted database. Database copy procedure is explained in detail .

Please make sure you don't reuse any node's NodeID by accident, especially don't restore another node's ID, see for details. Each node must has its own unique NodeID, otherwise, the nodes sharing the same ID will not behave correctly, which will impact your validator's uptime, thus staking rewards, and the stability of your Subnet.

The DOSwap SDK provides a straightforward method to create your own ecosystem wallet. It offers a code-splitting environment and essential tools to bring your wallet SDK to life, making the process both easy and efficient.

Video