
<p>Even though the first blockchain protocol (Bitcoin) came to life over 12 years ago, adoption has moved very slowly on all fronts &#8211; this largely has to do with a lack of understanding in the subject and poor Web3 tools for developers. As such, blockchain development was time-consuming and overly complex. With the birth of Relysia, the definitive blockchain as a service provider, development and adoption are accelerating on the Bitcoin SV blockchain.</p>



<p>This blog article will take a closer look at the tech stack that we use for all development projects at the <a href="https://www.vaionex.com/">Vaionex Corporation</a> and Product Applications.&nbsp;</p>



<p>By reading this guide, you’ll get an excellent overview of all layers involved in blockchain development. Plus, you’ll learn about many incredible tools that are waiting to be utilised by you. Another vital layer of the stack is Relysia, the cutting-edge blockchain development platform. The careful consideration given to the Relysia endpoints and architecture saves time and resources, allowing you to invest more resources in other aspects of your business. Thus, make sure to <a href="https://relysia.com">create your account today</a>. But enough about Relysia for now; let’s rather focus on the broader view of the Web3 tech stack.&nbsp;&nbsp;&nbsp;</p>



<p><strong>Web3 Tech Stack &#8211; An Overview</strong></p>


<div class="wp-block-image">
<figure class="aligncenter size-full is-resized"><img loading="lazy" src="https://cms.vaionex.com/relysia/wp-content/uploads/2022/06/Web3TechStackBlog-1.jpg" alt="" class="wp-image-50" width="575" height="411"/></figure></div>


<p>Before we take a closer look at each level of the Web3 tech stack, it’s important to have a clear picture in mind.</p>



<p>The BSV blockchain is at the lowest level of the Web3 tech stack and that Web3 applications are at the top. In between, we have APIs and platforms. As mentioned, we will take a closer look at each of these levels of the Web3 stack.</p>



<p>It should be quite clear that users care the most about the top layer since this is the finished product that they use &#8211; so it is important to consider each part of the blockchain development stack carefully if you want to build cutting-edge blockchain apps.</p>



<p>Your Web3 tech stack should be designed in such a way that focuses your attention on the frontend/platform level. This will help you to reduce waste of precious time on creating your own backend to manage UTXOs and user keys. Luckily there are many useful tools that help you to ship your product faster and offer users a superior experience.</p>



<p><strong>Web3 Tech Stack Layer One &#8211; Blockchain</strong></p>



<p>Blockchain technology is the first Web3 tech stack layer. Without the Bitcoin protocol there is no Web3 development. Henceforth, we place this as the foundation for our stack. In recent years, Ethereum has been the leader in development activity and user numbers. </p>



<p>However, the poor network architecture inevitably leads to high transaction fees and malicious exploits. In the future there can only be one blockchain protocol that the world uses for a transparent record of ownership and exchange.</p>



<p>The Bitcoin SV blockchain is, as Dr. Craig Wright often says, just plumbing. How often does the average homeowner tinker around with their pipes?&nbsp;Most likely never, right?&nbsp;</p>



<p>There are many services that allow you to use the blockchain and access data that include: WhatsOnChain, BlockChair and others. It is important to note that people mistakenly refer to these “listener” services as Nodes, but by definition in the Bitcoin whitepaper, Nodes process transactions by mining blocks.</p>



<p><strong>Web3 Tech Stack Layer Two &#8211; APIs</strong></p>



<p>An Application Programming Interface, API for short, is a set of functions and protocols for building applications, or blockchain applications. The interoperability offered, allows for a piece of software to interact with other pieces of software. It is also worth noting for developers, that a proper set of APIs contribute to an easy and stable coding experience.&nbsp;</p>



<p>APIs and SDKs are very popular in the Web3 development stack due to the high complexity and costs of building your own blockchain backend that will not fail your users. All blockchain as a service providers offer documentation for their APIs. The Relysia <a href="https://docs.relysia.com/">documentation</a>, for example, covers our broad suite of endpoints and includes in depth explanations in code editors and videos. You can also learn more about how Relysia works in practice at Satolearn.com.</p>



<p><strong>Relysia’ SDK</strong></p>



<p>The Relysia SDK offers over 60 endpoints, with examples including: /createWallet, /invoice, /upload, /getTransaction, /balance, /issue(NFT), /getAddress, /history, /metrics, etc. There are many more APIs in our suite that simplify blockchain development. </p>



<p><strong>Web3 Tech Stack Layer Three &#8211; Platforms</strong></p>



<p>You may be familiar with many legacy development platforms such as Firebase, Azure, and Amazon Web Service (AWS). But when it comes to Blockchain Development, Relysia is the tool for all of your needs.&nbsp;</p>



<p>Without a BaaS provider, you need to manage and maintain your own backend if you want to use APIs. Normally software engineers would have to build functionality that includes: UTXO management, authentication, NFT minting, etc.&nbsp;</p>



<h5><strong>Relysia’s Main Features</strong></h5>



<p>Some of the powerful capabilities that Relysia provides include:</p>



<ul><li>Web2 and Web3 Authentication.</li><li>P2P Smart Contracts.</li><li>Blockchain Database for Files, Transactions and Web Hosting.&nbsp;</li><li>STAS Tokens &amp; NFTs</li><li>UTXO Management</li><li>Invoice Payments</li></ul>



<p>As you can see, Relysia is a platform that essentially gives you an end-to-end blockchain development experience. You have all the tools to take your idea from concept to application. Do you already have an idea? Use Relysia to fuel your development! </p>



<p>All you need to do is create your free Relysia account. With an account, you’ll be able to see your auth token and service ID. From there, you can call any of the API endpoints, and much more. If you combine the simplicity of Relysia with a boilerplate frontend from a marketplace such as Envato Themeforest, you can build a stunning blockchain application in days.</p>



<h5><strong>Fourth Web3 Tech Stack Layer &#8211; Applications</strong></h5>



<p>At last, we reach the most layer that your users are most interested in &#8211; Web3 applications. This is generally the stage of development that separates the best from the rest. You can get creative and build an amazing UI that offers an advanced user experience. Some notable CSS frameworks for frontend development include: TailWindUI, Bootstrap, Material UI and more. CSS frameworks are really useful because they provide a consistent set of style parameters that you can add via css classes.</p>



<p>We advise developers to use a JavaScript framework such as: Next.JS or React.JS. These frameworks have become increasingly popular among frontend developers and engineers and they are also compatible with our Relysia APIs and SDK.</p>



<h3><strong>Web3 Tech Stack for Blockchain Development – Summary</strong></h3>



<p>At this point, you are all caught up and know that the Web3 tech stack consists of five layers:</p>



<ul><li>Bitcoin SV Blockchain</li><li>APIs and API providers</li><li>Development platforms</li><li>Decentralised applications</li></ul>



<p>You have also learned the basics of each component of the Tech Stack for web development and you now know to focus on APIs and platforms for all of your blockchain backend functionality. If you made it this far through the blog, then you have probably created a free Relysia account and you are ready to start building with the only development platform that can service all of your Web3 needs.</p>



<p>With Relysia on your side, its neat documentation and consistent developer support you have all the tools to bring your blockchain idea into reality. Moving forward, we recommend you read our API documentation and test our endpoints in SwaggerUI.However, in case you are not yet JavaScript-proficient, make sure to enrol in the final project in the “Wallet Workshop” course. This will give you a chance to learn to build real world blockchain apps using JavaScript. By enrolling at <a href="https://satolearn.com">Satolearn</a>, you’ll also access some of the best lecturers and coders in the industry.</p>


The Ultimate Web3 Tech Stack – Full Guide


