Bitcoin Forum
September 23, 2024, 01:06:31 PM *
News: Latest Bitcoin Core release: 27.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 [25] 26 27 »
481  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 22, 2010, 11:51:03 AM
Let's drop the analogies then and go straight at the problem.

The maximum block size is big, having room for all or most transactions.
Therefore, transaction fees are (close to) zero.
Therefore, total block transaction fees are also (close to) zero.
Therefore, all for-profit block generation ceases.
Therefore, difficulty drops.

If for-profit block generation was the only generation going on then difficulty would be very low and double spending very easy. The only thing that can save the system is people generating at a loss.

Now we have a lot of bitcoin holders that would lose greatly if payments become unreliable and confidence in the system drops. Will they contribute to their common good? If they do it will not be out of self interest. If you contribute to the system reliability you lose your contribution and benefit very little because the benefit is shared with everyone. If you use the system without contributing you benefit from everyone elses contributions anyway.

The usual sad result is that everyone tries to live off of everyone elses contributions, very little is actually contributed and everyone loses.

Classic tragedy of the commons.


I agree with db on this. The issue can be put simply like this: the generator which accepts the lowest fees, makes the most profit. given any two generators with the same capacity.

I don't quite understand da2ce7's post, but he seems to be implying that it's profitable "in the long run" to accept higher fees only. This seems flawed, because in the short run, such a generator will be the first to go out of business.

I want to start thinking about solutions.

One avenue might be to impose some sort of protocol restriction on the fee distribution of transactions in a block. In such a way that generators can't just include every little transaction in a block or else the network will reject it. For example, for a block to be valid, no more than half of the transactions in the block can have fees below the average fee for that block. So, if 10 transactions have a fee of 1BTC and 10 more have a fee of 0.5BTC the average is 0.75. Now half the fees are already below this so an additional transaction with a 0.5BTC fee cannot be accepted, but a 0.8BTC fee is okay. That's just an example, I'm not sure if it would actually work.
482  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 22, 2010, 04:51:07 AM
In the future we will have generators that will _not generate_ until there is a certain amount of high fee blocks waiting, and then they will automaticity turn on their massive generation capacity and quickly generate the block.  This leaves the average difficulty relatively low, and makes a strong incentive to include larger fees.  These generators plainly won’t include any low fee blocks, low fee blocks will have to wait around for a charity block.

How will the fees build up if the smaller generators are constantly processing them. there isn't going to be a sudden influx of high fee transactions... The large generators will simply be leaving all the profit to competitors. And if the competitors are snapping up any transaction no matter how small the fee, there is little incentive to pay a high fee in the first place.
483  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 21, 2010, 11:14:36 PM
I think there is an important difference. When one generator is faced with deciding to take tiny fees and fill up the block or leave them will compare the immediate gain of fees to his future loss via the general reduction of fees. But unless he has significant market share this general influence will affect other generators more than himself.

<here I paused to think for several minutes and almost deleted my post>

I was thinking that he should ignore the influence on other generators and simply calculate how much on average he expects fees to rise by keeping the cheapest fees out of his blocks and see if it is worth it. But then I realized that he actually benefits from reducing fees because they will remove marginal generators and decrease difficulty resulting in him generating blocks more quickly. And he will keep these particular small fees from going to a competitor as well.

I still can't say for sure, but I think the best strategy will be to accept all fees.

The bread story is not so good because almost everyone prefers the morning bread and won't wait just for a discount.

This is the problem: there is NO incentive to NOT accept every fee paying transaction, unless the fee is extremely small (ie. it costs more for the ram + cpu time than the value of the fee). Fundamentally, I think there has to be a built in cost for generators to process a fee and this cost must scale with economic activity.

Adjusting the block size automatically is fine, if you can find a function that scales appropriately. This creates an artificial scarcity for transactions, so generators prioritize higher fees.

We need more debate on this issue. This is a serious economic flaw.
484  Bitcoin / Development & Technical Discussion / Re: Block size limit automatic adjustment on: November 21, 2010, 10:49:58 PM
It seems to me that the spam issue and the txfee issue are related. Some want to limit the block size to stop spam and some want to limit it to create an artifical scarcity to drive up txfees.

The problem, as I see it, is that there is NO incentive to NOT accept a fee paying transaction, unless it's ridiculously small. Once a generator has established his infrastructure, It costs a negligible amount to process a transaction. If you can impose some sort of protocol rule on blocks that makes smaller fee transactions less desirable, this would solve both problems.

Automatically adjusting the block size is a solution, if you can find an algorithm that scales appropriately with economic activity. If set too high, there will be too much spam and transactions will be too cheap; generators will leave. If set too low, transactions will become very expensive and people will stop using bitcoin.

Also, there is the idea of restricting the distribution of transactions fees in each block. Like mandating that a frequency distribution of fees fit a linear scale. I don't know if this is workable, I'm just throwing ideas around.

