CommonAccord

Re-wiring the ecosystem

Problem #1: blockchain not enough

Smart contracts are not contracts:• Automation but no text• Using blockchain: data in too many places

(privacy, data security)

Problem #2: unstructured data

• Contracts mix business data with boilerplate• Trapped in Word/PDF documents• Spread across legacy systems

But GDPR requires:

• Personal data inventory• Privacy by design • Right to be forgotten• Data portability

GDPR – April 2018

Solution

Structured data, contracts as code:• CommonAccord data model• Cryptographic access control and management• Smart contract ready documents

Architecture

The Smart Contract ecosystemSCLL

CommonAccordHuman-friendly language to describe contracts as modular components in an

object oriented model

TELP

Target Platform Executable Languageto transform SCDL instructions into platform specific instructions

(Solidity, Golang, etc…)

SCDL

Smart Contract Description LanguagePlatform independent language to capture meaning and intent of contracts into

events, conditions, flows etc…

CommonAccord in 3 steps

Education Implementation

Contentcuration

Legal and regulatory

world

- Codification core- Outreach / Education- Implementation- Curation- Administration

1 project

through

3 types of actions

connecting

2 worldsBusiness and IT

world

Current status

• Member Caisse des Dépôts « LabChain » consortium• Member of Kantara Initiative discussion group on

« Blockchains and Smart Contracts »• Joint paper with MIT Connection Sciences accepted

by W3C – discussed at workshop on Distributed Ledgers on the Web, 29-30 June, 2016

• Solution implemented at several startups• 3 students from Paris II started codifying docs as part

of their summer project

Questions

http://www.commonaccord.orgmarc@commonaccord.org

Connecting two worlds

General CounselData Privacy OfficersLawyers, Regulators

Publishers

Hyperledgerproject

CommonAccordproject

Developers (IoT, blockchains, payments)

CIOs