-
Notifications
You must be signed in to change notification settings - Fork 168
Smart contract project assesment criteria
Anton Trunov edited this page Apr 25, 2025
·
1 revision
| Code Quality | Reusability | Testing | Documentation | Tooling |
|---|---|---|---|---|
| Gas assertions and fee checks: 0–3 | Consistent code style: 0–1 | Test coverage: 0–3 | TL-B schema included: 0–1 | Deployment and scripting tools: 0–2 |
| Workchain support: 0–1 | Gas optimization: 0–2 | Testnet protocol coverage: 0–1 | Architecture diagram: 0–1 | Indexing and analytics tools: 0–2 |
| Storage management: 0–2 | Scalability considerations: 0–2 | Documentation coverage: 0–2 | On-chain get methods: 0–1 | |
| Cross-contract interactions: 0–1 | Known vulnerabilities addressed: 0–2 | Code comments and clarity: 0–2 | Protocol integrations: 0–2 | |
| Magic numbers replaced with constants: 0–1 | Modular code structure: 0–1 | Build process documentation: 0–1 | Wrappers and SDKs: 0–2 | |
| On-chain API quality: 0–2 | Readability and naming: 0–1 | Explicit dependency listing: 0–1 |