website: http://autotip.io/

github: https://github.com/priestc/Autotip

chrome web store: https://chrome.google.com/webstore/detail/autotip/flffaocphcckgaklakkmccbfikneciib

Autotip is a system I created that is an alternate way to monetize content on the web.

Basically its a chrome browser extension that you install, load with BTC, and it will tip out small amounts to each participating page.

I'm just a single developer, Autotip is not a silicon valley play with millions of dollars in VC.

The extension uses shapeshift.io so you can recieve tips in BTC, LTC, DOGE, or any other supported currency.

Right now, Autotip is very young, so there are very few sites that support the protocol. I made a subreddit for posting links to sites that are supported: https://reddit.com/r/Autotip

The difference bwtween Autorip and other tipping services like Changetip is that Autotip is completely decentralized. There is no Autotip account you have to sign uo for. All money moving between tipper and tippee is done peer to peer. The only fee associated with an autotip is the fee to the bitcoin miners.

I'm building a mictotipping platform. The way it works is a chrome extension that works like a wallet sends out transactions to the "tipee".

The problem I'm running into is that when you have an address with a single funding transaction, you're limited to one transaction per block or one transaction every 10 minutes, since you can't use an unconfirmed output in a transaction. You always have to wait until the previous transaction confirms before it can be used in another transaction.

Is there some way to have it so that one wallet can send, say, 25 transactions per minute?

I have no idea if what I just wrote made any sense.

One solution I came up with is to "chop up" any unspent outputs so that you always have a set of confirmed outputs when making a transaction.

So it goes like this:

1. Generate deposit address
2. User sends $10 bucks to deposit address
3. After that transaction confirms, split up the single $10 input into one hundred smaller outputs.
4. Once the chopping transaction confirms, the address will have a ton of unspent outputs and will never be "vapor locked".
5. User sends $0.05 transaction, using one (or multiple) of the chopped outputs
6. 20 seconds later he sends another transaction, using some more of the chopped outputs
7. 20 seconds later... etc. etc.

Does this problem have a name? Has anyone ran into this problem before?

You can see the code here: https://github.com/priestc/Autotip (still in beta)

I'm looking for some kind of API service (like blockr.io) that will return the price of BTC (for any exchange, but preferably Bitstamp or something) at a point in the past.

So I could do something like:

http://some.api.com/get_price?date=[timestamp]

and it would return the price as it was on that timestamp. All the API's that I've been able to find will only return the current price.

I have an idea for a bitcoin wallet system that works like this:

1. You go to a website. Enter you credit card / pay with bitcoin.
2. Once the card has been charged / the transaction confirms, a new VPS instance is created for you.
3. On that VPS instance, bitcoind, nginx, and the CoinSentry software is installed. (basically a django based web wallet)
4. A domain name is set to that VPS instance (something like bob.coinsentry.com)
5. A SSL cert is installed
6. An email is sent to the user when the server has been built giving them their hostname and login details. Also they get the SSH keys so they can ssh into their newly created VPS instance.

Not the user has a hosted wallet running in their own server. Think something like blockchain.info wallet, but running in their own private server. You get the advantage of a hosted wallet, without giving up your private keys.

The user can change the SSH keys which locks out EVERYBODY to that machine.

The downside to this architecture is that you'd have to pay $5 a month to keep the VPS going. But you'd be the only person using that server, so it would be super fast.

Another problem is making sure no one else can get into the VPS server except for the user. Some VPS providers (such as AWS and Digital Ocean) provide an "out of band" console to the instance, which we would need to disable.

What do you all think? Is this something that sounds interesting? Basically the idea is split into two parts: The VPS creator (which is like a single purpose heroku), and the wallet software itself (which I'm calling CoinSentry). I had the idea for a project using a similar architecture (for performance reasons), but realized that this architecture may also work for a bitcoin wallet as well.