originprotocol / oeth.com Goto Github PK
View Code? Open in Web Editor NEWFrontend for oeth.com
Frontend for oeth.com
See Google Doc π€
#47 calls for the first page of Proof of Yield to be shipped by itself. In fact, there is another iterative step we could take that wouldn't be much more complicated. The second page for PoY can be broken down into two parts. First, we give more detail for the yield distribution on a given day. This includes a line item for each rebase, an accounting of the performance fee, etc. The second half of the page is dedicated to yield source attribution. It shows where the pre-dripped yield comes from and allows us to compare strategy performance to expectations.
Before trying to wrap up the backend accounting necessary for the yield attribution, let's ship this second page just with the top half. We'll provide more evidence of the yield distribution and detail with the other part in a subsequent version.
Adding feedback from oeth analytics Blocker feedback
oeth.com/governance currently points to a non-existent CMS page. It should redirect to ousd.com/governance or serve the same page. Someday, we will likely have a different domain handling this.
Currently it's using the protocol logos, should be tokens - see design
The Hero Image on OETH.com lays on top of the title background, whereas the images on our other blogs strike through the title and body backgrounds. The ladder looks better, especially with certain color schemes.
OETH example: https://www.oeth.com/oeth-litepaper
OUSD example: https://www.ousd.com/litepaper
Under the "Always the best pool" heading on the homepage, contrast OETH's performance to the LSDs. According to @HrikB, it sounds like there may not be a reliable source for the LSD APYs yet so we may need to do our own calculations. Let's just be sure to compare apples to apples with the same timeframe for each one (e.g. 24-hour, 30-day, etc).
Comment from Micah: Minted OETH is missing from the collateral totals, so they don't add up to 1196.48. In the OUSD case, we interpreted OUSD in Convex to be equal to 3Crv and we added it proportionally to the DAI, USDC, and USDT balances. I don't think this works in the OETH case but I'm not sure what to do here.
Add "Analytics" as a category on https://www.oeth.com/ecosystem
Currently blocked on adding Dune/Coingecko/DeFillama/etc. as ecosystem partners as analytics integrations.
Lets get it looking like:
Marked up across desktop and mobile
For #47, we decided to leave "today" off of the 30-day history (first page) of Proof of Yield. This was to avoid an unhappy experience we had back in the day when /apy would show an APY that fell throughout the day. Here's why that was happening:
π¨ = hour (+/- 300 blocks)
β»οΈ = rebase
Scenario A
π¨ π¨ β»οΈ π¨ π¨
Scenario B
π¨ π¨ β»οΈ π¨ π¨ π¨ π¨ π¨ π¨
Our APY calculation looks at the change in OETH supply, which is affected by rebases and transfers but not affected by growth in underlying collateral (pending rebase). It calculates the change in OETH supply since the last day, then it extrapolates this out into a full day of blocks and annualizes it. In scenario A, the change is effectively multiplied by SIX (24 hours in a day divided by 4 hours passed = 6). In scenario B, the change is effectively multiplied by THREE (24 hours divided by 8 hours passed = 3). As a result, the APY from A expects to have a rebase every 4 hours. The APY from B expects to have a rebase every 8 hours. In reality, there is unlikely to be a second rebase unless a large mint or redeem occurs.
If my understanding is correct, this is basically time-weighting the yield and projecting that the same earning rate will be experienced throughout the day. This is not what this page should do. It should report the actual amount of yield distributed within the given period. I think the way to fix it would be for the "today" line to account for when the last rebase had occurred (not including the prior day), figure out how many blocks had passed since then, and assume that there are no more rebases coming.
Curve, Beefy Finance, CoinGecko, Dune, MEW, Maverick, Morpho, Nansen, Token Terminal, Votium, yearn.finance and Uniswap integrations are published on the CMS but do not populate on oeth.com/ecosystem.
(may need to be separate issue) but Josh asked to sort integrations by notoriety/liquidity. It would be helpful to add a way to do this without needing to update each partner to be sorted chronologically.
We've got Sentry in place for error tracking on ousd.com. It should be added to both the staging and prod versions of oeth.com.
Add Rocket Pool and Convex. Remove Balancer. Sizing and padding had to change in the design slightly to fit more logos
Aside from the data that we show on the homepage, we will want an OETH version of the new analytics site that we recently launched for OUSD. The new one should live at oeth.com/analytics.
https://www.figma.com/file/BA9IMIvswYcD5xlJpcEOYG/Analytics?node-id=333-7570&t=1tlrPCf43eI1j3ok-4
A few observations:
Our Proof of Yield project is a significant undertaking and it keeps getting pushed back. We already cut the scope once to limit the backend accounting to be "pre-Dripper" since this still lets us compare actual strategy performance to expectations. It also helps us gain trust by showing users that the yield is real and where it comes from.
Aside from the Dripper page, which we were planning to move to /analytics, there are two pages that are currently in-scope for PoY:
The data for the second page is a bit complicated because measuring strategy performance is non-trivial, particularly when harvests are involved. But the data for the first page should be much easier to get. It's basically a prettier version of our popular old /apy page without all the esoteric columns. We've actually taken a step backward with OETH in this regard because we don't have this APY detail page, so users can only see our advertise 7-day trailing average metric. I don't think we should launch an OETH version of the old analytics frontend. As a first step, let's just launch the first page of PoY to provide some level of detail for users who want a daily report on OETH's performance.
Josh had mentioned the ecosystem page should have the more important protocol integrations come up first, but right now the integrations are ordered randomly. Can items be sorted either by a position number or publish date? If the ladder, I'd need an option to publish a back date to easily order partners.
Compare OETH's APY to the underlying LSTs but in a positive way.
(picking wOETH in the second input forces OETH in the first)
After #48 comes the third phase of PoY: yield source attribution. This is the bottom section of the daily detail page shown at https://www.figma.com/file/eN26ytHYvZ7bhCaHy5K0iv/OUSD-Proof-of-Yield?type=design&node-id=487-50955&t=wzlJxv23ETCqYGj1-4.
Proof of Yield consists of two categories of information:
The former is covered by #47 and #48 and is calculated post-Dripper. It's all about what happens after each rebase
event and organizes this information by calendar days.
The latter depicts what happens pre-Dripper, namely how each strategy has performed in addition to redeem fees, etc. It's incredibly complicated to track the yield from when it is generated to when it is dripped out since the Dripper commingles funds that were generated at different points in time, mixes them together, and distributes them over indeterminate periods of time. Because of this complexity, we decide to focus just on the generation of the yield prior to entering the Dripper. However, this has UX implications for the PoY pages. When looking at a PoY detail page for a particular day, the top portion depicts the yield that was distributed on that day and the bottom portion shows the yield that was generated on that day. Users will not be able to draw connections in the UI from yield being generated and then being distributed. The plan is to test this out and see if users find value in PoY and demand more thorough accounting. I'm fairly confident that we're already going above and beyond what is necessary.
Related: OriginProtocol/origin-dollar#1234
Create the OETH equivalent of https://www.ousd.com/partners for marketing to populate.
The APY chart on staging.oeth.com currently shows OUSD's performance, not OETH's.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.