Will

looks like we have `web3c.oasis.subscribe`, but maybe the missing link is on `web3c.oasis.contract`

looks like they've refactored quite a bit. no concept of request manager anymore. i'll take a look at what needs to change.

eventually we'll need to support the newer setup in recognition that a non-beta web3 will come out eventually :) On Sun, Jan 27, 2019 at 8:27 PM Armani Ferrante wrote:...

better pinned in v1.0.4 as a temporary bandaid

web3c is up to beta 46. api doesn't appear to be breaking too much in the couple recent updates

`new Buffer()` gets used in crypto/node/siv_ctr.js test/siv_ctr.js i think the main reason the old api was nice is for the tests where it can auto-convert base64 data back into a...

The semantics of sendBatch is the clients saying "i want these operations to happen in this order". if they are sent as independent web3 calls, there's a potential for re-ordering,...

does assigning this to me mean i should start this process?

We have now * trialed an alpha release on GitHub, * setup team ownership for https://www.npmjs.com/package/web3c * setup CI to maintain a 'latest' CDN staging * pretty URL for hosted...

is this an issue with the web3c library? I guess the issue is that the name of the event `Transfer` is meant to be confidential, so we should expect a...