3Jane Docs | Audits & Security
How to evaluate security evidence without assuming coverage.
An audit label is only useful when the report, commit, contract scope and deployed implementation can be matched. This page does not invent auditor names or report dates that are not present in the supplied source; it provides the verification framework users and integrators should apply to current security material.
What to verify in an audit
Confirm auditor identity, publication date, repository commit, contracts in scope, severity ratings, remediation status and whether the deployed bytecode corresponds to the reviewed version. A report covering a previous implementation should not be treated as proof for a later upgrade.
Proxy and upgrade review
If contracts are upgradeable, inspect proxy and implementation addresses, upgrade authority, timelocks or multisig controls, and the events associated with implementation changes. Security review must follow the code that actually executes.
What audits do not cover
A smart-contract review may not cover credit underwriting quality, fintech servicing, stablecoin risk, offchain data integrity, legal isolation or economic concentration. Those belong to broader protocol risk analysis.
| Evidence | What it supports |
|---|---|
| Contract audit | Code-level review within scope |
| Deployment verification | Code-to-address match |
| Risk docs | Economic / operational context |
| Facility reporting | Credit performance context |
| Monitoring | Changes after audit date |
User checklist
Before interacting with a new deployment, verify current addresses, read the latest available security material, review changes since the report and understand the amount you are willing to expose even if all known findings were remediated.
Protocol mechanics are documented for education and integration context. Current rates, caps, emissions, eligibility and transaction parameters should be verified in the live 3Jane interface before acting.

