OliverNChalk

Well, without fees you can pass the sqrt of the invariant to the contract and save a good portion of the gas costs. That said, I don't think the same...

I implemented this and tested i with variable fees, it appears holds true for all fees < 49.99%. I will probably implement a wrapper contract for Uniswap and do some...

I'm fairly certain that tokenToToken charges the fees twice (each reserve takes a 0.3% cut). Also, if this is on the front-end, is it not possible to simply call tokenToToken...

I can't remember exactly anymore, did this link help (https://devblogs.microsoft.com/typescript/announcing-typescript-4-4/#exact-optional-property-types)

The example is still broken 1.5 years later

How many sockets are you using? The request socket is sequential in its sends (`await client.send` actually waits for the response, not just the send). So to me, your example...

Using your examples I get the following results: `20160.827192609595 ops/s zeromq 496.0113940000301 ms, 42.36328125 MB memory` `41917.7431192103 ops/s net module 238.56246199994348 ms, 41.078125 MB memory`

- OS: Ubuntu 20.04 - ZeroMQ.js version: 6.0.0-beta.6 - Node 14.4.0