|
Desktop sync Now Active. It can be found in [Import / Export].
It allows you to easily import keys from Bitcoin-QT if you would like to switch to My Wallet or export keys if you want to switch to the Desktop client.
However it is not recommended for everyday use if you want to keep your wallets separate as by entering your RPC username, password and wallet password you are giving the javascript full access to your Bitcoin-Qt wallet. The username and password for the Bitcoin-Qt wallet is not saved.
|
|
|
|
|
Is is possible you could add a JSON feed of the Bet Addresses, Winning Odds, Min & Max Bets etc?
|
|
|
|
Google Chrome is telling me that the wallet verifier app needs new permissions. What's the story?
It's for a new feature which allows you to import and export keys to Bitcoin-Qt without needing to use pywallet or command line. The problem is talking with the Bitcoind RPC server is a violation of the browser's Same origin policy and most browsers won't let you do it without special CORS HTTP headers. I made a pull request to add CORS headers to the RPC interface but the Bitcoin devs have dismissed the idea previously. As a workaround the Verifier browser extension can be used to circumvent the restrictions - as extensions have the ability to bypass the same origin policy if requested. 1) If you are not running Bitcoind-Qt there is no risk. 2) If you have not enabled the RPC server (by default it is off) there is no risk. 3) If you have the RPC server enabled the web interface will be able to talk with Bitcoin-QT so be sure the username and password is set. 4) The extension only runs on blockchain.info or www.blockchain.info.  |
|
|
|
v1.9.8 now on Cydia- Scan private keys from paper wallet (or mini private key QR Code) - Faster transaction signing with javascript webworkers (iOS 5 only). - More reliable web socket support (iOS 4.2+). - Logout button - Other bug fixes v1.9.7 is not working for me (3GS iOS v4.21). When i try to send transaction... it breaks... just like it was the case before v1.9.5.
The bug fix accidentally got reversed in v1.9.7, it should be fixed again in 1.9.8.
|
|
|
|
My app shows the balance, the transactions, but the little icon on upper-left is red.
Yes I also get the red X. It means the WebDocket isn't connected (so you will need to press the refresh icon in the top right), i'm not sure why this is I need to have a closer look. The encrypted backup don't ask for my yubikey, only relying on the passphrase? I just want to be sure of that.
Correct, two-factor authentication does not effect how the wallet is encrypted. --- New Smarter Transaction Push Algorithm ----Although Eligius should process low fee transactions for My Wallet users there has been some issues getting low fee transaction to propagate properly through the network. Now transactions will be directly relayed to every known mining node. If network propagation is still poor they will be relayed again every 10 minutes. If your transaction doesn't confirm within 24 hours you will now receive a notification: A transaction made through My Wallet has been removed from our database because it was taking a long time to be included in a block. The transaction can be temporarily viewed at {link} however it will be removed shortly. In addition the WebSocket server now runs on all 3 servers providing better fault tolerance and a flash fallback has been added for older browsers without native WebSocket support. Anyone who has been having problems with slow transactions or any errors pushing transactions things should be much improved now. void NodeManager::pushTransaction(CTransaction& tx, int maxNodes) {
if (fDebug)
printf("pushTransaction() %s\n", tx.GetHash().ToString().c_str());
std::set<unsigned int> already_pushed;
ReadLock read(nodeManagerMutex);
//100ms lock timeout
boost::system_time const timeout = boost::get_system_time()+ boost::posix_time::milliseconds(100);
int nPushed = 0;
int retryTimes = 5;
bool done = false;
uint256 hash = tx.GetHash();
for (int retry = 0; retry < retryTimes; ++ retry) {
bool allZero = true;
//Node mangers handle groups of nodes 100 at a time
for (int ii = 0; ii < nodeManagers.size(); ++ii) {
NodeManager * manager = nodeManagers[ii];
if (manager->connectedNodes.size() == 0) {
if (fDebug) printf("Size %lu\n", manager->connectedNodes.size());
continue;
}
//If the recent inventory contains the transaction hash then we can finish because the network
// has already relayed us back the transaction
if (CNode::recentInventoryContains(hash)) {
if (fDebug) printf("Breaking because recent inventory contains transaction hash\n");
return;
}
allZero = false;
if (fShutdown)
return;
if (manager->connectedNodesMutex.timed_lock_shared(timeout)) {
if (fShutdown)
return;
//Push to mining pools first
BOOST_FOREACH(CNode* pnode, manager->connectedNodes) {
if (already_pushed.count(pnode->addr.ip) > 0) {
continue;
}
if (ConnectionManager::isMiningPool(pnode->addr.ip)) {
already_pushed.insert(pnode->addr.ip);
if (pnode->hSocket == INVALID_SOCKET || pnode->fDisconnect)
continue;
pnode->PushMessage("tx", tx);
++nPushed;
}
if (nPushed > maxNodes) {
if (fDebug) printf("Relayed to sufficient number of nodes (known) %d\n", nPushed);
done = true;
break;
}
}
manager->connectedNodesMutex.unlock_shared();
}
}
if (allZero) {
return;
}
if (done) {
return;
}
}
if (nPushed < maxNodes) {
printf("Didn't relay to enough nodes %d < %d\n", nPushed, maxNodes);
return;
}
}
|
|
|
|
One question - I changed my wallet pass yesterday via the web interface, and yet my Android app seems to work.
A new password dialog should popup when the wallet next syncs e.g. when you open and close the app. Sometimes syncing can be a bit patchy when the web socket server is down. first time password didn't worked for some reason
"error while decrypting password"
Do you know if they were creating a new wallet or logging into an existing one? I just testing creating a few new wallets and couldn't replicate the issue. Doesn't that mean that not only the block displays are wrong, but that many of the charts are wrong too?
Thanks for the bug report, this was a display issue only and should be fixed now. The largest block by value is http://blockchain.info/block-index/127584 (4m BTC) |
|
|
|
Care to share any technical details? How does it work?
1) Generates a new private key 2) Sends fund to the newly generated address. 3) Sends a link to the private key in a Facebook PM. 4) Upon claiming the private key is then swept into the receivers wallet. It uses the Facebook javascript SDK ( http://developers.facebook.com/docs/reference/javascript/) so does not share any of your Facebook info with blockchain.info. The new private key is also never shared with blockchain.info. The sender retains a copy of the private key in their wallet so can reclaim the bitcoins at anytime by sweeping that address. Fill out the form pre filled with your Facebook contacts. Add a custom message. Follow the link in the PM: |
|
|
|
Actually, I tried to send to Facebook, to a labeled address, and to a raw Bitcoin address, and all three attempts failed.
Some of the failures actually wrote "success", but no money was sent. This repeats consistently for me.
The RMI bridge between bitcoind and the website frontend died for a bit so the UI would not have updated with any new transactions. The transaction may have been pushed out successfully though so check you haven't double sent. If you have double sent the coins can be reclaimed by sweeping the address labelled 'Sent via Facebook' in your archived addresses. Is the wallet feature offline again? I cannot send transactions unfortunately. The page says 'client disconnected' despite me being logged in.
Everything should be fully functional again now. Apologies for the issues. |
|
|
|
Send to Facebook doesn't seem to work right now.
Should be fixed now. For some reason Facebook won't send links with blockchain.info as the domain, it maybe something wrong with the app settings. But as a workaround I set the link to blockchain.co.uk which redirects to the correct domain. |
|
|
|
just like mtgox: whenever btc's arrive on an archived address i want to sweep them automatically to my main address.
The idea is that "Archived addresses" should be inactive and you shouldn't be receiving any BTC to them. I don't want people to rely on auto-forwarding also creating transactions without User interaction could be confusing. Thanks Feature request: when you send an email for received (or sent) transactions, can you include the new balance of the wallet?
I would also prefer non html email.
Unfortunately not. The balance of wallets are not available to blockchain.info as we are unable to view the addresses in a wallet. I added your suggestion to https://blockchain.uservoice.com/. deepbits blocks are regularly very wrong or other miners are announcing blocks through them.
Deepbit should tag their coinbases then  There is no way to tell if is accurate or not. I don't know if this issues were discussed before:
1) In the web wallet, I set Euro as currency but after a while always rolls back to U.S Dollar.
2) The android app is not available for my phone, probably because of the small screen resolution
Thank you for the bug reports. ** New Charts **Average transaction confirmation time. I was hoping to see some correlation with the recant transaction spike but it doesn't look like there is any. Number of My Wallet wallets: http://blockchain.info/charts/my-wallet-n-usersNumber of My Wallet transactions per day: http://blockchain.info/charts/my-wallet-n-txAlso nice spike on: http://blockchain.info/charts/n-transactions-excluding-popular |
|
|
|
Up to date test re-run: Building Test Ledger
Ledger generation took 128s
Number of unspent outputs 1053033
Original disk size 1716.7MB
Compressed Ledger size 71.9706MB
4.19238% of the original size
Since the last test the blockchain has more than doubled in size but the ledger has only increased by 20MB. In my opinion this is the only way that bitcoin will scale. Merkel tree pruning is a dead end because not even the centralised nodes holding the full blockchain will be able to scale. Keep variable number of blocks (Default ~2 weeks) unspent outputs in blocks older than that are compressed into a ledger. |
|
|
|
Could you maybe specify somewhere how exactly the send to email or facebook functions work and whether or not my addresses get associated with my facebook account in anyway?
The Facebook feature uses the Javscript SDK so does not need server interaction with blockchain.info. Neither your contacts or login are shared with the server. All it does is create a new private key send funds to that private key then send the user a link to it e.g. https://blockchain.info/wallet/login#newpriv%7C9hdfTHWy9TU12nuCN2Hc2XxT5KtXcRE4qFdUF6pkK4k3Yes this is horribly insecure at the moment, i will add password protection soon. Custom tx form "Return Change" drop-down only contains addresses with balances (as the "send from" one, rightly, does) (+new, +any). Can we have our zero balance addresses in there too?
Fixed. Thanks. I found another problem - under Import/Export - Paper wallet - the paper wallet popup page is blank - no codes and no text.
It should open in a new popup window, please check if your browser is blocking it. Sometimes I want to send more than 0.0005 tx fee, because the tx is very large.
You can use the custom send for to set the transaction fee, but there is currently no way to set the default fee. ...and it's back!
Thanks, it needed a prod New FeatureJavscript transaction signing using WebWorker background threads if supported. Transactions should be much quicker to send now. |
|
|
|
Had a few problems with the site earlier. Too many unconfirmed transactions (10,000+) caused some queries to jam the database. Everything should be running smoothly now. Also where do we change the default miners fee?
You can't at the moment. I think the interface is in need of a new preferences panel. |
|
|
|
Want to see what Piuk thinks and then lock it in 'officially'?
I have excluded M-Of-N (Escrow) transactions from firstbits calculations. P2SH addresses ( http://blockchain.info/address/3N6RjoL4Z93c2VFpqpwJNCUsy5MFikzBWr) get a firstbits with the prefix 3 so as not to collide with old style addresses. Anything you would like me to change? |
|
|
|
That way all of yours addresses belongs to left column and all the third parties addresses (and change addresses) belongs to the right column.
I'm not sure about this. I prefer inputs always on the left and outputs always on the right. I guess if you don't know about bitcoin inputs and outputs it makes more sense your way. I'll see if I can add an it as a preference setting. I just installed the javascript verifier extension for chrome and when I went to the my wallet page and clicked the "turn off" button at the top right for logging out before I entered my pw and opened my wallet it sets off the javascript verifier and gives me the following two boxes:
This can sometimes happen when you refresh the page mid load or when I'm deploying an update to the site. If you get the error once wait a few seconds then refresh the page - if the error shows again there maybe a more serious problem with the javascript. I'm having a few problems with the website (tried on both Opera and Chromium):
Both of these should be fixed now. Thanks for the bug report. The website has been looking a little ugly on my end recently, and I have no idea why.
Those new buttons are actually deliberate (I upgraded to bootstrap v2 http://twitter.github.com/bootstrap/components.html). Do people prefer the old ones? Well that page is definitely broke for me as of right now:
All in the name of progress is it fixed now? ** New Send Forms ** Note: The quick send form will not ask for confirmation for transactions below 20 BTC in value.   |
|
|
|
Thank you for the donations everyone. Sorry... I copy and pasted my decryption password, which is quite complex, to ensure that I was not mistyping it on the iOS keyboard. I also attemtped to enter it on a bluetooth keyboard.
Did you get it working in the end? Maybe try an alphanumeric password only if possible. Feedback needed on the interface: compact or original as default? |
|
|
|
Davout did not say he was using just one address, did he ?
He said http://blockchain.info/address/1FrtkNXastDoMAaorowys27AKQERxgmZjY was Instawallet cold storage address. Even he was using one address why would you assume carelessness one his part more than on the part of piuk or any other bitcoin service operators ?
In my view it's best to plan for the worst - The best laid plans of mice and men often go awry. Bitcoin doesn't exactly have a stelar history of services operators not making mistakes. Client side encryption puts much less risk on the operator. Individually encrypted wallets, operator has no access to funds, User's balances are stored in the blockchain rather than an SQL db and users can backup their own wallets etc. |
|
|
|
when the address is public (see 1frtknx for instawallet's)
I don't consider leaving $100k in one bitcoin address a wise security decision, I don't care how "offline" it is. Mistakes happen in the worst ways possible. When your cold storage address is public, you cannot lie about getting hacked in order to steal user funds for yourself.
You can only lie about a hack and steal the funds that are in the hot wallet.
There is no way to correlate the balance in that public address with full balance of instawallet users. There could be 50% missing and nobody would be any the wiser. |
|
|
|
Another donation awaits you when the 5.1.1 fix is released . Issue with the new jailbreak should now be fixed. Turned out I needed to code sign the app with a self signed certificate rather than no certificate at all. Any donations appreciated. please unlock!
Done |
|
|
|
Sensationalist title? I've never claimed that blockchain.info is zero-trust but it requires significantly less trust then hosted wallets. Here's my 10 11 point rebuttal: 1) Javascript verifier is almost equivalent to having a signed browser extension. You still have to trust the operator somewhat. 2) With a hosted wallet the operator can make off with everyone's funds at anytime and say they were hacked. This is not true of blockchain.info and would be significantly harder to pull off. 3) You can backup your own wallet, no need to trust the operators backup schedule. 4) The iPhone and android apps are not vulnerable to server side hacking at all. 5) Watch only wallets. 6) The wallet side of the site is open source ( Server Side iPhone, android) 7) All code running on the Site is signed and checksummed at the time of deployment. This checksummed is checked regularly, a log of changes can be seen at https://github.com/blockchain/Checksum/commits/master. 8 ) Two-factor authentication not available with Desktop clients. 9) Having your own private keys leaves you in control of your money. If blockchain.info went offline for any reason you can just import a wallet backup into multibit, if instawallet went offline Users would be left high and dry. 10) The Site is operated by a registered UK company, my name is Ben Reeves. This is me at Ycombinator's offices a few weeks ago, anyone feel free to contact me at +44 7525 431876 (9-5 GMT). 11) Hosted wallets can change your balance at anytime, you can verify your blockchain.info balance in the blockchain. |
|
|
|
|
Show Posts
