gobitfly/etherchain-light

Lightweight Ethereum blockchain explorer

etherchain-light's Issues

Problems while cloning the submodules

Problem

While cloning the repository by using

git clone https://github.com/gobitfly/etherchain-light --recursive

It was giving following errors:

Cloning into 'utils/solc-bin'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of '[email protected]:ethereum/solc-bin.git' into submodule path 'utils/solc-bin' failed

Possible fix

We could use https instead of ssh while cloning submodules. I worked out this issue on my system by

• Clone the base repository using git clone https://github.com/gobitfly/etherchain-light
• Change the value of url in .gitmodules file to https://github.com/ethereum/solc-bin.git
• Update submodule:

   cd etherchain-light
   git submodule sync # This will update submodule url for 'utils/solc-bin'
   git submodule update # This will pupulate submodule
  

Error: invalid block number on several elements

#7 has been fixed, but with the current version I get Error: invalid block number again with clicks on almost every element: the miner hash, account hashes, etc.

Simple setup, PoA modeled after DemoPoA-tutorial of parity, all parameters set correctly from start of each of the two nodes. ipcpath points to first node.

Error: invalid block number
    at Object.InvalidResponse (/home/hal9000/parity/etherchain-light/node_modules/web3/lib/web3/errors.js:35:16)
    at Object.<anonymous> (/home/hal9000/parity/etherchain-light/node_modules/web3/lib/web3/requestmanager.js:86:36)
    at /home/hal9000/parity/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:66:44
    at Array.forEach (native)
    at Socket.<anonymous> (/home/hal9000/parity/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:50:47)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at Socket.Readable.push (_stream_readable.js:134:10)
    at Pipe.onread (net.js:548:20)

Insecure Credential Storage

Insecure Credential Storage
Vulnerable module: web3
Introduced through: [email protected]
Detailed paths
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected]
Overview
web3 is a JavaScript API which connects to the Generic JSON RPC spec.

Affected versions of this package are vulnerable to Insecure Credential Storage. The current implementation of web3.js could result in wallet decryption under certain circumstances. When a wallet is saved and encrypted into local storage, a private key is needed to load the wallet. However, this private key is available via LocalStorage and is readable in plaintext on a webpage after a wallet is loaded.

This implementation could be abused by an attacker through client-side attacks such as Cross-site Scripting (XSS) and could result in theft of a user's wallet private key.

App crashes when browsing to /accounts if there are no accounts.

Parity//v1.7.0-unstable-57770ce84-20170314/x86_64-linux-gnu/rustc1.15.1
Etherchain-light commit b9ea0dcf927676e0d53e5c2c972b8cd2e85b18a0

$ parity account list
[]

Browse to /accounts & the app crashes with:

/home/xxx/Development/TrekDev/etherchain-light/routes/accounts.js:20
      var lastAccount = accounts[accounts.length - 1];
                                         ^

TypeError: Cannot read property 'length' of null

PS. Big thanks for this app. Really useful for working through development issues on our private chains 👍

(Problem) Issue verifying a contract

1. Deploy any contract with 0.4.18
2. Try to verify it

Error during contract verification: module.js:472 throw err; ^ Error: Cannot find module './solc-bin/bin/soljson-v0.4.18-nightly.2017.10.16+commit.dbc8655b.js' at Function.Module._resolveFilename (module.js:470:15) at Function.Module._load (module.js:418:25) at Module.require (module.js:498:17) at require (internal/module.js:20:19) at Object.<anonymous> (/home/pool/etherchain-light/utils/compile.js:56:39) at Module._compile (module.js:571:32) at Object.Module._extensions..js (module.js:580:10) at Module.load (module.js:488:32) at tryModuleLoad (module.js:447:12) at Function.Module._load (module.js:439:3)

Update the demo

looks like light.etherchain.org is no longer available, I am wondering whether we could add a new demo?

Crash when opening contract hash after new contract is uploaded

I have set up two nodes node0 and node1 with parity by following their tutorial on Ubuntu 18.04. I have deployed a contract with python web3, and the contract successfully deployed and is displayed in the home of ethereum light.

But when I try to enter the hash page of the contract deployment transaction, etherchain-light crashes with the following error:
npm ERR! Linux 4.18.0-22-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: node ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'node ./bin/www'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the etherchain-light package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./bin/www
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs etherchain-light
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls etherchain-light
npm ERR! There is likely additional logging output above.

