The successor of BitcoinSpinner is now available for open beta on Google Play: https://play.google.com/store/apps/details?id=com.mycelium.walletThe sources are published here: https://github.com/mycelium-com/walletApart from a total rewrite the wallet has a new name: Mycelium Bitcoin WalletThe security model of the Mycelium wallet is the same as for BitcoinSpinner: Your private key only leaves your device if you choose to export it. In addition to having all the features of BitcoinSpinner it boasts an impressive set of new features, many of which were asked for in this thread: - Private key import (also Casascius private keys)
- Manage multiple keys/addresses
- Redundant backend servers with client side load balancing
- Uses new fee rules (0.0001 pr 1000 bytes, etc)
- Switch between BTC/fiat when sending coins
- Switch between BTC/fiat amount when making a payment request
- Export private key to SD card (allows printing without intermediary computer)
- Change Bitcoin denomination: BTC, mBTC, uBTC
- Integrated QR scanner
- Landscape mode
- Improved transaction history
- View transaction details: tx hash, block#, inputs/outputs
apetersson and I have been working really hard on developing this. We hope you like it and leave a 5 star review on Google Play. Our thanks go to Jethro, who has done an astounding job testing all the corners of the wallet on many devices. The Mycelium Bitcoin Wallet deserves its own thread, but we would like to announce it in this thread first and let the hard-core BitcoinSpinner users give us some feedback. TL;DR The successor of BitcoinSpinner is now available for open beta on Google Play: https://play.google.com/store/apps/details?id=com.mycelium.walletThe sources are published here: https://github.com/mycelium-com/walletWe hope you like it and leave a 5 star review  |
|
|
|
What if a trusted member in the Bitcoin community sets up the vanity address. We start the campaign to fill it. Do a few press releases. When the amount is significant enough I believe the problem of getting the private keys in Snowdens hands will solve itself.
How about we start with getting him on board? |
|
|
|
wishlist: 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. |
|
|
|
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. 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. |
|
|
|
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 thread about this already? It's one of the most awesome things I've run into recently. Beccy & Austin are having their wedding in 1 month. They plan to live the first 90 days of their marriage using only bitcoins! They have a professional film crew but they need funding to do it. It can be funded with bitcoins and USD. http://lifeonbitcoin.com/This project is absolutely awesome. I already donated personally and our company will also support this. Wow... Awesome. Watch the video. |
|
|
|
The truth is that I never came around to do a pull request on the page. I'll do it for the re-write. Now that Bitcoin-QT has changed its default TX fee to 0.0001 is it possible you do the same?
The sooner the clients implement the lower fee, the sooner miners will accept it with the same priority as the previous one.
Thanks!
Yes, the new fee rules will be applied in the re-write. Not only the 0.0001 fee pr 1000 bytes, but also the minimum output size. |
|
|
|
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. ... and it is soon going into closed beta  |
|
|
|
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. 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 |
|
|
|
...
Fee Policy changes
The default fee for low-priority transactions is lowered from 0.0005 BTC
(for each 1,000 bytes in the transaction; an average transaction is
about 500 bytes) to 0.0001 BTC.
Payments (transaction outputs) of 0.543 times the minimum relay fee
(0.00005430 BTC) are now considered 'non-standard', because storing them
costs the network more than they are worth and spending them will usually
cost their owner more in transaction fees than they are worth.
Non-standard transactions are not relayed across the network, are not included
in blocks by most miners, and will not show up in your wallet until they are
included in a block.
The default fee policy can be overridden using the -mintxfee and -minrelaytxfee
command-line options, but note that we intend to replace the hard-coded fees
with code that automatically calculates and suggests appropriate fees in the
0.9 release and note that if you set a fee policy significantly different from
the rest of the network your transactions may never confirm.
...
Gavin, was it only mintxfee that changed in this release? In other words: are mintxfee and minrelaytxfee the same now? Also, the minimum allowed output will gradually invalidate most alternative client implementations, time to start coding. I guess that the policy for change-back-to-self worth less than 5420 satoshis should be to remove the change output add it to the miner fee. In general I think it is time to update https://en.bitcoin.it/wiki/Transaction_fee |
|
|
|
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? - 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. |
|
|
|
It would be really nice to be able to change the unit to mBTC on BitcoinSpinner. I cant see that option currently.
Small payments are troublesome in BTC. Sometimes I put too many decimal places
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. |
|
|
|
Sent a transaction at 8:44. Still listed as incomplete in BticoinSpinner's transaction history but *does not* appear in the blockchain at all. I missed out on a group buy because of this and now have coins presumably heading somewhere where they will no longer do me any good. Not happy. http://blockchain.info/address/13qnEgPTxJW6mm88dLpnHXZyryN5EXBciqThe transaction you sent has the following hash 6b92ba8967f1a8794b30acc30e8dc13848e2cab70cb919d29c15631e184f0f3d and is being rejected by the network. The problem seems to be that that it uses input 185 from this transaction 5826ac8c46bd42de7d9a80b0168bc022b483b2c14a099f28e1c6ca1adfd4f445 which is a coinbase transaction with 55 confirmations. The network will reject your transaction until the coinbase transaction has matured, which happens after 100 confirmations. 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. After 45 additional blocks your transaction will no longer be rejected, and the next re-broadcast attempt after that will successfully push it into the network. |
|
|
|
I have noticed my bitcoin transactions are taking longer and longer to process, could this be a perpetuating issue? How practical would it be to use a currency that takes a day to process a transaction? Or am I just way of base here?
Do yoy pay transaction fees? |
|
|
|
...
Would you please share the latest version of Spinner as it is in the market. The market version was updated several times but not so the repository.
The market and repository have the same released versions, the most recent is 0.8.2b. Are you planning to open source the rewrite, too?
(This one you implicitly answered with "yes", which I'm glad to hear.)
On another topic, will the new version avoid the one-address-for-life pattern? The implications of people seeing the money that went through my pocket and that will go through it are scary.
The new version allows you to manage several keys and read-only addresses. This makes the UI more complicated, and will be confusing for newcomers. For that reason I am considering to make two versions... simple/expert. Let's see how it all pans out. |
|
|
|
When copying the address to the clipboard, it is preceded by the prefix "bitcoin:" - in most cases, this just requires manual deletion of the prefix by the user when pasting into the Web form.
Can we have the handle removed, and only copy the address itself?
Absolutely, good idea. I'll do that in the rewrite. Can we have the latest version in the repository?
Jan you claimed a rewrite. Will that be open source, too?
The rewrite is still very much in alpha. I have shown it to anyone interested at the conference, and the feedback has so far been very positive. If you are at the conference seek me out at the Mycelium booth and I'll give a demo. The sources (and the app) will be published once I have given it more polish. Please allow me to work on it a few more weeks :-) |
|
|
|
|
Does anyone have stats on which versions are currently running?
I really wonder whether 0.8.1 has majority.
|
|
|
|
|
For those of you attending Bitcoin2013 in San Jose the coming weekend, I'll be demonstrating the next generation Bitcoin wallet for android, which will eventually replace BitcoinSpinner. It is a total rewrite, where I use all the experience gained from BitcoinSpinner over the last 1.5 years and all your feedback to create the best mobile bitcoin wallet on the planet.
Most notable features (not present in BitcoinSpinner):
- Import Private key (and obviously export)
- Multiple keys with key-control
- Readonly wallet (only holds Bitcoin address)
Sneak peek of what you can do (Cold storage spending scenario):
1) take a pice of paper from your safe with a SIPA formatted private key as a QR code
2) import the key to your phone by scanning the QR code
3) send some funds to some other address
4) delete the key from the phone
The entire operation takes less than a minute
Sneak peek of what you can do (Cold storage monitoring):
1) You have a Bitcoin address on a piece of paper as a QR code
2) Import the bitcoin address to your phone by scanning the QR code
3) Monitor balance/history of the bitcoin address
If you loose your phone only your bitcoin address is revealed
All of this is currently in alpha, but I'll release a beta some time after the conference.
|
|
|
|
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? - Jan |
|
|
|
|
Show Posts
