memoscan

0xf75b…cce8

All memos sent from and to 0xf75b…cce8.
0xf75b7857…cce8sent to0xe991247b…7677·#7,084,203·0xfabb14af…e16184
Ethereum main-net: will the Byzantium->Constantinople fork happen by the end of February 15, 2019 (UTC)?{"longDescription":"Whether the fork is \"successful\" or not (e.g., results in consensus failure between node implementations, for any reason) shall bear no weight on the outcome of this market.\n\nIt is only concerned with the time of the actual transition, in Coordinated Universal Time:\n\n* https://en.wikipedia.org/wiki/Coordinated_Universal_Time\n\nIf the set of changes proposed in the original Constantinople is split into several incremental upgrades, or altered in any way, then only the first scheduled set is to be considered by this market. What changes are included in the set bears no weight on the outcome.\n\nShould a contentious fork happen, resulting in two chains: Byzantium and Constantinople (for example, due to another potential vulnerability being published without sufficient time to postpone again), this market shall resolve as \"Yes\", provided both of the following conditions are met:\n\n- lasting for at least a thousand blocks on either side; and\n- at least 20% of total difficulty accrues on the Constantinople side, from the moment of the fork until time in title.\n\n-----\n\nPossible starting points for prospective reporters:\n\n* https://blog.ethereum.org/\n* https://www.parity.io/blog/\n* https://www.reddit.com/r/ethereum/search?q=constantinople&restrict_sr=on&sort=new\n* https://google.com/\n\n-----\n\nBack story:\n\nThe rule transition (network upgrade, fork) was scheduled to happen on block 7080000 (2019-01-17 05:57:13 +UTC):\n\n* https://etherscan.io/block/7080000\n\nIt was postponed due to a potential reentrancy vulnerability:\n\n* https://blog.ethereum.org/2019/01/15/security-alert-ethereum-constantinople-postponement/\n\nThe new block number, likely with a different set of changes than the original, will be decided in the coming days/weeks, starting with core devs call 53:\n\n* https://github.com/ethereum/pm/issues/70","resolutionSource":"","tags":["CONSTANTINOPLE","FORK"]}
0xf75b7857…cce8sent to0xe991247b…7677·#6,446,654·0x8ce23722…63982f
Ethereum Ropsten testnet: will the Byzantium->Constantinople fork happen on block 4200000?{"longDescription":"Backstory:\n\nhttps://www.reddit.com/r/ethereum/comments/9jo3y1/ropsten_constantinople_hard_fork_officially_set/\n\nWhether the fork is \"successful\" or not (e.g., results in consensus failure between node implementations, for any reason) shall bear no weight on the outcome of this market.\n\nIt is only concerned with the fork block number, as set in node implementations that take part in Ropsten.\n\nPossible starting points for prospective reporters:\n\n* https://blog.ethereum.org/\n* https://www.parity.io/blog/\n* https://github.com/ethereum/go-ethereum/\n* https://github.com/paritytech/parity-ethereum/\n* https://www.reddit.com/r/ethereum/search?q=ropsten&restrict_sr=on&sort=new\n* https://google.com/","resolutionSource":"","tags":["ROPSTEN","TESTNET"]}