#DrupalEthereum @digitaldonkey09
Source: https://w3techs.com/technologies/details/pl-php/all/all
CMS
Ya. Goal is semi-decentralized (for now).
Many Dapps add a database
Client signs using Transaction-signers
Server just pulls data
(no private key on Server)
road to a decentralized economy
and many more...
Full Client?
Integration
Libraries
Complementary Tools
The goal is not a full client, but a toolset to easily build services connecting the web 2.0 to Ethereum
Servers (Ethereum-nodes)
List Servers, gather information (Server Entity)
Deployability, Testability
Accounts
Ethereum Addresses
Map Accounts to Drupal Accounts
➡ Identity for known user group
Transactions
Read (own contracts/known ABI)
Log TX based on Contract interaction
Process Events data in Drupal
Smart Contracts
Manage deploy as Drupal Admin
Provide ABI to process data in Drupal & frontend
Watch for Blockchain Events triggers by Contracts
Ethereum Signup
Ethereum user connector
Basic Infrastructure
Text
Text + Private Key => Signature
Text + Signature Text => Public Key (--> Ethereum Address)
and
The challenge to reach mainstream users
diagram by Bobby Dresser (uPort)
⇢ Experiment with UX interactions
⇢ Develop standards for Dapp interaction
Architecture summary
(MetaMascara is an experimental zero-install signer)
everything is an experiment
Visualize TX signer state
Initialize dapplet when requirements are met
thorsten.krug@consensys.net
@digitaldonkey09
The development of Drupal Ethereum Module
has been sponsored by ConsenSys
@ConsenSys
https://slides.com/digitaldonkey/paralelni-polis
and all others I talked to
(Commit stats refer to the various involved projects)