Home

Cothority-SDA

• Cothority - Collective Authority
• SDA - Secure Distributed API

The project offers a framework for research, simulation and deployment of crypto-related protocols with an emphasis of decentralized, distributed protocols.

Our documentation is split in three parts:

• Users, when all you want is to use one of our services
• PhD, for those of you who have an idea and want to implement it using Cothority
• Developer, hard-core hackers that want to make our code even better

Users

So you want to use one of our services and you are interested in one of our projects:

• CoSi - Collective Signing, where you can submit a hash of a document and get a collective signature on it
• Cisc - Cisc Identity Skipchain, a distributed key/value storage handled by a permissioned, personal blockchain with an SSH-plugin
• Scmgr - Skipchain Manager, if you want to dive in further using Skipchains and create your own root- and config-Skipchains
• Conode - everybody can run his own personal conode that can be included in the global cothority-network

PhD students

Privacy preserving, decentralized, distributed, blockchain-related, and lots of other buzzwords are covered with our Cothority-framework. Different projects are done using our framework in EPFL and other Universities. Here is some overview of what you can do and what not.

• SDAArchitecture gives you a broad overview of how the different parts work together
• CothorityTemplate explains a very simple protocol/service/app that can be used as a template for further work
• CoSiExample shows you how the ideas of a paper have been implemented
• Coding technical aspects of programming in Cothority

Developer

So you want it all, go down to the base of the code and make it faster / more secure / better understandable. Or perhaps you see a bug and want to fix it yourself. Here is a list of places that can help you:

• GoDoc entry point to the go-documentation
• Coding technical aspects of programming in Cothority
• Layers that are used in the framework
• DirectoryScheme what is stored where
• EntryIssues if you want to start with a small issue
• Roadmap things we plan on doing
• OpenIssues what we know to fail and how to work around it