Skip to content
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

Open
CrackerHax opened this issue Jun 12, 2020 · 14 comments
Open

Need an ETH node of our own to get away from infura #40

CrackerHax opened this issue Jun 12, 2020 · 14 comments

Comments

@CrackerHax
Copy link

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.

@CrackerHax
Copy link
Author

Temporary bandaid fix, run your own light eth node:

sudo ./parity --no-warp --light --jsonrpc-interface all --jsonrpc-hosts all&

Then edit your .env file, replace the infura address with localhost. Might need to open ports in firewall too.

Con:
Sometimes light eth node will get stuck on an old block so needs to be restarted.

@leonprou
Copy link
Member

As @Andrew-Pohl pointed out the parity light client is not stable and deprecated https://github.com/openethereum/openethereum/issues/11681
Need to look for other alternatives

@CrackerHax
Copy link
Author

CrackerHax commented Jul 20, 2020

As @Andrew-Pohl pointed out the parity light client is not stable and deprecated openethereum/openethereum#11681
Need to look for other alternatives

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.

sudo ./parity --light db kill
sudo ./parity --light --jsonrpc-interface all --jsonrpc-hosts all&

@Andrew-Pohl
Copy link
Member

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!.

@Andrew-Pohl
Copy link
Member

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:
2020-07-20 10:52:09 Imported #10495456 0x2f34…1fc8 (11.90 Mgas)
2020-07-20 10:52:17 Imported #10495458 0x864d…afeb (11.90 Mgas)
2020-07-20 10:52:30 Imported #10495460 0xe460…74b1 (11.93 Mgas)

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.

@Marksmargon
Copy link

Marksmargon commented Jul 20, 2020 via email

@Andrew-Pohl
Copy link
Member

Andrew-Pohl commented Jul 20, 2020

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 😊

@Andrew-Pohl
Copy link
Member

Screenshot_2020-07-20-17-14-04-03

@Marksmargon
Copy link

Marksmargon commented Jul 21, 2020 via email

@CrackerHax
Copy link
Author

CrackerHax commented Jul 21, 2020

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.

@Andrew-Pohl
Copy link
Member

Andrew-Pohl commented Jul 22, 2020

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
import time

web3Eth = Web3(Web3.HTTPProvider("{IP}"))

while(True):
print("block: " + str(web3Eth.eth.getBlock("latest").number))
time.sleep(1)

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

@CrackerHax
Copy link
Author

My parity hasn't had the syncing issue but it is missing blocks regularly.

Are you sure it's not only pulling the blocks it needs to pull?

@Andrew-Pohl
Copy link
Member

My parity hasn't had the syncing issue but it is missing blocks regularly.

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.

@CrackerHax
Copy link
Author

I thought maybe it only pulled blocks when they were requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants