Open alexauroradev opened 3 years ago
I've been thinking it's really unclear how to do this and still have a way to really verify anything.
Ignoring signatures there is no way to have NEAR accounts that match the addresses (as NEAR account -> to EVM address is a hash function) but also signed messages are not NEAR messages (tx, metatx) in any way.
To really test our implementation we need to have lots of inter-related contracts. It's possible to replace all accounts to NEAR accounts that the test facilitator controls. This will allow to re-sign transactions and submit them to NEAR.
The validation of the result though becomes more complex. The only thing possible to validate is that transaction that passed on Ethereum pass here.
At this point just running unit tests of a bunch (like a two dozens?) of projects seems like a more realistic goal for Phase 2.
@frankbraun, @artob, we do have an issue for EVM Bully. Should we move it to near-evm?
@djsatok, The EVM Bully is developed in https://github.com/near/evm-bully. Should we deal with EVM Bully related issues there?
Implement intellectual Ethereum -> NEAR EVM transaction feed with expected results