Online `savings` to `current` account replenishment idea

[jago25_98]

 Here's a simple idea.
 
 Have a wallet on your own webserver, this server as locked down as possible. Have a button on that server that can only send to one address; your `current account`. For ease of use the amount could be fixed or for security, the amount limited. 

 Thus, let's say you use your Android wallet for everyday spending. If your phone gets stolen you shouldn't have much balance to lose.

 In addition to this you can backup the private key from the phone wallet to somewhere safe. If the phone walks you would probably have time to grab the balance and send it elsewhere, especially if the Bitcoin wallet app is not too obviously accessible, I wouldn't expect a thief to know enough to react quicker than you can anyway.

 It's important not to have access to the webserver logged in the phone browser history too.

[1714056854]

1714056854

[1714056854]

1714056854

[1714056854]

1714056854

[1714056854]

1714056854

[1714056854]

1714056854

[1714056854]

1714056854

[the founder]

that already exists.

[BitterTea]

that already exists.

Not a very informative post. To what are you referring?

[the founder]

there's about 20 services out there that do that.    Google helps ...  I never had any experience with most of them listed,  so I can't vouch for them.

[Maged]

One way this could be done is to pre-generate a transaction that does this, and then toss the private key.

[wareen]

Have a wallet on your own webserver, this server as locked down as possible. Have a button on that server that can only send to one address

(emphasis mine)

that already exists.

I'm not aware of anything that fulfills the OP's requirement of running on your own webserver and more or less being made for that specific purpose - a quick search didn't turn up anything either.
If you could please point me towards one project that facilitates that, I'd be very grateful.

I like the idea very much and think such a thing could be quite useful!

[ctoon6]

One way this could be done is to pre-generate a transaction that does this, and then toss the private key.

thank you for this post, i would never have thought of that

[cbeast]

1. What would happen if payment sent as public/private key pairs?
2. Would then only the change returned require a new transaction?
3. Would a zero confirm transaction suffice when moving?

[giszmo]

so the server would have an interface waiting on http for someone to press a button? with login/password? Guess you don't need a server actually.

how about prepared transactions on your desktop client? so when you run low on your wallet, you send 1 satoshi to an address you know and get 10 bitcoins to your android wallet. With single-use addresses.