Pickle and Yearn developers have worked out a structure to allow the two projects to work together in symbiosis. This is done to reduce duplicate work, increase specialization, and to leverage shared expertise. A description is provided below with more information to follow. This is an initial minimal release, with further integration planned.
I have become increasingly obsessed with capital efficiency. Current liquidity is segmented. You get to choose one of;
Deriswap (currently under audit), combines Swaps, Options, and Loans into a capital efficient single contract, allowing interaction between the two assets that make up the pair.
Lets consider ETH-BTC pair.
The swap contract is standard Uniswap x * y = k. LPs provide ETH-BTC as liquidity. Traders can swap ETH to BTC and vice versa. LPs earn trading fees.
The TWAP oracle was expanded to take readings every 30 minutes, this allows us to report realized variance, realized volatility, implied volatility (derived from Realizing Smiles), and price over an arbitrary selected time series. …
We previously wrote about Keep3r Network’s on-chain oracles
Given that Keep3r’s price feeds allow for sampling multiple points over a fixed window we can expand this to include realized volatility between pairs.
We have released a new oracle candidate which includes;
For integration & documentation;
One of yearn.finance’s core tenets is downside mitigated savings accounts. Thus far we have focused on lossless strategies, while the upside is potentially less, the downside is mitigated. This however leaves a lot of desirable opportunities unavailable to vaults.
Lets go through an example; lets assume the current best opportunity for DAI is at 10%, however if we did DAI:ETH we could be earning 20%. …
What are Oracles?
An oracle is an external data source that provides an answer to a specific question. For example; “what was the temperature in NYC over the past 24 hours”.
A subset of Oracle’s are price feeds. “what is the price in ETH for wBTC”.
Why do we need Oracles?
Not all data can be provided on-chain. And if it can be provided on-chain, not all data should be trusted. Two examples;
Bob and Alice make a wager on the outcome of a coin flip. Bob says heads, Alice says tails. They both lock in their ETH. Bob is the oracle source, and Bob inputs “heads” into the contract. …
An important goal for Keep3r Network is to keep the “maintenance” of keepers to a minimum. To achieve this, we wanted to create a mechanism for keepers to be able to instantly recoup their gas spent in ETH. This allows for truly set and forget keepers that do not require any devops.
Using MetaKeep3r along with OpenZeppelin | defender means a 0 friction setup environment.
By default, executing work on jobs is rewarded with bonded KP3R (can be unbonded as normal for KP3R). This is important for the following reasons;
The goal with Keep3r is simple, create an agnostic, easy to implement, incentivization layer for routine ecosystem maintenance.
Keepers, as described in the documentation, are technical users, capable of implementing bots and/or scripts and running these in some scheduled manner (cronjobs, tasks managers).
With OpenZeppelin | defender, this is no longer a requirement. We will walk through how to set up a keeper in a few simple steps, earning passive rewards, and not needing to worry about maintenance again.
Jobs have been added for;
Jobs under review;
A scripts section has been added to github
These are very simple scripts with no redundancy, but they can be used to get you started working with keepers.
A subsection for Keep3r Network has been created on the yearn.finance governance forums;
Feel free to register and participate for any technical or project related queries or discussions.
This includes but is not limited to;
creditfor projects to help them on-board
voting rights(non transferable voting shares)
Before posting, please make sure to have read the available documentation
Updated the UI;
Pending Keep3r Features;
Pending Governance Features;