I'll lock this thread to let the discussion continue in the dev thread here: https://bitcointalksearch.org/topic/bitcoinspinner-53353
We are busy discussing the Mycelium Bitcoin Wallet over there... the successor of BitcoinSpinner, come join us.
Topic: [ANN] BitcoinSpinner (Read 45071 times)
...
Good ideas, I'l add them to our list- before receiving money to an address, display warning if the private key is not known
- when deleting a private key that has money on it, mention that in the delete confimation dialog
...
can mycelium combine money from different keys when sending? It currently seems to me that the 2 addresses I have are handled as completely separate wallets? If that's correct, you could call them "wallets" instead of "addresses".
can mycelium combine money from different keys when sending? It currently seems to me that the 2 addresses I have are handled as completely separate wallets? If that's correct, you could call them "wallets" instead of "addresses".
The way the Mycelium wallet works right now is that you work with one key at a time. This means that balance, transaction history, sending/receiving all works on the currently selected key or address. This gives you fine-grained control over your keys, and that has its merits. We have been thinking about changing that to a model where keys/addresses are treated as a pool. This has the following consequences:
- Balance: The combined balance of all your keys and addresses (address = 'read-only wallet')
- Transaction History: The combined history of your keys and addresses
- Sending: Spend from the sum of funds available to your keys, addresses ignored
- Receiving: Your default receiving address will be used. You will select which in the Keys & Addresses view.
While the above is all nice, it also means that you will have less control when accessing your cold-storage (import key / spend / delete key), as the key will be part of the list of other keys and you may do a spend from several addresses. To alleviate that a special single key mode has to be made while not cluttering up the UI.
If more people ask for it we may make the change.
is there a way to copy the address I just sent money to?
in other words: I would greatly appreciate the transaction history item have a context menu that at least contains: "copy receiving address".
You will get it all in the next generation wallet.in other words: I would greatly appreciate the transaction history item have a context menu that at least contains: "copy receiving address".
Andreas and I are making the final touches on the Mycelium wallet. Right now we are at the "getting new server certificates, Google Play publishing certificates, and publishing sources" stage. Just a few days until open beta.
Molecular, I happen to remember that you used an Android 2.1 device. The new wallet will be Android 2.2 and forward only (more than 90% of the market), so I really hope you have upgraded in the meantime.
Yes, I now have phone that pretty much dwarfs the desktop I had just 1 year ago.
Apart from the fact that I hate to use it as a telephone (yes, you can use it as a telephone) because of very bad microphone / earspeaker design and that I almost need a backpack to transport it (where are the small phones?!?) and the display breaks easily (just one drop from about 60 cm into the shower tub did the trick), it's a great device.
I also must say again that I like mycelium and it'll probably replace spinner. Love the multi-address feature, however for me to use this safely, I suggest 2 changes:
- before receiving money to an address, display warning if the private key is not known
- when deleting a private key that has money on it, mention that in the delete confimation dialog
And one question: can mycelium combine money from different keys when sending? It currently seems to me that the 2 addresses I have are handled as completely separate wallets? If that's correct, you could call them "wallets" instead of "addresses".
wishlist:
Be able to
* specify fiat amount for tx.
* swipe private keys.
Be able to
* specify fiat amount for tx.
* swipe private keys.
* specify fiat amount for tx.
Yes, both when sending and receiving
Quote
* swipe private keys.
Almost. You can import a private key, spend from it, and delete it.
I like it. Because of the security risk I assume you write a warning or something...Almost. You can import a private key, spend from it, and delete it.
wishlist:
Be able to
* specify fiat amount for tx.
* swipe private keys.
Be able to
* specify fiat amount for tx.
* swipe private keys.
* specify fiat amount for tx.
Yes, both when sending and receiving
* swipe private keys.
Almost. You can import a private key, spend from it, and delete it.
wishlist:
Be able to
* specify fiat amount for tx.
* swipe private keys.
Be able to
* specify fiat amount for tx.
* swipe private keys.
is there a way to copy the address I just sent money to?
in other words: I would greatly appreciate the transaction history item have a context menu that at least contains: "copy receiving address".
You will get it all in the next generation wallet.in other words: I would greatly appreciate the transaction history item have a context menu that at least contains: "copy receiving address".
Andreas and I are making the final touches on the Mycelium wallet. Right now we are at the "getting new server certificates, Google Play publishing certificates, and publishing sources" stage. Just a few days until open beta.
Molecular, I happen to remember that you used an Android 2.1 device. The new wallet will be Android 2.2 and forward only (more than 90% of the market), so I really hope you have upgraded in the meantime.
The sources are open and if you know a skilled blackberry developer up for it I'd be happy to give him my support.
So is this, from a Kévin Forest, not an approved release? (it is named "Bitcoin Spinner"):
- http://appworld.blackberry.com/webstore/content/20080938/
I didn't build or sign the APK, and don't know the developer who did, and thus cannot vouch for it's integrity. If I had a BB I would only use this version for pocketchange.
is there a way to copy the address I just sent money to?
in other words: I would greatly appreciate the transaction history item have a context menu that at least contains: "copy receiving address".
in other words: I would greatly appreciate the transaction history item have a context menu that at least contains: "copy receiving address".
The sources are open and if you know a skilled blackberry developer up for it I'd be happy to give him my support.
So is this, from a Kévin Forest, not an approved release? (it is named "Bitcoin Spinner"):
- http://appworld.blackberry.com/webstore/content/20080938/
I love Spinner, but I would love it even more if we could import private keys, I also would love to use vanity addresses on my cell.. 
That feature is announced for the rewrite.
I love Spinner, but I would love it even more if we could import private keys, I also would love to use vanity addresses on my cell..
That feature is announced for the rewrite.
I love Spinner, but I would love it even more if we could import private keys, I also would love to use vanity addresses on my cell..
That feature is announced for the rewrite.
I love Spinner, but I would love it even more if we could import private keys, I also would love to use vanity addresses on my cell..
I am right now working full time on the next generation of BitcoinSpinner, lit will be a full rewrite. Allowing the user to specify mBTC instead of BTC will be included along with an awesome set of new features.
This is awesome news! I am looking forward to it!
Will it be also possible to import private keys from WIF51 format? At the moment it can only import ("restore") from bitcoinspinner's proprietary wallet format.
Reason for my question: I'd like to generate a key with vanity address with "vanitygen" and use that one in my smartphone, like "1phoneXYZ..." to be able to differentiate it from my other addresses.
Update: I have made a fix on the backend system, and Richy_T has confirmed over PM that he can now monitor his coinbase transactions using BitcoinSpinner. The bug was not directly related to coinbase transactions in general, but to the 'strange' zero value transaction output at the end of each transaction that the mining pool he uses adds. Look for the last output in this sample: https://blockchain.info/tx/7b5cfb3365f1fe227376b218c0db681fda089d0582190f78d315c3ab019782bb
Interesting. I'll pass this on to the pool guys too. Thanks.
Sorry for not getting back to you on this issue earlier. As I noted above BitcoinSpinner does not handle coinbase maturity. This means that if you mine directly to a BitcoinSpinner wallet and it sends a transaction that references a coinbase input before it has 100 confirmations it will get rejected by the network until the coinbase has fully matured. The effect will be that your transaction will get delayed anywhere between 0-100 blocks.
Hi Jan, I think this is a separate issue as the transactions I was testing against were most definitely mature. Since I'll be discontinuing mining to the bitcoinspinner wallet, this is not really an issue for me anymore. I did like seeing the transactions come in but I'll probably just put together an android app for that.
Sorry for not getting back to you on this issue earlier. As I noted above BitcoinSpinner does not handle coinbase maturity. This means that if you mine directly to a BitcoinSpinner wallet and it sends a transaction that references a coinbase input before it has 100 confirmations it will get rejected by the network until the coinbase has fully matured. The effect will be that your transaction will get delayed anywhere between 0-100 blocks.
Hi Jan, I think this is a separate issue as the transactions I was testing against were most definitely mature. Since I'll be discontinuing mining to the bitcoinspinner wallet, this is not really an issue for me anymore. I did like seeing the transactions come in but I'll probably just put together an android app for that.
The root problem is that BitcoinSpinner does not regard coinbase inputs as unspendable until they have matured. This is clearly a bug, and something I'll have to look into.
OK. I'll stop sending my coinbase transactions to bitcoinspinner for now.
Not sure if this is a bug in bitcoinspinner or just my cobbled-together setup. I mined some coins to the address and they showed up OK but when I click on "View transaction history", I get a null pointer error in AsynchronousApi.java, line 171. I wonder if because there *are* transactions but none of them can be displayed, I get this error. I'll try sending some coins there through regular transactions and see what that does.
s is null from map.get(item.hash);
There are two entries in map.table, 0 and 1 and both are null. I assume that this is related to transactions.array which is in a similar state.
I'll try and work out what's going on as I dig in deeper but I just thought this might be something of interest to you.
Edit: Sending more coins to the wallet did not help with the null pointer. So next up I have created a new wallet which received sent coins OK and next I will try to mine to it.
It's looking to my like BCCAPI isn't returning any info when the info for the mined transactions is being requested. But I'm not sure on that yet. More to discover...
As I have never mined I did not have the opportunity to test BitcoinSpinner with coinbase transactions. My gut feeling is that it chokes because the transaction has no outPoint (funding transaction). Can you send me a stack-trace and a transaction ID?s is null from map.get(item.hash);
There are two entries in map.table, 0 and 1 and both are null. I assume that this is related to transactions.array which is in a similar state.
I'll try and work out what's going on as I dig in deeper but I just thought this might be something of interest to you.
Edit: Sending more coins to the wallet did not help with the null pointer. So next up I have created a new wallet which received sent coins OK and next I will try to mine to it.
It's looking to my like BCCAPI isn't returning any info when the info for the mined transactions is being requested. But I'm not sure on that yet. More to discover...
- Jan
Hi Jan, I posted over in the bccapi thread. It appears that there are a couple of issues at play. Foremost is that bccapi appears to not return information for transactions from mining (Though it does list them in the transaction history object it returns). This puts an immediate stop to any plans I had to add that in (in fact, it seems it's possible that if BCCAPI did return the information, Bitcoinspinner would display them correctly anyway). Secondly, Bitcoinspinner seems to not handle this missing information gracefully. However, this appears to be conditional somehow as I mine to my wallet on my phone all the time and it runs fine (apart from not displaying the mining transactions).
Sorry for not getting back to you on this issue earlier. As I noted above BitcoinSpinner does not handle coinbase maturity. This means that if you mine directly to a BitcoinSpinner wallet and it sends a transaction that references a coinbase input before it has 100 confirmations it will get rejected by the network until the coinbase has fully matured. The effect will be that your transaction will get delayed anywhere between 0-100 blocks.
Jump to: