aave-v3-core VS compound-protocol

Pooled assets earn interest in a decentralized non-custodial liquidity market protocol called Aave. You can withdraw your crypto and exit the pool at any time. Note that neither Crypto for Charity nor JustCause will ever have control over your assets so you will always retain custody of your assets.

These are collateralized loans that are automated with "smart" contracts. Programmable money.

Who? Anyone who wants to provide liquidity. Is this different from existing solutions? Yes and no, the difference is that there is no human intervention here... you don't have to ask for permission. You're also dealing with a global pool of funds using open source technology, instead of just a single bank or service.

The only additional "fees" above the interest rate are the cost of a transaction on the block chain. There are certainly a lot fewer hands in the pot and overhead.

Learn more at one of the largest and oldest sites: https://aave.com

> That's a totally valid use case and possible today. The best part is that I don't need any sort of permission to do so. No credit checks. No banks. No government involvement.

Because that is definitely something that regular consumers do and a problem that needs solving.

> In fact, it is so possible, the market for this on a single platform is over $7.8 BILLION. https://aave.com/

What you've just showed me is effectively an actual ponzi scheme all built on nothing with no doubt there is artificial inflation going on there.

The DeFi landscape has witnessed the rise of industry giants like Uniswap and Aave, gaining widespread recognition. However, amidst these prominent platforms, a group of dynamic companies is making significant strides in the Web3 revolution. In this article, we highlight a selection of innovative companies that have caught our attention with their valuable contributions to the DeFi ecosystem. What sets them apart is their compelling approach to directly engage with their communities. Before delving into their unique strategies, let’s explore these remarkable companies in greater detail.

https://aave.com/ is the only real aave.

The AAVE V3 business license expired recently, it's open source now: https://github.com/aave/aave-v3-core/blob/master/LICENSE.md

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.