# Information on the Non-Cryptocurrency Public Chains

A Non-Cryptocurrency Public Chain is a transformed public chain framework based on an existing public chain. Gas Credit transfers are not permitted between standard wallets. There are no cryptocurrency incentives for mining or participating in consensus. On Spartan Network, there are three Non-Cryptocurrency Public Chains at launch. We expect to add more in the foreseeable future.

## Spartan-I Chain (Powered by NC Ethereum)

### About Spartan-I Chain (Powered by NC Ethereum)

The Spartan-I Chain is a blockchain compatible with Ethereum that runs independently from the public Ethereum blockchain. Full Nodes, which can freely join and exit the Spartan Network, synchronize block information of the entire chain and submit transaction requests to the network.

A Spartan-I full node runs an EVM (Ethereum Virtual Machine) that allows developers to use Solidity programming language to create smart contracts that are compatible with the Ethereum network. Also, all the different tools and wallets available for Ethereum (such as Truffle, HardHat, Metamask, etc…) can be directly used with Spartan-I Chain.

Ethereum-based networks have two identifiers, a network ID and a chain ID. Although they often have the same value, they have different uses. Peer-to-peer communication between nodes uses the network ID, while the transaction signature process uses the chain ID.

Spartan-I Chain Network Id = Chain Id = 9090

> [!Tip|style:flat]

> - For detailed installation documentation, please refer to GitHub.

### Ethereum and Geth Documentation

Below is a list of useful online documentation about Ethereum and Geth.

How to set up Geth and execute some basic tasks using the command line tools.

https://geth.ethereum.org/docs/getting-started

JSON-RPC API methods Interacting with Geth requires sending requests to specific JSON-RPC API methods. Geth supports all standard JSON-RPC API endpoints. You can send RPC requests on the port 8545.

https://geth.ethereum.org/docs/rpc/server

Developer Documentation

This documentation is designed to help users build with Ethereum. It covers Ethereum as a concept, explains the Ethereum tech stack, and documents advanced topics for more complex applications and use cases.

https://ethereum.org/en/developers/docs/

Smart Contract tutorials

A list of curated Ethereum tutorials to learn about coding smart contracts and DApps.

https://ethereum.org/en/developers/tutorials/

Solidity Lang

https://docs.soliditylang.org/

Web3j Document

https://docs.web3j.io/

Web3.js

https://web3js.readthedocs.io/en/v1.7.5/

## Spartan-II Chain (Powered by NC Cosmos)

### About Spartan-II Chain (Powered by NC Cosmos)

The Spartan-II Chain is a Cosmos-based network which has two identifiers, a network ID and a chain ID. Although they often have the same value, they have different uses. Peer-to-peer communication between nodes uses the network ID, while the transaction signature process uses the chain ID.

EVM module: Network ID = Chain ID = 9003

Native module: Network ID = Chain Id = starmint

> [!Tip|style:flat]

> - For detailed installation instructions, please refer to GitHub.

### Resources

To find out more about Spartan-II Chain (Powered by NC Cosmos), visit GitHub.

API Introduction

https://github.com/BSN-Spartan/NC-Cosmos/tree/main/docs/endpoints

CLI Client Commands

https://github.com/BSN-Spartan/NC-Cosmos/tree/main/docs/cli-client

Solidity Lang

https://docs.soliditylang.org/

Web3j Document

https://docs.web3j.io/

Spartan-II Chain GoLang SDK

https://github.com/BSN-Spartan/nc-cosmos-sdk-go

## Spartan-III Chain (Powered by NC PolygonEdge)

### About Spartan-III Chain (Powered by NC PolygonEdge)

The Spartan-III Chain (Powered by NC PolygonEdge) network has two identifiers, a network ID and a chain ID. Although they often have the same value, they have different uses. Peer-to-peer communication between nodes uses the network ID, while the transaction signature process uses the chain ID.

Spartan-III Chain Network Id = Chain Id = 5566

> [!Tip|style:flat]

> - For detailed installation instructions, please refer to GitHub.

### Resources

JSON-RPC Commands

NC PolygonEdge is compatible with ETH JSON RPC interface, please refer to the detailed interface list from below link.

https://docs.polygon.technology/docs/edge/get-started/json-rpc-commands

CLI Commands

NC PolygonEdge provides a wealth of CLI commands for managing your nodes. For a detailed command list, please refer to the link below.

https://docs.polygon.technology/docs/edge/get-started/cli-commands

Prometheus Metrics

PolygonEdge can report and serve the Prometheus metrics, which in their turn can be consumed using Prometheus collector(s). The following is a detailed description reference.

https://docs.polygon.technology/docs/edge/configuration/prometheus-metrics

Backup/Restore Node Instance

This guide goes into detail on how to back up and restore a PolygonEdge node instance. It covers the base folders and what they contain, as well as which files are critical for performing a successful backup and restore.

For detailed operation, please refer to the link below.

https://docs.polygon.technology/docs/edge/working-with-node/backup-restore

Polygon Edge API

https://docs.polygon.technology/docs/edge/get-started/json-rpc-commands

How to Use Smart Contracts

https://docs.polygon.technology/docs/category/smart-contracts

Solidity Lang

https://docs.soliditylang.org/

Web3j Document

https://docs.web3j.io/

Web3.js

https://web3js.readthedocs.io/en/v1.7.5/

# results matching ""

# No results matching ""

# results matching ""

# No results matching ""