I don't mind dividing it up if people want to do it that way. For example, one guy does the Bitmessage integration, another guy does the Bitcoin integration, etc. We can even parcel out things like the Chrome plugin, Skype plugin, Firefox plugin, etc.
I've got to hit the sack, I'll check back tomorrow.
Topic: Holy Grail BOUNTY - page 13. (Read 36337 times)
I would be happy to host this (and personally help manage it) on CIYAM Open free of charge (http://ciyam.org/open).
Note that CIYAM Open is a system that only locks in *one* dev for an agreed period of time to deliver (and accepted delivery would be determined by a merged git pull request).
If desired this could be divided up into several smaller tasks each of which would be a potion of the *overall* bounty (rather than having the whole thing be a "all or nothing" bounty).
Note that CIYAM Open is a system that only locks in *one* dev for an agreed period of time to deliver (and accepted delivery would be determined by a merged git pull request).
If desired this could be divided up into several smaller tasks each of which would be a potion of the *overall* bounty (rather than having the whole thing be a "all or nothing" bounty).
Is it possible to claim the bounty as reserved/taken while someone works on it? I'm positive I can accomplish this task if I have no stress of completing the job and in the context of possibly not receiving a reward. 
EDIT: the bounty is now up to 81+ BTC
EDIT: "CIYAM Open" has offered to allow us to use their system for free, for the purpose of dividing up the tasks, so I suggest we take them up on that offer. I have posted the project there. Please click here and sign up.
-------------------------------------------------------------------------
Rassah has donated 18 BTC towards this bounty, and Monetas can pledge an additional 18 BTC as well.
So that's a total of 36 BTC so far, not counting any other contributions.
Anyone else wishing to contribute to this bounty, please send the funds to the OT donation address: 1NtTPVVjDsUfDWybS4BwvHpG2pdS9RnYyQ
This application will actually be rather easy to write, as I can provide the code for all the OT functions, and I will be available to support you and answer all your questions. If any changes are necessary inside OT itself, I will code them for you.
If you are interested in collecting this bounty, please contact me at: [email protected]
REQUIREMENTS:
1. Open Source license.
2. The application itself will be a Systray Menu written in QT / C++.
3. When you click on the Systray Icon, it should display this menu:
MENU:
------------------
Overview... (Pops up a list of incoming/outgoing transactions and receipts.)
NOTE: I will provide you the code that generates this data -- you just display it in the GUI.
------------------
Default Nym: Trader Bob ( Click: goes to a list of Nyms where you can add / edit / delete )
Default Server: Digitalis ( Click: goes to a list of Servers where you can add / edit / delete )
------------------------------------------------
gold account: $66,422 (Default account, on server.)
gold cash purse: $40,000 (Cash in local wallet.)
Note: Clicking on the account should pop up a modal dialog for the account.
Note: Clicking on the purse should pop up a modal dialog for the purse.
------------------
Withdraw --> (as Cash or Voucher.)
Deposit -> Paste Cash or Cheque. (Deposit into account or local purse.)
------------------
Send Funds--> Cash, cheque, voucher, or transfer.
Request Payment --> Send an invoice or a payment plan proposal.
------------------
Advanced --->
Agreements (smart contracts)
Markets (offers, trades)
Settings (Settings tab)
------------------------------------------------
Note: In all cases above, I will provide you the code you'll need for the OT portion of any functionality needed above. I will make this super easy for you.
4. The application will also need to provide an HTTP interface so that external applications can send messages to it.
For example, I might have a Firefox plugin that sends a "Withdraw Cash" message to OT through the HTTP interface.
All you have to do when that happens is trigger the same "Withdraw Cash" function from the menu, as if the user had clicked on it.
(FYI, we're going to model the OpenTransact HTTP interface as closely as possible, although we'll adapt it to OT as necessary.)
5. The application will also need to be able to talk to Bitcoin through Bitcoin's HTTP interface.
Not much is required here... basically we just want to be able to verify that bitcoins were received,
and we also want to be able to send a multi-sig transaction. Here's an example of this.
We also want to be able to do this with colored coins, but I won't hold you to it unless the colored coin guys can provide sample code.
6. The application will also need to be able to talk to Bitmessage through Bitmessage's HTTP interface.
Basically we just want to be able to send/receive broadcasts, so that we can wire funds between OT servers,
and have cross-server discovery for trading. The protocol is described here.
Also, here is sample code for using Bitmessage. Easy, right?
We will want to use an abstraction layer here.
As I said, I will be available to support you on your development, and will provide pre-written code that does the OT heavy lifting for you.
EDIT: "CIYAM Open" has offered to allow us to use their system for free, for the purpose of dividing up the tasks, so I suggest we take them up on that offer. I have posted the project there. Please click here and sign up.
-------------------------------------------------------------------------
Rassah has donated 18 BTC towards this bounty, and Monetas can pledge an additional 18 BTC as well.
So that's a total of 36 BTC so far, not counting any other contributions.
Anyone else wishing to contribute to this bounty, please send the funds to the OT donation address: 1NtTPVVjDsUfDWybS4BwvHpG2pdS9RnYyQ
This application will actually be rather easy to write, as I can provide the code for all the OT functions, and I will be available to support you and answer all your questions. If any changes are necessary inside OT itself, I will code them for you.
If you are interested in collecting this bounty, please contact me at: [email protected]
REQUIREMENTS:
1. Open Source license.
2. The application itself will be a Systray Menu written in QT / C++.
3. When you click on the Systray Icon, it should display this menu:
MENU:
------------------
Overview... (Pops up a list of incoming/outgoing transactions and receipts.)
NOTE: I will provide you the code that generates this data -- you just display it in the GUI.
------------------
Default Nym: Trader Bob ( Click: goes to a list of Nyms where you can add / edit / delete )
Default Server: Digitalis ( Click: goes to a list of Servers where you can add / edit / delete )
------------------------------------------------
gold account: $66,422 (Default account, on server.)
gold cash purse: $40,000 (Cash in local wallet.)
Note: Clicking on the account should pop up a modal dialog for the account.
Note: Clicking on the purse should pop up a modal dialog for the purse.
------------------
Withdraw --> (as Cash or Voucher.)
Deposit -> Paste Cash or Cheque. (Deposit into account or local purse.)
------------------
Send Funds--> Cash, cheque, voucher, or transfer.
Request Payment --> Send an invoice or a payment plan proposal.
------------------
Advanced --->
Agreements (smart contracts)
Markets (offers, trades)
Settings (Settings tab)
------------------------------------------------
Note: In all cases above, I will provide you the code you'll need for the OT portion of any functionality needed above. I will make this super easy for you.
4. The application will also need to provide an HTTP interface so that external applications can send messages to it.
For example, I might have a Firefox plugin that sends a "Withdraw Cash" message to OT through the HTTP interface.
All you have to do when that happens is trigger the same "Withdraw Cash" function from the menu, as if the user had clicked on it.
(FYI, we're going to model the OpenTransact HTTP interface as closely as possible, although we'll adapt it to OT as necessary.)
5. The application will also need to be able to talk to Bitcoin through Bitcoin's HTTP interface.
Not much is required here... basically we just want to be able to verify that bitcoins were received,
and we also want to be able to send a multi-sig transaction. Here's an example of this.
We also want to be able to do this with colored coins, but I won't hold you to it unless the colored coin guys can provide sample code.
6. The application will also need to be able to talk to Bitmessage through Bitmessage's HTTP interface.
Basically we just want to be able to send/receive broadcasts, so that we can wire funds between OT servers,
and have cross-server discovery for trading. The protocol is described here.
Also, here is sample code for using Bitmessage. Easy, right?
We will want to use an abstraction layer here.
As I said, I will be available to support you on your development, and will provide pre-written code that does the OT heavy lifting for you.
Jump to: