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. Applications

Backend

This page explains how resources constitute the application backend.

PreviousApplicationsNextInterface

Last updated 4 months ago

Resources are not formally associated with applications. However, resources related to an application can be identified and queried by their kind (see Indexing).

Accordingly, consumed resources constitute historical application state, whereas created (i.e., unconsumed) resources constitute the current application state. The resource logics associated with the current application state constrain the future application state space that the application can transition into via transactions.

Example: Token Logic Constraints A token resource might require authorization (usually a signed message) by its

  • (1) originator when created for the first time or

  • (2) current owner when transferred.

Additionally, the token can also ensure a fixed supply, which means that the total quantity of all resources of this specific kind cannot change.

Instead of manually constructing transaction objects creating and consuming resources, users interact with an .

application interface
Resources being created and consumed in a transaction.