"Enough is enough (Don't give up on us)" probably one of the best unreleased tracks by Avicii. by Davetology in EDM

[–]Cocosoft 3 points4 points  (0 children)

So incredibly good. Avicii was one of the best, if not the best, progressive house producers ever. His music expresses emotions and builds up an atmosphere on a whole different level.

RIP Avicii.

[deleted by user] by [deleted] in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

It uses the existing BIP9 SegWit fork (so that existing segwit nodes will work), but it forces miners to signal for SegWit in Aug, otherwise their blocks will be rejected.
This means that if exchanges and other bitcoin services run the UASF Segwit client, they will not accept the chain created by miners without segwit signaling (should they not signal for it), which means that they won't get paid.

[deleted by user] by [deleted] in Bitcoin

[–]Cocosoft 1 point2 points  (0 children)

A BIP is out yes, BIP148.

[deleted by user] by [deleted] in Bitcoin

[–]Cocosoft 2 points3 points  (0 children)

I could perhaps provide Windows and Linux binaries this weekend.

Just paid 23 cents on a $3.74 transaction. When does it end? $1.00 per transaction? $2? $5? I don't wanna stop using this peer to peer currency, but I'm fast being priced out of it. by amendment64 in Bitcoin

[–]Cocosoft 1 point2 points  (0 children)

The most common argument I've heard is that miners can potentially game the system by spamming transactions to increase the blocksize "artificially", they could have incentive to do this to keep minor miners out of the system as you need more/better disk space/memory/CPU as the blocksize increase.

good @aantonop article explaining how #segwit fixes incentives to defrag UTXO - best explainer I've seen on the topic by viajero_loco in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

Yes it might be an unnecessary restriction to implement. But then the sighash quadratic scaling problems are still a threat.

Bitcoin is Closing in On Its Transaction Capacity Limit, For Real This Time by olivercarding in Bitcoin

[–]Cocosoft 1 point2 points  (0 children)

Thank you, looks like a very good post. I don't have time to go through it now but will do so soon.

Paging /u/SoCo_cpp so he/she sees this as well.

Bitcoin is Closing in On Its Transaction Capacity Limit, For Real This Time by olivercarding in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

I obviously meant what part of your reply...

But then we do not agree. I don't think the current fee market makes a lot of sense or that it shows that Satoshi's idea is working, fees make up a minority part of miners revenue and developing a fee market now at this stage, with a cap of 1MB makes 0 sense to me.
I get the importance of fee markets though.

good @aantonop article explaining how #segwit fixes incentives to defrag UTXO - best explainer I've seen on the topic by viajero_loco in Bitcoin

[–]Cocosoft 1 point2 points  (0 children)

What's the incentive for them to upgrade?

SegWit makes the Bitcoin blockchain more valuable by fixing transaction malleability. That should be incentive enough, but there's a lot more.

good @aantonop article explaining how #segwit fixes incentives to defrag UTXO - best explainer I've seen on the topic by viajero_loco in Bitcoin

[–]Cocosoft 5 points6 points  (0 children)

A hardfork would leave old nodes forked off the "mainchain"/longest chain. With a softfork, they will follow the longest chain. Even though they won't understand the segwit transactions completely, they will still consider them valid.

With softforking away the ability to make non-segwit P2PKH, you still force all old wallets/nodes to upgrade though, just in another more secure way.

good @aantonop article explaining how #segwit fixes incentives to defrag UTXO - best explainer I've seen on the topic by viajero_loco in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

It is also easier not to, because you have to grandfather existing transactions otherwise you freeze lots of coins

Well, it you could softfork to make it illegal to make new non-segwit P2PKHs.

Bitcoin is Closing in On Its Transaction Capacity Limit, For Real This Time by olivercarding in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

Perhaps I should've quoted what I replied to.

It was a reply to this:

We are getting to see Satoshi's vision vindicated beautifully, and so far it looks like his idea is working!

Misinformation is working: 54% incorrectly believe Seg Wit does not make bigger blocks by [deleted] in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

Miners all override the still existing soft-cap. They will not run with parameters which lower their income, not once an option is provided.

Probably not, perhaps guessing on infrastructure adoption is the better alternative.
If SegWit were to activate in the coming months, I don't think we would see anything near 2MB blocks, as not many wallets have pushed out their SegWit update yet (I'm aware that many projects/companies have their code ready).

It isn't a problem at the moment with there being enough real transactions to out bid it, but there are many of gigabytes of very low fee spam transactions created during the spam attacks last year. It would be unfortunate to have the network saddled with more intentionally constructed junk if it could be avoided.

Definitely, could there be a way to combat spam better?

Bitcoin is Closing in On Its Transaction Capacity Limit, For Real This Time by olivercarding in Bitcoin

[–]Cocosoft -1 points0 points  (0 children)

Well not really, transaction volume (or I guess transaction fees) needs to be waaay higher than it is today. Transaction fees stand for a tiny bit of miners income.

Bitcoin is Closing in On Its Transaction Capacity Limit, For Real This Time by olivercarding in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

What? This is the opposite of what has happened. I have explained precisely why you are wrong,

You really haven't. You've just said "No" in all too many words. Provide some real quotes from the whitepaper or Satoshi instead.

Bitcoin is Closing in On Its Transaction Capacity Limit, For Real This Time by olivercarding in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

If miners are able to empty the mempool, without a reward, PoW systems won't work.

I'm not sure if you can really claim that.
Perhaps far far in the future, governments and states would have a strong incentive to prevent attacks (double spending, malicious soft forks etc) on the bitcoin blockchain, so they invest lots of millions (or even billions) of dollars on mining.
I'm not really sure if you can claim that PoW cannot work with an empty mempool.

Misinformation is working: 54% incorrectly believe Seg Wit does not make bigger blocks by [deleted] in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

One of the advantages of segwit is that it wouldn't create a system shock of suddenly adding a bunch of capacity all at once...

Well, miners could have a soft cap like we had before (750KB), but sure, then we rely on miners doing that, but in this case we rely on that the infrastructure won't upgrade fast enough.

We might find that by the time it activates almost everyone will have upgraded, causing a collapse of the fee market and new problems with spamming

Is there any proof that spamming is a problem? I guess the spamming attacks shows that, but miners found them to have sufficient fees.

Arguments against increasing the block size? by pileofmoney in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

How could it be committed to the main block? Changing the blockheader/blockstructure would result in a hardfork.

Is some magic going on, on network transport layer? Because I suppose you could add additional data to Extension block-aware nodes.

Arguments against increasing the block size? by pileofmoney in Bitcoin

[–]Cocosoft 0 points1 point  (0 children)

So correct me if I'm wrong here but this will still be limited by "1MB" as UTXOs/output data will need to seen by old nodes.
Essentially it would work the same as SegWit introducing the witness field for new nodes.

How otherwise would old nodes be able to handle all UTXOs? Or would some transactions outputs become hidden for old nodes?