Skip to main content

Coco Glossary

TermDescription
actorA participant in an interaction (e.g., a user or logic). Actors own context where logic state can be stored.
assetA native digital item managed by the asset engine, with quantities tracked in actor accounts.
asset engineMOI subsystem that enforces safe asset access and transactions.
asset logicA Coco logic attached to an asset. It can call the asset engine directly and expose endpoints to other logics via interfaces.
atomic storageImplementation of storage in MOI where elements of complex objects (maps, arrays and classes) are accessible individually, so large data structures don't need to be transferred between network and PISA when logic is executed.
CocoCoco Programming Language is a highly readable, statically typed, indentation-based language for writing logics on MOI.
contextThe data on the actor. Each actor brings its own data into interactions so logics can compute with their data in the context of actors only, without the need to deal with irrelevant data of other participants.
depolorizingConversion of POLO binary data into a data structure (deserialization).
endpointFunction of a logic that can be invoked by an interaction. When multiple logics participate in an interaction, logics can invoke endpoints in other logics.
invocationA call to a logic’s endpoint within an interaction, including all participating logics and actors.
logicA Coco program that runs on MOI (analogous to a smart contract).
manifestA file that represents a logic. Coco compiler produces the manifest that can be deployed on MOI, so interactions can invoke endpoints on that logics.
MOIMOI : Context-aware massively parallel blockchain, the environment where Coco programs run.
PISAVirtual machine that executes logics, used by MOI. Coco produces logic manifests that PISA can execute.
POLOA custom binary format for data exchange in MOI, PISA and Coco. It's compact and assures deterministic encoding of collections.
polorizingConversion of data structure into POLO binary format (serialization).
statePersistent data of a logic, stored on the network. Logic can have logic state that resides with the logic itself and actor state that resides with actors. Each actor holds the data for multiple logics in its storage (context) and brings the data into interactions when the actor participates in an interaction.