Dan Connolly

Ah right... well, I lose doing that too (details below). I think I'm getting lost in a maze of twisty docker containers. And that's really beside the point. I should...

My real goal is for people to just check out my project and `npm install`... or perhaps a short list of npm commands. In particular, I'd like nix to get...

OK, using Standard Style does seem to address the ASI hazard. I thought about closing this now, but I prefer to leave it open until a CI check enforces this...

As I start more thorough documentation, some of the warts in the API seem worth fixing. For example, h2b and b2h #54 . I'm not sure I like ethereum norms...

ok, I've got markdown-doctest working for [ed25519verify](https://github.com/dckc/RChain-API/blob/rnode-0.9/docs/index.md#ed25519verify). It pointed out that the example in the README was out of date. :)

I changed my mind about the API again. Top level of [API TOC][toc] now (027aca3) fits in a short list: - RHOCore - RegistryProxy - RevAddress - Ed25519keyPair - RNode...

I wonder about combining RevAddress and SignDeployment into one thing... about REV transactions. Maybe fold Ed25519keyPair in there too.

Status by section as of a6dc377: - [RholangCrypto][] - example, refs **done** - `RegistryProxy` - TODO (#32) - [RNode][] - example, refs **done** - `RHOCore` - _not done_ - `Ed25519keyPair`...

Examples like this suggest the API is getting too "deep": ```js const aliceAddr = REV.RevAddress.fromPublicKey(Hex.decode(alicePub)); assert.equal(aliceAddr.toString(), '11112cFcjtrjwn7qCDvTLMu5jEvMSBN2qT1sBwQxDP9AyQCVi26xKZ'); ``` Maybe it should be more like... ```js const aliceAddr = REV.address(alicePub).toString(); ```

I don't have enough information to address this. Exactly what steps should I take to reproduce the symptoms?