Why is this happening and how can I fix it? Thanks

Last Transactions is empty

I'm running a private Proof of Authority chain with Parity version Parity/v1.8.2-beta-1b6588c-20171025/x86_64-macos/rustc1.21.0.
I'm using config options from the README (--tracing=on --fat-db=on --pruning=archive).

I can see the list of all transactions, but when I open an account page, Last Transactions table is empty.

It is working correctly in the demo (https://light.etherchain.org/).

Tryed to connect with parity private blockchain. Returned with error.

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]prestart: [email protected]
6 info lifecycle [email protected]start: [email protected]
7 verbose lifecycle [email protected]start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/user1/etherchain-light-master/node_modules/.bin:/home/user1/bin:/home/user1/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle [email protected]start: CWD: /home/user1/etherchain-light-master
10 silly lifecycle [email protected]start: Args: [ '-c', 'node ./bin/www' ]
11 silly lifecycle [email protected]start: Returned: code: 1 signal: null
12 info lifecycle [email protected]start: Failed to exec start script
13 verbose stack Error: [email protected] start: node ./bin/www
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/user1/etherchain-light-master
16 verbose Linux 4.4.0-31-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v8.11.3
19 verbose npm v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: node ./bin/www
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

This is the log for the error in .npm Wondering if it has to due with my npm version please let me know.

etherchain-light should work in dev mode

When starting parity in dev mode ("immediate mining"), I would like to use etherchain-light, but I get the following error on opening the index page:

invalid block number

Error: invalid block number
    at Object.InvalidResponse (/home/hal9000/etherchain-light/etherchain-light/node_modules/web3/lib/web3/errors.js:35:16)
    at Object.<anonymous> (/home/hal9000/etherchain-light/etherchain-light/node_modules/web3/lib/web3/requestmanager.js:86:36)
    at /home/hal9000/etherchain-light/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:66:44
    at Array.forEach (native)
    at Socket.<anonymous> (/home/hal9000/etherchain-light/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:50:47)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at Socket.Readable.push (_stream_readable.js:134:10)
    at Pipe.onread (net.js:548:20)

Invalid params when clicking on an account

Hi!

I've installed etherchain-light following the instructions and everything works fine but the account details screen. Home page is ok, I can navigate through blocks, but I cannot view details of an account. I'm always getting this error:

Invalid params
Error: Invalid params
    at Object.InvalidResponse (/home/poc/etherchain-light/node_modules/web3/lib/web3/errors.js:35:16)
    at /home/poc/etherchain-light/node_modules/web3/lib/web3/requestmanager.js:86:36
    at XMLHttpRequest.request.onreadystatechange (/home/poc/etherchain-light/node_modules/web3/lib/web3/httpprovider.js:118:13)
    at XMLHttpRequestEventTarget.dispatchEvent (/home/poc/etherchain-light/node_modules/xhr2/lib/xhr2.js:64:18)
    at XMLHttpRequest._setReadyState (/home/poc/etherchain-light/node_modules/xhr2/lib/xhr2.js:354:12)
    at XMLHttpRequest._onHttpResponseEnd (/home/poc/etherchain-light/node_modules/xhr2/lib/xhr2.js:509:12)
    at IncomingMessage.<anonymous> (/home/poc/etherchain-light/node_modules/xhr2/lib/xhr2.js:469:24)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)

Any idea on what could be going on? The only difference from the main config instructions is that instead of using IpcProvider in config.js I'm using HttpProvider.

A issue when I started it

