Glossary

Updated on 2024-05-10 GMT+08:00

View PDF

This section describes common terms used in NES to help you better understand and use NES.

**Table 1** Glossary
Term	Sub-item	Description
BSC	Mainnet	An EVM-compatible, Proof of Staked Authority (PoSA) mainnet, with shorter block time and lower fees.
BSC	Chapel	As a replica of mainnet, Chapel allows you to develop, test, and deploy your DApps.
Ethereum	Mainnet	It uses Proof-of-Stake (PoS). Mainnet coins have monetary value, incur gas fees, and are recorded on distributed ledgers.
	Sepolia	Sepolia has fewer deployed applications as compared to Goerli. It has a smaller state and history, allowing for faster syncing and requiring minimal disk space to run a node. The validator set is restricted, so not everyone can run a validator node. Ethereum.org recommends Sepolia as the primary choice for testing applications and smart contracts due to its restricted validator set and higher stability guarantees.
	Holesky	The first-ever Ethereum testnet launched on the top of the PoS consensus, serving as a staking, infrastructure, and protocol-developer testnet.
TRON	Mainnet	A primary TRON blockchain network. Transactions on this network have real value.
TRON	Nile	It is used to test new features of TRON, and the code version is generally ahead of the mainnet.
Polygon PoS	Mainnet	The Proof-of-Stake (PoS) mechanism and compatibility with EVMs make mainnet the preferred choice for fast transactions and low costs.
Polygon PoS	Mumbai	As a replica of mainnet, Mumbai allows you to develop, test, and deploy your DApps.
Arbitrum	One	An L2 optimistic rollup chain that implements the Arbitrum Rollup protocol and settles to Ethereum's L1 chain. It supports EVMs and lets you efficiently perform transactions at low cost.
Arbitrum	Goerli	A testnet chain that replicates the features of the Arbitrum One mainnet. It is tethered to the Goerli testnet of Ethereum, providing a secure testing ground for developers to experiment with.

Previous topic: Restrictions

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot