-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
PubSub Booster network integration #6418
Comments
@vyzo can you elaborate a bit how these agreements would look like and what exactly they are aiming to "peer"? |
@f8-ptrk sure. We want to peer the miner's full node (one of them suffices if they have multiple, they can do their own internal peering for their full nodes) with one of the boosters, and maintain this peering agreement indefinitely. Basically we need to get their full node multiaddr and have them configure a respective pubsub booster for direct peering. So let's say that we have full node
and the booster will have to add this to its config:
that's all it takes code wise. |
If this helps with increasing successful block rewards it is a very welcome change. Seems like lucky value for small and medium miners has dropped since Hyperdrive upgrade. |
Could you please provide the data source that drives up to this statement? |
i honestly doubt it. the math behind it hasn't changed. and if you are winning or not is a local calculation. if you mean "luck value" as in "blocks that made it onto the chain" - maybe. but the amount of blocks "small" miners are able to mine in theory is unaffected by network issues (you can win a block without even being online - you can't mine it, sure - but the win is the "luck" and not if it got on chain) |
A random sampling of miners with less than 200TiB (lucky value from Filflox) seems to suggest low successful block rewards: I hope it's just bad luck and it all evens out over time. Can't figure out why though. :-( |
For context, see protocol/web3-dev-team#104
Code related Action Items:
Deployment:
The text was updated successfully, but these errors were encountered: