Skip to main content
Schema: canton.core Table: fact_amulet_unlocks Type: Incremental

​
Description

Tracks unlocking/unstaking of locked amulets through exercise events. Joins to child Amulet created events to capture details of the newly created unlocked amulet.

​
Key Use Cases

  • Monitoring unstaking activity
  • Tracking unlock reasons and transaction types
  • Analyzing unlocked amounts and their destinations
  • Understanding validator unstaking patterns

​
Important Relationships

  • Counterpart to core__fact_amulet_locks
  • Joins parent unlock event to child Amulet creation event
  • Links to rounds via round_number and open_round_cid

​
Commonly-used Fields

  • unlock_action: Either ‘unlock’ or ‘expire_lock’
  • unlocked_amount: Amount being unlocked
  • owner: Party receiving the unlocked amulet
  • amulet_price: USD price at time of unlock
  • round_number: Round in which unlock occurred
  • unlock_reason: Metadata describing why unlock happened
  • locked_amulet_contract_id: Original locked contract
  • created_amulet_contract_id: New unlocked amulet contract

​
Columns

Column NameData TypeDescription
UPDATE_IDTEXTUnique identifier for the Canton update/transaction. An update contains one or more events and represents an atomic change to the blockchain state.
MIGRATION_IDTEXTCanton migration identifier. Used to track different phases or migrations in the Canton network’s evolution.
RECORD_TIMETEXTTimestamp when the update was recorded in the system.
EFFECTIVE_ATTEXTTimestamp when the event or update became effective on the blockchain. This is the canonical time for ordering and analyzing blockchain events.
EVENT_IDTEXTUnique identifier for the event within the Canton blockchain.
EVENT_INDEXTEXTOrdering index of events within an update. Events within the same update are sequentially numbered starting from 0.
CHOICETEXTThe choice/action/method being executed on a contract. Examples include ‘DsoRules_RequestVote’, ‘AmuletRules_Transfer’, ‘LockedAmulet_Unlock’, etc.
ACTING_PARTIESTEXTArray of party identifiers who are executing this action/choice.
UNLOCK_ACTIONTEXTType of unlock action: ‘unlock’ for normal unlock or ‘expire_lock’ for lock expiration.
OPEN_ROUND_CIDTEXTContract ID reference to an open mining round.
UNLOCKED_AMULET_CIDTEXTContract ID of the unlocked amulet from exercise result
AMULET_PRICETEXTUSD price of one amulet at the time of the event.
ROUND_NUMBERTEXTSequential number identifying a mining round in the Canton network.
UNLOCK_REASONTEXTMetadata describing the reason for an unlock operation.
TX_KINDTEXTTransaction kind metadata describing the type of transaction.
UNLOCKED_AMOUNTTEXTAmount of amulet being unlocked from a locked state.
CREATED_AT_ROUNDTEXTRound when the amulet amount was originally created
RATE_PER_ROUNDTEXTRate at which fees or rewards accrue per mining round.
OWNERTEXTGeneric party identifier for an owner. Specific context determines what is owned.
AMULET_CREATED_ATTEXTTimestamp when the new unlocked amulet was created
EVENT_TYPETEXTType of event: ‘created_event’ for contract creation or ‘exercised_event’ for method execution on existing contracts.
LOCKED_AMULET_CONTRACT_IDTEXTContract ID for a LockedAmulet contract.
CONSUMINGTEXTBoolean indicating whether this action consumes/archives the contract.
CREATED_AMULET_CONTRACT_IDTEXTContract ID for a newly created Amulet contract (typically after unlock).
FACT_AMULET_UNLOCKS_IDTEXTSurrogate key generated from event_id
INSERTED_TIMESTAMPTEXTTimestamp when the record was inserted into this table (Snowflake SYSDATE).
MODIFIED_TIMESTAMPTEXTTimestamp when the record was last modified in this table (Snowflake SYSDATE).