<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: shivam1903</title>
    <description>The latest articles on DEV Community by shivam1903 (@shivam1903).</description>
    <link>https://dev.to/shivam1903</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1002989%2F3651aa3e-b772-4528-b24f-e0f7e369f99f.png</url>
      <title>DEV Community: shivam1903</title>
      <link>https://dev.to/shivam1903</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shivam1903"/>
    <language>en</language>
    <item>
      <title>Modular Blockchains and how are they an upgrade over regular blockchains</title>
      <dc:creator>shivam1903</dc:creator>
      <pubDate>Thu, 12 Jan 2023 19:15:00 +0000</pubDate>
      <link>https://dev.to/buildbear/modular-blockchains-and-how-are-they-an-upgrade-over-regular-blockchains-4o7n</link>
      <guid>https://dev.to/buildbear/modular-blockchains-and-how-are-they-an-upgrade-over-regular-blockchains-4o7n</guid>
      <description>&lt;p&gt;Before understanding Modular Blockchains, it is important for us to understand how blockchains (monolithic blockchains) work and its limitations. As the name ‘Blockchain’ suggests it is chain or series of blocks. Each block contains the block header and the transaction data linked to that header. "Full nodes" analyse and compute the entire block data to validate blocks to make sure transactions are valid.&lt;/p&gt;

&lt;p&gt;A blockchain functions in 4 layers, these are:&lt;/p&gt;

&lt;h3&gt;
  
  
  1) Data Availability
&lt;/h3&gt;

&lt;p&gt;On this layer, the information needed to confirm the validity of a state change should be presented. In the event of assaults where rogue block producers withhold transaction data, this should be simple to verify.&lt;/p&gt;

&lt;h3&gt;
  
  
  2) Execution
&lt;/h3&gt;

&lt;p&gt;Here is where transactions and state changes are first processed. Through this layer, users often communicate with the blockchain by executing smart contracts, signing transactions, and transferring assets.&lt;/p&gt;

&lt;h3&gt;
  
  
  3) Consensus
&lt;/h3&gt;

&lt;p&gt;Blockchains' consensus layer establishes order and finality through a network of complete nodes that download and process block contents and agree on the legitimacy of state transitions.&lt;/p&gt;

&lt;h3&gt;
  
  
  4) Settlement
&lt;/h3&gt;

&lt;p&gt;The verification of rollup execution and dispute resolution occur at the settlement layer. This layer is an optional component of the modular stack that does not exist in monolithic chains.&lt;/p&gt;

&lt;p&gt;In a monolithic blockchain all these functionalities are carried on a single layer, i.e. the base layer. Due to this there are several drawbacks in the monolithic chain such as delays due to re-executions of transactions, lower efficiency due to bandwidth and storage limitations, etc. The solution to most of these problems is in the Modular Blockchain.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is a Modular Blockchain?
&lt;/h2&gt;

&lt;p&gt;The system is divided into a number of separately designed pieces or additives by a modular chain. The execution layer in a modular blockchain structure is independent of the bottom consensus and data availability levels, allowing nodes to execute transactions on their own instead of performing them all to validate their validity in a single block or space. The most well-known instances of modular blockchain systems are the Cosmos, Fuel, and Celestia blockchains.&lt;/p&gt;

&lt;p&gt;In modular chains, three core layers work independently to make its output easier and quicker:&lt;/p&gt;

&lt;h3&gt;
  
  
  1) Consensus Layer
&lt;/h3&gt;

&lt;p&gt;The consensus layer lays forth the rules that nodes must follow in order to validate blocks and maintain a canonical blockchain state. This guarantees genuine security and decentralisation by ensuring that there is agreement among all of the nodes in the consensus network regarding the installed blocks and transactions.&lt;/p&gt;

&lt;h3&gt;
  
  
  2) Data Availability Layer
&lt;/h3&gt;

&lt;p&gt;The data availability layer manages the on-chain and stale-chain blockchain records, making sure that records are available and public for everybody to look at.&lt;/p&gt;

&lt;h3&gt;
  
  
  3) Execution Layer
&lt;/h3&gt;

&lt;p&gt;All transactions are carried out by the execution layer in order to produce high-quality records that are then stored on the blockchain network.&lt;/p&gt;

&lt;h2&gt;
  
  
  Benefits of a Modular Blockchain
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1) Scalability
&lt;/h3&gt;

&lt;p&gt;A monolithic blockchain enables a user to access all of the anticipated blockchain features in only one layer, known as "Layer-1." Because it seeks to handle all operations at once under a single layer, this makes blockchain generation difficult to do. A modular blockchain increases scalability and prevents potential network interruption by sharing the functions among several layers.&lt;/p&gt;

&lt;h3&gt;
  
  
  2) Blockchain Creation
&lt;/h3&gt;

&lt;p&gt;Miners must contend with a number of security and decentralization-related challenges to introduce a brand-new blockchain, which may also prohibit some from optimising the out-of-network hash rate. Regardless of the blockchain architecture, miners can take advantage of the layout and build new blockchains more quickly if they focus less on specific tasks like consensus.&lt;/p&gt;

&lt;h3&gt;
  
  
  3) Flexibility
&lt;/h3&gt;

&lt;p&gt;The modular blockchain layout is substantially more adaptable than the monolithic blockchain. It is made to give miners access to functionalities that aren't available in the monolithic blockchain. A few basic traits are shared by all cryptocurrency blockchains, such as guaranteeing data availability, security, consensus, and transaction execution. Blockchains often handle this type of operation at the same layer. Blockchains that are modular ensure greater efficiency by delegating work to other layers.&lt;/p&gt;

&lt;p&gt;Modular blockchains also have certain drawbacks including security. Even after such vulnerabilities modular blockchains are the future of blockchains. Since blockchain developers now recognise the requirement for a seamless and efficient transaction structure, monolithic chains like Ethereum and Solana are already moving toward a modular design.&lt;/p&gt;

&lt;p&gt;If you appreciate what we are doing, please follow us on &lt;a href="https://twitter.com/_BuildBear" rel="noopener noreferrer"&gt;Twitter&lt;/a&gt; and &lt;a href="https://t.me/+6mjOnBFUR9xjN2U1" rel="noopener noreferrer"&gt;Join the Telegram&lt;/a&gt; group if you haven’t done yet.&lt;/p&gt;

&lt;p&gt;And please give us a clap 👍 if you like our work and please do share this article.&lt;/p&gt;

&lt;p&gt;Thank you.&lt;/p&gt;

&lt;p&gt;Author:&lt;/p&gt;

