Bitcoin Forum
July 12, 2024, 02:51:52 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 [535] 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 ... 800 »
10681  Other / CPU/GPU Bitcoin mining hardware / Re: 7990 revealed..... on: March 26, 2012, 11:12:14 PM
Hope this thing hits soon. Bring on the flood of HD 5970s  Cool

Hell no, don't do that. I've spent all I can afford to at the mo on used 5970s, and had to pay prices that were a fair bit higher than I initially budgeted for (most expensive cost me £330). If I have to sell my family into slavery* for my rigs, the rest of you can bloody well too.




*I don't have a family. But if I did...

I think you are lying.

How on earth you got to pay only 330 GBP for a 5970 is beyond me.

Prices are 400 GBP at least Sad

I see 5970s routinely sell on eBay in the US$400 range, both in the US and in the UK. Why on Earth would you pay 400GBPs for a used one?

UK eBay checked just now only buy it now offer for 5970 is 400 GBP.

Maybe eBay only shows me the high priced GPUs Cheesy

But seriously 330 GBP for a 5970 in the UK is a STEAL.

Must be a lot of stealing going on then...
http://www.ebay.co.uk/csc/i.html?rt=nc&LH_Complete=1&_nkw=HD%205970&_fln=1&_trksid=p3286.c0.m283

Completed listings.
£275.00
£320.00
£290.00
£300.00
£325.00
£300.00
£240.00
£258.00

Actually can't find a COMPLETED sale for >350.  Granted there is always the idiot noob who values his crap at insane prices but I am willing to wager a BTC that card doesn't sell for 400.00 and likely the idiot will try again 2 or 3 times and then drop it to 350.00
10682  Bitcoin / Bitcoin Discussion / Re: Could Satoshi ever spend his Bitcoins? on: March 26, 2012, 09:51:24 PM
This story has all of the makings of a post-apocalyptic religious text.

In the beginning there was only the endless fiat and the masses cried out in agony from the persecutions inflicted upon them by the FED. The Satoshi said let their be a block and there was a block and it was good.  The world was divided between the fiat and the block and it was good ...
10683  Bitcoin / Pools / Re: [340GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: March 26, 2012, 09:46:56 PM
So it has come to this. P2Pool miners joining the Mystery Miner in the transaction throttling attack.

Funny.  Charging for a service = attack.  In related news mining pools and Mt.Gox daily launch massive attacks on the Bitcoin economy.

Also please don't slander p2pool.  p2pool is made up of individual members.  Saying p2pool is attacking Bitcoin makes no more sense than saying Bitcoin is attacking Bitcoin.  Be a man and say DeathAndTaxes is attacking the network when you lie.


I would say something like "cry bitclown cry, your freeloader tears only nourish me", but that would be trolling so I won't.
10684  Other / Beginners & Help / Re: Transactions fees at this time on: March 26, 2012, 09:44:51 PM
There is no standard tx fee.  Non spam tx can be sent with 0 BTC and will be considered valid.  Miners have the choice of what tx they will include and can exclude tx that have too little (or no) fee, but almost all include all valid (non spam) txs regardless of fee.

About spam.  To protect the network the protocol requires a fee of 0.0005 BTC if the inputs are less than 1 bitcoin day old*.  For example if you received 1 bitcoin and wanted to spent it you would have to wait 1 day to avoid a fee.  If you received 10 bitcoins you would need to wait 1/10th of day.  If you received 0.1 BTC and wanted to spend it you would need to wait 10 days.

If you wait that long (or longer) you can send coins without any fee.  If you want to send it early you need to pay the spam-fee.  Other nodes will declare your tx invalid and refuse to relay it if you don't pay the fee.  The client also needs to be modified to get around the fee.  Since unmodified clients will refuse to relay the tx you run the risk of having the tx in limbo or not seen by recipient if you modify a client to break the spam rules.

The important thing is the spam fee isn't designed to "make money".  You can simply wait (or keep some "old coins" handy) and never pay it.  The spam fee is designed to protect the network from a DOS attack involving massive amounts of tiny transactions.

*technically the limit is in blocks but it is roughly 1 bitcoin day which is slightly easier to remember than  57,600,000 satoshi blocks per byte.
10685  Bitcoin / Development & Technical Discussion / Re: Miners that refuse to include transactions are becoming a problem on: March 26, 2012, 09:24:13 PM
sturle I don't think you get the idea of a free market.  

You think 0.01 is too high..  Fine don't pay it.  some miners set fee requirement at 0, some at a single satoshi, some at 0.001 BTC.  Some at 0.01.  The market determines the price.  The intersection of supply and demand.

You make it sound like if I (me little ole D&T) set min fee of 0.01 for my 0.15% of network suddently no tx which a fee less than 0.01 will ever be processed.  Take all your arguments and replace 0.01 with 0.001 instead.  Problem solved.

Quote
This is an increase of 0.01 BTC for almost all normal transactions.  Currently 0.05 USD.  Less than a year ago it would be 0.31 USD per transaction, which is higher than even the normal payment PayPal fees.  And it comes in addition to the collective fee implied by inflation.

Extrapolating the cost when BTC is worth $30 or $100, or $20,000 is just intellectually bankrupt.  Obviously no miner's fees would be fixed in stone for the life of the GPU.  I think a tx should be worth a couple cents.  If BTC price doubles the tx fee can be cut in half and miner generates the same.  As BTC rises competitive pressures will ensure prices are held in check.  That is also a part of a dynamic fee market. Even the spam fee eventually will need to be adjusted.  OH NOES BTC has a 0.005 hardcoded fee on tx smaller/younger than 1 BTC/1day.  When BTC is $100,000 each that means all tx will cost $1,000.  It will cost $1,000 to send $1.00.  OH NOES OH NOES SELL YOUR GPUS NOW BTC IS HORRIBLY HORRIBLY FLAWED.

Ironically you just pointed out something the total cost to users (in terms of fees + inflation) is falling.  Even with a 0.01 fee on every tx without exception (as if I could control 100% of all hashing power on the planet) the implicit cost is lower today than even a year ago and will be significantly lower after the subsidy drop.

Quote
Out of curiosity: Do you pay 0.01 BTC fee for your transactions?

Of course not.  Why would someone pay more fees than necessary?  That is the point.  Charging a higher fee gives those who pay more a higher level of service.  
10686  Economy / Trading Discussion / Re: Mt Gox thinks it's the Fed. Freezes acc based on "tainted" coins. on: March 26, 2012, 09:16:23 PM
Surely anyone who cares about privacy must be a criminal  Roll Eyes

Or terrorist.

The sad thing is some people would be like "damn right".  The whole "you shouldn't care unless you got something to hide" nonsense.

Patriot Act = no problem.   You got nothing to hide unless you are terrorist.
Warrantless searches = no problem. You got nothing to hide unless you are a criminal.
Mt.Gox invasion of privacy = no problem.  You got nothing to hide unless you are a money launderer.

Anyone think that maybe some people don't want Mt.Gox to have their ID (likely in a pile of thousands of other ID poorly protected).  That an image which will give any identity thief an erection.  Remember this is the company too stupid to salt user passwords.  I mean it is understandable since per user salting was only invented in 2010 ... er wait no it wasn't it has been around since the 1960s.
10687  Bitcoin / Development & Technical Discussion / Re: Miners that refuse to include transactions are becoming a problem on: March 26, 2012, 09:08:52 PM
I'm not sure I understand why the fee is always discussed to be flat or per KB.

Because the network has no idea how much the tx is for.  It only knows the inputs and outputs which are greater than the amount being "spent".

Got it.

I really like the suggestion on how to handle micropayments. What i like most about it is it provides miners a means of competition and distinction, and it also gets them into more business than just mining, which, long term, is probably  thankless, low margin work.

Similar system would provide non-51% double spend protection.  Broker gets contracts for 51%+ of hashing power.  Merchant sends tx to broker who sends it to contracted pools.  Pools guarantee they will include tx in the next block and will not replace it will a double spend under any conditions.  A merchant (like say Walmart) would have a high level of confidence they couldn't be double spent economically.  Walmart would process tx instantly using the guarantee provided by a broker.  Likely that 0-confirm guarantee would be worth a lot more than say normal tx processing so it would provide an additional revenue stream for pools/miners.
10688  Bitcoin / Project Development / Re: [BOUNTY] A patch for bitcoind to modify tx list in "getmemorypool" on: March 26, 2012, 08:56:33 PM
If you want, I could trivially build a Windows binary. I won't bill for the time spent by the compiler, of course :p

That would be great.  Thanks.
10689  Bitcoin / Project Development / Re: [BOUNTY] A patch for bitcoind to modify tx list in "getmemorypool" on: March 26, 2012, 07:48:59 PM
".01 BTC" is not a reasonable fee, period. Here's why.

That is how free markets work.  If I want to change 0.01 BTC I can.  Obviously I lose your business.  Someone else might charge 0.005, someone else 0.001, someone else might accept free tx.

There is no scenario where every miner demands the exact same fee amount.

Hypothetically someday lets say:

10% of miners require a fee of at least 0.01 BTC
25% of miners require a fee of at least 0.005 BTC
25% of miners require a fee of at least 0.0001 BTC
20% of miners require a fee of at least a single satoshi.
20% of miners require no fee.

Obviously in reality this sliding scale would have many more data points but using this as an example.

If you included no fee your tx would still be processed but only 20% of the network would be working on it so confirmation time is 50 min.
If you included a single satoshi as a fee then 40% of the network would be working on it so your confirmation time drops to only 25 min.
If you included a fee of 0.0001 (1/20th of a cent at todays value) you buy 65% of the network and avg confirmation of 15 min.
etc.

If miners broadcasted fee schedules and hashing power via a p2p protocol clients could advise users on fees and projected confirmation times.

Another option would be to include a "charity window".  Miner could specify to include x  or x% of outstanding tx which are below the fee limit.  "low fee" tx would be processed first come first serve after priority tx so confirmation times would be longer but they would be processed.

Quote
I would say a "Fair" rate is more like 0.05%, maybe 0.025%, with a spam fee that increases exponentially per digit below the spam threshold, say 20% to send 0.001BTC, 50% for 0.0001BTC, 100% for 0.00001BTC, and doubling forward. Of course, since this was very poorly thought out before client was released, figuring out how to reach any kind of consensus between miners and clients is not going to be easy.

% based fees are neither desirable nor possible in the Bitcoin network.  What you or I consider fair is irrelevant.  Most miners will likely accept 0 BTC tx, each if free to set their own price.  Users are free to set what they are willing to pay.  The market (not you or me) will determine what is "fair".

Fair price in a free market is what someone is willing to pay and someone is willing to sell.  What is being bought and sold is inclusion of a tx in the next block.


Quote
unless all miners and all clients agree to what a reasonable fee is, there's going to be serious conflicts at some point. Either significant numbers of empty blocks, no way for a client to determine what a "good" fee is
That is simply impossible.  100% consensus on "fair" never happens.  Only central control can implement price controls.  IF you feel that is the only possible "fix" then you should uninstall Bitcoin now because it will NEVER happen in a decentralized network.


Quote
and if enough people get tired of that behavior, you might end up on your very own blockchain fork one day. Of course, for the protocol to change at all, and for any reason would generally end up producing large forks, which is a major downside of the BTC system, and of the fact that it's experimental.

This requires no protocol change.  If hypothetically miners setting their own tx fees was outlawed by some future protocol change well I could simply stop (and I likely would stop mining too).
10690  Bitcoin / Development & Technical Discussion / Re: Miners that refuse to include transactions are becoming a problem on: March 26, 2012, 07:30:41 PM
I'm not sure I understand why the fee is always discussed to be flat or per KB.

Because the network has no idea how much the tx is for.  It only knows the inputs and outputs which are greater than the amount being "spent".

Quote
Maybe the client could recommend a Percentage based fee + 1 satoshi per output?

It could but miners have no effective way to determine what that % is. 

I lay out some reasons why % based fee rules are not viable.
https://bitcointalk.org/index.php?topic=73941.msg819583#msg819583


There are alternative methods of handling micro payments.  Long, only read if interested in alternative payment scenarios. One would be bulk contracts.  Say WSJ wants to to charge 0.01 BTC per page.  WSJ could pregenerate a list of payment addresses to provide users.  It would provide a copy of the public addresses to a mining pool.  Since micropayments are unlikely to be a source of fraud and likely need to be 0-confirm anyways WSJ can wait for longer than normal confirmations.

The pool could create a contract with WSJ for a flat fee or a nominal fee per tx. So on a per tx basis maybe the pool has a fee requirement of 0.5 cents (USD nominal) however by signing a bulk contract with prepayment the WSJ effective cost is (1/10th of cent per tx).  WSJ pays $500 and pre-purchases 500K low priority tx.  The pool fills blocks as normal w/ "priority tx" and then fills up the blocks w/ these lower priority tx as space is available.  Sometimes WSJ gets 1 block confirms but often it is 4 blocks, 8 blocks, 20 blocks.

The analogy would be low cost bulk mailing from postal service vs Fedex overnight.  junk mail doesn't work at Fedex prices it doesn't mean everything needs to be one size fits all. 

Now hypothetically if enough micro tx demand existed a broker will acts as middle man.  It would contract w/ multiple pools for their "junk mail rates".  The broker would sell the services to multiple micro tx receivers.  The brokers cut would be based on the difference between what they contract mining pools for and what they sell that service to service providers which use micro txs.


10691  Bitcoin / Pools / Re: [340GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: March 26, 2012, 07:16:14 PM
Custom Fee Rules for p2pool (and solo) miners:

As a p2pool miner would you like to be able to control which tx you include in a block?

I created a bounty to modify bitcoind to allow a miner to set rules on which tx are included in the block they are working on.  Luke Jr has created and published the source code.  Code is open source licensed under MIT license (same license as bitcoin).

As the block subsidy declines over time fees will play an important role in miner revenue.  If users can get included in the next block w/ no fee they will never have an incentive to include a fee.  The RPC calls allow a user to set the minimum fee they will accept and tx w/ smaller fee are excluded from the tx list that p2pool uses to build a block.  p2pool miners also are unlikely to alter the fee dynamic but we can be part of the discussion.  As pools (including p2pool miners) set fee requirements >0 confirmation times for free/low fee tx will increase.  This will create an incentive for users to increase fees.  We aren't talking massive fees but every bitcent helps.

Luke has requested a pull into the "mainline" bitcoind here:
https://github.com/bitcoin/bitcoin/pull/989

Please don't comment at the link above unless you are an active client developer.  Cluttering up this with "yeah add it" is bad form.  I included the link to allow people to allows you to see the status on the pull.

Here the "custom fee" git created by Luke
https://github.com/luke-jr/bitcoin/tree/customfee

I will try to get some compilation instructions up for windows/linux for users who wish to try it out before it becomes part of the mainline.

Non-developers can indicate support with a post in this thread:
https://bitcointalk.org/index.php?topic=73941.0

More support = quicker inclusion in mainline client.

10692  Bitcoin / Pools / Re: [340GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool on: March 26, 2012, 06:33:10 PM
Yeah someone has asked forrest to remove the /xxx+y from charts and reports.

thus "username/3000+1" = "username".  Maybe in a future version.
10693  Bitcoin / Development & Technical Discussion / Re: question about address generation on: March 26, 2012, 06:31:32 PM
Thanks Pieter I learned something today (I knew it would be a good idea to get out of bed).
10694  Other / Off-topic / Re: Mini-Rig from Butterflylabs on: March 26, 2012, 06:30:23 PM
I wish I could give you some info, but at this point please let us have our final unit in front of us before
giving out details. Regarding the dB, it will be virtually silent when compared to GPUs... In fact, it is
engineered that way...

Interesting.

Quote
Good Luck,

Why does BFL always wish me good luck?  Do they think I am in competition with them? Smiley
10695  Bitcoin / Development & Technical Discussion / Re: Miners that refuse to include transactions are becoming a problem on: March 26, 2012, 06:26:32 PM
If Bitcoin transactions get more expensive than PayPal transaction (which you actually suggest for small transactions later in this thread), then people will use PayPal instead, making Bitcoin less valuable for everyone.  It is not in the interest of most miners.

Paypal costs $0.30 plus 2.9%. 

Current fees are roughly 0.001131751 BTC per tx. 
Even if tx fees on avg were 0.01 that would be an 883% increase but still a tiny fraction of Paypal.

However compared to Paypal (using current BTC:USD exchange rate)
$1 USD transferred  Paypal fee: 0.07 BTC (7x higher)
$10 USD transferred Paypal fee: 0.13 BTC (14x higher)
$100 USD transferred Paypal fee: 0.70 BTC (70x higher)
$1,000 USD transferred Paypal: 6.50 BTC (650x higher)

MtGox for example never includes tx fees.  One of the most sucessful bitcoin ventures and it provides nothing in compensation to the network.  The Bitcoin network will eventually need to be run on fees.  Nobody is saying massive fees overnight or that even 1 bitcent is going to make up the majority of block rewards but it starts the ball rolling.

Currently: ~0% fees, 100% subsidy
Someday: 100% fees, 0% subsidy

Even IF average fees were increased 800% (<1 bitcent per tx on average) and tx volume doubles after the block reward declines to 25 BTC fees would only make up 4%.  Still I consider 4% more healthy than 0%.


One Bitcent tx fee would increase fees
10696  Bitcoin / Project Development / Re: [BOUNTY] A patch for bitcoind to modify tx list in "getmemorypool" on: March 26, 2012, 06:15:47 PM
Looks good to me.  Thanks for the prompt response.
If this is complete, where would you like me to send a refund (if you want one) of your advance? Let me know if you would prefer to wait for testing and merging to mainline (which might require more time, depending on the reactions of other developers).

Polvos, you also offered to contribute toward the bounty; if you feel the desire to tip me, you can use 1DGzpZzce1c7nsg1SN7exV6bsaju1Mcrc6 - it's fine with me if you choose not to, though.

I've submitted an upstream pull request. Miners who want this feature should express their support on this thread, and developers with comments can do so on the pull request itself.

No keep the advance.  We likely need some testing and the code may require some tweaking.  20 BTC IMHO is well spent. 

Now is there a guide anywhere for compiling modified version of bitcoind under windows?
10697  Bitcoin / Project Development / Re: [BOUNTY] A patch for bitcoind to modify tx list in "getmemorypool" on: March 26, 2012, 06:07:26 PM
I think everyone would like to see that, but  something slightly more complicated and thorough needs to be thought up.

Of course but right now you choices are accept all tx or pocess no tx.  Here at least you now have some crude control.  This was intended to be a starting point to a) provide p2pool users some control and b) spark a conversation on mining fees.

Quote
No, actually it wouldnt.  This patch does not change the minimum default fee in AcceptToMemoryPool which is required for a tx to a. get relayed through the network and b. be accepted by your node.

For most tx the default fee is 0.00.  It is based on coinage (1 day, 1 BTC input = free).  One could reject only zero fee txs (accept tx which don't violate spam rules and have at least 1 satoshi in fees).

One could modify the spam rules but I didn't want that because I think it is reckless.  The spam rules are designed not to cost users money but to protect the network.  If enough miners foolishly removed the spam rules one could cripple the network, users, wallets with massive (TBs) worth of spam for a negigible cost.  I intentionally asked for the spam rules to be enforced for that reason. 


Quote
Though this only partially applies today (as the 50 BTC per block is usually much higher than any fees), in the future as the 50 BTC/block subsidy decreases, any incentive miners had to do this "for the good of the network" goes away and it becomes get a few coins, or get nothing.  Thus, the fee system could use some help to avoid this very dilemma.

True miners will reduce their direct compensation by excluding paying low fee tx but the amount they lose is essentially negligible.   Chart tx vs fees in the blockchain for the last 100,00 or so tx.  You will notice that even excluding tx w/ fee < 0.01 results in only a negligible drop in gross revenue (as in pennies a block).  With a lower min fee you "lose" even less.

At this point it is more the principal of the issue and to spark a debate.  The "cost" to a miner is essentially nothing (even one with dozens of GH/s).  If not enough miners start enforcing higher fees then fees won't rise but the amount lost remains "almost nothing".  If enough miners start enforcing higher fees then all miners benefit.  Yeah there is some aspect of tragedy of the commons but w/ block subsidies still high (yes 25 BTC is high) the "cost" of helping is nearly nothing.
10698  Other / Off-topic / Re: Mini-Rig from Butterflylabs on: March 26, 2012, 05:49:45 PM
I've seen the Mini Rig CAD mockup and the dense board placement makes my sphincter tense up.  Which sphincter?  All of them.

So share the images (the CAD ones not the sphincter ones).
10699  Other / Off-topic / Re: Mini-Rig from Butterflylabs on: March 26, 2012, 05:36:59 PM
Is there any information how the mini rig or the rig bix will look like? I am wondering what will be their phisical dimension, are they going to be expandable, etc.

I wonder that myself.  I wonder how large it will need to be not because the FPGA take up a lot of space but due to the fact that 2.5KW is a lot of energy and the smaller the pkg the harder it is to cool.  

A visual excercise:
A 4x5970 rig is ~1KW.  Open framed it requires good amount of airflow to cool.   In a closed case, forget about it. Smiley  Now 1.25KW would be 20% more thermal load so image a hypothetical 5x5970 rig (pretend no 8 GPU limit). The "full rig box" (if it ends up getting built) would be double that.   To get an idea of the thermal energy vs volume visualize a 4U server chassis w/ 5x5970s inside now stack two of them on top of each other to simulate 2.5KW of power draw.  That is a pretty big box (8U = 14" by 19" by 24").  Could you cool that with air?
 How noisy would it be?  We already have a pretty large "rigbox".  Going larger would make it somewhat easier to cool.

Before I get flamed:
I am not saying the rigbox isn't more efficient.  It is.  The same sized box with the same amount of electricity/heat would produce 50 GH/s vs ~7 GH/s (10x 5970s). Still the laws of thermodynamics don't care what (or how much) the 2.5KW produced.  50GH/s on 2.5KW or 7GH/s on 2.5KW is still 2.5KW either way.  

That is an interesting challenge.  In mining the difficulty in cooling 1KW+ heat loads is what has lead to open frame rigs, extenders, extra high rpm fans, etc.  Will be interesting to see how they intend to cool them and how noisy they will be.  Not saying high potential noise is a problem (it isn't as most will be in datacenters or semi-industrial locations).  It just may shock some people who think of FPGA as silent and cool but that is just because nobody has scaled FPGA up to tens of GH/s in a compact space yet.

So BFL come on at least give us some estimated dimensions and db specs. Smiley
10700  Bitcoin / Mining / Re: BAMT Quick Start Guide For Newbies! on: March 26, 2012, 04:55:18 PM
BAMT is x86 only.  That means no 8 GPU rigs (at least I have never gotten it to work).  I am converting all my rigs to 8 GPU rigs for improved efficiency.   The other minor annoyance is you need to build cgminer from source if you want to upgrade.  There are no x86 binaries for cgminer so it isn't as easy a "wget" and decompress.

If you only want to use 6 ( not sure about 7) GPU per rig then I found BAMT very "plug and play".  
Download the img, use the writer to write it to a USB stick.  BAMT includes a "fixer" daemon which downloads and installs hotfixes.  Very nice "setup" it just doesn't work w/ 8 GPUs. Sad  I held out hope because developer said he was testing x64 version but "it didn't work".  I guess it was a closed beta so I was never able to try it out.
Pages: « 1 ... 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 [535] 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 ... 800 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!