Glossary
A list of some unfamiliar words and phrases found throughout Entropy documentation.
Account
A unique public and private key pair that can hold, send, and receive digital assets. The account essentially contains all the information associated with a specific program for a particular user or entity. An account is established with an admin key which can assign capabilities to device keys.
Admin key
A key that allows you to deploy programs and modify the settings of those programs. Admin keys cannot request signatures. This key must be funded to perform some actions.
Adapter
Plugins that provide support for different chains and program configurations. For example, an adapter can define a specific hashing function to use when signing. Different chains have different signing algorithms; this allows us to support them all.
Application chain
A blockchain that is exclusively designed for a single application, unlike a public blockchain designed for multiple apps. Also called an application-specific blockchain, or appchain.
Autonomous agent
A program designed to act independently, capable of executing tasks and making decisions based on predefined rules or algorithms. Autonomous agents are seen as key players in the evolution towards digital environments where AI and blockchains intersect, often called autonomous worlds.
Autonomous agents are sometimes also called intelligent programs.
Consumer key
A synonym for a device key or deploy key.
Device key
A key that can request signatures from Entropy Programs. By default, device keys cannot install or modify the Programs settings. However, Programs can be given admin-key privileges. A device key does not need to hold funds in order to perform actions.
Entropy chain
An application-specific layer-1 blockchain to coordinate distributed signing.
Entropy network
The set of Entropy validators.
Intelligent program
A synonym for an autonomous agent.
Partition
Also called a signing subgroup, a subgroup is a set of threshold signing servers that all hold identical key shares. To sign a message, one member of each subgroup must participate. The Entropy chain assigns new threshold signing servers to a subgroup.
Program
The logic defining what conditions a threshold signing server (TSS) should participate in signing a particular transaction or message. Programs are compiled into WebAssembly blobs that are uploaded to the blockchain and can be updated by subsequent authenticated, valid transactions.
Programs run when a device key requests a signature from the Program. Each Program returns true or false. If the Program returns true, the Entropy Network executes signing, and a signature is returned to the requesting device key.
Program developer
Refers to the human or humans using the Entropy Network to build and deploy programs.
Program dev key
An authorization key that permits its holder to deploy Programs for installation onto the Entropy blockchain by admin keys. Program dev keys do not need to be registered.
Registration
The process of establishing an Entropy account. Registered accounts can be initialized with Programs and modify those Programs later.
Session
An on-chain session is 2400 blocks or about four hours.
Signature request account
The account on the Entropy chain that is used to initiate signature requests.
Signing committee
A set of threshold signing servers that have been selected to participate in signing a particular message. This is composed of validators from different signing subgroups.
Signing subgroup
A set of threshold signing servers that all hold identical keyshares. To sign a message, one member of each subgroup must participate. The Entropy chain is responsible for assigning new threshold servers to a subgroup.
A signing subgroup is also called a partition.
SS58
The default Substrate address format. The SS58 encoded address format is based on the Bitcoin Base-58-check format but with a few modifications specifically designed to suit Substrate-based chains.
TSS account
A threshold signature server account is the identifier for an Entropy chain account belonging to a given threshold signing server. These servers are sometimes referred to as threshold signing servers.
Threshold signing
A cryptographic technique that allows a group of participants to collectively produce a digital signature on a message without any single participant having access to the complete private signing key. The private signing key is divided into multiple shares, with each participant holding one share. A predetermined threshold number of shares (e.g., 3 out of 5) must be combined to produce a valid signature. This way, no single entity possesses the entire private key.
Threshold server
An instance of the Entropy threshold signature server.
Transaction
A transaction is a specific request submitted for inclusion on the Entropy blockchain. It can contain a program or account registration, modification, or any other data that a user, like a program developer or autonomous agent, wants to have signed and validated by the Entropy Network.
User
Refers to whoever is using the Entropy network to sign transactions or messages. This may be an individual, an organization, or some other entity.
Validator
A device running both an _Entropy chain node_and a threshold signing server.
Wallet
A program or application that stores and manages a user’s tokens. Wallets hold the public and private keys that provide access and control over a user’s assets. Since Entropy is built on the Substrate blockchain, most Substrate wallets should be compatible with Entropy.