it shows this error message:
IPC Connection Error { Error: connect EACCES /Users/peng/Library/Application Support/io.parity.ethereum/jsonrpc.ipc
but my Parity service already run.
By the way, how can I use the "localhost:8545" in the config file?

Geth Compatibility (Instead of Parity)

Is there anyway to make this block explorer work for geth nodes?

Note getting pending transactions while node is still syncing

Hi,

Explorer is working great except no pending transactions.
Should it be fully sync before able to get the pending?

Pending Transactions
Currently there are no pending transactions

Etherchain Light | Parity//v1.8.6-beta-2d051e4-20180109/x86_64-linux-gnu/rustc1.22.1 | 25 Peers connected

Thanks,
Ady.

Publish docker image

There are plenty of docker images available from forks of this repo, at various stages of up-to-dateness, but there doesn't seem to be any publicly available docker image built from this repo itself.

Would be nice to have that to easily be able to throw in a docker image of this in a docker-compose.

Doesnt handle accounts with alot of txs very well

Anytime I try to load an address with a ton of tx's like say, poloniex, it just bogs the script down and essentially kills it. Might be better to scan the chain from genesis and store all the chain data in mongo or something.

Apparently this has already been considered in the README.md
So it would be cool if there was a flag we could set in the config to make it run light or with a db.

Searching for an unknown hash makes the system go boom

Prototype Override Protection Bypass

Prototype Override Protection Bypass
Vulnerable module: qs
Introduced through: [email protected] and [email protected]
Detailed paths
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Overview
qs is a querystring parser that supports nesting and arrays, with a depth limit.

By default qs protects against attacks that attempt to overwrite an object's existing prototype properties, such as toString(), hasOwnProperty(),etc.

From qs documentation:

By default parameters that would overwrite properties on the object prototype are ignored, if you wish to keep the data from those fields either use plainObjects as mentioned above, or set allowPrototypes to true which will allow user input to overwrite those properties. WARNING It is generally a bad idea to enable this option as it can cause problems when attempting to use the properties that have been overwritten. Always be careful with this option.

Overwriting these properties can impact application logic, potentially allowing attackers to work around security controls, modify data, make the application unstable and more.

In versions of the package affected by this vulnerability, it is possible to circumvent this protection and overwrite prototype properties and functions by prefixing the name of the parameter with [ or ]. e.g. qs.parse("]=toString") will return {toString = true}, as a result, calling toString() on the object will throw an exception.

Example:

qs.parse('toString=foo', { allowPrototypes: false })
// {}

qs.parse("]=toString", { allowPrototypes: false })
// {toString = true} <== prototype overwritten

Arbitrary Code Injection

Arbitrary Code Injection
Vulnerable module: morgan
Introduced through: [email protected]
Detailed paths
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected]
Remediation: Upgrade to [email protected].
Overview
An attacker could use the format parameter to inject arbitrary commands.

Windows version?

Any possibility of a windows version or could you point me to something similar?
Thanks in advance.

Regular Expression Denial of Service (ReDoS)

Regular Expression Denial of Service (ReDoS)
Vulnerable module: debug
Introduced through: [email protected], [email protected] and others
Detailed paths
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected] › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Overview
debug is a JavaScript debugging utility modelled after Node.js core's debugging technique..

debug uses printf-style formatting. Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks via the the %o formatter (Pretty-print an Object all on a single line). It used a regular expression (/\s*\n\s*/g) in order to strip whitespaces and replace newlines with spaces, in order to join the data into a single line. This can cause a very low impact of about 2 seconds matching time for data 50k characters long.

CONNECTION ERROR: Couldn't connect to node on IPC.

work@server-0:~/etherchain-light$ sudo docker-compose up [sudo] password for work: Starting etherchain-light_etherchain-light_1 ... done Attaching to etherchain-light_etherchain-light_1 etherchain-light_1 | npm info it worked if it ends with ok etherchain-light_1 | npm info using [email protected] etherchain-light_1 | npm info using [email protected] etherchain-light_1 | npm info lifecycle [email protected]~prestart: [email protected] etherchain-light_1 | npm info lifecycle [email protected]~start: [email protected] etherchain-light_1 | etherchain-light_1 | > [email protected] start /usr/src/app etherchain-light_1 | > node ./bin/www etherchain-light_1 | etherchain-light_1 | IPC Connection Error { Error: connect ENOENT /root/.local/share/io.parity.ethereum/jsonrpc.ipc etherchain-light_1 | at Object._errnoException (util.js:1021:11) etherchain-light_1 | at _exceptionWithHostPort (util.js:1043:20) etherchain-light_1 | at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1175:14) etherchain-light_1 | code: 'ENOENT', etherchain-light_1 | errno: 'ENOENT', etherchain-light_1 | syscall: 'connect', etherchain-light_1 | address: '/root/.local/share/io.parity.ethereum/jsonrpc.ipc' } etherchain-light_1 | Error updating node status: Error: CONNECTION ERROR: Couldn't connect to node on IPC. etherchain-light_1 | at Object.InvalidConnection (/usr/src/app/node_modules/web3/lib/web3/errors.js:28:16) etherchain-light_1 | at IpcProvider._timeout (/usr/src/app/node_modules/web3/lib/web3/ipcprovider.js:150:48) etherchain-light_1 | at Socket.<anonymous> (/usr/src/app/node_modules/web3/lib/web3/ipcprovider.js:38:15) etherchain-light_1 | at emitOne (events.js:115:13) etherchain-light_1 | at Socket.emit (events.js:210:7) etherchain-light_1 | at emitErrorNT (internal/streams/destroy.js:64:8) etherchain-light_1 | at _combinedTickCallback (internal/process/next_tick.js:138:11) etherchain-light_1 | at process._tickCallback (internal/process/next_tick.js:180:9)

