Timeline for GETH Proper Way of Setting --ws.origins
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2021 at 19:55 | review | Close votes | |||
| Feb 4, 2021 at 4:13 | |||||
| Jan 27, 2021 at 19:39 | comment | added | clement | Does this answer your question? Geth can't connected to via Websocket | |
| Jan 27, 2021 at 15:43 | comment | added | ceds | @SimonR do you have any experience with web3-eth-admin? IPC works fine for normal web3 but throws crazy errors for the admin class | |
| Jan 27, 2021 at 15:18 | comment | added | ceds | Thanks man. You might actually have solved two problems for me here | |
| Jan 27, 2021 at 15:17 | comment | added | SimonR | You can. IPC is generally the way to go if the application sits on the same machine as geth. It's faster, and security is much improved. Check out 'web3.js IPCProvider'. | |
| Jan 27, 2021 at 15:14 | comment | added | ceds | I'm also assuming IPC might give a performance boost ? | |
| Jan 27, 2021 at 15:12 | comment | added | ceds | That's a good question. I've always used WSS. Apologies my technical expertise on this is... not the greatest. Can I use IPC with web3.js ? | |
| Jan 27, 2021 at 15:11 | comment | added | SimonR | Is there a particular reason not to use IPC in this case? | |
| Jan 27, 2021 at 15:10 | history | asked | ceds | CC BY-SA 4.0 |