This blog has moved

This blog has moved, update your links and RSS to

You can read the reasons for moving the blog, it centers on me wanting to control the architecture and have it run on the decentralised web

Installing IPFS via ipfs-update on Linux or WSL

  1. download latest version of ipfs-update download latest from e.g. wget

  2. extract the zip: e.g. tar -zxvf ipfs-update_v1.6.0_linux-amd64.tar.gz

  3. go into the folder: cd ipfs-update/

  4. run the install command: sudo ./

  1. You should now be able to check it is working via: ipfs-update help
  1. Intall latest go-ipfs sudo ipfs-update install latest

IPFS should now be installed!

Devcon 4 report: Day 4

Previous days:

Today is a shorter update. I spent a lot of time in meetings with different tools teams (Truffle, Zeppelin, EthPM) about how to better do contract upgrades in a DevOps manner. Expect more from me once I get it working and write it up ๐Ÿ˜‰

Internet archive

Brewster Kahle

Distributed web version of IA

Told a story where back in the day they started taking Bitcoin, so they had some young guy come in and help them set up their initial wallets. It was Vitalik ๐Ÿ™‚

Instead of the world wide web where we have lots of blogs, everything has collapsed into Facebook and Twitter. People are building castles. The web is being turned into a global surveillance tool
Internet Archive is getting involved in the decentralised world to help try and affect change.
The goal is: Universal access to all knowledge. Want to be the library of Alexandria version 2.

He loaded up
Showed that the first HTML page is a bootloader. Loads up the JS libraries to access IPFS, torrets.
Browsed around the site, loaded videos. It all just worked.

More privacy. Reader privacy, and no third party storing of data.
People being rounded up based on what they’ve read, has always led to bad things.

13 challenges (I missed some)

  • Naming of decentralised websites
  • Permissions, auth and key management
  • Identity & reputation
  • How do you manage & name mutable data at scale?
  • The web beyond advertising: who will pay for what and how.
  • How do we make the decentralised web work in browsers today
  • Storage in the DWeb
  • Governance in the DWeb
  • Defining D-terms
  • Rethinking UI and UX for a decentralised web

Money is the killer รapp: crypto in Venezuela

Venezuela has issues with their currency and government controls and corruption.
Bitcoin is the most liquid in Venezuala, about $1m being traded a day.
Crypto is being used for:
Earning across borders.
Storing value (safer than banks)
Defeating extortion, when crossing boarders.
Providing aid to families in different locations.
Open money initiative. They have a wiki for Venezuelans to use and learn how to use crypto

Self-Sovereign Sexuality

Ameen Soleimani, Chelsea Palmer

Will talk about how the Ethereum community, and the sex worker community are aligned. It was easier to just take a photo of each slide for this talk, as they have written down for each aspect how they are alike.
Where is blockchain adoption going to happen first? He realised that this community that has been ostrasied from traditional financial system was a great place to start.

About a year ago, he was feeling pretty depressed. Wasn’t spending time on Tinder because he was working a lot. He wasn’t having luck talking with girls and was getting more and more nervous over it. He had a lot of money and was lonely, so started looking up sex workers in his local area. Made a meeting with a local escort. But when he went to get cash out, he was at his daily ATM cash out limit. He couldn’t get enough money out and had to change his 2 hour apointment down to 1 hour. He met the escort, talked about crypto, got her on board, and paid her by cypto.
Morality does not equal legality.

Was a sex worker. Wish she had crypto back when she was working. Now she is a crypto educator.


Needing to trust and verify.
Vetting a new client for first time, need to get a referral from another escort. Difficult for 1st time customers.

Sex workers are cypherpunks. They use proton mail, loads of crypto currencies.

Sex workers can be immediately blocked by most traditional financial systems.
Sex work criminalisation, currently stops sex workers from calling local police if they have things to report. As it is more likely that they will just be arrested than helped.

Devcon 4 report: Day 3

Previous days:


Building the Ecosystem for the Next Wave of Users


Creating a story and personality for what you build
They found that adding a background and story behind the cats helped with the adoption. The breeding concept gave a good anchor point.


Users were burning gas without realising. Were sending 10x more gas price than required.
User education and guidance was required quickly after launch to help teach.
Adding more feedback after a transaction to the user to make them more comfortable. Sending emails when things happened and what will happen next after breeding cats.
-Users need guidance when they’re in unknown territory.


Teaching a user that is interested in the service, that they need something called a wallet, they need cryptocurrency. Bit of a learning curve.
People came to the service because they wanted to buy cats. But now they’ve got a PhD in cryptoeconomics, which is not what they were after. Created a massive drop off rate of new users through the signup process.


Making the Web Distributed Despite Itself

Dietrich Ayala, Mozilla

“We are committed to an internet that promotes civil discourse, human dignity, and individual expression”
What does it take to be a 100 year organization.
The web is ~25 years old, and its not going to well. Being used a misinformation platform, fueling hate.

There is WAY more information and web apps available online via web browsers, than there are available via apps on iPhone & Android (~5 billion pages).
URLs are what made the web powerful and universally accessible. Urls are understood by technology people, but “normal people” don’t really know what a web browser is, or where things are stored. Same with domain names.

What does re-decentralizing the web look like?
Current web is centralised. Browser request, response. Easy to censor.
All the power resides on one side, on the server. The browser doesn’t have any say.
While we have that centralisation chokepoint, we won’t be able to get away from centralised services like Facebook.

How do we go about creating a decentralised browser to give control back to users?
Need to think how to build things for century long longevity. Whatever we build now will need to be supported.
Start with protocol primitives that can be built up on.

How do we get those lower primitives prototyped and built, so others can start building higher level primitivies
As a browser vendor they could do it as part of the browser engine, or JS APIs, or extensions. Makes sense for them to do it via extensions, to give everyone a bit more flexibility while experimenting

Announcing libdweb extension


IPFS team took it, got IPFS running in it. Got IPFS running completely within a browser.
But now they have a bunch of new things they need to think about. What is the origin of a website loaded by a IPFS hash. This has an impact on local storage, cookies, certs, etc. What is the threat modelling for this.

Use what you make, if you don’t use it why would others. Build for the long web. The web was (originally) built with redundancy built in. Are there multiple implementations of your software.


Privacy for Everyone, Recent advances in privacy

Zookoo Wilcox, Zcash

Released Zcash 2.0, 4 days ago. “Sapling”
They reduced the time complexity required to generate a ZK proof down dramatically. Should enable them to be generated on a mobile phone now.

They did this by replacing the hash function that is used when creating a ZK circuit.
This reduced the time required by 75%. Took it from ~40secs to 10secs. But still too much time. So replaced some of the ECC functions used to reduce to 5 secs. Then did split circuit design to half it to 2.3 seconds.

One of the troubles they have had, is ZK-SNARKS required the “toxic waste” which was the secret string to provision the system. They went through an elaborate ceremony to create it to try and ensure that it could never be created by any 1 person at any time. But still has a cloud over it as you can’t convince everyone of it.
ZK-STARKS doesn’t have any “toxic waste”. But the proof size is orders of magnitude too big to be used in a blockchain in every single transaction.

They could try changing their Blockchain away from Bitcoin software based, to make it higher bandwidth so they could put in STARKS.

Common thoughts are “regulators are scared of privacy” and don’t like things like zcash. But the regulators in USA have been fine with it.
New York requires cryptocurrency companies to register for a “Bit license”. Zcash is the 7th cryptocurrency that has been explicitly approved to be used and traded, and they called out the privacy preserving aspects.

Previously SSL encryption was scary and governments were worried that it could be used by criminals, but is now required by governments. Blockchain encryption will probably be the same thing.
The regulators even told them “We don’t want the pocketbooks of our children and family open to everyone on the internet”
It is not okay for our society to go down the path where everyone’s privacy is read by 2 or 3 centralised services, it is wrong and dangerous.


Lex cryptographica : the legal challenges of new blockchain-based lifeforms

Primavera De Filippi

Properties of Blockchain:

  • Blockchain is a decentralised database
  • Networks are global and transnational
  • Blockchain is resilient
  • Tamper resistant
  • Transparent
  • Non-repudiable (need to use private key, can’t deny it later)
  • Pseudonymous
  • Guarantee of execution

Blockchain code can be written to include traditional law, it only cares about what the code says.
Code is trustless and allows disintermation and autonomy.
Conflict between the rule of code, and the rule of law

Governments use the law to put pressure on centralised companies via regulators to say what the code can do.
Can the new wave of crypto-anarchist effect change in the new decentralised web.
Traditional property rights. Are defined by law, and can be taken away by the law.

It is now possible to deploy Autonomous Agents. They can hold property, and can execute smart contracts.

Created blockchain based “Plantoids”. They can’t breed by themselves and need others help.

1. capitalisation. Collecting cryptocurrency to repoduce. It tries to loook pretty to encourage people to donate ether to it.
2. if it has funds, then it can ask people to vote on the new artist to create its child
3. it will use a smart contract to hire the artist to create the new plant model.

Artist gets royalties from how much the plant earns as an incentive to make good ones, and for them to breed.
Now instead of sending money to artists, you send money to the art pieces. A different funding model.

The plantoids can have requirements put upon them. Its children need to be based on its rules (requirements for decorative elements) and artists can put new requirements on the ones they create. Will make different species emerge.
Requires “Holographic consensus”
COALA (Coalition of Automated Legal Applications) is a global research initiative.



Decentralize, Democratize, or Die

Cory Doctorow, EFF

EFF origin stories from 25 years ago.
The original “crypto wars”. NSA put restrictions on civilian use of cryptography.
Gov tried to lock everything down to just DES-50 encryption. EFF tried to show that DES was insufficient and built hardware that could crack the entire DES space in 2 hours.
But govs said ‘well, we need it otherwise criminals will go dark’
The technical arguments didn’t work. So EFF posted the source code for stronger encryption online on usenet, then argued under free speech that it was fine. Was the way EFF allowed people to use encryption higher than DES-50.

Showing that there are more tactics in your toolchest than just “deploying code”.
Main ways:
Deploying code and hardware.
Markets. Getting partners to go in and argue.
Norms. What is socially acceptable. Moving encryption from just nerds, to making it mainstream.
Law. Whats legal.

You can’t make everyone you communicate with use crypto, something will leak
You can’t audit all of your hardware.
You can’t verify every cypher algorithm is solid and sound.
OPSEC is not going to save you. Security favours attackers. Defenders need to be perfect all of the times, attackers only need to find a mistake once.

Crypto and privacy tools can help protect and shelter you for short periods of time. Can help protect you while you have discussions that you aren’t ready to have public.
There are many things that used to be illeagal which are now embraced and considered normal (being gay, interraccial marriage, weed).
They happened because people could have secret communities that they could whisper and have secrets with people. Social progress was able to continue.

DMCA was used to stop people reversing engineering DRM.
So anyone what didn’t want you to modify hardware, would just put a tiny layer of DRM on top of the hardware. To make it impossible to modify without “breaking DRM”.
Insulin machines using cartridges that have DRM, so it is illegal to bypass the DRM to use alternatives.
Now that everything has a DRM chip in it, make it really difficult for researchers to do anything without it being illegal.
DRM in browsers. No browser vendor promised to not use DRM to prevent security researchers from disclosing vulnerabilities.


Attacking. You want to make it so that the cost of attacking a system, costs more than the expected economic return.
This works, until the value of the thing you are protecting suddenly goes up (such as a cryptocurrency suddenly spiking).
For crypto people, it means the cost you should put in to protecting your computer is going up, because the vaule of what you’re holding is going up.
This means new 0-days for attacking machines are becoming more valuable, as the expected return is going up as there is more chance you could find private keys.
The rule of law is the best way to get things changed. We love code, but need to find ways to help the law change towards how we want it seen.


P2P Networking in Ethereum 2.0

Jannik Luhn, Kevin Mai-Hsuan Chia

Very short session

Validators are a new class of node. Similar to a shard node but only downloads recent history, and switch between shards regularly and randomly.

Networking protocol requires 3 things. Discovery protocol for discovery. Gossip protocol to distribute data. And RPC calls to sync data history.
Gossip will pass things out to a few neighbours to help it get diseminated throughout the network.


They used GossipSub by libp2p (rather than devp2p).
Did simulations for 1,000 nodes to see how things would work. Found that nodes didn’t go over 60% capacity. None hit 100% which meant that things weren’t being bottlenecked.

Cranked it up to 10,000 nodes

P2P implementation
They are using libp2p. Allows them to switch out the protocols like TCP, etc
Requirement for the networking layer was that clients should be able to subscribe to one or more shards. And the client should only receive data for shards it has subscribed to, and not others.
They have implemented the essential funcions like joining sharding network, subscribing to multiple shards, etc.


Managing upgradeability and EVM packages with ZeppelinOS

Facundo Spagnuolo, Open Zeppelin

Tutorial blogs are online

ZeppelinOS. Open source platform to help you build smart contract systems.


How to do upgradeability
npm install -g zos
zos init my-project

Write the smart contract (MyWallet contract)
zos add MyWallet
zos push -n ropsten
zos create MyWallet -n ropsten
> 0x23abba13

Later find there is a bug in the wallet.
Update the source code.
zos add MyWallet
zos push -n ropsten
zos update MyWallet -n ropsten
> 0xccab2314

This is all done using proxies
ZeppelinOS provides a standard way to fix bugs, and add new functionality.

EVM Packages
EVM packages are upgradeable on-chain packages of smart contract code

Can have your code depend on other packages and link to them. Later they can be upgraded.

How do we know these packages online are correct? ZeppelinOS Vouching system.
Will allow users to back the quality of an EVM package. Signal your support. First step towards a curated on chain packages system.


Unscrambling an Egg: Decentralization and the Zcash Foundation

Josh Cincinnati

Are we decentralised yet

What is the goal, what are we really after?
Zcash want to be used for the public good. The foundation is there to help guide and make sure the zcash company are on the right path.


CBC Casper Design Philosophy

Vlad Zamfir


“Correct by Construction” protocol design is a process of protocol specification which guarantees that the resulting protocol definitions satisfy desired properties.
As opposed to a process of iterated trial and error.

He spent 5 minutes talking about defining undefined, and how you can define the most undefindness you can have. I just got lost (a common theme throughout this talk)

“Bottom times bottom, is more defined than bottom”
“bottom times empty set is more defined than bottom times bottom”
(you can see why I’m getting lost here)

CBC protocol design, goes from defining the most simple things, and then define things on top of the previous definitions.

“sometimes CBC design isn’t quite straight forward”

The beauty of using CBC, is that the protocol is defined by the definition. Means there can’t be ambiguity, it just does exactly what it says it should do. Makes it easy to prototype and test, and things just work.
Thinks like not needing to worry about consensus protocols as much, as it all just work out. Showed an example prototype where shards can just keep becoming the new root that others build off, and them continuously rotating around with new roots.


Ethereum 2.0 randomness

Justin Drake


They use randomness in 2 places.
One in sampling to select validators.
Can also be used to expose randomness to EVM apps.

Goals for randomness is to make it unpredictable, unbiasable, and unstoppable
In RANDAO proposers are given slots. And they can reveal a secret to seed the randomness.
Gives the last revealer 2 numbers to pick from, the current random seed, or what they would add.

Verifiable Delay Functions. Takes an input, difficulty, and outputs the value and proof.
Can chain them to make it harder to bias

Need to make sure that good actors can calculate it within a threshold of attackers. They are thinking of creating VDF ASICs that can do it, and then handing them out to many people.

To create the initial random seed that will be used for the VDFs, they will use a RSA creation ceremony with 1024 participants. Just need 1 party to be honest to be successful.


VDF ASIC hardware
Doing it in partnership with Filecoin!


LibSubmarine – Temporarily hide transactions on Ethereum

Prevent reordering attacks. Keeps data private temporarily, can’t see who or what is being committed
Can add it into contracts fairly easily. Can modify ERC721 to add a “sealed bids”


Off chain you generate a submarine address and generate a merkle-patricia proof. Then on chain execute a transaction to commit the submarine tx, and then later reveal the proof.


The Entire History of You Is Being Sold

Jesse Leimgruber

In the USA there are 10,000+ companies currently pooling and selling your data. And it isn’t even being kept securely as Equifax showed. Data leaks are becoming more common occurrences.

Users need to own their data (Bloom app stores the data on your phone)
Limiting access (user is responsible in selecting how it gets shared)
Data reusability. Good UX to allow many apps be able to reuse the data.
They just partnered with BMW to use Bloom for BMW loans.
Also announced partnership with American Express to use bloom for their loans.

Devcon 4 report: day 2 – Ethereum 2.0 keynote

Other days:

Today had less sessions and was less intense. Apart from the keynote by Vitalik and SpankChain sessions there isnโ€™t much to report on.


The MC wrote a song (I tried to take a video but was too far back to get anything good, I’m sure there are videos online).

He is tokenising his songs and putting online

Welcome to Devcon 4

Aya Miyaguchi, Ethereum foundation

Ran through her history of learning about blockchain & Ethereum.
Ethereum has a chance to empower society with it’s decentralisation, but we need to protect against it being used to restrict people by centralised powers (traditional companies and gov). Important for Ethereum community to keep these values as we scale.
Ethereum foundation keeps on making sure it minimises power in individual people. It wants to see itself as helping connect and foster collaboration in the community and connecting dots. But its goal is to grow the Ethereum community, not itself. Is why it didn’t structure itself in the way of a traditional startup or corporate.


She has invited a number of special guest speaker for the week. Like the internet archive

Ethereum 2.0

Vitalik Buterin

It is the 10 year anniverary of Satoshi’s Bitcoin whitepaper.
Ethereum 2.0 is a collection of research projects that have been ongoing over the last number of years.
Back in 2014 he wrote a paper on how slashing could be used in a “proof of stake algorithm”.
There was a bunch of aborted research in 2014 around different scaling mechanisms. Poof of proof of work, Hub & spoke chains, hypercubes.

During 2015-16 was a bunch of quiet research.
Resarch on “consensus by bet”. Some people would bet, which influence others to bet on those blocks, until one of the blocks have enough backing.
Wrote a scalability paper in 2015.
Wrote about the “data availability problem”. Could allow malicious parties to not publish data, which is required in sharding.
Everything got stopped in 2016 after the DAO attack, and the Shanghai DOS attacks.
But still quite worki happening on ewasm.

First Casper FFG paper came out.
At Devcon last year he showed the new sharding design.
Vlad released Casper CBC paper.
End of 2017 they released a Casper FFG proof of concept of a hybrid proof of stake system. Would allow gradual upgrade and migration. This research got very far.
But meanwhile there was a lot of working happening on Sharding. During a retreat in March they had a lot more details solidify. But they realised that there were teams trying to implement hybrid proof of stake inside existing blockchain, then a separate group that is trying to make a sharding system and a validating contract. The 2 groups weren’t really talking to each other. Realised they could reduce a lot of work if they just integrated them better.

It did mean that they lost a bunch of work that had already been done. But it meant that it would be simpler, and be better integrated, and the final state would be much better. (I think they did a great thing being able to step back, not worry about the sunk cost, and made the better overall decision).
Meanwhile LOTS more research happening on things like cross shard transactions and contracts.
Development happening on beacon chain implementations.

Ethereum 2.0’s real name is “Serenity”.
Gets us closer to it being “the world’s computer”


Phase 0 will be part way between main net and test net. The beacon chain will be there and running, but can’t really do anything with it directly.
Phase 1 will do sharding of data. NOT sharding of state. Could do decentralised twitter on the blockchain. But no smart contract applications.
Phase 2: enabling state transitions (smart contracts)


Track overview

Layer 1 (sharding, casper), Layer 2 (state channels, plasma, sidechains), ZK-SNARKS, light clients, etc.
Suggested sessions:
Making sense of layer 2 – Josh Stark
Snarks for mixing signalling – Barry whitehat

Ethereum 2.0 sessions


Designing robust systems


Lots of centralised companies are harvesting our data. We need to take the web back.
Suggested talks:
LibSubmarine – Temporarily hide transactions on Ethereum – Stephane Gosselin 
Plugging the metadata leaks in the ethereum ecosystem – Peter szilagyi

Developer Experience
Suggested session on EthPM

UX design
She just flicked through many session names. Nothing jumped out.

Society & systems
Technology changes society. And society can influence tech.


Events around Prague 

Decentralized development, what does that even mean?

Amber from Clovyr

Web 3.0 is about trying to keep data close to where it resides, decentralisation, data portability,


Development of blockchain clients (Bitcoin, Ethereu, zcash). Funnily enough the core code contributors of those clients are centralised in just a few developers hands. But if you look at something like kubernetes they have sooo many more people contributing.
How about code hosting, 90%+ of projects are all hosted on Github.

Browser 3.0

Mist team.
Current browsers are owned by centralised companies who track (Chrome, Safari, setting default search engine, etc).
Metamask extension was removed from Chrome store for a while. Chrome apps all got killed off.

Lets build our own. Lets start by using Electron.
Current web3 clients on the desktop are Metamask, Brave, Ethereum Mist, Parity. 3 of those 4 were built on Electron. But electron has a lot of security issues which is a bad thing for crypto private keys
Electron keeps lagging far behind the latest versions of chromium, meaning it is vulnerable to known exploits for long periods of time. Mist team don’t want this so they are building their own electron alternative called Tau.

SpankChain: Payment Channels in Production NSFW!


Their “pegged” stable token is called Booty.
It all goes into the “spank bank”.


Took 4 attempts at payment channels.
2nd, the MVP. Was a unidirectional ether only. Issues they had was that querying infura was non-deterministic, and Truffle timeout was 240 seconds which meant things failed in production.
3rd they launched. They got hacked when they unlocked their geth node for the deployment. Was only unlocked for 140 seconds and lost all the funds in that wallet.
4th they upgraded it. Had p2p virtual channels, ERC-20. The contract got hacked “they got spanked”. Worked with the hacker to fix the bugs.

The rewrote the smart contract and the UX. There were issues with the original version trying to get adult performers to join payment channels, as they’d need Eth to pay the gas to run the transaction. So Spankchain would need to send the performers enough gas before the show starts, to open the channel. And then do the same again when they close.

Announcing “ComeSwap” to cash out your booty for Ether

Devcon 4 report: Day 1 – core tool updates

Other days:

The first day of Devcon started at midday, but still had 12 talks. It was a bit of an โ€œupdatesโ€ session. The main event kicks off tomorrow morning with the keynote by Vitalik.


  • Universal Ethereum Logins was the show stealer for me. The demo blew me away, and there is a full SDK available now to use.
  • Lots of research into switching from Devp2p to libp2p (the networking stack IPFS uses)

EF Grants update

Ken Ng giving an overview of how EF grants foundation has been going since the launch this year.

So far has given out $11,000,000 to 75 projects over 4 waves!
Grants program is to fundamentally empower the Ethereum community and open source development. About creating up the core Ethereum platform, for others to build upon.
Want to help people build their passion projects that will help the Eth community. There will be more waves of funding, be sure to apply.

Ethereum Mist

Everton Fraga from Brazil

Submitting transactions looks scary at the moment.
Currently revamping the transaction window with a lot more details

Syncing improvements. Instead of a full sync, do it in stages.

Ethereum Name Service

Nick Johnson


Making it easy to attach friendly names to Ethereum addresses.
Rolled out with the .eth support with traditional DNS.
Rolling out 2 new domains .xyz & .luxe

Permissionless integration via DNSSEC
Can claim now via or you can use EasyDNS

More researching is ongoing for the registrar. They found that a lot of the names are being owned by just a few people.
Moving to a “yearly rent” style model to prevent squatting. Also help pay for ongoing development

There will be a migration process over to the new domain registrar. If you do it within the first year then you get a year renewal.
Otherwise if you don’t migrate it after a year, the name will be released.


Adding support to into client libraries like Web3.js 1.0, ethers.js. And other projects like Gitcoin.
They are developing a new Dapp interface. It is much slicker and easier to use.


EthereumJS – Our roadmap for 2019

Is an implementation of most of the base Ethereum technologies, implemented in JS (EthVM, merkle trees, etc.)
Used by Truffle, Metamask, Embark, etc.


Ethereum JS virtual machine. 
Is a “web first” library, embedded in Remix and Metamask. Captures Ethereum’s state transition rules.
Looking at integration with ewasm, but there are difficulties in EthereumJS being completely async, but the current specification for ewasm is synchronous.

Ethereum JS client
It isn’t meant to be a R&D platform for new features and research efforts. An educational tool.
The architecture is inspired by bcoin 
It can currently sync to the main net (fast & light syncing).
In browser can sync via libp2p.

Ethereum JS Sharding (ShasperJS)


For the phase 2 Ewasm research, is taking a list of ordered transactions and executing them.
Why Shasper in JS? Because it’ll need to be written and supported so the other tools can use it.
Not much real info in this session.

EtherTS (Typescript)
There are lots of EthereumJS that is written Sync, and lots written async. Want to take the learnings from the last 2 years and implement them.
They started by using Typescript to help find bugs by pointing out type issues
*cheers from the crowd for using Typescript*
Will be using more Typescript in the future.


Zlex Beregszaszi, Solidity co-lead.

It is a “Language for language developers”
Last year he did a talk on Julia, but there was a naming conflict, so now it is Yul.
Easier to just show the slides for this bit. They are helping compilers build better code.
Is currently being used by Solidity, Flint, LLL


Making ICOs fair (Reversible ICO)

Fabian Vogelsteller

He has helped build a few important things, like Ethereum wallet, mist browser, web3, ERC-20 standard, ERC-725.
Tokens allow you to own them, and transfer them.
Just a smart contract with an internal list of account balances.

What triggered the ICO explosion was the way that smart contracts could call and integrate with each other. Could creating funding contracts, token issuance, etc.

But people greedy. Were collecting a LOT of money, but maybe without having a solid basis for the proposed project.
So how can we make this more fair, what makes a Fair ICO?

Vitalik wrote an article on “DAICO” as one possible solution, was based on voting on the funding flow from the pool to the developers. Problem is people don’t vote.

Reversible ICO

Funds are given over time based on a “tap”.
Everybody can send his tokens back and get the “not yet given” funds out.

1. allocation phase. Committing funds to the project.
2. distribution phase. Funds are released slowly over time.
2.1 if at some point you think the project has gone off course, you can withdraw your tokens and get back your (not yet given) funding.
3. Swap phase. Swap out for utility tokens to use the final project, or final shares, etc.

He is going to try it out with his own ICO for


SWARM Team update

Decentralised file storage.
Session is a collection of team updates

Warning: <My yearly rant as they never make any real progress>

I still do not understand why they don’t just embrace IPFS as the base decentralised file store layer, and then build Ethereum specific extensions on top of this. It would help ensure there is a critical mass of decentralised file nodes, faster connection times, resolution, etc. Not only that, the community has been building on IPFS for the last 2 years.

The ONE interesting part they were doing was the SWAP/SWEAR/SWINDLE incentive layer. That would have been a great research project to put on top of IPFS, and leveraged what is already built. But this year they didn’t even speak of the incentive layer!

They are just reinventing the wheel, and have delayed their own progress by YEARS.

New release process. It is now in the same repo as geth. Whenever there is a geth release, there is a swarm release.
Whenever there is a swarm release, the nodes at are updated to newest version.
It is easier to install now. Can get via apt-get, docker images, binaries.

Is a pub/sub system.
Is a key/value store.
Each user can only update their own key space, but can read other key spaces..
Could be used for IoT data feeds.


Rolled their own encryption algorithm.
Took an existing crypto algorithm and “tweaked it”.
Missed a screenshot of their variation.

I’m sure nothing has EVER gone wrong with writing your own encryption algorithm.

Access Control
Does it by encypring the data, and giving keys to just the people that should be able to access it.
Accessing content which is “access controlled” is enabled ONLY when using a local node.
Don’t use a public node, as they could read anything you have access to.


Metric logging for swarm nodes. CPU, memory, number of peers, etc.

“yet another messaging system”, why this over Whisper?
Focuses on efficiency over secrecy.
On by default, can’t disable.

Light Node
Only briefly connected clients that spin up, let a user do something, and then usually disappear



Universal Ethereum logins

The bad UX experience of signing up first time to Ethereum is terrible. Requring taking selfies with your passport to sign up for an exchange, to get buy Ether, etc etc etc.
The UX is so bad, that there were more ICOs this year than daily average Ethereum users ๐Ÿ˜‰


Showed an awesome demo of onboarding a new user, completely in browser. No keys or ether. Really watch this session for inspiration.




After Devcon 3, Implemented a libp2p version as an experiment.
It works, but the GO implementation of libp2p isn’t very modular and brings in a LOT of dependencies. This needs to be resolved before it is rolled in.

Devp2p was the Ethereum team created protocol.
Libp2p is the one used by IPFS.

Currently they have implemented libp2p next to existing devp2p implementation. Will slowly migrate it across to libp2p and remove the devp2p stuff.


The are working on the Moon project (This was my #1 thing from last year).

Moon browser: Instead of traditional accounts and passwords, uses crypto signatures.
What if you could fork an entire web application. (not just the front end, but the eth contracts as well).

To enable this, Dapps need a formal specification. A spec of everything this Dapp promises to do.
So to enable moon browser to do something like this they needed to solve this problem.

They looked at a bunch of existing formal spec languages, but non fit. And all were slooooow.

So they created their own called “Formality”

Devp2p development update

Felix Lange, Maintainer of the devp2p specification.

Itโ€™s a p2p networking stack.
Doing experiments on running devp2p apps on libp2p. Have an idea how to integrate libp2p into devp2p.

He seemed a bit defeatist. “yeah there are a bunch of implementations. Pretty much all Ethereum blockchain implementations”
State of live network. “Well we’re still alive”.
Development update. “This is where we usually talk of what we did in 2018. We finalised writing up the spec! And we have a test suite now”
Geth p2p changes. They implemented mitigations to a responsibly disclosed denial vector.
Sharding research is mostly being done on libp2p at the moment. Peers need to switch quickly for sharding, which doesn’t work too well in devp2p right now.

Special projects

Dr. Virgil Griffith

Is a grab bag of links to cool projects.

  • Moving nash equilibriums.
    Prisoner’s dilemma is non-cooperative. But can change to cooperative if they both pony up a deposit.
  • Created a new frontend for EF grants
  • Created a new wiki
  • ethereum gift cards
  • peaceBridge. ETH-ETC bridge.
  • They just gave Ethereum Classic a $150k grant.
  • can help you create wolframe code. Can use it as an oracle to calculate big numbers
  • Using Intel SGX on desktops, allows you to use any desktop PC as a hardware wallet.
  • helps protect your staking machines in future.
  • The Crypto Paradise of the Caribbean

Running docker on WSL (Windows Subsystem for Linux)

UPDATE 2019/11/22:
There is a much better way to do this now with WSL2.ย  You can actually host the Docker engine inside WSL2 and have it accessible to windows & Ubuntu without needing to expose without TLS. If you did the steps below previously, remove the export DOCKER_HOST declaration before updating to the new WSL2 version.


My build toolchain is frequently in there for node based applications, and I was looking for a way to run docker commands from WSL (Windows Subsystem for Linux ).

Note: The below steps are a quick way to get it working but involves disabling TLS authentication. A more involved way to do this without disabling TLS can be found atย

This setup puts the docker engine in Windows on top of Hyper-V, but allows you to control it either from Windows, or within WSL by connecting it to the Windows Docker Engine.

  1. Install docker for windows
  2. Go into the Docker for Windows settings and expose daemon on localhost
    docker windows settings
  3. Install docker in WSL (it’ll just install the client)ย
  4. Tell WSL to look for a docker engine on localhost
    TIP: put the export into your ~/.bashrc so you don’t need to run it ever time.
    export DOCKER_HOST=tcp://

Now you will be able to run standard docker commands run new images, show the running containers, etc. docker linux