The use of this site and the content contained therein is governed by the Terms of Use. When you use this site you acknowledge that you have read the Terms of Use and that you accept and will be bound by the terms hereof and such terms as may be modified from time to time.
All text, graphics, audio, design and other works on the site are the copyrighted works of nasscom unless otherwise indicated. All rights reserved.
Content on the site is for personal use only and may be downloaded provided the material is kept intact and there is no violation of the copyrights, trademarks, and other proprietary rights. Any alteration of the material or use of the material contained in the site for any other purpose is a violation of the copyright of nasscom and / or its affiliates or associates or of its third-party information providers. This material cannot be copied, reproduced, republished, uploaded, posted, transmitted or distributed in any way for non-personal use without obtaining the prior permission from nasscom.
The nasscom Members login is for the reference of only registered nasscom Member Companies.
nasscom reserves the right to modify the terms of use of any service without any liability. nasscom reserves the right to take all measures necessary to prevent access to any service or termination of service if the terms of use are not complied with or are contravened or there is any violation of copyright, trademark or other proprietary right.
From time to time nasscom may supplement these terms of use with additional terms pertaining to specific content (additional terms). Such additional terms are hereby incorporated by reference into these Terms of Use.
Disclaimer
The Company information provided on the nasscom web site is as per data collected by companies. nasscom is not liable on the authenticity of such data.
nasscom has exercised due diligence in checking the correctness and authenticity of the information contained in the site, but nasscom or any of its affiliates or associates or employees shall not be in any way responsible for any loss or damage that may arise to any person from any inadvertent error in the information contained in this site. The information from or through this site is provided "as is" and all warranties express or implied of any kind, regarding any matter pertaining to any service or channel, including without limitation the implied warranties of merchantability, fitness for a particular purpose, and non-infringement are disclaimed. nasscom and its affiliates and associates shall not be liable, at any time, for any failure of performance, error, omission, interruption, deletion, defect, delay in operation or transmission, computer virus, communications line failure, theft or destruction or unauthorised access to, alteration of, or use of information contained on the site. No representations, warranties or guarantees whatsoever are made as to the accuracy, adequacy, reliability, completeness, suitability or applicability of the information to a particular situation.
nasscom or its affiliates or associates or its employees do not provide any judgments or warranty in respect of the authenticity or correctness of the content of other services or sites to which links are provided. A link to another service or site is not an endorsement of any products or services on such site or the site.
The content provided is for information purposes alone and does not substitute for specific advice whether investment, legal, taxation or otherwise. nasscom disclaims all liability for damages caused by use of content on the site.
All responsibility and liability for any damages caused by downloading of any data is disclaimed.
nasscom reserves the right to modify, suspend / cancel, or discontinue any or all sections, or service at any time without notice.
For any grievances under the Information Technology Act 2000, please get in touch with Grievance Officer, Mr. Anirban Mandal at data-query@nasscom.in.
AppChains continues to gain traction as more web3 developers realize the ease of managing their large projects on a dedicated single purpose blockchain over using a shared public chain. If your dApp too demands a dedicated blockchain, you have two ways to go unless you want to fork any specific blockchain:
Use solutions like Subnets & Supernets and leverage their underlying L1’s security
Use popular frameworks like Cosmos or Substrate to build from scratch and still benefit from the ecosystem.
Regardless of which approach you opt for, this guide presents a step-by-step AppChain development process to simplify your experience.
Who should use Application-specific blockchain?
Application specific blockchains are ideal for large decentralized applications, where resource consumption may be high. For example, if your application is projected to manage about 100K daily active users, then building an AppChain is definitely the right decision.
With AppChains, you can have your own gas token, earn a gas fee, and introduce more flexibility in the token utility over time. Further, you ensure consistent performance with high TPS and ultra-low gas fees. If you choose to launch your application-specific blockchain on any main chain, then you can leverage its liquidity, bridges, and overall security.
How to launch your own custom blockchain
This guide explains the process of launching a custom blockchain, which includes multiple phases like deciding the build approach, requirement gathering, infrastructure customization, testnet launch, production-level deployment, and finally monitoring.
Let’s go through all these steps one-by-one and understand them thoroughly, concluding how an enterprise can create a custom blockchain that can power their dApp(s).
Deciding a build approach
The first step is to brainstorm how you want to build your application specific blockchain. As we discussed earlier, you can leverage the existing chains like Avalanche Subnet and Polygon Supernets, or else, you have the option to design an ecosystem from scratch using frameworks like Substrate and Cosmos. Analysis for this can be done on parameters such as your blockchain’s desired architecture, token model, scalability (TPS), validator requirements and smart contract specifications.
Once this is done, we can move on to the next step.
Finalize Blockchain-level Specification:
In this step, we have to decide on the key specifications of your blockchain based on the purpose it’s desired to serve.
Tokenomics
As a sovereign network, AppChain can build its own unique custom tokenomics with native tokens, validator incentives, and fee market as per the use case.
Consensus mechanism
Consensus mechanism in a blockchain network defines the parameters for how transactions will be validated, recorded, and added further to the chain. Proof-of-stake, Proof-of-work, delegated proof-of-stake, and Proof of Authority are some popular consensus you can consider implementing in your AppChain.
Validator nodes
Setup a certain number of validators (depending on the project) to bootstrap your AppChain network and allow it to validate the transactions on the network. With ecosystem expansion, the network must allow more validators to participate in the consensus and help AppChain to ensure security.
Permissioned/permissionless
With respect to dApp’s technicalities, you can choose to open your AppChain ecosystem for all participations or limit it to specific participants. For an in-depth analysis of what you should choose— permissionless or permissioned, you should talk to blockchain consultants and make the right decision.
Incentive parameters
AppChains are accountable for rewarding the validators in return for the block they verify and produce. You can decide a logical incentive rate by taking inspiration from prominent blockchains. For example, if we look into the Subnets, it has set a minimum delegation fee of 2% while the reward is proportionate to their stake + delegators’ stake, provided that validators maintain a minimum uptime of at least 80%. Again, you have the freedom to customize these incentive parameters fully.
Infrastructure customization
Below are key considerations for infrastructure customization; however, you can add customization as per the mother chain you choose.
Creating the genesis file
The Genesis file is integral as it defines the initial state of your application specific blockchain. By finalizing the parameters on the genesis file, you ensure that all the essential elements on your AppChain will be added to function seamlessly. Following are the specifications you can include:
> Network and chain ID
Using the Genesis file, you can generate a Chain ID and network ID. These are the two important identifiers that share the same value, but they offer different uses. Network ID enables communication among the nodes, while Chain ID ensures that transactions are sent to the correct network.
> Fee configuration
Fee config in the genesis file may include the gas Gas limit, base fee, minimum limit of block gas cost, maximum limit of block gas cost, increment and decrement of gas cost based on the fast and slow rate of block produced by the mother chain.
Security Implications
Security is undoubtedly critical for your AppChain, which requires you to configure security parameters such as restricting who can deploy smart contracts, who can submit the transactions, activating native token minting, configuring dynamic fees, modifying the fee reward mechanism, etc. There’s a detailed guide on how AppChains can ensure unparalleled security.
Architecturing the AppChain Blueprint
Considering all the infrastructure customization requirements, security considerations, and integrations you decided on in the previous stages, you must create a blueprint for your AppChain. This approach will include the creation of wireframes and prototypes and the mapping of the user experience and interface. The blueprint provides you with an overview of how your AppChain will look like, its functionalities, and integrations. At this stage, you can include or exclude the specifications if you wish.
Setting up the nodes
All types of nodes— RPC nodes and dedicated nodes are an integral part of your Application specific blockchain as they serves various purposes including:
RPC nodes allow AppChain dApp to interact with various blockchains and get relevant data. Likewise, full nodes store blockchain data and pass the valid data to further nodes. On the other hand, validator nodes allow the participation of nodes for the authentication of transactions and blocks on any AppChain network.
Be aware that running a blockchain node comes with challenges, such as specialized hardware, reliable infrastructure, technical knowledge, computing resources, and huge storage capacity. You can better connect with a node-as-a-service provider to eliminate all these barriers. Apart from nodes, you can consider integrating APIs on your AppChain if you want people to access your network and its data.
Making the necessary Integrations
Your AppChains will function exactly like a blockchain. However, it manages a single application. That means your AppChain should include integration of wallets (hardware or software), faucets, and blockchain explorers to serve the designated purpose. Make sure these custom integration must be finalized during the requirement-gathering phase and integrated before testnet launch.
Creating and launching the AppChain Testnet
The next step is to create a Test environment that allows you to test your blockchain and smart contract and the specifications outlined in the blueprint. You can verify that all the components of AppChain work as expected, if something went wrong, or what upgrades are needed.
Simply put, you will design your entire blockchain, including customized infrastructure, integration, and security implications. The only difference is that your AppChain will be live on a test environment instead of mainnet. As Testnet replicates mainnet, you need tokens (test tokens), nodes, faucets, wallets, and every other component to start your AppChain network. Hence, gather all the resources, program your AppChain, and make the network live on the testnet.
Deploying the AppChain to the production environment
Launching the mainnet is the final step of launching your custom blockchain. Mainnet provides a production environment where the blockchain goes live with integrated functionalities, making it accessible across the web3 space. Note that for production-level deployment, you require a set of nodes and scalable infrastructure to manage the AppChain network. Once you set up the node setup and cross-check all the configurations, migrate the codebase from the testnet to the production environment and launch your AppChain.That’s done! Your AppChain is now officially live, and you can use it to manage your dApps and other use cases.
Monitoring your AppChain
After your AppChain is live, you must ensure reliable performance with the best monitoring and maintenance practices. This will maintain the sound health of the network and the interconnected nodes acting as peers. Blockchain monitoring should be done on vital parameters such as block statistics, network uptime, memory usage, disk space utilization, potential downtime in performance, and all activity logs for a reliable and to maintain robust, risk-free operations.
About The Author
Dr. Ravi Chamria is co-founder CEO of Zeeve Inc, an Enterprise Blockchain company. He has an experience of 18+ years in IT consulting spanning across Fintech, InsureTech, Supply Chain and eCommerce. He is an executive MBA from IIM, Lucknow and a prolific speaker on emerging technologies like Blockchain, IoT and AI/ML.
Passionate About: Blockchain, Supply Chain Management, Digital Lending, Digital Payments, AI/ML, IoT
That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.
Zeeve is an enterprise-grade Blockchain Infrastructure Automation Platform. Join the growing list of clients that trust us with their Blockchain initiatives
The evolution of decentralized distributed ledger technology may be attributed to bitcoin, but in all honesty, Ethereum became the true harbinger of the said revolution. When bitcoin at its core still remains a distributed ledger, a platform to…
Businesses, to stay competitive, need to accelerate their digital transformation journeys and make the transition to industry 4.0. It would include achieving real-time convergence between physical and digital platforms and disrupting the market…
The Ethereum Merge is slated to the be the most significant event in the crypto space in 2022. The long-awaited upgrade from energy-guzzling Proof of Work (PoW) consensus to Proof of Stake (PoS) consensus algorithm is now very close to reality.…
Hyperledger is quickly becoming one of the most popular blockchain frameworks for large and medium-sized businesses. Its flexibility and strength, though, make it difficult to comprehend.
Before we dive into the blockchain frameworks, let’s…
Many people believe that blockchain seems to be exclusively about cryptocurrencies such As bitcoin, although the area of blockchain is considerably larger. Blockchain network, immutable, and transparent ledger. Here's some of each complicated term…
Hyperledger, Corda, and Ethereum are all blockchain platforms which are used for the creation and tracking of cryptocurrencies. Let’s take a moment to contrast Hyperledger, Corda, and Ethereum to see how they work. While different frameworks…
