---------- Forwarded message ----------
From: chris cook <cojock@hotmail.com>
Date: Fri, Sep 27, 2013 at 1:11 AM
Subject: Ripple Goes Open Source
To:


This is an important development, and correctly recognises:

  • base-less Bitcoin clones (altCoins) are a dead end.

  • chain generation for settlement of open bilateral (P2P) obligations is crucial to decentralised credit creation and clearing (which will be a mobile/tablet financial service).

This presentation 


aims to demonstrate that no currency is technically required to create and clear 'people-based' P2P credit, which is not the same thing at all as P2P debt in respect of existing fiat currency manufactured by the banking system. .

Of course, in order to increase liquidity, generally acceptable currency, whether land-use based (locally fungible); energy-based (generally fungible) or fiat currency (in the meantime), must be available, which involves policy choices in relation to equitable sharing of commons.

However, where I differ from the Ripple guys (I think) is that the framework of trust within which chains can be generated has to be a collective one (the 'Guarantee Society' protocol), rather than routing through individual chains.

Best Regards

Chris



To: rippleusers@googlegroups.com
From: rippleusers@googlegroups.com
Subject: [Ripple] Digest for rippleusers@googlegroups.com - 5 Messages in 1 Topic
Date: Thu, 26 Sep 2013 23:26:19 +0000

Group: http://groups.google.com/group/rippleusers/topics
    Melvin Carvalho <melvincarvalho@gmail.com> Sep 26 02:13PM +0200  


    > I only just noticed this:
     
    > https://github.com/ripple/rippled
     
    > So does this mean that ripple (server) is now fully open sourced?
     
    Official announcement:
     
    https://ripple.com/forum/viewtopic.php?f=2&t=3718&p=18013#p18013
     
    [[
     
    Hey all!
     
    It's my great pleasure to announce the release of the rippled p2p node
    source-code, the code that implements the Ripple protocol and powers the
    Ripple payment network. In conjunction with the open-sourcing we're also
    announcing that OpenCoin Inc. will change its name to Ripple Labs Inc. That
    latter part is mostly because the old name was confusing and required
    explanation. We hope the new name is a bit more self-explanatory - we're
    the place that Ripple came out of and we'll continue to experiment with and
    develop Ripple technology.
     
    For those of you who are less technical, the significance of our
    announcement is that Ripple is not another altcoin. All the protocols and
    data formats have evolved independently of Bitcoin. Our
    consensus<https://ripple.com/wiki/Consensus>process uses peering
    (kinda like the Internet itself) instead of mining.
    The ledger is a data structure that describes the current state of the
    network as a merkle tree (this has the same effect as the merkle tree of
    unspent outputs <https://bitcointalk.org/index.php?topic=21995.0> proposals
    that have come up within the Bitcoin community.) The time between ledgers
    is adaptive <https://ripple.com/wiki/Continuous_Ledger_Close> rather than
    fixed. The current implementation supports holding deposit contracts -
    balances representating currencies other than the native currency. And we
    support the trading of these currencies in the network - as one atomic
    transaction, even across multiple conversions. The Ripple ledger is a
    general purpose data store and we plan to enable you to program the network
    freely via contracts<https://ripple.com/wiki/User:Justmoon/Contracts:_Overview>
    .
     
    It feels weird that it falls upon me to announce the open-sourcing of this
    code, since aside from a tiny fix here or there I wrote none of it. But I
    have worked closely with the people who did and they have completely
    changed my perspective on what's possible. I remember promoting Bitcoin to
    blank stares three years ago and now talking to bitcoiners about Ripple I
    often feel the same way. I hope that over the next year, starting from
    today, we can change that - and you'll be able to see Ripple as we do.
     
    I want to address a few questions that I know will come up:
     
    1. Forks
     
    People will fork the network pretty much instantly (as soon as they can
    figure out our config files [image: :D]), so does that worry me re: job
    security? Of course. But that's the whole point of open-sourcing: It's one
    thing we can do to help keep us honest. I believe as long as we continue to
    live up to our promises, work hard and provide value to users, they will
    continue to use our network. And in doing so they're supporting our effort
    to build out the software and extend the network through any and all means
    available until all XRP are sold or given away.
     
    I don't believe in closed-source, I don't believe in copyright, but I do
    believe in supporting the artists, the developers and entrepreneurs who
    make things happen. We have a growing team of people with big ideas and
    ambitious plans. So please consider using the original network so we can
    continue to develop amazing features and integrate every payment system on
    the face of the planet.
     
    One final request for those planning to fork: If you do fork, please come
    up with a unique name for your network and a different currency code than
    XRP. A little search and replace won't kill you and you'll make life a lot
    easier and less confusing for both our users and your own.
     
     
    2. Decentralization
     
    Whether the code is open-source or not has nothing to do with whether
    Ripple is decentralized or not. As far as the original network is concerned
    we will continue to recommend our own validators for the time being.
    Running the core group of validators lets us close security holes much more
    quickly, which is very important at least until major feature development
    is completed. The last of these major features left is contracts.
     
    So to recap, the general plan is to focus on contracts next and once their
    API is reasonably stable focus on building out the tools and testing needed
    to move to a fully distributed network topology.
     
    That said, we do encourage interested parties to start running validators
    immediately - this is your chance to build a history and reputation as a
    reliable validator so people will later be more likely to add you to their
    UNLs <https://ripple.com/wiki/UNL>.
     
     
    3. Bugs
     
    There will be bugs. If they are security-critical, please consider
    responsible disclosure through bugs@ripple.com. We also have a bounty
    program <https://ripple.com/bug-bounty/> for critical bugs.
     
    ------------------------------------------------------------
     
    Alright, that leaves only one thing.
     
    https://github.com/ripple/rippled/
     
    Go nuts.
     
    ------------------------------------------------------------
     
    Cheers,
     
    Stefan Thomas
    CTO, Ripple Labs Inc.
     
    ]]
     
    Melvin Carvalho <melvincarvalho@gmail.com> Sep 26 03:06PM +0200  


    > seems like it...anyone able to build it?
     
    builds for me! (ubuntu)
     
     
     

--
You received this message because you are subscribed to the Google Groups "Ripple Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rippleusers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



--
P2P Foundation: http://p2pfoundation.net  - http://blog.p2pfoundation.net

Updates: http://twitter.com/mbauwens; http://www.facebook.com/mbauwens

#82 on the (En)Rich list: http://enrichlist.org/the-complete-list/