...
 Is that a sock puppet of Andy Dick?  |
|
|
|
|
Two random pumps in the last 72 hours with no apparent news behind it... me thinks someone has inside info. Gemini next week perhaps?
|
|
|
|
|
Hey OP, any updates when you will start accepting orders and begin shipping?
|
|
|
|
Added New Video: How To Create Dynamic Bitcoin URIsUpdated tinyStore source files to include basic form validation and integrated bitcoin URI to auto-populate payment amount, payment address and item description during the purchase. |
|
|
|
what i wonder is whether this is actually a good thing ... i think it is - if all exchanges pay attention to high level thefts / scams AND track the stolen coins from the point of origin AND every single exchange takes action to confiscate illegally obtained coins pending legal system justice / assists law enforcement in tracking down and punishing these criminals ... then no more bitcoin theft crime ? right ? ... it'd basically fall to the dozen or so major exchanges to monitor and enforce legal activity ... if nobody anywhere accepts *obviously* stolen coins on any exchange then large scale theft would not be possible ? (without adequate mixing / obfuscation of origin / slowly spending of stolen coins for goods) ... personally i'd love no exchange anywhere in the world being willing to accept stolen bitcoin ...
Do we want them making the decision as to what qualifies as a crime? There have been numerous reports about Coinbase tracking for people that gamble. Do you think that is okay? I think it's a slippery slope. Bitcoin should be mathematical and unbiased. If you have the private key that's all that should be required. |
|
|
|
|
"legit".
Whois shows site was just registered today. Spent a lot of time on this didn't you?
Anyone who deposits to this site better be prepared to lose it.
|
|
|
|
Never thought I'd see the day where BTC-e starts policing the coins on their exchange. Bitstamp of finex probably, but not BTC-e. Are they going to start verifying ID's too?
That may happen once Bitlicence takes form. Isn't BTC-e still mostly anon when it comes to it's ownership? Do you think a Bolivan? exchange would care what NY says/does? |
|
|
|
|
Never thought I'd see the day where BTC-e starts policing the coins on their exchange. Bitstamp of finex probably, but not BTC-e. Are they going to start verifying ID's too?
|
|
|
|
well............ have you considered ripemd160? I mean it is easier (lol easier) to find collision in 160 than 256.
Yes, all this speculation takes RIPEMD-160 into account. It is because of the RIPEMD-160 that a collision is going to look like having two different private/public keypairs which correspond to the same address. Here's some super simple code I wrote for a mini bitcoin address collider. I call it mini because it only does 324 address per hour, however the RNG process being used is unclear. If the RNG is flawed there is a better chance of collision. Blockchain.info provides this ( https://blockchain.info/q/newkey) which is supposed to create a fresh public/private key pair whenever you call that address. Since the RNG process behind these addresses are unclear is the reason I'm using it. There's a limit of ~1 query per 10 seconds or you'll get banned/blocked which is why this script only does about 320 per hour. It pulls the new key (assuming RNG is good) and then we use the address info and return the total amount received to that address and plugs everything into a DB. If total amount received is ever greater than 0 then you have a collision. Or you can also query your DB to see if there are any repeats. Put it in a cron job to run every 5 minutes. Cool. Note that a collider doesn't need high-quality randomness for each address. Just working through all the private keys in order from 1 to 115792089237316195423570985008687907852837564279074904382605163141518161494336 would be fine (yes, there are quite a lot of different private keys). Anyway. At 320 addresses per hour and assuming all else constant, you should be finding an address collision once every 121 billion trillion trillion years on average (similar to the way a new block is generated once every 10 minutes on average so expect some variance). Notice that you'd actually be generating a collision on average once every 7.8 billion trillion trillion years but because your code checks collisions by checking for a balance and most addresses in the blockchain have a balance of 0 you'll be missing a lot. I feel it's worth comparing this to Bitcoin block generation. A script which generates 320 hashes per second will find a block on average once every 72 trillion years. Given that many CPUs are capable of hashing 10 000 times faster and that an address with non-zero balance contains about 3.2 BTC (compared with the average block payout of about 25 BTC) we see that anyone looking to run this code for profit would be about 100 trillion trillion times better off just CPU mining Bitcoin. I was simply responding to the OP's question "how would somebody trying to cause a collision notice that they've succeeded?" What I provided is perfectly valid to his question, it attempts to create a collision based on poor RNG and let's you know if you found one. What you posted everyone already knows. from 1 to 115792089237316195423570985008687907852837564279074904382605163141518161494336 would be fine (yes, there are quite a lot of different private keys) Yea I quite aware of the # of addresses... your code checks collisions by checking for a balance and most addresses in the blockchain have a balance of 0 you'll be missing a lot.
No it doesn't, it checks total amount the address has ever received, in other words checks to see if the address has ever been used. At 320 addresses per hour and assuming all else constant, you should be finding an address collision once every 121 billion trillion trillion years on average
The script is checking the RNG of blockchain's ( https://blockchain.info/q/newkey) tool. It has no extra points of entropy like bitaddress.org and could very well be flawed. Do you know the RNG behind this newkey tool? |
|
|
|
The 1st transaction in every block is the reward payment to the miner and their address. Get the latest block height: https://blockchain.info/latestblockPlug it into $block_index: https://blockchain.info/block-index/$block_index?format=json For example this one was found by ghash and it provides their address: "hash":"03ca37ec3c01ee6cbcab1f374acc33771f286f2834b12366b7b051de73cae6c4",
"vout_sz":1,
"relayed_by":"178.63.63.214",
"out":[
{
"addr_tag_link":"https:\/\/www.ghash.io\/",
"addr_tag":"ghash.io",
"spent":true,
"tx_index":50557126,
"type":0,
"addr":"1CjPR7Z5ZSyWk6WtXvSFgkptmpoi4UM9BC",
"value":2506369541,
"n":0,
"script":"76a91480ad90d403581fa3bf46086a91b2d9d4125db6c188ac"
}
]
}
Technically you could write a loop that starts at the current block height, and then grabs the "addr" from the json ["tx"][0]["out"][0]["addr"];
and log it to a database, at the end of each loop you can subtract 1 from the block height until you run out of blocks. Then you'll have a database of all addresses that have solved a block. |
|
|
|
Here's some super simple code I wrote for a mini bitcoin address collider. I call it mini because it only does 324 address per hour, however the RNG process being used is unclear. If the RNG is flawed there is a better chance of collision. Blockchain.info provides this ( https://blockchain.info/q/newkey) which is supposed to create a fresh public/private key pair whenever you call that address. Since the RNG process behind these addresses are unclear is the reason I'm using it. There's a limit of ~1 query per 10 seconds or you'll get banned/blocked which is why this script only does about 320 per hour. It pulls the new key (assuming RNG is good) and then we use the address info and return the total amount received to that address and plugs everything into a DB. If total amount received is ever greater than 0 then you have a collision. Or you can also query your DB to see if there are any repeats. Put it in a cron job to run every 5 minutes. <?php
$counter = 0;
while($counter < 27){
//gen new key pair
$url = "https://blockchain.info/q/newkey";
$content = file_get_contents($url);
$arrEx = explode(" ", $content);
$bitcoin_address = $arrEx[0];
$privKey = $arrEx[1];
//check the balance
$jsondata = json_decode(file_get_contents("https://blockchain.info/address/$bitcoin_address?format=json"), true);
$totRec = $jsondata["total_received"];
//insert the pub key, priv key, and balance into DB
$conn = mysqli_connect("localhost", "username", "password", "database_name");
if (mysqli_connect_errno()){
echo "Connection to DB failed" . mysqli_connect_error();
}
mysqli_query($conn, "INSERT INTO collision (pubK, privK, balance) VALUES ('$bitcoin_address', '$privKey', '$totRec')");
$counter++;
sleep(10);
}
mysqli_close($conn);
?>
|
|
|
|
|
Good morning fellow coin traders... looks quiet.
Will the weekend stay flat?
Will the EW-ers be right and we'll fall hard?
Will the winkies launch Gemini next week?
Only time will tell...
|
|
|
|
This is what happens when you try to hold down a bull.  |
|
|
|
Tarmi, have you closed your short yet?
I felt pretty good about closing my $290 short at $260 (~10%) this morning. How much bigger of a profit are you looking for in one trade?
no. What's your target? $240? $220? not telling you, sorry. Haha, you're not sorry  |
|
|
|
Tarmi, have you closed your short yet?
I felt pretty good about closing my $290 short at $260 (~10%) this morning. How much bigger of a profit are you looking for in one trade?
no. What's your target? $240? $220? |
|
|
|
The true moment of going all-in is RIGHT NOW.  Why might the latest pennant be such a different beast to the previous ones? Was wondering the same. A larger, similar shaped pennant could be seen if we were still to have another capitulation event. Which would mean the all in moment would be quite a while from now. That pennant theory is long gone. That graph is from march 2014... I believe he was posting that to show others have tried to use historical patterns to predict the price and have failed miserably. |
|
|
|
|
Tarmi, have you closed your short yet?
I felt pretty good about closing my $290 short at $260 (~10%) this morning. How much bigger of a profit are you looking for in one trade?
|
|
|
|
LOVING THE OGRANIC GROWTH
Pretty sure that little pump had some steroids  |
|
|
|
|
Ya'll get your buys in, in time? Boom boom!
|
|
|
|
|
Show Posts
