Open Aursen opened 8 months ago
I am not sure what this would involve but it sounds like a lot of work.
Also if possible I strongly recommend a second crate composing on top of litesvm instead of a feature flag
IMO, this is not a huge task.
We have to implement a lite-weight version of the plugin-manager
and slightly modify the existing code (accounts_db.rs
for update_account
notification and so on). I'd like to take part in the realization of this enhancement, and maybe split it into a couple of deployable steps, like:
IMO, this is not a huge task. We have to implement a lite-weight version of the
plugin-manager
and slightly modify the existing code (accounts_db.rs
forupdate_account
notification and so on). I'd like to take part in the realization of this enhancement, and maybe split it into a couple of deployable steps, like:
- plugin-manager
- accounts
- txs
- slots
Amazing to know, a lot of plugin use the local client too. Maybe can we integrate a lite server for this case too
@Aursen, yeah, you mean having an opportunity to fetch get_balance
, get_account
, and so on, that are pointing to the HashMap<Pubkey, AccountSharedData>
instead of Banks
fork, right?
@Aursen, yeah, you mean having an opportunity to fetch
get_balance
,get_account
, and so on, that are pointing to theHashMap<Pubkey, AccountSharedData>
instead ofBanks
fork, right?
Yep that's the idea
At the moment, we have no way of using geyser plugins with LiteSVM. This may be useful for testing programs like Clockwork. Put it behind a feature flag