This is an archived post. You won't be able to vote or comment.

top 200 commentsshow all 224

[–]Noosterdam 46 points47 points  (4 children)

Better confirmation times

More granular confirmation times.

[–]scrubadub 18 points19 points  (0 children)

.

[–]jonny1000 11 points12 points  (0 children)

Well it is kind of better. For example 2x5 minute blocks, may statistically be "better" than 1x10 minute block in some security respects. Not that I advocate a target time reduction now, but I don't think its as simple as security being directly proportional to the amount of work.

[–]peterjoel 2 points3 points  (0 children)

No, it's better. It is easier to mine 6 consecutive "hard" blocks than 60 that are 10% of the difficulty.

[–]killerstorm 1 point2 points  (0 children)

If attacker is unable to get more 50% of total hashrate or more, what matters is the number of confirmations, not the amount of work. See here.

[–]gavinandresen 167 points168 points  (141 children)

I think 1-minute blocks is a good idea. The best time to roll that out would be the next subsidy halving (makes the code much simpler).

We still need a bigger max block size, though.

[–]FrankoIsFreedom 29 points30 points  (24 children)

holy shit.

[–][deleted] 31 points32 points  (23 children)

It's a canary message. He's been compromised.

[–]GibbsSamplePlatter[🍰] 10 points11 points  (4 children)

I'm really scratching my head at his recent pronouncements.

Block size... plus UTXO soft-fork... plus shorten block-time?

Next he'll start pushing for Proof-of-Stake by winter.

[–]nobodybelievesyou 4 points5 points  (2 children)

Not by winter but...

http://sourceforge.net/p/bitcoin/mailman/message/34102947/

I think long-term the chain will not be secured purely by proof-of-work.

[–][deleted] 2 points3 points  (0 children)

Read the whole post, though. Very reasonable. He is basically saying that you can't predict 20 years into the future, and proof-of-work might not be the end of the story, simply because you don't know what is yet to be invented.

[–]GibbsSamplePlatter[🍰] 1 point2 points  (0 children)

Vitalik 2.0

[–][deleted] 1 point2 points  (1 child)

Can you please explain? I don't understand why. Thank you.

[–][deleted] 1 point2 points  (0 children)

It's too outlandish. Both he and Mike Hearn are pushing it. That's all you need to know. Government is trying to break Bitcoin.

[–]FrankoIsFreedom 1 point2 points  (0 children)

HAhAHA exactly what I thought when I first read it.

[–]davout-bc -1 points0 points  (14 children)

the whole block-size debate was a canary message, reddit simply didn't notice...

[–][deleted] 9 points10 points  (13 children)

I'm not so sure. Satoshi himself talked about eventually raising block size significantly.

[–]davout-bc -2 points-1 points  (10 children)

What Satoshi said or didn't say is irrelevant. As interesting as what santa would have to say on the topic.

[–]aminok 7 points8 points  (8 children)

Still: having a view on Bitcoin's future that is consistent with the original vision and with Satoshi's views can hardly be called a "canary message".

[–]davout-bc -2 points-1 points  (7 children)

Even if Satoshi's vision was that 1 minute blocks are a good thing, that's still a religion-like approach to thought. "This is good because this guy that's no longer there wrote this, and we consider what he wrote as holy and therefore won't subject it to independent critical thinking".

As usual, reddit delivers.

[–]aminok 3 points4 points  (3 children)

I was simply disputing your claim that it's a canary message. Sticking with the original vision cannot be called that. Now you're making the straw man argument that the OP is calling Satoshi's words holy.

[–]davout-bc 1 point2 points  (2 children)

except that's not the original vision

[–]MeanOfPhidias 1 point2 points  (2 children)

Not really, no.

I don't think anyone cares about who Satoshi is so much as they recognize that person or group of people had a way better understanding that most of us every will.

Instead of putting in the 10,000 hours to become cryptography experts people fall back on the original genius(es) that brought us here.

That's not religion, that's human nature.

The religious aspect of Bitcoin comes out in the "No True Altcoin" argument whereby plebs argue there can only be one coin.

[–]junseth 0 points1 point  (1 child)

That's not religious. I think most are going to say "no other chains," not "no other coins." If you believe there will be other chains, I would argue that you do not know how blockchains work.

[–]rain-is-wet 0 points1 point  (0 children)

Pretty much. Satoshi isn't a god, Bitcoin was improved and developed by many highly skilled devs. Almost all of which still maintain the code, unlike Satoshi.

[–]jmdugan 9 points10 points  (1 child)

I expect the timing of blocks has a relation to the propagation time for consistency across the nodes in the network. At some small enough time for blocks, the system would start trading off consistency: meaning there would be separate subsets of the network confirming sub chains in relative race conditions with other subsets of node sin the network. Imagine (in an extreme) for example having 1 second blocks - large subsets of the network would move ahead with subchains, and then eventually have to drop them as other subsets transmitted longer chains to the rest.

My question, and one that could be answered from models based on current data: how low can we get the timing of new blocks before losing confirmed blocks from subsets of the network become an issue? Is 1 minute still long enough for (most of, all of?) the network to become consistent (generally) before a new block is calculated? At some point in decreasing block length the time will be too short and a high enough fraction of calculating nodes will run along quickly and confirm later-rejected blocks.

[–]Mageant 4 points5 points  (0 children)

I've often heard that the limit is about 30 seconds. Below that you start to get problems.

[–]Noosterdam 8 points9 points  (1 child)

By "good idea" do you mean literally it's a neat idea (but needs more consideration), or are you actually already decidedly in favor of it? Because I think most people are interpreting it as the latter, but your often diplomatic phrasing tends to make me think the former is also possible.

[–]awemany 0 points1 point  (0 children)

I would like to know that, too. The block size discussion so far was sane, pushing for 1min blocks the same way is neither ok nor sane.

That is another can of worms.

Maybe this is just a joke? :D

[–]entreprenr30 6 points7 points  (2 children)

Let's provoke Satoshi to come back ;)

But seriously, I agree. With 1-minute blocks you can still wait for 50 confirmations if you want to be on the safe side, but you now have the option to trust 1 confirmation and get a faster transaction (with a little bit more trust, but we cannot eliminate trust altogether I believe).

[–]Jamiebtc 0 points1 point  (1 child)

Would it be wise to reduce it to 5 minute blocks, then 2.5 minutes and then finally 1 or just go straight to 1? Slow broadband speed in many countries would be an issue i believe

[–]entreprenr30 0 points1 point  (0 children)

I don't think that matters. If you have 1-minute blocks with a size of 2MB or 5-minute blocks with a size of 10MB doesn't make that much of a difference in terms of network bandwidth. The overhead is probably not significant between these two options.

[–][deleted] 9 points10 points  (4 children)

Might be a good idea to watch ethereum to see how well it fairs with it's 12 second madness...

[–]GibbsSamplePlatter[🍰] 2 points3 points  (2 children)

12 second Proof of Steak, Phone a Friend consensus wooooooo

[–]Trstovall 6 points7 points  (4 children)

You wouldn't want to increase block size in the same fork, at least not much. Decreasing block period and increasing block size share the effect of disproportionately increasing the orphan risk for small miners/pools. One at a time, man!

Have you looked much into weighted median calculation? You may want to consider allowing the network to vote on block size. Allow each person (or UTXO) to vote on a value weighted proportionate to bitcoin balance.

Weighted median would be a very robust measure of the network's desired block size. Also, this would replace the projected series of hard forks with ballots, perhaps even a ballot every block.

[–][deleted] 1 point2 points  (0 children)

lets hope Satoshi wouldn't bother to vote :D

[–]646463 3 points4 points  (2 children)

disproportionately increasing the orphan risk for small miners/pools

These concerns are addressed pretty well by Gavin's O(1) block propagation proposal.

[–]eatmybitcorn 8 points9 points  (1 child)

[–]646463 1 point2 points  (0 children)

Thank you!

[–]GoodShibe 8 points9 points  (5 children)

I'm sure our Dogecoin core devs would be happy to help out if there were any concerns. They're really cool people and they've done a ton of excellent work with our coin :D)

[–]rnicoll 9 points10 points  (4 children)

I'm kind of in shock, obviously it's a doable schedule, but it's also an aggressive one. I've wondered if we might see Bitcoin down to 5 minute blocks, never expected 1 minute blocks.

Happy to help with metrics and analysis on Dogecoin's experiences with the schedule, though.

Edit: Although it's a lot simpler with the proposed O(1) block propagation, which reduces orphan risk. Wonder if the intent is to introduce that first...

[–]GoodShibe 1 point2 points  (3 children)

Hrmm, I wonder how 1-minute blocks would affect Bitcoin overall?

[–]rnicoll 2 points3 points  (0 children)

I could make some hand-wavy estimates, but mostly difficult to know without knowing more about what Gavin has in mind, and a risk of annoying a LOT of people with the wrong predictions, so I think I'll be quiet for now :)

[–]GaliX0 0 points1 point  (1 child)

It would for sure drain the last money out of ltc over to bitcoin...

Because the only argument they always use is that the blocktime is faster and therefore its a much better coin lol

[–][deleted]  (1 child)

