Skip to content

geneticsequencing/Exzo-Network-Blockchain

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

20 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Exzo Network

Chain Specs

  • Native Token Name - EXZO
  • Symbol - XZO
  • Supply - 50 Million
  • Blocktime - ~400ms
  • Consensus - DelegatedProof-of-Stake (PoS)
  • P2P Port -
  • JSON-RPC Port - 8899
  • ChainID Mainnet - 1229
  • ChainID Testnet - 2370
  • Ethereum Virtual Machine (EVM) Compatible

Official Links

About the Exzo Network

  • Exzo Network uses a modular architecture and provides Ethereum compatibility.
  • Users able to interact with industry standard wallets through JSON-RPC.
  • Develop with Solidity/Vyper, full EVM support.
  • Build using widely-adopted Ethereum tooling, libraries and development tools.
  • Streamlined UX when doing cross-chain operations.
  • Go beyond Ethereum’s Smart Contracts with Runtime plugins.

The Exzo Network Token (XZO) features the following utilities, and the value of XZO token will accrue with the increased usage of the network and revenue from stability fees and liquidation penalties.

  • As Network Utility Token: to pay for network fees and stability fees.
  • As Governance Token: to vote for/against risk parameters and network change proposals.
  • As Economic Capital: in case of liquidation without sufficient collaterals.
  • As fee reducing token on decentralized applications and wallets upon the Exzo Network.
  • For staking to help secure the Exzo Network in a decentralized fashion.

Cross-Chain Communication

  • Completely trustless and decentralized built-in Ethereum Bridge solution.
  • Transfer assets to and from any EVM compatible network, most notably Exzo Network and Ethereum mainnets.
  • Transfer ERC-20 tokens, NFTs or wrapped native currencies.
  • Customize the bridge functionality using Bridge plugins.

Building

1. Install rustc, cargo and rustfmt.

$ curl https://sh.rustup.rs -sSf | sh
$ source $HOME/.cargo/env
$ rustup component add rustfmt

Please sure you are always using the latest stable rust version by running:

$ rustup update

On Linux systems you may need to install libssl-dev, pkg-config, zlib1g-dev, etc. On Ubuntu:

$ sudo apt-get update
$ sudo apt-get install libssl-dev libudev-dev pkg-config zlib1g-dev llvm clang make cmake protobuf-compiler

On Mac M1s, make sure you set up your terminal & homebrew to use Rosetta. You can install it with:

$ softwareupdate --install-rosetta

2. Download the source code.

$ git clone https://github.com/ExzoNetwork/exzocoin.git
$ cd exzocoin

3. Build.

$ cargo build

4. Run a minimal local cluster.

$ ./run.sh

Testing

Run the test suite:

$ cargo test --no-fail-fast

EVM integration

Info about EVM integration is at our docs.

Starting a local testnet

Start your own Development network locally, instructions are in the online docs.

Accessing the remote testnet and mainnet

  • testnet - public accessible via bootstrap.rpc-test-1.exzo.network.
  • mainnet - public accessible via bootstrap.exzo.technology.

Benchmarking

First install the nightly build of rustc. cargo bench requires use of the unstable features only available in the nightly build.

$ rustup install nightly

Run the benchmarks:

$ cargo +nightly bench

Release Process

The release process for this project is described here.

Copyright


Copyright 2022-2023 Exzo Network

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.