The Blockchain Infrastructure
Zebro Smart Chain is ethereum based layer2 blockchain with Ethash fixed supply Proof of Work [PoW] consesus and Go client 'GoZebro'.
The goal of Zebro Smart Chain (ZSC) is to bring programmability and interoperability to Project Zebrocoin. In order to embrace the existing popular community and advanced technology, it will bring huge benefits by staying compatible with all the existing smart contracts on Ethereum and Ethereum tooling. And to achieve that, the easiest solution is to develop based on go-ethereum fork, as we respect the great work of Ethereum very much.
Zebro Smart Chain (ZSC) starts its development based on go-ethereum fork. So you may see many toolings, binaries and also docs are based on Ethereum ones, such as the name “gozebro”.
'gozebro' is cmd go client to run Zebro Smart Chain from shell like go-etherem with 'geth'
Proof-of-Work(PoW) increases the decentralization and favors community governance.
Zebrocoin ZEBRO total/maximum supply is capped by 10 Billion ZEBRO, 5 Billion out of 10 Billion ZEBROs will be locked forever to bridge-contracts to bridging ZEBRO to other 5 chains BSC, Polygon, Fantom, Phoenix and EtherGem blockchain.
All 10 Billion ZEBROs are allocated to Zebrocoin owner in genesis block to prevent inflation in maximum/circulation supply, miners can join network and mine for transaction fee.
Zebro Smart Chain PoW consesus benefits:
Blocks are produced by any miner node to mine transaction fee.
Miner nodes can use Ethereum's Ethhash consensus engine to mine blocks.
All miner nodes are validators which gives Zebro Smart Chain 100% decentralized concept.
Transaction fee will be changed according to market price to encourage ZEBRO miners.
Ethash Proof-of-Work(PoW) consensus engine will interact as an original Etherem PoW concept.
To achieve the cross-chain communication from Zebro Chain to Zebro Smart Chain, need introduce a on-chain light client verification algorithm. It contains two parts:
1. Stateless Precompiled contracts to do tendermint header verification and Merkle Proof verification.
2. Stateful solidity contracts to trusted appHash.
Zebrocoin ZEBRO will run on Zebro Smart Chain in the same way as ETH runs on Ethereum so that it remains as native token for ZSC. This means, ZEBRO will be used to:
1. pay gas to deploy or invoke Smart Contract on ZSC
2. perform cross-chain operations, such as transfer token assets across Zebro Smart Chain.
Linux x64h: https://zebrocoin.info/downloads/gozebro/linux/gozebro_linux_64.tar.gz
Windows x64: https://zebrocoin.info/downloads/gozebro/linux/gozebro_win_64.tar.gz
git clone https://github.com/ZebroTech/ZSC.git
The hardware must meet certain requirements to run a full node.
VPS running recent versions of Mac OS X or Linux.
50GB of SSD storage for mainnet, 5G of SSD storage for testnet.
8 cores of CPU and 32 gigabytes of memory (RAM) for mainnet.
4 cores of CPU and 8 gigabytes of memory (RAM) for testnet.
A broadband Internet connection with upload/download speeds of at least 10 megabyte per second
As an alternative to passing the numerous flags to the `gozebro` binary, you can also pass a configuration file via:
$ gozebro --config /path/to/your_config.toml
To gozebro an idea how the file should look like you can use the `dumpconfig` subcommand to
export your existing configuration:
$ gozebro --your-favourite-flags dumpconfig
As a developer, sooner rather than later you'll want to start interacting with gozebro and the Zebro Smart Chain network via your own programs and not manually through the console. To aid this, gozebro has built-in support for a JSON-RPC based APIs (standard APIs and gozebro specific APIs). These can be exposed via HTTP, WebSockets and IPC (UNIX sockets on UNIX based platforms, and named pipes on Windows).
The IPC interface is enabled by default and exposes all the APIs supported by gozebro, whereas the HTTP and WS interfaces need to manually be enabled and only expose a subset of APIs due to security reasons. These can be turned on/off and configured as you'd expect.
HTTP based JSON-RPC API options:
--http Enable the HTTP-RPC server
--http.addr HTTP-RPC server listening interface (default: localhost)
--http.port HTTP-RPC server listening port (default: 8545)
--http.api API's offered over the HTTP-RPC interface (default: eth,net,web3)
--http.corsdomain Comma separated list of domains from which to accept cross origin requests (browser enforced)
--ws Enable the WS-RPC server
--ws.addr WS-RPC server listening interface (default: localhost)
--ws.port WS-RPC server listening port (default: 8546)
--ws.api API's offered over the WS-RPC interface (default: eth,net,web3)
--ws.origins Origins from which to accept websockets requests
--ipcdisable Disable the IPC-RPC server
--ipcapi API's offered over the IPC-RPC interface (default: admin,debug,eth,miner,net,personal,txpool,web3)
--ipcpath Filename for IPC socket/pipe within the datadir (explicit paths escape it)
You'll need to use your own programming environments' capabilities (libraries, tools, etc) to connect via HTTP, WS or IPC to a gozebro node configured with the above flags and you'll need to speak JSON-RPC on all transports. You can reuse the same connection for multiple requests!
Note: Please understand the security implications of opening up an HTTP/WS based transport before doing so! Hackers on the internet are actively trying to subvert BSC nodes with exposed APIs! Further, all browser tabs can access locally running web servers, so malicious web pages could try to subvert locally available APIs!
Zebro Smart Chain can be added to any EVM chain supported hardware/software wallets, some famous ones as following.
Zebro Smart Chain can be added to any EVM chain supported hardware/software wallets by entering following details. Chian details can also found here ChainList.Org
The zsc library (i.e. all code outside of the cmd directory) is licensed under the MIT General Public License.
The zsc binaries (i.e. all code inside of the cmd directory) is licensed under the GNU General Public License v3.0, also included in our repository in the COPYING file.