v2-core VS big.js

For source code, Uniswap V2 Core and Uniswap V2 Peripheral

Here is the Uniswap V2 on github: https://github.com/Uniswap/v2-core

Eh, Curve pools and other invariant-based AMMs have some interesting properties outside traditional finance, bank runs, etc.

I'd read up on the Uniswap constant product invariant (xy=k) and consider reading the Uniswap v2 code (it's a pleasure to read) [0].

Then check out the StableSwap paper by Curve founder Michael Egorov [1]

Finally if you want a well-documented implementation to read in Solidity, check out Saddle [2]. Disclaimer, I helped write the first iteration.

[0] https://github.com/Uniswap/v2-core

UniswapV2Pair.sol：https://github.com/Uniswap/v2-core/blob/master/contracts/UniswapV2Pair.sol

Any of those above functions that have require statements could have triggered it. I guess that is why you suggested the "hardhats console log". I am not familiar with that and will get right on trying to get that to work. Sorry for slow response, it seems since your message I have went all up and down the entire uniswap code database that includes the router, pair, libraries, transferhelper, WETH, etc.... So I just had the most extensive crash course I have ever had. hahahaha... Thanks for pointing me in that direction. I have learned A LOT. Though I still haven't figured out why the error is happening so I will now try using the hardhats console log to debug it.

The function comes from UniswapV2Pair.sol, shown here:

For example Uniswap has 0 releases

ii) Third-Party Libraries There are various libraries like math.js, decimal.js, big.js that solve the problem. Each library functions according to its documentation. This approach is comparatively better.

For financial applications, APIs commonly return currency values, balances, stock/currency positions, and other amounts as strings. The best way I've found to deal with this is to use a library like big.js.

Just for fun, using javascript library:

Another different approach maybe to have the money represented in the decimal in your database at the decimal places of the currency with the highest decimal point you are going to be dealing with for example using Decimal(n, 2) in case of fiat, and perform your calculations in arbitrary-precision Decimal type. In javascript, using libraries like Big.js , Decimal.js will be of help.

With that said, using a library like big.js will solve both this and the potentially unsafe eval use:

It will explain this weird behavior. You have to use a special lib for precise floating point math. Here is one: big.js.