ENGINEERING RECORD
Technical claims need
inspectable evidence.
Records generated by the project’s development environment with synthetic identities and local assets. They are not independent audits or evidence of production service availability.
Distinguish real verification from simulated environments.
Semaphore/Groth16 proofs were actually generated and verified with synthetic identities and membership data. Trading tests executed real contract bytecode on a local in-memory EVM with test quote assets.
These records come from the same developer. File hashes detect changed downloads; they do not establish safety, independent endorsement or project identity.
REAL CRYPTOGRAPHY / SYNTHETIC INPUTS
Zero-knowledge verification records
- real proof verifies, no identity commitment or private field in public transcript
- two concurrent session submissions accept once; replay is valid crypto but duplicate
- application and epoch scopes differ, proofs verify, same member root remains
- changed curve point and altered public message fail real verification
Browser-session replay protection is not persistent, cross-device production protection. Different nullifiers across scopes do not establish resistance to timing, IP, message or small-group linkage.
Raw ZK record JSON ↗LOCAL EVM / NO REAL FUNDS
TIME contract and trading records
- constructor rejects zero recipient and zero issuance
- fixed issuance goes to explicit treasury; no mint or admin entrypoint
- transfer, approval, transferFrom and finite allowance accounting execute on EVM
- deploy official Uniswap V2 factory, router and wrapped ETH bytecode
- actual AMM buy and sell with finite approvals, minimum outputs and deadlines
- expired deadline and impossible minimum output revert without token loss
Compiler: 0.8.30+commit.73712a01.Emscripten.clang. No official mainnet asset, real funds, actual public-wallet signing or exchange custody acceptance.
Raw contract record JSON ↗DEPLOYMENT REFERENCE / 2026-11-01
From local tests to reproducible delivery.
The deployment reference below has a separate scope and test count from the website/ZK suite. It is developer-generated and not independently audited.
6 groups passed, 0 failed. Actual execution checked UID 1000, loopback-only networking, read-only root, empty effective capabilities and no privilege escalation. Rehearsal records were saved.
Execution record JSON ↗
5 schedules and 182 timestamps checked cliffs, catch-up, rounding, beneficiary changes and native/token destinations. No official vesting funds exist. Rights are transferable and later funding follows the original schedule.
Boundary record JSON ↗
Actual local-EVM positive cases checked initcode, constructor arguments, derived address, canonical block, confirmations, runtime and initial mint events. Negative cases explicitly inject faults; they are not public-chain incident tests and do not guarantee RPC trust or finality.
Transaction verification record JSON ↗
Recorded at 2026-11-01T13:19:15.024Z (UTC): chain 84532 and block 53086447 were read. This proves that read only: no wallet connection, no sent transactions and no official public-testnet TIME deployment.
Connection record JSON ↗
Historical trimmed package: 0 production and 9 development advisories, including 1 critical. This excludes website/ZK dependencies. Zero production advisories do not guarantee safety.
Scope and statistics JSON ↗
Includes token and vesting references, complete Standard JSON compiler input, lockfile, Docker and tests. Synthetic data only; no private keys, actual investor allocations or real funds.
Download deployment and vesting reference ZIP ↓Read container isolation checks ↗WEBSITE USABILITY / CHROMIUM
Recorded website usability review.
Eight pages at four actual viewport widths (1440, 768, 390, 320): 32 combinations without horizontal overflow. Checks covered Escape/focus return and outside-click menu closing, Home/End scenario navigation and accessible naming. Mobile evidence text was increased to 14px.
Verification links returned HTTP 200, and the browser-fetched source ZIP matched its published SHA-256. Physical devices, screenshots and screen-reader audits remain incomplete. Native download controls had prior third-party extension interference and were not retested in this historical review.
Read browser record JSON ↗DOWNLOAD INTEGRITY / SHA-256
File integrity
Compare downloaded files against these SHA-256 hashes. Hashes do not replace independent review.
101,201 bytes
b9f09d0d87b6eb6e48d8151d996e68141b96ce7d0df0cbb2add3f5d0d59fbb60
28,342 bytes
905e437d9bf07abc489dfe3bbbd024938346cbbab484608c5a1405d3504d5bff
16,008 bytes
0af173bb01750f5a4f5a65f6ac4e3833669775f95ce7073c540f2de3727aec9c
9,673 bytes
1397bd1ef14b227fdb3aa3286069ed9958c04a6ad883a75d667b3beb7ea86ec5
4,785,036 bytes
791db79d1780cbfd465e52a6d30b8ebac54fa323dada9ef553c41ade9b2e0046
57,197 bytes
19f161d2d27816beeff909780494b17d23b0fb92650e721e6c1d8ae4b7596916
1,185 bytes
c02d4910a5c698699600d3639ad1f7de91365f9f4348f8e7f45136fb098fd7e3
733 bytes
a27f0224107a0d1973c0713034668d1e3748390e19f07e34c38c386b53c2ef7c
316 bytes
b6b08841c1b83eaf047232af66a2608b6ec725e765949b47fcc6d82685b6651a
168 bytes
9bcb6cdef6c9fd5c0f6b2f7c387b0ac838639b1dfaa338f7179a9bce45cc55c5
3,165 bytes
7cf01a7a220aa125650c21d656fd9321a7f32b945f5abcc6245a2910a6df1f23
2,949 bytes
13e28598ccac5b477adaf8bf13321d7d60c5c3cfcdcd4f8ced205646702571c7
32,363 bytes
d4f80a8b33ca104de1115c97bab9b96200782a5421bf7b51d43893cca8ea02b8
1,033 bytes
52ca80da4431ad45884f967576d6719092499f8df0cc5d4aa85c0b985623803c
VERIFICATION LIMITS
Conclusions these tests do not establish.
- Anonymous issuance, recovery linkage and real biometric deduplication remain unresolved.
- Dependency remediation and independent security audit remain incomplete across the full project.
- Responsive and keyboard checks have been rerun; physical-device, screenshot and screen-reader acceptance remain incomplete.
- Entity, economics, actual liquidity and exchange applications remain incomplete.