feat(rpc): Setup RPC Crate #35
Conversation
|
Going to cut this off here with |
| /// An implementation of the [`RollupNodeServer`] trait. | ||
| #[derive(Debug, Clone)] | ||
| pub struct RollupNodeRpc { | ||
| /// The version of the node. | ||
| version: String, | ||
| } | ||
|
|
||
| #[async_trait] | ||
| impl RollupNodeServer for RollupNodeRpc { | ||
| async fn op_output_at_block( | ||
| &self, | ||
| block_number: BlockNumberOrTag, | ||
| ) -> RpcResult<OutputResponse> { | ||
| trace!("op_output_at_block: {:?}", block_number); | ||
| unimplemented!() | ||
| } | ||
|
|
||
| async fn op_safe_head_at_l1_block( | ||
| &self, | ||
| block_number: BlockNumberOrTag, | ||
| ) -> RpcResult<SafeHeadResponse> { | ||
| trace!("op_safe_head_at_l1_block: {:?}", block_number); | ||
| unimplemented!() | ||
| } | ||
|
|
||
| async fn op_sync_status(&self) -> RpcResult<SyncStatus> { | ||
| unimplemented!() | ||
| } | ||
|
|
||
| async fn op_rollup_config(&self) -> RpcResult<RollupConfig> { | ||
| unimplemented!() | ||
| } | ||
|
|
||
| async fn op_version(&self) -> RpcResult<String> { | ||
| Ok(self.version.clone()) | ||
| } | ||
| } |
There was a problem hiding this comment.
usually rpc extensions contain have a reth Provider, where various on disk information can be fetched. I'm assuming this rpc will be used either in the standalone binary or in the exex. For the standalone binary, I am guessing that the L1 RPC will be used for this, making the reth Provider traits the wrong abstraction. So maybe an enum would have to implement fetching each type of data:
enum ProviderType<RP, AP> {
Local(RP), // reth provider
Network(AP) // alloy provider
}lmk if my understanding is off. There are probably other ways to implement this as well
Just to confirm: the op_output_at_block and op_safe_head_at_l1_block seem like the only two things that would need to fetch information from the L1 node?
Description
Sets up an
rpccrate.Metadata
#7