I first learned about Gno.land from a friend. Gnoland adopts a new language called Gnolang, which is a fork of Golang. Golang has clear advantages over other languages ​​when dealing with concurrency. While most programming languages ​​like C++ or Java use multithreading to run concurrent programs, Go uses Goroutines.

Multithreading is running multiple threads in parallel in a single process. This could be your browser playing music and running a search engine at the same time, or your word processor displaying your input while checking grammar. The problem with multithreading is that it requires context switching, where the operating system scheduler manages switching between processes and threads.

This often results in overhead and consumes excessive resources. Goroutines, on the other hand, take the burden off the operating system by implementing a runtime local scheduler, the Go Scheduler. The creation and destruction of goroutines seems to consume less memory (as low as 0.2% of threads) and fully utilize all cores of the hardware.

Gnoland provides the most feasible solution for this, which is to integrate goroutines by supporting Golang as a smart contract language. The most commonly used languages ​​in the current blockchain development environment are Solidity for EVM-compatible networks and Rust for Solana and Cosmos SDK networks; both Solidity and Rust are inspired by C++.

While the above are excellent languages, Gnolang inherits Golang's faster compilation speed, cleaner syntax, and resource-efficient concurrency.

The initial model for the Cosmos Hub involved a fee token called PHOTONs, which limited the use of ATOM to governance and staking. At launch, the concept of a fee token was deprecated, and today ATOM can be used as both a governance/staking token and a fee token. Not only Cosmos, but most layer 1s in the blockchain space like Ethereum, Avalanche, and Solana run a single-token model.

Gnoland, on the other hand, is looking to adopt a dual-token model similar to the original idea of ​​Cosmos, where "fee utility" is stripped from the governance token.

As Jae Kwon suggested, a two-token model using a fee token with a fixed constant inflation rate (rather than indexing like a staking token) would have the following advantages over a single-token model:

Most end-users are technically ignorant, which means that most of them don’t know which validators they should support and how to evaluate governance proposals. In short, the dual-token model mitigates operational risk by shifting governance responsibility from end users to nodes, validators, and network stakeholders who have a practical understanding of the blockchain.

The purpose of governance tokens is to stake them on the network for the security of the blockchain. The irony of the single-token model is that the more traction a blockchain gains, the more likely it is to earn more tokens as gas fees, which can lead to a decrease in the security of the network. Having a dual token model solves this problem.

A fixed-inflation-fee token specifically designed to power blockchain contracts will allow users to keep tokens in wallets for future use without fear of inflating their value.