You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently we fetching account and storage proofs fully depends on remote rpc call. ofc we do some tricks for parallel fetching to reducing this limitation. But ofc each I/O call takes like 300ms and we want more faster.. so could be one idea is to have sqlite db locally storing account/storage proofs and check the proofs first from sqlite ( in-memory/disk decidable ) and then if not exist fetch from rpc
The text was updated successfully, but these errors were encountered:
motivation
currently we fetching account and storage proofs fully depends on remote rpc call. ofc we do some tricks for parallel fetching to reducing this limitation. But ofc each I/O call takes like 300ms and we want more faster.. so could be one idea is to have sqlite db locally storing account/storage proofs and check the proofs first from sqlite ( in-memory/disk decidable ) and then if not exist fetch from rpc
The text was updated successfully, but these errors were encountered: