I don't think Bitcoin's SHA2-256 + RIPEMD-160 usage is based on sound crypto. It's not terrible but it's also a little bit silly since a collision in SHA2-256 will be a collision in the pair, which means all you're doing is shortening the hash while avoiding the length extension attack. There are also potential weaknesses in the pair that may not exist in either one due to the fact that the pairing has not been well studied. You could accomplish the same end with less CPU and less code by using a truncated SHA-512 hash.
Otherwise, I tend to agree with your goals and approach, though I think it may be more impactful to simply bring the decentralized identity aspect of it to the web. The fact that I have no portable identity with which to comment on or post arbitrary content around the web is very annoying. At best, the current system could be described as federated, but even that's not entirely true since few sites actually support OpenID and fewer users know what their OpenID URL is. On Mon, Sep 23, 2013 at 9:48 PM, Liam Edwards-Playne < [email protected]> wrote: > I've been working on a new open micropublishing network that's entirely > peer-to-peer, relying on a publish-subscribe overlay to facilitate scalable > distribution of messages on hashtags, profiles and threads. > > You can peruse its design in this document: > http://bitweav.org/whitepaper.**pdf <http://bitweav.org/whitepaper.pdf> > > Its main features: > - first of its kind to support publish/subscribe to topics (profiles, > hashtags, threads) > - doesn't use rendez-vous nodes for topics (meaning only nodes who are > subscribed to a topic will help distribute messages on it) > - message threading and replies. multilingual support. > - more scalable approach to message dissemination using rings, rather > than gossip-based flooding (see ch. 7 of whitepaper) > > I'd appreciate any constructive criticism / discussion and if anyone would > like to help I would greatly appreciate it. I'm currently developing the > frontend graphical client, afterwhich I will progress to implementing the > backend daemon. > > Cheers, > Liam Edwards-Playne. > ______________________________**_________________ > p2p-hackers mailing list > [email protected] > http://lists.zooko.com/**mailman/listinfo/p2p-hackers<http://lists.zooko.com/mailman/listinfo/p2p-hackers> >
_______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
