The current version of ORMP is designed with L1 layer in mind, storage is expensive and calldata is cheap, but now for L2 or even L3 chain, calldata is more expensive than storage, so consider to implement ORMPL2 with storage query instead of indexing version, which can greatly reduce the workload of L2/L3 integration.
Idea
The current version of ORMP is designed with L1 layer in mind, storage is expensive and calldata is cheap, but now for L2 or even L3 chain, calldata is more expensive than storage, so consider to implement ORMPL2 with storage query instead of indexing version, which can greatly reduce the workload of L2/L3 integration.