01 / Account & intake
Wallet ownership is authenticated before upload. Package size, format and request rates are enforced on the server.
TRUST THROUGH TRANSPARENCY
Verification is a process. Not a promise.
Every package is untrusted at the door. Each required stage must pass before a bot can become eligible for launch.
Private by default. Approval by evidence.
Uploads are quarantined and tracked by their SHA-256 hash. Approval applies to an exact package version, and can be revoked when new evidence appears.
02 / Private quarantine
Original packages live in private storage. No public download links. Uploaded content never runs on the web server.
03 / Structural checks
The v1 format is a strict declarative JSON package. Archives, executable code, extra fields and undeclared dependencies are rejected.
04 / Layered scanning
Malware, secret, dependency and structural checks must pass. An unavailable scan blocks eligibility rather than being counted as a pass.
05 / Isolated evaluation
A dedicated validation service must evaluate the exact version under strict CPU, memory, time and network limits.
06 / Human review
Reviewers examine version-bound evidence and paper evaluation. Approved packages may still be paused or revoked.
What approval means
The specified version passed the configured checks and a reviewer granted launch eligibility. Evidence must be current and refer to the same file hash.
Changing the package requires a new submission. Approval does not transfer to a different file.
What it never means
Approval is not a guarantee of safety, future behavior, profitability or token value. It is not a financial recommendation or a substitute for your own assessment.
Security validation, trading results and token transaction status are presented separately.
Current platform stage: Pre-launch. No bots have been verified and no live trading or token minting is enabled. Required external validation services must be connected before approvals can be granted.