You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So as of now, all the major ETH node implementations support \n delimiter after every JSON message on their IPC socket.
The problem is. Some even require it. Geth and Nethermind at least won't ever reply to a request if it is not terminated with \n. For Geth the reason is they use the default JSON decoder from golang which is built for streams and needs a delimiter. Nethermind just hardcoded \n as their delimiter for IPC request handling.
Please fix this. Thanks a lot. Ethers.js is amazing
Code Snippet
No response
Contract ABI
No response
Errors
No response
Environment
Ethereum (mainnet/ropsten/rinkeby/goerli), node.js (v12 or newer), Geth, Other (please specify)
Environment (Other)
Nethermind
The text was updated successfully, but these errors were encountered:
Ethers Version
6
Search Terms
ipc,socket,json
Describe the Problem
So as of now, all the major ETH node implementations support \n delimiter after every JSON message on their IPC socket.
The problem is. Some even require it. Geth and Nethermind at least won't ever reply to a request if it is not terminated with \n. For Geth the reason is they use the default JSON decoder from golang which is built for streams and needs a delimiter. Nethermind just hardcoded \n as their delimiter for IPC request handling.
Please fix this. Thanks a lot. Ethers.js is amazing
Code Snippet
No response
Contract ABI
No response
Errors
No response
Environment
Ethereum (mainnet/ropsten/rinkeby/goerli), node.js (v12 or newer), Geth, Other (please specify)
Environment (Other)
Nethermind
The text was updated successfully, but these errors were encountered: