chainbound/fiber-rs

Fiber client in Rust

fiber-rs's Issues

doc: Missing imports in README example

I just noticed that the imports are missing in this example:
https://github.com/chainbound/fiber-rs?tab=readme-ov-file#send_transaction

use reth_primitives::TransactionSigned;

It should probably be like the following one:

use reth_primitives::{Transaction, TxEip1559, Address, TransactionKind, AccessList, Signature, U256, TransactionSigned};

Release v0.6.0 tasks

Tasks

Beta Give feedback

1. Update fiber-proto (git submodule update --remote fiber-proto)
2. Regenerate and implement the new gRPC bindings (in build.rs)
3. Implement only the non-deprecated streams
4. Add x-client-version header to all gRPC streams
5. Switch to reth-primitives for all transaction types (decode RLP into normal transaction, wrap with signer to form TransactionSignedEcRecovered)
6. Use https://github.com/ralexstokes/ethereum-consensus for consensus types
7. For transactions and blocks, have a "raw" variant that just returns the RLP / SSZ encoding

API

The api should expose the following methods:

• This should return the signed, recovered transaction. The sender is sent on the gRPC stream.
  • subscribe_transactions() -> impl Stream<Item = TransactionSignedEcRecovered>
• This should return a tuple of the sender and the raw RLP encoded transaction
  • subscribe_raw_transactions() -> impl Stream<Item = (Address, Bytes)>
• subscribe_execution_payloads() -> impl Stream<Item = ExecutionPayload>
• This should return the full SignedBeaconBlock.
  • subscribe_beacon_blocks() -> impl Stream<Item = SignedBeaconBlock>
• This should return the full SignedBeaconBlock but SSZ encoded.
  • subscribe_raw_beacon_block() -> impl Stream<Item = Bytes>

Pin all dependencies

Add a retry mechanism for underlying gRPC connection & streams

Transient network failures should not result in a permanent error, but should be retried

bug: `sendRawTransactionSequence` API response

When sending a transaction with the send_raw_transaction_sequence api, the transactions are actually propagated correctly but the API response format seems to be inconsistent for some reason. This error is returned:

thread 'tokio-runtime-worker' panicked at /usr/local/.../fiber-rs/src/lib.rs:282:46:
index out of bounds: the len is 0 but the index is 0

This is the corresponding code path:

fiber-rs/src/lib.rs

Lines 280 to 282 in d405281

	let res = rx.await?;
	let timestamp = res.sequence_response[0].timestamp;

Issues?

Any open issues to tackle?

docs: add Eip4844-related documentation

We need to document how Fiber handles Eip-4844 transactions. In short:

• subscribe_new_transactions: contains transactions of type 0, 1, 2, 3. Type 3 transactions here are without blobs.
• subscribe_new_blob_transactions contains only transactions of type 3 with blobs sidecar attached.

Migrate types to `alloy`

rETH integration