search

aurora-is-near / aurora-engine

⚙️ Aurora Engine implements an Ethereum Virtual Machine (EVM) on the NEAR Protocol.
https://doc.aurora.dev/develop/compat/evm
322 stars 79 forks source link

Looking for devs to answer a couple questions about Sputnik (rust EVM) for parrellized evm proof of concept #887

Closed moskalyk closed 6 months ago

moskalyk commented 6 months ago

Hey there, I'm looking to get in contact with a either a specific dev from the ecosystem: https://github.com/mrLSD or someone who might have the knowledge to accomplish a specific goal with Sputnik or even maybe extend a version to support the function I’m looking for

They did some work on this it seems, and seems somewhat in the ecosystem, so I thought I'd try asking: https://github.com/aurora-is-near/sputnikvm

Or, if someone else has knowledge on how to do certain things like get state from the storage BTree of the executor... The backend variable seems private right now. My goal is to combine multiple VM states in a proof of concept that uses a parrelized just-in-time approach to execute call transactions, by stringifying the state and passing storage p2p

it’s funny, I think the most minimal architecture for this network would look like the near logo.

Thanks, morgan

birchmd commented 6 months ago

Hi @moskalyk

This repository is not the best place for such requests. Please limit issues here to technical problems with Aurora Engine.

As for your question about SputnikVM, the Backend is a trait which you can implement with any type you want. You should be able to accomplish your PoC without changes to SputnikVM. For example if you want both the Executor and some other part of the application to have access to the same storage type (call it say CustomStorage) then you could implement the Backend trait for Arc<CustomStorage> to share the same underlying storage with both the Executor and anything else.