Topic: [SERVICE] [Android] [2 btc] [Google Play] Android Qt wallet compilation - page 2. (Read 6689 times)

I only offer the standard client for now, I will offer a solution similar to coinomi soon, including iOS support.

With modern phones, storing the chain is not really a big deal, also as shown in the pie chart posted before, the ressources usage is very reasonable, but the standard wallet offers some features coinomi doesn't like wallet encryption, backup and more.

I have tested this wallet with coins that are more than a year old and it works fine. Thanks!

Have you done Android compilation with Coinami? https://bitcointalksearch.org/topic/universal-wallet-coinomi-bip44-compatible-713649

The issue I have with an android wallet would be holding the entire chain on your phone so over time it would consume a fair amount of resources. Coinami is open source and uses an electrum server to create a lightweight client. Is this something that you think you would be able to do?

If that is not possible then just the standard client would be fine, I have BTC available for the work.

Sounds good, thanks

Great, I'll get some BTC together, do some checks with the source and let you know once I'm ready

2 to 4 days depending on my work load.

How long does it normally take to do the android wallet?

Security is the same as the desktop linux wallet with compilation securities like buffer overflow protection, and also user security as the wallet offers the same encryption options as the desktop client to encrypt the wallet with password.

Other java/javascript android wallets are less secure than this one.

how about security owned by android wallet qt so far? whether toughness similar to those of the PC?

Well looks like what you need is an rpc client to connect to your remote staking nodes, it can be done over https for more security. No need for an android wallet in your case 

Yes but it only allows you to host a small amount of different Coins on any one phone, if you had 5-6 different POS Coins on an android phone Staking, updating Blockchains and the average chain was 1 gb then that is 5-6 GB of space along with the resources required to constantly sync and run those wallets and that would drain your battery and resources very quickly. If you could connect to your own hosted wallet then you could host the chains there, or on several different nodes and the space, CPU requirements and Staking would be handled there with near 100% uptime so you could then connect to different nodes you control which may host 10-15 Blockchains each at $5 a month per node hosted, then you are only using and controlling your nodes from your android without consuming the resources and could manage 30-50 different Coins without any impact on usage.

I did some work last year where I connected through VNCviewer to a Linux node and would be perfect if using additional security of SSH keys and multilayer-security in order to connect. The only issue I had was being able to use it properly on a touchscreen since it's made for a desktop so was very cumbersome to use. If doing an android wallet traditionally, you need to constantly rebuild the wallet whenever doing updates, it would be better to more or less use the system by viewing it and manage updates through Linux which is the standard for building.

I had the same idea, but accomplishing this would require some major changes to how the code handles the blockchain database. Not sure if it is worth it as with modern sd cards, disk space is cheap.

Could you make an andoid wallet which works locally on the phone as a light client that connects to your own web wallet? The idea is something akin to VNCviewer in which you would connect with your SSH keys to your node so you don't have to run the Blockchain and Stake and use resources on your phone. The problem I have with android wallets is that Staking and holding many different Blockchains uses up a lot of resources when it would be better to be able to connect remotely to your own hosted and secured node which holds the Blockchain and Stakes for you but to have the functions of use and the QT. If you were running POS on your phone then you could only Stake when connected when you want to be able to be connected, staking and synced all the time.

Price reduced to 1BTC

Nice service, yes direct Qt wallet compilation for android is a better solution in many cases, especially for PoS coins.

I'm skipping qrencode and miniupnpc for now, might give it a shot if it is necessary, but most coins do no use qrencode at all, nor miniupnpc on linux.

I'm curious, did you manage to get both qrencode and miniupnpc compiled for ARM or have you decided not to implement them?

Very interesting.  This provides a quicker way that what I do with bitcoinj/bitcoin-wallet.