File Service
Network service that stores bytecode, fee schedules, and other artefacts under key-controlled files.
Pending schedule
Scheduled transaction that has not yet gathered sufficient signatures.
Schedule Service
Service that queues transactions for deferred execution once signature requirements are met.
expires with
Identifies the event that marks the expiration of a scheduled transaction.
has collected signature
Connects a scheduled transaction to signatures already obtained.
has collected signature count
Number of signatures collected so far for the schedule.
has execution
Associates a scheduled transaction with its execution once signatures complete.
has file content
Links a file to the payload stored within it.
has file id
Ledger identifier (e.g., 0.0.x) for a file.
has file key
Associates a file with the keys authorised to modify it.
has file memo
Memo describing file purpose or metadata.
has file size
Size of file contents in bytes.
has required signature count
Number of signatures needed before execution.
has schedule expiration
Timestamp at which the scheduled transaction expires.
has schedule id
Ledger identifier for a scheduled transaction.
has schedule memo
Memo describing the scheduled transaction purpose.
has schedule payer
Account identifier paying for schedule execution.
has schedule status
Enumerated status such as pending-signatures, executed, or expired.
performed by
Identifies the account that submitted the file update.
requires signature
Identifies accounts whose signatures are required for a scheduled transaction.
schedules transaction
Links a scheduled transaction artefact to the process that will execute once signatures are collected.
stores artefact
Indicates that a file stores an artefact such as bytecode or fee schedules.
updates file
Connects a file update process to the file being modified.
Bhash Ontology Working Group
Vocabulary for modelling Hedera File Service artefacts and Scheduled Transaction lifecycle states.
Hedera File and Schedule Services module
Phase 3 sprint module integrating File Service bytecode storage and scheduled transaction governance for CQ-COMP-004.
File content
Payload stored within a File Service file such as contract bytecode or fee schedules.
File key
Key that authorises file creation, update, and deletion actions.
Schedule execution
Process that executes a scheduled transaction once all required signatures are collected.
Schedule signature
Signature provided by an account approving a scheduled transaction.
File update
Process that amends file contents or metadata under the control of file keys.
File
On-ledger file storing bytecode, configuration, or metadata referenced by other services.
Scheduled transaction
Deferred transaction waiting for a quorum of signatures before execution.