Smart Contracts

WASM Runtime — Contracts That Think for Themselves

Write in Rust, C, or AssemblyScript. Compile to WebAssembly. Deploy on-chain. With autonomous triggers, your contracts execute on schedule — no keepers, no cron, no third party.

4
Languages
Rust, C, AssemblyScript, Go
~1KB
Bytecode Size
Lightweight on-chain
100x
vs EVM
Compiled, not interpreted
0
External Deps
No keepers or cron needed
Rust / C / AS
Compiler
WASM
On-Chain
Execute

Write in the Language You Know

🦀

Rust

Systems-level performance with memory safety. The gold standard for WASM contracts.

📝

AssemblyScript

TypeScript-like syntax — easy onboarding for web developers. Compiles directly to WASM.

⚙️

C / C++

Maximum performance for compute-intensive workloads. Legacy system integration.

Built for Production

Not a toy VM — a production-grade compiled runtime

  • Compiled performance — orders of magnitude faster than EVM interpreted bytecode
  • Sandboxed execution — memory-safe, no host filesystem access, deterministic results on every node
  • Hot-upgradeable — deploy new contract versions via your transaction chain, no migration needed
  • FHE host functions — call ZAMA/OpenFHE directly from your contract for confidential compute
Sandboxed Memory-safe, isolated execution
Deterministic Same result on every node
Upgradeable New versions without migration
FHE Access Compute on encrypted data natively

Autonomous Triggers

Contracts that execute themselves — on schedule, on event, on condition. No Chainlink Keepers. No Gelato. No cron jobs.

Why This Changes Everything

On Ethereum, you need third-party services (Chainlink Keepers, Gelato) to trigger smart contracts — extra cost, extra dependency, extra failure point. On ATSHI, triggers are native to the protocol, evaluated at consensus level. Your contracts are truly autonomous.

📅

Date / Time Trigger

Execute at a specific date, one-time or recurring. Schedule a token unlock for January 1st, a quarterly dividend distribution, a daily rebalancing — all defined in the contract itself.

Schedule
🔄

Interval Trigger

Periodic execution every N blocks or N minutes. A health-check contract that runs every 5 minutes. A rebalancer that executes every 100 blocks. Set it and forget it.

Periodic
📡

Oracle Trigger

React to external data feeds — price changes, weather data, API responses. When ETH drops below $3,000, execute the hedge. When temperature exceeds 40°C, trigger the insurance payout.

External Data
⛓️

On-Chain Trigger

Execute in response to on-chain events — token transfers, contract calls, threshold reached. When a wallet receives more than 10,000 ATSHI, auto-stake. When supply chain alerts fire, notify.

Chain Events

Why Developers Choose ATSHI WASM

🌐

Multi-Language

Rust, C, AssemblyScript, Go — use the language your team knows. No Solidity lock-in.

Compiled Speed

10-100x faster than EVM interpreted bytecode. Real performance for real workloads.

🤖

Autonomous

Built-in triggers — no Chainlink Keepers, no Gelato, no third-party dependency.

🔄

Hot-Upgrade

Deploy new versions via transaction chain. No proxy patterns, no migration scripts.

🔒

FHE Native

Call FHE host functions directly — compute on encrypted data from your contract.

📦

Lightweight

~1-2 KB bytecode on-chain. Minimal storage cost, fast deployment.

ATSHI WASM vs. Other Runtimes

Feature Solidity (EVM) CosmWasm Solana (BPF) ATSHI WASM
LanguagesSolidity onlyRustRustRust, C, AS, Go
RuntimeInterpretedWASMeBPFCompiled WASM
Autonomous triggersNo (needs Keepers)NoNo (needs Clockwork)Native (4 types)
Hot-upgradeProxy hackMigrationNoNative
FHE host functionsNoNoNoZAMA + OpenFHE
SandboxingLimitedFullFullFull WASM

Write Your First Smart Contract

Open the Playground, pick your language, and deploy to testnet in minutes. No setup, no boilerplate — just code.