Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Clean up VMC -> SMC and move it to sharding repo
See original GitHub issueWhat is wrong?
It’s better to compile the contracts on CI with Vyper and check the bytecode, and it’s not good to install Vyper in Py-EVM.
How can it be fixed
- Move VMC to sharding repo under
/contracts/directory. - Also, rename
Validator Manager Contract (VMC)toSharding Manager Contract (SMC).
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Automatically clean up after moving a project to a different shard
Moving a project from one shard to another leaves behind the repo on the original shard, and it isn't cleaned up automatically.
Read more >Ethereum Research Weekly Calls - HackMD
Reorganize/Clean up SMC and SMC handlers; Move SMC and handlers to sharding repo ... Catch up on sharding spec; Clean up casper repo...
Read more >Using Oracle Sharding - Database
Start the shard catalog database and local listener. Start the shard directors (GSMs). Start up the shard databases and local listeners. Start the...
Read more >Remove Shards from an Existing Sharded Cluster - MongoDB
To remove a shard you must ensure the shard's data is migrated to the remaining shards in the cluster. This procedure describes how...
Read more >4.4. Shard Management - CouchDB Docs
This document discusses how sharding works in CouchDB along with how to safely add, move, remove, and create placement rules for shards and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jamesray1 Thank you, but the step 3 task includes more than just Vyper contract, but also the SMC handler APIs. I’d say it’s better to let @NIC619 complete it.
In the meantime, I suggest you can start to write some component/library/APIs design like SMC handler logic in Rust for your implementation, and how it interacts with the main chain client.
For py-evm/eth-tester/py-evm dependent loop issue, it’s better to move SMC handler to sharding repo too. @mhchia what do you think about it?