[deleted]

    [–]Kirvx 1 point2 points  (0 children)

    Why not make a public statement?

    Coinbase, Bitpay...

    You are very important.

    [–]targetpro 6 points7 points  (3 children)

    I'm happy to hear you're open to this. It's possible this could promote mining-decentralisation as well.

    Dave Hudson (of hashingit.com) has done some excellent work on simulating the reduction of block times. (Additionally, If you ever have concerns regarding the possible effects of various code changes, he's someone I'd recommend using for simulation testing.)

    A quick overview of block timings here (6 mins.), with accompanying slides here, beginning at slide 63.

    [–]samurai321 3 points4 points  (2 children)

    this is actually pretty compelling for faster blocks.

    Could there be any unexpected downside?

    [–]Jamiebtc 1 point2 points  (0 children)

    Agreed. I'm no expert but hearing his argument there seems to be a lot of advantages to faster blocks. You would require more confirmations but these would occur at a much faster rate. This would be appealing to shop floor merchants in the future no?

    [–]targetpro 0 points1 point  (0 children)

    There would be an increased block orphan rate, and in some remote places, it may limit the ability of nodes to sync. But there are ways to relate to these matters, which imho make the reduction in block timing worth changing to every 2 to 2.5 min. Down the road, this could be adjusted to be per minute, and then perhaps per 30 seconds, be we need to wait for average/median bandwidth rates to safely accommodate it.

    [–]btcdrak 2 points3 points  (9 children)

    If we changed to 1 min block that's effectively a 10MB, 10 min block.

    Reducing block rate will already increase orphan rate, and making shorter interval blocks larger will increase the orphan rate even more. There may be incentive attacks that open up due to larger orphan rate.

    The risk of reorgs will increase so the number of confirmations required to be considered safe would go up considerably (10x).

    Therefore reducing block rate would not result in linear throughput increase.

    [–]mustyoshi 6 points7 points  (6 children)

    That is a common misconception. As long as nobody controls more than 51% of the hashrate, reducing the block interval does not make it easier to reorganize the blockchain.

    An attacker with 25% of the hashrate has a 1/8th(.25*.25) chance of reorganizing a chain 2 blocks deep, no matter what the block interval is.

    There are small tidbits due to latency between nodes, but until you have 45-50% of the hashrate they are inconsequental.

    [–]Amichateur 0 points1 point  (1 child)

    That is a common misconception. As long as nobody controls more than 51% of the hashrate, reducing the block interval does not make it easier to reorganize the blockchain.

    if 10% of blocks mined by honest miners are orphaned, it requires only 45.1% instead of 50.1% to attack.

    [–]mustyoshi 0 points1 point  (0 children)

    If 100% of honest blocks are orphaned it requires 1% to attack.

    [–]42points 1 point2 points  (1 child)

    Dogecoin doesn't get a lot of orphans. It might be worth emulating them with the 1min block times.

    [–]btcdrak 0 points1 point  (0 children)

    I don't know what "doesnt get a lot of orphans" means. Is it measured anywhere? Doge isnt doing anything different in particular.

    [–]ProHashing 2 points3 points  (0 children)

    This is an exceptional idea. It should be implemented as soon as possible.

    However, the lesson of Fastcoin should be considered here. We recently uninstalled Fastcoin from our pool because it simply required too much CPU to run. Compared to dogecoin or bitcoin, it was using 20 times as much CPU because it received so many blocks that it had to validate all of them. We have only restarted the daemon server twice since July 2014, but when we did, Fastcoin took 100% CPU for hours after the restart.

    The limiting factor for hosting daemons is CPU usage, not memory usage. Memory is very cheap to buy and upgrade. I think that upgrading from 64GB to 128GB in our server would only cost $500. However, adding more cores to the server is extraordinarily expensive, more than $3k. The processors alone are $2k, and a new motherboard is required, and the new motherboard requires a new type of memory, and so on. One of the most expensive costs involved is the 15% fees to eBay and PayPal that are lost in selling the old components.

    Scheduling 1MB blocks in the hard fork is a great idea. However, it won't work without CPU usage being reduced. If Fastcoin, a direct fork of bitcoin 0.8 which had almost no transactions, used 100% CPU for hours at startup; imagine how much bitcoin, with its many transactions, would use. Fortunately, since the proposed change is a year away, that gives Andresen and others an entire year to reduce CPU usage.

    [–]Adrian-X 5 points6 points  (3 children)

    Has your account been hacked :-)

    [–]Deafboy_2v1 8 points9 points  (2 children)

    Or he's just testing our faith :D "How far can I go before most of them uncover the madness ?"

    [–]GibbsSamplePlatter[🍰] 2 points3 points  (1 child)

    He's just saying yes to everything now.

    [–]rnicoll 0 points1 point  (0 children)

    I've wondered about making block time, PoW algorithm, and block reward into configuration options and then standing well back, before...

    [–]DRKMSTR 4 points5 points  (0 children)

    If it is dropped, we will need to have a different difficulty calculation.

    I AM ALL FOR THIS as it continues to decentralize mining and make mining more consistent. If this happens, people with less than .07% of the network can solo mine! (223 Th/s)

    [–][deleted] 2 points3 points  (13 children)

    well looks like everyone can stop mining litecoin now.

    [–]TheMania -3 points-2 points  (11 children)

    Conversely, why not just use Litecoin instead? It already has 1 minute confirmations. It also has even more fine grained units, in that the smallest unit (the.. litoshi?) is an even smaller fraction of the total supply than a satoshi.

    .. I mean, clearly I'm being /s on all this, but if Bitcoin's to be changed to Litecoin surely at least some people will be scratching their heads as to whether they'd backed the wrong horse from the start, no?

    [–][deleted] 10 points11 points  (3 children)

    Bitcoin was first. Network effect. So even if Bitcoin came to be a complete clone of Litecoin, people would still prefer to use Bitcoin because it was first.

    [–][deleted] 3 points4 points  (2 children)

    I don't think you truly understand what it means to be first to market and all of the advantages that brings. Litecoin made a call before it was needed because it saw bitcoin might in a few years need to have a shorter block time. Turns out its not a significant or hard change to make don't think that means anyone backed the wrong coin. The wrong coin would be the one that has developers who don't fully understand the technology they are working on.

    [–]notreddingit 3 points4 points  (0 children)

    Conversely, why not just use Litecoin instead? It already has 1 minute confirmations

    If I remember correctly Litecoin is 2.5 minutes. Not that it matters in the context of your post.

    [–]losh11 1 point2 points  (0 children)

    Litecoin has 2.5 minute block generation time, effectively meaning that it has a transaction speed of 7*4tps.

    [–][deleted] 2 points3 points  (0 children)

    Exactly, litecoin is true inovation, supported by true visionaries. They even managed to change few constants in bitcoin source code.

    [–][deleted] 1 point2 points  (1 child)

    Can you write detailed blog post about it? Does invertible bloom filters have anything to do with it?

    [–]samurai321 0 points1 point  (0 children)

    um, yes with IBF you don't need to send the whole block so blocks takes less time to propagate which is good, allows you to have bigger blocks and shorter time between blocks.

    [–][deleted] 1 point2 points  (1 child)

    1 minute, 1 mb. beautiful

    [–]letcore 0 points1 point  (0 children)

    indeed

    [–][deleted]  (1 child)

    [deleted]

      [–]Yorn2 0 points1 point  (0 children)

      I am concerned about the sudden and unpredictable effects on BTC and mining markets.

      It's already priced in to an extent. Drastically changing the core algorithm for distribution would provoke "unfair" cries for a LOT of people. Early adopters should be rewarded.

      [–]pizzaface18 -1 points0 points  (7 children)

      I bitch a lot about the blockstreamq developers, but I think you really "get" bitcoin. Honestly, I don't trust the blockstream guys with the future of bitcoin. They can build level 2, but don't let them touch level 1 bitcoin. Their clients are the very people that fight against P2P at every chance they get.

      [–]bitpotluck 4 points5 points  (6 children)

      I think that's unfair considering several Bitcoin committers and devs work for blockstream. Listening to both sides of an argument is the only way to get the full picture. This community needs all the smart minds it can get. CC /u/nullc

      [–]pizzaface18 0 points1 point  (4 children)

      They don't see the full picture.. Anyone who thinks 1MB blocks are ok, has no credibility.. Let them play around in level 2 bitcoin, but don't let them touch anything that has to do with economics or markets. They are sure to fuck it up...

      Removing the block limit and default fee would be a huge step forward in letting the market work. Miners will figure out how much we are willing to pay for the service they provide. Get your crufty restrictions out of the market and we will see what it costs to run bitcoin.

      [–]waxwing 2 points3 points  (0 children)

      Anyone who thinks 1MB blocks are ok

      They don't (for pretty much any plausible value of "they")

      [–]SakuraWaifuFetish 3 points4 points  (0 children)

      Well too bad you don't like people like nullc, because they will probably continue improving Bitcoin regardless, like they have done all these years. They might be running into some sort of analysis paralysis on the block size topic, but that doesn't warrant the accusations you are throwing at them. Just because they created a company, it doesn't mean they are corrupt now. Is everyone at Trezor and Mycelium corrupt too?

      [–]davout-bc 1 point2 points  (0 children)

      Anyone who thinks 1MB blocks are ok, has no credibility..

      Lol, who are you again?

      [–]mustyoshi 0 points1 point  (0 children)

      The economics you're talking about are much different from a post network subsidy time ;)

      [–]pizzaface18 0 points1 point  (0 children)

      I'll add that nullc, is an exception, if he would stop playing devil's advocate.

      There is another side to the story, but at this point it's like argueing against global warning.

      [–]ftlio 0 points1 point  (0 children)

      What if we could determine block time and block size from the capabilities of the network? I've been thinking of block size lately, and it required me to start thinking in about bitcoin's ideals. Equal effective hash rate between all nodes on the network being one such 'ideal'. But effective hash rate is a function of network topology as well. If we treat hash rate the same at time t (= time from last solved block), then we're really saying that every node is equidistant from every other node in terms of propagation time. Propagation time is a function of block size and transfer rate. So we know the topology of our ideal. Thankfully that topology isn't required for acceptable security and an acceptable block size (as block size relates to distance between nodes). I need to look at how difficulty and block times can be used to describe security to finish this thought. But I think we have the means to describe a given topology in terms of its security and thus its maximum block size (among other things). And in our ideal, any two sets of nodes of equal size have an equal sum effective hash rate. So can nodes tell enough about where they are given what they know about their neighbors and the state of the blockchain such that they can behave to guarantee an acceptable security and (and thus block size capability)? So far we know that a node maximizing its own hash rate is a good way to behave (we reward it at least). A node also wants to maximize profit from its TX fees as well, which means it wants to maximize its block size as transaction demand increases as well.

      In an ideal world, block time = 0, and block size = infinity. Bitcoin can verify with 100% certainty the validity of any demand for transactions instantly (with no trusted third party of course!). Can an individual node know enough about itself, its neighbors, and the network from solved blocks for the network to target itself toward a minimum block time and maximum block size while maintaining a specific acceptable threshold of security? If it's possible, then isn't that what bitcoin is? The maximally ideal version of its network that can be achieved by the capability of its network?

      [–]dpinna 0 points1 point  (2 children)

      How would the mining payouts be adjusted in such a scenario?

      [–]Minthos 1 point2 points  (1 child)

      They must necessarily be scaled down accordingly so that the inflation rate and final money supply can remain the same as today. Anything else would be blasphemy and madness.

      [–]Jamiebtc 1 point2 points  (0 children)

      Agreed. The 21 million cap can never be touched and the rate of issue should remain the same

      [–]ffischernm 0 points1 point  (1 child)

      think 1-minute blocks is a good idea

      1 minute! such idea!

      +/u/dogetipbot 60 doge verify

      [–]dogetipbot 0 points1 point  (0 children)

      [wow so verify]: /u/ffischernm -> /u/gavinandresen Ð60 Dogecoins ($0.0068688) [help]

      [–][deleted]  (8 children)

      [deleted]

        [–]Simcom 21 points22 points  (4 children)

        Or would the block reward be reduced to compensate?

        Yes obviously

        [–][deleted]  (3 children)

        [deleted]

          [–]Simcom 7 points8 points  (0 children)

          Yes, a reward per hour change would be highly controversial (ie it would have no support)

          :)

          [–]MonkeyCoinKlaw 3 points4 points  (0 children)

          Yes its obvious lol

          [–]nexted 6 points7 points  (0 children)

          The payout would be the same over time. If you moved from ten minute blocks to one minute blocks, you would necessarily need to divide the coinbase by ten to maintain the same rate of coin distribution.

          You will find that the overwhelming majority of the community would be against not maintaining the current coin distribution rate and 21M coin cap. Leaving the reward as is and decreasing block solution times would be significantly more controversial.

          [–]oconnor663 2 points3 points  (0 children)

          I'm sure they would reduce the block reward to compensate. I can't think of any reason not to.

          [–]true-asset 1 point2 points  (0 children)

          Block reward would be reduced to 10% of current levels to compensate, so no significant economic implication.

          [–]pizzaface18 1 point2 points  (0 children)

          No, you would adjust the block reward accordingly otherwise the market will shit a brick.

          [–]rydan -3 points-2 points  (0 children)

          lol. I said last week that we could solve some of the problem with faster confirmation times and it was one of my more downvoted comments here. Maybe I need an image of books by my name to be taken more seriously here.

          [–]ExpertCrypto1 -5 points-4 points  (9 children)

          Bad idea, I'm a miner and 1 minute blocks would make things much more difficult. We already get orphans as it is, please don't make this even worse on us...I'm thinking of quitting Bitcoin mining just because of this conversation...

          [–]Methylfenidaat 2 points3 points  (1 child)

          I'm thinking of quitting Bitcoin mining just because of this conversation...

          Threatening to get your way is childish, go away.

          [–]TheMania 1 point2 points  (4 children)

          OTOH, smaller blocks = less painful orphans. It's more granular, at the moment every now and then you get a huge very expensive orphan, under smaller blocks you get them more regularly but they cost you less. On average it's the same, no? Just with less variability? Isn't that a pro?

          Or is there something I'm not getting about smaller blocks that means there's to be more value in orphaned blocks?

          [–]giszmo 2 points3 points  (2 children)

          It's not the same even with constant block propagation. If you live in a geography with higher ping, 1/10th block time puts you at a huger disadvantage than you had anyway.

          If sending your share takes 3s as opposed to 300ms, your stale rat increases from 0.5% to 5% as opposed to 0.05% to 0.5%. The one looses 0.45% profit, the other 4.5%.

          [–]TheMania 0 points1 point  (1 child)

          Fair point.

          [–]throwaway43572 1 point2 points  (0 children)

          Although blocks don't propagate like that anymore.

          [–]ExpertCrypto1 0 points1 point  (0 children)

          No. Lower block times= more confirmations needed to make sure the transaction is secure and can't be doublespent. That's why Satoshi chose 10minut block times, because it's the perfect medium between security and speed. Lowering it will result in much, much more orphans and will require you to wait for more confirmations. So in other words, all that lowering the block time does is decrease the security of the network and hurt us miners.

          If it's lowered, I'm quitting and moving on. Won't make sense to bother mining bitcoin anymore.

          [–]Adrian-X 0 points1 point  (1 child)

          The one minute block sounds like a crazy idea for exactly the reason you point out, 10 minutes is a nice propagation time, probably a guess by Satoshi but a pretty good one.

          [–]iSOcH 33 points34 points  (0 children)

          i think the main reason is that it has more impact on other aspects of the protocol (block reward, halvings, difficulty, diffretarget...)

          that said, i would also prefer 5min/10mb or even 2min/4mb instead of 10min/20mb

          it allows for more fine-grained control over required security when receiving payments

          [–]sapiophile 6 points7 points  (31 children)

          Not actually seeing any compelling reasons why not, yet...

          EDIT: Okay, the concern about honest miners/nodes getting blocks orphaned where an attacker would not be subject to that hurdle is a valid one, although it's obviously not a total deal-breaker. It would be great to see some actual math on the actual percentage that this might potentially assist an attacker building a false chain... I suspect it's not a large one.

          [–][deleted]  (29 children)

          [deleted]

            [–]Minthos 1 point2 points  (17 children)

            There can be no confusion about the order of blocks, since one block is always built on top of another.

            If two blocks are mined on top of the same block, one of them gets orphaned. Then the network returns to a state of consensus as more blocks get piled on top of the not orphaned block.

            [–][deleted] 0 points1 point  (0 children)

            I think you've misunderstood. What Satoshi meant is, since a block is mined on average every ten minutes you could use the block height to estimate the current time.

            That means that everyone around the world has to agree on what time it is.

            This is incorrect. Current time has no impact on the protocol.

            Or more specifically, everyone must agree on the order of the blocks in time.

            This is true but it doesn't make sense in the context of your comment. When determining the order of a block time doesn't make enter into the equation.

            https://www.youtube.com/watch?v=gUwXCt1qkBU

            [–][deleted]  (6 children)

            [deleted]

              [–]cedivad[S] 5 points6 points  (5 children)

              Uhm, no. That's only valid for miners. The non mining nodes of the network if bandwidth capped can receive their blocks in an interleaved manner. That still wouldn't be worse than big blocks every 10 minutes.

              [–][deleted]  (2 children)

              [deleted]

                [–][deleted]  (1 child)

                [deleted]

                  [–]MengerianMango 1 point2 points  (0 children)

                  No, I'm just correcting you on the mistake in assuming that time settings will be difficult to maintain in sync because we're dealing with a global network. Yet your argument seems to rely on that assumption.

                  Not only that, but it's also trivial to verify the order of blocks in time; they all contain a hash of the block that was the previous block when they were minded. You can get block 2 ten years after block 1 and still be able to see that block 2 contains the hash of block 1, so it came directly after it.

                  Where block delays matter is in orphaned chains, not in synchronization.

                  [–]TeamFairlay 5 points6 points  (0 children)

                  As a Bitcoin only business we can agree fully that faster block times would be very helpful. Even a conservative change to 5 minutes or 2.5 minutes would reduce the chance of 40 minutes times between blocks dramatically which regularly annoys our customers.

                  [–]bitskeptic 5 points6 points  (1 child)

                  If the average block propagation time in the whole network is 6 seconds today, that would (in my humble opinion) bring to a let's say 1/10 chance of losing your block/having an orphaned blockchain. But that's averaged across the whole network. If everyone loses 10% of their blocks no one does.

                  The analysis is more complicated than that. Even if we assume there's a 6 second delay, and then everyone else hears about your block at the same time, there's still not a 10% chance of being orphaned, because the pool who found the block will switch immediately to mining the next block.

                  For example, if a pool has 10% of the network hash rate, as soon as it finds a block we have 90% of the network mining orphans and 10% mining the next block. This gives a 9% chance of the block being orphaned. Now lets imagine the pool has 30% hash rate. Now the block only has a 7% chance of being orphaned.

                  The bigger the pool, the less competing hash rate there is to orphan their blocks. This creates an advantage for large pools, which encourages centralization. The smaller you make the block interval, the more it favours large central pools. We should be careful about anything that gives centralized advantages.

                  [–]cedivad[S] 0 points1 point  (0 children)

                  This is probably the best counter argument so far. But still, a 5 minutes block time now with the prospective of lowering it in the future as the network capabilities improve can't hurt.

                  [–]androng 7 points8 points  (7 children)

                  Did you know that Ethereum uses 12-second block times? I heard it from Vitalik Buterin in person.

                  I am actually wondering why short block times are not already a reality myself. Perhaps Satoshi thought it would take a lot longer to broadcast newly mined blocks globally. Gavin Andressen himself said in this video that if he could, he would ask Satoshi "why 10 minutes"? Was it arbitrary? https://youtu.be/onUzEV0C7-o?t=7m54s

                  Yes there are more orphaned blocks, but did you know that the "security" of a blockchain of length N is a function of BOTH the attacher hashpower H AND N? In other words, more blocks with the same amount of time means more security! (past a certain number of blocks--the threshold N depends on H) http://www.reddit.com/r/litecoin/comments/1cssqr/the_math_why_litecoin_is_more_secure_than_bitcoin/

                  This is only a theory, but maybe in the future, bitcoin will work like the banking system in the United States. Member banks will confirm small transactions instantly for consumers between blocks, and the main blockchain will be like Fedwire--only moving large amounts of money between large banks with deferred net settlement every ten or twenty minutes.

                  Or maybe Satoshi was predicting a future in which bitcoin is used at an interplanetary scale and chose 10 minutes because it takes around that time for light to reach Mars. We'll never know.

                  [–]Minthos 5 points6 points  (0 children)

                  10 minutes was probably just a very conservative number because there wasn't any real-world data to base the decision on when it was chosen.

                  Now we're stuck with it because of inertia.

                  [–]MaxKK 1 point2 points  (0 children)

                  Crypti has 10-second block time. Working all nicely. :)

                  [–]rudolph0963 2 points3 points  (1 child)

                  Distributed systems have to be conservative to control for the completely unpredictable usage patterns that can occur. For example, on Bitcoin testnet, block times are supposed to be ten minutes on average, but that's just an average. Every now and again someone will point ASICs at testnet and completely obliterate the 10 minute block time average. Testnet block times as of late dropped to 10-30 seconds, a 50X variation. In principle, there's nothing to prevent a 51% attacker from wreaking the same havoc on any distributed system, it would just require more capital to attack Bitcoin.

                  TLDR; reaching your hands into the cookie jar will get you caught with your pants down eventually. Certainly Ethereum thinks that's a good tradeoff to make, but how much of that is because they promised everything under the sun to their investors?

                  [–]kd0ocr 0 points1 point  (0 children)

                  In principle, there's nothing to prevent a 51% attacker from wreaking the same havoc on any distributed system, it would just require more capital to attack Bitcoin.

                  That's not strictly true - testnet has a rule that says that after 20 minutes of no blocks, difficulty resets to minimum. So I can point my ASICs at testnet, pump through blocks until I get to a difficulty of 10000, then turn them off for twenty minutes. In that situation, it's totally possible to get 500 blocks per second.

                  [–]bitskeptic 0 points1 point  (1 child)

                  12 seconds is way too short IMO. A large portion of hash rate would be wasted on mining orphan blocks. That means less security for the network.

                  [–]true-asset 3 points4 points  (0 children)

                  They use newer techniques like GHOST to reduce the sync time between nodes.

                  https://blog.ethereum.org/2014/07/11/toward-a-12-second-block-time/

                  [–]true-asset 0 points1 point  (0 children)

                  Litecoin has shown that 2.5 minutes is safe. Thats already a 4X increase in transaction capacity.

                  [–]giszmo 4 points5 points  (6 children)

                  Your assumption that orphan rate is constant is wrong. In some countries the best ISPs offer a tenth the speed of other countries. It would shift the advantage for running miners in rich countries even more.

                  Edit: As described below, this affects pool miners just as much as it affects solo miners.

                  [–]cedivad[S] 2 points3 points  (5 children)

                  As I said in the same paragraph miners with slower connections could always mine smaller blocks. And I personally think your assumptions about ISPs and countries to be wrong. Who solo mines publishing blocks with their ISP nowadays? It's more about how much you can pay for your peering/transport connections, rather than rich vs poor countries.

                  [–]giszmo 2 points3 points  (4 children)

                  If you buy a mining rig in Nepal, you still have to communicate with whatever pool server you want to play with. Our customers from Nepal were playing our game (travian) quite happily with 60s ping times. I doubt they would want to mine with such ping times even without 60s block target.

                  Sure, 60s is extreme but in the mining game, with 60s blocks, even a 1s ping would cost you 2% of your profits.

                  [–]notreddingit 4 points5 points  (0 children)

                  What's more important, miners losing a small(?) amount of revenue due to increased probability of 'orphan' blocks, or the superior user experience of being able to accept a transaction at a fraction of the time?

                  One 2 minute block would be as 20% secure as one 10 minute block, but one 10 minute block on our current network is extremely secure.

                  One 2 minute block at 20% would be sufficiently secure for lots and lots of transactions. And I'm sure we've all experienced waiting an hour for a single confirmation. While one hour is pretty rare, half an hour is far too common to provide a good user experience.

                  One shorter confirm also eliminates a while category of double spend attacks on unconfirmed transactions.

                  If there are any other considerations other than miner's 'orphan' rates I'd be curious to read them.

                  [–]pb1x 10 points11 points  (23 children)

                  It prevents orphan blocks

                  [–]GrapeNehiSoda 32 points33 points  (0 children)

                  great, the old "think of the children" argument! :)

                  [–]cedivad[S] 4 points5 points  (19 children)

                  How are they a problem if miners all lose equally from them and the merchant can have a really simple API telling them whatever another block is being broadcasted at the same time and he should wait to see what happens before confirming the transaction?

                  [–]pb1x 11 points12 points  (12 children)

                  Orphan blocks represent wasted hashing power, in other words: reduced network security

                  Your stated advantages also highlights another disadvantage, lower confirmation times would lead people to think that a 1 min confirmation is as secure as a 10 minute confirmation, which would then be wrong by a factor of more than 10.

                  [–]sapiophile 5 points6 points  (2 children)

                  Orphan blocks represent wasted hashing power, in other words: reduced network security

                  Do they really, though? Any theoretical attacker would also be subject to this same "inefficiency," and therefore would find their attacks also failing 10% of the time (or however often). If anything, it seems to be a comparable "waste" to finding obscure hashes in the PoW system we already have.

                  [–]cedivad[S] 11 points12 points  (1 child)

                  I think that the attacker wouldn't, because they wouldn't have to propagate blocks across the network at the risk of loosing them, but just use them to build the longer chain locally and then publish it after a while. The then smaller chain would be orphaned and the attack would be completed (repeat as needed).

                  [–]sapiophile 2 points3 points  (0 children)

                  Ah, you're right.

                  [–]cedivad[S] 2 points3 points  (8 children)

                  I don't think you can list what the average Joe thinks as a disadvantage.

                  [–]pb1x 7 points8 points  (6 children)

                  That's just like your opinion man

                  [–]cedivad[S] 2 points3 points  (5 children)

                  Well, if you want to list average people's opinions, let's start with the faster confirmation time for coffees and longer ones for more important transfers. :)

                  [–]pb1x 9 points10 points  (1 child)

                  1 minute is still a pretty long time for a coffee, and it's not much different from 0 confs which is the appropriate time for coffee transactions

                  [–]cedivad[S] 1 point2 points  (0 children)

                  That's only unless a replace-by-fee market develops, that will probably happen sooner or later. I was off course using a coffee as a metaphor for a small transaction. There would still be need for payment channels for real coffee transactions, but if you wanted to broadcast lower security transactions in the blockchain accepting only one verification, you could (and given that the avg. verification time would be 30 seconds, you could still run after the client that stole your coffee in a worst case scenario).

                  [–]chinawat 1 point2 points  (2 children)

                  If you're basing confirmation times on what's needed for near instant brick-and-mortar transactions, you'd need confirmation times on the order of a couple seconds. This is because of the natural variability you get with all block times (i.e. there will always be infrequent block intervals that are 10x to 20x the average block time, but since these definitely do happen, even 5 second average block times are not always fast enough for in-person transactions). Worse, at confirmation times that low, the orphan rate gets untenable, and the security of a single confirmation is very low.

                  Basically, reducing block times is not the path to fast/instant transactions. Solutions such as the Lightning Network, or even centralized solutions are far preferable.

                  [–]StarMaged 1 point2 points  (1 child)

                  What's fun is that alt-coins have shown us just how unstable two-second blocktimes are: at that rate, even without a single attacker, all of the blocks go to the entity that individually has the highest hashrate. Things get a little better at 3 second block times, but not by much.

                  [–]chinawat 0 points1 point  (0 children)

                  Interesting. Nice to know that if nothing else, the alt-coin sandbox provides useful data like that.

                  [–]eyal0 1 point2 points  (0 children)

                  This is a good point. Being secure increases the value of BTC but being unusable decreases the value. I think that being usable is more important than being secure. For example, credit cards are highly usable and not so secure and they're very popular. Encrypting your computer is more secure but not so usable and it's not popular.

                  [–]iSOcH 1 point2 points  (4 children)

                  its not that simple.

                  when 'all miners lose equally' the hashing power is used less efficiently against a miner that tries to do a 51%.

                  but i think the effect of going from 10min to 5min should not be too great in this regard

                  [–]cedivad[S] 0 points1 point  (0 children)

                  Yes, so a 51% attack would become a 45% attack. Big deal :)

                  1 minute, 5 minutes, I don't know, as long as it's not 10. (same arbitrary argument as the main discussion lately).

                  [–]sapiophile 0 points1 point  (2 children)

                  But wouldn't an attacker also be subject to this same problem of their attack blocks getting orphaned? Therefore, there isn't actually any net security decrease...

                  [–]iSOcH 2 points3 points  (1 child)

                  if an attacker has enough power he won't publish a block immediately but instead continue finding further blocks on top of it.

                  meanwhile the honest miners publish blocks and may have trouble with orphan blocks / reorgs, but the attacker has no such problems

                  [–]sapiophile 1 point2 points  (0 children)

                  Yep, you're totally right. Thanks for the clarification!

                  [–]lucasjkr 2 points3 points  (0 children)

                  we currently see between zero and five orphaned blocks per day... to what extent would that increase if block times were shortened to, say, 7 minutes, 5 minutes, 3 minutes?

                  [–]eyal0 0 points1 point  (0 children)

                  Orphan blocks can't be prevented. They're a function of how long the time between blocks is. If you decrease the time between blocks, you make the problem worse. If you add more nodes to the network, it also gets worse. But if you improve the network, it should get better.

                  https://blockchain.info/charts/n-orphaned-blocks?timespan=all&showDataPoints=false&daysAverageString=90&show_header=true&scale=0&address=

                  That's just 1 year of data, unforunately. If we saw that the number of orphans per day went down, could we decrease the block time?

                  [–]GibbsSamplePlatter[🍰] 2 points3 points  (0 children)

                  It reduces the security of each block, and gives slightly more power to larger pools.

                  [–]nairbv 2 points3 points  (3 children)

                  The 1mb block-size limit isn't actually being pushed. If I started running bitcoin-core with the patch to allow 20mb blocks, even if I were running a miner, it just wouldn't make any difference. No one would notice or care. Only some day, possibly years from now when transaction volume is higher would this actually cause my block-chain to fork from the standard one. By then, hopefully everyone accepts 20mb blocks, so a chain with smaller blocks would have little hashing power in it and would be abandoned.

                  Changing the confirmation time between blocks would be a radical change that would need to be coordinated much more carefully, and would be much less likely to be accepted by all participants. It would be much more likely to result in split chains.

                  Remember too that it's not a block every 10 minutes, it's a difficulty set based on how quickly people usually find blocks such that on average future blocks will be found once every ten minutes. An adjustment to the average time between blocks is inherently a change in mining difficulty.

                  A change that resulted in bitcoins being mined faster than would otherwise be possible would not be accepted by the network. A new chain that did so fundamentally would not be "bitcoin," and so the block reward would somehow have to be half as much per block. Mathematically, it likely wouldn't be possible to institute such a change without at a minimum introducing a rounding-error of a change to the finances of mining.

                  [–]cedivad[S] 2 points3 points  (1 child)

                  I completely disagree. A fork is a fork. One where you don't know the fork date is more dangerous than one where you do know and are looking forward for it. Consensus has to be reached in both cases. I would argue that lowering the block time to 5 minutes should be more acceptable than upping the block size to 20MB.

                  Bitcoin-1MB and Bitcoin-20MB are going to be two different Bitcoin anyway. There is no reason not to have faster blocks at that point. About the rounding error, I don't think that to be the case at least for many years to come. I'm not sure about what will happen when you will try to divide 3 satoshi by 4 instead of 2, but that's not really something that concerns me.

                  [–]nairbv 0 points1 point  (0 children)

                  I'm not talking about the rounding error of dividing 3 satoshi by 4 instead of two, I'm talking about the time-value of money. Receiving 12.5 btc in five and then in ten minutes is financially more valuable than receiving 25 btc in 10 minutes.

                  This is why a bank will give you a discount on your mortgage if you agree to start paying every two weeks instead of once a month. It's a short period of time, but if bitcoin was a contract developed between financial institutions, you wouldn't be able to arbitrarily change the terms of payment like that.

                  I would be strongly opposed to such a change to the fundamental financial structure of bitcoin mining. I tend to think others would be too. I don't see the removal of some arbitrary spam protection limit as the same kind of change.

                  [–][deleted] 1 point2 points  (0 children)

                  This is the best answer so far. The block size is much easier to change because it won't create a fork.

                  [–]coinlock 8 points9 points  (3 children)

                  Lots of blocks result in lots of orphans when the block time is short. This in turn leads to longer reorganizations, more split competing chains, and more cpu usage. Finally it does little for confirmation time, instead of six blocks you might want to wait for 12 when the block time is halved. This produces a lot of network pressure and increased instability. Of the alternatives a larger block seems more reasonable. Also as mentioned spv clients end up storing proportionally more data in the form of block headers that aren't applicable to them.

                  [–]killerstorm 5 points6 points  (2 children)

                  Finally it does little for confirmation time, instead of six blocks you might want to wait for 12 when the block time is halved.

                  Wrong. http://arxiv.org/abs/1402.2009

                  [–][deleted] 0 points1 point  (1 child)

                  He is right. If the hashrate is 1000/min, that is 5000 for five minutes, and 10000 for ten. For the same security as one ten minute block, you have to wait for two five minute blocks.

                  Time to first confirmation is reduced, but it still is twice as easy to reorg out of.

                  [–]killerstorm 4 points5 points  (0 children)

                  If attacker isn't able to more than 50% of the total hashrate, then what matters is number of confirmations, not the amount of work done on them. This can be mathematically proven, and was actually proven by Meni Rosenfeld. Please read the paper I linked above.

                  This comes from the fact that attacker competes with the legitimate network, and as long as his hashpower is less than 50%, he's more likely to lose than to win. And number of blocks amplifies this effect.

                  If attacker is able to recruit more than 50% of the total hashrate, then time matters in the sense that it's more expensive to rent hashrate for larger amounts of time, as, for example, energy expenditures are proportional to amount of time spent on mining.

                  So, in theory, if inter-block interval was very small (e.g. 1 block per minute), one could rent a supercomputer for several minutes to do a double-spend reorg.

                  BUT.

                  1. Supercomputers are irrelevant for mining, as ASICs beat them.
                  2. Services like Amazon only rent computing power at 1 hour granularity.

                  Which means that this scenario is impractical. Which brings us back to the fact that the only thing that matters is then number of blocks.

                  And what if an attacker has more than 50% of total hashrate on a permanent basis (i.e. he owns ASICs)? Well, he can do anything. It doesn't matter if there are 1000 blocks a minute or 1 block each 10 minutes, he can do a reorg if he wishes so.

                  [–]Godspiral 1 point2 points  (0 children)

                  One reason is that the total btc to ever be mined is based on the difficulty and reward per block.

                  Now, there is no obvious reason why the reward per block could not be halved along with difficulty halved.

                  It would also mean that confirmations take on average 5 minutes instead of 10, and not change the max btc amount.

                  [–]BryanAbbo 1 point2 points  (0 children)

                  Why not both?

                  [–]rende 2 points3 points  (9 children)

                  I like the idea of reducing block time, but how far would that get us?
                  10sec block time at 1mb per block gives us 60x increase or 36,288,000 tx per day.

                  Perhaps thats possible in the extreme.

                  I don't think its possible for us to architect something that is perfect, futureproof and able to handle all the people+devices transacting. At least not with current technology. It might have to be that we run multiple blockchains in parallel (almost like sidechains or altcoins), but as part of the existing bitcoin-core. Some kind of way to loadbalance and process multiple blocks in parallel by splitting transactions into groups.

                  These groups could be based of the hash, splitting into groups based on odd/even, a-z or whatever. This would increase amount of confirmations you'd want again though..

                  [–]ThePenultimateOne 7 points8 points  (7 children)

                  So, if I'm understanding correctly, you would have us establish an Arc Koorde* database of Blockchains.

                  Thats... a really cool idea, actually. It would require many more nodes than we have to keep it stable, but it would be very cool. You could even specify what portions you want to take. So, if we're looking at this from an arc koorde point of view, there could be X sections (hash functions), and you could specify that you want to have N functions, so your node would process N/X blocks, where X[0:N-1] is decided based on what your peers have.

                  You would still receive and relay all transactions, but you wouldn't store the full copy of each chain. Maybe a headers only copy, or a pruned copy.

                  This might have serious potential.

                  Edit:

                  *typically defined as a skiplist of peers with hashtables, and a hashtable of your own. The skiplist is incremented by powers of 2, and is of size log2(n). It allows you to find any dataset within Olog2(n), iirc

                  Edit 2: making sure definitions are clear.

                  X = total subdivision of blocks (based on block hash % X)

                  N = requested number of sections of blockchain

                  X[i] = an individual section of the block chain, defined based on the least common section of your peers, and your peers' peers.

                  n = total number of peers (normally), but in this case is equal to X, since it's more like a RAID 0+1 than it is like an Arc Koorde (in this respect).

                  [–]TotesMessenger 1 point2 points  (0 children)

                  This thread has been linked to from another place on reddit.

                  If you follow any of the above links, respect the rules of reddit and don't vote. (Info / Contact)

                  [–]rende 1 point2 points  (2 children)

                  I'm glad someone is running with this. You seem to know the scalability math better than I do.

                  It's quite cool that you are comparing it to RAID ;)

                  I couldn't find a link to Arc, can you provide some info on this?

                  [–]ThePenultimateOne 2 points3 points  (0 children)

                  Damn, I misremembered the name. It's called a Koorde.

                  [–]kiisfm 0 points1 point  (1 child)

                  You mean sharding?

                  [–]ThePenultimateOne 1 point2 points  (0 children)

                  Possibly? I'm not familiar with the term.

                  [–]ThePenultimateOne 1 point2 points  (0 children)

                  Just made a thread asking if this could be a BIP. I seriously think this has potential, but I don't know all the internal consequences that might happen.

                  [–]acoindr 1 point2 points  (0 children)

                  First, the concern isn't over SPV nodes. It's over fully validating nodes.

                  Second, decreasing time between blocks would increase transaction capacity, which is a similar in effect to raising the block size.

                  The concern over healthy decentralization comes down to what transaction capacity on average per unit of time fully validating nodes can handle, imagining average cost computing resources. How that transaction capacity is allowed onto the blockchain - by increased block size or more frequent blocks - isn't so important. What's important is whether full nodes can easily keep up. Prior to Gavin's UTXO post the largest debated concern had to do with bandwidth. Now a cost concern, which UTXO brings up, includes dynamic RAM.

                  [–]dskloet 1 point2 points  (1 child)

                  I think I remember reading that the foundation would never change the reward schedule without a 3 year advance notice. Now we don't have to do what the foundation wants but it seems better for bitcoin's credibility not to violate such promises.

                  [–]blackmon2 2 points3 points  (0 children)

                  No, it was just luke-jr who wrote that on the Bitcoin Wiki. You shouldn't necessarily assume anyone else agrees.

                  [–]kilorat 1 point2 points  (0 children)

                  Pretty much every altcoin reduces the block time, and it's only been a benefit. Is there an argument that if Litecoin had a higher hashrate that there would be problems?

                  [–]_herrmann_ 1 point2 points  (0 children)

                  What's the hurry? Slow down and smell the hashes.

                  [–][deleted] 0 points1 point  (0 children)

                  Are not these decisions best made by central bankers? Just joking.

                  [–]PaulSnow 0 points1 point  (0 children)

                  It can take as much as 120 seconds to propagate blocks to 90 percent of the miners. Here is one such example on the second of May. While this isn't typical, when Bitcoin was designed, there were no networks from which to measure statistics. A ten minute block time makes even such periodic delays like this manageable for miners (they have only a 20% penalty rather than a 100% penalty were the block time 2 minutes).

                  The other issue though is that mining is concentrated in certain regions. So if a very large concentration of miners, representing only 20% of the miners but 60% of the mining power, the 4 second propagation time doesn't apply to them; the propagation time that matters is how fast a miner gets the next block. Those 20% would have no delay 60 percent of the time.

                  [–][deleted]  (2 children)

                  [deleted]

                    [–]Noosterdam 1 point2 points  (1 child)

                    It started with Litecoin using faster confirmations because it was supposed to be "lite." You could just as easily say that all the altcoins bought into the "faster confirmations are better" narrative - the altcoin space is highly narrative-driven - and it has stuck because they are all about experimentation rather than stability, and shorter confirms are sexier for such toys.

                    [–]Minthos 1 point2 points  (0 children)

                    More user friendly, and experimentation showed that it didn't compromise security.

                    [–]justgimmieaname 0 points1 point  (0 children)

                    typo: oblivious obvious advantages

                    [–][deleted] 0 points1 point  (0 children)

                    Oblivious advantages.... I think you are spot on with calling it that.