Submitting a Project
This page answers what you need, what you pay and what happens between pressing Create Project and seeing your report.
Everything below happens in the app at app.spectra-audit.com.
Before You Start
- A browser wallet. Spectra uses SIWE (Sign-In with Ethereum): you sign a message to prove you control the address, and you never hand over a private key.
- At least one deployed contract address. A listing with no valid contract address cannot be submitted.
- Enough balance or stablecoin to cover the listing fee. See Pricing and Payments.
Step 1: Connect Your Wallet
Connect, then sign the SIWE message. That signature is what creates your session. The address you sign with becomes the owner of any project you list, and only the owner (or an admin) can edit it or re-run its audit later.
Step 2: Fill In the Wizard
The project wizard has four steps and saves a draft as you go, so you can close it and come back.
| Step | What it collects | Required? |
|---|---|---|
| Project Details | Project name, description, logo URL | Name is required and must be at least 3 characters. Description is optional, but if you write one it must be at least 10 characters. Logo URL is optional and must be a direct image URL |
| Smart Contracts | Network, then one row per contract: address, optional name, and a flag for whether the contract is the project's token | At least one valid contract address is required |
| Social Links | Platform and URL pairs | Optional |
| Terms and Privacy | Agreement, and whether you want the project audited | Agreement is required |
Notes on the contracts step:
- Supported networks in the wizard are Ethereum (chain 1) and Polygon (chain 137).
- Mark the token contract with the token flag. This is load-bearing. It decides whether your project is scored on the has-token path or the no-token path, and it identifies which contracts count as core when the code score is calculated. See Audit Score Reference.
- The contract count also drives your fee, because the listing price includes a per-contract component.
- Addresses are validated in the form. An invalid address is rejected before submission, not after payment.
Step 3: Pay
There are two supported routes, and the app picks the one that matches how you are paying.
Pay from your Spectra balance. Your listing is drafted first, then charged against your deposit credit balance. The draft expires if it is left unpaid, so pay in the same session where you can.
Pay on-chain, then submit. You send the payment to the SpectraPaymentsV3 contract and submit the listing together with the transaction hash. Spectra creates a pending submission and waits for the payment to be verified on-chain before the project itself is created.
Either way the amount is bound server-side to a quote for your exact project and contract count. A payment that does not match the expected quote does not unlock the listing.
Step 4: Verification and the Audit Run
For the on-chain route, the app watches for verification two ways at once: a live push (server-sent event) and a bounded fallback poll, roughly every 20 seconds for up to 6 minutes. Whichever arrives first completes the flow exactly once. If verification fails or the submission expires, you are told why rather than left waiting.
Once the project exists, the audit is queued. The blockchain worker fetches and analyses the registered contracts, then reports its results back to the backend, which computes and persists every dimension and the headline Security Score in one pass.
Step 5: Where Results Appear
Your report is the project page in the app. It is public, so you can share the link. Scores populate as the audit completes, and a dimension that could not be measured shows as unavailable rather than as a zero.
Re-Running an Audit
You can re-analyse a project you own. A few limits apply, by design:
- Owner or admin only.
- Rate limited to 5 requests per minute.
- Non-admin accounts consume a monthly audit allowance per re-analysis.
- If a run for that project is already pending, queued or running and is less than 30 minutes old, the request returns the in-flight run instead of stacking a second audit.
While a re-analysis is in progress, the code dimension is marked reanalyzing and is left out of the headline score rather than showing a stale number. See Reading Your Report.
Editing a Listing
Edits are a separate, cheaper fee, and adding new contracts to an existing project costs the same per-contract amount as listing them would. See Pricing and Payments.
A high score does not guarantee safety. Results come from AI security analysis with community review, and the product is in beta. Always do your own research.