Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding a geth+wagon node to the testnet #99

Open
gballet opened this issue Nov 12, 2018 · 14 comments
Open

Adding a geth+wagon node to the testnet #99

gballet opened this issue Nov 12, 2018 · 14 comments
Assignees

Comments

@gballet
Copy link
Member

gballet commented Nov 12, 2018

No description provided.

@MaxGraey
Copy link

MaxGraey commented Nov 17, 2018

May be better life instead wagon? If you not yet starting progress in this direction

@lrettig
Copy link
Member

lrettig commented Nov 17, 2018

Does this refer to adding a node to the testnet?

@MaxGraey
Copy link

MaxGraey commented Nov 17, 2018

I'm not sure. life just is better alternative of wagon VM. It already great tuning for blockchain scope, has JIT, validate and decline wasm op codes which contain non-deterministic behaviour like float point op codes and etc. Also it tested even on AssemblyScript binaries. Actually perlin-network also using AS for its own contacts. But anyway it's just suggestion. May be wagon better align for your needs

@MaxGraey
Copy link

MaxGraey commented Nov 17, 2018

Actually I personally am a big fan of VMs based on Cranelift (developed by Mozilla and use Rust) like wasmer, wasmtime and Nebulet (run on Ring-0). But they are not yet mature

@gballet gballet changed the title Adding geth+wagon to the testnet Adding a geth+wagon node to the testnet Nov 17, 2018
@gballet
Copy link
Member Author

gballet commented Nov 17, 2018

@MaxGraey We already have a working implementation with wagon. Life sounds interesting, I will experiment with it next week. it shouldn't be too difficult to port the work I did on wagon.

@gballet gballet self-assigned this Dec 6, 2018
@gballet
Copy link
Member Author

gballet commented Dec 6, 2018

So this should be good to go (not with life, that's something for the next milestone). Waiting feedback on ewasm/go-ethereum#6 and ewasm/go-ethereum#1

@jwasinger
Copy link
Contributor

@gballet I'll deploy a geth+wagon node.

@jwasinger jwasinger self-assigned this Dec 8, 2018
@gballet
Copy link
Member Author

gballet commented Dec 8, 2018

@jwasinger ok, just to confirm: you need to use --vm.ewasm="metering:true" for it to work

@gballet
Copy link
Member Author

gballet commented Dec 8, 2018

./geth+wagon init ewasm-testnet-geth-config.json && ./geth+wagon --etherbase 0x9AfA52330797885BC7f6Df7b7d87835995d0f4f1 --rpc --rpcapi "web3,net,eth,debug" --rpcvhosts="*" --rpcaddr "0.0.0.0" --rpccorsdomain "*" --networkid 66 --bootnodes "enode://53458e6bf0353f3378e115034cf6c6039b9faed52548da9030b37b4672de4a8fd09f869c48d16f9f10937e7398ae0dbe8b9d271408da7a0cf47f42a09e662827@23.101.78.254:30303" --vm.ewasm="metering:true" --syncmode full --mine --miner.threads 1

is the exact command line that I use

@jwasinger
Copy link
Contributor

Thanks. I'll work on it in 10 hours (tomorrow).

@jwasinger
Copy link
Contributor

@gballet
Copy link
Member Author

gballet commented Dec 9, 2018

Very nice, thank you

@MaxGraey
Copy link

Great bench for different VMs:
https://github.com/fluencelabs/fluence/blob/master/bench/vm/README.md

Note: life in that research didn't use jit

@gballet
Copy link
Member Author

gballet commented Dec 13, 2018

thank you for this. This corresponds to what we're currently observing, although there are a lot of optimizations that we need to look into.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants