You should use getaccountaddress, not getnewaddress. getaccountaddress only creates a new address once you received coins to the previous address.
|
|
|
It's probably not only the CommandLineRPC method that causes problems. UTF-8 account names created from js-remote are wrong, too.
|
|
|
Another idea: Force SSL by default and don't add CORS (doesn't work well over SSL anyway), then use a proxy like SSLserver.py from js-remote that serves the Javascript UI and proxies RPC calls through another SSL connection.
|
|
|
It seems like the RPC interface can't handle account names with non-ASCII characters properly. Copy&paste form listaccount to getaccountaddress will create a new account with yet another name.
Can we restrict accountnames to a limited charset (like [a-zA-Z0-9\-_]) or add UTF-8 support?
|
|
|
I think this is about adoption. If you start using xbtc that would count in its favor.
I personally would prefer the shortest possible, as this keeps the qrcodes small. x-btc mandates an action to be specified ("store" or "send" currently) and also mandates the "addr=" part in front of the adress, both which I consider to be redundant.
I like the simplicity of bitcoin:xxxxxxxxxxxxx plus very much approve of its accessibility. Should someone from the outside happen to see such a uri, the protocol name already gives a description. A quick google search should then do the rest. x-btc sounds much more cryptic, the chance that s/1 gooogles that out of curiosity are much slimmer. Also, very likely, what s/he will find are mostly technical specifications. Not a good introduction to bitcoin.
Yep, having bitcoin: infront of the adress seems more accessible. Maybe we can work on a "new" URI scheme using ideas from both?
|
|
|
here is a qr-code generator for the software to read: http://qr.ma.eatgold.com/it supports specifying an amount to be sent. the js-software can implement this quite easily. Can we first please stick to one URI scheme? I don't want to parse QR codes for three different possible schemes. I prefer x-btc.
|
|
|
I'd like to add that feature to js-remote (address + amount). Do we have a simple URI scheme that supports that, yet?
|
|
|
Added SSL support to js-remote using a little server script.
|
|
|
Added SSL support (using a small SSL webserver).
|
|
|
Wait a second, I thought this is about a full implementation of Bitcoin on top of Android and not some remoting.
You can run bitcoind on the phone. This even makes your wallet compatible with the desktop version.
|
|
|
SSL works in theory. In practice, there's either a bug in browsers or bitcoind that prevents a reliable connection. I hope to resolve that within the next days.
|
|
|
My js-remote is fully working on Android and supports local transactions by displaying QR codes on the phone and scanning them with the camera. It's also possible to display QR codes on a computer and send Bitcoins to it from a phone. Does this qualify for the bounty?
|
|
|
New feature: Display address as QR code and scan QR codes on Android phones. This makes phone2phone transfer of bitcoins possible without having to enter addresses.
|
|
|
Is this going to be enabled by default ?
Yep. It just adds two headers so browsers don't complain when using JSON-RPC across domains.
|
|
|
I've created a JavaScript user interface for bitcoin. It's project page is located at: http://tcatm.github.com/bitcoin-js-remote/bitcoin-js-remote is a user interface for Bitcoin written in JavaScript. It works in most modern browsers as well as on Android and iPhones. If run on an Android phone it can scan QR codes containing addreses to send Bitcoins to! If you don't own an Android device, you can still enter raw bitcoin: URIs in a textbox. For SSL support a small server side script written in Python is required. - SSL for secure communication
- Display QR code with address
- Scan QR codes (Android only)
- Supports multiple accounts
- Android and iPhone support
- Send and receive Bitcoins
- List transactions
|
|
|
Thanks for the donation(s)!
@bitcoinex: I'll add your orderbooks soon.
Network graphs are on my todo. Currently busy with another interesting bitcoin project that's close to release.
|
|
|
That coin is a very cool momento. You should consider selling that merchandise.
I'm working on it. I'm currently trying to make a copper core + gold surface coin.
|
|
|
|