insecurity at national.shitposting.agency [ARCHIVE] on Nostr: ๐
Original date posted:2015-05-11 ๐ Original message:> So if the server pushes ...
๐
Original date posted:2015-05-11
๐ Original message:> So if the server pushes new block
> header candidates to clients, then the problem boils down to increasing
> bandwidth of the servers to achieve a tenfold increase in work
> distribution.
Most Stratum pools already do multiple updates of the header every block
period,
bandwidth is really inconsequential, it's the latency that kills. At the
present
time you are looking up to 15 seconds between the first and last pools
to push
headers to their clients for the latest block. It's sort of
inconsequential with
a 10 minute block time, but it cuts into a 1 minute one very heavily.
Some pools already don't do their own validation of blocks, but simply
mirror
other pools, pushing them to be even more latency focused will just make
this an
epidemic of invalidity rather than a solution.
> There are several proof-of-work cryptocurrencies in existence
> that have lower than 1 minute block intervals and they work just fine.
> First there was Bitcoin with a 10 minute interval, then was LiteCoin
> using a 2.5 interval, then was DogeCoin with 1 minute, and then
> QuarkCoin with just 30 seconds.
You can't really use these as examples of things going just fine. None
of these
networks see anything approaching the Bitcoin transaction volume and
none have
even remotely the same network size. Some Bitcoin forks use floats in
consensus
critical code and work "just fine", for the moment. We can't justify
poor
decisions with "but the altcoins are doing it".
Is there even a single study of the stale rates within these networks?
Published at
2023-06-07 15:34:42Event JSON
{
"id": "9f707b221ae9ee56b6128d09d231f2d9489adff917dfc077e18b9ad8209ab838",
"pubkey": "cff960fb6e3f0f23fff5e1473106242d03f259990b48657336eefdcc18ca4d35",
"created_at": 1686152082,
"kind": 1,
"tags": [
[
"e",
"94c939015842f61df2dc30f3a313a8b9830ba760a8155e60b0e804778d86edc0",
"",
"root"
],
[
"e",
"298118b5328d5eeaf604622dd37f845e19c779bec468d6e6e6c1be87a37db82a",
"",
"reply"
],
[
"p",
"1e54a6de7941fa2778512f8b39026a806a830835f3e28d29701b37064e5ed5f2"
]
],
"content": "๐
Original date posted:2015-05-11\n๐ Original message:\u003e So if the server pushes new block\n\u003e header candidates to clients, then the problem boils down to increasing\n\u003e bandwidth of the servers to achieve a tenfold increase in work\n\u003e distribution.\n\nMost Stratum pools already do multiple updates of the header every block \nperiod,\nbandwidth is really inconsequential, it's the latency that kills. At the \npresent\ntime you are looking up to 15 seconds between the first and last pools \nto push\nheaders to their clients for the latest block. It's sort of \ninconsequential with\na 10 minute block time, but it cuts into a 1 minute one very heavily.\n\nSome pools already don't do their own validation of blocks, but simply \nmirror\nother pools, pushing them to be even more latency focused will just make \nthis an\nepidemic of invalidity rather than a solution.\n\n\n\u003e There are several proof-of-work cryptocurrencies in existence\n\u003e that have lower than 1 minute block intervals and they work just fine.\n\u003e First there was Bitcoin with a 10 minute interval, then was LiteCoin\n\u003e using a 2.5 interval, then was DogeCoin with 1 minute, and then\n\u003e QuarkCoin with just 30 seconds.\n\nYou can't really use these as examples of things going just fine. None \nof these\nnetworks see anything approaching the Bitcoin transaction volume and \nnone have\neven remotely the same network size. Some Bitcoin forks use floats in \nconsensus\ncritical code and work \"just fine\", for the moment. We can't justify \npoor\ndecisions with \"but the altcoins are doing it\".\n\nIs there even a single study of the stale rates within these networks?",
"sig": "50e4a8a508a4bc1aea29001ddae01ee95e8fa03335f878193b0c522bd1439cc2decc95e3ce08357a9f8ada6c2ed77c2fe2a92a344b79b0d42567c35d03a7d7fb"
}