Will

i think we purposefully scoped block positioning out of this interface for simplicity - the primary purpose here is dapps, not analytics / full exposure of the complexity.

auth plugins the developer writes may also inspect the http request as a way of conveying other information about the requesting user. as such, i don't think we need to...

can we synchronize through the database directly?

if it lives in a custom auth plugin, i'd guess it could be a part we don't release / stays internal to our deployment

yeah, a separate private repo seems reasonable. i'll put together a PR for how they'd link

I thought this was a soft wallet bug? https://github.com/ethereum/web3.js/blob/v1.0.0-beta.37/packages/web3-eth-accounts/src/index.js#L148

it looks like the issue here is that `websocket` failed to build during `npm install`. I see ``` [email protected] └ [email protected] (git://github.com/frozeman/WebSocket-Node.git#6c72925e3f8aaaea8dc8450f97627e85263999f2) ``` the websocket module does have a native...

can we skip generation from mnemonic entirely, and use a private key directly? On Wed, Jun 12, 2019 at 2:20 PM david-yan wrote: > We need to decide on and...

I think mostly just trying to understand what's the minimum we can do for MVP the problems i see with mnemonic is that it's another whole protocol for synchronization where...

cc @armaniferrante - https://github.com/oasislabs/web3c.js/pull/138 should have introduced support for subscriptions