aave-v3-core VS bolts

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

True although I'm not talking about Ethereum smart contracts, I'm talking about Bitcoin ones which are very limited and not Turing complete. The lightning smart contract is like 20 lines and has been live since 2018, I feel the probability of the contract getting hacked is very low(famous last words!) https://github.com/lightning/bolts/blob/master/03-transactio...

LN is a protocol for sending signed txns around, keeping track of balances locally, and broadcasting channel open/close/justice txns. All the rules are outlined in the foundational BOLTs https://github.com/lightning/bolts/blob/master/00-introduction.md

BOLT12 offers an attempt to achieve some of the core functionality that LNURL provides without requiring the use of a web server. An offer encodes the data necessary to reach a node to request an invoice to make a payment, either a node_id, or a blinded path (the last few hops in an onion route, pre-computed and encrypted) to that node using onion messages. It also can encode a minimum amount for a payment, the currency being paid in, an expiry time and minimum/maximum quantity numbers (for purchasing multiple items).

In practice, I do not know if this is possible. I am quite unfamiliar with Bitcoin OpCode scripting and if the revocation tree of the channel state (which is just an unpublished Bitcoin contract) is expressive enough to allow inputting an arbitrary address to recieve the attacker's funds. I am attempting to use this documentation as a clue to whether or not, and how this might be possible: https://github.com/lightning/bolts/blob/master/03-transactions.md.

No they can't, that's the whole point of onion routing. The next hop doesn't know if the packet started with you or if you're just another node in the payment path.

Reference: https://github.com/lightning/bolts/blob/master/04-onion-rout...

There is a discussion to add to the lightning BOLT specification for 'inbound fees' which essentially enables a 'rebate' for using a particular channel to route through your node.

Basis Of Lightning Technology BOLT specificiations

tbh i have a text file with definitions of many of these because I constantly confuse them, most of which were pulled from using search at https://github.com/lightning/bolts and similar