Another thing I can't believe I missed; why isn't there a sendmany type option to include multiple outputs?
We are very keen on keeping the UI simple while being rich on features. This means making many tough choices. Sendmany is IMO a feature you would rarily use on a mobile wallet, actually you are the first one asking for it.
Topic: Mycelium Bitcoin Wallet - page 107. (Read 586368 times)
Thanks for your support 
Don't worry about the UI falling behind. We do have grand plans to overhaul it.
If you have any specific suggestions or something is bugging you, please don't hesitate to post here or write to [email protected]
if you want to see the early beta builds you need to join the google group AND activate beta builds at https://play.google.com/apps/testing/com.mycelium.wallet
Don't worry about the UI falling behind. We do have grand plans to overhaul it.
If you have any specific suggestions or something is bugging you, please don't hesitate to post here or write to [email protected]
if you want to see the early beta builds you need to join the google group AND activate beta builds at https://play.google.com/apps/testing/com.mycelium.wallet
just beta or normal work this?
this posible backup or restore?
Backup/restore? Yes, since the very first version. Most notable features shown in this video: http://youtu.be/G8FmwbgJuLM
Another thing I can't believe I missed; why isn't there a sendmany type option to include multiple outputs?
We are very keen on keeping the UI simple while being rich on features. This means making many tough choices. Sendmany is IMO a feature you would rarily use on a mobile wallet, actually you are the first one asking for it.Thanks for your support
Don't worry about the UI falling behind. We do have grand plans to overhaul it.
If you have any specific suggestions or something is bugging you, please don't hesitate to post here or write to [email protected]
if you want to see the early beta builds you need to join the google group AND activate beta builds at https://play.google.com/apps/testing/com.mycelium.wallet
Don't worry about the UI falling behind. We do have grand plans to overhaul it.
If you have any specific suggestions or something is bugging you, please don't hesitate to post here or write to [email protected]
if you want to see the early beta builds you need to join the google group AND activate beta builds at https://play.google.com/apps/testing/com.mycelium.wallet
just beta or normal work this?
this posible backup or restore?
Another thing I can't believe I missed; why isn't there a sendmany type option to include multiple outputs?
You can set a "trusted peer" in the Schildbach wallet, which makes it connect to only that address.
Still not enough to say that the SPV store is not the correct way to do it, because you don't have to download from genesis block. You would download from last checkpoint, or somethign smarter in the future by maybe the last block of the first transaction of the wallet which MUST be after the earliest original checkpoint.
Are there any mobile wallets out there that connect to a running version of Bitcoind that you're running at home? That would seem to be the way to go to me if you wanted to stay decentralized (Though I'm happy with the Mycelium model for walking-around purposes).
We are expanding!
We are determined to deliver the best mobile wallets in the Bitcoin space. To do this we need more hands on deck.
We are currently have four positions open:
Details: http://megiontechnologies.com/career.html
We are determined to deliver the best mobile wallets in the Bitcoin space. To do this we need more hands on deck.
We are currently have four positions open:
- DevOps Engineer for Bitcoin Technologies
- Mobile Developer for Bitcoin Technologies
- Community Manager for Bitcoin Technologies
- Embedded Systems Developer
Details: http://megiontechnologies.com/career.html
This sounds like a lot of fun. I'm not looking to move though, unfortunately
I was going the reverse engineer approach but since there are signed keys involved this is probably not possible
As I understand it the complete source of the Mycelium wallet app is on github, what keeps you from reading the portion of the code that is talking with their servers to understand what the server must do and replace the SSL certificate in the code with the one of your own server once you have managed to write one?You're right I could do the same thing, just alot more work to figure out how each call to the API relates to talking to the bitcoin node. I preferred not to because its hard to really look inside of a closed loop to see what is going on from every angle. If people really wanted this Im guessing someone would do it anyway, or they can simply open up their API like they should. Having it closed to me means there are hidden agenda's we don't know about.
I looked into the BitcoinSpinner source and the API was pretty straightforward. I'm guessing that the Mycelium API is similar if not identical as there are only so many things you can do and so many ways to do them. My main complaint was that it relied on serialized Java objects rather than a more general standard. It only took me a couple of hours to find what I was trying to look for and I'm not even a Java guru.
I think the major part of writing a version of this would be the whole blockchain side of things. Possibly you'd want to look at that Abe project someone else is working on.
Yeah, Andreas' wallet just puts a bitcoin URI into the NFC tag.
This would probably be the easiest option. Bonus points if there's a cool animation lol
Yeah, Andreas' wallet just puts a bitcoin URI into the NFC tag.
We should look into that. I actually think that it would be a small change. I only have one NFC enabled device, but I think Andreas has access to two
My thinking is that the receiving device should broadcast a Bitcoin URI with optional amount when on the Receive page, and the sending device automatically populates address/amount if it receives the URI when on the Send page. This could be a start and from that we could investigate whether it is feasible / secure to automatically launch the app when close to an NFC device.
That sounds really nice. I've been thinking that NFC should be an option. It would also open the door for smaller devices without a camera or full display to authorize transactions on their own. All they'd have to do is display the price and get a confirm or deny from the user.My thinking is that the receiving device should broadcast a Bitcoin URI with optional amount when on the Receive page, and the sending device automatically populates address/amount if it receives the URI when on the Send page. This could be a start and from that we could investigate whether it is feasible / secure to automatically launch the app when close to an NFC device.
I've got a suggestion, what if Mycelium could use NFC to send bitcoins to another phone? Like you press send, then tap NFC instead of QR and the others and then you type in an amount, then you put your phone up against the other person's which provides a receiving address, and your phone shows a bitcoin icon that you tap to send the coins (also enter PIN). A little easier when both people have phones than scanning qr codes, and takes advantage of newer technology. Thoughts?
We should look into that. I actually think that it would be a small change. I only have one NFC enabled device, but I think Andreas has access to two My thinking is that the receiving device should broadcast a Bitcoin URI with optional amount when on the Receive page, and the sending device automatically populates address/amount if it receives the URI when on the Send page. This could be a start and from that we could investigate whether it is feasible / secure to automatically launch the app when close to an NFC device.
I've got a suggestion, what if Mycelium could use NFC to send bitcoins to another phone? Like you press send, then tap NFC instead of QR and the others and then you type in an amount, then you put your phone up against the other person's which provides a receiving address, and your phone shows a bitcoin icon that you tap to send the coins (also enter PIN). A little easier when both people have phones than scanning qr codes, and takes advantage of newer technology. Thoughts?
We should look into that. I actually think that it would be a small change. I only have one NFC enabled device, but I think Andreas has access to two My thinking is that the receiving device should broadcast a Bitcoin URI with optional amount when on the Receive page, and the sending device automatically populates address/amount if it receives the URI when on the Send page. This could be a start and from that we could investigate whether it is feasible / secure to automatically launch the app when close to an NFC device.
I've got a suggestion, what if Mycelium could use NFC to send bitcoins to another phone? Like you press send, then tap NFC instead of QR and the others and then you type in an amount, then you put your phone up against the other person's which provides a receiving address, and your phone shows a bitcoin icon that you tap to send the coins (also enter PIN). A little easier when both people have phones than scanning qr codes, and takes advantage of newer technology. Thoughts?
I noticed a small bug; when scanning a qr code for sending with amount=0.0892, the amount sent was exactly 0.089, so it seems amounts gets rounded somehow.
Which app was the QR code created with, Mycelium, or something else?
I noticed a small bug; when scanning a qr code for sending with amount=0.0892, the amount sent was exactly 0.089, so it seems amounts gets rounded somehow.
(Wrote this here since apparently Google now requires google+ for commenting in play store).
Thanks for the report. I am unable to reproduce this.(Wrote this here since apparently Google now requires google+ for commenting in play store).
I have made a payment request and sent it to myself in an email like this:
Tap Receive -> tap the keyboard icon -> enter 0.0892 -> Ok -> Share Payment Request -> Gmail -> my email address
Result: bitcoin:1BoBsT2QicxGf3eroqcaXTwz9qaYiZZSNC?amount=0.0892
I have turned the string into a QR-code: http://imgur.com/KJnqj3H
When I scan it I get the correct amount 0.0892
Here is the transaction i sent: https://blockchain.info/tx/51096ef74647dd692b2bb64c88f0b9ff1b87fc231daf1ba3533ed771f9ae5043
If you can reproduce the bug please send me a copy of the QR code you scanned.
That's interesting. On my laptop, I still use bitcoin-qt, and I only get connected to 8 to 20 nodes. Every transaction I make, with or without fees, appears in blockchain.info within 1 to 2 seconds as soon as I broadcast it.
Your servers sending to 250+ nodes should get noticed by blockchain immediately.
I believe it is a matter of how many transactions you send. I have noticed it once in a while, but I don't have any statistics. Your servers sending to 250+ nodes should get noticed by blockchain immediately.
I noticed a small bug; when scanning a qr code for sending with amount=0.0892, the amount sent was exactly 0.089, so it seems amounts gets rounded somehow.
(Wrote this here since apparently Google now requires google+ for commenting in play store).
(Wrote this here since apparently Google now requires google+ for commenting in play store).
That's interesting. On my laptop, I still use bitcoin-qt, and I only get connected to 8 to 20 nodes. Every transaction I make, with or without fees, appears in blockchain.info within 1 to 2 seconds as soon as I broadcast it.
Your servers sending to 250+ nodes should get noticed by blockchain immediately.
Your servers sending to 250+ nodes should get noticed by blockchain immediately.
Jump to: