Ethereum-wallet should default to light client mode #2372

jtoomim · 2017-05-29T00:02:19Z

When launching ethereum-wallet, the default mode should be to run geth in light client mode. There are a few main reasons for this:

Running a full node with a complete state trie is only useful to advanced users, and advanced users know how to change configuration options. Casual users need to have default options that address their needs with as little UX friction as possible.
Applications should be configured to use the minimum amount of system resources possible by default until directed by the user that greater functionality is needed.
Going from 100 MB of data to 10 GB of data means that a lot of people simply can't run ethereum-wallet with its default configuration as it would cause them to run out of disk space.
There are no good easy-to-use light client options for ethereum wallets with decent encryption of wallet files and open source code. Ethereum-wallet is pretty close, but the need to run it with special command line options in order to not make it use a ton of memory means that I can't just tell my mom to download and run it.

paddycy · 2017-05-29T04:15:32Z

I agree with this guy. It is ridiculous to have a 10gb download for a wallet. I CANNOT sync the wallet for over a week now

housemobile · 2017-05-30T12:56:43Z

What flags can you input to sync EW or Mist in light mode?

jtoomim · 2017-05-30T19:40:22Z

Usually, with ./ethereum-wallet --node-light. However, light mode got borked in the most recent release of Ethereum-wallet due to some changes in the geth command line options in 1.6.0 (#2254). That should be fixed by the next mist/ethereum-wallet release, though.

MaximRunev · 2017-07-06T15:10:44Z

Full node (ethereum wallet) let normal sync only on SSD hard drive.

User195 · 2017-07-19T15:50:00Z

I also vote to set light mode as default

jtoomim · 2017-07-19T15:55:58Z

#1547

pparent76 · 2017-07-27T09:27:13Z

Unfortunately the light client mode don't seem to work better in 0.9 than it was working on 0.8.9:


Node type: geth
Network: main
Platform: linux (Architecure x64)

...Fatal: flags --fast, --light can't be used at the same time


[2017-07-27 11:28:04.557] [INFO] EthereumNode - Node type: geth
[2017-07-27 11:28:04.557] [INFO] EthereumNode - Network: main
[2017-07-27 11:28:04.557] [INFO] EthereumNode - Start node: geth main
[2017-07-27 11:28:04.558] [INFO] EthereumNode - Start node using /home/pparent/.config/Ethereum Wallet/binaries/Geth/unpacked/geth
[2017-07-27 11:28:07.596] [INFO] EthereumNode - 3000ms elapsed, assuming node started up successfully
[2017-07-27 11:28:07.597] [INFO] EthereumNode - Started node successfully: geth main
[2017-07-27 11:28:07.598] [INFO] Sockets/node-ipc - Connect to {"path":"/home/pparent/.ethereum/geth.ipc"}
[2017-07-27 11:28:07.599] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:08.600] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:09.601] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:10.602] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:11.604] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:12.605] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:13.607] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:14.608] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:15.610] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:16.611] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:17.613] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:18.614] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:19.616] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:20.617] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:21.619] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:22.629] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:23.631] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:24.633] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:25.634] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:26.636] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:27.638] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:28.639] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:29.640] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:30.642] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:31.643] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:32.645] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:33.647] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:34.649] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:35.650] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:36.652] [WARN] Sockets/node-ipc - Connection failed, retrying after 1000ms...
[2017-07-27 11:28:37.599] [ERROR] Sockets/node-ipc - Connection failed (30000ms elapsed)
[2017-07-27 11:28:37.600] [ERROR] EthereumNode - Failed to connect to node Error: Unable to connect to socket: timeout
    at Timeout.setTimeout (/opt/Ethereum Wallet/resources/app.asar/modules/sockets/base.js:97:43)
    at tryOnTimeout (timers.js:232:11)
    at Timer.listOnTimeout (timers.js:202:5)
[2017-07-27 11:28:37.620] [ERROR] EthereumNode - Failed to start node Error: Unable to connect to socket: timeout
    at Timeout.setTimeout (/opt/Ethereum Wallet/resources/app.asar/modules/sockets/base.js:97:43)
    at tryOnTimeout (timers.js:232:11)
    at Timer.listOnTimeout (timers.js:202:5)
[2017-07-27 11:28:37.621] [ERROR] main - Error starting up node and/or syncing Error: Unable to connect to socket: timeout
    at Timeout.setTimeout (/opt/Ethereum Wallet/resources/app.asar/modules/sockets/base.js:97:43)
    at tryOnTimeout (timers.js:232:11)
    at Timer.listOnTimeout (timers.js:202:5)

muten85 · 2017-07-27T13:39:36Z

Same issue here. Not working on MIST 0.9

pparent76 · 2017-07-27T15:23:02Z

I had it working with this staring script:

#!/bin/bash

ps -ae | grep geth
if [ "$?" -ne "0" ]; then
	geth  --syncmode "light"  &
	sleep 10;
fi
ethereumwallet --light-node

evertonfraga · 2017-07-28T14:53:35Z

Light client still has some way to go in regards to logs (events). We're closely following this subject.

forest-hermit · 2017-07-30T10:03:27Z

I hope so, my wallet uses 118 GB right now, this is unsustainable for most of users.

rodgermoore · 2017-08-21T19:24:43Z

Thanks @pparent76 ! This works for Mist

I had it working with this staring script:

#!/bin/bash

ps -ae | grep geth
if [ "$?" -ne "0" ]; then
	geth  --syncmode "light"  &
	sleep 10;
fi
mist --light-node

alex-miller-0 · 2017-09-14T00:38:28Z

I got around this by running geth at the command line:

geth --light

And then opening the Ethereum wallet. It should automatically find your geth client by RPC.

But I very much agree with this issue. Ethereum Wallet should be doing light syncing by default.

HaleTom · 2017-09-24T11:33:19Z

As a work-around for linux users, based on @pparent76's script, I came up with:

#!/bin/bash
# Work around for issues:
# https://github.com/ethereum/mist/issues/2254
# https://github.com/ethereum/mist/issues/2372
# https://github.com/ethereum/mist/issues/2999
set -eu # For script robustness
geth=$(which geth)
mist=$(which mist) # Change to explicit path if you call this script "mist"

# Use pidof as procps' pgrep is broken:
# sleep 1& pgrep -ax '^sleep$' should return null
if ! geth_pid=$(pidof geth); then
  echo "Starting $geth."
  "$geth" --syncmode light &
else
  echo "Geth is already running with PID(s): $geth_pid"
fi

if ! mist_pid=$(pidof mist); then
  echo "Starting $mist."
  "$mist" --light-node
else
  echo "Mist is already running with PID(s): $mist_pid"
fi

Call the script "emist" so it doesn't recursively call itself :)

evertonfraga · 2017-10-19T18:48:55Z

From Mist 0.9.1 on, there's a light client option under Develop menu.

Please note there are still some bugs on the wallet when using Light Client. It will be reassessed when fixed.

jacktang · 2017-10-24T12:47:47Z

I have download 110G+ data, and I switch to light client mode, How to deal with the data under full node mode? Can I delete the data? or any script the remove the data?

alex-miller-0 · 2017-10-24T22:30:50Z

@jacktang The light client will create a different directory for the new data. Find the location of your Ethereum directory (see here) and navigate to /yourpath/Ethereum/geth. You will see two directories: chaindata and lightchaindata. If you only plan on using the light client from now on, you can remove chaindata and that should free up your 110GB 👍

mahmoudilyan · 2017-12-11T13:14:33Z

Does light client gets updated with the network?and can I do all the basic stuff inside it?

solderzzc · 2017-12-19T23:18:03Z

The chaindata is 167GB for now, it was taking 30+ days for me for the sync, if the procedure done faster, I would end up to sell them at $300...

mrspiderbrain · 2018-01-23T00:15:16Z

This would really help, the default install process looks all pretty but will fail on many people's hardware, or appear to fail due to the massive time required to sync.

cloudzhong · 2018-01-25T14:42:35Z

totally agree, meaningless for a wallet to sync so big data, it is not an node.

evertonfraga · 2018-01-25T18:04:13Z

The Light Client's discovery protocol is defective at this very moment, making it almost unusable. It is treated as "highly experimental" by its own developers.

Here in Mist we're coming up with some solutions, that include a remote node integration (like INFURA), which you can follow on this branch: https://github.com/ethereum/mist/tree/layered-nodes

We'll keep you all posted about this progress.

danielocdh · 2018-02-21T23:15:49Z

@evertonfraga where are you keeping us posted? thanks

evertonfraga added the v0.8.10 label Aug 14, 2017

evertonfraga self-assigned this Aug 15, 2017

evertonfraga added the Type: Enhancement label Aug 15, 2017

PatchRanger mentioned this issue Aug 17, 2017

No accounts in From dropdown at contract creation page #2938

Open

Swift42 mentioned this issue Aug 29, 2017

Wallet cannot light sync #2999

Closed

HaleTom mentioned this issue Sep 24, 2017

Starting mist in light mode does not work since geth 1.6.0 (conflicting node options?) #2254

Closed

mist-bot bot added the Status: Triage label Jan 26, 2018

alexvandesande closed this as completed Jan 26, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ethereum-wallet should default to light client mode #2372

Ethereum-wallet should default to light client mode #2372

jtoomim commented May 29, 2017

paddycy commented May 29, 2017

housemobile commented May 30, 2017

jtoomim commented May 30, 2017 •

edited

Loading

MaximRunev commented Jul 6, 2017

User195 commented Jul 19, 2017

jtoomim commented Jul 19, 2017

pparent76 commented Jul 27, 2017 •

edited

Loading

muten85 commented Jul 27, 2017

pparent76 commented Jul 27, 2017

evertonfraga commented Jul 28, 2017

forest-hermit commented Jul 30, 2017

rodgermoore commented Aug 21, 2017

alex-miller-0 commented Sep 14, 2017

HaleTom commented Sep 24, 2017

evertonfraga commented Oct 19, 2017

jacktang commented Oct 24, 2017 •

edited

Loading

alex-miller-0 commented Oct 24, 2017

mahmoudilyan commented Dec 11, 2017

solderzzc commented Dec 19, 2017

mrspiderbrain commented Jan 23, 2018

cloudzhong commented Jan 25, 2018

evertonfraga commented Jan 25, 2018

danielocdh commented Feb 21, 2018

Ethereum-wallet should default to light client mode #2372

Ethereum-wallet should default to light client mode #2372

Comments

jtoomim commented May 29, 2017

paddycy commented May 29, 2017

housemobile commented May 30, 2017

jtoomim commented May 30, 2017 • edited Loading

MaximRunev commented Jul 6, 2017

User195 commented Jul 19, 2017

jtoomim commented Jul 19, 2017

pparent76 commented Jul 27, 2017 • edited Loading

muten85 commented Jul 27, 2017

pparent76 commented Jul 27, 2017

evertonfraga commented Jul 28, 2017

forest-hermit commented Jul 30, 2017

rodgermoore commented Aug 21, 2017

alex-miller-0 commented Sep 14, 2017

HaleTom commented Sep 24, 2017

evertonfraga commented Oct 19, 2017

jacktang commented Oct 24, 2017 • edited Loading

alex-miller-0 commented Oct 24, 2017

mahmoudilyan commented Dec 11, 2017

solderzzc commented Dec 19, 2017

mrspiderbrain commented Jan 23, 2018

cloudzhong commented Jan 25, 2018

evertonfraga commented Jan 25, 2018

danielocdh commented Feb 21, 2018

jtoomim commented May 30, 2017 •

edited

Loading

pparent76 commented Jul 27, 2017 •

edited

Loading

jacktang commented Oct 24, 2017 •

edited

Loading