Cursor-based API

[dpc]

Each downstream consumer would maintain a cursor, and ask for next blocks using it. The response would contain new cursor. This way multiple unrelated consumers can follow the ledger, without API having to keep track of them.

Canceling protocol should be used, so we will need code converting truncating protocol in the db into canceling one. Should be easy.