I found issue https://github.com/vechain/vechain-sdk-js/issues/480 by @rodolfopietro97, which mentions that hardhat does not rely on some functions, but I think a full RPC compatibility is what the SDK should aim for to open up to the whole EVM ecosystem, not just hardhat compatibility.
May I thereby also suggest to implement other functionality, which is in ethereums RPC documentation.
Basic Example
import { ThorClient, VeChainProvider } from "@vechain/sdk-network";
const thorClient = ThorClient.fromUrl("https://mainnet.vechain.org");
const provider = new VeChainProvider(thorClient);
const result = await provider.request({ method: "eth_getBlockReceipts", params: ["latest"] });
console.log("Successfully called eth_getBlockReceipts");
Summary
The RPC Provider fails with the latest graph node connectivity due a missing method implementation for
eth_getBlockReceipts
https://ethereum.github.io/execution-apis/api-documentation/ does list it as official API
I found issue https://github.com/vechain/vechain-sdk-js/issues/480 by @rodolfopietro97, which mentions that hardhat does not rely on some functions, but I think a full RPC compatibility is what the SDK should aim for to open up to the whole EVM ecosystem, not just hardhat compatibility.
May I thereby also suggest to implement other functionality, which is in ethereums RPC documentation.
Basic Example