&lt;p&gt;Shivam (&lt;a href="https://twitter.com/shivam___ag" rel="noopener noreferrer"&gt;Twitter&lt;/a&gt; || &lt;a href="https://www.linkedin.com/in/shivam---agrawal/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;), technical writer BuildBear.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;About BuildBear:&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;BuildBear is a platform for testing dApps at scale. It provides users with their own private testnet to test their smart contracts and dApps, which can be forked from any EVM chain. It also provides a Faucet, Explorer, and RPC for testing purposes.&lt;/p&gt;

&lt;p&gt;BuildBear aims to be building an ecosystem for testing dApps at scale for the entire team&lt;/p&gt;

</description>
      <category>career</category>
      <category>productivity</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Zero Knowledge and Identity</title>
      <dc:creator>shivam1903</dc:creator>
      <pubDate>Wed, 11 Jan 2023 12:43:58 +0000</pubDate>
      <link>https://dev.to/buildbear/zero-knowledge-and-identity-1j8n</link>
      <guid>https://dev.to/buildbear/zero-knowledge-and-identity-1j8n</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fnywau6b6cjgb5brhwxsi.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fnywau6b6cjgb5brhwxsi.png" alt="ZK and Identity" width="800" height="532"&gt;&lt;/a&gt;&lt;br&gt;
ZK is anticipated as one of the technologies that will undoubtedly change Web3. When it comes to ensuring the privacy, security and integrity of blockchain applications ZK looks quite promising.&lt;/p&gt;

&lt;p&gt;Trust is backbone of Blockchain and ZK would be helpful in securing user identity and data, so that they can authenticate themselves in a trustless world.&lt;/p&gt;

&lt;p&gt;In today’s world privacy is the main point of concern. An individual won’t want to reveal his complete identity to get a small job done, but at the same time the verifier also needs the information to confirm if the things are fine to proceed. The answer to this scenario is Zero Knowledge.&lt;/p&gt;

&lt;h2&gt;
  
  
  Understanding Zero Knowledge with an example
&lt;/h2&gt;

&lt;p&gt;The classic &lt;a href="https://en.wikipedia.org/wiki/Zero-knowledge_proof#The_Ali_Baba_cave" rel="noopener noreferrer"&gt;Ali Baba cave&lt;/a&gt; example gives deeper insights about the ZK concept. But for beginners it might be confusing and unclear to get started with understanding the concept of ZK. So let’s discuss another interesting example.&lt;/p&gt;

&lt;p&gt;When you visit to a club, at the entry you are asked to show a proof that you are 18+ in age. Normally you share your ID card which contains your photo, date of birth and other private details like your residential address or your work place details. It’s not desired that just to verify an individual’s age all other private details would also be revealed. Now what’s the solution to this ?&lt;/p&gt;

&lt;p&gt;The answer is ZK proofs. In the above scenario, the individual can generate a ZK proof that he/she is 18+ in age which can be stored as a claim. Now any organisation or individual who wants to verify the claim can do so easily without having a need to look at ID card and check the date of birth. It’s a win-win situation for both the parties as the prover don’t need to reveal his ID card and the verifier can verify is the prover is 18+ in age or not.&lt;/p&gt;

&lt;p&gt;Now, for the online world a user has his/her identity too. Many platform demands for the gmail authentication and unnecessary access to mails and other details. Same is the case with web3 platforms, once the user connects his wallet to the platform, indirectly his entire on-chain data is revealed to that platform via his blockchain wallet address.&lt;/p&gt;

&lt;h2&gt;
  
  
  Existing ZK and Identity Solutions and Tools
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Polygon ID
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ft6z8tsr5v4ntyzqjgqwq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ft6z8tsr5v4ntyzqjgqwq.png" alt="Polygon ID" width="800" height="400"&gt;&lt;/a&gt;&lt;br&gt;
&lt;a href="https://0xpolygonid.github.io/tutorials/" rel="noopener noreferrer"&gt;Polygon ID&lt;/a&gt; is the first ever to be powered by zero-knowledge (ZK) cryptography, a privacy and blockchain scaling technology. It provides Blockchain-based ID for decentralized and self-sovereign models backed by zero-knowledge native protocols for ultimate user privacy.&lt;/p&gt;

&lt;h3&gt;
  
  
  trinsic
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fstpb7cwcdq5ylvkflqqm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fstpb7cwcdq5ylvkflqqm.png" alt="trinsic" width="800" height="325"&gt;&lt;/a&gt;&lt;br&gt;
You can leverage ZK proofs using &lt;a href="https://studio.trinsic.id/SignUp" rel="noopener noreferrer"&gt;trinsic&lt;/a&gt; platform to build your end-to-end identity solution. Trinsic’s API makes it easy to build identity products that helps users manage their data and identity.&lt;/p&gt;

&lt;h3&gt;
  
  
  iden3
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fh0048eqj2hqxdt66wg1v.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fh0048eqj2hqxdt66wg1v.png" alt="iden3" width="280" height="280"&gt;&lt;/a&gt;&lt;br&gt;
&lt;a href="https://iden3.io/" rel="noopener noreferrer"&gt;iden3&lt;/a&gt; is a next-generation private access control based on self-sovereign identity, designed for decentralised and trust-minimised environments. The main idea of the iden3 protocol is that each identity is self-soverign and can issue claims on another identity. The iden3 protocol is based on &lt;a href="https://docs.circom.io/" rel="noopener noreferrer"&gt;Circom&lt;/a&gt; circuits which is the backbone of the protocol.&lt;/p&gt;

&lt;h3&gt;
  
  
  Semaphore
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Farpuat5nvg6df6dehjde.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Farpuat5nvg6df6dehjde.png" alt="Semaphore" width="800" height="400"&gt;&lt;/a&gt;&lt;br&gt;
&lt;a href="https://semaphore.appliedzkp.org/docs/introduction" rel="noopener noreferrer"&gt;Semaphore&lt;/a&gt; consists of a smart contract and zero-knowledge proof components which work in tandem. The on-chain proof verification and identity state is maintained and handled by smart contract. The zero-knowledge components work off-chain to create identities, manage groups and generate proofs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;The above discussion would have established a curiosity and a fundamental understanding of zero knowledge proofs and related tools and platforms built over it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Author:&lt;/strong&gt;&lt;br&gt;
Rishikesh Kale&lt;br&gt;
Find me on following socials, I would love to hear from you!&lt;/p&gt;

&lt;p&gt;LinkedIn : &lt;a href="https://www.linkedin.com/in/rishikeshkale" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/rishikeshkale&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Twitter : &lt;a href="https://twitter.com/0xrishikesh" rel="noopener noreferrer"&gt;Rishikesh Kale (@0xrishikesh) / Twitter&lt;/a&gt;&lt;/p&gt;

</description>
      <category>softwaredevelopment</category>
      <category>testing</category>
      <category>developers</category>
      <category>community</category>
    </item>
  </channel>
</rss>
