Page 1 of 1

stVaults-powered product: technical review from Lido team

This form helps us gather context and technical details about your product. Our goal is to share experience, exchange feedback, and help identify potential risks early. We’d like to learn more about your setup and explore how we can best support you technically.

Name

Primary technical contact

Who is the person we can ask questions if further details are needed.

Source code access

Please share links to repositories (GitHub)

Audit reports

If you don’t have an audits yet, we can help suggest auditors familiar with the Lido V3 codebase.

Deployed contract addresses

Include network (testnet / mainnet) and verification links. Deploy verification from auditors if available.

Commit hashes: audited version + currently deployed version

Technical Documentation

Link to tech docs. In case you don't have full documentation, please briefly describe:

1. Architecture and how Lido V3 is used

2. External protocol dependencies

3. Upgradeability

4. Admin / owner roles

5. Emergency or pause mechanisms

6. Off-chain components (if any)

Unit test coverage, %

Bug Bounty program

Additional testing (integration tests, fuzzing, invariants)

Any additional info covering possible rounding and math issues

UI link

Please provide a link to the interface your users will interact with.

Please describe the UI flow and functionality

1. A written description of the core UI flow, including: ◦ general description on what functionality it covers; ◦ key user interactions; ◦ assumptions and limitations with configurations.

2. Environments & access: ◦ UI links: staging or production; ◦ Feature flags / configs.

3. Supported wallets and devices list;

4. Off-chain dependencies: API besides stVaults API, RPCs, indexer, caching rules, etc;

5. Known issues