---
title: "BlockVectra Engineering (@blockvectra) | Hashnode"
description: "Engineering notes from BlockVectra. Read the latest articles by BlockVectra Engineering on Hashnode."
url: "https://hashnode.com/@blockvectra"
---

@blockvectra

# BlockVectra Engineering

@blockvectra · Joined October 2026

Engineering notes from BlockVectra

### [Check the sender when simulating OP cross-domain messages](https://blockvectra.hashnode.dev/check-the-sender-when-simulating-op-cross-domain-messages?utm_source=hashnode&utm_medium=feed)

Two simulations with the same destination and calldata can produce different outcomes when their execution origins differ. Before treating that difference as a contract failure, compare the sender con

3 min read · [blockvectra.hashnode.dev](https://blockvectra.hashnode.dev/check-the-sender-when-simulating-op-cross-domain-messages?utm_source=hashnode&utm_medium=feed)

[5d ago](https://hashnode.com/posts/check-the-sender-when-simulating-op-cross-domain-messages/6af6291fd6620b7fd0b9546e)

### [Verify Boba, Soneium and World Chain IDs with a JSON-RPC batch](https://blockvectra.hashnode.dev/verify-boba-soneium-and-world-chain-ids-with-a-json-rpc-batch?utm_source=hashnode&utm_medium=feed)

Before using an RPC endpoint, check that it serves the network you intended. A successful HTTP response alone cannot tell you that. For Boba, Soneium and World Chain mainnet, the expected chain IDs ar

3 min read · [blockvectra.hashnode.dev](https://blockvectra.hashnode.dev/verify-boba-soneium-and-world-chain-ids-with-a-json-rpc-batch?utm_source=hashnode&utm_medium=feed)

[6d ago](https://hashnode.com/posts/verify-boba-soneium-and-world-chain-ids-with-a-json-rpc-batch/6af56b69ce55d9e80dabe5f5)

### [Read RPC docs from Node.js with mcp-use—without a model or API key](https://blockvectra.hashnode.dev/read-rpc-docs-from-node-js-with-mcp-use-without-a-model-or-api-key?utm_source=hashnode&utm_medium=feed)

You can retrieve RPC setup documentation through MCP without starting a model-driven agent. This Node.js example lists the available documentation tools, searches for quickstart, and prints the Markdo

2 min read · [blockvectra.hashnode.dev](https://blockvectra.hashnode.dev/read-rpc-docs-from-node-js-with-mcp-use-without-a-model-or-api-key?utm_source=hashnode&utm_medium=feed)

[6d ago](https://hashnode.com/posts/read-rpc-docs-from-node-js-with-mcp-use-without-a-model-or-api-key/6af555abab05fad579ee8992)

### [Four transactions, eight transfers: an ERC-20 ingestion regression fixture](https://blockvectra.hashnode.dev/four-transactions-eight-transfers-an-erc-20-ingestion-regression-fixture?utm_source=hashnode&utm_medium=feed)

Run an offline Python check on eight real Base ERC-20 logs. Preserve multiple transfers per transaction with transaction hash and log index.

3 min read · [blockvectra.hashnode.dev](https://blockvectra.hashnode.dev/four-transactions-eight-transfers-an-erc-20-ingestion-regression-fixture?utm_source=hashnode&utm_medium=feed)

[Nov 8](https://hashnode.com/posts/four-transactions-eight-transfers-an-erc-20-ingestion-regression-fixture/6af0069d603b423303f457fb)

### [JSON-RPC batch responses: match by id, not array position](https://blockvectra.hashnode.dev/json-rpc-batch-responses-match-by-id?utm_source=hashnode&utm_medium=feed)

A strict, dependency-free correlator for out-of-order success and error replies

7 min read · [blockvectra.hashnode.dev](https://blockvectra.hashnode.dev/json-rpc-batch-responses-match-by-id?utm_source=hashnode&utm_medium=feed)

[Oct 20](https://hashnode.com/posts/json-rpc-batch-responses-match-by-id/6ad7c46c10246aa49334056d)
