Advantages
Why GEMNODE
Easy to join
GEMNODE offers a robust environment for Dapps on top of a secure EVM-compatible structure with built-in RPC, allowing crypto enthusiasts to fully explore the chain by simply adding its RPC to a crypto wallet.
Regarding network validation, any Avalanche validators can easily validate GEMNODE with their ready resources to earn GEM in return. It should take less than an hour to configure a full-node, please refer to the section for Validator in our docs.
It would be even easier for developers to join GEMNODE space since its coding language is similar to most EVM chains, includes the full Ethereum toolchain. Traditional developers can just integrate GEMNODE SDK and interact on GEMNODE Client Interface to generate Blockchain components for traditional Web 2.0 applications and games.
Non-coding
The ultimate target of GEMNODE is to establish a complete non-coding framework for traditional applications to join Blockchain and set up their own tokenomics. The first landscape will be traditional web-based applications and games.
By approaching GEMNODE SDK, traditional developers can reduce DevOps workload efficiently and time spent on launching contract, deploying server, API, etc. as an out-of-the-box solution.
Efficient Consensus
Aforementioned in GEMNODE introduction, the very first version of GEMNODE will facilitate the Snowball Consensus of Avalanche with sharding solutions that generates quick finality alongside great throughput.
Once GEMNODE DAO established, GEMNODE community will be able to vote for network upgrades, incudes the next version of consensus and even a major mainnet hard fork from Avalanche.
Measuring Time
GEMNODE does not use the same mechanism to measure time as Ethereum which uses consistent block times. Instead, GEMNODE supports asynchronous block issuance, block production targets a rate of every 2 seconds.
If there is sufficient demand, a block can be produced earlier. If there is no demand, a block will not be produced until there are transactions for the network to process.
Hence, developers should not measure the passage of time by the number of blocks that are produced. The results will not be accurate.
Instead of checking block rate, developers should measure time simply by reading the timestamp attribute of the produced blocks. Timestamps are guaranteed to be monotonically increasing and to be within 30 seconds of the real time.
Great Finality
On Ethereum, the blockchain can be reorganized and blocks can be orphaned, so developers cannot rely on the fact that a block has been accepted until it is several blocks further from the tip (usually, it is presumed that blocks 6 places deep are safe).
That is inapplicable on GEMNODE. Blocks are either accepted or rejected within a second or two.
Once the block has been accepted, it is final, and cannot be replaced, dropped, or modified. So the concept of 'number of confirmations' on Avalanche is not used. As soon as a block is accepted and available in the explorer, it is final.
Secure
GEMNODE's first started as an Avalanche subnet. This move enables GEMNODE network to be literally backed by the developed infrastructure of Avalanche since every GEMNODE node is an Avalanche node. Hence, the chain is considered more secure in comparison to building on its several nodes at first.
The Avalanche infrastructure is highly tolerated to 51% attacks, single point of failure (SPOF), and network congestion due to gas fluctuation without compromising decentralization.
Last updated