As a key member of the Chain Strategy team and the primary person behind the 2.0 upgrade, what were your responsibilities?

I manage and operate the Finschia mainnet, deciding features for releases, adjusting on-chain parameters, and planning Tx executions based on policy changes. We coordinate with off-chain and on-chain teams to implement technologies and policies outlined in the Finschia whitepaper. My role extends to writing and updating guides for developers, partners, and Finschia Governance Members (FGMs).

 

For the 2.0 upgrade, I organized the scope, policies, and processes, collaborated with departments and partners, and executed the upgrade process according to the schedule.

 

Any interesting episodes during the upgrade preparation?

This team-based project posed challenges in planning the upgrade timeline and process. Our Chain Strategy team dedicated effort to coordinating with all products, services, and exchanges connected to the Finschia main network. Personally, determining the target block height for the 2.0 upgrade was critical. We calculated it meticulously to avoid delays during the on-chain governance process, ensuring a seamless transition. The precision paid off, with the actual chain break only two minutes off the planned time.

 

What changes with the mainnet 2.0 upgrade?

The 2.0 upgrade signifies the technical and policy readiness of the Finschia mainnet to transition towards a public chain. Changes include allowing each validator to operate its public endpoint, enhancing accessibility for external developers to test and integrate services. A minimum gas price policy facilitates development by setting a threshold for charges. Additionally, Key Management Server (KMS) technology mitigates security risks by securely storing consensus keys on a separate server. On-chain governance is also strengthened by modifying the FoundationTax parameter and enabling CreateValidatorAuthorisation through on-chain governance.

 

What changes when an endpoint is released and becomes public?

Public endpoints empower anyone to develop and maintain dApps. Information in a block can be directly accessed using Query, enabling various uses. With Tx, developers can create and use contracts without restrictions, freely utilizing functions related to asset transfer (FNSA) and staking. Creating personal nodes and connecting them to public endpoints (P2P) ensures stable dApp services.

 

Finschia’s strategy to attract developers to the ecosystem?

“Stable mainnet operation” is a key advantage, with FGM-run validator nodes ensuring both technical security and business synergies. The FGMs, composed of companies, consider regulations, providing a competitive advantage.

 

Service contribution rewards transparently measure and reward contributions to the Finschia ecosystem’s activation and value. DApp developers can register as service contributors and receive FNSAs based on their contributions.

 

What skills do developers need for Finschia dApp development?

Developers need a basic knowledge of Go for Finschia node applications and Rust for smart contract development. For those with JavaScript skills, a JavaScript-based SDK, finschia-js, is available.

 

Advice for developers starting with Finschia dApp development?

Read Finschia Docs to understand node powering and communication. Follow the guide to connect a node or use Tx/Query. The Ebony testnet facilitates dApp development, supported by a basic smart contract development guide. Further details on contract development can be found in the Finschia repo, which is based on Cosmos SDK and Cosmwasm.

 

Is there a guide for dApp development?

A detailed smart contract development guide will be available later.

 

When can dApp developers start issuing tokens based on Finschia?

Issuing tokens requires technical and policy preparation. As smart contracts can be deployed on the Finschia mainnet, the technical preparation for issuing contract-based tokens is complete with the 2.0 upgrade. However, the standard for contract-based tokens has not yet been finalized on the Finschia mainnet, allowing dApp developers to issue tokens with the same specification and support them as standard tokens for distribution and use in multiple products or services. We are currently in discussions to finalize the contract-based token standard and expect to finalize the standard through consultation with the FGM and on-chain governance by the end of the year. At that point, dApp developers will be able to issue contract-based tokens based on the standard.

 

Any plans for the Mainnet 3.0 upgrade?

We’ve just completed the mainnet 2.0 upgrade and are now discussing the next 3.0 upgrade. Firstly, we are planning to update the major software (Finschia-sdk, Ostracon, Wasmd, ibc-go, etc) that technically make up the Finschia mainnet. We are also considering adding various features needed to extend the Finschia ecosystem in an environment where public endpoints are open. In addition, we want to focus more on building an environment where various dApps can be onboarded to the Finschia mainnet by providing dApp developers with more convenient and useful development tools and features. For your reference, public endpoints for the Ebony testnet will be supported from mid-November, and the Finschia endpoints will be followed at a later date.

 

Finschia’s vision of ‘Blockchain for All’ in the short term?

In order to eventually achieve Blockchain for All, I think Finschia needs to be popularized, although it is not easy to reach this stage in a short period. I think we will achieve this step by step, according to our long-term roadmap. We are taking steps to move from a private chain to a consortium chain and now to a public chain. Governance is currently a consortium system based on FGM, but we are also considering opening governance participation to general holders and strengthening the governance forum and developer community. Given the speed at which the Finschia ecosystem is expanding and going public, we believe that in the not-too-distant future, it will become a significant chain in the global market.

 

Direction for building a better Finschia as a chain strategist?

Finschia has always been based on the fundamental premise of conducting business and development in full compliance with regulations, so we have been somewhat limited in terms of overall progress and timing compared to other chains. However, since this year we have been steadily improving various structures, procedures, and awareness to address these areas. We are currently accelerating the steps towards becoming a public chain. Of course, our compliance with existing regulations is also a competitive advantage at a time when the blockchain market is becoming increasingly regulated. Therefore, I think it is necessary to maintain a good balance between the speed of progress and compliance.

 

Personally, when I think about the Finschia mainnet as a product, I believe it’s essential to listen to the voices and opinions (VOC) of our users and holders and reflect them in our development and policy direction. That’s why I want to focus on opening up more mainnet information and features to the outside world, interacting with our users and holders, and continuously improving our technology and policies.

 

Any final words?

As much as I personally love the Finschia mainnet, I would like to see it receive more attention and love from dApp developers, partners, and owners. For your reference, public endpoints for the Ebony testnet will be supported from mid-November, and the Finschia endpoints will be followed at a later date.

 

 

FNSA Overview