@chainlink Chromion hackathon grand winner | Featured by @CyfrinUpdraft | Building Yieldcoin v2 with CRE, ACE & CCIP - seeking launch partner
Joined December 2024
- Tweets 1,118
- Following 299
- Followers 589
- Likes 5,665
381 Photos and videos
Pinned Tweet
18 Jul 2025
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…
31
23
189
17,701
Yieldcoin v2 @certora suite HelperHarness
All contracts have their own harness that inherits this, for reusable helper functions across specs
the role helpers could be spec definitions, but they'd have to be chisel'd
github.com/contractlevel/yie… started certora on yieldcoin v2
38
github.com/contractlevel/yie… started certora on yieldcoin v2
64
Contract Level retweeted
Jun 11
“I formally verified its secure”
3
2
58
1,498
Jun 13
github.com/contractlevel/yie… yieldcoin v2 management fees capped.
management fees are taken at the end of every rebalance and equal approximately 1% of TVL annually. the cap means more than that can't be taken in a single rebalance
1
42
Jun 13
Side quest for the week: Reaper Vaults V2 shadow audit on @ZealynxSecurity academy
Reaper vaults are automated financial strategies, so similar conceptually to Yieldcoin v2.
Need some closure on those FPs
academy.zealynx.io
28
Jun 12
github.com/contractlevel/yie… zero checks added for values that should never be zero
some setters can be zero, as that is how the values are removed - this is documented in the natspec for relevant funcs
30
Jun 12
github.com/contractlevel/yie… explicit recovery modes
Jun 11
struct would be too much bloat
flag could be changed to RecoveryType
1
42
Contract Level retweeted
Jun 11
Tomer takes threat analysis to the extreme. He challenges every aspect of how a system may go wrong.. This complements auditing, FV, testing, and any software design methods. It is applicable beyond defi
Hot take from @tomer_ganor, the security researcher behind @aave, @LidoFinance, among other major protocols:
Protocol design determines security before code exists. "There are a lot of bugs that exist before the code is written. I was able to find a lot of 'bugs' in the protocol without even seeing the code”.
Full interview on @CCNCitizens 👇
1
2
19
1,154
Jun 11
struct would be too much bloat
flag could be changed to RecoveryType
Jun 11
github.com/contractlevel/yie… added an explicit recovery exists flag, rather than inferring from the state of multiple recovery modes
come to think of it, maybe we should be using a general Recovery struct with a RecoveryType
1
78
Jun 11
github.com/contractlevel/yie… added an explicit recovery exists flag, rather than inferring from the state of multiple recovery modes
come to think of it, maybe we should be using a general Recovery struct with a RecoveryType
1
84
Jun 11
github.com/contractlevel/yie… 3 days spent checking claim solvency with halmos. still getting timeouts
Compilation times are so painful. @chainlink ACE's CredentialIdentityRegistryValidator stack-too-deep errors need to be solved.
at least certora jobs will be quicker than this 🤡
36
Jun 10
At a certain TVL, the commercial operator of Yieldcoin v2 just monitors it and collects fees.
Permissionless recovery modes can be automated, and so can $LINK reserves topups.
There's not a whole lot to monitor for except incident response.
Automated, secure IR looking good.
Jun 10
Yieldcoin v2 architecture:
- 1 @chainlink CRE workflow with multiple triggers/handlers for executing rebalances and closing epochs
- ParentVault on *only one* chain <- this is where users interact with the system via @chainlink ACE
- ChildVaults on every other supported chain (interact with parent and each other via @chainlink CCIP and CRE)
- Every chain has an AdapterRegistry, with adapter contracts per supported strategy protocol, and a WorkflowRouter, for routing CRE reports to the vault
- YieldcoinShare token is ComplianceTokenERC3643 from ACE repo, and minted on parent chain as a receipt/share for underlying asset in the crosschain vault
- Cloudflare Worker Relay API for filtering DefiLlama API to workflow. The biggest impact of the centralized risk for API is delayed rebalancing. If either API goes down, the system continues regular epoch operations, generating yield in the current active strategy.
It's a cool system.
4
117
Jun 10
Yieldcoin v2 architecture:
- 1 @chainlink CRE workflow with multiple triggers/handlers for executing rebalances and closing epochs
- ParentVault on *only one* chain <- this is where users interact with the system via @chainlink ACE
- ChildVaults on every other supported chain (interact with parent and each other via @chainlink CCIP and CRE)
- Every chain has an AdapterRegistry, with adapter contracts per supported strategy protocol, and a WorkflowRouter, for routing CRE reports to the vault
- YieldcoinShare token is ComplianceTokenERC3643 from ACE repo, and minted on parent chain as a receipt/share for underlying asset in the crosschain vault
- Cloudflare Worker Relay API for filtering DefiLlama API to workflow. The biggest impact of the centralized risk for API is delayed rebalancing. If either API goes down, the system continues regular epoch operations, generating yield in the current active strategy.
It's a cool system.
1
156
Jun 9
Spent the day trying to integrate Halmos into Yieldcoin v2's Chimera suite. Not going well because the suite handles a lot of infrastructure, so attempting to explore all paths runs out of memory.
Efficient use of halmos in this codebase is likely to focus it on isolated, unit-style, epoch-solvency properties, with minimal deployment overhead.
The Chimera suite already uses Foundry, Medusa and Recon-fuzzer to assert properties against a comprehensive crosschain environment
The question is how to aesthetically fit halmos into/around the rest of the tests
First time using Halmos since completing Cyfrin Updraft fv course
1
1
55
Jun 8
github.com/contractlevel/yie… Yieldcoin v2 can optimize yield for any integrateable asset, so long as it's compatible with @chainlink CCIP and the supported strategies.
$USDC is intended to be the first instance
1
46
Jun 8
github.com/contractlevel/yie… Known issue: settlement overwrites calculated total withdraw estimate with the actual amountOut
When an epoch closes with net withdraws, the expectedAmount is withdrawn from the strategy, and the amountOut is distributed pro-rata to withdrawers for that epoch.
Adapters revert if amountOut < expected
2
63
Jun 7
github.com/contractlevel/yie… After a year of iteration, I can finally see the finish line with Yieldcoin. Audit ready by end of July - mid Aug, best effort estimates, assuming Certora and mutation testing doesn't reveal something new.
Currently working through known issues flagged by various tools and generally cleaning up the codebase, then:
- certora (🥳)
- mutation testing
- tvl impact rough simulator in workflow
- comprehensive docs (including incident response plans, threat modeling, etc)
- probably some other stuff... the proxy question lingers and the closer this codebase gets to being audit-ready, production grade infra, the more attractive they appear.
Happy with the progress.
Jun 7
feels simultaneously lazy and convoluted writing a plan to finish naming errors and unit testing them
1
6
245