Development Concepts

PulseVM uses the Antelope execution model (the lineage behind XPR Network, WAX, and Telos). If you've built Antelope/EOSIO contracts, it's the model you know; if you're coming from EVM, these are the ideas that differ most. Each page below is PulseVM-native; for the exhaustive C++ reference, the Antelope docs are canonical.

• Accounts & Actions — named accounts, contracts, and the actions they expose
• State & Tables — on-chain storage via multi-index tables
• ABIs — the interface that describes a contract
• Authorization & Inline Actions — require_auth, permission checks, and contracts calling contracts

Ready to write one? See the Rust, C++, or TypeScript quickstarts, and the host-functions reference.