Apologies for the issues with the API. I'm expecting a resolution within the next 2 hours. Cloudflare has been enabled as a temporary measure to reduce load on the database while a crash on one of our database nodes is investigated. Typically this indicates that a startup just hired a new marketing person. Typically the first thing they do is to irritate everyone at the shop by coming up with a new logo as a means of demonstrating that they do things.
 |
|
|
|
I heard they removed it due to money laundery. What I don't get is why Shared Coin is still available then since it basically is the same.
Shared Send wasn't removed for any specific legal concern, Shared Coin is replacing Shared Send as it is better technology which is more in keeping with the client side wallet approach. Blockchain is a software company not a financial institution and hence want to offer client side products only (No handling of private keys). Can someone explain the difference of both and the system of how Shared Coin works? I never used it.
This is a good explanation https://bitcointalk.org/index.php?topic=325594.msg3697300#msg3697300. |
|
|
|
piuk, so what is you general guess about the situation? should we be calling lawyers? or it is a glitch
In my experience when sending a lot of bitcoin payments it is quite easy to get out of sync with the blockchain and get into a mess which is difficult to untangle - so it is certainly possible that it is a glitch. But I don't really know enough about the situation so don't quote me on that! |
|
|
|
They've change the structure of bitcoin_tx and remove some data for security purposes.. thereby hiding the stats.. < BitCoroner> MagicalTux: why can't we see the raw transactions anymore on https://data.mtgox.com/api/0/bitcoin_tx.php ? <@MagicalTux> BitCoroner, because phantomcircuit found a security issue with showing this Which is complete and utter nonsense. Every raw tx ever made and which will ever be made is available in the blockchain. There is absolutely no security issue by making the raw tx known. Possibly there is. This is a guess, but by making the raw transaction known it could allow someone to alter the DER encoding of the signature scripts producing a clone of the transaction with different hash. If the modified transaction is then broadcast and confirms before the original Mt.gox may check the original transaction hash and see the outpoints have been double spent then resend the payment using new inputs resulting in the withdrawal been paid twice. It really depends on how Mt.gox detects a failed transaction. |
|
|
|
|
When you made the transaction were any errors displayed? Please link the shared coin transaction and the bitcoin address the coins were supposed to be sent to.
Edit: Found your ticket on Zendesk the destination address did receive the correct amount of bitcoins and they are fully confirmed. The problem is at bitpays end.
|
|
|
|
|
The firefox issue should be fixed now.
|
|
|
|
IP Bans expire in 4 hours.
Thank you piuk. I tried it now and it is expired. So I can access the site again. (But the duration of ban was more than 4 hours. Something like 12 hours or more.) May I ask what is the reasonable number of requests? I do not want to give reason to ban in the future  . The time is extended if the ip has already been banned previously. The request limits are shown on the bottom of the api page https://blockchain.info/api |
|
|
|
Is this feature still working? I haven't been able to click the "review payment" button for quite some time now when I try to submit a shared coin transaction.
Yes sharedcoin is still functional. What browser are you using? Are there any errors in the javascript console. |
|
|
|
|
IP Bans expire in 4 hours.
|
|
|
|
|
For some reason the camera is not showing in firefox, I'll look into it. Chrome should work fine.
|
|
|
|
BTW, I just visited Blockchain.info, and the bottom half of the "stats" page with the worthless "miners' operating revenue/margin/BS" was missing .... although one can always hope for a Merry Christmas present from blockchain.info.
Its finally gone. Merry Christmas! But, no, that wasn't the announcement |
|
|
|
You can use the blockchain wallet api: |
|
|
|
Are you going to add qr scanning to the online wallet like coinpunk? It would be nice for the iOS people who can't get a good app or they are banned to have all the functionality through the web browser.
Scanning QR codes should now be possible through the web interface on iOS. I'm not sure if coinpunk is any better but from some brief testing the lighting and whitespace around the qr code need to be perfect for the code to scan correctly, not very practical for real world use. |
|
|
|
Sharedcoin transactions on blockchain.info lowered to 0.0001 BTC per repetition. On average 1.8 unique participants are joining in together each transaction, so over several repetitions there is a very good chance your transaction will be directly mixed with other users not just the sharedcoin server. When did that happen? That's a major change that deserves a large announcement. Are they using BIP32 to derive the new addresses?
It's just for Sharedcoin transactions and not BIP32 yet but I hope that will be available soon. |
|
|
|
|
Unfortunately this isn't possible with our current setup. The newly generated address needs to be encrypted with the second password before it can be inserted into the wallet. It would be possible to leave the key unencrypted and encrypt it on next login but that feature is not available at the moment.
|
|
|
|
That's what Blockchain.info does. You send from a single address, you give it an amount and a destination address, and it goes through 2+ CoinJoin steps, split up into random amounts from your source address, then after all the steps gets recombined into the amount you sent (minus transaction fee) into your destination address. Basically, it's as if your amount is exploded into random chunks, and then recombined into the same amount. Unless multiple steps involve multiple different coinjoiners, and much of what you get isn't tied to your own bitcoin at all, I'm not sure it's secure.
Assuming you use a single input of the exact size then it will be recombined into the same output value. But the client will deliberately select more inputs than necessary in order to make determining the input value more difficult. The server will also add multiple outputs of the same size as your inputs. Even if you are restricting outputs to power of two sizes, as in the original coinjoin proposal, the same issue is still a problem. Address A sends 2 * 0.1 BTC + 1 * 1 BTC outputs then Address BTC receives 2 * 0.1 BTC + 1 * 1 BTC soon after it is easy to connect the dots. Mixing in the background rather than on demand is probably the best way to solve this. |
|
|
|
|
Type the first letter into the to field and it should give you a dropdown.
|
|
|
|
|
Ok all tag links must now be verified by a moderator before being displayed on the site. The moderation rules will now be a bit stricter, any links should provide context for the purpose of that address which would be useful to other users e.g. "Wikipedia Donation Address" linking to wikipedia.org = good, "This Address Scammed Me!" linking to reddit = bad.
You can now also submit tags verified with a signed message, rather than a link, which will be approved immediately. Blockchain wallet users can do this through the wallet ui label address function.
I will add a way to remove tags soon.
|
|
|
|
|
Show Posts
