Topic: Android Bitcoin RPC client (Read 10899 times)
I can't get it working anymore =( the only think I did was upgrading the bitcoin client on windows. using bitcoin 0.6.2 now.
I think this project died, and I can't find any WORKING, CURRENT RPC front-ends on Android. Anyone have any ideas on either getting this project back up and updated and working with the current bitcoind? Or are there alternatives out there I'm just not seeing?
nice project.
I am looking for an existing android client that could be adapted to Electrum.
I was thinking to use BitcoinSpinner, but perhaps this one would be better.
I think this project died, and I can't find any WORKING, CURRENT RPC front-ends on Android. Anyone have any ideas on either getting this project back up and updated and working with the current bitcoind? Or are there alternatives out there I'm just not seeing?
I can't find this app at the market and cannot install it via the market-website. So I guess this is because my Phone is an HTC Wildfire (is this a matter of the screen size?). Will there be a version for my phone?
Here: http://www.filesonic.com/file/1080163654/bitcoin.zip
This won't crash when rpcssl=1, and it works with this great android app too!
This won't crash when rpcssl=1, and it works with this great android app too!
Very nice work!
Here: http://www.filesonic.com/file/1080163654/bitcoin.zip
This won't crash when rpcssl=1, and it works with this great android app too!
This won't crash when rpcssl=1, and it works with this great android app too!
Just an idea:
What would you think about a thin client that doesn't store the block chain, but only talks to one trusted node who does all the checking and verifying.
It would have it's own wallet.
It seems like no advantage over the existing RPC client, but you could choose to trust a node of a friend or a respected community member like the slush pool node.
So you would not necessarily need to set up your own internet-accessible node.
Any thoughts?
What would you think about a thin client that doesn't store the block chain, but only talks to one trusted node who does all the checking and verifying.
It would have it's own wallet.
It seems like no advantage over the existing RPC client, but you could choose to trust a node of a friend or a respected community member like the slush pool node.
So you would not necessarily need to set up your own internet-accessible node.
Any thoughts?
I've had a bounty waiting for this exact concept for months.
I started compiling from source according to this guide http://forum.bitcoin.org/index.php?topic=5851, and this post http://forum.bitcoin.org/?topic=1434.msg16585#msg16585, but dear Thor does it take long!!
I'll post the SSL-enabled result here whenever it's done, hopefully it'll enable me to use this app.
I'll post the SSL-enabled result here whenever it's done, hopefully it'll enable me to use this app.
Just uploaded a small update that should help with the force closes.
Just an idea:
What would you think about a thin client that doesn't store the block chain, but only talks to one trusted node who does all the checking and verifying.
It would have it's own wallet.
It seems like no advantage over the existing RPC client, but you could choose to trust a node of a friend or a respected community member like the slush pool node.
So you would not necessarily need to set up your own internet-accessible node.
Any thoughts?
What would you think about a thin client that doesn't store the block chain, but only talks to one trusted node who does all the checking and verifying.
It would have it's own wallet.
It seems like no advantage over the existing RPC client, but you could choose to trust a node of a friend or a respected community member like the slush pool node.
So you would not necessarily need to set up your own internet-accessible node.
Any thoughts?
I figured as much. =/
Oh well, compiling bitcoin with SSL support is a project for another day... unless someone trusted already has the compiled binaries for this?
Oh well, compiling bitcoin with SSL support is a project for another day... unless someone trusted already has the compiled binaries for this?
I did try to follow those instructions. After i've created my certificate and updated bitcoin.conf to use rpcssl=1 i am told to restart bitcoin.exe but then it chrashes with the "bitcoin not compiled with full openssl libraries" error.
Could it have anything to do with this?
https://bitcointalksearch.org/topic/m.16585
or is that old post no longer relevant?
Could it have anything to do with this?
https://bitcointalksearch.org/topic/m.16585
or is that old post no longer relevant?
I just tried it on windows and it seems like you'd have to compile it with ssl support. My node runs on linux and apparently it's already built in there.
In the meantime you can try the app out inside your local network without SSL.
I did try to follow those instructions. After i've created my certificate and updated bitcoin.conf to use rpcssl=1 i am told to restart bitcoin.exe but then it chrashes with the "bitcoin not compiled with full openssl libraries" error.
Could it have anything to do with this?
https://bitcointalksearch.org/topic/m.16585
or is that old post no longer relevant?
Could it have anything to do with this?
https://bitcointalksearch.org/topic/m.16585
or is that old post no longer relevant?
Perhaps a noob question... but do i have to compile my own version of the official bitcoin client to get SSL support?
Getting error "bitcoin not compiled with full openssl libraries" when trying to use rpcssl=1
Getting error "bitcoin not compiled with full openssl libraries" when trying to use rpcssl=1
I guess its because bitcoin can't create a certificate itself.
This "https://en.bitcoin.it/wiki/Enabling_SSL_on_original_client_daemon) should get your started.
Perhaps a noob question... but do i have to compile my own version of the official bitcoin client to get SSL support?
Getting error "bitcoin not compiled with full openssl libraries" when trying to use rpcssl=1
Getting error "bitcoin not compiled with full openssl libraries" when trying to use rpcssl=1
You should be able to use host names. I'm using
'https://somehost.dyndns.org:8332' as URL string and it works fine.
Thanks, I'll give it one more try…
Update: it works with hostname, I don't know why it crahsed last time then.
Cheers,
Update to v0.92
Alert the user if SSL certificate changes.
----------
You should be able to use host names. I'm using
'https://somehost.dyndns.org:8332' as URL string and it works fine.
Alert the user if SSL certificate changes.
----------
You should be able to use host names. I'm using
'https://somehost.dyndns.org:8332' as URL string and it works fine.
Update to v0.91
Client allows untrusted certificates because installing certs on android is a pain. So more people can use SSL (https://... instead of http://)
That's very cool! I managed to import an SSL-certificate, but the previous version failed to connect over https anyway. Perhaps I did something else wrong…
With the new version, however, I have to ring in the server's IP address — if I ring in a hostname Bitcoiner crashes (and I have to go to the system settings and clear any data associated with Bitcoiner to be able to enter an IP address instead). Is this the expected behaviour, or should I be able to use a hostname?
Cheers,
You mean like a message "This certificate is untrusted, trust anyway and never show this message for this certificate again"?
Yep, something like that. Could you cache ssl certs for known servers and/or warn the user if a certificate is untrusted?
You mean like a message "This certificate is untrusted, trust anyway and never show this message for this certificate again"?
Jump to: