-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need an ETH node of our own to get away from infura #40
Comments
Temporary bandaid fix, run your own light eth node:
Then edit your .env file, replace the infura address with localhost. Might need to open ports in firewall too. Con: |
As @Andrew-Pohl pointed out the parity light client is not stable and deprecated https://github.com/openethereum/openethereum/issues/11681 |
Mine has been staying synched for over 24 hours straight now. Looks fine to me. Still keeping an eye on it though. Removing --no-warp seems to fix it.
|
I did notice this might be worth it for fuse. https://www.quiknode.io/pricing (the QuickNode dedicated) they say no rate limits and infinite calls per day. obviously running your own full node would be cheaper ($80-160 a month for a decent spec server). But this is fully managed!. |
I also tried with no-wrap I haven't seen the same syncing issue... yet! but looking at the logs it still misses blocks regularly: I've got a geth light node running now will see how that goes, seems ok so far but finding peers takes an age because full nodes don't service light nodes by default like parity, it's an opt in thing. |
I see there is a limit of 10Million request a day on their highest plan
…On Mon, 20 Jul 2020 at 12:15, Andrew-Pohl ***@***.***> wrote:
I did notice this might be worth it for fuse.
https://www.quiknode.io/pricing (the QuickNode dedicated) they say no
rate limits and infinite calls per day. obviously running your own full
node would be cheaper ($80-160 a month for a decent spec server). But this
is fully managed!.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADCGM6N6LOJRVIEDQ5GENELR4QDMFANCNFSM4N4NFK5A>
.
|
Hi Mark that's for the use of their API. Press the "quick node dedicated" tab 😊 |
Oh that's actually a good price - anyway i think we need to do it but not
right now. We need to make sure we are not creating a new problem by
jamming our own dedicated node
…On Mon, 20 Jul 2020 at 19:14, Andrew-Pohl ***@***.***> wrote:
[image: Screenshot_2020-07-20-17-14-04-03]
<https://user-images.githubusercontent.com/55916961/87960615-77201b80-caac-11ea-93b0-591b3ebd3cb6.jpg>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADCGM6PNBXGTWGURTJ52U53R4RUPPANCNFSM4N4NFK5A>
.
|
I really think a light mainnet node as part of quickstart is the way to go, as long as it works. No point in storing the entire mainnet blockchain since it is not even used by Fuse. Even if there is a problem with parity light client support might be worth fixing it ourselves. However, there may be implications I am not aware of so more research probably needed. |
My parity hasn't had the syncing issue but it is missing blocks regularly. if you try this python code you might see it on yours too: from web3 import Web3 web3Eth = Web3(Web3.HTTPProvider("{IP}")) while(True): My geth node is doing great now though takes ages to find peers though but at 7 now I'm switching servers next month might spec it up with a spare 1tb ssd and run a full node on it |
Are you sure it's not only pulling the blocks it needs to pull? |
nope it full on skips blocks :/. running that script where it's grabbing the latest block doesn't increase block by block it regularly jumps 2-5 blocks at a time. |
I thought maybe it only pulled blocks when they were requested. |
Would gladly pay a small fee for this as a validator. Better than someone from infura shutting me down one day demanding 1000s of dollars.
Also, infura is bad for eth.
The text was updated successfully, but these errors were encountered: