* getting hit by lightning while taking a crap for how many years in a row is equally probable as finding a collision: log(1E-65) / log(6.8E-12) = 5.8 I don't get why you put logs here perhaps because we're talking about taking a crap? lmao! I solved the equation 1E-65 = 6.8E-12 ^ y via log(1E-65) = y * log(6.3E-12) to y = log(1E-65) / log(6.3E-12) The first thing I don't get is this : probability of taking a shit at any given point in time: 1/(60*24*365) = 1/525600 (assuming you take a crap every day and the actual process takes 1 minute) If you take one shit a day, that prob is 1/(60*24) to me THe second thing I don't get is this 1E-65 = 6.8E-12 ^ y I don't understand why "y" would have something to do with the number of years to get your result. I don't mean to be sarcastic or anything, and I might be slow - this is saturday evening to me, I am probably need to focus.
|
|
|
information = inverse of entropy Are You sure? The universe increases in complexity over time. So the interpretable properties of universe that someone might call information also increases. See Shannon. the Universe is a closed system I'm not so sure but it is likely. The scientists does not have a definite answer about such fundamental properties of our universe but we will see. What I think is important is to not mix models here. I know quantuum physicists have exotic models which exchange things from an Universe to another one, but I stay in a thermodynamic POV here There is not such law as of "information conservation" Information can be easely destroyed. Kick a jigsaw for example, or crash a harddisk by dropping it on the floor for that matter. Both cases have the information preserved. jigsaw can be reassembled by examining trajectories of flying pieces. The hard drive will not be damaged by dropping on the floor. I got accident when rack collapsed and spare hard drives fell on hard floor from height of almost 3 meters. All drives tested OK. And even if the hard drive is damaged by dropping, the information is still there, only inaccessible. Of course the information can be destroyed by other means. [/quote] Altho I admit the dropping a HDD is a bad example, the very true relation between entropy and information needs to be understood. Information is a way to order things, entropy is the destruction of that order.
|
|
|
* getting hit by lightning while taking a crap for how many years in a row is equally probable as finding a collision: log(1E-65) / log(6.8E-12) = 5.8 I don't get why you put logs here
|
|
|
1) information = inverse of entropy
2) the entropy of a closed system always increase with time (2nd law of thermodynamics)
3) the Universe is a closed system
4) There is not such law as of "information conservation" Information can be easely destroyed. Kick a jigsaw for example, or crash a harddisk by dropping it on the floor for that matter.
Are you sure about number 3? tbh I am sure of none of these. But as far as thermodynamics are concerned, yes. And as of today, the future of the Universe is a cold place with entropy maximum and all information gone. Maybe some place may be used as vaults to preserve some of it for some time ...
|
|
|
This "oil" bathing is all well and good until.........
1. An Ecap explodes, spraying oil everywhere. 2. You have a "Chip-pan fire" during a critical failure.
HC
+1 Maybe not. Liquids are good at avoiding things to get on fire and at absorbing exploding energy. Fixing it stays a mess tho.
|
|
|
1) information = inverse of entropy
2) the entropy of a closed system always increase with time (2nd law of thermodynamics)
3) the Universe is a closed system
4) There is not such law as of "information conservation" Information can be easely destroyed. Kick a jigsaw for example, or crash a harddisk by dropping it on the floor for that matter.
|
|
|
You can print an address along with it's the private key on a piece of paper
./bitcoind dumpprivkey <bitcoin address you want to give away>
=> gives you the private key
Your friend would just have to import that private key in his wallet =>
./bitcoind importprivkey <private key you sent> ""
|
|
|
You may use http://printcoins.com/I never used that service tho. I have no idea if they are good or/and trustworthy
|
|
|
An address collision would be a SHA256 collision
And if you find a SHA256 collision then bitcoin is the last of our problem
Technically it would be a RIPEMD160(SHA256(SHA256())) collision. Not nitpicking, it's an important distinction given that the last step in that process yields 2^160 possible addresses instead of 2^256. 96 bits of keyspace ain't no joke son. If I understand this right, does this basically mean that each address actually has tons of private keys (only one of which is known)? That reminds me of this joke : An 80-years old woman is attending a lecture on astronomy, where the astronomer states that our sun will explode and transform itself into a red giant within 5 billion years. At the end of the lecture, the old lady asks the astronomer : - How long did you say our sun will last ? - 5 billion years - What a relief ! I thought you said 5 millions !
|
|
|
It's already in the price.
Markets are always ahead of you.
|
|
|
For the record: I will contact the FCC and find out what changes we need to make if any to keep within regulation.
You may want to do it for EU too. the CE thingy is somewhat easy to get: you just make a statement that the device follow the CE specs and you sign it (copy one from another manufacturer, they are all the same), and you join one copy of this auto-signed certificate to each sold device in EU. Ok now, if the device exceeds the CE specs, you may end in trouble, but it's just a matter of measuring the EM fields emitted by the said device, and add a little coil here and there, easy does it.
|
|
|
why is everybody assuming 12$ not to change while calculating for any other circumstance? I dont find too many people thinking about that. After blockhalving we wont see $/btc doubling, because 10,305,400 BTC (according to bitcoinwatch) have been mined already and 7200btc/day vs 3600btc/day wont affect the price like that. Anyway an increase purely based on that fact is pretty much what i expect, but of course there are more factors.
What if btc/$ drops within first days (after the first wave of asic-miners tries to sell their easy mined btc) and everybody mining after that waits for block halving (and $/btc to rise) holding their btcs together? i would expect another bubble like we had some months back, but to peak at around 20-25$..
what you guys think?
methink it's already in the price. It happend when it went from $5 to $10
|
|
|
I estimated this at 50X so 50X ~28Thash/s (the total hash power at the moment) = 1,400 Thash/s =>
50 * 1.4 = 70 , not 28.
|
|
|
There are as many upward trends as there are downward ones anyway.
|
|
|
I have a question. I must admit I didn't read everything about pools handling asics, but, ...
If solving blocks is roughly returning blocks with the first 53 bits = 0 (well, a bit more), pools request miners to return computed blocks with the first 32 bits = 0.
Why not simply make pools specialized for asics which would request returning blocks with the first (32+8) 40 bits = 0 ? that would divide the numbers of returned blocks by 256 and make everyone happy.
I probably missed something. Can someone explain the n00b I am why this would be bad .. ?
|
|
|
To make it more related to bitcoins :
Create a bitcoin address and its private key (with no money in it)
Publish the address and assign the first 256 bits of the private key to the grid bits, keep that secret of course.
At the end of the game, publish the private key so everyone can check that you didn't cheat with defining the 16x16 grid.
my 0.02BTC
|
|
|
Seriously this is very good.
And very very good news.
|
|
|
|