The lending section is a good place if you want to remain anonymous. Other popular options are BTCJam and BitLendingClub.
|
|
|
We've definitely messed up somewhere since the checksums don't match. The key does not validate properly.
|
|
|
I can sell you a sr. member account. It has 316 activity and 364 potential activity. I can sell it to you for 0.25 BTC
That is one overpriced account And what is your counter offer? I can negotiate, although that account's price is based on what I have seen here. .15btc thats the best I can offer.. That is too low for a sr. member account.
|
|
|
Did someone clam the 0.2 BTC prize for solving the puzzle or is it still live? And more important, did OP pay the winner or scammed-away with the money? Dont want to spend a lot of time solving it it has alreay been done. Nice game though.
It's all still there. The puzzle seems to come out to the private key for the address. It would be nice if OP could add some more to the prize as this has gone on for a few days already.
|
|
|
then we get 5hee2 which looks like the beginning of a private key. The second character in an uncompressed private key has to be one of H,J,K. If we use 'XoXo' from the hint to indicate case, we get 5HeE2. If you decode 5hee2 with the same shift cipher as the hint, it comes out as 5juu2, and 5Juu2 would also be a valid start for a private key. Also, part of the hint was "UU EqUAl SmAll lETTErS", which further points in this direction. Bingo. I think that's it. the hint is actually all upper case "UU EQUAL SMALL LETTERS" That makes sense. So that string is probably the start. Maybe the "replace 1 and 2" hint also meant to swap 1 and 2? So it starts with 5Juu22CkB3
|
|
|
I can sell you a sr. member account. It has 316 activity and 364 potential activity. I can sell it to you for 0.25 BTC
That is one overpriced account And what is your counter offer? I can negotiate, although that account's price is based on what I have seen here.
|
|
|
I can do it for you if your price is 0.75. Or for 0.5 BTC with you letting me keep whatever coin that I mine initially to support the network.
|
|
|
I should be able to do it for you in Java. It would be nice to see the not working source code as well for a basis of where to start.
|
|
|
I can sell you a sr. member account. It has 316 activity and 364 potential activity. I can sell it to you for 0.25 BTC
|
|
|
the whole point of my proposal is that it avoids a middle man..
to say again:
- the seller encrypts the file symmetrically with his public key - the buyer sends bitcoin to the associated bitcoin address - the seller must publish the public key of the address to spend the payment
no middle are necessary
however, another issue with it is that the buyer has no guarantee that the file was actually encrypted with the address'es pubkey
Wait a minute... so if the file is encrypted with seller's public key, how can buyer decrypt it? Am I missing something? It uses symmetric encryption which is "normal" encryption. It only needs one key, which can be the public key in this case.
|
|
|
I am very glad that you enjoy the cipher/puzzle so far Can you give us a hint for number 6?
|
|
|
So I am a little stuck with a small issue of ip bans. Bitcointalk will ban my server's ip if it makes too many requests at once.
I think you should use user side to query the forum, so the service can be made available to more than one user at the same time. If you query the forum server side, you will need to change server IP if your IP gets banned for some reason. The problem is a policy called same-origin policy in which browser's prevent the page from querying a domain different from the sites own domain. Thus, I can't have it query bitcointalk browser side unless my domain is bitcointalk.
|
|
|
I'm actually going to put some ads on it so that it will be free for everyone to use while I can still make some Bitcoin off of it. It is just like paying a few Satoshis to have the ads up while not having to go through the hassle of sending them.
That's a good idea - be sure to add a donation address to your site as well! Have you figured out how you'll deal with the one request per second rule yet, and any ETA on when the site would be made public? I'm going to use a queuing system and limit requests to once every 5 minutes. The site should be public by August 10th.
|
|
|
I figured out the beginning I think. The whole cipher seems to be a private key, although I am missing a few characters. Disregard 1 because REPLACE 1 WITH 2. did you enjoy the fake cipher ? Then number 2 becomes the front. The hint of number 2 is 2hee5 If we Change position of 5 an 2 then we get 5hee2 which looks like the beginning of a private key.
|
|
|
I would offer this as a paid service on a website. Instead of taking donations, just ask a few Satoshi's for it's use. Once people get familiar with the service, and experts have checked the code for security issues, this might become a profitable venture for you. I will not go through all the trouble to pull the code and execute it through a website... but I will visit a website and use the service, when I need it. I love my account too much to sell it anyways, but I guess there are a need for it out there. More people will do this, if they know how valuable accounts can become. I'm actually going to put some ads on it so that it will be free for everyone to use while I can still make some Bitcoin off of it. It is just like paying a few Satoshis to have the ads up while not having to go through the hassle of sending them.
|
|
|
If the faraday cage's gaps are big enough to let light through, then I would think that a small USB cable could fit through the gaps to charge the phone.
|
|
|
On August 15th 2010, somebody found a buffer overflow exploit in the wxBitcoin client (which is now called Bitcoin Core) and used it to create 184,467,440,737 BTC (184 billion) out of thin air ( https://bitcointalk.org/index.php?topic=822.0 ). Just 5 hours later a new version of the Bitcoin client was published with a fix but in addition the blockchain was hard forked and the offending tx removed from it. If a serious issue like this was ever found in the Bitcoin Core client again, would the offending txs be removed again? if so, then why doesn't this happen when bugs are found in other clients? Does Bitcoin Core have some kind of privilege in this sense? or was this just a once off thing, or did the small bitcoin community at the time manage to get everyone to agree to have this tx removed? I don't think Bitcoin Core has this kind of privilege really. The offending txs were removed not because they were made in Bitcoin Core but because it was a massive consensus breaking bug that caused the problem. It will probably happen with other clients too if something comes from those clients that breaks consensus or completely messes with the blockchain like making 184 Billion BTC out of thin air. but i doubt that such a major bug will happen again.
I wouldn't count on it. Heartbleed went for 2.5 years before being discovered. The shellshock vulnerabilities have been around ever since bash was first created in 1989. Even if we don't know about a vulnerability doesn't mean that they don't exist.
|
|
|
I think each answer is 5 characters that combine in a private key.
You still would need it to start with a 5 right? and private keys are 51 characters? We are then missing a character (or we switch the 5 and 2 or what was the hint on that?) They could also start with a K or L if they are uncompressed. Also, some of them might not be 5 characters. I think number 1 is more than 5. Has anyone figured out number 6 yet?
|
|
|
If you need someone to do Java coding or Android app developing, I can help.
|
|
|
Help me with the hex to image conversion! Here's my hex code: http://pastebin.com/htR5DVnUI put it in a hex editor and save it as a.jpg but my image viewer says the file cannot be loaded/opened! It works for me. Try a different hex editor Here is the image
|
|
|
|