Pages:
Author

Topic: ... - page 3. (Read 3472 times)

hero member
Activity: 1029
Merit: 712
August 16, 2015, 05:51:55 AM
#15
Please use your eyes and read this: Bitcoin transaction fees go up when transaction data volume goes up, the blockchain functions perfectly normal regardless of transaction # or size. This is what the Bitcoin core developers already agree on.

Yes, we will clearly continue to be able to fit 10 minutes worth of transactions from a global populace into two-thirds of a floppy disk for the rest of forever.   Roll Eyes

Fees alone will not solve scalability.  If you honestly believe that then you don't understand this system as well as you claim to.  

Here's an honest question to those who advocate keeping a 1MB block:  how long would the backlog of transactions have to get before increasing the blocksize would become a viable option in your opinion?  I genuinely want to know just how far you're prepared to cripple the network to justify your agenda.
Under organic circumstances the Bitcoin transactions per day will increase slowly, and a slight increase in transaction fees will keep things running smoothly. Currently we are nowhere needing a blocksize increase, and Bitcoin transactions per day are growing steadily but definitely not exponentially.

I love Bitcoin so of course if there was a problem I'd support the fix. There simply is no problem though. Spam attacks helped prove that, transactions increased by insane amounts that would never happen naturally and network still ran fine.



Please explain how increasing fees will allow the network to scale beyond 7 transactions per second?

(For the sake of argument I'm assuming that the current capacity limit is 7 TPS which seems to be a widely accepted number.)
legendary
Activity: 3948
Merit: 3191
Leave no FUD unchallenged
August 16, 2015, 05:51:21 AM
#14
Please use your eyes and read this: Bitcoin transaction fees go up when transaction data volume goes up, the blockchain functions perfectly normal regardless of transaction # or size. This is what the Bitcoin core developers already agree on.

Yes, we will clearly continue to be able to fit 10 minutes worth of transactions from a global populace into two-thirds of a floppy disk for the rest of forever.   Roll Eyes

Fees alone will not solve scalability.  If you honestly believe that then you don't understand this system as well as you claim to.  

Here's an honest question to those who advocate keeping a 1MB block:  how long would the backlog of transactions have to get before increasing the blocksize would become a viable option in your opinion?  I genuinely want to know just how far you're prepared to cripple the network to justify your agenda.
Under organic circumstances the Bitcoin transactions per day will increase slowly, and a slight increase in transaction fees will keep things running smoothly. Currently we are nowhere needing a blocksize increase, and Bitcoin transactions per day are growing steadily but definitely not exponentially.

I love Bitcoin so of course if there was a problem I'd support the fix. There simply is no problem though. Spam attacks helped prove that, transactions increased by insane amounts that would never happen naturally and network still ran fine.

Perhaps there was some ambiguity in my post.  That's not what I asked.  Those recent transactions may well have been spam, but if the network did grow to a point where it was filled by legitimate transactions, what figure in MB would you be willing to see the backlog reach before supporting larger blocks?
legendary
Activity: 3948
Merit: 3191
Leave no FUD unchallenged
August 16, 2015, 05:24:47 AM
#13
Please use your eyes and read this: Bitcoin transaction fees go up when transaction data volume goes up, the blockchain functions perfectly normal regardless of transaction # or size. This is what the Bitcoin core developers already agree on.

Yes, we will clearly continue to be able to fit 10 minutes worth of transactions from a global populace into two-thirds of a floppy disk for the rest of forever.   Roll Eyes

Fees alone will not solve scalability.  If you honestly believe that then you don't understand this system as well as you claim to. 

Here's an honest question to those who advocate keeping a 1MB block:  how long would the backlog of transactions have to get before increasing the blocksize would become a viable option in your opinion?  I genuinely want to know just how far you're prepared to cripple the network to justify your agenda.
full member
Activity: 196
Merit: 100
August 16, 2015, 04:33:00 AM
#12
Says the guy with dozens of bitcointalk accounts, that's real legit.  Roll Eyes

What can i expect from a guy who just pass opinions as facts Then got a nerve to keep repeating it when asked for proof?


Keep repeating shit does not make it truth. Got that?

You can assume i have dozen accounts all you want, only admins here can know the truth. Retard.
full member
Activity: 196
Merit: 100
August 16, 2015, 04:24:23 AM
#11
Let's not forget that the bitcoin core developers excommunicated Gavin for being a selfish nutcase. Now he is trying to destroy bitcoin with outright terrorism via month long transaction spam attacks and declaring Bitcoin is forked when he does not have the ability to do so. He's causing the entire bitcoin community to lose money just because he is butthurt

Please back up your claim with evidence about gavin being the culprit behind the recent spam attack on the bitcoin network.

Otherwise please STFU  Grin

thanks
I know it was him and the BitcoinXT crew, they were trying to prove Bitcoin needs bigger blocks and failed miserably. He is so desperate at this point it is amusing.

The only thing Gavin destroyed was his reputation and credibility. Maybe he should do something useful and terrorize Dogecoin.

So in summary:

" i pulled shit out of my ass, put it in my mouth, then spit it out on screen for you guys to see ..."

The only reputation being destroyed is yours,... if its actually worth anything.
full member
Activity: 196
Merit: 100
August 16, 2015, 04:22:16 AM
#10
Let's not forget that the bitcoin core developers excommunicated Gavin for being a selfish nutcase. Now he is trying to destroy bitcoin with outright terrorism via month long transaction spam attacks and declaring Bitcoin is forked when he does not have the ability to do so. He's causing the entire bitcoin community to lose money just because he is butthurt

Please back up your claim with evidence about gavin being the culprit behind the recent spam attack on the bitcoin network.

Otherwise please STFU  Grin

thanks

Oh yeah i'm also waiting for this, Mr. NOT SPREAD MISLEADING INFORMATION!


What a piece of shit.
full member
Activity: 196
Merit: 100
August 16, 2015, 04:21:16 AM
#9
Please use your eyes and read this: Bitcoin transaction fees go up when transaction data volume goes up, the blockchain functions perfectly normal regardless of transaction # or size. This is what the Bitcoin core developers already agree on.

ignoring everything I wrote and posting a red herring is aggravating. Ignorance is the only reason this debate still exists. I will no longer respect people who spread this misinformation.

wtf? you're the one that dont understand shit and spread BS.

lol why did you open your mouth to remove all doubt?
sr. member
Activity: 300
Merit: 250
August 16, 2015, 04:00:50 AM
#8
Please use your eyes and read this: Bitcoin transaction fees go up when transaction data volume goes up, the blockchain functions perfectly normal regardless of transaction # or size.

Except that it can only perfectly function at the rate of 3tx per second.
legendary
Activity: 2492
Merit: 1473
LEALANA Bitcoin Grim Reaper
August 16, 2015, 04:00:12 AM
#7
Let's not forget that the bitcoin core developers excommunicated Gavin for being a selfish nutcase. Now he is trying to destroy bitcoin with outright terrorism via month long transaction spam attacks and declaring Bitcoin is forked when he does not have the ability to do so. He's causing the entire bitcoin community to lose money just because he is butthurt

Please back up your claim with evidence about gavin being the culprit behind the recent spam attack on the bitcoin network.

Otherwise please STFU  Grin

thanks
hero member
Activity: 882
Merit: 1006
August 16, 2015, 03:54:55 AM
#6
the 1 MB blocksize was a temporary fix and now 3 devs are holding bitcoin back  Cheesy


Should Bitcoin grow, even if the network changes its structure as a result?

   The current system where every user is a network node is not the intended configuration for large scale. That would be like every Usenet user runs their own NNTP server. The design supports letting users just be users.


    — Satoshi Nakamoto, July 2010

Great quote. I had not noticed it before. It sums up the whole blocksize issue really, it needs to be changed. The whole XT situation is now a different problem to the blocksize situation IMO. I want the blocksize increased, but I am totally against this incredibly dangerous way to try and change Bitcoins design.
legendary
Activity: 1148
Merit: 1014
In Satoshi I Trust
August 16, 2015, 03:49:26 AM
#5
the 1 MB blocksize was a temporary fix and now 3 devs are holding bitcoin back  Cheesy


Should Bitcoin grow, even if the network changes its structure as a result?

   The current system where every user is a network node is not the intended configuration for large scale. That would be like every Usenet user runs their own NNTP server. The design supports letting users just be users.


    — Satoshi Nakamoto, July 2010
hero member
Activity: 882
Merit: 1006
August 16, 2015, 03:47:02 AM
#4
This seems like a sort of propaganda there is no tricks happening from Gavin, we need to go ahead and fork to increase block size, this has been agreed by everyone. The only issue is how.

I think we should do it the same way we did it the last 2 times we had to change the blocksize. People seem to forget we changed this before and it wasn't nearly as controversial of a change.
Yeah because Bitcoin wasn't nearly as big or nearly as worth as much that and Satoshi was at the helm and everyone trusted him. Don't forget Satoshi trust Gavin enough to give him the emergency keys, even though everyone thinks he is an enemy.

The second time it was changed it was done under Gavin, Satoshi wasn't around. Gavin just picked 1MB blocks and nobody complained. Nobody really cared, I remember when it happened clearly.

Yes of course Satoshi didn't just give him the alert keys, Gavin was appointed lead developer of Bitcoin Core by Satoshi - he gave him commit access to the Bitcoin Core source code repository,

The good news is everyone knows drama is like rocket fuel for Bitcoin so hopefully we have enough fuel to hit the moon Cheesy
legendary
Activity: 1148
Merit: 1014
In Satoshi I Trust
August 16, 2015, 03:38:04 AM
#3
Bitcoin XT is a patch set on top of Bitcoin Core, with a focus on upgrades to the peer to peer protocol. By running it you can opt in to providing the Bitcoin network with additional services beyond what Bitcoin Core provides.

Currently it contains the following additional changes:

+Support for larger blocks. XT has support for BIP 101 by Gavin Andresen, which schedules an increase from the one megabyte limit Bitcoin is now hitting.

+Relaying of double spends. Bitcoin Core will simply drop unconfirmed transactions that double spend other unconfirmed transactions, forcing merchants who want to know about them to connect to thousands of nodes in the hope of spotting them. This is unreliable, wastes resources and isn't feasible on mobile devices. Bitcoin XT incorporates work by Tom Harding and Gavin Andresen that relays the first observed double spend of a transaction. Additionally, it will highlight it in red in the user interface. Other wallets also have the opportunity to use the new information to alert the user that there is a fraud attempt against them.

+Support for querying the UTXO set given an outpoint. This is useful for apps that use partial transactions, such as the Lighthouse crowdfunding app. The feature allows a client to check that a partial SIGHASH_ANYONECANPAY transaction is correctly signed and by querying multiple nodes, build up some confidence that the output is not already spent.

+DNS seed changes: bitseed.xf2.org is removed as it no longer works, and seeds from Addy Yeow and Mike Hearn are (re)added to increase seed diversity and redundancy.


tl;dr it's just Bitcoin Core but with ability to have larger blocks, a bug fix, and two minor things that are useful for app developers.
hero member
Activity: 882
Merit: 1006
August 16, 2015, 03:32:45 AM
#2
This seems like a sort of propaganda there is no tricks happening from Gavin, we need to go ahead and fork to increase block size, this has been agreed by everyone. The only issue is how.

I think we should do it the same way we did it the last 2 times we had to change the blocksize. People seem to forget we changed this before and it wasn't nearly as controversial of a change.
full member
Activity: 197
Merit: 100
August 16, 2015, 03:22:38 AM
#1
...
Pages:
Jump to: