Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add YieldNest ynETH logo #1311

Merged
merged 2 commits into from
May 27, 2024
Merged

Conversation

danoctavian
Copy link
Contributor

This PR adds the following token from YieldNest protocol:

ynETH: https://etherscan.io/address/0x09db87a538bd693e9d08544577d5ccfaa6373a48

Supporting links
Socials
Official website: https://yieldnest.finance/
In-depth documentation on the YieldNest restaking protocol and ynETH token: https://docs.yieldnest.finance/

On-chain addresses:
https://docs.yieldnest.finance/security/deployment-addresses

Twitter / X: https://twitter.com/yieldnestFi

Discord: https://discord.gg/ayAZuQgFaE

Linktree: https://linktr.ee/yieldnest

Coingecko Link:

ynETH: https://www.coingecko.com/en/coins/yieldnest-restaked-eth

Defillama Link:

https://defillama.com/protocol/yieldnest

Github public protocol code repo:

https://github.com/yieldnest/yieldnest-protocol

Discussion

I am the CTO and core developer at YieldNest protocol. The protocol is a next-generation liquid restaking protocol that provides simple-to-understand, risk-adjusted restaking strategies. the ynETH token is a liquid restaking token simlar to WEETH, ezETH and others.

The token starts as a a 1:1 with ETH in terms of value, and appreciates over time as the total assets that back ynETH increase in value through yield accrual.

The token will soon go multi-chain, this is the mainnet deployment.

@danoctavian danoctavian requested a review from a team as a code owner May 27, 2024 02:12
@MRabenda MRabenda merged commit 79fd2e0 into MetaMask:master May 27, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants