First OpenUDC fork: introduction to uCoin project

[Cédric Moreau]

Dear OpenUDC community,

It has been a while now since I first heard of OpenUDC project. Trying to appropriate the concepts in my first steps, I quickly understood I could not be of so much help in OpenUDC development, as I am not at all a C developer, neither could I help in OpenUDC protocol as remaining part of it only depends on jbar's decisions. My last discussion with Galuel on this mailing list helped me to take my own: I couldn't just wait for jbar to develop its own software, I had to try my own way.

This was 6 months ago. Now uCoin project has reached a mature enough step (to me), and I would like to share it with you.

Quickly, and not to pollute any further OpenUDC list with non-OpenUDC related comments, here are main uCoin features, most of them forked from OpenUDC project:

• PGP based
• Monetary Contract
• P2P decentralized and relative database
• Not solving double-spending issue, on purpose

You may find source code and specifications on github, GPLv3 licensed.

Hope this project may receive your (benevolent) critism.

Cédric

[Stéphane Laborde]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Cedric, this is a wonderfull news and looks like a great work !

I will follow and study uCoin for sure, and it will be probably
usefull for OpenUDC itself as well as the concepts developped by
OpenUDC inspires it.

I hope this movement will be followed by new developpers who now can
have more choices with two free softwares projects, and perhaps give
ideas to new ones towards a free money achievement for many men, now
and in the future.

Le 08/01/2014 13:55, C�dric Moreau a �crit :

> Dear OpenUDC community,
>
> It has been a while now since I first heard of OpenUDC project.
> Trying to appropriate the concepts in my first steps, I quickly
> understood I could not be of so much help in OpenUDC development,
> as I am not at all a C developer, neither could I help in OpenUDC
> protocol as remaining part of it only depends on jbar's decisions.
> My last discussion with Galuel on this mailing list helped me to
> take my own: I couldn't just wait for jbar to develop its own
> software, I had to try my own way.
>
> This was 6 months ago. Now uCoin project has reached a mature
> enough step (to me), and I would like to share it with you.
>
> Quickly, and not to pollute any further OpenUDC list with
> non-OpenUDC related comments, here are main uCoin features, most of
> them forked from OpenUDC project:
>

> * PGP based * Monetary Contract * P2P decentralized and relative
> database * Not solving double-spending issue, on purpose

>
> You may find source code and specifications on github

> <https://github.com/c-geek/ucoin>, GPLv3 licensed.

>
> Hope this project may receive your (benevolent) critism.
>

> C�dric
>
> -- OpenUDC aims to provide a open standard for Universal Dividend
> Crypto-Currencies.
>
> homepage: http://openudc.org --- git's home:
> https://github.com/Open-UDC/open-udc.git --- Multi User Chat:
> open...@muc.jappix.com. --- You received this message because you
> are subscribed to the Google Groups "OpenUDC" group. To unsubscribe
> from this group and stop receiving emails from it, send an email to
> openudc+u...@googlegroups.com. For more options, visit
> https://groups.google.com/groups/opt_out.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJSzU0uAAoJELdo2ekCUDkjkuQH/RKrRFGC/jCuzlVcLfEWWs3J
49Lls50zS4EL3reX6w78JFWzTVK9+QIlwrOdQgKcMfOBVlT2XKoAAC0G7FC6BWfC
Jo6xaRXoPWanS9VPS+M+EKcj1wnNciXh6g0F41OVzYvSXqKOu4VD6G5/C23C+vob
03lV7jUziEEY+NmHsr+0RrN+NL+XJe+M1Z45AvHPpXBEAxmle3hdCtlrcVrXhDZl
GTqCnDqlRijy6kq2VBmjtuXUf3Hh2JIMnrEc2SDy9/jy656Qi0Ea8C/oCSmxKWRo
fzrHKFiNF+0x+tWHIdzd6NyvL5bLyhAchdGS4qh8Ze79VnmYzK9ZyzTMKzk5FLo=
=vZMY
-----END PGP SIGNATURE-----

[jbar]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

First congrats Cedric for the amazing job you've done.

