Separate Shomei RPC for Linea

[adraffy]

• added setShomeiURL() to LineaRollup
• added optional shomeiProvider to LinearProver

Note: this is untested because I don't have a Shomei provider to test.

Note: the tests only fail because of Sepolia (Pectra) which is fixed in BoLD PR.

---

Ideally, I would remove the linea_getProof workaround here and here and force the developer to supply two RPCs. The problem is: the Shomei RPC needs to have batching disabled and URG design makes no assumptions about the choice of providers. So I made it optional, and keep GatewayProvider workaround to fix the batch issue.

[clowestab]

What is the context to this separation? As I understand the RaaS providers working with Linea (namely Infura) simply proxy requests through to the Shomei nodes. Is this simply intending to remove the additional step?

I note that Shomei is still laggy - we still get BLOCK_MISSING_IN_CHAIN - block is missing errors regularly.

I feel like for this use case Linea simply isn't 'production ready' for this use case at this point due to the centralisation and time-lag unreliability of proof generation. Thoughts?

[adraffy]

Block missing even with the latest version? What RPC? We have that proof check so a failure would mean two differently synced nodes are replying to requests from the same IP?

[adraffy]

Maybe isShomeiReady() needs a real address?