| The RAIblocks whitepaper is worth reading just as a reference on how a technical paper should be written. (Disclosure: I became interested in RAI on NYE and recently invested some money in it) The RAI secret sauce is the "block lattice" design where each account is its own blockchain and you only need to care about the chains you want to do business with, unless you encounter conflicts. Conflicts are resolved by proof-of-stake voting. If you don't run a full node, you choose a representative to vote on your behalf. Today I spent the afternoon playing around with a conceptual design in ClojureScript for a better desktop wallet: http://petrustheron.com/posts/xrb-wallet-concept/ From a contrarian investor point-of-view, RAIBlocks is interesting because it is at the juncture of a terrible wallet experience, a weird name, dubious exchanges (at least UI wise), an okay website - but an excellent whitepaper and a working protocol that's free to transact on. If it scales, I predict it will do well. My biggest concern is C++ as an implementation language, compared to, say OCaml that is easier to verify. I also don't have a strong feel for the robustness of the conflict resolution mechanism. However, the author is proficient and the codebase is readable. The closest DAG impl. AFAIC, is Hashgraph, based on supermajority consensus that counts transactions that were "strongly witnessed", but it is patented with no coin presently for sale. |