Wish List

[n1bor]

This is a wish list of items that I need to complete btc-listener project. Are in order of priority - but exact order is not critical.

1. Interface to a LevelDB Library
2. Binary File operations and seek
3. Crypto operations specifically EC public key cryptography library and RIPEMD160
4. JSON Library - would be nice to have to parse some specific test cases.
5. Logging Library - does not feel right to create my own. Every non-trivial application needs a logging library.

Plus my continuous stream of minor bug fixes to Aver.

I will update as I think of more stuff.

[jasisz]

Your Store is the most charming piece of Aver I have ever seen. Three backends behind one opaque sum, and no caller can tell which one it is holding.

Majority of this list is coming out of the current work on capabilities, and I can already see you are using it extensively, exactly in the manner I imagined. 1) and 3) you closed yourself in three days — I did not hand you a LevelDB or a curve, you declared the contract and put a provider behind it. That is the whole idea.

2. will be the same shape: another contract with a provider, not a library from me. 4) and 5) are Aver code — you are already parsing Bitcoin, so JSON will not scare you, and a logger is a few lines over an effect. There will be no package manager and no "aver-batteries"; capabilities are the mechanism, and everybody gets the same one.

Sorry for all the rough edges, it is still WIP. I read every issue you post and they are extremely valuable. Things may still move a bit before the next release — if a contract changes shape, contract_hash will tell you before anything else does.

But to be honest? I love how it turns out!