4.3.Review Workflow
Last updated
Last updated
From submission to security-verified launch.
Every project submitted to OPPAD goes through a strict, sequential audit pipeline. The review workflow ensures no project can bypass validation, pay to be approved, or hide behind fake badges.
Project Submitted β- Dev fills the application β- Token and launch logic uploaded
AegisAIβ’ Audit Triggered β- Contract scanned instantly β- Issues flagged in <5 mins β- Score + risk level recorded
If Passed β Go to Sentinel β- If Critical: Blocked β- If Warning: Sent for explanation
Sentinel Review Begins β- Human auditors inspect logic β- Match declared tokenomics vs code β- Check dependencies and forks
Final Review Outcome β- β Pass = Audit Badge β- β οΈ Warning = Soft flag + Badge β- β Reject = Launch blocked
Results Published β- Audit score and badge displayed on frontend β- Stored on-chain for transparency
Projects that fail any stage may:
View their audit logs
Fix issues
Resubmit once for re-review
[!TIP] Multiple failed attempts will flag the project internally and lock its form.
π Unskippable: All projects must pass both layers
π΅ Unbribable: No paid audits or skip tokens
π Verifiable: Review data stored off-chain + verified badge stored on-chain
[!INFO] This process ensures only credible, secure, and honest projects are launched through OPPAD.