Geth Support

Hi is geth supported now ? and what about testrpc or a private network such as ganache ?

Styling bug

I saw that the styling of my local explorer was different that https://light.etherchain.org/. And i realized that it was pointing to a different bootstrap file. You should change https://github.com/gobitfly/etherchain-light/blob/master/config.js.example#L10 for this line

this.bootstrapUrl = "https://maxcdn.bootstrapcdn.com/bootswatch/3.3.7/paper/bootstrap.min.css

Thanks!

testrpc support?

I switched from IPC to Http Provider - works fine, but trufflesuite/ganache-cli-archive#363

Explorer crashes when searched hash is not found

The explorer crashes when a hash is returned as not found. There have been multiple instances to confirm this behavior. The error logs generated after the crash are as follows:

/home/ubuntu/ayushya/blockchainExplorer2/routes/tx.js:73
web3.trace.transaction(result.hash, function(err, traces) {
^

TypeError: Cannot read property 'hash' of null
at /home/ubuntu/ayushya/blockchainExplorer2/routes/tx.js:73:36
at nextTask (/home/ubuntu/ayushya/blockchainExplorer2/node_modules/async/dist/async.js:5297:14)
at next (/home/ubuntu/ayushya/blockchainExplorer2/node_modules/async/dist/async.js:5304:9)
at /home/ubuntu/ayushya/blockchainExplorer2/node_modules/async/dist/async.js:906:16
at Object.callback (/home/ubuntu/ayushya/blockchainExplorer2/routes/tx.js:70:9)
at /home/ubuntu/ayushya/blockchainExplorer2/node_modules/web3/lib/web3/method.js:142:25
at Object. (/home/ubuntu/ayushya/blockchainExplorer2/node_modules/web3/lib/web3/requestmanager.js:89:9)
at /home/ubuntu/ayushya/blockchainExplorer2/node_modules/web3/lib/web3/ipcprovider.js:66:44
at Array.forEach (native)
at Socket. (/home/ubuntu/ayushya/blockchainExplorer2/node_modules/web3/lib/web3/ipcprovider.js:50:47)

(Problem) Solc version management

Can you explain how to install all versions of solidity compiler and have them available locally?
What is your strategy?

Transactions visible only for configured IPC node

I have different nodes (node0 and node1, both mining/validating), if in the etherchain-light config I choose the IPC path for node0, if the validating account is on this node, all transactions of this account are shown, if I change to node1, only those transactions of the validating account in that node are shown.

As a result, the balance of all accounts is correct, but the transaction list is filtered according to the mining accounts of the node with the configured IPC path, even if I don't want to.

Might be a conceptual limitation, then please comment and close issue.

support multiple OS

For mac OSX, I had to change config file to:

this.ipcPath = process.env["HOME"] + "/Library/Application Support/io.parity.ethereum/jsonrpc.ipc";

When trying to connect to ipc on parity 1.7.0-unstable

openethereum/parity-ethereum#5530

Accounts seem to load fine, everything else doesnt.

(Problem) When I clicked on txid from README.md

Cannot read property 'toString' of undefined
https://light.etherchain.org/tx/0x82da63f3d998415b748111e6f1d11051167fb995fdca990acd3cfd5a8b397c20

fatal: clone of solc-bin.git into submodule path

met a git clone problem.

System information

$ git version
git version 2.9.3

Steps to reproduce the behaviour

$ git clone https://github.com/gobitfly/etherchain-light --recursive
...
Submodule 'utils/solc-bin' ([email protected]:ethereum/solc-bin.git) registered for path 'utils/solc-bin'
Cloning into '/home/lin2/etherchain-light/utils/solc-bin'...
The authenticity of host 'github.com (192.30.253.112)' can't be established.
...
Please make sure you have the correct access rights and the repository exists.
fatal: clone of '[email protected]:ethereum/solc-bin.git' into submodule path '/home/lin2/etherchain-light/utils/solc-bin' failed

Any workaround for this issue?

$ cd etherchain-light/utils && git clone https://github.com/ethereum/solc-bin.git

Error during Contract verification

"Contract creation transaction not found"

I'm trying to verify the code for my contract, however when I submit the code I get this error:

Error during contract verification: Contract creation transaction not found

I can see the contract creation transaction, but it doesn't appear on the page for the contract account. How can I get etherchain to detect this transaction?

Issue connecting over IPC

this.ipcPath = "$HOME/.parity/jsonrpc.ipc";

$ ls -al $HOME/.parity/jsonrpc.ipc
srwxr-xr-x 1 pi pi 0 Mar 10 18:34 /home/pi/.parity/jsonrpc.ipc

$ PORT=3080 npm start

> [email protected] start /var/www/dev/etherchain-light
> node ./bin/www

IPC Connection Error { Error: connect ENOENT $HOME/.parity/jsonrpc.ipc
    at Object.exports._errnoException (util.js:1022:11)
    at exports._exceptionWithHostPort (util.js:1045:20)
    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1087:14)
  code: 'ENOENT',
  errno: 'ENOENT',
  syscall: 'connect',
  address: '$HOME/.parity/jsonrpc.ipc' }
Error updating node status: Error: CONNECTION ERROR: Couldn't connect to node on IPC.
    at Object.InvalidConnection (/var/www/dev/etherchain-light/node_modules/web3/lib/web3/errors.js:28:16)
    at IpcProvider._timeout (/var/www/dev/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:150:48)
    at Socket.<anonymous> (/var/www/dev/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:38:15)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at emitErrorNT (net.js:1278:8)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

etherchain.org issue

I don;t know whether I have the correct people or not, but here goes. I know nothing of coding, I just want to get my ETHER OUT of this platform and somewhere I can make use of it. CAN ANYBODY HELP OR AM I JUST SCREWED???

Contract State is empty

I am running a local version of the etherchain-light. After deploying a contract I verify it's source code (Solidity) which runs okay. I can then see the Code but Contract State is empty, and also ABI. Should I verify the contract in another way and maybe send the ABI somewhere to get to see everything?

parity data too big

At around no.2900000 block，about 9MB is needed every block. So if I want a full-blockchain of eth, about 8TB disk sized is needed. I think there must be something wrong about parity.

Trace's transaction hash is null and being used

In account.pug:47 the code #{trace.transactionHash.substr(0, 10)} fails with Cannot read property 'substr' of null. This happens on URL http://[explorer-domain]/account/[account-no]. The account in question is the etherbase account that Puppeth used to fill up with ether. Another account doesn't display this error.

etherchain-light should work in PoA-mode

possible dup to #6

etherchain-light shows this error after installing PoA according to https://github.com/paritytech/parity/wiki/Demo-PoA-tutorial

Error: invalid block number
    at Object.module.exports.InvalidResponse (/home/radgon/dev/ethereum/2017/parity/etherchain-light/node_modules/web3/lib/web3/errors.js:35:16)
    at Object.<anonymous> (/home/radgon/dev/ethereum/2017/parity/etherchain-light/node_modules/web3/lib/web3/requestmanager.js:86:36)
    at /home/radgon/dev/ethereum/2017/parity/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:66:44
    at Array.forEach (native)
    at Socket.<anonymous> (/home/radgon/dev/ethereum/2017/parity/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:50:47)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at readableAddChunk (_stream_readable.js:153:18)
    at Socket.Readable.push (_stream_readable.js:111:10)
    at Pipe.onread (net.js:534:20)

Regular Expression Denial of Service (ReDoS)

Regular Expression Denial of Service (ReDoS)
Vulnerable module: fresh
Introduced through: [email protected] and [email protected]
Detailed paths
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Introduced through: etherchain-light@gobitfly/etherchain-light#0163743bbd61c33ad71cb238ca4ea900fa922710 › [email protected] › [email protected] › [email protected] › [email protected]
Remediation: Upgrade to [email protected].
Overview
fresh is HTTP response freshness testing.

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks. A Regular Expression (/ *, */) was used for parsing HTTP headers and take about 2 seconds matching time for 50k characters.

Crash if open URL tranzaction type create

when opening a transaction link with a type create an application crashes with the error:

/var/lib/parity/etherchain-light/node_modules/levelup/lib/levelup.js:141
    throw new ReadError('get() requires a key argument')
    ^
ReadError: get() requires a key argument
    at LevelUP.get (/var/lib/parity/etherchain-light/node_modules/levelup/lib/levelup.js:141:11)
    at /var/lib/parity/etherchain-light/routes/tx.js:86:10
    at nextTask (/var/lib/parity/etherchain-light/node_modules/async/dist/async.js:5324:14)
    at next (/var/lib/parity/etherchain-light/node_modules/async/dist/async.js:5331:9)
    at /var/lib/parity/etherchain-light/node_modules/async/dist/async.js:969:16
    at Object.callback (/var/lib/parity/etherchain-light/routes/tx.js:83:9)
    at /var/lib/parity/etherchain-light/node_modules/web3/lib/web3/method.js:142:25
    at Object.<anonymous> (/var/lib/parity/etherchain-light/node_modules/web3/lib/web3/requestmanager.js:89:9)
    at /var/lib/parity/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:66:44
    at Array.forEach (<anonymous>)

Mining rewards are displayed twice

I fixed it just by removing all reward traces from data.tracesSent but it is probably the wrong way, not sure, that's why I won't submit a pull request, just yet.

Use this app on base path url

Hello,

I would like to use this app on a sub url like https://exemple.com/explorer/
I setup this app with an nginx reverse proxy. The proxy work, and I gan get the index page,
but every link are wrong and goes to https://exemple.com/block instead of https://exemple.com/explorer/block

I tried but I'm unable to (and don't have enough knowledge) to edit the app.js file successfully.
I tried to put a router with var router = express.Router();
and edit all routes to router.use('/block', block); and finally make the app use app.use('/explorer', router); but it's not working.

