News for hackers. Stuff that matters.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by dannyw on Monday May 03, 2021 @04:55AM (#27022917)
It's not black and white. Would 2MB blocks (and hence 10GB of disk space) be a worthy trade off?

The problem I see is bitcoin devs refusing to be pragmatic. Segwit is just an accounting trick.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by xorcist on Monday May 03, 2021 @08:24AM (#27024149)
Not sure what an accouting trick is, but it might be interesting to note that Bitcoin right now averages 1.4MB blocks.

Would 2MB be preferable? Would it be useful? Just the same magnitude of transactions that visa settles would require slightly above 500MB sized blocks, and that's without any more sophisticated transactions such as atomic swaps, which could potentially be useful.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by rocqua on Monday May 03, 2021 @05:06AM (#27022969)
I believe the point of segwit is more than accounting. Essentially these signatures /spend-scripts are pruneable once the blocks they are in are old enough.

After all, if a transaction had an invalid spend script, it would not have gotten 100 blocks worth of confirmations.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by csomar on Monday May 03, 2021 @05:13AM (#27023011)
Bitcoin has checkpoints: https://bitcoin.stackexchange.com/questions/1797/what-are-ch... even for normal P2PK transactions.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by nullc on Monday May 03, 2021 @07:50AM (#27023895)
Checkpoints don't do what you think they do.

They only exist today as a mechanism to prevent nodes from being flooded by low difficulty fork blocks, forking off back before height 230k, because the initial difficulty of Bitcoin (2^32 hash operations per block) is too low relative to multiple TH/s asic mining devices.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by keymone on Monday May 03, 2021 @08:31AM (#27024207)
is there any ongoing work to have utxo set commitments? if not - why?
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by nullc on Monday May 03, 2021 @09:18AM (#27024660)
I'm not sure, I haven't been actively involved in development for a couple years.

There were a couple distinct activities. One is the rolling utxo hashes, which has no major engineering hurdles, and can allow a compromised security "bootstrap from a utxo set".

The other are schemes that allow nodes to not have the utxo set but still validate-- these have historically had unfavorable IO costs, and the bandwidth storage tradeoff hasn't seemed that appealing-- e.g. would you find reducing storage from 10 GB to 1MB but at a cost for increasing bandwidth 10x to be appealing? In some applications it would be, not others.

I believe work related to both has been ongoing, however.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by keymone on Monday May 03, 2021 @09:41AM (#27024952)
> compromised security "bootstrap from a utxo set"

could you elaborate what's compromised about including a sha256 of utxo set in every block and allowing users to choose how far back they want to bootstrap from?

isn't it strictly better than current situation with assumevalid?

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by nullc on Monday May 03, 2021 @10:54AM (#27025818)
Depending on a utxo state in blocks is effectively the SPV security model, -- it's an utter blind trust in miners to set the value honestly. Something which is only theoretically sound on the assumption that someone else is checking.

If you're happy with the spv security model-- perhaps you should be using SPV? :) This is a little trite I know, because it's not quite identical because of the "past": but the vast majority of the sync time is in the last two years in any case, and practical considerations mean you wouldn't be able to just arbitrarily choose how far to sync from (as you need to be able to get the utxo set as of that height).

In the ethereum world effectively almost all synchronization is done using 'fast sync' which is essentially the committed utxo blindly trust miners model. Performance and storage considerations mean you can't go back more than a tiny amount of time (I believe its normally 4 hours). Many commercial entities operate with multiple nodes and if they detect they've fallen behind they just auto-restart and fast sync to catch back up. Effectively this means that if miners commit invalid state they'll just blindly accept it after a couple hours outage.

All assumevalid is doing is asserting that the ancestors two weeks back and further of a specific block hash all have valid signatures. When you get a setting there as part of the software you're running you're assuming that the software isn't backdoored (e.g. because of a public review process, or your own review). Assumevalid is strictly easier to review than pretty much any other aspect of the software integrity. E.g. there are 100 places where a one character change would silently bypass validation completely. Reviewing AV simply requires checking that the value set in it is an accepted block in some existing running node. AV as implemented also requires the blockchain to agree and have two weeks of work ontop of it, so it's just in every way harder to undermine validation by messing with it than changing the code some other way.

On a technically pedantic point. It takes a minute or so to sha256 the UTXO set, so doing literally what you suggest would utterly obliterate validation performance. (fortunately rolling hashes accomplish what you mean without the huge performance hit.)

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by keymone on Monday May 03, 2021 @11:09AM (#27026067)
thanks for detailed response!

> Depending on a utxo state in blocks is effectively the SPV security model, -- it's an utter blind trust in miners to set the value honestly

if it was hardforked in as part of consensus protocol - miner's wouldn't be able to set invalid utxo set hash any more than they are able to "produce" blocks with invalid signatures, or am i missing something?

as for storage and performance, maybe it would make sense to take the performance hit of maintaining a persistent immutable set such that you would be able to travel back as far as you like with minimal overhead.

do you know of any active PRs/branches where utxo commitment work is/has been happening?

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by nullc on Monday May 03, 2021 @11:16AM (#27026163)
They can produce blocks with invalid signatures, but they're stopped by nodes validating. But if instead of validation nodes skip blocks and use a commitment to the state, then they're not validating anymore. How that fails is why I gave the ethereum example, because I think the security has actually practically failed there-- just not been exploited yet.

> as for storage and performance, maybe it would make sense to take the performance hit of maintaining a persistent immutable set such that you would be able to travel back as far as you like with minimal overhead.

The cost of supporting that arbitrarily would be extremely high over and above the cost of having the complete blockchain. I don't see why anyone would choose to run a node to serve that. I certainly wouldn't-- it's obnoxious enough just to have an archive node. But having some periodic snapshots would probably be fine ... but not that many since each would be on the order of 7GB of additional storage.

No, there is work ongoing I haven't been following closely. Sounds like you're more interested in the assumeutxo style usage, so search for that and muhash.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by csomar on Monday May 03, 2021 @05:12AM (#27023002)
2 MB doesn't solve the issue, does it? Bitcoin is having exponential growth. You don't go for a hard-fork to just "double" the capacity. If the hard-fork was promising x100-x1.000 capacity, I'd imagine it being less contentious.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by riffraff on Monday May 03, 2021 @06:30AM (#27023405)
> Bitcoin is having exponential growth

in number of transactions? I do not think so, and according to the first few results I've found[0][1] it's not true.

[0] https://www.statista.com/statistics/730806/daily-number-of-b...

[1] https://bitcoinvisuals.com/chain-tx-day

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by keymone on Monday May 03, 2021 @08:29AM (#27024196)
yes, in number of transactions. just realize that if bitcoin went unlimited, most of the altcoin activity would be happening on bitcoin chain. blockchain space being limited resource priced out economically un-viable activity into shitcoins.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by riffraff on Monday May 03, 2021 @12:28PM (#27027091)
I linked two sources that show the number of transactions is not increasing exponentially.

What source do you base your claim that they are?

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by keymone on Monday May 03, 2021 @12:37PM (#27027210)
did your sources include all the activity on all of the altcoins?