Built & operating Yieldcoin - https://xitter.cf/t.co/C0SlnSxFAl - with CRE & CCIP | @chainlink Chromion grand winner | Featured by @CyfrinUpdraft | Looking for work
Joined December 2024
- Tweets1.4K
- Following338
- Followers604
- Likes7.3K
rate for @Compound_xyz on @base spiked around last night's rebalance then tapered off to below 3% net apy
this is acceptable every now and then but if it happens consistently, I'd investigate and reconfigure rebalance frequency because about 14 hours later, the active strategy was ranked 9/12
net apy back above 4% now and compound on base is 1/12 (this occurred naturally without a rebalance)
yieldcoin's annualized return sitting at 5.27% after 12 days live in production
shout out to @Compound_xyz on @Optimism
2nd time yieldcoin has rebalanced into this strategy in the last week
bridge time with @chainlink CCIP took 12 seconds: ccip.chain.link/msg/0x2af388…
Yieldcoin has been live for 10 days and has currently delivered a net annualized return of 5.41%
yield.contractlevel.com
🤖 Made with AI
Yieldcoin is live with @chainlink CRE & CCIP, optimizing USDC across 12 Aave/Compound markets on 6 chains yield.contractlevel.com
I designed, built, tested, formally verified, took through audit, launched, and operate it.
I'm looking for work. Yieldcoin is open to opportunity.
Yieldcoin is live with @chainlink CRE & CCIP, optimizing USDC across 12 Aave/Compound markets on 6 chains yield.contractlevel.com
I designed, built, tested, formally verified, took through audit, launched, and operate it.
I'm looking for work. Yieldcoin is open to opportunity.
Thank you @chainlink for awarding YieldCoin the grand prize in the Chromion hackathon! We all know the entire world is going to run on Chainlink, so this is a great honor, and (was) a personal life goal.
Thank you @CyfrinUpdraft for the resources to learn invariant testing, formal verification, and the security first approach!
Thank you @concero_io for inspiring the idea, Parent-Child architecture, and custom CCIP tx types!
Thank you everyone for the support!
YieldCoin development continues alongside researching a proposal for the vLEI hackathon, Contract Level Identity (name pending review): A Decentralized Fuzzy Extractor, to address the critical need for absolute sybil-resistance by consensus - an inherent requirement for onchain identity and compliance.
Read the YieldCoin dev notes taken during the hackathon here: medium.com/@contractlevel/de…
yieldcoin generating a net of 7.68% (this is after the protocol takes its 1% fee)
total value of $YIELD (CA:0xab83ba0bc3c4fee04fe4ad5df914f86f5f31c45d on @base @buildonbase) is up 0.11% since launching 8 days ago
currently operating as private financial infrastructure
yieldcoin is live and has been for over a week, I just havent announced it yet.
in that time it has earned 5% apy. that number would probably be higher but for the first 3 nights, rebalancing happened at 0:00UTC into aavev3 on eth for around 12-13%
every night a whale would withdraw $133m around 23:30, then deposit again around 0:10. so rates would spike during the rebalance window and then drop sharply for the rest of the day
the biggest design mistake made apparent by deployment was not having a dedicated role for setting ccip gas limits. this functionality is controlled by CONFIG_OPERATOR_ROLE, which also sets crosschain vaults - a much more security critical operation. next time, or in a future upgrade, I'd separate them so the vault setter is a timelock msig and gas limits is a secure eoa
annoyingly after deploying to mainnet, the ai powered property workflow im building identified an optimization in the parent vault recovery, but it does not warrant an entire upgrade by itself
yieldcoin is live and has been for over a week, I just havent announced it yet.
in that time it has earned 5% apy. that number would probably be higher but for the first 3 nights, rebalancing happened at 0:00UTC into aavev3 on eth for around 12-13%
every night a whale would withdraw $133m around 23:30, then deposit again around 0:10. so rates would spike during the rebalance window and then drop sharply for the rest of the day
the biggest design mistake made apparent by deployment was not having a dedicated role for setting ccip gas limits. this functionality is controlled by CONFIG_OPERATOR_ROLE, which also sets crosschain vaults - a much more security critical operation. next time, or in a future upgrade, I'd separate them so the vault setter is a timelock msig and gas limits is a secure eoa
annoyingly after deploying to mainnet, the ai powered property workflow im building identified an optimization in the parent vault recovery, but it does not warrant an entire upgrade by itself
