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
Create a cluster with at least 50gb memory (30 if ur just experimenting).
Copy the .env file and enter your information under ATLAS
Aquire the necessary amount of RPC API keys. Yes even pokt, however you might he able to get away sticking a different provider. This is more to spread out your chances of getting rate limited (lol)
Buy premium Etherscan API. You will get rate limited otherwise and you might find it useful idk.
6a. configure RPCs under the .env file
6b. npm run init-db
In a separate shell instance (or tmux or nohup) start these processes:
init-common
init-mempool
init-txs
Visit Blocknative.com and then realize they have exactly this fucking mempool explore with much richer and pretty GUI and not shitty mongodb.
Cry havoc and let slip the bots of war.
The text was updated successfully, but these errors were encountered:
{"status": "pending"}// pending state otherwise its not in the mempool{"baseFeePerGas": "<50","_not": true}// baseFeePerGas no tx's under 50 plz{"type": {"gt": 0}}// greater than 0, meaning non-legacy tx'
Sign up for mongodb's managed service Atlas.
Create a cluster with at least 50gb memory (30 if ur just experimenting).
Copy the .env file and enter your information under ATLAS
Aquire the necessary amount of RPC API keys. Yes even pokt, however you might he able to get away sticking a different provider. This is more to spread out your chances of getting rate limited (lol)
Buy premium Etherscan API. You will get rate limited otherwise and you might find it useful idk.
6a. configure RPCs under the
.env
file6b.
npm run init-db
In a separate shell instance (or tmux or nohup) start these processes:
init-common
init-mempool
init-txs
Visit Blocknative.com and then realize they have exactly this fucking mempool explore with much richer and pretty GUI and not shitty mongodb.
Cry havoc and let slip the bots of war.
The text was updated successfully, but these errors were encountered: