Euler V2 | Ethereum | 10.06.2025

[yvesbou]

Please have also a look at
https://github.com/euler-xyz/euler-interfaces/blob/master/addresses/1/OracleAdaptersAddresses.csv
and determine the different adapters used. Insights from this research will determine the autonomy/dependency risk for the report.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
defiscan	Ready	Preview, Comment	Jan 7, 2026 3:15pm

[newgnart]

I would take on this task if possible?

[yvesbou]

@gnart33 let us finish kodiak first please

[varshith257]

@yvesbou I would like to work on this if it's available.

Can i know more info on this?

[yvesbou]

Hi @varshith257

Thank you for your interest, the review is yours if you confirm. You have two weeks time to submit a first draft.
Join our discord if you have questions, we cant stress enough that all questions are encouraged!

I've updated the template to the latest version just now. Go through the contracts table, run them with the permission scanner. Fill out the permission table with the functions that are restricted/permissioned. While doing that, figure out the smart contract architecture, draw a diagram showing key user interactions + permissioned function calls. This should help contextualise the report and the mentioned contracts and permissions.

The ratings section should name concrete centralization vectors (upgrading, stealing funds, withholding fees/incentives etc.). The protocol analysis section should explain the diagram(s) and can be more technical, mention concrete functions etc.

The permission table (contract | function | impact | owner) should also be technical.

Regarding autonomy/dependency, this is for assessing the risk of dependencies that could break and what's the effect on the studied defi protocol (in this case euler v2). Dependencies are strictly outside, so a multisig of the team is not considered for the category of dependency. For a borrow lending platform, price oracles are the obvious dependency that have centralizing effect on their autonomy

Generally, when speaking about risk:

high risk -> users can suffer loss of deposited funds
medium risk -> users can suffer loss of unclaimed yield or temporary loss of funds
low risk -> users are confronted with drastic performance changes, like excessive fees etc.

all these risks are induced through
either malicious/faulty upgrade or dependency failure/manipulation

[varshith257]

Thanks for detailed info. I will work on this and join discord

[yvesbou]

@varshith257 here is the excalidraw which you should use to draw the diagram
https://link.excalidraw.com/l/9pt8PDVB43r/ADYKutqqDB8

[yvesbou]

Here is the permission scanner repo: https://github.com/deficollective/permission-scanner

[yvesbou]

@varshith257 can you give us an update where the report stands atm?

[varshith257]

@yvesbou Will be drafting PR

[yvesbou]

@varshith257 can you report your progress?

[varshith257]

@yvesbou Done with analysis and writing report just left with minor tweaks and a diagram

I will draft my work by EOD

[yvesbou]

@varshith257 It does not have to be perfect, but we want to see the progress, if it's on track to improve. Otherwise we make it available again.

[varshith257]

@yvesbou Got it.

I had initially planned to draft and push the update by EOD as mentioned earlier assuming my laptop service would be complete that day. I have already completed the DeFi scanner analysis and filled the relevant info into the template for the linked PR but the files are still on my desktop and haven’t been pushed to Git yet due to the ongoing repair.

The service will be completed by tomorrow and I will push the progress as soon as I am back on my system.

Appreciate your patience and apologies for the delay.