Additional requests while preparing transaction

[sim31]

When making eos.transaction() call with eos returned from scatter it makes a bunch of get_info/get_block/get_abi requests:

When using [email protected] directly, however it's much better:

Plus I was able to reduce additional requests to just only one get_abi call, by providing transaction headers myself. Through scatter only one get_block request is saved this way.

Is where anyway to reduce the overhead?

Btw, does scatter have it's own version of eosjs which it uses? Because it looks a lot like this issue, which appears to be almost fixed in newest eosjs.

[nsjames]

I'd suggest tagging onto the ticket I created on eosjs (EOSIO/eosjs#208). There's really nothing Scatter can do about this. Scatter already caches ABIs on our side but all those requests are coming from eosjs alone. I agree, it's a problem which needs a solution.

[sim31]

Why I don't see that many unnecessary requests when using eosjs directly?

[nsjames]

Hmm, let me run some tests.
Scatter shouldn't be doing anything with get_block or get_info, and even if it does it does so through your injected eosjs which will match your version. I'll reopen for now and debug though.