|
What you see is the transaction being echoed back to you via other peers (not the ones you sent to). It is meant as
1. an indicator that the transaction was broadcasted and there were no technical issues and
2. a sufficient (as of mid-2014) indicator the transaction will confirm. It can be gamed, but so far it didn't happen. If it matters, wait for real blockchain confirmations (green parts of the circle) to arrive.
|
|
|
|
As long as you don't install untrusted stuff on your phone you'll be ok. I don't think anyone has had their android wallet hacked yet..?
I haven't heard of any hack so far. |
|
|
|
|
HD wallets will arrive first. The spending password should arrive shortly after.
|
|
|
|
|
The minimum amount to send is about 0.05 mBTC. This is the so-called anti-dust rule. It will probably be adjusted in future, but a significant amount of nodes need to agree.
|
|
|
|
Thanks! The PIN option is planned. It will arrive after HD wallets.
I hope that this actually encrypts the wallet, and preferably allows for passwords as well. It's a must have feature IMHO. It will encrypt the private keys, so that you cannot spend or sign without the password. Essentially, it will be switched to receive only. And yes, it will be a pass word. |
|
|
|
|
What do you mean by "send unconfirmed transaction"? When you sign a transaction, it's always unconfirmed before it gets confirmed by a miner. This is not any different with Bitcoin Wallet.
The app can scan and relay raw transactions from QR code, if the transaction is relevant to your wallet.
|
|
|
|
I have more than one address in the wallet, and sometimes I'd like to sort the btc received based on which address received it. I haven't yet found a way to see which address received a payment without clicking "browse" and opening up a particular transation in a block exploring website. Is there a way to sort "received" based on address? Or just to show, for each received, which address received it?
I did not implement anything like this. Generally it is not recommended to manage addresses manually. Hmm, I thought that was one of the main reasons you might provide "names" for addresses. If I give you an address to pay me on and I name it "payments_from_AS" then if I want to see how much you've paid me or if you've paid me recently, I want some way to see only the payments to this address, right? What other reason do we have for "naming" addresses in receiving addresses? That's right, it used to be like this. It works because most clients still reuse addresses (including Bitcoin Wallet). In future, addresses will not be reused, so there is no point in labeling them. Information about who and for what you paid will be attached to the transactions themselves, or in the far future payment objects that bundle 1..n transactions. I'm sure when we're at that point there will be ways to search, e.g. for payments to a specific merchant. |
|
|
|
I have more than one address in the wallet, and sometimes I'd like to sort the btc received based on which address received it. I haven't yet found a way to see which address received a payment without clicking "browse" and opening up a particular transation in a block exploring website. Is there a way to sort "received" based on address? Or just to show, for each received, which address received it?
I did not implement anything like this. Generally it is not recommended to manage addresses manually. |
|
|
|
|
Thanks! The PIN option is planned. It will arrive after HD wallets.
|
|
|
|
|
Yes, we will add password-encrypted wallets.
|
|
|
|
|
Interesting, so USB Mass Storage device gives you access to the raw sectors. I didn't think of that earlier. On the other hand, Android 4+ has more or less replaced USB Mass Storage by MTP (Media Transfer Protocol) which is object oriented, right?
|
|
|
|
Sorry, it's not possible to view private keys. You could build your own version though. Bitcoin Wallet is free software and open source. |
|
|
|
|
I recently read that if do a factory reset on Android, certain devices only do a quick format. That would mean all files are still there and could be recovered using an undelete tool. However, I have no further experience with this.
|
|
|
|
|
That sounds like an extremely advanced usecase.
We will add password-encrypted wallets. If your password is strong enough, it will prevent loss of coins when your phone is stolen.
|
|
|
|
|
We are monitoring transaction fees closely. At the moment it looks like even though lots of nodes relay transactions with a 0.01 mBTC fee per kB, miners don't care. They still require 0.1 mBTC per kB. As a result, transactions will get stuck.
If you want to experiment with fees, feel free to build your own binary from the source.
|
|
|
|
|
Yeah, that explains the slowness. We're working on improving performance for wallets like yours, but currently our first priority is getting HD wallets out of the door.
|
|
|
|
|
You can check how many inputs there are in your wallet if you send a report (Options > Settings > Report issue) to yourself. It should read something like
Transactions: 15
Inputs: 19
Outputs: 29 (spent: 14)
On a sane wallet, number of outputs is roughly double the number of transactions, and inputs somewhere between number of transactions and double the number of transactions.
|
|
|
|
|
Show Posts
