Bitcoin Forum
May 26, 2024, 06:57:28 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 [132] 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 »
2621  Bitcoin / Mining / Re: Noob speculative question: Department of Energy's computer and btc mining on: March 15, 2013, 05:51:32 AM
They will not even have 10% of current Bitcoin network hashing power. Bitcoin network as whole is more powerful than any supercomputer.

Yep. And when the pre-ordered ASICs come on-stream, then the DOE would be <1% and lucky to hash 1 block a day.
2622  Bitcoin / Press / Re: 2013-03-11 Planet Infowars: Bitcoin WILL DESTROY Humanity & Insert A Trojan RFID on: March 15, 2013, 04:56:30 AM
Not sure this is worth being posted in press releases, but yeah, what's the deal about no trash cans? I remember some years ago I was in the subway in london and eventually had to just throw shit on the floor. And talking about trash cans, wish I could offer him one where he could throw his rants.

From the late 1970s to early 1990s the Irish Republican Army used to place bombs inside trash cans (rubbish bins) to kill civilians and damage buildings. They often phoned in a coded warning to the UK govt which meant the area could be cleared first. Unlike 21st century Islamic Jihadists, the IRA terrorists (always called criminals by the UK govt - which is where Bush Jr went horribly wrong in 2001) were often after scare tactics, not always outright slaughter.

All the trash cans disappeared from the streets, but since Blair brokered a peace deal the cans have slowly reappeared. One can usually be found if you want to spend an hour looking!
2623  Economy / Speculation / Re: Fair price of bitcoin after a crash on: March 15, 2013, 01:45:52 AM
Just wait for a tiny bit of bad news to come in about bitcoin

- Exchange hack

- Government outlaws bitcoin

- Something related to regulation

- Flaw in the protocol

- Exchange closes down ala bitcoinica

Then we're gonna see something interesting Wink

Like this week? Worst news in 3 years, flaw in protocol (default max db locks was insufficent).

http://bitcoincharts.com/charts/mtgoxUSD#rg5zigHourlyztgSzm1g10zm2g25zv

= price down $1 after 3 days
Is that interesting enough?
2624  Bitcoin / Mining / Re: What's up with blocks 225883 and 225884? on: March 14, 2013, 10:21:32 PM
Could consecutive empty blocks be a new ASIC miner configuring their setup before starting off properly?
2625  Bitcoin / Bitcoin Discussion / Re: So far we got Wordpress, 4chan, mega, namecheap and reddit so whats next? on: March 14, 2013, 09:49:00 PM
What about other currency exchange sites like

http://www.xe.com

and

http://www.transferwise.com


A lot of bitcoiners already use these sites to deposit into exchanges and buy BTC. Wouldn't it be great if these sites themselves could exchange for BTC?

xe.com would be a very nice adition.. srsly!
...

Absolutely, but xe.com respect the ISO currency convention.

Which is why the Bitcoin community needs to push for XBT as a quasi-official code so that SIX standards are forced to accept it because the mainstream banking system has adopted it.
https://bitcointalk.org/index.php?topic=148229.0

BTC is fine for unofficial use. There is a majority which accepts the need for an X-code:
https://bitcointalk.org/index.php?topic=149150.0

2626  Economy / Speculation / Re: Fair price of bitcoin after a crash on: March 14, 2013, 07:11:58 AM

No it isn't. I explored the use of Bitcoin with a friend just this morning. The biggest problem for her is that the market is not liquid enough to absorb something like $1M without hickup.


This week was an interesting test of that. $2M $3M was cashed out during the worst technical hitch for years, and the market just shrugged it off...

http://bitcoincharts.com/charts/mtgoxUSD#rg5zig30-minztgSzm1g10zm2g25zv
2627  Economy / Speculation / Re: Fair price of bitcoin after a crash on: March 14, 2013, 06:33:17 AM
Mark thread: Extremist Bears Only.

Don't get me wrong. I strongly believe in bitcoin success. In twenty or may be ten years it can reach $50 again. But with current level of volatility it cost nothing.

May I translate?  You were too late for the train and are hoping for a dip to $1 so that you can load up and make 50x your money in a decade (a retirement fund perhaps?).

You should read proudhon's posts because it seems he was on the train and got off and is hoping for the same scenario. One day you might meet up and can sit on a verandah watching the sunset repeating the words "If only...." over and over again....
2628  Economy / Speculation / Re: Wall Observer - MtGoxUSD wall movement tracker on: March 14, 2013, 03:38:18 AM
As a trading newbie i dont understand at all!
Looking at the wall image a couple of posts back, it seems like there is a vertical line to the right... that suggests to me that it would be hard for the price to move up.
The line to the left is way less steep... doesn't that mean it is easier for the price to drop?

How are you supposed to read these images?? Why do you all think the price is about to go up? What are you looking at??

Superficially, you are right. Based upon inspection of wall charts it would seem that the price is more likely to drop than increase.
For every buyer there is a seller at the same price, so for every dollar which buys bitcoin another dollar flees it. What drives prices is sentiment. The sentiment for Bitcoin has been unrelentingly bullish since 2011. Yes, there are dips when the market gets ahead of itself, or when there is a bad news event (this week), but the main trend is intact. The wall at $20 looked formidable, but it was cut like a blowtorch through butter.
2629  Bitcoin / Bitcoin Discussion / Re: Should the bitcoin community ban the Satoshi Dice filter patch? on: March 14, 2013, 12:59:59 AM
The problem is that SD's model is scalable much faster than the Bitcoin network's capability. SD usage could scale 10x while the network capability might only double in that time.
This is an artifact of the extremely low transaction volume that makes fees negligible compared to the block subsidy. The network will be more sustainable when the volume is high enough that transaction fees match the block reward because from that point on increase volume will directly translate in the increased revenue for the miners to pay for the necessary capacity.

Fair enough. Then, what is the path to get smoothly to that future?

There is no proper fees market for block access at present because fees average <5% of the block reward. A 1MB block accommodates about 2400 transactions (ignoring many inputs/outputs possible). With the block reward about $1150 it means an average fee of $0.48 is required to match the reward in value. Is there a consensus on a "reasonable" fee for a vanilla Bitcoin transaction? Is it closer to 5c than 0.5c or 50c? Probably. So the fees market for block space becomes viable when 10MB blocks are common. This is a while off. Until that time SD (and anything with a similar business model) can flood the network, unless these apps are throttled at the discretion of their owners.

2630  Bitcoin / Bitcoin Discussion / Re: Should the bitcoin community ban the Satoshi Dice filter patch? on: March 13, 2013, 09:30:29 PM
Nobody is "passing judgement" on SD (or maybe someone is, but it's unrelated to this) for being gambling or anything like that.
Enabling flooding is simply not possible.

I agree. SD's business model best runs without internalizing transactions, unlike Coinbase or Mt. Gox, who do internalize. The problem is that SD's model is scalable much faster than the Bitcoin network's capability. SD usage could scale 10x while the network capability might only double in that time.

SD brings in a lot of fees, and is "stress-testing" Bitcoin, and highlights the risk of a flooding attack. All these are beneficial to have or know. I did suggest blocking SD yesterday and got criticism for it. I accept that and withdraw that idea. My earlier suggestion stands: which is for fees to somehow rise exponentially for flooding sources on a per block basis. It seems possible to do this, but perhaps it isn't.

2631  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 13, 2013, 07:45:11 AM
Some of this profit can be fairly spent RIGHT NOW on improvements to internalize transaction flow, or it should be blocked until it does. This is the real choice.

Sounds like extortion, doesn't it?

The Story of Bit City and its Transport System

Bit City has a privately run train system. Its shareholder's capital is being pumped into it at a regular pace until passenger volumes increase to make it self-funding and then profitable. In order to encourage passenger numbers Bit City Trains (BCT) are offering family tickets at a rock-bottom rate, hoping to attract groups instead of just individual commuters, some of whom pay well for a seat already, yet overall commuter revenue is not high.

Bit City has a bus company called Efficient Coach Interchange (ECI) owned by Mr Dihsotas, which has some ticket revenue, but, by itself is not profitable. Lo and behold there is an opportunity.  BCT has a network which goes to all suburbs and even neighboring towns. If the ECI buses went to all those places he would make a good profit on all the customers which would flock in.

Mr Dihsotas decides to park his buses at all the stations and sells tickets to all destinations. The clever part is that every passenger who buys a bus ticket automatically gets adopted into Mr Dihsotas' family, so they get to use the train network during their bus journey for a low price. This is so popular that soon there are thousands of passengers crowding BCT's trains, forcing extra rolling stock to be used. The trains are often full, but BCT shareholders are not making a profit yet, even though family tickets are making more money than all the commuter tickets combined. There is also a steady stream of complaints from regular commuters about lack of seating, long queues, platforms too short for the extra carriages, it goes on.

Bit City Trains has the illusion of success but something is just not right. The share price is high, but for how long? At the AGM one of the shareholders heckles the board saying that Mr Dihsotas should not get the family discount tickets anymore....
2632  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 13, 2013, 05:12:52 AM
Cumulative Fees Paid:        2837.93797500 BTC

What's wrong with the fees paid? Those all went to miners.

It is a small fraction of the total revenue, swamped by the block reward, Collectively revenue is doing very handsomely at the moment anyway:
https://blockchain.info/charts/miners-revenue
does Bitcoin need to be forced to have high fees at this time?

The problem is that the SD volume is essentially unbounded and is stress-testing Bitcoin quickly towards a known limit (the 1Mb block size) but now also finding a previously latent limit (default number of db locks) along the way.

I posted this only a few hours before the chain fork situation arose because I was worried about SD accelerating Bitcoin to the 1MB limit.
https://bitcointalk.org/index.php?topic=150493.msg1612165#msg1612165

My suggestion was to slowly push back flooding ("dead puppy") volume with higher fees targeted at that source.
Ultimately SD is under the control of the Bitcoin community. But what it is doing could be replicated in an attack by a malicious group.
2633  Bitcoin / Mining software (miners) / Re: Deepbit pool and other old version Miners: Time is running out to upgrade! on: March 13, 2013, 03:18:40 AM
Good news. It seems that more people on v0.7 at the moment the better!
2634  Bitcoin / Development & Technical Discussion / Re: The MAX_BLOCK_SIZE fork on: March 13, 2013, 03:16:25 AM

No, you misunderstand the problem and in the process spreading FUD. 0.8 LevelDB was required to emulate BDB behaviour and it didn't.

Rushing everyone onto 0.8 is asking for problems.

Deepbit has been prudent and a pillar of defending the blockchain and you are pressuring them to do what exactly?

Criticizing 0.8 for not emulating an unknown bug (let alone that it was in 3rd-party software) is itself FUD.
It appears 60% of the network would have recognized the problem block. If more people were prepared to upgrade in a timely manner then it might have been closer to 90% and a minor issue arguably leaving a better situation than exists now.


Please give the development team time to put together a plan.  If the majority of miners are on 0.8, a single bad actor can cause another fork by making a block with too many transactions for <= 0.7 to handle.

+1

Yes. I agree with that because of where the situation is now.

2635  Bitcoin / Bitcoin Discussion / Re: Alert: chain fork caused by pre-0.8 clients dealing badly with large blocks on: March 13, 2013, 01:08:59 AM
Also, I'm afraid it's very easy to say "just test for longer" but the reason we started generating larger blocks is that we ran out of time. We ran out of block space and transactions started stacking up and not confirming (ie, Bitcoin broke for a lot of its users). Rolling back to the smaller blocks simply puts us out of the frying pan and back into the fire.

We are only in this situation because ONE source application is flooding the network with low fee transactions. That source application is abusing the Bitcoin network as a messaging system because it helps their business model run just slightly more conveniently for them.

.....
 1dicegEAr   56000      0.85449 |    62398 |   52977 (0.85686) |    8850 |     571 |   77209.45 |   76593.02 |   400.54 |    616.42 |  99.202
 1diceDCd2   60000      0.91553 |    95911 |   87374 (0.91620) |    7992 |     545 |   70581.58 |   69778.98 |     0.50 |    802.59 |  98.863
 1dice9wVt   64000      0.97656 |    16558 |   15147 (0.97956) |     316 |    1095 |   23993.71 |   23581.20 |   240.19 |    412.51 |  98.281
----------------------------------------------------------------------------------------------------------------------------------------------
           small (bets < 4 BTC) |  3522656 | 1452152           | 2054095 |   16409 |  766592.38 |  752057.27 |   261.23 |  14535.10 |  98.104
            big (bets >= 4 BTC) |   114417 |   52348           |   61777 |     292 | 2635378.11 | 2579381.45 | 23628.70 |  55996.66 |  97.875
----------------------------------------------------------------------------------------------------------------------------------------------
                                |  3637073 | 1504500           | 2115872 |   16701 | 3401970.49 | 3331438.72 | 23889.93 |  70531.76 |  97.927
----------------------------------------------------------------------------------------------------------------------------------------------

SD Profit before fees:      70531.76560380 BTC (2.073%)
Cumulative Fees Paid:        2837.93797500 BTC
SD Profit after fees:       67693.82762880 BTC (1.990%)
Pending Liabilities:          -74.93245984 BTC
Final SD Profit:            67768.76008864 BTC (1.992%)
----
Since Satoshi Dice started, there have been:
Blockchain Tx: 11423662  :  SatoshiDice Tx:  6698542  (58.6%)
Blockchain MB:   4904.6  :  SatoshiDice MB:   2753.4  (56.1%)[/font]


Some of this profit can be fairly spent RIGHT NOW on improvements to internalize transaction flow, or it should be blocked until it does. This is the real choice.
2636  Bitcoin / Bitcoin Discussion / Re: Miners: Demand more in fees from the userbase by blocking spam transactions on: March 12, 2013, 11:38:36 PM
This is becoming very serious.

http://sourceforge.net/mailarchive/message.php?msg_id=30589099

The thrust of the OP is addressing the most urgent issue affecting Bitcoin right now.
2637  Bitcoin / Bitcoin Discussion / Re: Why the hell this shit was not tested on testnet? on: March 12, 2013, 11:08:42 PM
Maybe the alert system should be used to force client upgrades, it is abit draconian but we can't risk the whole premise and validity of bitcoin because some people are slow to upgrade

Worst idea in the last 24 hours.  That is pretty amazing given the pretty much nonstop run of bad ideas.  There will not and should not EVER be a forced upgrade option for Bitcoin.  Not today, not tomorrow, not a century from now.  Your idea would be a "kill bitcoin" button available to anyone with the resources (either financial or through use of force) to push it.

That's not quite right D&T because we already have a forced upgrade situation imminent!

http://blockorigin.pfoe.be/top.php

When the percentage at the bottom of that screen goes from 78% to 95% then 5% of the hashing power is forced to upgrade or cast adrift.
However, IMHO, this is the only way Bitcoin can progress from a crypto-experiment to a world-beating currency and payments system.

There is a difference between that and the aforementioned force upgrade. One gives you the "or cast adrift" option; the other changes the software on your computer. One is beneficial, the other is a "kill bitcoin" button.

That's why I said "not quite right" rather than flatly refute. There are a lot of perspectives to the argument.
Of course I reject forced changes of software as you (and whitenight) describe.
2638  Bitcoin / Mining software (miners) / Deepbit pool and other old version Miners: Time is running out to upgrade! on: March 12, 2013, 10:14:49 PM
Over 80% of new blocks are now Version 2. Once this hits 95% any version 1 block you mine will be rejected by the network.
An upgrade to 0.7 is necessary (or 0.8.1 when available).
Yesterday, core dev and btc guild rescued miners on an old version, but it won't happen for version 1 miners when they are churning out orphans with unspendable rewards.

Don't be among the last few heading for the exit on version 1 getting guaranteed down-time.

The percentage at the bottom of this screen is moving centre-stage in the Bitcoin show now:
http://blockorigin.pfoe.be/top.php


2639  Bitcoin / Bitcoin Discussion / Re: Why the hell this shit was not tested on testnet? on: March 12, 2013, 09:29:01 PM
Maybe the alert system should be used to force client upgrades, it is abit draconian but we can't risk the whole premise and validity of bitcoin because some people are slow to upgrade

Worst idea in the last 24 hours.  That is pretty amazing given the pretty much nonstop run of bad ideas.  There will not and should not EVER be a forced upgrade option for Bitcoin.  Not today, not tomorrow, not a century from now.  Your idea would be a "kill bitcoin" button available to anyone with the resources (either financial or through use of force) to push it.

That's not quite right D&T because we already have a forced upgrade situation imminent!

http://blockorigin.pfoe.be/top.php

When the percentage at the bottom of that screen goes from 78% to 95% then 5% of the hashing power is forced to upgrade or cast adrift.
However, IMHO, this is the only way Bitcoin can progress from a crypto-experiment to a world-beating currency and payments system.
2640  Bitcoin / Bitcoin Discussion / Re: Should the bitcoin community ban the Satoshi Dice filter patch? on: March 12, 2013, 09:08:24 PM
They are now also responsible for a fork on the chain, like the spam wasn't enough.

I usually steer clear of these particular trains of thought, but you do understand SD wasn't responsible, right? A bug in the BDB code caused this, and yes, SD did trigger the bug but while it was a nuisance to be very mild (I lost almost 4 hours of what was otherwise already too little sleep for this), it does mean some big enterprise (read government) that happens to find this bug can't create havoc and properly abuse this situation with properly prepared double spends and the like.

Honestly, I strongly believe everyone is entitled to their own opinion, mine isn't better than yours outside my own system of values but this community should keep together a little better and your constant calling wolf isn't helping, in my opinion... it is just my opinion! I don't really care too much what other people think anyway, unless I perceive a chance of learning from them.

In fact SD didn't trigger the bug.
The devs rushing to "fix" things which could be "fixed" by SD changing it's ways instead of "fixed" on the network level was the trigger.

+1
Pages: « 1 ... 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 [132] 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!