How ton-community/contract-verifier-backend works
Main System Components
a) API Layer
• Entry point through server.ts
• Request handling middleware (req-id-middleware.ts)
• Main controller logic (controller.ts, deploy-controller.ts)
b) Source Verification Layer
• Multiple verifier implementations:
• FunC verifier (func-source-verifier.ts)
• Fift verifier (fift-source-verifier.ts)
• Tact verifier (tact-source-verifier.ts)
c) External Integrations
• IPFS Storage (ipfs-code-storage-provider.ts)
• TON Blockchain interaction (ton-reader-client.ts)
• Smart Contract Wrappers (sources-registry.ts, verifier-registry.ts)
d) Binary Execution Layer
• Compiler version management (fetch-compiler-versions.ts)
• Binary execution handling (binaries.ts)
Data Flow Representation
a) Input Flow:
Client Request → API Layer → Source Verification Layer → Binary Execution
b) Output Flow:
Binary Execution → Verification Result → IPFS Storage
• → TON Blockchain (signed message)
External Dependencies
• TON Blockchain - Hexagon
Key Technical Elements
• Environment configuration (.env)
• Compiler versions support (shown in config.js)
• Security elements (private key signing)
• Smart contract interaction points
Specific Implementation Details
• Multiple compiler version support (0.2.0, 0.3.0, 0.4.0)
• Source code verification workflow
• Message signing process
• IPFS storage integration
• Smart contract interaction