feat(blobs): Limit blob txs to ones with full network representation

[ryanschneider]

📝 Summary

This is an alternative to the no-fwd-blobs branch that filters blobs depending on whether or not they have the BlobTxSidecar available. If the sidecar is available then the blob is in the correct network representation form and can be collected and forwarded, otherwise the blob data is incomplete and shouldn't be forwarded.

2024-06-21T09:17:06.111-0700	DEBUG	processTx	{"tx_hash": "0x82161fd324f41f29fa8fdf0720938b946b37ea7f6fa051f74305dbd384ed624d", "source": "alchemy"}
2024-06-21T09:17:06.112-0700	DEBUG	error: invalid blob transaction	{"tx_hash": "0x82161fd324f41f29fa8fdf0720938b946b37ea7f6fa051f74305dbd384ed624d", "source": "alchemy", "reason": "missing blob sidecar"}

Notably the "full" newPendingTransactions subscription from Alchemy and Quiknode returns the incomplete blob. This is probably an upstream geth bug I'll see if it's possible for the subscription to contain the sidecar.

I haven't been able to test other node sources, but hopefully they return the full network representation.

⛱ Motivation and Context

Blobs come in two forms, there's the PoolTransactions network representation used in the mempool, and the blobless TransactionPayload format used in block bodies.

📚 References

• https://eips.ethereum.org/EIPS/eip-4844#networking
• feat(EIP-4844): eth.Transaction/Receipt EIP-4844 support INFURA/go-ethlibs#92

---

✅ I have run these commands

• make lint
• make test
• go mod tidy

[metachris]

thanks!