iquidus

any preferences on flag naming for ethereum mainnet? `--ethereum` or `--foundation` ? edit: faucet already uses 'foundation', will stick with this.

update: staying inline with recent upstream additions, --mainnet will be used for ethereum mainnet. initial phase (no chain flag warn) has begun, see: https://github.com/etclabscore/core-geth/pull/319

update go.mod (missing deps [however they appear to already be in go.sum]) ``` go get github.com/naoina/go-stringutil go get github.com/steakknife/hamming ``` edit: this is likely a local issue on my end....

to chain config or ethash config? Ubiq migrated rewards to ethash config. https://github.com/ubiq/go-ubiq/blob/master/params/config.go#L68 https://github.com/ubiq/go-ubiq/blob/master/consensus/ubqhash/consensus.go#L622

Existing network support: ``` Ethereum network: pre-configured Ethereum Mainnet --classic Ethereum Classic network: pre-configured Ethereum Classic mainnet --mordor Mordor network: Ethereum Classic's cross-client proof-of-work test network --social Ethereum Social network:...

Ethash networks according to whattomine. These will be the easiest additional networks to support due to being ethash or minor ethash variants (similar to etchash). Adding support for everything however...

related PR: #362

It's not possible for the MEW team to move coins from any address, the server/nodes never see any private keys or wallet files, MEW does not hold any coins. Everything...

very strange, looking at the raw block and tx data, everything looks normal. Nothing comes to mind right now, i will need to investigate further.

just to confirm, you have txindex enabled? (although if you didnt, it would error out much sooner than that block)