Anoma Developer Documentation
  • Overview
  • Build
    • Getting Started
    • Your First Anoma App
      • Define a Resource
      • Write a Transaction Function
      • Write a Projection Function
      • Run your App
    • Anoma App Examples
  • LEARN
    • Overview
    • State Model
      • Model Comparison
    • Resource Machine
      • Information Flow Control
    • Resources
      • State
      • Logic
      • Kind
      • Lifecycle
    • Transactions
      • Delta
      • Actions
      • Balanced Transactions
      • Intents
    • Applications
      • Backend
      • Interface
    • Services
      • Indexing
      • Solving
Powered by GitBook
On this page
  1. LEARN
  2. Transactions

Actions

This page describes the Action object and its purpose.

PreviousDeltaNextBalanced Transactions

Last updated 2 months ago

Actions separate the transaction, i.e., consumed and created resources and related data, into distinct contexts. For example, one action can transfer coins from Alice to Bob, whereas another one transfers coins from Carol to Dave.

Resource logics of created and consumed resources can only see and relate to other resources if they are part of the same action. This context separation is important to compose transactions with each other without causing interferences.

The underlying action object contains standardized data fields, which are defined in the .

Anoma specs