DEV Community: DappaDan

Mask On: A Code Journey into ID-Mask and Mina

DappaDan — Mon, 29 Jul 2024 14:55:03 +0000

Launching a mainnet is like that awkward moment when hosting a party.

You know the one.

At the start of the party when no one has come exactly on time you start to worry.

Are people fashionable late? Are they coming? Did I send the wrong date?

Of course, those worries go out the window once the first guest arrives.

In the case of the Mina Mainnet, ID-Mask is the first guest.

In this article, we will take a technical dive into ID-Mask and what it shows about the future of building ZKApps.

By the end of this article, you should feel inspired to start building your own ZKApps after realizing how accessible it is to develop on Mina.

So let's get this party started!

What is ID-Mask?

Proving your identity is something we do almost every day. Whether you're handing over a plastic ID card to get a nice beverage or a passport to enter a country. This requires us to carry these documents around and hand them over to people we may or may not trust.

Don't get me started on trying to port over my physical ids to the "digital world". The amount of times I have tried to take photos of my passport at the right angle for the OCR to work is countless.

ID-Mask aims to solve these problems. It's a service that allows users to generate Zero-Knowledge proofs to verify they are an adult, have no sanctions against them, and are a unique human. Users can now use the generated proof for identification purposes.

Goodbye plastic cards, hello ZK proofs!

How Does it Work?

Step 1: User Signature

Currently, the team has created an integration with a service called Smart-ID. This identification service lets users create digital, verifiable signatures through an application. The user's identification is stored on the Smart-ID platform, and any service integrating with it can create a signature request from the user.

These signatures can be used for a variety of different use cases. For example, when performing a large bank transaction, signing a contract, or approving new terms, integrating services can obtain data verification from the client side. This is because the user has approved the signature, confirming the data's validity.

ID-Mask uses this personal data as private inputs to respect the privacy of users:


methods: {
    proveUniqueHuman: {
      privateInputs: [
        PersonalData,
        Signature, // zkOracle data signature
        CircuitString, // unique secret value
        Signature, // signature of unique secret value
        Signature, // creator wallet signature
        PublicKey, // creator wallet public key
      ],

Step 2: Consuming the Data and Creating Proofs

After receiving personal data from Smart-ID, a proof needs to be generated for that information.

To prevent data tampering during this process, ID Mask uses an oracle connected to the Smart-ID data:

     const validSignature = oracleSignature.verify(
          PublicKey.fromBase58(
          'B62qmXFNvz2sfYZDuHaY5htPGkx1u2E2Hn3rWuDWkE11mxRmpijYzWN'
          ),
          personalData.toFields()
        );
        validSignature.assertTrue();

ID-Mask using the ZKProgram interface built into 'o1js' to create the proof. Here is an example for generating a proof of age:

export const proofOfAge = ZkProgram({
  name: 'ZkProofOfAge',
  publicInput: Field, // ageToProveInYears
  publicOutput: PublicOutput, // defined above
  methods: {
    proveAge: {
      privateInputs: [
        PersonalData,
        Signature, // zkOracle data signature
        Signature, // creator wallet signature
        PublicKey, // creator wallet public key
      ],
      async method(
        ageToProveInYears: Field,
        personalData: PersonalData,
        oracleSignature: Signature,
        creatorSignature: Signature,
        creatorPublicKey: PublicKey
      ): Promise<PublicOutput> {

Step 3: Using the Proof

Now that you have created the proof, the question is what to do with it.

In the case of ID Mask, the proof is attached to a Mina address. This gives the ability for the user to also prove their identity by proving they are the owner of the address. Anyone can then send a confirmation message to that address, allowing the user to prove their ownership:

     const validSignature_ = creatorSignature.verify(
          creatorPublicKey,
          personalData.toFields()
        );
        validSignature_.assertTrue();

Step 4: Verifying the Personal Data

To prove that the data meets a certain requirement, it needs to be processed. For example, to prove "Proof of Age," ID Mask extracts the date of birth from the personal identification number and compares it to the specified olderThanAgeToProve.

        const dateOfBirth = parseDateFromPNO(personalData.pno);       personalData.currentDate.greaterThan(dateOfBirth).assertTrue();
        // verify that (current date - age to prove) > date of birth
        const olderThanAgeToProve = personalData.currentDate
          .sub(ageToProveInYears.mul(Field(10000)))
          .greaterThan(dateOfBirth);
        olderThanAgeToProve.assertTrue();

If the age is higher than the age to prove, a proof is created. If not, sorry kid...time to grow up.

Step 5: Emitting the Event

The final step is to create a smart contract that handles putting the proof on chain. This shows a major benefit of using a network like Mina: other applications can also use this proof.

export class ProofOfAge extends SmartContract {
  events = {
    'provided-valid-proof': PublicOutput,
  };
  init() {
    super.init();
    // https://docs.minaprotocol.com/zkapps/o1js/permissions#types-of-permissions
    this.account.permissions.set({
      ...Permissions.default(),
    });
  }
  @method async verifyProof(proof: ProofOfAgeProof) {
    // if the proof is invalid, this will fail
    // its impossible to run past this without a valid proof
    proof.verify();
    // the above is enough to be able to check if an address has a proof
    // but there needs to be a way to save the number of years that are proved
    // emit an event with number of years to be able to query it via archive nodes
    this.emitEvent('provided-valid-proof', proof.publicOutput);
  }

The future of ID-Mask and ZKApps

The team at ID-Mask has some great ambitions to grow the use of this service. There is also a feature for storing these proofs in a mobile wallet like Apple or Google wallet. This brings this ability to more consumers who don't have a crypto wallet themselves.

Currently, Smart ID solution is limited to Baltic countries and Belgium. Other countries, such as Sweden and Switzerland, offer similar services, but they come with high costs. As the code is open source, more developers can start contributing to the expansion.

As consumer adoption grows for the use of ZK apps, so must the speed of proving. Especially if we are competing against systems that are more performant, even though they are less private. The team at Mina is aiming to make proving 8x faster soon.

If that is the case, I will leave you with one question, what are you going to build?

The Confused Developers Guide to Sidechains

DappaDan — Fri, 01 Mar 2024 19:10:28 +0000

Introduction

Have you noticed how many scaling solutions there are nowadays? There are several categories like L2s, modular blockchains, and sidechains. The growing number of choices within Layer 2 solutions, modular blockchains, and sidechains can make any level of developer feel overwhelmed.

Within each of those categories, there feels like an ever-growing list of options that is enough to make a developer's head spin.

It's easy to go for the solution with the largest hackathon prize (totally understandable), but when it comes to deploying a dApp in the real world, the decision is much harder.

Let's explore what makes sidechains a unique pick for developers, and how they compare with the rest of the pack. Following that, we're going deep into the Horizen EON EVM sidechain, highlighting the developer experience—what changes and what remains the same.

This will provide some clarity to confused developers. Let's get started:

Sidechains - A Story of Relationships

Blockchains are all about relationships. Relationships can be between addresses, contracts and even other blockchains. We see the relationships between addresses and contracts mostly when using blockchain explorers. A less visible type of relationship exists between different blockchains.

Why do blockchains need to create connections with other blockchains? Because life as a blockchain is hard. It is especially hard if you are a mainchain. You need to consider security (stopping attackers from hijacking the network), scalability (managing and settling all transactions), and decentralization (ensuring control is shared fairly among participants). Managing all three of these well is so important that it has been given its own name called "The Blockchain Trilemma".

To make life easier, a mainchain can recruit friends to help with this trilemma. Friends in this case can be supporting chains like sidechains.

Work alongside the mainchain, enabling assets to move back and forth through a two-way peg system.
Maintain independence in security and consensus, offering the flexibility to test various rules and scenarios for enhanced scalability.
Use the same computing system, like the Ethereum Virtual Machine (EVM), as the mainchain, so developers can work with familiar tools and languages that can coexist with the Ethereum ecosystem.

Layer 2s - The Other BFF

Scalability is so important that mainchains need multiple solutions to address it. Another option is Layer 2 blockchains (L2s). If sidechains are the friends of mainchain, L2s are the siblings. The key difference between L2s and sidechains is that L2s usually rely on the mainchain's security.

Their goal is to enhance scalability, utilizing optimistic rollups and zero-knowledge proofs for quicker transaction handling compared to the mainchain. These transactions still get settled on the mainchain eventually.

Sidechains on the Horizen

To help our understanding of sidechains, let's look at the Horizen EON EVM sidechain as an example. There are two main relationships in the Horizen ecosystem:

Horizen to EON

The first relationship is between Horizen and Horizen EON. Horizen acts as a 'blockchain of blockchains,' offering support for creating fully customizable sidechains optimized for speed, privacy, or consensus. It has its own native token called $ZEN and uses a Proof-of-Work consensus model. Created for particular applications, these sidechains communicate with the mainchain and achieve interoperability with one another through the Cross-Chain Transfer Protocol (CCTP).

EON, designed as an EVM-compatible sidechain, links the EVM with the Horizen network. It allows assets to be sent from Horizen to EON through forward transfers, and assets can be moved back to Horizen using backward transfers.

This means that they execute smart contracts like the EVM with little to no extra changes. From a developer perspective, this means that the same tools that would be used directly deploying a contract to the Ethereum network can still be used.

EON to Ethereum

For EVM compatibility, EON adopts Ethereum's account-based transaction system to handle assets. This system has two kinds of accounts: Externally-Owned Accounts (EOAs) and Contract Accounts.

Externally-Owned Accounts (EOAs) come with private keys, giving the owners the ability to carry out transactions with the assets stored in these accounts. Contract accounts don't have a private key. They are also required to run the code that is attached to the account.

Get Started Building

As we discovered before, a big plus of using an EVM-compatible sidechain is not being required to learn new tools and programming languages.You can use Remix IDE or Hardhat to test and deploy your smart contract. Although it is compatible, you still need to make small modifications to your configuration to access the Gobi testnet (Horizen EON´s testnet).

Thirdweb makes it simple to deploy smart contracts, allowing you to choose from its library or use your own contracts. After adding the Gobi Testnet to your wallet configuration, you can get TZEN, the testnet EON token, by using the Horizen Faucet. Then you can use one of the popular contracts from Thirdweb like NFT Drop or Token. Follow this developer guide to complete the deployment.

Wrapping Up

The variety of options for developers shows how important it is to scale mainchains. With so many options, this can be confusing. Sidechains offer the best of both worlds, giving developers flexibility to improve on what the mainchain misses and connecting back to it when needed.

The Horizen ecosystem puts Horizen EON in a perfect spot to give developers these benefits. Being a 'blockchain of blockchains' means it can host specialized sidechains while maintaining compatibility with the EVM whenever it's needed. The aim of this article was to help developers confused by all these solutions. The best way to stop being confused is to start deploying code on testnet and just experiment with the tools available. Become part of the Horizen community today!

Finally, the best way to truly understand the power of this technology is to start building on it. Check out the Horizen EON documentation to start deploying your first dApp!

Layers of a Blockchain: A Guided Tour

DappaDan — Fri, 11 Feb 2022 14:28:39 +0000

The journey of learning about blockchain has many twists and turns along the way but the path always includes a stop at the 'layers of a blockchain' station. Like ogres and onions, blockchains consist of layers that help enable the complex operations required to run smoothly and efficiently.

It is common to compare the layers of a Blockchain to the layers of the Internet Protocol suite(IP) to explain how they work. There are some great parallels between the two and since many hope blockchain technology will reinvent the world much like the internet did, the comparison makes sense.

If you have a good understanding of IP, this is of course an effective way to learn this concept. But if you are like most internet users who happily use the internet and don't care about how exactly HTTP is working in the background, this is not so great.

jeanayala.eth (🧱, 🚀)

@mrsalitre

I wish this but in the other hand people are not used to using the internet and do not know how it works. twitter.com/DAppaDanDev/st…

00:27 AM - 09 Feb 2022

DappaDan is writing (🧱,🚀) @dappadandev
There will probably be a time where it's not critical to understand how blockchain technology works like it's not critical to understand how 'the internet works'. But that time is not now so educate yourself anon!

For this tour of the layers of a blockchain, let's take something more familiar - a typical company - to explain the function of each layer in a blockchain. But first, what are these layers everyone is talking about and why do we have them?

What Are Layers?

A layer is a set of rules or protocols on how internal processes should be handled and how information on those processes should be shared with other layers externally.

To start our business analogy, a layer would be a specific team in the company. Each team has its own set of goals, its own set of tools to meet these goals, and a way to communicate with other teams about them. Although each team has a different focus area, they all aim to serve the business as a whole.

In the "blockchain company" the ultimate goal is to balance the decentralization, security, and scalability of the network. Each layer contributes to this goal in its unique way.

Why Have Layers?

Operating in a layered architecture provides the benefits of flexibility to be upgraded, interoperability, and the ability to be designed for and applied to multiple use cases.

Without layered system design, the internet would not be what it is today. We would be required to upgrade and use specific hardware and software to perform the common functions that we take for granted. Luckily one can access this article on the latest Macbook Pro or the long and forgotten closet PC.

As a business scales from the 'wear multiple hats' start-up stage to a larger organization, specialization of roles and teams naturally happens. When a blockchain needs to scale, a similar type of specialization is needed by creating separate but connected layers.

Like most things in the world of blockchain, the number of layers and naming is up for debate. For the sake of simplicity, let's look at the main three layers:

Source GetSmarter

Layer 1 - Protocol Layer - The Accounting/Legal Team

No, the sacred developer rule of starting with 0 has not been broken. Layer 0 is best described as the 'groundwork layer'. It is made up of physical components like the hardware and infrastructure to support Layer 1.

Layer 1, the protocol layer, is the base layer of any blockchain network. It supports the architecture as a whole and it is what proceeding layers are built on top of. This is where the familiar names such as Bitcoin and Etheruem 'live'.

In a business, Layer 1 would be the accounting and legal departments. It performs the slow but necessary work that requires due diligence and attention to detail. The main functions of layer 1 are:

Preventing "double-spend" - using a centralized or decentralized ledger to ensure that the same money promised to one party is not also promised or sent to another.
Building Consensus - using popular algorithms like proof of stake (PoS) or proof of work (PoW) to ensure all participating nodes agreed on the present state of the ledger.
Verification of Information - like the financial reviews of an accounting department, Layer 1 also acts as the source of truth for settling transactions.

This is a lot of responsibility for one layer to handle. And like the quote goes, "with great responsibility, comes a great amount of time to handle this responsibility". Since no one likes to wait, more scalable and faster solutions are required.

Layer 2 - The Networking Layer - The Sales Team

As anyone knows who has worked in any type of sales or commercial fashion, the ABC's of sales is "Always Be Closing". Like a skilled sales team, Layer 2 solutions want to process transactions faster and in an affordable way so that the customer keeps coming back.

There are many flavors of these types of solutions but at their core, they provide methods to escrow assets so that two or more parties can transact at a faster pace without involving the main chain (Layer 1) settling every time. These methods are growing in popularity as more and more transactions are hitting the popular networks.

Wesley

@wslyvh

Skip L1 - Build on L2 🚀

14:48 PM - 30 Dec 2021

Rollups

Rollups allow for computation of non-critical elements to the blockchain like executing the code smart contracts to be done off-chain. Information that is processed by the rollup on a sidechain is then 'rolled up' on to the main chain. This is done under one signature and added to a block as any normal transaction would. The two most popular approaches to this are Optimistic Rollups (OR ) and Zero-Knowledge Rollups (ZK). Optimistic rollups, like Polygon, send their final computations "optimistically" without any requiring proof of validation. ZK rollups, like zkSync, uses the cryptographic concept of zero-knowledge proofs which allow for a submitter to prove knowledge of certain information without exposing that information. It is the 'secret handshake to get into the club' of the blockchain world.

Sharding

Sharding achieves scalability by dividing tasks up into more manageable pieces and then spreading those tasks across the entire network. This allows for the necessary tasks of both validating and authenticating transactions to happen in sequential order and at the same time. This is the project manager on the team that lives and breathes on a JIRA board. It makes sure everyone is working dutifully and towards the same goal.

State Channels

State channels allow for a larger amount of assets to be committed to a certain transaction with the idea there will be several smaller transactions that are within this amount. In this case, a party can transact multiple times with another in an open state channel that is not committed to the main chain. Only after the parties agree to close the state channel, do the transactions get broadcasted and settled from each account. While there could have been many transactions that took place between the two parties, the main chain only sees two. This saves on compute for the settlement.

Source: @deversifi

Layer 3 - Application Layer - The Marketing Team

So we have established a base for the transactions to take place (layer 1) and made sure that these transactions can be done in a scalable fashion (layer 2). Now it's time to tell the world about our accomplishments! Like any good marketing team inside a company, you want to get your product out in the real world and have customers use it. This is where Layer 3 or 'the application layer' comes into the mix.

Like a magician that doesn't reveal its secrets, the goal of Layer 3 is to abstract away all of the work of the earlier layers to allow users direct interaction with applications. Through the creation of DApps (Decentralized Applications) that live on Layer 3, real-world use cases can be addressed to enable the greater expansion of blockchain technology.

Since the goal of layer 3 is to mask the unique technical and semantic aspects of a given network, this layer is also prime real estate for interoperability. As this area of research grows, innovations around layer 3 will be important to deliver a seamless user experience similar to the Internet Protocol. Hopefully one day we can say "Blockchain, it just works!".

Like any business, teams and structures can and will change. The layered architecture that we have currently may very well do the same. As Web3 continues to embrace new use cases and discover unknown challenges, investment in research and development for solutions will be needed. Luckily, there is a well-beaten path from the Internet Protocol to act as a guide for the future.

Photo by Chastagner Thierry on Unsplash

Blockchain Interoperability - A Gentle Introduction

DappaDan — Fri, 04 Feb 2022 13:46:49 +0000

If you were to survey the entire Crypto community on what is needed to make Blockchain technology more mainstream you would probably get the same amount of answers as people you asked. Some would say improvements to onboarding are critical, others might feel that improvements in the UX are the true key. You would probably also get a few people banking on Ethereum moving to Proof of Stake being the silver bullet to the path of glory. We all know those types.

The correct answer is, of course, blockchain interoperability. Right?

Introduction

Interoperability might be a tricky word to say 5 times fast and even a tricker word to type out over and over again (thank you spell check!). But what does it mean?

The earliest definition comes from Peter Wenger who defines interoperability as the "ability of two or more software components to cooperate despite differences in language, interface, and execution platform" (Wenger, 1996).

You might not have known the exact definition of interoperability but you have experienced its benefits as all modern-day communication is built on top of this concept. The fact that you can access this page on the browser of your choice through the series of TCP/IP protocols is a testament to the power of interoperability (Blockchain Interoperability, n.d.). Imagine a world where this article was only available via Microsoft Edge and if you wanted to view it on Brave then I would need to send it through a specific proxy and destination network for any Brave users to access it. That would be a nightmare.

This is not a world I want to live in but sadly this is the state of affairs when working across different blockchains. Seamlessly and securely transferring assets across blockchains for example an NFT on Ethereum to Solana remains a mountain to be conquered.

Why is it important?

While we all like to be in team ETH or team SOL on Twitter, in reality, we shouldn't need to be this tribal and this fragmentation is only hurting the crypto community as a whole.

The reason behind this 'display name warfare' is primarily due to many blockchains being built as silos by design. Freely exchanging data and assets weren't inherently built into the original structures of the most popular blockchains.

Armani Ferrante

@armaniferrante

It's pretty common to see these types of takes from @evan_van_ness and others on Solana. Kicking people when they're down. Would be great to see you guys in the arena instead of booing from the stands. twitter.com/evan_van_ness/…

03:12 AM - 03 Feb 2022

Evan Van Ness 🐬 @evan_van_ness
This bridge that Sqlana hyped as "secure, trustless" a few months ago just got hacked for 80k ETH About $220m at current ETH price. https://t.co/ADKQEIMwoA

As much as some might not like to admit it, different blockchains have their strengths and weaknesses. Whether it's a priority on decentralization, scalability, or security. Wouldn't it be great if depending on the asset or application being used, you could leverage certain chains based on their strengths?

If only asking the question was as easy as implementing the solution.

Why is it a challenge?

Blockchain Interoperability is a tricky (and some would say impossible) endeavor due to the very nature of blockchains. For interoperability to be achieved there are a few things that are required in a three-phase procedure (Belchior et al., 2021):

1) Source Blockchain - this is where the initial transaction will be initiated.
2) Target Blockchain - this is where the transaction will be finally executed.

Step 1: Locking of the asset on the source Blockchain. This is needed to ensure that the record will not exist twice on the source blockchain and target blockchain.

Step 2: Committing the Transfer - we will explore later how different solutions handle this. Some may use a 3rd party or protocol to handle the transfer from source to target blockchain.

Step 3: Create a representation - now that the transfer is completed, that asset now needs to exist on the target blockchain.

For these steps to be performed, interoperability on both a technical integration level as well as covering any application-specific semantics between the two blockchains needs to be covered (Belchior et al., 2021) These challenges have been met with a few different approaches which have resulted in some interesting projects.

Three Different Approaches

There have been many ways to categorize Interoperability solutions, the most modern way is by dividing them into 3 types: Public Connectors, Blockchain of Blockchains, and Hybrid Connectors.(Belchior et al., 2021)

Public Connectors
These types of solutions were the earliest attempts at providing blockchain interoperability between cryptocurrency blockchains. An example of this would be the notary schemes that are utilized by both centralized exchanges like Coinbase and decentralized exchanges like Uniswap. These schemes monitor for certain events, like the deployment of a smart contract, taking place on multiple blockchains which then trigger transactions between chains. (Belchior et al., 2021)

Blockchains of Blockchains
To achieve interoperability, these solutions allow for the reusability of several layers of the blockchain including the data, network, consensus, incentive, and contract layers. These solutions typically operate with a secondary blockchain that is application-specific and interacts with the main blockchain as sort of a source of truth. (Belchior et al., 2021)

The two main examples of these are Polkadot and Cosmos. Polkadot consists of three levels - 2 infrastructure (Relay chain and Parachain) and a Bridge level. The Relay chain is Polkadot's main network and is where all transactions are finalized. The parachains are customized blockchains that operate independently for specific developer or business use cases. These parachains rely on the Relay chain to ensure the accuracy of transactions. Lastly, the bridge level allows for communication with other networks like Ethereum when needed. (ChangeNOW.io, 2021)

Cosmos is similar to Polkadot as it allows for independent blockchains to be running in parallel with each other. These blockchains can communicate with one another through the Inter-Blockchain Communication protocol (IBC). The IBC Protocol consists of a transport layer for security/authentication and an application layer for how data should be read by source and target blockchains.

Hybrid Connectors
Hybrid Connectors achieve interoperability through the use of an abstraction layer that exposes a set of operations with which dApps can interact. The two primary approaches are through trusted relays and blockchain-agnostic protocols. (Belchior et al., 2021)

Trusted Relays are trusted third parties that act as redirectors for transactions from source to target blockchains. By having a complete view of blockchain operations via the abstraction layer, blockchain-agnostic protocols can provide accountability to transacting parties across multiple blockchains. You can think of these as sort of the prison guards watching over the prisoners in the guard tower.

Outside of these categories, there are exciting projects such as Chainlink which recently released the Cross-Chain Interoperability Protocol (CCIP) that enabled smart contracts across different blockchains to communicate and exchange data. Another is the Universal Passport from Nervos which is a suite of tools built on top of the Nervos CKB chain that enables "cross-chain circulation of assets".

Like most solutions in this space, blockchain interoperability is still an angry baby looking for the right bottle. Each approach offers a series of benefits and there is a body of research being conducted to make improvements. Rather than bashing each other for choosing the right or wrong crypto to maxi, solving the interoperability problem should be a top priority for those in the community. This is a final boss-level challenge on the path to greater blockchain adoption which everyone benefits from. Solving this will open up a never-ending tap of use cases to apply this beloved technology to. Together, forward.

Belchior, R., Vasconcelos, A., Guerreiro, S., & Correia, M. (2021). A Survey on Blockchain Interoperability: Past, Present, and Future Trends. ArXiv:2005.14282 [Cs]. http://arxiv.org/abs/2005.14282

Blockchain Interoperability: What Is it and Why Does it Matter? (n.d.). Retrieved February 3, 2022, from https://www.algorand.com/resources/blog/blockchain-interoperability-what-is-it-and-why-does/

ChangeNOW.io. (2021, November 18). Why Is Blockchain Interoperability The Future Of Cryptocurrency? The Capital. https://medium.com/the-capital/why-is-blockchain-interoperability-the-future-of-cryptocurrency-dd083374ad5d

Gorbunov, S. (2022, February 3). Lessons Learned: The Internet’s Evolution as a Blueprint for Blockchain Interoperability [Blog]. Lessons Learned: The Internet’s Evolution as a Blueprint for Blockchain Interoperability; Nasdaq. https://www.nasdaq.com/articles/lessons-learned%3A-the-internets-evolution-as-a-blueprint-for-blockchain-interoperability

Wegner, P. (1996). Interoperability. ACM Computing Surveys, 28(1), 285–287. https://doi.org/10.1145/234313.234424

DEV Community: DappaDan

Mask On: A Code Journey into ID-Mask and Mina

What is ID-Mask?

How Does it Work?

Step 1: User Signature

Step 2: Consuming the Data and Creating Proofs

Step 3: Using the Proof

Step 4: Verifying the Personal Data

Step 5: Emitting the Event

The future of ID-Mask and ZKApps

The Confused Developers Guide to Sidechains

Introduction

Sidechains - A Story of Relationships

Layer 2s - The Other BFF

Sidechains on the Horizen

Horizen to EON

EON to Ethereum

Get Started Building

Wrapping Up

Layers of a Blockchain: A Guided Tour

What Are Layers?

Why Have Layers?

Layer 1 - Protocol Layer - *The Accounting/Legal Team *

Layer 2 - The Networking Layer - *The Sales Team *

Layer 3 - Application Layer - The Marketing Team

Blockchain Interoperability - A Gentle Introduction

Introduction

Why is it important?

Why is it a challenge?

Three Different Approaches

Layer 1 - Protocol Layer - The Accounting/Legal Team

Layer 2 - The Networking Layer - The Sales Team