Re: [Ripple-protocol] New Bitcoin-inspired ideas

[Jorge T. <tim...@gm...>]

Not sure, but it seems you're talking about path discovery. The issue
registers solve is transaction atomicity (and the possible attack of
locking intermediaries credit with fake transactions that never commit
?).

2011/5/24, Stephen Paul Weber <sin...@si...>:
> Somebody claiming to be Ryan Fugger wrote:
>>On Tue, May 24, 2011 at 2:57 AM, Jiri Baum <ji...@ba...> wrote:
>>> Hmm, again I was skimming rather quickly, but my first impression is that
>>>
>>> the
>>> registries would become central points of trust... and Ripple design
>>> should
>>> probably avoid that.
>>
>>Unfortunately, it is necessary for transaction atomicity.  I've
>>discussed the dangers of registries abusing their powers here (near
>>the bottom of the message):
>
> I'm sure this has been discussed countless times: but what's wrong with just
> using OSPF or even simpler stuff?  Like, node A knows about some
> connections, builds them and broadcasts to nodes reachable from account A1,
> those nodes do the same (with broadcast path being kept to prevent flooding
> and such) and eventually after some TTL the request comes back with either a
> match or "no match withing that TTL" (where TTL is probably a number of
> hops).
>
> --
> Stephen Paul Weber, @singpolyma
> See <http://singpolyma.net> for how I prefer to be contacted
> edition right joseph
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Ripple-protocol mailing list
> Rip...@li...
> https://lists.sourceforge.net/lists/listinfo/ripple-protocol
>