📖Open-Source

Smart contracts, minting policies are only a part of the full product. In order to function properly, dApp usually consists of:

• PAB, which is responsible for building and balancing transactions specifically built for a smart contract.

• Blockchain querying service. In order for the frontend to function properly, it has to constantly get up-to-date information about smart contract state, including UTXOs and their state. This is again specific to smart contract business logic.

• UI. It may sound simple, but dApps heavily rely on frontend. Frontend usually implements complicated business logic.

It is common practice to only publicly disclose smart contract (validator script) code. It does its job, by proving that the core component of the dApp is secure, fair and reliable. But how can CERRA utility token holders have ownership of the platform, without having the full code? That is why we will be open sourcing each and every smallest part of Cerra platform, including all of its dApp products.

We are making it our mission to eliminate hosted black box backend services from our stack completely with the help of Lucid (https://lucid.spacebudz.io/).

This tool will enable us to replace backend transaction building, balancing and querying with the frontend solution, which can run in a decentralized manner on users' browsers.

It was also previously possible to achieve that with Cardano-serialization-lib, but its low-level nature is an obstacle to a fast development cycle.

We also released the P2P lending Smart contract to the public, making it open source. You can find smart contract code on our Github: https://github.com/cerraio/lending-plutus

We will be open sourcing other system parts, once P2P lending is released to mainnet.