The leveldb back end adaptor that I wrote does not guarantee ordering.
In theory, chainpad need not depend on messages arriving in order. In practice, we get a "too much recursion" error when searching for a parent hash which does not exist (or which hasn't yet been delivered via websocket).
There are a few ways to fix this, but the simplest is to guarantee ordering from the api.
The leveldb back end adaptor that I wrote does not guarantee ordering.
In theory, chainpad need not depend on messages arriving in order. In practice, we get a "too much recursion" error when searching for a parent hash which does not exist (or which hasn't yet been delivered via websocket).
There are a few ways to fix this, but the simplest is to guarantee ordering from the api.