Common Press Proposal: Cover DevCon 2 Sessions on Ethereum Security

Security on Ethereum

Day 2 of DevCon has several sessions dedicated to securing smart contracts and the dapps that use them. We would like to cover each session individually and write an overview article on Ethereum security. Our coverage for individual sessions will be geared towards helping developers identify informative segments or entire sessions that they should watch themselves. Our overview coverage will aim to spread the most valuable information about securing contracts to the entire Ethereum community.

Fund this Grant on Benefactory

Sessions

  • Panel: Smart Contract Security in Ethereum
  • Security learnings from BTC Relay
  • Visualizing Security
  • Ethereum Security Overview
  • Formal Verification for Solidity
  • Parity Dapp Security Infrastructure
  • Imandra Contracts: Formal Verification for Ethereum

Deliverables

We aim to publish a short article on each session in addition to our overview article by September 23, 2016, three days after the sessions. We hope to publish them as early as possible.

Team

  • Bill Gleim
  • Simon de la Rouviere
  • Rebecca Migirov
  • Joseph Chow
  • Andres Junge
  • Paul Kohlhaas

Cost

$500

Fund this Grant on Benefactory

Posted Sep 6, 2016, 5:44 PM UTC · edited

416
Anodigitalog•
2
[deleted]•

[removed]

1
natriusOP•

Here's the first contribution record. Instead of funding a DAO up front, we weave contributions into a commonwealth. Common Press starts here.

1
latetot•

I just made the second contribution- I'm wondering if people will be more willing to contribute for access once the articles / meeting is complete. But I guess the writers need an advance. We almost need a simple donation address to raise the $500- i'm worried the benefactory interface is still a bit too complex- does it work with Mist?

1
natriusOP•

Benefactory should work with Mist, but it's only been tested with Metamask. We talked with a few exchanges about reusing their DAO integrations for Benefactory, but they were built to handle one destination at a time (The DAO), not multiple grant destinations. We expect this to change as exchanges adapt to their additional role as an interface to add funds to dapps.

1
latetot•

Its strange that when you go to common press on benefactory, you dont even see the link to donate to this proposed grant- it only shows funded grants but that makes it harder to find this one and track its progress

1
natriusOP•

Good point! We're adding a feature that lets commonwealth forks list promising grants: grants they expect to include in the fork when the work has been completed. Commonwealths only include grants after the work has been completed.

Until then, r/Benefactory is the place to keep up with grant proposals. Come back tomorrow for another one!

1
cryptopascal•
1
natriusOP•

The math is correct, there's just a confusing distinction between pledges and actual contributions. We're going to redesign that concept.

2
latetot•

Is there any way to have the authors provide a Q&A session ? I think if they voiced their commitment to this more visibly they would raise the $500. - do you know if they have any plans? Thx

1
natriusOP•

Thanks for the suggestion! We're going to do more pushing next week so enough people are aware of the grant. This week's feedback has identified a few confusing aspects of the app that we want to simplify, and hopefully those fixes will be ready for next week.

1
cryptopascal•

My experience:

The contribution ID looks like a transaction ID but isn't (it's only an ID of a record in a contract probably?), this should be more clear to the user I think. Maybe mention it in the same sentence in the permalink, so people understand it better "This is your contribution ID - with it you can link to your contribution: http://www.benefactory.cc/grants/0x39590f0b13693aeb5e16a414be8ba28b4c382cc6/contributions/0xf7f73be4b48837d3eb9664e2f06bdaa76ff4c34237073c2ec6cd557e019f006a" or something similar.

The contributor address is not the original sending address but is a contract https://etherscan.io/address/0xdd88d2954c358781921f2642899a29098eb9bbd2 (point to improve: link to the address on a block explorer).

This is confusing. How do I control the contract? What is it for?

I just read in the getting started guide that the best way is to use MetaMask. Will do that next time, just wanted to report how an "innocent" browser user experiences it.

1
natriusOP•

Thanks for the helpful feedback! The contributor address is a contract on purpose. Contributions aren't transferrable, but the ecosystem will gradually move to more robust authentication mechanisms than a simple key, which is easy to lose. Benefactory accounts can be transferred to whatever authentication mechanism you want, and your contributions will still be attachd.

1
cryptopascal•

So in the background is a kind-of Uport-like proxy contract created that I am able to control by signing with the original sending externally owned account (as soon as there's an interface for that)?

1
natriusOP•

Exactly. Most Ethereum applications use transferable funds, but for applications like Benefactory that use non-transferable records, it's important that the identity itself be transferable. One day soon, there will be an ecosystem of identity managers that you can suck your Benefactory account into to use just like any other Ethereum account.

1
natriusOP•

Here's an early draft of summaries of the sessions. A final draft will be published in the coming weeks.

1