testnet
testnet copied to clipboard
Parity support
child of #33
Interesting! Can you expand a little on this?
In order of priority we are working on cpp-ethereum, geth, and then parity/trinity. No one is working on parity support yet. Want to help? :)
We'll launch the alpha testnet using cpp-ethereum only but we'd love to add geth support shortly after, would be wonderful to also have parity support.
Sent via Superhuman ( https://sprh.mn/[email protected] )
On Fri, Jun 01, 2018 at 4:32 PM, Sergey Pepyakin < [email protected] > wrote:
Interesting! Can you expand a little on this?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub ( https://github.com/ewasm/testnet/issues/34#issuecomment-393986727 ) , or mute the thread ( https://github.com/notifications/unsubscribe-auth/ADKbNPHMnzT89-WzFV6md-pdbBfStRKaks5t4Za6gaJpZM4UXF0O ).
Q: how does this relate to the partity-wasm project?
@avive: A: no direct connection, this is about adding Ewasm support to Parity Ethereum. As for how much work this would take, and how much existing p-wasm work can be reused, @pepyakin and @sorpaas could speak to that.
From my point of view, it looks quite likely that we can reuse some parts of pwasm, so it shouldn't be a massive task.
I suppose starting a testnet signifies transition to a more stable state for the ewasm spec? If so, then we could try to start tackling this...
@pepyakin We're publicly launching a stable testnet at DevCon next week :) For now we'll only be using geth but it would be great to add parity at some point.
plus aleth! 😉
FYI - @ks started working on this.
@5chdn nice!