<p>Non-custodial wallets rely on the user to store their mnemonics. While often overseen, that step is essential to maintain your user funds long term since systems are programmed defensively to rather loose funds access then to loose user funds.</p>



<h2>What are mnemonics</h2>



<p>Mnemonics are a 12 word seed phrase that resolve your HD Privatekey. From that HD Privatekey, we can derive more than a billion private keys that each generate you a different address (for privacy purposes.</p>



<h2>How do we keep track of paths</h2>



<p>Since we have so many paths, how do we keep track of them? We do it with a peer to peer payment architecture, where each payment gets added to a UTXO array that involves the path descriptor. As long as we have the mnemonic, path and utxo we can always trigger a transaction (often from many paths and privatekeys at the same time).</p>



<h2>How is that better than classical transactions</h2>



<p>With the peer to peer model, we dont need to scan the whole blockchain for each wallet address (that can be tens of thousands that need to be checked against each transaction going through the chain). Instead we keep the data communication direct between sender and receiver (via paymail). Since we still support classical transactions for the foreseeable future, we are actually scanning the whole blockchain for transactions, but definitely will have trade offs in terms of speed and cost for our own infrastructure.</p>


Wallet Mnemonics and Path


<h2>Blockchain Infrastructure</h2>



<p>Similar to early home computer adoption, the general use of a technology is often hidden till a critical threshold of adoption is reached. For those adoptions, catalysts such an Apple 2 are required that significantly reduce the difficulty of joining the space, with the necessary robustness and user friendliness to keep the interest and adoption sustainable. Within the blockchain ecosystem, we see similar tendencies: Cryptocurrencies are nowadays mostly seen as speculative assets or potentially fintech solutions, but rarely as database alike core infrastructure, even though the widespread commitment to the Ethereum Enterprise Alliance would suggest otherwise. The first step of the equation is a blockchain protocol that facilitates competitive mining prices, which we see in Bitcoin SV. The second step is, to reduce the low transaction fees that represent friction of any adoption and reduce it to effectively 0 as part of our infrastructure offering. The combination allows us to offer GCloud or AWS alike competitive SAAS offerings, but moreover a seamless blockchain technology adoption of a broader market.</p>



<h2>Where do we go from here?</h2>



<p>The release of Relysia is for us only a first step in the creation of a broad number of SAAS services. It is the heart infrastructure of our internal applications, such as MetaShard, Satolearn, Apiandme, Raspora &amp; co and moreover integral part of our client consulting offerings. The efficiency created by reusing a single infrastructure allows us to offer ultra-competitive market offerings, but also create internal incentives to keep the Relysia wallet infrastructure at the highest standards at all times. We see a increasing complexity of regulatory compliance and transaction handling on the horizon. We made it thus our mission to offer developers and clients of the ecosystem a professional and rounded infrastructure product that can be integrated at low cost. In the following month we will make plenty of announcement related to KYC, Compliance and Token solutions in our continued effort to create best in space blockchain solutions.</p>


Why Infrastructure Matters


<h2>Non-Custodial</h2>



<p>A standard requirement for wallets to not become money transmitters is to let purely the owner of the keys compose and transact transactions. While a good implementation significantly reduces the chance of attacker based fund losses, it also increases the chance of user losing funds (due to password or mnemonic key losses). Even though the reputation of non-custodial wallets is to be limited in functionality, most functionalities can be replicated even dissolving the concept.</p>


<div class="wp-block-image">
<figure class="aligncenter size-full is-resized"><img loading="lazy" src="https://cms.vaionex.com/relysia/wp-content/uploads/2022/06/ezgif.com-gif-maker2.jpg" alt="" class="wp-image-18" width="524" height="375"/></figure></div>


<h2>What does non-custodial actually mean</h2>



<p>While the definition states that the users need to be in full control of their funds and in extended version, wallet service providers shall not be fiduciaries of the money, the definition is still wide open. While some wallet providers such as MoneyButton encrypt their Mnemonics with a password (which requires the user to never forget their password, the equivalent is the <strong><em>Relysia Secure Wallet</em></strong>), others go with &#8220;keyless solutions&#8221;, where the key is fragmented in multiple parts (owned by various providers, equivalent is the <strong><em>Relysia Standard Wallet</em></strong>). The question in both solutions is rather to which degree it is impossible to intrude the users security, but certainly none of the solutions provide any bullet proof security. The question then is, do we define as non-custodial an application based on effort it would take to take custody? (cracking a short password or hacking the client side application/internal structure). One may argue above named steps are basic server security requirements (that face the same dilemma), not specific blockchain or crypto based standard measures. It likely comes rather down to the base operational practices of a wallet infrastructure whether they access keys without permission or not.</p>



<h2>Smart Non-Custodial</h2>



<p>Even without a non-user triggered key usage, there is a wide variety of p2p inspired methods to make full usage of our newly discovered &#8220;programmable&#8221; money. Transaction bundles can be composed, but not submitted (equivalent to writing a cheque), and thus be used in auctioning mechanisms. Other methods including bitcoin script based atomic swaps to exchange goods (another pre-composed bundle, just in different shape), that are especially attractive in combination with tokenization contracts. We think that different types of non-custodial wallets with different security standards are best suited to offer each client group the best service for their needs. While some users prefer the ease of use, and password reset functionalities of standard wallets, others prefer the higher degree of security with password protected or even multi signature based wallets.</p>



<p>The debate on methods related to creating non-custodian wallets will likely fade over time in the background of blockchain adoption, as regulations are not fine grained enough to create clear definitions. We thus take the user experience first, and let everyone pick the combination of utility and security they require for their individual applications.</p>


Non-Custodial: Security & Utility


<h2>Core Properties of Blockchains</h2>



<p>While it seems that there is a sheer amount of different blockchain protocols with different advantages, a closer inspection reveals that most of them fall into specific groups of economic incentive and scalability properties that make them unremarkably similar.</p>



<h2>Game Theoretical Incentive</h2>



<p>For the long term maintenance and functioning of a decentralized system, it is the incentive, not the narrative, that protects the system from collapse or takeover. Incentive system means, that when every player of the system acts in their own self interest, the system stays sustainable.</p>



<p>While that is obvious, few blockchains actually care about long term incentives and rather aim for short term gains or popularity of narrative.</p>



<p>Miners and infrastructure providers need to be incentivized to create better value to their costumers (the blockchain users) by scaling the network and lowering the fees of the network. Users, such as blockchain application developers need to have the guarantee of immutability, stability of the protocol and low transaction costs to ensure that they themselves can offer a valuable solution to their end costumers.</p>



<p>When end costumers are satisfied by the additional benefits of the blockchain, usage increases, and transaction through put demand rises. If they then combined pay more fees to the miners, the miners get incentivized to invest more into their infrastructure to provide a faster network at lower network costs.</p>



<p>If on the other hand miners don&#8217;t get incentivized to improve the user experience, and only compete against each other &#8211; may it be with proof of work hashpower of proof of stake investment, the network has no intrinsic property to grow towards a global infrastructure.</p>



<h2>Why Bitcoin SV</h2>



<p>Bitcoin SV has a simple but battle proven incentive system. Blocks are not limited by protocol developers, but purely by miners that orient their own infrastructure investment (to increase server capacities and network throughput) based on reward expectations (which is the transactions * fee). If some miners process too big blogs for others to process, other miners will orphan those blocks and keep mining their own perceived honest branch.</p>



<p>Users on the other hand can expect a decrease in fees and a constant increase in maximum transaction capabilities (based on moores law) and thus rely on the Bitcoin SV protocol as a long term infrastructure solution. It may sound simple, but its those simple insights that are often over seen but painfully critical once developing a system of scale. One cannot build a world spanning global network without getting the basics right, and at closer look very few seem to focus on real world adoption.</p>
