Topic: Blockchain.info - Bitcoin Block explorer & Currency Statistics - page 85. (Read 482537 times)

Nope - just went through!

Is the error still occurring now?

I'm having this problem as well.

Seconded.  Both Coinlab and Lindsay from the Bitcoin Foundation (same office space) have encountered this problem today.

My transactions via the mobile and webbrowser client appear not to be going through. The mobile client just says "sending" and the browser says "pushing transaction" and nothing happens. Is something wrong with the site?

Replied via PM. You can now request a new code be sent on the login page if the first one isn't received.

-----

Bitinstant cash deposits re-enabled.

Tags can no longer be submitted that link to blockchain.info, they must have context outside of blockchain.info itself.

Internal refactoring, transaction and address pages should be quicker to render.

I've been having a problem today where I attempt to log into my wallet, but the SMS authentication code is never sent to my phone ... so I am unable to login!

- sign and verify message added to JSON RPC api (credit to Mike Hearn)
- Improvements to the javascript verify message functionality.
- Bug fixes to JSON RPC when using ruby and python libraries.
- Improvements to polish translations.


Thank you for the bug report, Davout reported this issue previously. It will take a while to get a fix out so in the meantime users of the iphone app should be careful sending values less than 0.01 BTC.


Thank you for the feedback. Fees are calculated based on the priority of the transaction which should mirror how Bitcoin-Qt calculates it https://en.bitcoin.it/wiki/Transaction_fees. Is there a specific transaction that you think should have included a fee but didn't? If the fee policy is set to generous a 0.001 BTC fee is guaranteed to be included.


This is expected behaviour since once an address is deleted the client no longer has a record of it so thinks the address belongs to an external wallet. I could see how it could be confusing though. Perhaps the sub-header would be better changed to "Transactions involving your active addresses".

I reported this one a while ago. The mobile app rounds sent amounts to six decimal places. I think it should be considered a serious issue because it can mess up a lot of use cases where sending an exact amount is important.

(The Google docs thing is irrelevant, the reason it displays weird amounts is because it's internally handling floating point data types which are suited to represent approximations but not exact values.)

And thank you for implementing them! You are one hell of a builder, blockchain.info is becoming quite the masterpiece.

BTW I noticed one more thing.. "My transactions" doesn't correctly display my history. I'm not sure about this but it seems like it shows only those tx that are associated with addresses that I didn't archive. Not only that but also for instance I see a tx that says I received x btc when the truth is I sent y btc from another address that I have now deleted entirely and x was merely the change that went back to my wallet to a brand new address..

If you can't fix this because obviously you don't know which addresses are in my wallet, maybe you could clarify this somewhere on the my transactions page where instead of "Transactions Summary of your recent transactions" it could say something like "Transactions Recent activity on your active addresses" or just scratch "My transactions" and change it to "Recent activity" and scratch "Transactions" and change it "Address activity"

I encountered a particularly nasty bug or effect and tracking it down and correcting it is going to be extremely annoying.

I needed to send an exact amount of bitcoins and bitcents to a particular address. I input the address into Blockchain.info's search and brought up the destination wallet. Then I clicked Request Payment and input via copy/paste the exact amount of bitcoins and bitcents to send. The QR code changed and I scanned it with the iPhone Blockchain app.

I verified it was sending to the destination address the exact amount of bitcoins and bitcents (YYY.YYY70658). Then I clicked send payment. It actually sent (YYY.YYY707) to the destination address. It rounded up .00000042. My initial thought was the Blockchain app rounded it but perhaps there is something a little deeper at play. For example, when I have the two different wallet send amounts in Google Docs and subtract the actual sent from the proposed sent then Google Docs thinks the difference in the amounts is 0.0000004199999 repeating and not .00000042.

I thought it may have been an error with the display of the wallet amounts but verified it on blockexplorer.com also. It did send the wrong amount contrary to what was displayed on the screen before send payment was clicked.

I intended to send it from one of the two active addresses in the wallet but inadvertently left the default app selected to Any Address. Nevertheless, even if that were a contributing factor by pulling inputs  from multiple addresses the problem is in rounding up the amount sent. That output amount to the destination address should not be changed. Additionally, there was no verification of inputs and outputs like the browser based.

Suggestions:
1. Perhaps the app and web browser should display all 8 bitcents for all amounts. This rounding is problematic for usability.

2. Perhaps there should be an input/output verification with the iPhone app?

Great service piuk, I use it daily but have a small issue, my fees are set to normal but sometimes the coins get sent without any fees. It happens randomly so I can't reproduce the issue so you can check.

I have doubled the width of the value field on the custom send form and added an extra 20px to the quick send form. (Changes will show the when the next update is deployed).


This makes sense. However It might be easier to add a checkbox to the custom send form to make the transaction anonymous rather than duplicating the form.


Can do.


I think this should be left to the user to decide rather than forcing a particular way. My second password would take a while to type using the onscreen keyboard I might be tempted just to disable it instead if it was an inconvenience.

Thanks for the suggestions.

Finally got round to implementing the changes to logging.

- All wallet ip addresses are now hashed.
- Still recording the hashed ip the wallet was created with and the hashed ip it was last updated with. This cannot be disabled.
- Access logs remain disabled.
- You can now choose to enable or disable more detailed logging in [Account Settings]. This is much better from a security standpoint and includes actions taken by admins. For example if you submit a two factor authentication request and it is approved you will see "admin (piuk) approved two factor reset request" in the logs. I am still the only admin at present. Logging is disabled by default.

Enabled:



Disabled:

Much appreciated, thanks!

Will do tomorrow.


Maintenance taking a bit longer than expected: https://bitcointalksearch.org/topic/blockchaininfo-you-are-the-best-d-134461

The blockchain.info site has been intermittently slow or down for me, is anyone else experiencing this?

Piuk, any chance you get the time to address my post above? Thanks in advance!

All PingIt and Bank Deposits should be clear now.

I am going to close all zendesk tickets regarding PingIt and Bank deposits, if any users are still having problems with orders please create a new ticket. The following surnames have orders with incorrect reference numbers that I have not been able to resolve: LOOR, SMITH, KING, BAKER - please contact me.

Deposits will remain disabled until the end of the Japanese bank Holiday on the 4th. 12:00 AM Tonight (3rd Jan) the site will be going down for approximately 30 mins - 1 hour maintenance.

The issue appears to have been resolved now.

[Edit: The Twitter account had addressed the issue in their status update:

  ]