Bitcoin Forum
May 07, 2024, 05:52:17 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 [11]  All
  Print  
Author Topic: Egad. 81,000 + Transactions Unconfirmed. Again. Ugh!  (Read 8827 times)
Carlton Banks
Legendary
*
Offline Offline

Activity: 3430
Merit: 3074



View Profile
March 05, 2017, 05:05:35 PM
Last edit: March 05, 2017, 09:10:16 PM by Carlton Banks
 #201

Therefore, BU doesn't actually "give miners more power", it just facilitates consensus.

BU facilitates breaking consensus, not enforcing it. That's the whole point of BU.

No-one will be able to trust the validity of on-chain transactions, as BU can fork or reorg itself unexpectedly at any time. The ability to alter the consensus rules on the fly turns forks and re-orgs into a feature, when they're highly undesirable for a stable uniform blockchain.

Vires in numeris
1715104337
Hero Member
*
Offline Offline

Posts: 1715104337

View Profile Personal Message (Offline)

Ignore
1715104337
Reply with quote  #2

1715104337
Report to moderator
"You Asked For Change, We Gave You Coins" -- casascius
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Lauda
Legendary
*
Offline Offline

Activity: 2674
Merit: 2965


Terminated.


View Profile WWW
March 05, 2017, 08:52:40 PM
 #202

51% of mining power already has defacto control of the network. 
Wrong that is not 'control'. They can attempt to attack the network, after which they would get 'fired' with a algorithm change.

Therefore, BU doesn't actually "give miners more power", it just facilitates consensus.
BU breaks consensus and attempts to change the security model into something that isn't even adequately tested.

BU facilitates breaking consensus, not enforcing it. That's the whole point of BU.

No-one will be able to trust the validity of on-chain transactions, as BU can fork ior reorg tself unexpectedly at any time. The ability to alter the consensus rules on the fly turns forks and re-orgs into a feature, when they're highly undesirable for a stable uniform blockchain.
Indeed.

"The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"
😼 Bitcoin Core (onion)
jonald_fyookball
Legendary
*
Offline Offline

Activity: 1302
Merit: 1004


Core dev leaves me neg feedback #abuse #political


View Profile
March 05, 2017, 09:05:32 PM
 #203


BU breaks consensus and attempts to change the security model into something that isn't even adequately tested.
 

Your point about consensus depends on one's point-of-view.

To quote BU:

We believe that the block size is NOT part of blockchain consensus...
By moving the blocksize limit from the protocol layer to the transport layer,
Bitcoin Unlimited removes the only point of central control in the Bitcoin economy -
the blocksize limit - and returns it to the nodes and the miners.


You are certainly correct that it is not tested. 

I suppose that supporters of BU like myself feel that the
risk is small compared with the damage that is likely to
come by allowing the current impasse and stagnation to continue, and/or allowing core to continue its governance.

LoyceV
Legendary
*
Offline Offline

Activity: 3304
Merit: 16616


Thick-Skinned Gang Leader and Golden Feather 2021


View Profile WWW
March 05, 2017, 09:32:52 PM
 #204

If that person is willing to pay for it, the network should just be able to handle it. Email spam makes up 97% of the 200 billion emails sent each day. The email system was adjusted in such a way that it can handle it, instead of making people wait longer to send an email.
That statement is complete nonsense. In no way will Bitcoin be able to sustain the amount of spam that it can be thrown at it.
If a spammer is willing to pay $1000+ per hour on fees, that should be enough to create a network that can withstand it. I don't see any other way to stop the spam.

No-one will be able to trust the validity of on-chain transactions, as BU can fork or reorg itself unexpectedly at any time. The ability to alter the consensus rules on the fly turns forks and re-orgs into a feature, when they're highly undesirable for a stable uniform blockchain.
This makes sense. It's the first time I read about this as a reason not to go for BU.

Carlton Banks
Legendary
*
Offline Offline

Activity: 3430
Merit: 3074



View Profile
March 05, 2017, 09:33:22 PM
 #205


To quote BU:

We believe that the block size is NOT part of blockchain consensus...

Then they're out of their tiny little minds.

From the Bitcoin source code, consensus.h:

Code:
/** The maximum allowed size for a block excluding witness data, in bytes (network rule) */
static const unsigned int MAX_BLOCK_BASE_SIZE = 1000000;

Vires in numeris
Lauda
Legendary
*
Offline Offline

Activity: 2674
Merit: 2965


Terminated.


View Profile WWW
March 05, 2017, 09:38:23 PM
 #206

Your point about consensus depends on one's point-of-view.
No.

We believe that the block size is NOT part of blockchain consensus...
What "you" believe has zero relevance. The block size was always part of the consensus rules else they'd not need a HF to change.

You are certainly correct that it is not tested
There we have it: BU is not even tested.

If a spammer is willing to pay $1000+ per hour on fees, that should be enough to create a network that can withstand it. I don't see any other way to stop the spam.
That amount of money is trivial for a fair number of people. You are talking beyond decentralized networking capabilities. There are limits to all of this you know?

"The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"
😼 Bitcoin Core (onion)
jonald_fyookball
Legendary
*
Offline Offline

Activity: 1302
Merit: 1004


Core dev leaves me neg feedback #abuse #political


View Profile
March 05, 2017, 09:49:13 PM
 #207



We believe that the block size is NOT part of blockchain consensus...
What "you" believe has zero relevance. The block size was always part of the consensus rules else they'd not need a HF to change.
 

Me?  No that is a quote from bitcoinunlimited.info.

Obviously the limit is in the codebase, and we think removing it is a good idea.
So from our point of view, this facilitates consensus, not breaks it.

Perhaps you still haven't gained the ability to discern facts from opinions.


Carlton Banks
Legendary
*
Offline Offline

Activity: 3430
Merit: 3074



View Profile
March 05, 2017, 09:58:41 PM
 #208

Obviously the limit is in the codebase

And your quote from bitcoinunlimited.info contradicts that very basic fact.

Vires in numeris
alexrossi
Legendary
*
Offline Offline

Activity: 3738
Merit: 1739


Join the world-leading crypto sportsbook NOW!


View Profile
March 05, 2017, 10:01:41 PM
 #209

50 megabytes of mempool constantly since a week on my full node. I think that the only decent way to trim well this huge amount of unconfirmed transactions will be to raise the minimum relay fee to 0.0001 BTC per kB

  ▄▄███████▄███████▄▄▄
 █████████████
▀▀▀▀▀▀████▄▄
███████████████
       ▀▀███▄
███████████████
          ▀███
 █████████████
             ███
███████████▀▀               ███
███                         ███
███                         ███
 ███                       ███
  ███▄                   ▄███
   ▀███▄▄             ▄▄███▀
     ▀▀████▄▄▄▄▄▄▄▄▄████▀▀
         ▀▀▀███████▀▀▀
░░░████▄▄▄▄
░▄▄░
▄▄███████▄▀█████▄▄
██▄████▌▐█▌█████▄██
████▀▄▄▄▌███░▄▄▄▀████
██████▄▄▄█▄▄▄██████
█░███████░▐█▌░███████░█
▀▀██▀░██░▐█▌░██░▀██▀▀
▄▄▄░█▀░█░██░▐█▌░██░█░▀█░▄▄▄
██▀░░░░▀██░▐█▌░██▀░░░░▀██
▀██
█████▄███▀▀██▀▀███▄███████▀
▀███████████████████████▀
▀▀▀▀███████████▀▀▀▀
▄▄██████▄▄
▀█▀
█  █▀█▀
  ▄█  ██  █▄  ▄
█ ▄█ █▀█▄▄█▀█ █▄ █
▀▄█ █ ███▄▄▄▄███ █ █▄▀
▀▀ █    ▄▄▄▄    █ ▀▀
   ██████   █
█     ▀▀     █
▀▄▀▄▀▄▀▄▀▄▀▄
▄ ██████▀▀██████ ▄
▄████████ ██ ████████▄
▀▀███████▄▄███████▀▀
▀▀▀████████▀▀▀
█████████████LEADING CRYPTO SPORTSBOOK & CASINO█████████████
MULTI
CURRENCY
1500+
CASINO GAMES
CRYPTO EXCLUSIVE
CLUBHOUSE
FAST & SECURE
PAYMENTS
.
..PLAY NOW!..
Pages: « 1 2 3 4 5 6 7 8 9 10 [11]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!