poa-chain-spec
poa-chain-spec copied to clipboard
JSON RPC request fails
Nifty or Metamask
window.ethereum.sendAsync(
{
method: 'eth_sendRawTransaction',
params: ["0xf86c80843b9aca00825208940039f22efb07a647557c7c5d17854cfd6d489ef38806d09918fdd148008081bda0afd64714f9de9131c87ac39cd81dea24e0bb5a3b513fa6a2b7d22ab425f16e9ba0068a1b2eddf2a29109c2f81ff6a44f106a1ac6abec5a676c0ccfed8174d83490"],
jsonrpc: '2.0',
from: "0xb036A9d5201f48c110692E8048EE784b988F6192"
}
request fails because it doesn't like from
field, while all other EVM networks are fine with this parameter
TO fix I had to omit the from
field
window.ethereum.sendAsync(
{
method: 'eth_sendRawTransaction',
params: ["0xf86c80843b9aca00825208940039f22efb07a647557c7c5d17854cfd6d489ef38806d09918fdd148008081bda0afd64714f9de9131c87ac39cd81dea24e0bb5a3b513fa6a2b7d22ab425f16e9ba0068a1b2eddf2a29109c2f81ff6a44f106a1ac6abec5a676c0ccfed8174d83490"],
jsonrpc: '2.0'
}
I think POA, SPOA, xDAI RPC endpoints should be compatible in terms of JSON RPC API
Hi @rstormsf On which network did you find this bug? I've tested Kovan and Sokol and I haven't reproduced this. Could you re-check please? Maybe the bug is already fixed
could be