compound-protocol VS v2-core

https://github.com/compound-finance/compound-protocol/tree/master/contracts/Governance .

I'm making an NFT crowdfunding protocol as a summer project and am using Compound Governance contract along with ERC20Votes to do so.

I highly recommend you do two things, first, try and get a feel for the behavior of smart contracts, there are tools that can help with this, like the ones at blockchain.ey.com - you can get a free personal use account and has a pretty convenient smart contract and token explorer tool for Solidity, you just drop in the code from the protocol’s GitHub (like recommended above) and bam. Here’s Compound’s timelock contract as an example: https://github.com/compound-finance/compound-protocol/blob/master/contracts/Timelock.sol

The Tranquil protocol smart contracts are forked from the Compound protocol with minimal changes. It is a deeply battle-tested and audited protocol with formal verification of its contracts.We plan to get audits for the Tranquil protocol as soon as possible.

Yep however I don't think I'd consider it to quite the same extreme. No doubt it was bad however proportionally to the size of the platform Cream's exploit was far more damaging. Like the rekt.news post mentions, it was more of a banking/spec error than an outright vulnerability. Your spec can't protect you if the loss is due to intended behaviour. There are ways to mitigate this however. The main way is by making your spec concise and clearly representable as a series of state transitions & operations or as a series of transformations.

The Compound Finance paper spec essentially just lists "this subsystem does these things" and then each function/operation is a list of preconditions, what actions are taken in what conditions, and the expected result. This isn't bad per se but it's not great either. Instead the paper spec really should be showing what transformation is being applied to the state, why we want that transformation applied, what properties must hold throughout the transformation, and then demonstrating that those properties hold.

Compare this (Compound):

https://github.com/compound-finance/compound-protocol/blob/m...

Provide alert for 10% or more change in Utilization Rate within a 60 minute window in a given pool.

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