Parity-ethereum: Compilation issues with Mist and parity running in geth compatibility mode
Cross-referencing this issue at request of @luclu
https://github.com/ethereum/mist/issues/1082
I was informed previously that Mist support may be abandoned, although it would be preferable to stay and quirks be sorted out.
D-Nice
All 2 comments
This issue is labelled with _annoyance_: The client behaves within expectations, however this "expected behaviour" itself is at issue. It's inactive since last year, neither assigned nor linked to any milestone.
@paritytech/core-devs Are we keeping geth and mist compatibilty or are we going to drop it at some point? Please, decide within 7 days on a deadline and add an assignee or close it otherwise. Thanks.
5chdn
on 10 May 2017
Hi there, just a side-note: we are currently refactoring the IPC endpoint selection in Mist the be node agnostic.
Once merged any node added to Mist's clientBinaries.json will be recognized with any arbitrary dataDir/ipc-socket/etc specified in the JSON file.
We would like to have Parity as a node option in Mist, but this would further require to download the binaries for all major OS as a archive (I couldn't find them for all OS).
Once we are ready I will ping you again on this in a more prominent way than this issue!
luclu
on 10 May 2017
Related issues
Michael2008S
·
3Comments
danfinlay
·
3Comments
tzapu
·
3Comments
BillSantos
·
3Comments
vmenond
·
3Comments
Most helpful comment
Hi there, just a side-note: we are currently refactoring the IPC endpoint selection in Mist the be node agnostic.
Once merged any node added to Mist's clientBinaries.json will be recognized with any arbitrary dataDir/ipc-socket/etc specified in the JSON file.
We would like to have Parity as a node option in Mist, but this would further require to download the binaries for all major OS as a archive (I couldn't find them for all OS).
Once we are ready I will ping you again on this in a more prominent way than this issue!