• Breaking News

    Monday, April 30, 2018

    Ethereum Vitalik Teases Sharding Release on Twitter

    Ethereum Vitalik Teases Sharding Release on Twitter


    Vitalik Teases Sharding Release on Twitter

    Posted: 30 Apr 2018 11:33 AM PDT

    Sharding is coming

    Posted: 30 Apr 2018 11:32 AM PDT

    On the next episode of Silicon Valley: Pied Piper Coin & it's upcoming ICO

    Posted: 29 Apr 2018 10:54 PM PDT

    Open Source Money will BUIDL the Open Source Ecosystem - Gitcoin Vision Piece

    Posted: 30 Apr 2018 11:08 AM PDT

    Ethereum smart contract security analysis - detecting batchOverflow and similar flaws

    Posted: 30 Apr 2018 10:50 AM PDT

    Ethereum, Swarm, Whisper Reference App

    Posted: 30 Apr 2018 01:55 PM PDT

    Is there a reference app (or toy app that demonstrates how something works) that uses the Ethereum's 'Holy Trinity'? I understand that Swarm and Whisper are alpha only, but I would like to see if someone has put together an example how these three components would work together.

    submitted by /u/kirakun
    [link] [comments]

    district0x Quarterly Report - Q1 2018

    Posted: 30 Apr 2018 09:15 AM PDT

    Kyber Network - A Letter From The CEO

    Posted: 30 Apr 2018 05:20 AM PDT

    First open source winery selling wine with a cryptoasset on eth!

    Posted: 30 Apr 2018 10:35 AM PDT

    The Kleros Ecosystem: the Future of Decentralized Arbitration

    Posted: 30 Apr 2018 09:56 AM PDT

    Enter Cellarius, a Transmedia Universe 100 Years in the Future

    Posted: 30 Apr 2018 11:17 AM PDT

    Announcing the Dharma Protocol Public Bug Bounty: Earn up to 50,000USD for critical exploits

    Posted: 30 Apr 2018 11:59 AM PDT

    Ethereum [ETH] Foundation developer unveils a proposal for a smart contract insurance pool

    Posted: 30 Apr 2018 07:15 AM PDT

    UNICEF Is Mining Digital Currency As a Donation For Children

    Posted: 30 Apr 2018 07:48 PM PDT

    A take on a simple ETH recovery fund/dao

    Posted: 30 Apr 2018 10:30 AM PDT

    Alex Van de Sande made a recent contribution to the idea of a non-fork solution for recovering ETH lost to bugs like the Parity multi-sig issue. His article followed a number of other notable ideas from the community. I had some code that was already quite similar to some of these so I've repurposed it as a first pass at what could constitute a recovery fund/dao. Part of Alex's suggestion is for the fund to provide future insurance. This use-case would likely mean that the related token be regarded a security token. As that may complicate participation the project could be pursued in two stages - basically insurance could be added as a module at a later date.

    Project Stages

    • Stage 1: goal only to restore as much ETH as possible to those who lost it. not a security token.
    • Stage 2: add insurance module. likely becomes security token.

    The current contracts attempt to achieve Stage 1 with the following basic outline:

    • Two tokens
      • Voting and non voting (REEV & REE)
      • Each equal claim to backing ETH (either can burn to claim portion of backing ETH at any time)
    • Voting/DAO contract
      • controls each token - can mint/burn from each
      • accepts ETH to award voting REEV 1:1
      • props are added along with a 1 REEV stake which is burned if the prop fails
      • props pass with 2/3 token vote after PROP_DURATION and any PROP_CLOSE_FLIP_DELAY
      • vote duration is extended by PROP_CLOSE_FLIP_DELAY if the result flips within PROP_CLOSE_DURATION before the end of the vote
      • prop actions are NONE, UPGRADE, ENDOW_REE, ENDOW_REEV
      • passing props can be enacted after ENACT_DELAY (stakeholder can withdraw in the case of vote abuse)

    The use of two tokens is a simplification over Alex's suggestion to have separate tokens for different classes of ETH losses. REEV holders (bought 1:1 for ETH) would vote for who to allocate REE to, but both would have claim to the ETH held in the contract. Of course any REEV holders who vote to allocate REE would be dilluting their own claim to the backing ETH but they would be free to exit with their current share at any point. The point I guess is to provide something as a target for socializing these losses as well as something that could be built on in the future (insurance).

    submitted by /u/carlslarson
    [link] [comments]

    Clear Regulations Result in High Volumes of Crypto Trading, According to Morgan Stanley

    Posted: 30 Apr 2018 11:40 AM PDT

    Profit Trailer 2.0: An Honest Review You Won't Get Anywhere Else.

    Posted: 30 Apr 2018 04:55 PM PDT

    Decentralized Database Bluzelle is building Ethereum Integration

    Posted: 30 Apr 2018 01:09 AM PDT

    Let's try this experiment: refer to @EthereumLive when announcing Ethereum-related live streams on Twitter

    Posted: 29 Apr 2018 11:15 PM PDT

    Building an invite list for a new chat group only for community resource creators

    Posted: 30 Apr 2018 09:24 AM PDT

    we're putting together an invite list for people that create resources for the community. if you have a blog or a youtube channel or a website or something else, shoot me a DM. let me know who you are, and send me a link to your stuff or site.

    the community won't be a business, we arent looking to monetize anyone. just a way for positive creators to connect. if you pitch scams or sell reviews, please do not waste your time or mine.

    my site is ConcourseQ.io

    submitted by /u/scott_lew_is
    [link] [comments]

    Panmunjom Declaration for Unification of the Korean Peninsula on Ethereum smart contract

    Posted: 30 Apr 2018 05:29 AM PDT

    I created a simple Ethereum smart contract to store the Panmunjom Declaration for Peace, Prosperity and Unification of the Korean Peninsula which was adopted between leaders of North Korea and South Korea on April 27, 2018, during the 2018 inter-Korean Summit.

    You may use Google translator to use the site. Please leave your comments on Ethereum.

    Main Site: https://panmunjom.github.io/

    Contract Address: https://etherscan.io/address/0xdc7c743110Ec689d82f050302319AE27aF84f8fa

    Site source: https://github.com/panmunjom/panmunjom.github.io/blob/master/index.html

    About the declaration: https://en.wikipedia.org/wiki/Panmunjom_Declaration

    submitted by /u/atomrigs
    [link] [comments]

    OpenLaw Development Update (4/30/2018)

    Posted: 30 Apr 2018 11:21 AM PDT

    Quick question regard how the blocks work

    Posted: 30 Apr 2018 01:17 PM PDT

    From my understanding, a block is defined at a mined time. Therefore the transactions are not logged before it is found, however, there is being written into the block start 1 sec to 12 sec.

    Why is it not an incremental release of the block to give "acceptance" throughout a block time instead of them being released?

    submitted by /u/qqAzo
    [link] [comments]

    No comments:

    Post a Comment