Then I think I have to repeat what is this mailing-list for:
This mailing list is for OpenUDC, which aim to be, as the footer say,
an open standard for Universal Dividend Crypto-Currencies.

There are yet still a lot of things to specify, to implement, to test
(and often time to repeat them) until you think we have build the best
we can do for the moment, and then may finalize the specifications.

Some part of the specifications have done all this steps may be
consider as "finalized".

Some other part are really far from that, and need so to pass the steps.

For me Ucoin is still part of OpenUDC project, as it have the same
bases (OpenPGP and HTTP APIs, you seems to agree with the "finalized"
parts of specifications ;-)) and the same aims (to create and exchange a
crypto-currency enabling universal dividend in a decentralized manner).

Like me you are just doing the steps (specify, implement, test,
re-specify, re-implement...) on the parts that need them.

So YOU are also defining an OpenUDC protocol. Remind (or learn) the
history of TCP/IP [1].

That is sad that you miss the 2 last developers meeting, but that is
also great that you have thinking and begin to implement/test some new
ideas.

For example I didn't imagine how we could use a merkle hash tree for
OpenUDC before reading your drafts[2].

There are now great probability than Merkle hash tree we be required in
"mine" OpenUDC protocol.

The most important steps are to implement and test, software designers
which don't also develop or maintain used software(s) often
produce only bullshit.

Now you've got my entire consideration to design what will be know one
day as THE protocol used for universal dividend crypto-currencies.

For sure, the best of our ideas will be merged one day inside a protocol
which will "hold 99% of the market", cf. [1]. And I prefer also working
on that, rather than waiting or building too fast a loosing solution.

I am sure that ucoin and ludd (or their forks) will be compatible one
day (ie run the same protocol), but for the moment we have to play
freely to find what may be the best one.

BTW I hope we will meet again and frequently, to better exchange
and discuss ideas, and make that day arrive sooner.

This mailing list is also the place to discuss about "our" protocol(s).

Feel free to keep announcing here ucoin releases, as I do for ludd,
even if they don't use exactly the same OpenUDC protocol.

NOTE: I tested ur server and it doesn't support yet the
hkp protocol so can't talk with existing softwares using OpenPGP.

[1]:http://en.wikipedia.org/wiki/History_of_the_Internet#Merging_the_networks_and_creating_the_Internet_.281973.E2.80.9390.29
[2]:https://github.com/c-geek/ucoin/blob/master/doc/HTTP_API.md#merkle-urls

On Wed, 08 Jan 2014 14:05:51 +0100
Stéphane Laborde <gal...@glibre.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Cedric, this is a wonderfull news and looks like a great work !
>
> I will follow and study uCoin for sure, and it will be probably
> usefull for OpenUDC itself as well as the concepts developped by
> OpenUDC inspires it.
>
> I hope this movement will be followed by new developpers who now can
> have more choices with two free softwares projects, and perhaps give
> ideas to new ones towards a free money achievement for many men, now
> and in the future.
>

> Le 08/01/2014 13:55, Cédric Moreau a écrit :
> > Dear OpenUDC community,
> >
> > It has been a while now since I first heard of OpenUDC project.
> > Trying to appropriate the concepts in my first steps, I quickly
> > understood I could not be of so much help in OpenUDC development,
> > as I am not at all a C developer, neither could I help in OpenUDC
> > protocol as remaining part of it only depends on jbar's decisions.
> > My last discussion with Galuel on this mailing list helped me to
> > take my own: I couldn't just wait for jbar to develop its own
> > software, I had to try my own way.
> >
> > This was 6 months ago. Now uCoin project has reached a mature
> > enough step (to me), and I would like to share it with you.
> >
> > Quickly, and not to pollute any further OpenUDC list with
> > non-OpenUDC related comments, here are main uCoin features, most of
> > them forked from OpenUDC project:
> >
> > * PGP based * Monetary Contract * P2P decentralized and relative
> > database * Not solving double-spending issue, on purpose
> >
> > You may find source code and specifications on github
> > <https://github.com/c-geek/ucoin>, GPLv3 licensed.
> >
> > Hope this project may receive your (benevolent) critism.
> >

> > Cédric

Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJS0F12AAoJEICx309/5mldP0kH/26Obx2G408y0jemxtEi9nm7
H2NIn/kDS49FFm4/Hi3Tzus+e1iYaD8HimN+Of//QSpwNhZLYJGB6Gp0WLdkRydS
AcI2K6Ohr99Jq5s4PVflaDIowGG7unyycbgM5CnNk8ykgD9b9QzDuxNP4BzpmfIC
dvCg81ZTG+idAPLSMgpllExWzkj6SCSYjzCdspB+L3NDYsx/ZVH6FHkDXrvmtspb
XeMM9mho7Z7wQcpsk0tRJ1W30WgY7XbD2BxNyvirOg1gomI/oTL0B3GBxoPpPnfh
7B2DhATzQ63zpq8ydm9/83uXqRRV3yQEhO+UdO353oppTiIvVZJ3idqq4NePO+E=
=CGvf
-----END PGP SIGNATURE-----

[jbar]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> Le 08/01/2014 13:55, Cédric Moreau a écrit :
> neither could I help in OpenUDC
> > > protocol as remaining part of it only depends on jbar's decisions.

I should have notice that before writing my previous mail, but you make
sad shortcuts.

The remaining parts only depends on implementations and tests, true that
previously I was almost the only one to develop and so the first to
test, but that was before ;-)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJS0GCvAAoJEICx309/5mldFIkH+wa88z/Dre6DSogcmvTp4wUV
NpU+/h0qbUSEduqav/6SjlFVWJaCKIDtk6QCV/M553tKnYgR40OvCEoHI9aL3I5F
uv3fqSMQ3P4qtKLbrqBGpn6LYuHuDfbnNL/GRCiCpEGFaDM5xCU9b5sgV0K8mq4I
Loh5k6PPNB7SHj7BqEb/hPP+DO7Hs6JfBU2EXz1RMXhWUwgEBI1GZ+SEciETZ59m
qCHdy99Zqdugo5tJqHOIpx7Brz6OvVvx2UVoV6sEz91bmz2JN4mLuTjnOv+bVmvr
np5xTzMuvhuefeQuXI8q4evOOXLbtGRdJ0WwYzuUUYYKV8IvmsL1ipThKmcKa5I=
=QYaf
-----END PGP SIGNATURE-----

[Cédric Moreau]

First, thank you jbar for this warming mail. I appreciate, really.

Indeed, we do share the same goals, obviously not trying to reach them exactly the same way.

Actually, I don't think my work deserves so much praises. I don't know what you deeply think of it, but to me what I have done is rather simple, technically speaking. I am just making a puzzle, not at all finished yet. But if it can help us to think differently so we collectively make a good tool, then I will be satisfied.

Anyway, I would be very happy to meet you and others again. I just had to make a break and think my own way.

And for sure I will continue to write on this list, apparently to announce ucoin releases too ;-)

See you next posts!

-----

About hkp, I started to implement it, but finally choosed not to continue. I am currently thinking about it, it might be something I will change. As you say, this is a step by step process.

2014/1/10 jbar <jeanjacqu...@gmail.com>

[Caner Candan]

A very impressive project, will study it ASAP, thanks for your contributions.

Caner

[jbar]

Cedric, I can also patch thttpgpd, so it can serve as a proxy for
node.js.

Then it will handle the required the OpenPGP features :
1- hkp support
2- signing response using multipart/msigned if your app didn't do
it when "asked" by the HTTP client
3- parsing multipart/msigned POST requests to verify signatures
and put the signers fingerprints inside a new extended HTTP header,
for exemple "X-Data-Openpgp-Fprs:"

U will still can do some other OpenPGP related operation by configuring
your app to use the same GnuPG home's dir than thttpgpd.

Putting such features in thttpgd appears for me much more easy than
supporting fastCGI, in fact : the first feature is already fully OK,
and the second one is already implemented and OK for CGI output.
I have also already started implementing things for the third one
features, (the embedded action to update parameter ie creation sheet).