|
So tense...im feeling a dump btw...why rush to buy in last few hours...
I think dump, its one last chance for a shake out, then within next day or two...boom back up
|
|
|
|
 if btc dumps anytime in within next 24/48hours, it will be a huge dump...40%-60% is possible...ETH will double up instantly....those that miss buying ETH now will buy dao as it will give back 10/1 ratio to ETH. Dao has become a second chance for those that dumped ETH and miss the train when it takes off.
|
|
|
|
OMFG I can't believe this is really halvening! im surprised most of us are all still alive and here,lol the amount of emotions we have went through coz of crypto...no average person could handle it,lol The cake is real...the cake is real....  |
|
|
|
ahh gd luck troll is back..  |
|
|
|
Great article http://hackingdistributed.com/2016/07/05/eth-is-more-resilient-to-censorship/We received many notes of support from the community. A very human, but completely flawed, response would have been to deny the problem, to minimize its potential severity, and to attack the researchers. In contrast, the Ethereum community has been amazingly science-driven, open and forthright. The civilness of their response should be a shining example to other communities. We are greatly encouraged by the Ethereum community, happy to have helped avert a potential disaster, and even happier to have stumbled onto an accidental but turns-out-to-be fundamental property of Ethereum, namely, that it is resilient to censorship, even by a majority of its miners. |
|
|
|
http://www.ethereum.net/news/technology/international-blockchain-week-devcon2-announcedDuring the first three days, from September 19th-21st, DEVCON2 will allow attendees the chance to discover more on Ethereum’s research, development and security, as well as DApps. Guests will also be treated with a special presentation from the event’s Premiere Sponsor, Microsoft , which will highlight more details on their Ethereum-based project, Azure. https://www.reddit.com/r/ethereum/comments/4rhac3/international_blockchain_week_and_devcon2_details/vbuterinJust some guy 1 point 11 minutes ago A website with much more detail dedicated to the devcon2 segment will be coming very soon; however, individuals interested in attending the whole week can definitely go through http://blockchainweek2016.org to buy the whole week pass for $1500 (NOTE: if you are a developer or student you may qualify for the developer/student discount for the devcon2 segment, in which case even if you want to attend for the whole week, registering for the devcon2 segment through the upcoming foundation website separately will still be a better deal for you). Anyone interested in speaking should obviously contact us, though I will warn that the schedule is >80% full already.
|
|
|
|
https://www.reddit.com/r/ethereum/comments/4r9yud/the_current_hf_status/1) The implementation has been largely spec-frozen to the following python: # call before running transactions def initialize(): if state.block_number == DAO_HARDFORK_BLKNUM: for acct in HARDFORK_DAO_LIST: state.set_balance(HARDFORK_DEST, state.get_balance(acct) + state.get_balance(HARDFORK_DEST)) state.set_balance(acct, 0) However, the dev community is debating the simplest way to minimize risks of issues related to light client syncing. The actual logic that allows DAO token holders to claim their ether would be implemented in HARDFORK_DEST. 2) The ether claiming logic is largely a simple withdrawable token contract, but small details are being debated regarding how to deal with secondary daos, legit splits, etc. Note that this can proceed in parallel to (1), there are no sequential dependencies. Simplicity of the ether claiming contract is understood to be a very important concern. 3) Note that the above should absolutely not be taken as an official endorsement of hardforking by either the foundation, or ethcore/slock/string, or the individual devs involved; some of the devs involved are pro-fork and some are anti-fork, the goal is to give the community a choice. thanks for all the great posts mrpumpitis. I cant believe there is still question on HF. seems like its a no brainer. Stealing shouldn't be rewarded even if done under guise of smart contract glad u like them m8, totally agree with you. Good to see things are moving forward well. Heres another post from the REEBOK story, well written and good info... http://coinjournal.net/ethereums-blockchain-secure-sneakers-honor-kanye-west/ "The antenna inside will break if a tag is removed, so a smart tag cannot be removed and then placed on a counterfeit item.” This got me thinking, i know ladies that have paid $1000+ for Gucci handbags on places like craiglist, im convinced the seller is selling a fake,lol if the bags ( or any other item ) had these tags inside they would be easy to verify if they are the real deal...This could be real good tech for the big names in the fashion industry. |
|
|
|
https://www.reddit.com/r/ethereum/comments/4r9yud/the_current_hf_status/The Current HF Status
submitted an hour ago by vbuterin1) The implementation has been largely spec-frozen to the following python: # call before running transactions def initialize(): if state.block_number == DAO_HARDFORK_BLKNUM: for acct in HARDFORK_DAO_LIST: state.set_balance(HARDFORK_DEST, state.get_balance(acct) + state.get_balance(HARDFORK_DEST)) state.set_balance(acct, 0) However, the dev community is debating the simplest way to minimize risks of issues related to light client syncing. The actual logic that allows DAO token holders to claim their ether would be implemented in HARDFORK_DEST. 2) The ether claiming logic is largely a simple withdrawable token contract, but small details are being debated regarding how to deal with secondary daos, legit splits, etc. Note that this can proceed in parallel to (1), there are no sequential dependencies. Simplicity of the ether claiming contract is understood to be a very important concern. 3) Note that the above should absolutely not be taken as an official endorsement of hardforking by either the foundation, or ethcore/slock/string, or the individual devs involved; some of the devs involved are pro-fork and some are anti-fork, the goal is to give the community a choice.
|
|
|
|
|
Show Posts