Could someone help me ?
Thanks

Nginx config

location /explorer/ {
                proxy_set_header Host $host;
		proxy_set_header X-Forwarded-Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_redirect         off;
                proxy_pass http://localhost:3000/;
}

error with contract verification ref #35

when attempting to add contract code, the compiler version only goes up to 0.4.19. as well, I get this error:

Error during contract verification: /bin/sh: /usr/bin/nodejs: No such file or directory

any help is much appreciated :)

(Problem) After verifying a contract, it's 502

https://light.etherchain.org/account/0x0190df91f46fe15717f7ba56ab71730e2e14802e

Error 502 Ray ID: 3c20e01e59ab41c3 • 2017-11-23 02:59:57 UTC
Bad gateway

ToDo: Intergrate abi-decoder

Use https://github.com/ConsenSys/abi-decoder to decode tx data and receipts in case a contract ABI is available

Error connecting to parity client 1.8.10

I am having an issue when starting etherchain, also when launched from Docker, so I suspect it's maybe related to the version of parity? Any idea how to fix this?

npm start

[email protected] start /Users/jeroen/dev/mola/etherchain-light
node ./bin/www

timers.js:394
throw new TypeError('"msecs" argument must be a number');
^

TypeError: "msecs" argument must be a number
at Object.exports.enroll (timers.js:394:11)
at Socket.setTimeout (net.js:388:12)
at ClientRequest. (_http_client.js:727:10)
at Object.onceWrapper (events.js:314:30)
at emitOne (events.js:120:20)
at ClientRequest.emit (events.js:210:7)
at tickOnSocket (_http_client.js:652:7)
at onSocketNT (_http_client.js:668:5)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

what's the version of your web3

cause the code now
is not compatible with the current web3
a lot of errors
like

Error: The method trace_block does not exist/is not available
    at Object.InvalidResponse (/home/user/Downloads/etherchain-light/node_modules/web3/lib/web3/errors.js:35:16)
    at Object.<anonymous> (/home/user/Downloads/etherchain-light/node_modules/web3/lib/web3/requestmanager.js:86:36)
    at /home/user/Downloads/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:66:44
    at Array.forEach (native)
    at Socket.<anonymous> (/home/user/Downloads/etherchain-light/node_modules/web3/lib/web3/ipcprovider.js:50:47)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at Socket.Readable.push (_stream_readable.js:134:10)
    at Pipe.onread (net.js:547:20)

Does etherchain-light work with geth?

I am using a private ethereum network. I boost my node by using geth. If I run geth on the background instead of parity would it work? Thank you.