pull down to refresh

2, your own and a miner, and then you connect to that miner. It's policy, not constrained by any threshold activation.
If you want to reliably be able to send a tx under the new policy, with outgoing connections only, at 32% adoption you would be able to do that reliably 95% of the time. With 125 connections, you need 0.3% adoption, much less than there is for v30 right now. But, you don't know how the v30 is configured.
For the inverse, to block every node with only outgoing transaction 95% of the time, you need about 99.4% of nodes to have a declining policy. With 125 connections, 99.96% of nodes is needed to block 95% of nodes from transmitting their txs.
So I need a newer SSD lol
reply
for your Pi4? No. You need someone to fix the regression. I'm working on it but if you know someone that can do it faster, I will not be upset, lol.
reply
what regression?
reply
The one where it takes up to 2 minutes to validate a block on a Pi4.
reply
when did it started? do you have some link about it? So that's why it's taking forever to sync on a rpi4 now?
reply
I shared it with you yesterday!!! #1269950
reply
Sorry my memory is almost dead, need more B12 lol
reply
No worries! Anyway, everyone is experiencing this on RPi4. I'll isolate it and propose either a fix to Core / Knots, or a patch if they don't want it.