# Submitting Data to the SCAS Database

To submit protocol data to SCAS, you can open the admin interface at scauditstudio.de/admin and input the login credentials provided by our team.

# Adding Protocol Data

To add protocol data to SCAS, click the "Add Protocol Data" button. To edit existing protocol data, search for the protocol and add data to the existing entry.

The following screen displays sections to add various data to SCAS. The inputs are highlighted and automatically checked for form. There are primarily five sections to add data:

Basic Information
Security Infrastructure Information
Codebase Information
Centralization Information
Calculating Score

# 1. Basic Information

The Basic Information section has six input fields:

Name of the protocol
Logo URL of the protocol (the URL must end with .png or .jpg and be from a trusted source like Twitter)
Website URL of the protocol (e.g., https://app.uniswap.org/)
Recommendations on how to avoid risks listed in the protocol's documentation
Blockchains on which the protocol is currently deployed (e.g., Ethereum, Base, Arbitrum, Optimism)
Protocol category (e.g., AMM, Lending, Staking)

# 2. Security Infrastructure Information

The Security Infrastructure section has four input fields:

Bug bounty URL (e.g., Uniswap Bounty on Cantina https://cantina.xyz/bounties/f9df94db-c7b1-434b-bb06-d1360abdd1be)
Maximum bounty amount offered by the protocol
Record of previous bounty payouts to whitehat researchers
Audit report links (must be either Sherlock or CodeArena GitHub issues repositories or a PDF file)

Note: Updating audit data may take up to 30 minutes to upload successfully.

# 3. Codebase Information

The Codebase Information section has four input fields:

Describe the code hierarchy or components of the protocol, and how the protocol's code functions and modules interact with each other.
Add the GitHub repository link for the protocol's codebase (e.g., Uniswap V3 GitHub Repo Link: https://github.com/Uniswap/v3-core)
Briefly describe the most complex code parts of the protocol (e.g., AMM, Tickspacing, Liquidity, Swapping in Uniswap).
Add links to similar protocols (e.g., other AMM protocols if the current protocol is an AMM).

Keep in mind that the "Basic Code Structure" and "Most Complex Code Parts" fields are the most time-consuming and require careful attention. The authenticity of the data will be verified by the SCAS team before approving the protocol, so providing accurate information is necessary.

# 4. Centralization Information

The Centralization Information section has six input fields:

Information about timelocks, such as withdrawal or unstake vesting tokens
Details about the protocol's governance, including admin wallets or multisigs
Information about the actions that admins can perform
Information about the ability to pause and unpause protocol modules
The frontend (dapp) link for the protocol
Information about the ability to use a third-party frontend with the protocol's deployed contracts, and a rating on how easy it is to maintain a third-party frontend (Excellent, Average, or Poor)

# 5. Calculate Scoring

The Calculate Scoring section has two dropdown inputs:

Select a boolean value indicating whether admins can directly steal funds (e.g., through a withdraw or recover function)
Select a boolean value indicating whether admins can indirectly steal funds (e.g., by setting withdrawals to 0 or pausing the protocol)

These selections are based on the "Metrics" block, which contains the scoring parameters.