Topic: Holy Grail BOUNTY - page 4. (Read 36328 times)
You guys kick ass! Thanks for the update!
There are many contributors who I'm sure want a quick UPDATE on status, and we're making LOTS of EXCITING PROGRESS!
------------------------------------------------------------------------
First, here are the main project tasks as posted on the "Ciyam Open" project management site:
Systray GUI with OT integration General UI BTC: 10.000
Namecoin integration (credentials) Integration BTC: 7.500
HTTP Interface General UI BTC: 8.000
Colored coins integration Integration BTC: 10.000
Bitmessage integration Integration BTC: 11.000
Bitcoin Integration (Multisig) Integration BTC: 10.000
Internationalization General UI BTC: 5.000
Integration with legacy banking Integration BTC: 12.000
Markets UI General UI BTC: 7.000
------------------------------------------------------------------------
LATEST STATUS ON TASKS:
-------------------------------------------------
Systray GUI with OT integration General UI BTC: 10.000
Since Xenland stopped working on this, I have taken over personally, courtesy of Monetas.
I'm nearly done! It's working great, and I will be posting a video really soon!
For those who have seen the iPhone video already, the functionality is basically the same, except more powerful. The UI is very similar and looks great... finally a real UI people can use for OT! Hopefully we can start making an official install program soon.
Here's my commit history:
https://github.com/Open-Transactions/Moneychanger/commits/master
===> Once this task is completed (video coming soon) I will split the bounty between myself and Xenland, based on the difference in code.
===> I will not keep my share of the bounty, but will re-distribute it among the existing tasks of the project.
-------------------------------------------------
Namecoin integration (credentials) Integration BTC: 7.500
The purpose of this integration is to allow us to eliminate Certificate Authorities, by making revokable OT credentials through Namecoin. (And to support other credential systems as well, with Namecoin just being the first one integrated.)
There's a developer working on this Namecoin integration, and I've been in regular contact with him -- he's progressing rapidly.
We are near the point now of adding it to the UI with full-functionality!
On Sept 17th, the developer wrote:
Quote
just a quick status update from my work on the Namecoin integration, in case you are interested.
I've now mostly finished a first version of libnmcrpc, which I'll use to communicate to Namecoin.
The code can be found at https://gitorious.org/libnmcrpc and already supports wallet unlocking,
querying of Namecoin names, signing and verifying messages and name registration
including semi-automatic handling of name_new/name_firstupdate,
although I still have some things to polish there.
I've now mostly finished a first version of libnmcrpc, which I'll use to communicate to Namecoin.
The code can be found at https://gitorious.org/libnmcrpc and already supports wallet unlocking,
querying of Namecoin names, signing and verifying messages and name registration
including semi-automatic handling of name_new/name_firstupdate,
although I still have some things to polish there.
On October 5th, he wrote:
Quote
I've already registered some names with my code and am working on finishing code to handle
multiple name registration processes conveniently (possibly in different "stages" of name_new / name_firstupdate
and waiting for confirmations.)
multiple name registration processes conveniently (possibly in different "stages" of name_new / name_firstupdate
and waiting for confirmations.)
On October 16th, he wrote:
Quote
I've finished the work (at least for now) on the base Namecoin library, it
now supports registering and managing the registration processes of
multiple names. It also includes a command-line utility that can be
used to register names and watch the registration processes including
"automatic" name_new / name_firstupdate, and I already used it
successfully to register some names for myself.
now supports registering and managing the registration processes of
multiple names. It also includes a command-line utility that can be
used to register names and watch the registration processes including
"automatic" name_new / name_firstupdate, and I already used it
successfully to register some names for myself.
On October 18th, he wrote:
Quote
I'm also implementing a method with the signature:
Quote
virtual bool VerifyCredentialHashAtSource(hash, source);
===> The best part of this is that Namecoin is just an example of the kinds of credentials OT will now be able to support!
===> OT also supports self-signed credentials, as well as CA-based certs (through OpenSSL.)
===> Since this is implemented through an abstract interface, it will be trivial to support other identification systems, such as GPG web-of-trust, BitShares' BitIDs, Retroshare, etc.
-------------------------------------------------
HTTP Interface General UI BTC: 8.000
No one is working on this one yet, but now that basic functionality is nearly done, it shouldn't be hard to add an HTTP interface on a local loopback address.
This will enable many other applications to integrate, including web apps.
-------------------------------------------------
Bitcoin Integration (Multisig) Integration BTC: 10.000
JaSK has been kicking ass on the Bitcoin integration! He's got multi-sig coded!
On October 8th, he wrote:
Quote
We can now verify that certain transactions have been made (if we have the tx id) so my next step is to implement the actual escrow protocol.
His commit history on October 21st says:
Quote
ESCROW MOTHERFUCKING WORKS THEORETICALLY - Added all missing functions required for receiving, verifying, creating, signing and sending to and from p2sh addresses and tested them successfully in a simple 2-of-2-escrow.
A lot more testing needs to be done and there are still some things I need to check to make sure noone gets scammed but all major issues are out of the way.
In the next commits I will do some cleaning up and commenting, create some helper functions and structures to hold information about the current state of outstanding escrow transactions and add GUI items so more people can start testing how well it actually works.
A lot more testing needs to be done and there are still some things I need to check to make sure noone gets scammed but all major issues are out of the way.
In the next commits I will do some cleaning up and commenting, create some helper functions and structures to hold information about the current state of outstanding escrow transactions and add GUI items so more people can start testing how well it actually works.
See his commit history:
https://github.com/tuttleorbuttle/Moneychanger/commits/master
TL;DR: This means we are finally going to have multi-sig voting pools on OT! (These will enable an OT server to process Bitcoin transactions, without having to trust that OT server with your Bitcoins.)
(I mean frankly, isn't everyone in the Bitcoin community tired of having to trust all the various servers out there with their coins?)
JaSK recently asked:
Quote
we can probably automate part of that process by communicating over bitmessage or direct p2p connections.
But that will take more time and I'll have to ask FellowTraveler how he'd like it to be done.
But that will take more time and I'll have to ask FellowTraveler how he'd like it to be done.
The answer is: When a user wishes to move Bitcoins into OT, he will be sending the coins multi-sig, using your code as described above. As long as I am able to send and verify those coins, and as long as I am able to perform multi-sig votes to remove those coins back out, then I will be able to do the rest on the OT side. Bitmessage will not be needed for this, but if you want to get started on the Bitmessage integration, it's definitely needed for other pieces.
-------------------------------------------------
Integration with legacy banking Integration BTC: 12.000
As you guys know, we have a 12 BTC bounty on implementing this protocol for p2p transfer of funds in/out of legacy banking systems:
http://pastebin.com/SsLrxVP6
The protocol requires the use of smart contracts for dispute resolution inside OT (which OT is able to do) but it also involves integration with legacy systems.
Fortunately, people have been working on the integration, and there is now alpha software ready for testing!
See this thread:
https://bitcointalksearch.org/topic/m.3429555
The next step is to integrate this (through an abstract interface) into the new GUI, and use OT smart contracts for escrow and dispute resolution.
The abstract interface will allow us to swap in alternate solutions as well, so we are not reliant on any one. But I have to say, it looks like these guys have done some great work so far.
-------------------------------------------------
Colored coins integration Integration BTC: 10.000
Not yet started.
We'll use an abstract interface here so we can handle disparate systems such as colored coins, master coins, bitshares, etc.
(OT strives to be agnostic on this sort of thing.)
BTW, we are also integrating with Project Praesto by ninjabanker, which is another system for providing fiat in/out, which uses Bitcoin reserves in order to eliminate the need for an "issuer" entity (normally trusted to hold the reserves in dollars / euros / etc)
I'm really excited about this solution, since it will take advantage of OT-based virtual corporations and of course, since it enables us to eliminate the issuer.
-------------------------------------------------
Bitmessage integration Integration BTC: 11.000
The original purposes of this integration:
1. Server-to-server wiring of funds.
2. Distributed exchange.
3. Integration with legacy banking.
Well, a great new benefit is being added to the pile:
4. Distributed bazaar. (Like E-Bay, except without the server.)
I realized a few weeks ago how easy this would be to add, using the same Bitmessage integration we already had planned.
So I worked out the UI with Yamamushi's help, and have started adding it to the GUI app.
This bazaar will not be functional until the Bitmessage integration is ready, but I do expect to have it all working soon.
-------------------------------------------------
Internationalization General UI BTC: 0.000
The Subtask in Ciyam Open appears to show a zero balance, but rest assured, a contributor put 5 BTC towards Internationalization, but the money is in the top-level wallet so it's showing incorrectly as a zero on the subtask. But the 5 BTC is really there, so if anyone wants to consider Internationalization of this project, there's a good reward waiting for you.
Update: Internationalization work has begun! See this commit history from one of our contributors:
https://github.com/Open-Transactions/Moneychanger/commit/023b0a0a649e7023d2c7dc10c9c8a3c692c97227
-------------------------------------------------
Markets UI General UI Open 7.000
Yamamushi is working on this page but I'm not sure of his current status. I will probably sync up with him sometime this week.
-------------------------------------------------
I will update the Ciyam Open project soon, once I have the video ready showing off the new GUI. (I hope to record one this week.)
Also please note that http://ciyam.org has had a complete design rework.
We are keen to continue working with the Moneychanger project and encourage skilled devs to sign up.
We are keen to continue working with the Moneychanger project and encourage skilled devs to sign up.
As you can see in my git history I managed to implement most of the required bitcoin api calls.
We can now verify that certain transactions have been made (if we have the tx id) so my next step is to implement the actual escrow protocol.
Iirc that requires just three more api functions (create-, sign- and sendrawtransaction) which shouldn't be difficult and some GUI elements and buttons.
At the beginning this won't be very comfortable to use (addresses and tx ids will have to be shared and typed in manually) but we can probably automate part of that process by communicating over bitmessage or direct p2p connections. But that will take more time and I'll have to ask FellowTraveler how he'd like it to be done.
We can now verify that certain transactions have been made (if we have the tx id) so my next step is to implement the actual escrow protocol.
Iirc that requires just three more api functions (create-, sign- and sendrawtransaction) which shouldn't be difficult and some GUI elements and buttons.
At the beginning this won't be very comfortable to use (addresses and tx ids will have to be shared and typed in manually) but we can probably automate part of that process by communicating over bitmessage or direct p2p connections. But that will take more time and I'll have to ask FellowTraveler how he'd like it to be done.
Any news?
There is a somewhat similar project by now: https://bitcointalksearch.org/topic/announce-zero-reserve-a-distributed-bitcoin-exchange-295930 (Zeroreserve, a Retroshare based Ripple Clone with BTC instead of XRP). Maybe there are some synergies to make use of...
There is a somewhat similar project by now: https://bitcointalksearch.org/topic/announce-zero-reserve-a-distributed-bitcoin-exchange-295930 (Zeroreserve, a Retroshare based Ripple Clone with BTC instead of XRP). Maybe there are some synergies to make use of...
Yes, I meant ian, sorry.
In Germany we spell it jan but pronounce it ian so my subconsciousness must've mixed that up :p
Thanks for fixing the issue, I also think one active bid per task would probably be best.
In Germany we spell it jan but pronounce it ian so my subconsciousness must've mixed that up :p
Thanks for fixing the issue, I also think one active bid per task would probably be best.
Am guessing by @jan you meant @ian and so have now deleted all the rejected bids for the Moneychanger project (allowing yourself and Xenland to bid any of the tasks again).
Although generally one bid per task makes sense this scenario wasn't one I had actually considered and so will give it some thought (maybe the limit should just be for one *active* bid per task).
Although generally one bid per task makes sense this scenario wasn't one I had actually considered and so will give it some thought (maybe the limit should just be for one *active* bid per task).
I'm currently implementing the multi-sig-functionality, guess I'll get that done over the weekend, GUI elements will follow next week.
@fellowtraveler and @jan
I think I can't place a new bid for the re-opened tasks on CIYAM because one can only apply once, so can you please enable them again for me?
I'm making good progress with Bitcoin Integration (when I find time to work on it), Bitmessage is something someone else can work on but if nobody will I'll do it next.
@fellowtraveler and @jan
I think I can't place a new bid for the re-opened tasks on CIYAM because one can only apply once, so can you please enable them again for me?
I'm making good progress with Bitcoin Integration (when I find time to work on it), Bitmessage is something someone else can work on but if nobody will I'll do it next.
Whom ever finishes the Basic GUI task could be so kind as to splitting up the reward based on code usage if they decide to use all or part of my code. Much would be appreciated 
Glad to hear.
I would like to suggest opening a CIYAM sub-task for translating the interface.
I've already said I'll translate it to portuguese.
It think it will help organizing the tasks and and distributing the tasks earlier will help to finish it earlier.
For most of the languages, probably bounties will not be necessary, but if someone wants to donate for the translation to any language that's not there, latin, klingon, elvish, russian, japanese, etc, etc, it would be welcome.
I would like to suggest opening a CIYAM sub-task for translating the interface.
I've already said I'll translate it to portuguese.
It think it will help organizing the tasks and and distributing the tasks earlier will help to finish it earlier.
For most of the languages, probably bounties will not be necessary, but if someone wants to donate for the translation to any language that's not there, latin, klingon, elvish, russian, japanese, etc, etc, it would be welcome.
Hi all!
Time for an update on this project (the tasks are viewable here: http://ciyam.org/open/?cmd=view&data=20130606055250338000&ident=M100V137&chksum=a2a9d6d5 )
----------------------------------------
First off, Xenland has done an excellent job creating a QT systray project that integrates with the OT API. (Xenland has already posted screenshots.) It is able to successfully make OT API calls, and it's got menus and some dialogs, but it's nowhere near complete.
You can see the project here: https://github.com/Open-Transactions/Moneychanger
Unfortunately Xenland said recently that he wouldn't be able to work on it for at least the next month, as he has real life things he has to prioritize.
As the last review date was a month or two ago, we're re-opened the task for bidding so we can get it moving again. Any QT experts interested? As always, I will be available to support you and provide whatever you need on the OT side.
----------------------------------------
Secondly, the code in Xenland's app that actually "drives OT" has been completed by myself, since at Monetas we had to use it in our iPhone app. (And we'll be using it in our Android app as well.)
So you can see that code working now in our iPhone demo videos:
introduction: http://goo.gl/8Dxak1
advanced: http://goo.gl/u6xqHc
----------------------------------------
Third, you may notice each individual task has a bounty associated with it. So if you want to donate to the effort, please donate only to the address associated with the INDIVIDUAL TASK you are supporting, and not to any other BTC address (such as the addresses appearing for the overall "Moneychanger" project or the "General UI" or "Integration" categories.) This way the amount will update for your individual task, and that will help incentivize coders to take on those tasks.
----------------------------------------
Fourth, the "Internationalization" task has a 5 BTC donation, but it appears as a "0.0" -- This is because it was donated to the main address instead of to the individual "Internationalization" task (which was my fault.) So at some point soon I'll be re-arranging the funds to get the 5 BTC to appear on that task.
----------------------------------------
Fifth, OT contributor randy-waterhouse has figured out the proper protocol for using Namecoin for OT credentials, which is viewable here: http://opentransactions.org/forum/index.php?topic=10.msg40#msg40
I've been contacted by a potential Namecoin integrator and so hopefully we'll be able to get that task assigned to him ASAP.
----------------------------------------
That's it for now!
Quote
Quote
Quote from: Bronzetank on August 20, 2013, 09:57:37 PM
Is it just me or does it seem like the videos cut off early? Is there a part 2 for either of these?
Awesome stuff FT! Really looking forward to future updates.
Is it just me or does it seem like the videos cut off early? Is there a part 2 for either of these?
Awesome stuff FT! Really looking forward to future updates.
Did you DOWNLOAD the videos?
If not, then the problem is probably not the videos themselves, but the Dropbox video player. (Had lots of similar comments.)
Thanks...download worked fine. I didn't know there were issues with Dropbox video player.
iam a yound professional graphic & web designer. love the idea behind ... if you need help on any design tasks pls let me know ...
looking forward heargin from you
looking forward heargin from you
How are transaction fees applied in this app?
Currently there are only Usage Fees -- meaning (if they are turned on) the server charges one "usage credit" per API call. The server operator has the ability to "re-up" your usage credits.
There is, of course, great demand for transaction fees from server operators, which charge some small percentage of the transaction itself. We haven't added this yet, but it's coming.
When that is implemented, it will have to be based on rules in the server contract, so that the client software can properly form the transaction request to include that fee. (The server can only verify/countersign your transaction requests, which prevents it from forging receipts, since it cannot forge your signature.)
Here are the new videos of the Monetas iPhone app
How are transaction fees applied in this app? Is it just me or does it seem like the videos cut off early? Is there a part 2 for either of these?
Awesome stuff FT! Really looking forward to future updates.
Awesome stuff FT! Really looking forward to future updates.
Did you DOWNLOAD the videos?
If not, then the problem is probably not the videos themselves, but the Dropbox video player. (Had lots of similar comments.)
Great thanks ft, I'm going back to work on the taskses I've claimed. Shouldn't be long now
Quote
Here are the new videos of the Monetas iPhone app:
Intro video: https://www.dropbox.com/s/cotk860n3e49kpn/monetas_iPhone_intro_HD.mp4
Advanced video: https://www.dropbox.com/s/uz1cgcj5j3kd3ds/monetas_advanced_iPhone_HD.mp4
Intro video: https://www.dropbox.com/s/cotk860n3e49kpn/monetas_iPhone_intro_HD.mp4
Advanced video: https://www.dropbox.com/s/uz1cgcj5j3kd3ds/monetas_advanced_iPhone_HD.mp4
Is it just me or does it seem like the videos cut off early? Is there a part 2 for either of these?
Awesome stuff FT! Really looking forward to future updates.
How much of a bounty to get this onto an Android?
Intro video -- Monetas iPhone app: https://www.dropbox.com/s/cotk860n3e49kpn/monetas_iPhone_intro_HD.mp4
This app does a lot more than you see in the video, which is meant to show basic functionality.
I'm recording an "advanced" video tonight and will post a link soon.
P.S. most of the code in this app is being re-used in the Android app as well as the "Holy Grail" project.
This app does a lot more than you see in the video, which is meant to show basic functionality.
I'm recording an "advanced" video tonight and will post a link soon.
P.S. most of the code in this app is being re-used in the Android app as well as the "Holy Grail" project.
It's an ongoing project. But bounties are always welcome xD
How much of a bounty to get this onto an Android?
Jump to: