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
How come that https://mempool.space has so fast propagation to pick up new transactions?
When I run my local full node with 125 peer limit on 100Mbit net I receive the transactions 5-10seconds later after they show up on site.
(I already use zmq, not rpc polling)
Mine is pruned, but that shouldn't affect reception, ram usage is only 3%, cpu is at max 5%, and chain is on SSD.
Is there a secret list of fast nodes? I read the nodes delay broadcasting by random 5seconds to prevent pin pointing, but that wouldn't affect reception on other side.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
How come that https://mempool.space has so fast propagation to pick up new transactions?
When I run my local full node with 125 peer limit on 100Mbit net I receive the transactions 5-10seconds later after they show up on site.
(I already use zmq, not rpc polling)
I don't see anything extra in bitcoind parameters:
https://github.com/mempool/mempool/blob/d0ad4742c14a1d10fee90a18720dea931328db31/production/linux/bitcoin.service
Mine is pruned, but that shouldn't affect reception, ram usage is only 3%, cpu is at max 5%, and chain is on SSD.
Is there a secret list of fast nodes? I read the nodes delay broadcasting by random 5seconds to prevent pin pointing, but that wouldn't affect reception on other side.
Beta Was this translation helpful? Give feedback.
All reactions