Decentralised Applications Engineer #blockchains #ethereum #DAOs #identity #p2p
Blockchain
Joined August 2014
- Tweets740
- Following175
- Followers683
- Likes725
d11e9.eth retweeted
You’ve heard of zero-knowledge proofs.
You’ve heard of SNARKs and PLONK and zkRollups.
But you haven't gotten started, because you don’t have a spare brain dedicated to learning cryptography.
That all changes today.
Introducing Noir, the universal language of zero knowledge.
d11e9.eth retweeted
On April 1, 2019 we are going to shut down our cluster and all access to centralized services for 24h. Learn why in @oskarth blog post below
d11e9.eth retweeted
ERC-1724 - zkERC20: Confidential Token Standard
A common interface for fungible tokens that want to implement confidential transaction functionalities via zero-knowledge proofs and a corresponding Cryptography Engine (see ERC-1732).
github.com/ethereum/EIPs/iss…
There goes #Immutability ... again. #jk
This quoted post is unavailable.
d11e9.eth retweeted
A zero knowledge DAI implementation working live on the main chain: github.com/AztecProtocol/AZT…
Programmable, private, stable. We're slowing approaching the holy grail of currencies.
d11e9.eth retweeted
Seriously, no one wants a single digital identity except the people selling solutions designed for that purpose.
People want easy-to-use tools to manage their digital relationships in a safe, secure and privacy-preserving manner.
Why does everything have to be "revolutionary?"
3/3. We could make ^identity^ cards and tokens much easier to use if we attended to the UX, without artificially merging, complicating and ruining what are actually disparate relationships. I don't see the time-has-come-need for a single Digital ID. #futureofdigitalidentity
d11e9.eth retweeted
Thanks @Bloomberg for breaking the news about Erasure today and for this great keyboard bloomberg.com/news/articles/…
d11e9.eth retweeted
I was having a call with a group that wanted to make contract development easier but were really struggling how to, so the next day I got back to them with a suggested layout of how I would approach it, focusing on modules instead of directly writing code line by line.
