Uses Compound, Aave, MakerDAO, and bZx as lending providers, Aave flash loans for leverage, 1split.eth as the on-chain dex aggregator, and ChainLink oracles for price verification.
Monitors mempool for unauthorized transfers from wallets and sends a competing transaction at a higher gas price to divert funds into a rescue wallet. Uses a signed EIP712 permission token to execute recovery.
Patreon built on an out-of-the-box tokenized bonding curve. Fans purchase an artist's token and gain access to exclusive content. Artists take a fee on every token purchase/sale.
13/ MetaCredits - Donate gas for meta transactions
A benefactor can deploy a MetaCredit DappFunder smart contract for a dapp, deposits funds in the contract, and grants the developer permission to use funds to pay for his and his user’s gas fees.
1/ Verifiable Compute is as important of a technological revolution as blockchain itself.
I've written a piece on the tech, including:
- an overview & history
- an outline of the use-cases
- a framework for evaluating verifiable compute projects
2/ Verifiable Compute allows external parties to run computations on your behalf while providing assurances around the validity of the computation’s inputs, outputs, and methods used.
It encompasses various cryptographic techniques for ensuring computational integrity.
3/ While blockchains provide economically-guaranteed integrity by having multiple untrusted machines re-execute the same program to agree on the end state, verifiable compute provides mathematically-guaranteed integrity by proving that some end state is the result of a set of inputs into some program.
1/ Most people think about a (blockchain) bridge as a monolithic piece of software or a set of smart contracts, but @arjunbhuptani elegantly breaks down the concept into a modular framework.
Here's what happens under the hood when you relay a message across chains:
2/ Transport: You take data from a source chain and post it to a destination chain.
This can happen using any relayer network.
This can also happen using native rollup bridges (i.e. the sequencer).
This part of the stack is highly commoditized since it's easy to implement.
3/ Message verification: Answers the question of "How do I know that some message that went across chains is correct?"
This is the main job of a bridge and how we classify them today (e.g. validator sets, light clients).
SNARKing chain consensus is probably the end game.
Simply put, an AppChain is a blockchain that dedicates its blockspace to a specific application.
Importantly, they *do not* only refer to monolithic L1s because "layers" are mostly just trust-minimized blockchains w/ two-way trust-minimized bridges.
3/ AppChains as a concept have been in the making since 2016 but have evolved and accelerated since 2020.
1/ Market timing is arguably the most important factor that determines the success of a company.
Here are three mental models for determining whether it is the right time for what you're building:
- Prior failures
- Ingredients for success
- Awareness & acuteness of pain
2/ Prior failures:
- Who else has tried something similar to what you're building and failed?
- Why did they fail (e.g. competition? no demand? bad UX)?
- Have those reasons been solved by the market (e.g. better tech)?
- Can you solve any of those reasons (e.g. better GTM/team)?
3/ Ingredients for success:
- What needs to come together for your project to be successful (e.g. platform scalability, end-user distribution)?
- Are most of these ingredients achievable in the next 1-2 years?
- Can you accelerate the timelines for any of these ingredients?
Bridges enable:
- Greater productivity and utility for existing cryptoassets
- Greater product capabilities for existing protocols
- New features and use cases for users and developers
3/ There are usually 4 components to these systems:
- Monitoring state on the source chain
- Relaying information to the destination chain
- Reaching consensus on which information to relay
- Cryptographically signing the information sent