RaiBlocks places transactions in to ledger on an individual basis.  This removes the concept of block intervals, block sizes, and all the other complicated parameters that destroy scalability.

https://raiblocks.net
Follow us on Twitter: @raiblocks

Why RaiBlocks?
No fees: The RaiBlocks network has no notion of fees.
Low latency: Transactions are natively processed instantly giving a responsive experience.
Scalability: Micropayments require a system capable of significant scalability
Simplicity: Users have a simple experience without technical jargon.

Follow on Twitter: @raiblocks



Block lattice whitepaper: https://docs.google.com/document/d/13s6BKzRq9oD5Me55JBRzR7BdvjJ44QKqPu2lf-JsAlU

Spec rationale: https://github.com/clemahieu/raiblocks/wiki/Design-features

Signing algorithm - ED25519
Hashing algorithm - Blake2
Key derivation function - Argon2
Block interval - Instant
UDP message protocol
IPV6 addressing

Translations:
源石币

RaiBlocks has removed the skimmers a.k.a. miners along with the associated fees and has native, instantaneous confirmation.

We're also up for voting for integration on Cryptsy under "RAI", so if you like the conncept, take a second and add a vote https://www.cryptsy.com/coinvotes/#

Wallet and faucet is available on https://raiblocks.net/

I put up a short blurb about a technique we use for mitigating the risk of memory scraping encryption keys.  I haven't seen others do it, we call it a password fan.  Basically we break apart the key in to a thousand or so separate places in memory and only reassemble it when actual signing needs to be done.

https://github.com/clemahieu/raiblocks/wiki/Password-fan

It's trivial to implement, I thought others may want to copy the technique.

Hey everyone, I designed a system which, for lack of a better term, is called a block lattice.

https://github.com/clemahieu/raiblocks/wiki/Block-lattice

The idea is each account in the system has a block chain that is controlled only by them, all chains are replicated to all peers in the network.

The advantage of doing this is each account can order their own transactions meaning no proof besides a digital signature is needed.

I think this goes a long way toward scalability by removing block intervals, mining, transaction fees etc and wondered what everyone thought.

We've been developing a system called RaiBlocks focusing on solving engineering problems of cryptocurrency specifically around transaction speed, eliminating transaction fees, and dropping the energy footprint i.e. removing mining.

Basic information about wallets and faucets are on the main site https://raiblocks.net/  Developer grade details about the block lattice https://github.com/clemahieu/raiblocks/wiki/Block-lattice or other design features https://github.com/clemahieu/raiblocks/wiki/Design-features are on the wiki.

I'd be happy to answer any questions people have.

I’m hoping people would have some feedback on a project I’ve been working on.  The issue I was trying to solve was scalability: transactions per second and confirmation speed.  What I ended up with is a system similar to side-chains except it’s taken to the extreme where each account manages its own chain and all chains are replicated to all nodes.  What happens with this system is there are virtually no distributed agreements because each account has authoritative control over its own chain.  With the account owner having authoritative control over their own chain, transactions don’t need to be mined for validity so confirmation time drops to near zero and transactions speed is as fast as they can be published.

I was looking for some comments, good, bad, indifferent on what people think.

For gritty details I did a writeup here https://github.com/clemahieu/raiblocks/wiki/Block-lattice which includes information about double-spending