FAQ Go Ethereum

EIP-1559 Grant - Please participate and spread the word!

EIP-1559 grant - Help to develop it sooner
Hey guys,
It would be great if all of us collaborate, even a little amount can make a difference. And if they see a lot of participants, EF will see that this EIP is really important.
It will have a tremendous positive impact in the future.
submitted by PlanetaOTC to ethereum [link] [comments]

Doubts about staking with DAppNode

Hi everyone!
I am getting ready to participate to the Medalla testnet and I want to try different setups to test my comfort zone with eth2 staking.
I have an Intel NUC and I have installed DAppNode from the ISO on it. It is very easy to use and setup everything, but I have grown uncomfortable with some points for which I would like to have advices or know other opinions:
1) The installation guide suggests to keep the root password blank. Is that 100% safe? Is there something I can do/check for increased safety?
2) I have accessed the server from Windows with putty, logging in with the user created during the installation phase, however I couldn't find anything related to the ethereum networks I am synchronizing (geth for the main network, and göerli testnet). Are these in the root user folder? I am uncomfortable with not knowing where everything is stored.
3) In general it is not clear to me if using DAppNode means having less "direct" control on your data, i.e. if for some tasks you need to use the UI through the VPN or if you can completely bypass it if you want for a specific task at some point. This is also partially related to the non-zero risk that at some point in the future DAppNode could be discontinued or lacking support. I understood that if I uninstall it all data will be erased.
In general I am very curious to know how other users feel about staking with DAppNode!
submitted by Ningia to ethstaker [link] [comments]

RiB Newsletter #15 – Turbofish in the Blocksea

Rust blockchain development continued at its typical blistering pace, and again it's impossible to follow everything going on.
This month we see continued advancement in zero-knowledge computing, an obvious focus from the entire blockchain industry on the DeFi phenomenon, and some new hackathons with opportunities for Rust developers.
Every month seems to bring advancements in zero-knowledge proofs, and new implementations in Rust. It is a research area that will probably impact the general computing industry eventually, and one where the blockchain industry is leading the way, and one where Rust has a huge foothold. Even projects that are not written in Rust we see implementing their zero-knowledge cryptography in Rust. But this stuff is extremely technical, and improving at a rapid pace. We fear we will never understand it.
There are several Rust blockchains now in development that are built around zero-knowledge VMs, whose smart contracts create zero-knowledge proofs:
These are networks that support nearly arbitrary computation over secret inputs. Like programable Zcash.
Speaking of Zcash, the zkSNARK pioneers announced their next-generation zero-knowledge proof system, called Halo 2, which uses a new zkSNARK construction, PLONK.
Two projects built on Rust blockchains launched this month: Serum, a decentralized exchange built on Solana; and Flux, a prediction market built on NEAR. Next month Secret Network launches their mainnet.
Finally, Mozilla laid off all but one of its full-time Rust employees. There are a few other people left at Mozilla who actively contribute to Rust as part of their role in Firefox, but this mostly ends Mozilla's commitment to Rust's development.
There's no need to worry though. Rust was designed to outlive Mozilla's withdrawal, and the project will continue nearly unaffected.

Project Spotlight

Each month we like to shine a light on a notable Rust blockchain project. This month that project is…
This is a blockchain with built-in software license management. We’re excited about this because license management is a rare non-currency use case for blockchains that makes a lot of sense. While we might expect to see more blockchain platforms devoted solely to digital licensing, fluence is actually a complete distributed computing platform, with a unique vision about using license management to generate profit from open source software.

Interesting Things


Blog Posts



Podcasts and Videos

Read more: https://rustinblockchain.org/newsletters/2020-09-02-turbofish-in-the-blocksea/
submitted by Aimeedeer to rust [link] [comments]

Just syncing...

Just posting it here for those who want clarification on which sync mode to run. I am prepping for the Phase 0 mainnet launch and we are talking about gigs of data. I intend to run an ETH1 node along with my Beaconchain node + validators. Hoping that this will save others the time on fact finding. This is OG knowledge after all and I am a newbie at best in comparison to many.
But first...
Guy on troubled boat: We are sinking.
Coastguard: What are you syncing about?

To clarify the differences on different sync modes...
According to: https://ethereum.stackexchange.com/questions/11297/what-is-geths-light-sync-and-why-is-it-so-fast
"Full" Sync: Gets the block headers, the block bodies, and validates every element from genesis block.
Fast Sync: Gets the block headers, the block bodies, it processes no transactions until current block - 64(*). Then it gets a snapshot state and goes like a full synchronization.
Light Sync: Gets only the current state. To verify elements, it needs to ask to full (archive) nodes for the corresponding tree leaves.

EDIT: Forgot to add this. The terminal command would look like -
geth --syncmode value
Where value is the Blockchain sync mode ("fast", "full", or "light") (default: fast)
You can also add destination directory with --datadir, e.g.:
geth --syncmode value --datadir="$HOME/ETH-mainnet"
which puts the chain data into a folder called "ETH-mainnet" in your home directory.
Want to save space on your precious SSD and save the old chain entries onto a separate HDD? You now can do this with:
--datadir.ancient value
where value is the data directory for ancient chain segments (default = inside chaindata).
So if I was to put it all together:
geth --syncmode full --datadir="$HOME/ETH-mainnet" --datadir.ancient /mnt/FatHDD/ETH-old
where "/mnt/FatHDD" is the mount point of the hard disk drive and we are storing it within the "ETH-old" folder.
Just syncing out loud... (OK that's the last one).
submitted by Rayblox to ethstaker [link] [comments]

Ethereum on ARM. Ethereum 1.0/2.0 ecosystem installation on Ubuntu server 64bit for Raspberry Pi 4 (step by step guide) - Join ETH 2.0 testnets through Prysm / Lighthouse clients on RPi4. Memory enhancements

Ethereum on ARM is a project that provides custom Linux images for Raspberry Pi 4 (Ethereum on ARM32 repo [1]),NanoPC-T4 [2] and RockPro64 [3] boards (Ethereum on ARM64 repo [4]) that run Geth or Parity Ethereum clients as a boot service and automatically turns these ARM devices into a full Ethereum node. The images include other components of the Ethereum ecosystem such as Status.im, Raiden, IPFS, Swarm and Vipnode as well as initial support for ETH 2.0 clients.
Images take care of all necessary steps, from setting up the environment and formatting the SSD disk to installing and running the Ethereum software as well as synchronizing the blockchain.
All you need to do is flash the MicroSD card, plug an ethernet cable, connect the SSD disk and power on the device.

The what and why of a 64 bits Raspberry Pi 4 image, 32 vs 64 bits

Following my last post [5], there are a couple of ongoing issues with the Raspberry Pi 4 that prevent Ethereum software to run as expected.
Given the massive adoption of the Raspberry Pi device, a 64 bit image would allow users to run full nodes without RAM issues and join ETH 2.0 testnets. While Raspbian certainly has a plan to migrate the OS to a full 64bit image there is not an official statement or roadmap about this. In the meanwhile, as ETH 2.0 phase 0 is around the corner, it is worth to try to find a viable alternative to run a 64bit OS on the Pi.

Installation of an Ubuntu server 64bit image for the Raspberry Pi 4 with Ethereum 1.0/2.0 ecosystem. Step by step guide.

James Chambers released an 18.04 Ubuntu server 64 bit image for the Raspberry Pi 4 using the latest Raspbian and the official 19.04 Ubuntu images [7] (amazing job, by the way). Obviously, this is work in progress, has no official support and is not considered stable. But it runs reasonably well and, as stated before, a native 64 bits image opens the door for joining the ETH 2.0 public test networks for Raspberry Pi 4 users as well as solving the 32 bits “out of memory” RAM issues. So it is worth it to give it a try.
DISCLAIMER: As this is a handcrafted image the installation it is not Plug and Play like the stable Ethereum on ARM images so you will need some Linux skills here. I tried to make the process as straightforward as possible though (it should take just 10-15 minutes).
The installation procedure has two main steps.
  1. Install Raspbian, needed to update the raspberry pi 4 to the latest (unstable) available firmware and format the USB disk
  2. Install Ubuntu 64 bits, to have a system with a 64 bit kernel and user space
DISCLAIMER: In this step we’re going to update the firmware to the latest unstable version. It can break things and even make the Raspberry Pi unbootable (not likely at all, but possible), so, be careful here.
Prerequisites: Make sure you have the USB disk attached (blue USB port) and the network connected to the RPi 4.
1. In your Linux desktop: Open a terminal, download the Raspbian image, insert the MicroSD and flash it:
wget https://downloads.raspberrypi.org/raspbian_lite/images/raspbian_lite-2019-09-30/2019-09-26-raspbian-buster-lite.zip unzip 2019-09-26-raspbian-buster-lite.zip sudo dd bs=1M if=2019-09-26-raspbian-buster-lite.img of=/dev/mmcblk0 conv=fdatasync status=progress 
2. In your Raspberry Pi 4: Insert the MicroSD, boot up and log in (user:pi password:raspberry). Keep in mind that ssh is not enabled by default so you will need a monitoTV and a keyboard. Download Ethereum on ARM setup script to update the Firmware and format the USB 3 disk.
wget https://github.com/diglos/pi-gen/raw/ethraspbian2.0/stage2/04-ethereum/files/ethonarm-rpi4-ubuntu64bit-setup.sh sudo sh ethonarm-rpi4-ubuntu64bit-setup.sh 
  1. Power off the Raspberry and extract the MicroSD again.
1. In your Linux desktop: Insert the MicroSD. Open a terminal, download James Chambers Ubuntu image and flash it:
wget https://github.com/TheRemote/Ubuntu-Server-raspi4-unofficial/releases/download/v26/ubuntu-18.04.3-preinstalled-server-arm64+raspi4.img.xz xz -d ubuntu-18.04.3-preinstalled-server-arm64+raspi4.img.xz sudo dd bs=1M if=ubuntu-18.04.3-preinstalled-server-arm64+raspi4.img of=/dev/mmcblk0 conv=fdatasync status=progress 
2. In your Raspberry Pi 4: Insert the MicroSD, boot up and log in (user:ubuntu password:ubuntu). You will be prompted to change the password so you’ll need to log in twice. SSH is enabled by default.
Download the install script and run it:
wget https://github.com/diglos/pi-gen/raw/ethraspbian2.0/stage2/04-ethereum/files/ethonarm-rpi4-ubuntu64bit-install.sh sudo sh ethonarm-rpi4-ubuntu64bit-install.sh 
4. Reboot the Pi and you will be running a full ETH 1.0 node / ETH 2.0 test client on a native Ubuntu server 64bit OS. Keep in mind that Geth and Status run by default so if you don’t want to run a full Ethereum node or a Status node you need to stop and disable them by running:

ETH 2.0 testnets on Raspberry Pi 4

Prysm and Lighthouse latest versions are now available so you can join/test the ETH 2.0 implementations with your Raspberry Pi 4:
Prysm 0.3.1: Take into account that at the time of writing this post, the sync process is very slow, see [8]. The packages provides 2 binaries: beacon-chain and validator.
Follow the instructions [9] to join the test network. Basically, get the Goerli ETH (no real value), set the validator password and run both clients. Once you have done all required steps and make sure everything goes as expected you can edit the file etc/ethereum/prysm-validator.conf and define the password previously set in order to run both clients as a systemd service:
sudo systemctl start prysm-beacon sudo systemctl start prysm-validator 
For more information about joining the Prysm testnet check the official docs [10]
Lighthouse 0.1.1: Currently provided as a single binary (no systemd service): lighthouse.
Lighthouse team is doing a fantastic progress as well [11] so expect news regarding the testnet soon. You can check their official documentation here [12]
ETH 2.0 is under heavy development right now [13] so I will be providing clients updates as soon as they are released. You can update the Eth 2.0 clients anytime by running:
sudo apt-get update && sudo apt-get install prysm-beacon prysm-validator lighthouse 
If you have the time and the skills to install the image and join the ETH 2.0 testnets, please do. It is a very valuable feedback for all teams involved, particularly at this early stage.

Memory and cache tweaks

Working on enabling swap memory for the Ubuntu 64bit image I realized that Armbian developers put a lot of work trying to maximize the memory usage on these kind of boards [14]. This is something really important with such a limited resource as it needs to be as much efficient as possible (try to avoid "out of RAM" crashes and don’t waste too much CPU as well as disk throughput in swap tasks).
Particularly, I focused on 2 tasks:
I encourage users to test these parameters and try to find the best combination in order to achieve better sync results. I'm currently running several test on the Rpi4 in order to find an optimal setup.
On top of this, I also ran some tests with the NanoPC (in this case, lowering a little the default Geth cache to 768) that resulted on Sync time improvements:
NanoPC-T4 Fast Sync data


  1. https://github.com/diglos/pi-gen
  2. https://www.friendlyarm.com/index.php?route=product/product&product_id=225
  3. https://store.pine64.org/?product=rockpro64-4gb-single-board-computer
  4. https://github.com/diglos/userpatches
  5. https://www.reddit.com/ethereum/comments/eehdjq/ethereum_on_arm_raspberry_pi_4_out_of_memory/
  6. https://github.com/ethereum/go-ethereum/issues/20190
  7. https://jamesachambers.com/raspberry-pi-4-ubuntu-server-desktop-18-04-3-image-unofficial/
  8. https://github.com/prysmaticlabs/prysm/issues/4508
  9. https://prylabs.net/participate
  10. https://prysmaticlabs.gitbook.io/prysm/how-prysm-works/overview-technical
  11. https://lighthouse-book.sigmaprime.io/intro.html
  12. https://twitter.com/paulhaunestatus/1217349576278999041
  13. https://blog.ethereum.org/2020/01/16/eth2-quick-update-no-7/
  14. https://forum.armbian.com/topic/5565-zram-vs-swap/
submitted by diglos76 to ethereum [link] [comments]

Plasma Update March 26, 2019

The past two weeks have largely been spent on closing out a bunch of feature work as well as some clean up. For the feature work, we’ve finished up development on:
During this validation phase of our internal alpha testnet, we’ve learned a lot about how the system runs over a longer period of time. We’ve run into some availability issues related to syncing with geth, the first Ethereum client we integrated with. We’ve spent a lot of effort refactoring the services to be more fault tolerant of geth crashes and have continued to improve syncing. Additionally, in the interest of consistent availability, we’ve added parity support for our services so that we can work towards redundancy in case one node fails.* In pursuit of our commitment to providing our integrators and partners a reliable service, we’ll be continuing this resiliency and availability work in the upcoming iterations.

*For those who are not familiar, geth and parity are the two leading Ethereum clients, which allow users to interact with the Ethereum chain. Different clients are often written in different languages and offer different features; building for multiple clients means extra work but provides greater resiliency in case one client has issues.
submitted by omise_go to omise_go [link] [comments]

Plasma Update #13 - February 11, 2019


The big news in the wider world of plasma research was Plasma Group’s first official announcement, accompanying the release of a “toolbox for deploying, transacting on, building with, and developing on plasma chains.” They’ve spent the months since DevconIV putting together a Plasma Prime testnet (for anyone who doesn’t know, Plasma Prime is an iteration on the Plasma Cash design) and tools to help interested developers either interact with or deploy their own plasma chains.
Another cool thing here - in anticipation of a future where many plasma chains coexist, they’ve created a registry, where trusted deployment is verified via a contract so that users can be sure that funds are safe on the chain they’re using.
Plasma Group has published a thorough writeup of the design here: https://medium.com/plasma-group/plasma-spec-9d98d0f2fccf


We’re considering our current testnet, which has been running on Rinkeby since December, a release candidate of the OMG Network. We’ve been happy with the network’s performance over the last couple of weeks. We’ve merged the initial updates to omg-js and have been testing these to ensure that things are going smoothly. We found and fixed a handful of bugs in the process, including addressing exceptions from the watcher when geth crashes, mitigating those crashes, and various improvements in syncing with geth.
Development continues on in-flight exits for ERC-20s and transaction metadata support. We also had some housekeeping to do, updating Elixir and our Exthereum dependency (Exthereum is an Ethereum client written in Elixir). To support testing in this phase, we’ve made it easier to adjust exit period times during deployment.
We are excited eager preparing with zen-like composure to get wider involvement in testing in the coming weeks.
submitted by omise_go to omise_go [link] [comments]

Ethereum Istanbul Hard Fork 2019 - Latest Updates on Changes Approved

Ethereum Istanbul Hard Fork 2019 - Latest Updates on Changes Approved
The developers of Ethereum have finally approved six codebase modifications (also known as Ethereum Improvement Proposals or EIP) for the backward-incompatible Istanbul hard fork. Istanbul Hard Fork will be activated in two different stages- the first stage will be implementing six EIPs, and the second phase will be implementing two major EIPs, which will happen in Q1 2020.
The Core Developer of the Istanbul upgrade project, Peter Szilagyi on the two-part Istanbul structure:

Let us understand these two phases in details:

#1 First Stage

The first stage will be the eighth hard fork for Ethereum blockchain after the Constantinople hard fork, and the third upgrade in the Metropolis Version 1.3. Initially, the original date in the Ropsten testnet was August 14, but it got pushed as the developers needed time to finalize the EIPs. The major Ethereum clients Geth and Parity have only one week to integrate six EIPs (discussed below) and prepared to implement the new code in a testnet.

Tentative Istanbul Hard Fork Date (Stage 1)

As of now, September 4, 2019, has been considered by the core developer, Peter Szilagyi, which he thinks might get postponed once more and the ETH mainnet execution can happen in October. The other developers agreed that the block number and the targeted activation date could be determined in the next week in a meeting as per Istanbul hard fork news. The activation of the first phase will be the last important milestone before the activation of the mainnet.

EIPs To Be Implemented

You can refer here for the updates in the six EIPs to be decided, as they keep on getting withdrawn and updated as per the developers.
Two months back, the developers agreed on two EIPs out of thirty- EIP 2024 and EIP 1702:
EIP 2024: Add new pre-compiler for Blake2 to optimize the blockchain operations and make transactions less costly.
EIP 1702: Focused on smart contract optimization, created by Wei Tang, a developer at Parity Technologies.

Aimed Upgrade

This stage is focused on increasing the compatibility of the Ethereum blockchain with the Zcash network, which will enhance the platform’s chain interoperability with the privacy coin. It is aimed at securing the network from replay attacks (duplicate transaction attacks), which will increase efficiency.
Like any other ETH hard fork with the Istanbul hard fork update, the miners must upgrade simultaneously causing a chain split in the network.

#2 Second Stage

The second stage will be the last hard fork before its transition to Version 2.0. This is scheduled for mainnet activation and will feature two big EIPs, which require much detailed testing and deliberation from the developers.
Istanbul hard Fork Date (Stage 2) : Q1 2020

EIPs To Be Planned

To Be Decided. The tentatively decided EIPs are mentioned here.

Aimed Upgrade

They are going to include Programmable Proof of Work (ProgPoW), a new kind of mining algorithm designed to close the efficiency gap available to the specialized ASICs.
Hudson Jameson, Ethereum Foundation Community Manager, said :
We will keep on adding more information as and when it is updated.
Article Source - https://coinswitch.co/news/ethereum-istanbul-hard-fork-2019-latest-updates-on-changes-approved
submitted by perky_coder to coinswitch [link] [comments]

Daily analysis of cryptocurrencies 2019-11-17(Market index 38 — Fear state)

Daily analysis of cryptocurrencies 2019-11-17(Market index 38 — Fear state)


Ethereum’s Harmony To Not Support Upcoming Istanbul HardforkIn more recent updates, Ethereum’s Tim Beiko took to Twitter to elaborate on the developments that took place in the Ethereum Core Devs Meeting 75. After the release of several versions of Nethermind, Besu, and Geth, Parity v2.5.10-stable and v. 2.6.5-beta were the latest versions to be released. The release would add block numbers for the activation of the Istanbul hardfork on the mainnet along with other updates. Along with the latest versions of Parity, Aleth 1.7.0 was also released which Focus on on EIPs for the Istanbul hardfork. While the developers urged the community to update their nodes, Beiko revealed that only 16% of nodes were updated.
Swiss Capital Markets And Tech Association To Publish Common Standards For Safe Custody Of Digital AssetsThe Capital Markets and Technology Association (CMTA), an independent Swiss association bringing together actors from Switzerland’s financial, technological and legal sectors, will publish common standards for the safe custody of digital assets. CMTA is currently consulting its members on proposed standards for the safe custody of digital assets by professional financial intermediaries.
Santander Says It Will Soon Expand Its Use Of Ripple’s Cross Border Payments PlatformAccording to The Daily Hodl, in a recent conference held by the Institute of International and European Affairs, managing director of digital investment banking at Santander, John Whelan, talked about the company’s efforts in blockchain. He says the company will bring its Ripple-powered payments platform called One Pay FX to all 10 of its main corridors in the near future.“We actually have a blockchain-based international payments system that’s running on four of our corridors: Brazil, Mexico, UK, Spain. It will be on all 10 soon. Instant transfers at very, very tight spreads: 30 basis points. It’s a nice user experience. I use it myself. I sent money to the United States. It’s available same-day.”

This past week, bitcoin saw an increase in selling pressure below the $8,880 support area against the US Dollar. Moreover, BTC price settled below the $8,700 pivot level and the 100 simple moving average (4-hours).
There were steady losses and the price broke the $8,600 and $8,500 support levels. A new monthly low is formed near $8,382 and the price is clearly trading in a bearish zone.
It is currently consolidating losses above the $8,400 level. Besides, bitcoin is trading near the 23.6% Fib retracement level of the recent decline from the $8,777 high to $8,382 low.
Review previous articles: https://medium.com/@to.liuwen

Encrypted project calendar(November 17, 2019)

OKB (OKB): 17 November 2019 OKEx Talks — Lagos Join us on 17 Nov for another OKEx Talks, discussing the “Life of a Crypto Trader”.BitCash (BITC): 17 November 2019 BitCash Gold Hard Fork We will introduce a third currency on the BitCash blockchain with BitCash Gold. BitCash Gold is pegged to the price of gold.EDC Blockchain (EDC): 17 November 2019 Blockchain Seminar “On November 17th, 2019, we invite you to visit the EDC Blockchain seminar in Surabaya, East Java, Indonesia. “Chainlink (LINK): and 1 other 17 November 2019 Joint Meetup This Sunday, Our @EmmaUltrain and @chainlink will co-host a meetup to discuss blockchain technology development in Beijing!!EOS (EOS): 17 November 2019 Hackathon “Do you want to build on #EOSIO? @LiquidAppsIO community #DAAPHackathon begins 8pm Sunday CST.”Enjin Coin (ENJ): 17 November 2019 Live Stream “Tune in for a stream of @ForgottenArtif with developer @CliffCawley and get a preview of the next game update along with…”

Encrypted project calendar(November 18, 2019)

Maker (MKR): 18 November 2019 MCD Launch “BIG changes to terminology are coming with the launch of MCD on Nov. 18th Say hello to Vaults, Dai, and Sai.”Vexanium (VEX): 18 November 2019 Nodes Blockchain Summit Vexanium will collaborate with Nodes Community to hold a blockchain conference called the Nodes Blockchain Summit.OKB (OKB): 18 November 2019 Utrecht Workshop “EVENT: We’re going back to basics with #101 workshops on #CryptoTrading in Utrecht & AmsterdamSantiment Network Token (SAN): 18 November 2019 Reddit AMA “…@Santimentfeed will be conducting its first Reddit AMA on the@EthfinanceRsubreddit on Monday, November 18, 2019 from 12pm to 3pm EST”.Decentralized Currency Assets (DCA): 18 November 2019 Added to Echoestrader “Decentralize Currency Assets(DCA) support’s the first crypto algorithm exchange goes live on november 18th 2019.”Aeternity (AE): and 5 others 18 November 2019 [TWITTERPOST] Shift Money 2019 conference from Nov 18–19 in Croatia.Maker (MKR): 18 November 2019 MCD Launch “BIG changes to terminology are coming with the launch of MCD on Nov. 18th Say hello to Vaults, Dai, and Sai.”Pundi X (NPXS): 18 November 2019 Binance Italian AMA “On November 18 at 3:00 pm CET, @binance Italian group will host AMA series with @peko0413 !”Crypto.com Coin (CRO): 18 November 2019 Exchange Closed Beta “Closed Beta starts the week of 18 Nov.”

Encrypted project calendar(November 19, 2019)

Lisk (LSK): 19 November 2019 Lisk.js “We are excited to announce liskjs2019 will take place on November 19th. This all day blockchain event will include…”Aion (AION): 19 November 2019 Hard Fork “Leading up to the hard fork on November 19th-20th, 2019 the Unity — Aion Kernel will be upgraded by node operators.”Enigma (ENG): 19 November 2019 Open Community Call The first Enigma Open Community Call is Tuesday, Nov 19th, 11AM ET! important updates on our protocol, the Genesis Game, and our road ahead.Lisk (LSK): 19 November 2019 Berlin Meetup “Ahead of LiskJS2019, our partners Berlin Valley are hosting a startup industry networking event, #DigitalTalents, tomorrow. “BitMax Token (BTMX): 19 November 2019 BitMax Delisting BitMax removes BTMXP/BTC, ETH/USDC, ETH/PAX, BAT/ETH, ZEC/ETH, DASH/ETH, LAMB/ETH, ZIL/ETH, COVA/ETH, ETC/ETH, FET/ETH, LAMBS/ETH, XTZ/ETH.

Encrypted project calendar(November 20, 2019)

OKB (OKB): 20 November 2019 OKEx Cryptour Odessa Ukr “Join us in Odessa as we journey through Ukraine for our OKEx Cryptour!DAPS Token (DAPS): 20 November 2019 Partnership with SWFT “Everyone will have $DAPS mobile wallets, atomic swaps and much more starting on the 20th of November!”Aragon (ANT): 20 November 2019 Draft Proposal Deadline “Draft proposals for Aragon Network Vote #5 are due in one week, on November 20 at 16:00 UTC…”IOTA (MIOTA): 20 November 2019 Smart City Expo Wilfried Pimenta, our Director of Business Development, will be among the speakers at the AI & Blockchain Summit in the Smart City Expo Worl…Bitcoin Fast (BTCF): 20 November 2019 BTCF Snapshot Snapshot taken of BTCF holders at 8:00 am (GMT-6).Credits (CS): 20 November 2019 AMA AMA with Credits team at 15:00 UTC.

Encrypted project calendar(November 21, 2019)

Cardano (ADA): and 2 others 21 November 2019 Meetup Netherlands (AMS) “This meetup is all about how to decentralize a blockchain, the problems and differences between Proof-of-Work and Proof-of-Stake…”Cappasity (CAPP): 21 November 2019 Virtuality Paris 2019 “Cappasity to demonstrate its solution for the interactive shopping experience at Virtuality Paris 2019.”Horizen (ZEN): 21 November 2019 Weekly Insider Team updates at 3:30 PM UTC/ 11:30 AM EDT: Engineering, Node network, Product/UX, Helpdesk, Legal, BD, Marketing, CEO Closing thoughts, AMA.OKB (OKB): 21 November 2019 OKEx Talks — Johannesburg “Join us the largest city of South Africa — Johannesburg where we will host our OKEx Talks on the 21st Nov.”IOST (IOST): 22 November 2019 Singapore Workshop Join the Institute of Blockchain for their 2nd IOST technical workshop in Singapore on 22 Nov 2019. The workshop includes IOST’s key tech.OKB (OKB): 22 November 2019 St. Petersberg Talks “Join us in St. Petersberg on 22 Nov as we answer your questions on Crypto Security. “NEM (XEM): 21 November 2019 SME Thought Leadership “SME Thought Leadership Series Forum #2” in Selangor, Malaysia from 8:30 AM — 2:30 PM.Stellar (XLM): 21 November 2019 NYC Meetup “Stellar Blockchain Meetup ft. FIC Network and Sam Conner’s Meridian Recap” in NYC from 6–8 PM.Waves (WAVES): 21 November 2019 Edinburgh Workshop “Next Thursday, we’re running a practical workshop on building DeFi products & designing Smart Contracts in your city!”

Encrypted project calendar(November 22, 2019)

IOST (IOST): 22 November 2019 Singapore Workshop Join the Institute of Blockchain for their 2nd IOST technical workshop in Singapore on 22 Nov 2019. The workshop includes IOST’s key techOKB (OKB): 22 November 2019 St. Petersberg Talks “Join us in St. Petersberg on 22 Nov as we answer your questions on Crypto Security. “Zenon (ZNN): 22 November 2019 Awareness Fund Payout “Distribution of the fund takes place every Friday until Pillars Lock-in Phase is completed.”

Encrypted project calendar(November 23, 2019)

Californium (CF) and 1 other: 23 November 2019 Greece Meetup “On November 23, the Greek #Cryptocurrency Community Meetup will take place in Greece!”

Encrypted project calendar(November 25, 2019)

0x (ZRX): 25 November 2019 0x V3 Proposal Live “The 0x v3 proposal was approved and will go live on Ethereum mainnet starting November 25th!”Dynamic Trading Rights (DTR): 25 November 2019 Chain Migration “On November 25 at 23:00 CET, TokensNet will make a migration of the $ELI token from Ethereum blockchain to Bitcoin Cash blockchain…”

Encrypted project calendar(November 27, 2019)

OKB (OKB): 27 November 2019 OKEx Cryptour Vinnytsia “Join us in Vinnytsia as we journey through Ukraine for our OKEx Cryptour!”Fetch.ai (FET): 27 November 2019 London Meetup “Join us on 27 November @primalbasehq to hear an exciting progress report as we prepare for the launch of our #mainnet”

Encrypted project calendar(November 28, 2019)

Horizen (ZEN): 28 November 2019 Weekly Insider Team updates at 3:30 PM UTC/ 11:30 AM EDT: Engineering, Node network, Product/UX, Helpdesk, Legal, BD, Marketing, CEO Closing thoughts, AMA.

Encrypted project calendar(November 29, 2019)

Zenon (ZNN): 29 November 2019 Awareness Fund Payout “Distribution of the fund takes place every Friday until Pillars Lock-in Phase is completed.”

Encrypted project calendar(November 30, 2019)

Ethos (ETHOS): 30 November 2019 (or earlier) Rebranding “In November, we unveil the broker token, a dynamic utility token to power our commission-free crypto trading and broker platform, Voyager.”Digitex Futures (DGTX): 30 November 2019 Public Testnet Launch “…We can expect to see the world’s first zero-commission futures trading platform live on the Ethereum public testnet from 30th November.”Monero (XMR): 30 November 2019 Protocol Upgrade “Preliminary information thread regarding the scheduled protocol upgrade of November 30.”Chiliz (CHZ): 30 November 2019 (or earlier) Fiat to CHZ Exchanges “We will add another two fiat to $CHZ exchanges in November…”Skrumble Network (SKM): 30 November 2019 (or earlier) P2P & Group Calling “P2P & Group Video Calling,” during November 2019.Aergo (AERGO): 30 November 2019 (or earlier) Mainnet 2.0 Upgrade Mainnet 2.0 Protocol update by end of November.Akropolis (AKRO): 30 November 2019 (or earlier) Beta Release “All functionality has been deployed to mainnet.”Nash Exchange (NEX): 30 November 2019 (or earlier) Mobile Strategy Phase 2 “Phase 2 of our mobile strategy will be live soon with our wallet and portfolio app hitting stores in November!”Akropolis (AKRO): 30 November 2019 (or earlier) Beta Release “All functionality has been deployed to mainnet.”Pakcoin (PAK): 30 November 2019 Staking Mobile App Android app for staklet is going to be launched on November 30th.

Telegram: https://t.me/Lay126
submitted by liuidaxmn to u/liuidaxmn [link] [comments]

Dev meeting summary

Here'z my summary of yesterday's dev meeting. Timestamps to this video.. Topics in order of interestingness:
sharding / casper research at recent meetings: 39:00-~60:00
recent ethCC conference / taipei meetup (shading workshop):
submitted by 9502 to ethtrader [link] [comments]

Geth Private Network

Hello Everyone,

I'm having a small issue with peer discovery. While I am able to successful link all the nodes on my private net together through addPeer it's not happening as I imaged it would. If I connect 3 devices to a node I'm hosting on the cloud I can view all three connections from that node. The other nodes however are only able to see that single node unless I manually run addPeer and connect all of them together. Here's the list of commands I run for the start up phase.

geth init genesis.json // The same genesis file on all nodes

geth --identity "ericsson" --rpc --rpcport "8080" --rpccorsdomain "*" --rpcapi "db,eth,net,web3" --port "30303" --networkid 1337 console 2>>eth.log

admin.addPeer("enode://ceb718ce11632d27feca519SAMPLEADDRESSb9049602e3b1b96dd383374f5[email protected]12.34.567.890:30303?discport=0")

I think it might be that I'm missing a flag in the geth command but I'm not sure.

Any help would be appreciated I've just started looking into Ethereum.
submitted by James_ericsson to ethereum [link] [comments]

Notes from Ethereum Core Devs Meeting #31 [1/12/18]

The next core dev meeting will be this Friday, January 26, 2018. The agenda and live stream link are located here.

Ethereum Core Devs Meeting 31 Notes

Meeting Date/Time: Friday 01/12/18 at 14:00 UTC

Meeting Duration: 1.5 hours

GitHub Agenda Page

Audio/Video of the meeting

Reddit thread


  1. Testing Updates.
  2. Yellow paper update.
  3. EWASM update + update on the following related EIPs. a. EVM 2.0 - https://github.com/ethereum/EIPs/issues/48 b. Extend DUP1-16 / SWAP1-16 With DUPN / SWAPN - https://github.com/ethereum/EIPs/issues/174 c. Subroutines and Static Jumps for the EVM - https://github.com/ethereum/EIPs/issues/615
  4. Stateless client development.
  5. Add ECADD and ECMUL precompiles for secp256k1 - https://github.com/ethereum/EIPs/issues/603 [See this blog post for context].
  6. Introduce miner heuristic "Child pays for parent" (like in BTC) to combat the weird cases when transactions with 1000 Gwei stuck in the mempool (because they are dependent via nonce on transaction paying much less and not getting mined).
  7. Creating a relay network of nodes to mitigate issues described here and other transaction propagation issues.
  8. Fork release management/Constantinople.
  9. Client updates.
  10. Other non-agenda issues.


Video starts at [4:36].

[4:56] 1. Testing Updates

No updates.

[5:27] 2. Yellow paper update.

Gavin put the Yellow Paper under the Creative Commons Free Culture License CC-BY-SA. Yoichi and Nick Savers have been making progress handling the Yellow Paper PRs. There is still the somewhat unresolved issue of what should define the "formal standard" of Ethereum and should an update to the Yellow Paper or another specification be required for every new EIP. This can be discussed in more detail in future meetings when there is greater attendance.

[7:43] 3. EWASM update + update on the following related EIPs.

[7:55] General update

Ewasm contributors are currently meeting in person together in Lisbon. EWASM EIPs listed in the subpoints are not up to date and can be disregarded. People should use the github.com/EWASM/design repo. The design has been pretty much speced out in the last year. During the design phase there were 2 implementations done in parallel: Javascript and C++ (which can be integrated in cpp-ethereum and geth). Issues have been faced in building out EWASM including struggling with implementing synchronous code in Javascript/browser. Idea was to move to an asynchronous model. Currently there is not a full decision on using synchronous vs asynchronous, but we are leaning towards synchronous implementation in C++ to run a testnet in cpp-ethereum that can run pure Web Assembly contracts. Metering contract in Web Assembly is on the to-do list and doesn't rely on sync/async decision. Likely will take week to come to a decision on sync vs async. More technical discussion and a funny anecdote involving the asynchronous vs synchronous decision and the affects of the recent Spectre/Meltdown attacks start at [12:07].

[15:08] a. EVM 2.0 - https://github.com/ethereum/EIPs/issues/48

Martin Becze will be closing this EIP. It is outdated.

[15:28] b. Extend DUP1-16 / SWAP1-16 With DUPN / SWAPN - https://github.com/ethereum/EIPs/issues/174

This doesn't have to do with EWASM, it has to do with adding extra opcodes in the current EVM. It is an upgrade to EVM 1.0 which is not needed if we skip straight to EWASM.

[16:47] c. Subroutines and Static Jumps for the EVM - https://github.com/ethereum/EIPs/issues/615

Greg has been working with Seed (Gitter tag) who is writing an ELM formalization of the EIP. Greg says that there is no formal social process for deciding things like EVM 1.5 implementation so he is not sure if/when it would be implemented. Greg has been working on cleaning up the proposal for those who want to use it. Greg has some ideas around an EVM 3.0 that pulls everything together with transpilation that he hasn't started working on yet and is not sure if he will.

[20:14] 4. Stateless client development.

Piper left some comments about some development of a stateless client for sharding, but it is very early. Alexey had a blog post describing stateless clients he may re-approach later.

[21:46] 5. Add ECADD and ECMUL pre-compiles for secp256k1 - https://github.com/ethereum/EIPs/issues/603 [See this blog post for context].

This topic was brought up months ago with mixed commentary. Christian R. says that ECADD and ECMUL were never intended to be used for general purpose cryptography, but rather it was suppose to be used in conjunction with the pairing pre-compiles for a specific curve that is pairing friendly. Christian says that in the past it has been discussed that there must be a very compelling reason for adding a pre-compile to Ethereum. Silur mentioned that the Monero research team is working on a new ring signature (still unnamed) that can be viewed in the Monero repository. The EWASM team may run some tests to compare native running of the pre-compiles vs EWASM. Adding a new pre-compile would only give a constant speed-up or reduction in cost, but if we achieve the same thing in new virtual machine it will give us a constant speed-up for every conceivable routine and allows for building other schemes like Casper and TrueBit. This is easier with Web Assembly because we can use existing C code. For the moment it looks like focusing energy on adding these proposed pre-compiles would not be worth it compared to just waiting for the next VM (likely EWASM) which will allow far more speed-ups across all computational routines.

[37:00] 6. Introduce miner heuristic "Child pays for parent" (like in BTC) to combat the weird cases when transactions with 1000 Gwei stuck in the mempool (because they are dependent via nonce on transaction paying much less and not getting mined).

[Note: I tried my best to cover what was discussed here, but I am not an expert in Ethereum transactions. If you find a mistake please point it out to me. Thanks!] Agenda item brought up to get people's opinion on this topic. Currently in Ethereum there are transactions that are stuck in the mempool for a long time because of the way transaction ordering per account is handled. The nonce of a transaction must be greater than the previous mined transactions (or equal if you are trying to replace a transaction). For example you can't process transaction #27 before transaction #26 has been mined. Many of the stuck transactions are dependent on other transactions that pay a much smaller fee, but are not being mined. It seems people inadvertently send an initial transaction with too small of a fee and then more transactions at a higher nonce with a much higher fee that cannot be processed until the first small fee transaction is processed. Alexey wondered if this may pose an attack vector or if we would get a benefit from implementing "child pays for parent" like Bitcoin does. Peter explained even if you define the max amount of gas your transaction could potentially consume, there is no guarantee it will use that much and we won't know until the transaction is processed (the only guarantee is that 21,000 gas will be consumed - a plain ether transfer). The attack vector example would be someone pushing a transaction that truly consumes 3,000,000 gas and attach a transaction fee of 1 wei and then push another TX that claims to consume 3,000,000 gas but with a transaction fee of 1000gwei. From the outside it looks like I can both can be executed for profit from the miner's perspective, but in reality the 2nd transaction will be processed first and the 1st tx will be long running and indirectly punish the miner. Alexey was concerned about the mempool filling up and impact on clients due to the way nonces are handled. Peter clarified that transactions in the mempool in the go ethereum client only maintains the top 4,000 most expensive transactions. If your cheap transaction gets evicted, the expensive transactions you stacked on top of it get evicted as well because they are no longer executable due to the nonce.

[42:21] 7. Creating a relay network of nodes to mitigate issues described here and other transaction propagation issues.

A relay network in general is a group of peers and/or miners who use a peer list to quickly connect to a group of known peers before connecting to (or instead of connecting to) random peers using network discovery. Alexey conjectured that this may create a powerful ring of network players who can share transactions very quickly and hurt the little guys on the outside (hurting the idea of this being a mesh network of peers). Clarifications were made about the issues involving transaction propagation issues with nodes with high transaction throughput such as Infura and Bittrex. Clients suddenly stop pushing transactions or cannot keep up with the blockchain when they are pushing out so many transactions. Hudson will work towards exploring this issue more and connecting the people with the issues with the devs.

[49:45] 8. Fork release management/Constantinople.

Hudson will be working on writing up a starting plan to discuss potential release management issues. BitsBeTripping sent Hudson some good material about project management that he will review and bring to the next meeting. We need to start discussing Constantinople sooner rather than later.

[52:55] 9. Client updates.

10. Other non-agenda items

[1:05:42] Question: Will we see any scaling improvements from Constantinople?

Answer is no because it potentially includes the first steps of the Casper consensus protocol and some account abstraction EIPs, but both of those do not alleviate scaling issues. Sharding would alleviate some of the issues. We are currently mostly bound by database and processing speed due to the database. Short term there are a lot of client improvements that can be accomplished to improve disk I/O, but long term things like sharding will be necessary. The Eth Research site has a lot of interesting threads about sharding including merkle tree formats to be used and ideas around asynchronous accumulators

[1:09:57] Decision process for EIPs?

Needs to be improved. Hudson and others will work on updating EIP #1 and other improvements in Q1. Nick Savers has been added as an EIP editor. Yoichi has been added as an editor. Both are doing a great job.


Alex Beregszaszi (EWASM/Solidity/ethereumJS), Alex Van de Sande (Mist/Ethereum Wallet), Alexey Akhunov (Turbo Geth), Ben Edgington (Consensys/Pegasys), Casey Detrio (Volunteer), Christian Reitwiessner (cpp-ethereum/Solidity), Daniel Ellison (Consensys/LLL), Greg Colvin (EVM), Hudson Jameson (Ethereum Foundation), Hugo de la Cruz (ethereumJS/EWASM), Jake Lang (EWASM), Jared Wasinger (ethereumJS/EWASM), Martin Becze (EWASM), Mikhail Kalinin (Harmony), Paweł Bylica (cpp-ethereum/EWASM), Péter Szilágyi (geth), Silur (ethereumJS / EWASM)
submitted by Souptacular to ethereum [link] [comments]

آپدیت شبکه سنت پترزبورگ و کنستانتینوپول

آپدیت شبکه سنت پترزبورگ و کنستانتینوپول

از ماه ها پیش کابران منتظر بروزرسانی شبکه اتریوم بودند که بنا به دلایلی که در پست های گذشته ذکر کردیم این آپدیت های به تاخیر افتاده بودند که توسعه دهندگان اتریوم وعده تحقق این آپدیت را هفته پیش داده بودند. در تاریخ 9 اسفند هاردفورک کنستانتینوپول بر روی بلاک 7,280,000 با موفقیت اجرا شد.
بیشتر بخوانید: بایننس از هاردفورک کنستانتینوپول پشتیبانی خواهد کرد
اتریوم که در چند ماه گذشته جایگاه دومی خود را از نظر ارزش بازار به ریپل داده بود دباره به جایگاه اصلی خودش بعد از بیت کوین برگشته است.
این هارد فورک، بروز رسانی بزرگی برای بلاک چین اتریوم بود که بهبودهایی در ساختار کارمزدها و راندمان شبکه ایجاد می کند و همچنین راهکارهای مقیاس پذیری نظیر تراکنش های خارج از زنجیره را به ارمغان می آورد.
این بروز رسانی برای انتقال از اتریوم به اتریوم 2,0 ضروری است و باعث بهتر و سریعتر شدن آن می شود.

بروز رسانی شبکه سنت پترزبورگ و کنستانتینوپول

علاوه بر بروز رسانی کنستانتینوپول، شبکه اصلی اتریوم شاهد بروزرسانی دیگری با نام سنت پترزبورگ بود که پس از به تاخیر افتادن هارد فورک کنستانتینوپول و پیدا شدن آسیب پذیری امنیتی در پروپوزال بهبود اتریوم 1283 معرفی شد.
تنها هدف بروز رسانی سنت پترزبورگ این بود که پروپوزال بهبود اتریوم 1283 را پاک کند. همه چیز طبق برنامه ریزی پیش رفت و این آپدیت ها در حال حاضر بر روی شبکه اصلی اتریوم می باشند.

این بروزرسانی مقولبیت داشته است؟

اگرچه این بروز رسانی ها موفق بودند، با این حال اطلاعات سایت Ethernodes.org نشان می‌دهد که تمام کاربران اتریوم این بروز رسانی ها را نپذیرفته اند. برای مثال، فقط 28,2 درصد کلاینت های گث (Geth) و پریتی (Parity)، نسخه های سازگار با کنستانتینوپول اتریوم را اجرا می‌کنند.
با این حال جای نگرانی نیست، زیرا این بروز رسانی هنوز بسیار جدید و نوظهور است و کلاینت ها و کاربران اتریوم در ابتدای امر محتاط و گوش به زنگ می‌باشند تا از هرگونه باگ در این بروز رسانی اجتناب کنند.
در مجموع موفقیت بروز رسانی کنستانتینوپول اتریوم، باری از دوش بسیاری از افراد برداشت زیرا پیش بینی می‌شد که این هارد فورک مجددا مانند موارد کذشته به تاخیر بیافتد.
بسیاری افراد منتظر تغییرات قیمت بعد از این بروزرسانی ها بودند که بر خلاف میل آنها قیمت اتریوم به این بروز رسانی ها واکنش نشان نداد و حدود ۱۳۶ الی ۱۳۷ دلار ثابت ماند.
submitted by arzcell to u/arzcell [link] [comments]

DEVCON2 report: Day Three - Final day

previous days
Question: the 3 days of devcon are over. Are people interested in reports on the next 3 days of international Blockchain week (demo day + 2 days of global Blockchain summit) http://www.blockchainweek2016.org
Event update
The buzz during the day was around the "stick puzzle" that Bok Khoo was giving out to people. It is just a stick, with a loop of string. He gets you to turn away, he uses "the trick" to put it onto your bag and then you try to get it off.
The WeChat channel was just filled with everyone asking where they can get it, and the screaming that they can't figure it out. Only about 5 people reported they were able to solve it (I haven't yet)
http://imgur.com/mYfJQP4 http://imgur.com/4Euka1a
I'm biased, but I thought the announcement from Microsoft with the update of cryptlets was a big deal. The morning sessions covered a few different oracle systems, the afternoon had lots of IPFS sessions.
Microsoft - A Lap around Cryptlets
https://azure.microsoft.com/en-us/blog/cryptletsdd/ https://azure.microsoft.com/en-us/documentation/templates/ethereum-consortium-blockchain-network/ https://azure.microsoft.com/en-us/blog/authomarleyg
Microsoft was a sponsor of Devcon1 & 2 Ethereum is a 1st class citizen Support for community & partners - Bizspark, Meetups, Workshops
Announcing: Bletchley v1 Distributed Ledger stack V1 is a private Ethrerum consortium, that you can spin up for your own enterprise / group
Cryptlets are being developed to help with security, identity, etc. How do you get trusted external data feeds injected into the Blockchain? Doing things on a specific interval (every 15 mins) When price of something hits a threshold (oil goes above $40/barrel) Secure IP protected algorithms, but still share with blockchain network. Use libraries for common platforms (.Net, Java, etc)
Cryptlets vs Oracle Cryptlets will have a marketplace on Azure that will allow you to purchase and utilise
Use case: Trigger on an event Wake up on 4pm, if market was open that day, then give me the price of gold for that day.Get signature of attested server, attested sender.
Use case: Control Using smart contract like a traditional DB. Declare data you are keeping track of, and the functions/"stored proc" to update that data. Cryptlet runs off chain, and can be scaled up.
Utility cryptlet. Use an attribute in solidity contract with cryptlet details Developer references at design time the cryptlet they want the contract to call Contract cryptlet, deploy the cryptlet at same time as contract.
Why would you want Azure to do this? SGX allows you to create "secure enclaves", can have complete isolation on the hardware chip where it is not modifable. Provides a secure enclave at the CPU level. Can give full attestation right down to the silicon. Will be provided as a enclave container on Azure. Will be released for .NET core CLR first, then other languages. Can create cryptlet libraries that you can scale and put into the Azure marketplace. An ecosystem for developers & ISVs to consume and publish.
Bletchley v1 released today will let you spin up a private consortium. Before today, it took a long time to try and deploy a private consortium (can take weeks to read doco, Now takes 5 minutes to deploy! Creates a private consortium, puts each member in its own separate subnet
Mist Vision and Demo I was too busy sharing the release posts of Microsoft project bletchey v1, missed this talk. It did look interesting, I will watch this one later. Idea: Reward for bandwidth. Providing connection could replace mining as entrance point for desktop computers. Allow you to have a trickle so you can trigger smart contracts. Standardised backends, so that you can swap out the underlying node between geth, blockapps, etc.
https://github.com/ethereum/web3.js Etehereum JS API Smart conracts are EVM opcodes, Helps translates calls to JSON RPC calls. Helps do the ABI encoding when sending data from JS to EVM It kept on growing, many different utility functions being thrown in. Is time to clean it up and be refactored.
They are now building a NEW web3.js The communication will be socket based, will enable subscriptions. Everything will be based on promises to subscribe to events, like log events. Bunch of other newer cleaner methods and ways to do things like deploying contracts.
Smart contract security
Was a very good postmorteum of The DAO and things that could be done to mitigate it in the future.
An issue with The DAO was trying to do a massive jump from centralisation all the way to full decentralisation. Meant no one could step up and make a decision on how to save it. We need to make smaller steps towards full decentralisation as we learn as a community how to do this. Same security patterns as yesterday's talks: check invarients, beware 1024 call stack depth, reentry exploit (update state BEFORE executing calls), timestamps are manipulatable. Updateable contracts. Who can update it? Community multisig? We need better rools: formal verification, compiler warnings, improved IDEs, trusted libraries, excape hatches
Conclusion: It is still very early days in this space, be careful.
A Provably Honest Oracle Model: Auditable Offchain Data Gathering & Computations
Oracalize is the most widely used oracle (until everyone starts using Microsoft Azure cryptlets ;-) ) Contract calls Oracalize contract with the data they want, off chain they see this get the data, Oracalise then trigger their contract externally, which does a callback to your contract with the data. Can use external notary servers. Can get proof from multiple external services to get a higher level of confidence about data (e.g. stock price from a few feeds). Off-chain (auditable_ computation) AWS sandbox 2.0. Put the execution package onto IPFS, AWS gets it and executes it, signs it.
iEx.ec: Fully Distributed Cloud Thanks to the Ethereum Blockchain
http://iex.ec/ Provides blockchain based execution environments Global market for computing resources. Idea is to do what we did before with "grid computing" use the idle capacity of computers. But this time do a trickle of micropayments. Allows people to harness this global power to execute their tasks in a global "distributed cloud".
The Final frontier: The company smart conract
http://otonomos.com/ Helping companies to incorporate on the blockchain.
Smart oracles
https://github.com/smartoracles Connecting to external resources is difficult. Hard to try and use external currencies (like a bank account / fiat money) to make transactions. Could hook in paypal, HSBC, wells fargo, etc. Can provide your own payment services as an API to a smart oracle for smart contracts to consume. Do off chain data storage by calling smart oracle API Roadmap: more data sources & more payment methods
IPFS & Ethereum: Updates
https://Ipfs.io IPFS is AMAZING, seriously go watch the full 1 hour talks Juan has given in previous years.
Current web has current issues. Centralisation, etc. IPFS is a new hypermedia transfer protocol Content can be retrieved not from specific servers, but instead via it's hash so that it can come from anywhere in the network (maybe from the person next to you who has cached it). It is highly modular, all of the transfer protocals, routing, naming, etc. are all swapable Is available as GO-IPFS & now JS-IPFS Means now you can run IPFS in the browser IPFS was great for static content, but not so great for dynamic content. Low latency pub/sub protocol will help with dynamic data. Created a distributed peer to peer chat app using this new dynamic content protocol. IPLD a common link-tree hash format Will be able to use IPFS to retrieve ethereum blockchain blocks DIRECTLY Can use IPFS as a package manager to retrieve them in a distributed manner.
Many projects are using Ethereum & IPFS Uport, Digix, Infura, Ujo, Eris, Blockfreight. Filecoin was created as a way to try and incentivize nodes to keep files longer time. People rent out hdd space to earn filecoin. Exchange bitcoin/filecoin. Use filecoin to store files in network. Filecoin is going to be built on top of the public Ethereum blockchain, as a virtual blockchain / token.
IPFS Libp2p & Ethereum networking
Network connectivity between any 2 nodes can be difficult. Censorship, bandwidth, network issues, etc. Having to deal with different networking topologies and access. Libp2p & Devp2p is different. Devp2p is for Ethereum. LIbp2p is modular, can swap out components to change network access, encryption methods, etc. Can build up a MEGA mesh network, by utilising traditional wired internet, radio, bluetooth between some nodes. Web browser using web socket, to a node, which routes across network, to zigbee to a IoT device. Libp2p & Devp2p could merge and augment each other. Could create the libp2p components to replace the devp2p bits Any 2 nodes that speak the same protocol can communicate and be a part of the network chain. Experiment. They took the browser based version of EVM. Then used Libp2p to talk to the Ethereum network. Had a complete ethereum node running in a browser.
https://uport.me/ Universal identity platform Current challenges: key management. Ux for average person. Dapps via mobile. Identity and data ownership. How do you keep a consistent identity, even if you lose a key. Have some multisig contracts that you can use to keep track. Social recovery, use your friends to attest it is really you. Keep private key on mobile, do transactions on the desktop, scan a QR code to sign the transaction on your phone and send it off.
A Deep Dive into the Colony Foundation Protocol
It is an open source governance protocol built on Ethereum Problem with voting is how to prevent Sybil attacks. Votes are weighted by a reputation score. Reputation is non-transferable that can only be earned. Total weighted voting helps mitigate this.
Chain orchestration tooling & smart contract package management
Eris is tooling for developers. Package manager to build your own blockchain. Can compose a chain, e.g. geth + tendermint consensus. Init, install, do. Can easily install on Mac/bew, linux/apt-get, Windows/choco
The Golem Project: Ethereum-based market for computing power
http://www.golemproject.net/ Anyone can make an offer to sell computing power. e.g. Distributed rendering Want to create a standard framework that anyone can use to submit and process jobs.
Status: Integrating Ethereum Into Our Daily Lives
https://status.im Want to get ethereum everywhere. "Mist for Mobile" Everyone is using their mobile phones for everything, but mostly using instant messaging. What would Ethereum in a IM window look? Created a IM mobile app that has a local geth node. tart up, it asks you to create a password, it generates a pub/private pair. Then can send messages via whisper, and the messages are signed with your public key. Can load Dapps up in the local webview and interact with them. Allows you to create "chat Dapps", that you interact with via text. Like chatbots
Maker Ecosystem Overview
www.Makerdao.com Dai: seeking stability on blockchain. Stablecoin engine: smart contract that holds collateral reserves and controls the Dai lifecycle. MKR: open source community managing risk of the system In the last year, investing in a solid technical core. More slow and audit things. Moving into the next phase of stablecoin development. Their latest project is the "Simplecoin project" Meeting Thereum community's need for stability. An independent platform for creating centrally administered simple stablecoins. Issues create their own rule sets: Collateral types, participant whitelists, security parameters. Example: Shrutebucks. The only people who own it are Dwight, Jim & Pam. They backed it with 1/3 ETH 1/3 DGX 1/3 DUSD.
Orbit. A distributed peer to peer app on IPFS
https://github.com/haadcode Created a full distributed chat room, itself distributed through IPFS. It is integrated with uPort for identification Using uPort allows you to verify that you are talking to the correct person in the chat channel. All their messages are signed with their public keys He also created a full distribited twitter clone, using uport for the identity as well. Orbit-db key value store DB that stores its data on IPFS. Eventually consistent Appends data to the DB, an event is sent to those subscribed on pub/sub so they can see the latest root hash. Based on CRDT Ethereum + Pubsub + CRDTs + IPFS = super power primatives to build dynamic distributed apps
Development considerations with distributed apps. Need to ensure that apps work offline. No centralised servers. No data silos. Provide integration path.
Future work: could you use uPort for ACL like permissions? Mobile use cases, how to make it work nicely on mobiles
Building scalable React Dapp architecture
https://github.com/SilentCicero/react-dapp-boilerplate React + Ethereum He has a configured boilerplate template. Has contract scaffolding. Enforced contract Linting/testing. Wallet generation/identity. Preconfigured web3 instance. UI: Mature react arhitecture "react boilerplate". Prices listed in USD with ETH/btc via kraken api. A basic multi-contract example Dapp. Offline first, dapp runs without internet. Uses Redux. State models in UI & blockchains work well. PostCSS, CSS Modules, sanitize.cs. Redux, immutableJS, reslect, redux-saga, i18n, redux-router. Web3, ethdeploy, dapple, solium, eth-lightwallet, chaithereum, ethereumjs0-testrpc Enforced contract testing in 2 languages.
Ethereum for Enterprise (BlockApps Strato)
Trying to make sure that Ethereum stays relevent to enterprise development. Why do you need a blockchain WITHIN an org, shouldn't they trust each other? Well different departments may not, they may reconcile differently, and can help automate/orchestrate between them. Blockchain is the "killer app" for cloud financial services. Legacy infrastructure, batch prossing, etc are all restricting fintech from progressing. Blockchain can happen in real time, can replace legacy. Ethereum is very flexible and programmable, works well. There are others based on Bitcoin (like Hyperledger). Ethereum + Blockapps = Extreme productivity + Proven Technology. Blockapps is extending Ethereum for Enterprise. Runs very well on Azure Enterprises don't want all their data exposed on public chain. Blockapps helps solve data privacy and scaling with multichain fabrics.
submitted by DavidBurela to ethereum [link] [comments]

Geth 1.0.0 released

Released Geth version 1.0.0; the first major version of the go-ethereum code base and the first live-net version of geth :-D
I'd like to thank everyone in ETH DEV and especially my team for their incredible hard and dedicated work and the amount of blood sweat and tears they've poured in this project and the release of Frontier. Without all of you this wouldn't have been possible!
Thank you, community, for your patience with us and the amout of testing you've done during the Olympic testing phase, it's been an incredible help to us and we're glad you've joined us on this batshit crazy ride! :-D
submitted by jeffehhh to ethereum [link] [comments]

ETC Weekly Development Report, for the period 26 Sep - 02 Oct

Summary of our achievements:
ETC related projects progress:
submitted by colibry545 to EthereumClassic [link] [comments]

Howto be part of the DAO since 28.05.2016

Dear DAO-Tokenholders,
I am auxborg, and I am a DAO-Tokenholder (42.000). My Account# is: 0x0CddbBf2871745B092E5b91eEd3066e890999B60 It can be monitored here: http://etherscan.io/address/0x0CddbBf2871745B092E5b91eEd3066e890999B60
I changed my mind, according to my first proposal to the DAO which is Proposal #15: https://daostats.github.io/proposal.html#15
Since a lot of community members still use conventional web2.0 media for communication I have made up my mind, thus posting my further thoughts here on reddit.
At the moment, a moratorium is in place. One could argue with that, but in fact, no contractor proposals which involve funds of the DAO are beeing whitelisted by the curators.
Some headlines of important blogposters underline that statement: Vlad Zamfir, Emin Gün Sirer, Dino Mark about possible attack vecors regarding the DAO: http://hackingdistributed.com/2016/05/27/dao-call-for-moratorium/
The curator progress outlined by a realtime spreadsheet: https://docs.google.com/spreadsheets/d/1EG639VqRZwib7SJLJ6NP8fzN49QAztrpL0uWFpTx-8U/edit?pref=2&pli=1#gid=0
and this post by Stephan Tual: https://blog.slock.it/dao-update-e79c9c5a335f#.9p0h15oau
Honestly, conventional web2.0 media helps to understand what is going on. Yet, it fails to represent the DTH's real state of interest. Not to mention, that it is centralised.
Currently there are various "dummy proposals" (which includes #15, of course) submitted to the DAO-Contract by DAO-Tokenholders. Some of these "dummy proposals" are experimental or neat. But some of those proposals seem to have a stronger meaning for the DAO, even if they are non-binding.
Let`s go through:
Proposal 17: This is a SURVEY. A DTH has put 2 ETH into the DAO-Contract to find out if a majority of the DAO would like to change some part of the Contract-code (Raising the deposit from 2 ETH to 11 ETH). If the proposal reaches quorum, the DTH who submitted the proposal gets back his 2 ETH. And here is the point: Nothing else happens. It is a dummy proposal, the submitter was risking 2 ETH but no further changes take place. What is left, is the result of a true DAO SURVEY, definitely contributing to the DAO's progress and evolvement. Decentraliced and autonomously made.
Proposal 5: THIS is a SURVEY, too. A DTH has put 2 ETH into the DAO-Contract to find out if a majority agrees to the need of a moratorium. This is an important SURVEY among real DAO-Tokenholdes since it will be seen by the curators as a true and immutable state of the DAO. A curator can rely on this. It's in the blockchain. Sorry to say, but other web2.0 platforms cannot have such an impact (yet). To emphasise this, I am referring to FelixA's blogpost's last part "Future outline": https://blog.daohub.org/what-is-the-proposed-moratorium-and-what-is-it-good-for-b37696aeb17f#.9xjh6scb0
Well, here we are. Some say we are stuck, but I think that would sound rather pessimistic. Some DTHs have started to use the DAO, either by submitting "dummy proposals", testing the currently working vote-mechanism or simply by initiating a split from the DAO. So, we're not stuck too much.
In my case, how can I participate or even contribute to the DAO until the important proposals come in? By important proposals I mean such proposals where funds or contractors are involved. First, let's not call "dummy proposals" "dummy proposals" any more. Imagine them as proposals with no other consequence but beeing either a SURVEY, a STATEMENT or a PREDICTION.
Some use-cases:
If I had something to say and I want to let the rest of the DTHs know, I would create a proposal - flagged as STATEMENT - putting my Statement into the descripton and pay 2 ETH as a deposit for that. That's currently about 25 EUR for putting my statement to test. A risk, but for me it is worth 25 bucks, because I think what I have to say is important.
The other DTHs can do 3 things:
1) Vote YES: This shows how many DTHs approve my statement.
2) Vote NO: This shows how many DTHs do NOT approve my statement.
3) no vote: If quorum isn't reached, the DAO is getting the deposit. I would know, that my statement might have been silly. Deposit lost.
Some other DTH has obviously aquired some information and is making a SURVEY (e.g. about how to deal with security issues regarding the DAO). She or he has already paid the deposit and the proposal is in it's debating period.
I can do 3 things:
1) Vote YES: This is a true commitment of my stake at the DAO, since my Tokens are locked for the time of the debating period. I still can make votes on other proposals, but until the debating period ends, my DAO-Tokens cannot be transfered, for instance to an exchange or another account.
2) Vote NO: The same Token-related situation applies to the NO-vote. Moreover, I am emphasising by my stake of the DAO, that I have a different opinion regarding the content of the SURVEY or PREDICTION.
3) no vote: several scenarios can be found in this case:
So, we are not stuck. We are at the beginning. Personally, I wish to convince at least 20% of all DTHs to vote on Proposal #5.
It helps the curators and all other folks involved in the currently, most important phase of the DAO: Securing the DAO, thus paving the way to prosperity and success.
According to my proposal #15, there is one thing that hasen't changed in my mind: Let's show what we've got!
I am auxborg
Some good news:
Now, geth-1.4.6 syncs the blockchain like having exchanged the old steam engine with a warp-drive. You can easily use mist for voting: https://blog.slock.it/dao-how-to-vote-video-tutorial-e9919a0fcc1f#.8d8bbbp8u
A little hint for windows-users:
1) start geth first.
Download here: https://build.ethdev.com/builds/Windows%20Go%20master%20branch/ Use: Geth-Win64-20160606144531-1.4.6-0f036f6.zip
This is your node. You can run the graphical user interfaces (Wallet, Mist for Voting) on top of the node. If you see constant messages with "... imported 1 block(s) ..." you are sync with the network.
2) start Wallet/Mist "on top" after geth has synced. Download 2 versions of the mist release:
Use version 0.6.2 if you want to use the wallet. https://github.com/ethereum/mist/releases/tag/0.6.2
Use version 0.7.4 if you want to do voting. https://github.com/ethereum/mist/releases/tag/0.7.4 -> "Ethereum-Wallet.exe --mode mist"
submitted by auxborg_c to TheDao [link] [comments]

People should stop repeating the same mistake

Latest two biggest known Ether loss has happened before and people keep repeating them.
The first one is the mistake of opening RPC to everyone:
You think this is a new one? Nope it has happened before.
Ethereum Foundation even published a blog about it
The second one is the latest DAO hack.
This is a newly discovered vulnerability right? I mean only after MakerDAO revealed this a few days ago
Nope actually this kind of subtlety is already reported in LeastAuthority's report in early Olympic phase:
The CALL opcode (used to send messages to other contracts, or send funds to non-contract accounts) will fail if it causes the call stack to exceed 1024 frames. This is not an exception: instead, the CALL operation indicates an error, instead of returning data from the callee contract
Early contract like Etherpot is affected by this(I think there was a reddit post but I can't find it):
The fact that DAO was made by the same people that was part of Ethereum Foundation at one time adds insult to injury.
Now the solution is 'Let's Destroy Fungibility', which sets a bad precedent in the future.
TL;DR Please understand any reported security related issue and try not to repeat them. History doesn't repeat but it does rhyme.
submitted by throwaway36256 to ethereum [link] [comments]

ETC Weekly Development Report for the period of Sept 26th to Oct 2nd

Summary of achievements:
-Geth release (internal) with Bomb Delay by Elaine Ou, Igor Artamonov and Eric Somdahl. You can download last version and help us with testing https://bintray.com/ethereumproject/GoEthereumClassic/go-ethereum/develop#files
-Working on possible solutions for Replay Attack
-ECIP Draft by Marcus R. Brown https://github.com/ethereumproject/ECIPs/pull/9
-ECIP Draft by Avtar Sehra https://github.com/ethereumproject/ECIPs/pull/10
-Cloud Templates by Cody Burns https://github.com/ethereumproject/Cloud-Template
ETC related projects progress:
-Fundonomy production servers now setup, and platform is being deployed for testing on public ETC chain. Reputation system being implemented using centralised mechanism for refinement for first public release. Wolverine, phase 1 release, is on schedule for public release. Key founding team will be made public soon.
submitted by CarloVetc to CryptoCurrency [link] [comments]

Set up your development environment for Ethereum on a ... Ethereum: The accumulation phase of a lifetime Ethereum wallet installation and fix - YouTube Ethereum Wallets for Beginners AND Experts - YouTube Ethereum Phase Blade Transmog and Gold Making (Legion Pre ...

During Ethereum’s 2015 debut, the Parity client launched after Geth. That launch caused the validator set to swing disproportionately toward the latter client; an 80-20 tilt. Drake commented: To install Ethereum client Geth, we will compile it from the GitHub source. Clone the repository $ git clone https: / / github. com / ethereum / go-ethereum. git --branch v < version > Remove --branch v < version > if you want to use the latest code (unstable). Go into the folder and build geth $ cd go-ethereum $ make geth (wait a couple of ... Phase 1.5 is the integration of Ethereum mainnet into the new eth2 consensus mechanism as a shard (existing as one of the many shards created in Phase 1). ... In an Ethereum client today (e.g. geth, etc) almost all of the complexity lies in handling user-level activity – transaction pool, block creation, virtual machine computation, and state ... How do Ethereum syncing work? A. The current default mode of sync for Geth is called fast sync. Instead of starting from the genesis block and reprocessing all the transactions that ever occurred (which could take weeks), fast sync downloads the blocks, and only verifies the associated proof-of-works. ... This phase is called the state trie ... The Eth1 and Eth2 chains will still operate in parallel after Phase 1. Important Considerations. In Phase 0, 1, and 2 the main PoW chain (Eth1) will remain live while testing and transitioning is happening on the Eth2 chain. This means that rewards will be paid to both Ethereum 2.0 validators as well as the normal PoW block rewards.

[index] [4639] [6846] [4093] [68] [557] [3408] [4036] [2406] [4953] [6446]

Set up your development environment for Ethereum on a ...

i do not participate in paid reviews or promotions. if you have been approached by someone on telegram claiming to be a part of the crypto tips team, they ar... how to get a really cool transmog sword and possibly make some gold. This is a really cool transmog item sold from a vendor in netherstorm nobody really know... This video is part of the "Become a Blockchain Developer with Ethereum and Solidity" online course on Udemy. If you want to learn more about how to use those... I just re-installed the ethereum wallet and it was all going well until I ran the wallet. An issue came up and it said: please install the geth node version ... Game Giveaway https://www.youtube.com/watch?v=nrKAdz8HLtI ***** Any Donations Are Welcome Pay...