So, I think that we need an incentive for generators to NOT accept fee paying transactions as they get smaller. I particular, build in some sort of fixed cost to processing a transaction, that adjusts with the market.
485  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 21, 2010, 01:09:05 AM
The maximum block size must be continuously adjusted to keep the transaction prices stable. The only way to change the maximum block size is through a lengthy political process of debate, decree, network fragmentation and majority agreement.

This is a bad idea. The generators will collude to keep the block size small; transactions scarce, gouging the market.

Some may try.  Keep in mind that generators have no sustainable monopolies on generation, not even as a group.  If the major generators collude to keep block sizes small amongst themselves; say by keeping their own max block sizes at 1 meg, but the regular users' clients all have a max block size limit of 3 megs, then the rising backlog of lower fee transactions will attract new players into generation.  Maybe forcing the colluding generators to change, maybe not, but a natural price balance will be maintained.  Perhaps the occasional blockchain split fight is neccessary.

Okay, I'm starting to like this idea. It could be a bit messy with blockchain splits, but it seems like it will work.
486  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 21, 2010, 12:56:16 AM
I'm pretty sure the computation time is linear with respect to data size,


Thats true on most calculations, but most certainly not so with data structures that self reference, and a conditional is a self reference.  I'm not sure if it would be true with hashing algorithims or not, but I wouldn't assume that the algorithim is particularly linear in nature.


I meant:
"I'm pretty sure the computation time is linear with respect to data size, for hash functions"

Anyway, as theymos pointed out, you only have to hash the transaction once, not on every attempt. So, this isn't a problem.
487  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 21, 2010, 12:52:06 AM
how about making the max block size a function of the difficulty? If there are too few generators, then the max block size will decrease making transactions scarce. This will drive up the txfee and create incentive for new generators to enter the market. vice-versa.
488  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 21, 2010, 12:34:30 AM
Are you sure? Given any difficulty, you still have to crunch the numbers to solve a block. The more transactions, the more numbers to crunch, thus the longer it takes to compute a given hash.

Block hashes are only hashes of the fixed-size 80 byte block header, which contains a hash of the transactions. Transactions only have a small one-time CPU cost for adding.

Ahhh, okay then. Thanks for the reassurance.
489  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 21, 2010, 12:30:45 AM
I just thought of something. The time it takes to generate a hash if proportional to the number of transactions you're hashing, right? So, it'll take twice as long (on average) to generate a block with 1000 transactions as one with 500. You're not going to waste precious hasing time on small fee transactions, they'll just decrease your hash/s for negligible gain.

I wouldn't assume that it's as straightforward as that, and you are probably overthinking it anyway.  Feel free to try it, though.

Well it's pretty simple really, unless I'm missing something, or hashes don't actually work like I think they do. The more data you have to hash, the longer it will take to compute the hash. Makes sense right? I'm pretty sure the computation time is linear with respect to data size, so double the number of transactions and you double the time to compute the hash.

This is a huge problem now, because why would anyone hash more than one transaction to generate a block. They get 50BTC either way, so you might as well just hash one transaction giving you the optimal hash/s.

I hope I'm wrong about this, I'd really like more feedback from you guys. Perhaps we need a minimum block size or something.
490  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 21, 2010, 12:14:55 AM
The time it takes to generate a hash if proportional to the number of transactions you're hashing, right?

No, not really. It's related to the difficulty factor only.

Are you sure? Given any difficulty, you still have to crunch the numbers to solve a block. The more transactions, the more numbers to crunch, thus the longer it takes to compute a given hash.
491  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 21, 2010, 12:08:47 AM
I just thought of something. The time it takes to generate a hash if proportional to the number of transactions you're hashing, right? So, it'll take twice as long (on average) to generate a block with 1000 transactions as one with 500. You're not going to waste precious hasing time on small fee transactions, they'll just decrease your hash/s for negligible gain.

Say for example, there are 999 transactions with 0.1 fee to process and one transaction with a 1BTC fee. It's more profitable to just process the one transaction and ignore the rest, because your hash/s will be 1000 times faster!

Now if you have 10 transactions with a 1BTC fee, your best off processing all 10 of them, because there's a small overhead in processing a hash. But, including an 11th transactions for 0.9BTC fee probably won't be worth it. 0.99BTC fee, maybe. It depends on the size of the overhead.

This implies that generators will only process the transactions with the highest fee! I'm still thinking through the implications of this. Ideas anyone?

492  Bitcoin / Bitcoin Discussion / Re: What will keep transaction fees up? on: November 20, 2010, 11:05:47 PM
The maximum block size must be continuously adjusted to keep the transaction prices stable. The only way to change the maximum block size is through a lengthy political process of debate, decree, network fragmentation and majority agreement.

This is a bad idea. The generators will collude to keep the block size small; transactions scarce, gouging the market.
493  Bitcoin / Bitcoin Discussion / Re: Why Are You Sold On Bitcoins? on: November 20, 2010, 10:39:56 PM
Lack of centralized (government) control and fixed supply.
I think that if bitcoin becomes widely adopted, it will severely mitigate the ability of government to raise revenue by force (tax and inflation). This will shrink the size of government and make it more accountable.

No dependance on 3rd party for transactions.
Bitcoin gives us a way out of the parasitic banking system and limits the ability of the government to monitor/audit our economic activity. This means it will be very difficult to regulate much of the economy leading to freer markets and therefore, greater economic growth. Taking away the power of the government to manipulate markets kills the incentive for corporate-government partnerships.

Bitcoin is nothing short of revolutionary.
494  Economy / Economics / Re: When to "move the decimal points" ? on: November 20, 2010, 12:13:58 AM

The 'max 8 decimal places' can stay for a while... Just my 0.0298723 BTC Cheesy

The 'max 8 decimal places' will have to stay for a long while, since that is a byproduct of how the bitcoin value is stored.  It's a very long (binary?) integer (64 bit, I think) and has no decimal point.  The clients simply display the values with a decimal point in the middle of the base 10 translation of the  integer, as there are 8 decimal places to each side of the display.  Changing that might prove to be a breaking change, and may not be an easy one.  I don't know how difficult it would be to switch to an 128 bit integer, but since I don't think that there is any OS that yet process 128 bit natively I imagine that might have to come first.

Wouldn't it by much easier to, for example, put a 1 as the first bit of the 64bit int to indicate a 16bit shift in the interpretation of the remaining bits?
so if I have 0000 ... 000110101 coins this could also be represented by 1000 ... 0001101010000000000000000, but now I have 16 more bits of low range precision.

It's not like the first bit will be used for anything else. no one will ever have 2^64 nanobitcoins. Alternatively you could change the precision after a agreed upon block number.

This seems to me much easier that changing the integer size. Clients just need to have a consensus about the protocol change.
495  Bitcoin / Bitcoin Discussion / Re: BitDNS and Generalizing Bitcoin on: November 18, 2010, 06:38:26 AM
I didn't read the thread, but you might be interested in the Netsukuku solution to distributed dns:
http://en.wikipedia.org/wiki/Netsukuku#A_Netsukuku_Domain_Name_Architecture

Netsukuku:
http://netsukuku.freaknet.org/
496  Bitcoin / Bitcoin Discussion / Re: Which method do YOU use to buy Bitcoin for cash? on: November 16, 2010, 03:29:59 AM
I used e-forexgold to buy liberty reserve using bank transfer. It took 2 days to clear and cost me %5 in fees.
497  Bitcoin / Bitcoin Discussion / Re: Have you ever accidentally send Bitcoin to the wrong person? on: November 13, 2010, 07:13:19 PM
Sweet! 17 BTC. thanks Bruce. ;-)
498  Economy / Economics / Re: Buy Silver - Crash JP Morgan on: November 13, 2010, 09:47:39 AM
Alex Jones didn't seem too enthusiastic about the plan. I would be cool if they actually pulled it off.
499  Bitcoin / Bitcoin Discussion / Re: Open Transactions: untraceable digital cash on: November 13, 2010, 09:32:57 AM
I think that neural networks are going to be a huge thing. The internet will soon become I giant AI hive mind of neural networks and human integration with this system will become more sophisticated with direct brain-to-computer interfaces. We are becoming the internet; the next phase of evolution. cool shit! :-)

I have this idea called "protocol AI" in my novel. The idea is that business interaction are mediated by a network of AI whom jobs is to learn reputation, make judgement calls, and so on. They are manned by game theory experts, who are called judges, but their real job is to make their protocol AI the best mediator on the internet.

Go one step further: artificial neural networks are probably going to surpass the capacity of their biological counter parts (humans). Eventually we'll have ANNs designing ANNs! Your Judges could themselves be computers.

Sounds like a cool book. Have you read Necromancer? It explores the idea of purely digital individuals.
500  Bitcoin / Bitcoin Discussion / Re: Open Transactions: untraceable digital cash on: November 12, 2010, 03:36:24 AM
I like the idea of OT cash backed by bitcoins.

I suppose you can run an OT server on a TOR hidden server? Throwing TOR into the equation gives us a highly resilient system which that government can do little to shut down. Awesome!

Philosophical Tangent...
It seems that the growth of the internet and social networks is quickly out-pacing the ability of governments for control them. I think we are going to see some revolutionary shit in the next 10 years. Bitcoin is one example.

I think that neural networks are going to be a huge thing. The internet will soon become I giant AI hive mind of neural networks and human integration with this system will become more sophisticated with direct brain-to-computer interfaces. We are becoming the internet; the next phase of evolution. cool shit! :-)
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 [25] 26 27 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!