Title: [ANN] BitcoinProc. A bitcoin implementation for developers. Post by: Anonymous on December 19, 2011, 04:04:05 PM When you are developing a site that processes bitcoin transactions, like an e-wallet, an exchange, or anything else (merchant stuff), you have always had to deal with the limitations of bitcoind. No more! I have developed what I call BitcoinProc. It uses bitcoinj to combine the processing engine and the actual bitcoin client into one executable. This is a huge advantage for the processing engine. The engine provides much more than bitcoind could ever provide:
Javascript engine scripting So the engine provides something really important. You can write javascript that the engine parses and acts on. bitcoin.js is what I call it. This is an example of the javascript that you will be using: Code: //Javascript
The engine will be up for sale within a couple months, and I am aiming for near the end of 1/12. Any feedback? Title: Re: [ANN] BitcoinProc. A bitcoin implementation for developers. Post by: dogisland on December 19, 2011, 06:53:02 PM OK, good luck with this.
I'm the developer of StrongCoin for me to move over to your platform for the server side I would require. 1. Balances for an arbitrary address (not an address in a wallet) 2. Payment information for an arbitrary address i.e. unspent TX outputs in the best chain for an address (So I can create a transaction) 3. Transaction broadcast ability. If I was a vendor selling items on a website I would need. 1. Ability to create a payment address 2. Notification when money arrives at the address. (By callback URL) 3. Ability to verify incoming payment is genuine. 4. For the money to be forwarded to an address in my wallet. For bonus points I'd want it to be deployable to Heroku and be database independent. I'm glad you're going with BitcoinJ you'll find it very easy to work with. Title: Re: [ANN] BitcoinProc. A bitcoin implementation for developers. Post by: Anonymous on December 19, 2011, 07:58:23 PM OK, good luck with this. Response:I'm the developer of StrongCoin for me to move over to your platform for the server side I would require. 1. Balances for an arbitrary address (not an address in a wallet) 2. Payment information for an arbitrary address i.e. unspent TX outputs in the best chain for an address (So I can create a transaction) 3. Transaction broadcast ability. If I was a vendor selling items on a website I would need. 1. Ability to create a payment address 2. Notification when money arrives at the address. (By callback URL) 3. Ability to verify incoming payment is genuine. 4. For the money to be forwarded to an address in my wallet. For bonus points I'd want it to be deployable to Heroku and be database independent. I'm glad you're going with BitcoinJ you'll find it very easy to work with. 1. That is something in the plans 2. I would definitely look into that 3. Very easy 1. A given. A bitcoin.js api 2. I do not understand. Do you want my code to make a post request to a URL. All you would have to do in bitcoin.js is add a line that says to do a http post/get 3. Using the green address standard? I could make an API for that 4. To send from bitcoin.js, trivial. Title: Re: [ANN] BitcoinProc. A bitcoin implementation for developers. Post by: Anonymous on December 19, 2011, 08:03:23 PM I will be adding an API for access to memcached, as that is how bitcoin debit used to work, and how it still works now (with the new owner). Everything can be set from bitcoin.js. I also got the discovery method to be changed via your bitcoin.js (I am now thinking about doing a settings.xml file), ex IRC, DNS, Static, etc...
And I am looking into what heroku is. Could you please explain. Title: Re: [ANN] BitcoinProc. A bitcoin implementation for developers. Post by: Anonymous on December 19, 2011, 08:17:57 PM More bitcoin.js ideas:
Code: btc = new BitcoinHost(); Title: Re: [ANN] BitcoinProc. A bitcoin implementation for developers. Post by: old_engineer on December 22, 2011, 02:26:25 AM My 2 satoshis worth: I suggest that you open source the project, and monetize your investment in time by making yourself available as a consultant to support businesses using your package, either at an hourly support rate, or by offering yearly support contracts.
With a project like Bitcoin, there are a large number of potential users that simply will not use a closed-source project, and you'll make more money and get more users if the project is open-sourced. The first users are alpha/beta testers anyway, and shouldn't have to pay for the privilege of debugging your software. Title: Re: [ANN] BitcoinProc. A bitcoin implementation for developers. Post by: Anonymous on December 22, 2011, 03:13:37 AM My 2 satoshis worth: I suggest that you open source the project, and monetize your investment in time by making yourself available as a consultant to support businesses using your package, either at an hourly support rate, or by offering yearly support contracts. Well of course it would have beta/alpha testers, but closed source is better for me. I have full control that way.With a project like Bitcoin, there are a large number of potential users that simply will not use a closed-source project, and you'll make more money and get more users if the project is open-sourced. The first users are alpha/beta testers anyway, and shouldn't have to pay for the privilege of debugging your software. Title: Re: [ANN] BitcoinProc. A bitcoin implementation for developers. Post by: old_engineer on December 22, 2011, 11:33:55 AM My 2 satoshis worth: I suggest that you open source the project, and monetize your investment in time by making yourself available as a consultant to support businesses using your package, either at an hourly support rate, or by offering yearly support contracts. Well of course it would have beta/alpha testers, but closed source is better for me. I have full control that way.With a project like Bitcoin, there are a large number of potential users that simply will not use a closed-source project, and you'll make more money and get more users if the project is open-sourced. The first users are alpha/beta testers anyway, and shouldn't have to pay for the privilege of debugging your software. |