Pages:
Author

Topic: Permanently keeping the 1MB (anti-spam) restriction is a great idea ... - page 10. (Read 105069 times)

hero member
Activity: 658
Merit: 500
I just wanted to point out that Monetas / Open-Transactions is working on a solution that eliminates the need to trust third parties.

What? With Bitcoin, you already don't need to trust a third party. Why would this be different?

Sure you do. You need to trust MtGox and Bitstamp when you want to do market trading. And as this thread shows, you will soon need to do off-chain just for normal transactions (as a result of the 1mb limit.)

Well, you eventually need to trust someone. Also, off chain? I will not stop using Bitcoin because of the block changes.
sr. member
Activity: 440
Merit: 251
I just wanted to point out that Monetas / Open-Transactions is working on a solution that eliminates the need to trust third parties.

What? With Bitcoin, you already don't need to trust a third party. Why would this be different?

Sure you do. You need to trust MtGox and Bitstamp when you want to do market trading. And as this thread shows, you will soon need to do off-chain just for normal transactions (as a result of the 1mb limit.)
hero member
Activity: 658
Merit: 500
I just wanted to point out that Monetas / Open-Transactions is working on a solution that eliminates the need to trust third parties.

What? With Bitcoin, you already don't need to trust a third party. Why would this be different?
legendary
Activity: 1470
Merit: 1006
Bringing Legendary Har® to you since 1952

Code:
Maximum supported users based on transaction frequency.
Assumptions: 1MB block, 821 bytes per txn
Throughput:  2.03 tps, 64,000,000 transactions annually

Total #        Transactions per  Transaction
direct users     user annually    Frequency
       <8,000       8760          Once an hour
      178,000        365          Once a day
      500,000        128          A few (2.4) times a week
    1,200,000         52          Once a week
    2,600,000         24  Twice a month
    5,300,000         12  Once a month
   16,000,000          4  Once a quarter
   64,000,000          1          Once a year
  200,000,000          0.3        Less than once every few years
1,000,000,000          0.06       Less than once a decade

As you can see even with an average transaction frequency of just once a week or once a month the network can't support more than a token number of users.  When someone advocates a permanent cap of 1MB what they are saying is I think Bitcoin will be great if it is never used by more than a couple million users making less than one transaction per month.  Such a system will never flourish as a store of value as it is eclipsed by alternatives which are more inclusive.  To support even 100 million direct users making an average of one transaction every two weeks would require a throughput of 82 tps and an average block size of 20 to 40 Megabytes.

This. This is excellent.
Good work on explaining it this way.

With this post, you have done a great deed to support the Bitcoin long-term.

sr. member
Activity: 440
Merit: 251
Permanently keeping the 1MB (anti-spam) restriction is a great idea ... if you are a bank.  Those favoring a permanent 1MB cap saying that Bitcoin can still be a financial backbone of sorts they don't know how right they are.  The problem isn't a limit in general but that 1MB is so low that under any meaningful adoption scenario it will push all individual users off the blockchain to rely on trusted third parties. 1MB is useless for end user direct access but is sufficient for a inter-"bank" settlement network.

...

Conclusion
The blockchain permanently restricted to 1MB is great if you are a major bank looking to co-opt the network for a next generation limited trust settlement network between major banks, financial service providers, and payment processors.   It is a horrible idea if you even want to keep open the possibility that individuals will be able to participate in that network without using a trusted third party as an intermediary.

I just wanted to point out that Monetas / Open-Transactions is working on a solution that eliminates the need to trust third parties.

So the bulk of transactions could move off-chain to Monetas notary servers, and a notary would be unable to steal the coins, and would be unable to falsify receipts or change balances without a user's permission.

With the vast majority of transactions occurring safely off-chain on Monetas notaries, any user would still be able to perform on-chain transactions when necessary -- it would just be a lot more rare, and would usually consist of a transfer from one voting pool to another.

So keep your 1mb limit if you want, it will definitely benefit Monetas.
sr. member
Activity: 346
Merit: 250
Why the blocksize limit keeps Bitcoin free and decentralized: https://www.youtube.com/watch?v=cZp7UGgBR0I

thank the good lord satoshi theres an ignore button ............
ahaaaaaaaaaa..........so much better

wuut?? this is a very enlightening video made by Peter Todd already more than a year ago.. guess the issue hasnt evolved pretty much..

BTW his site http://keepbitcoinfree.org/ in which the video was originally posted is now disabled..

no more keeping bitcoin free Huh  Cry

source: https://bitcointalksearch.org/topic/new-video-why-the-blocksize-limit-keeps-bitcoin-free-and-decentralized-208200
legendary
Activity: 1316
Merit: 1000
Si vis pacem, para bellum
Why the blocksize limit keeps Bitcoin free and decentralized: https://www.youtube.com/watch?v=cZp7UGgBR0I

thank the good lord satoshi theres an ignore button ............
ahaaaaaaaaaa..........so much better
newbie
Activity: 14
Merit: 0
Yes patience would be key.

I'm not one of the guys, or anyone really, but I'd guess they trust ben_vulpes, mod6 and asciilifeform more than most people previously known as core devs.

The whole thing has been tainted, and it's hard to know who in which camp is independent of mind or influence.
legendary
Activity: 4690
Merit: 1276
Let's not get sidetracked by sidechains and IBLT.

The first was demolished even by cypherdoc in his econ-for-trolls thread, whence half of you came. They wil be decimated by speculators within hours, as with gavincoin.

Cypherdoc couldn't demolish a wet paper bag.  More than half of his bullshit is to absurd to even respond to.

And sidechains will be unlikely to be 'decimated within hours' if it takes days to excersize the peg.  For speculators who have the patience, well, as a BTC hodler, 'please don't throw me in dat der brier patch.'

The second is a blatant move towards conformity and centralisation.
"With today's p2p protocol ..." https://gist.github.com/gavinandresen/e20c3b5a1d4b97f79ac2 starts USGavin, preparing our arseholes for "tomorrow's p2usg protocol".

The old bitcoin foundation added and proposed a ton of other such ways to eventually con you out of your money too, such as multisig, timelock.

Don't doubt it, but I've not seen any examples yet.  Nor have I looked real hard.  I was negative about the garbage because I felt it was risky and unneeded, but I've nearly come to the conclusion that I was wrong.  I'm open to being convinced otherwise, and it may be worthwhile if you guys want 5.3 since I'm glad to accept the labor savings of digging the arguments up for myself.

The new one has halted all such complications and is producing a purer form of the discovery that is bitcoin. Everything that makes sense stays, everything else...

Once the crust is removed, block size and all the other elements of bitcoin can be tested without interference from or reference to Gavin, Blockstream, anyone.

I'm naturally inclined toward Blockstream until someone points me to more credible contributors than Maxwell, Wuille, Back, Frie-whatever, etc.  Todd is up there and I'll carefully parse his input, but after watching things moderately carefully for a number of years now, it's going to take more than witty prose to make any seismic shifts in my orientation.  Especially since what these guys seem to be up to are things which have made sense to me for about forever.

legendary
Activity: 1260
Merit: 1008
All I was trying to do was to figure out if you were unable to comprehend IBLT's impacts on block size, or whether you were deliberately ignoring them because they (probably completely) nullify the argument you were trying to make and figured your target audience would be ignorant of them.

Not that it matters much...both possibilities suck for you.

Wrong on all counts.

You'd know that if you'd bother to read.

You're just setting yourself up to look even more ridiculous.

The profligate nature of your writing and speaking is eclipsed only by the content-less nature of both.  I swear to Christ I've never gotten so little out of a one hour podcast as I did with that thing I listened to the other day.  I'm not going to track down all your spam so pop up a link if you have one.

Speaking of the podcast (with some fake accent guy who spent the last 10 minutes of his time doing jl777 a solid), what was really funny was that even with 40 minutes or so to burn you still deferred on trying to explain the OT thing because, supposedly, it was to complicated or some such.  Signing an XML is complicated?  Or tracking some sigs with a centralized server system?  Ya, OK.  Occam's razor suggests that you didn't want to try to describe it because it is lame and mostly useless.

I'm going to give you guys a little help understanding what is missing.  OK, so I make a 'contract' and break it.  What are you going to do?  Kick me out of your Ayn Rand fun-fort?  You need some sort of enforcement.  Fiat has it because they have a court system.  Bitcoin has a proof-of-work.  As far as I can see, OT has bunkus unless you somehow major visibility and I don't see that happening.  Maybe you could attach to someone with a user tracking and validation charger (e.g., CoinValidation) but I suspect they'll tell you to piss up a rope and just role their own instead of working with you.  You might offer your solution to Blockstream to try out for their federated kludge.  A proof-of-concept which does something useful probably wouldn't hurt OT any.



Podcast?

http://bitcoinism.liberty.me/2015/01/21/economic-fallacies-and-the-block-size-limit-part-1-scarcity/
http://bitcoinism.liberty.me/2015/02/09/economic-fallacies-and-the-block-size-limit-part-2-price-discovery/
newbie
Activity: 14
Merit: 0
Let's not get sidetracked by sidechains and IBLT.

The first was demolished even by cypherdoc in his econ-for-trolls thread, whence half of you came. They wil be decimated by speculators within hours, as with gavincoin.

The second is a blatant move towards conformity and centralisation.
"With today's p2p protocol ..." https://gist.github.com/gavinandresen/e20c3b5a1d4b97f79ac2 starts USGavin, preparing our arseholes for "tomorrow's p2usg protocol".

The old bitcoin foundation added and proposed a ton of other such ways to eventually con you out of your money too, such as multisig, timelock.

The new one has halted all such complications and is producing a purer form of the discovery that is bitcoin. Everything that makes sense stays, everything else...

Once the crust is removed, block size and all the other elements of bitcoin can be tested without interference from or reference to Gavin, Blockstream, anyone.
legendary
Activity: 4690
Merit: 1276
All I was trying to do was to figure out if you were unable to comprehend IBLT's impacts on block size, or whether you were deliberately ignoring them because they (probably completely) nullify the argument you were trying to make and figured your target audience would be ignorant of them.

Not that it matters much...both possibilities suck for you.

Wrong on all counts.

You'd know that if you'd bother to read.

You're just setting yourself up to look even more ridiculous.

The profligate nature of your writing and speaking is eclipsed only by the content-less nature of both.  I swear to Christ I've never gotten so little out of a one hour podcast as I did with that thing I listened to the other day.  I'm not going to track down all your spam so pop up a link if you have one.

Speaking of the podcast (with some fake accent guy who spent the last 10 minutes of his time doing jl777 a solid), what was really funny was that even with 40 minutes or so to burn you still deferred on trying to explain the OT thing because, supposedly, it was to complicated or some such.  Signing an XML is complicated?  Or tracking some sigs with a centralized server system?  Ya, OK.  Occam's razor suggests that you didn't want to try to describe it because it is lame and mostly useless.

I'm going to give you guys a little help understanding what is missing.  OK, so I make a 'contract' and break it.  What are you going to do?  Kick me out of your Ayn Rand fun-fort?  You need some sort of enforcement.  Fiat has it because they have a court system.  Bitcoin has a proof-of-work.  As far as I can see, OT has bunkus unless you somehow major visibility and I don't see that happening.  Maybe you could attach to someone with a user tracking and validation charger (e.g., CoinValidation) but I suspect they'll tell you to piss up a rope and just role their own instead of working with you.  You might offer your solution to Blockstream to try out for their federated kludge.  A proof-of-concept which does something useful probably wouldn't hurt OT any.

legendary
Activity: 2492
Merit: 1473
LEALANA Bitcoin Grim Reaper
I agree doing a 10-20 min video to explain what D&T talked about in the OP would be very helpful in getting more people to understand the real issues with keeping a 1 MB cap going forward.

hero member
Activity: 896
Merit: 1000
Why can't someone just make a video explaining this concept and idea, for people that aren't techies because i have a few people already ask what is going on.
Because this is only going to lead to wide speculation for those who think or make crap up.

Kinda like the anti vaxors.
legendary
Activity: 1106
Merit: 1026
The part about showing the limitations based on average txn size of the last million transactions is quite interesting. I guess the idea of 7 tps limit did not take into account the variability of tx sizes. It is always good to over estimate (or under) to make sure your estimations are likely to be within the bounds of the claims being mentioned. Clearly the 7tps claim did not account for that.

According to my data the average transaction size is higher than expected, and slowly growing.



Average on the chart equals average of all transactions, where data points are based on the average of 2500 block intervals. The full data table is available here, though as image and only until block 327500, but it should provide a ballpark: somewhere around 500-600 byte per transaction.
legendary
Activity: 1400
Merit: 1013
All I was trying to do was to figure out if you were unable to comprehend IBLT's impacts on block size, or whether you were deliberately ignoring them because they (probably completely) nullify the argument you were trying to make and figured your target audience would be ignorant of them.

Not that it matters much...both possibilities suck for you.
Wrong on all counts.

You'd know that if you'd bother to read.

You're just setting yourself up to look even more ridiculous.
legendary
Activity: 4690
Merit: 1276
Speaking of intellectual integrity, when are you going to share your infinite wisdom on the effects of IBLTs on 'natural' blocksizes?  I couldn't help notice that you've ignored my comment when I inserted it into your supposedly coherent argument that blocks should remain small even if the max size is raised 'cuz they always have.  You are not alone among people who want to remain mum on IBLTs though.

So far I've published about 5000 words regarding the economics of block size and related topics.

You are perfectly free to read what I have written to see if your question is answered or not.

If you're going to demand a concierge answer without even bothering to participate in the public discussion, you should know that you certainly haven't earned that.

All I was trying to do was to figure out if you were unable to comprehend IBLT's impacts on block size, or whether you were deliberately ignoring them because they (probably completely) nullify the argument you were trying to make and figured your target audience would be ignorant of them.

Not that it matters much...both possibilities suck for you.

hero member
Activity: 764
Merit: 500
I'm a cynic, I'm a quaint
All it takes for transaction fees to go down to ~zero is a benevolent or a malevolent miner occasionally accepting 0 fee transactions.
One miner accepts 0 fee transactions. Why would the other follow their example?
If "enough" (1 large or many small) miners are willing to fill 20 MB blocks of ~0 fee transactions, then some bitcoin users will send ~0 fee transactions, and some miners that mine for transaction fees will stop mining, which weakens the security of the bitcoin network.
This is dumb.  Let us say one miner starts filling 20MB blocks with 0-fee transactions.  Let's say that there are users out there who supply her with 0-fee transactions.  Miners who are mining for fees will just ignore the 0-fee transactions, which means people who do 0-fee transactions just have to wait until the one miner who accepts them happens to get a block.

That means that the user has a choice between an 0-fee transaction that may or may not eventually get onto the blockchain at some unknown time in the distant future, or a fees-paid transaction that will get into the next block.  So, fees-paid transactions will keep happening because people don't want the uncertainty, delay, and hassle of wondering whether and when their tx will go through.

But it gets better.  That miner who is filling giant blocks with 0-fee transactions?  She's competing with miners who are collecting fees.  In that competition she will go broke.  So to the extent a miner can cause a problem by the behavior you describe, it's a self-correcting problem.

There are more logic faults in their post.

(Numbers made up.)

After the fork, the government could regularly post blocks with a million transactions in it.
Any entity that finds a block could fill it with the transactions they want to include. That includes the government.
If it happened regularly enough, people would lower their transaction fees, and some profit-seeking miners would leave.
Two non sequitors. Why would people lower their transaction fees? And why would it make some miners (I assume all miners seek profit) leave?
They can try to do the same thing before the fork, but each time they are limited to posting blocks with only 100 transactions in it. There's still scarcity, and fewer miners will leave.
Again a non sequitor. Why would miners leave if another miner is filling blocks with 0 fee transaction? Average block size at the moment is (well) under half a megabyte. Blocks are not even half full on average. How is that scarcity?
Granted, scarcity is not driving mining at this time. But transaction fees were "supposed to" take over mining bounties (which I think is bad design, see below).
Profit is driving mining at this time. I don't see that changing anytime soon.
I still don't get how you go from “Miners are mining at a loss” to “This is proof of stake”.
There are four groups of people (a) stakeholders, (b) saboteurs, (c) transactors, and (d) miners.
Care to elaborate on how you came to these groups? They are definitely not mutually exclusive.
With PoW, stakeholders want to protect their coins from saboteurs, and for some reason transactors pay miners to do so. That's pretty convoluted! Transactors and miners would be just as happy destroying the blockchain, if it enriched them somehow. (We've seen attack vectors along these lines.)
That's not why people pay a transaction fee. Transaction fees are paid to verify a transaction. That's what it's all about, isn't it? Trustlessly verifying transactions. The transaction fee is supposed to be an incentive for a third party to verify a transaction.
However, if block size is increased, there's really no reason why most miners won't include as many transactions as possible, since it doesn't really cost them anything.
It will cost them in bandwidth, storage space, propagation speed (chance of orphans?). Miners will find a balance that optimizes their profit.
Transactors will no longer be required to pay to have their transactions included in the blockchain,
There is no requirement to pay transaction fees right now.
and eventually profit-seeking miners will leave.
Non sequitor. It doesn't happen now, at least explain why would it happen tomorrow?
Stakeholders will still need to protect their coins from saboteurs. Suddenly, stakeholders will either have to mine themselves, or send bitcoin to themselves with large fees, in order to keep miners in the game (which is inefficient, because sometimes the fees will go to saboteurs). In this scenario, we've realigned the costs of maintaining the integrity of the blockchain: the transaction fees have dropped, and stakeholders are paying to protect their coins. These are the same incentives as PoS.
What if scenario filled with assumptions. Can't be bothered to disseminate this further.
However, this is a really inefficient way of determining which ledger is correct.
It seems to be working quite well at the moment.
There are at least two ways to do so:

(1) You can ask the stakeholders and the saboteurs to fight it out. The last one standing decides which ledger is correct. This is PoW.

(2) You can just ask the stakeholders which ledger is correct. This is PoS.
And the stakeholders will include saboteurs who will confidently tell you their ledger is correct... And the one that managed to get the largest stake gets to decide. The way you put it actually convinced me that it is a good thing to separate the people making transactions / holding an amount of currency and the people verifying their transactions.
Thoughts?

TL;DR:
The same thing we do every night, Pinky.
legendary
Activity: 924
Merit: 1132
All it takes for transaction fees to go down to ~zero is a benevolent or a malevolent miner occasionally accepting 0 fee transactions.

One miner accepts 0 fee transactions. Why would the other follow their example?


If "enough" (1 large or many small) miners are willing to fill 20 MB blocks of ~0 fee transactions, then some bitcoin users will send ~0 fee transactions, and some miners that mine for transaction fees will stop mining, which weakens the security of the bitcoin network.

This is dumb.  Let us say one miner starts filling 20MB blocks with 0-fee transactions.  Let's say that there are users out there who supply her with 0-fee transactions.  Miners who are mining for fees will just ignore the 0-fee transactions, which means people who do 0-fee transactions just have to wait until the one miner who accepts them happens to get a block.

That means that the user has a choice between an 0-fee transaction that may or may not eventually get onto the blockchain at some unknown time in the distant future, or a fees-paid transaction that will get into the next block.  So, fees-paid transactions will keep happening because people don't want the uncertainty, delay, and hassle of wondering whether and when their tx will go through.

But it gets better.  That miner who is filling giant blocks with 0-fee transactions?  She's competing with miners who are collecting fees.  In that competition she will go broke.  So to the extent a miner can cause a problem by the behavior you describe, it's a self-correcting problem.


legendary
Activity: 1400
Merit: 1013
Speaking of intellectual integrity, when are you going to share your infinite wisdom on the effects of IBLTs on 'natural' blocksizes?  I couldn't help notice that you've ignored my comment when I inserted it into your supposedly coherent argument that blocks should remain small even if the max size is raised 'cuz they always have.  You are not alone among people who want to remain mum on IBLTs though.
So far I've published about 5000 words regarding the economics of block size and related topics.

You are perfectly free to read what I have written to see if your question is answered or not.

If you're going to demand a concierge answer without even bothering to participate in the public discussion, you should know that you certainly haven't earned that.
Pages:
Jump to: