Smart Contracts and Tokens¶
All PQWERAI contract languages compile to the same EVM — there is no separate VM. Pick the language for its safety and ergonomics; deployment, ABI encoding and tooling are identical.
| Language | Compiler pinned | Status on chain 77240 | Best for |
|---|---|---|---|
| Solidity | solc 0.8.26 | ✅ Tested (Foundry, Wallet Studio) | Most contracts, OpenZeppelin ecosystem |
| Vyper | 0.4.3 | ✅ Tested (CLI) | Auditable, Pythonic contracts |
| Yul | solc 0.8.26 --strict-assembly |
✅ Tested (CLI) | Hand-written low-level code |
| Huff | Huff Neo hnc 1.7.1 |
🧪 Compiles and runs; Studio integration unreleased | Opcode-level optimisation |
| Fe | 26.5.1 | 🧪 Experimental | Research; not for value-bearing code |
Start with the language comparison (same contract in all five, measured gas), then:
- Standards: ERC-20 · ERC-721 · ERC-1155
- Patterns: access control and ownership · events · payable functions · Solidity libraries
- Verification · Application languages (JS/TS/Python)
Unaudited examples
Every example on these pages is tutorial code. Compiler success is not a security review.
Sources at 72057fe3ec: contracts/studio/compilers.json · architecture/MULTILANGUAGE_CONTRACTS.md
Found a problem? Report a documentation issue · Build testnet-rc1+72057fe3ec