CipherPact

Decentralized, trustless and publicly verifiable suite of financial agreements on Ergo and Cardano
Report Bug · Request Feature

Table of Contents

1. About The Project
   • Built With
2. Usage
3. Roadmap
4. Contributing
5. License
6. Contact

About The Project

With ever-increasing censorship and privacy-violations around the world, there should be tools to circumvent such acts and empower parties to perform financial agreements while maintaining the anonymity of those involved in the agreement. By substituting what would be a mediator or external platform hosting an exchange between two parties with a smart-contract, the mediator will remain fair, transparent and have an action-to-action documentation of the event happening without necessarily divulging the identity of the two parties, which may then be referred to in the future by any of the parties involved, for posterity or legal purposes.

Why blockchain-based financial agreements:

• Removal of trust on a third-party acting as mediator, code is law. Because smart contracts and the records they generate are verifiably stored using encryption on a shared ledger, users who don’t know each other can outsource trust to the blockchain rather than relying on a trusted intermediary.
• The cryptographic design of the blockchain and its use of distributed nodes makes it extremely resistant to hacks or security breaches.
• The contract is executed when one or more of the parties submits proof of the satisfaction of the terms.
• Publicly verifiable (actions taken place within an agreement are documented by the smart contract)
• Using code to implement contract terms avoids ambiguity over contract provisions that can lead to disagreements.

Built With

By launch, smart contracts should be deployed on the Cardano (solidity via KEVM or Plutus) and Ergo blockchains

• Solidity
• Plutus
• ErgoScript

Roadmap

See the open issues for a list of proposed features (and known issues).

Q2 2022

• Cryptographically-verifiable delivery disputes
• Escrow contract -> Solidity to Plutus port
• Initial minimal build of the client-side application

Q3-Q4 2022

• Escrow Contract -> Plutus to ErgoScript port
• Zero-Coupon bonds contract implementation in Plutus and ErgoScript
• Legally-binding Payroll contract
• UI design of the client-side application

2023

• UI implementation of the client-side application
• Contract For Differences (CFDs) contract implementation in Plutus and ErgoScript
• Hell or High Water contract implementation in Plutus and ErgoScript

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes (git commit -m 'Add some AmazingFeature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

License

Distributed under the GPL-3.0 License. See LICENSE for more information.

Contact

JKleinne - @jkleinne - jkleinne@pm.me

Project Link: https://github.com/CipherSpell/CipherPact