alchemy free tier

[ZzzzHui]

No description provided.

[miltonjonat]

Tried it out and I'm still getting the Alchemy errors. Do we need #59 as well to make it work?
Alternatively, maybe we could have some test to check that this is working as intended? @fabiooshiro what do you think?

[ZzzzHui]

Do we need #59 as well to make it work?

No we don't.

[miltonjonat]

Well, then the fix didn't work for me. Were you able to test it?

[fabiooshiro]

Tried it out and I'm still getting the Alchemy errors. Do we need #59 as well to make it work? Alternatively, maybe we could have some test to check that this is working as intended? @fabiooshiro what do you think?

I think we can go with your idea of having something like BATCH_SIZE or MAX_BLOCK_RANGE.
The env name is the most difficult part...

[miltonjonat]

Tried it out and I'm still getting the Alchemy errors. Do we need #59 as well to make it work? Alternatively, maybe we could have some test to check that this is working as intended? @fabiooshiro what do you think?

I think we can go with your idea of having something like BATCH_SIZE or MAX_BLOCK_RANGE. The env name is the most difficult part...

The Node is going to create that variable in some upcoming PR. That's not what I meant: I was asking if we could create a test for this specific scenario. As it stands, I understand @ZzzzHui ported the code change but wasn't able to test if it worked.

[miltonjonat]

@ZzzzHui you should be able to reproduce my test case (on Decaf) with the following parameters:

• Consensus address: 0xDa3d0547bB1AAa4feBb7599b8ad1871B15dF45bb
• App address: 0x21EF997AEa1A861c349Bd12d643701143495d158
• Template: echo-dapp

In the rollups-espresso-reader repo, if I have the docker compose up (pointing at Sepolia+Decaf), I can register the app like so:

docker compose exec cartesi_node_espresso cartesi-rollups-cli app register -v \
    -c 0xDa3d0547bB1AAa4feBb7599b8ad1871B15dF45bb \
    -a 0x21EF997AEa1A861c349Bd12d643701143495d158 \
    -n echo-dapp \
    -t applications/echo-dapp/

Hope that helps.

[fabiooshiro]

Ok, I will restore our decaf e2e test

[miltonjonat]

I tested again and @ZzzzHui is right: in my test scenario, InputBox inputs are being read ok with this PR. The issue is that I was using Node v2.0.0-alpha.4, which doesn't have the fix in its EvmReader, and that leads to Alchemy block range errors when checking for outputs. But the input reading part does seem ok.