Membrane

About

Overview

In the picture above, a user trades a token of a certain value, for a certain amount of time or data in order to connect to the Internet. The value exchange between the user and the access point provider occurs automatically following the Membrane protocol.
The picture above exemplifies, in a simplified manner, the different levels of abstraction that the Membrane specification covers. The actual specification is more detailed though, but the chart above gives you a grasp on how basic logical blocks are mapped onto real world object classes for a blockchain-based end-user application.
In the example above, the Rider is mapped as an Entity (A Membrane Business Model object) and the Driver is an object of the type Business Unit. To request a ride, the Rider calls the RequestRide() function which ensures that the ride is funded via the sub function called FundTransaction(). The Driver then accepts the ride via the AcceptRide() function call and makes sure that funds are locked until the end of the trip via the LockFunds() function call. When the ride reaches its end, two additional functions are called: The OnReachedDestination() called synchronously (triggered by the device GPS, for example) releases the funds to the driver via UnlockFunds() call, and finally there is an asynchronous call to SetReputation() that might happen later when the rider wants to give feedback about the driver and vice-versa.

Use Cases

  • An ecosystem for publishing game credits along with a marketplace where they can be utilized.
  • A software activation tool based on specific tokens.
  • DACs — Decentralized Autonomous Companies — Companies that work by putting together independent business units which interoperate by exchanging services in an autonomous manner.
The image above shows a comprehensive approach for the paradigm of value transport within a Membrane application. To the left, you can see the coins that play the role of legacy tokens that provide value to the ecosystem. These coins are pegged to the internal tokens by means of the atomic swap process. These tokens, by their turn, belong to a membrane sidechain and feed the basic functionality for the Membrane Business logic, which can be accessed by the Membrane Application via a basic API.

Conclusion

Next Steps

  • Building up a team capable of handling all the aspects of the basic implementation.
  • Finishing the partial implementation along with at least one MVP.
  • Working on the essentials until a basic implementation of the Membrane protocol can be spinned up as a live network.

--

--

--

Software as a Service (SaaS) powered by the Blockchain, supported by the MERGE Cryptocurrency and Tokenomics. Visit our official site: https://projectmerge.org

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Accessing Next Element While iterating | Python Tips

Cost-Effective Automated Testing

Arduino: Led Matrix 8×8, Max7219 and Arduino Uno R3

CS373 Fall 2021 Blog 11: Mason Eastman

Flutter fácil de internacionalizar — usando Provider y Json.

Big O Notation — Common Runtime Scenario’s

Flash Stock Rom on Xolo A550s ips

11111

Evaluation of Crodo and SafeLaunch platforms

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Merge

Merge

Software as a Service (SaaS) powered by the Blockchain, supported by the MERGE Cryptocurrency and Tokenomics. Visit our official site: https://projectmerge.org

More from Medium

ARTIST OF THE ERA: JUDY CHICAGO.

What Are NFTs, And Why Are They Exploding?

【NOTIFICATION】 FIXING THE RARE NFT PET’S REPRODUCTION ERROR

Meme Revolution in NFT Industry