Glossary OS

Plain meaning

Start with the shortest useful explanation before going deeper.

A deprecated Solana on-chain automation protocol (by Clockwork Labs, now sunset) that allowed developers to schedule and trigger smart contract instructions based on time (cron expressions) or on-chain conditions using a network of automation worker threads running alongside validators. Clockwork introduced the concept of Thread accounts that encoded trigger conditions and instruction targets directly on-chain, and while it has been discontinued, it pioneered the automation primitive model later explored by projects like Turbin3 and off-chain keeper bot architectures.

Mental model

Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.

Think of it as a building block that connects one definition to the larger Solana system around it.

Technical context

Place the term inside its Solana layer so the definition is easier to reason about.

RPCs, validators, snapshots, indexing, and network plumbing.

Why builders care

Turn the term from vocabulary into something operational for product and engineering work.

This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.

AI handoff

Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.

Clockwork (clockwork)
Category: Infrastructure
Definition: A deprecated Solana on-chain automation protocol (by Clockwork Labs, now sunset) that allowed developers to schedule and trigger smart contract instructions based on time (cron expressions) or on-chain conditions using a network of automation worker threads running alongside validators. Clockwork introduced the concept of Thread accounts that encoded trigger conditions and instruction targets directly on-chain, and while it has been discontinued, it pioneered the automation primitive model later explored by projects like Turbin3 and off-chain keeper bot architectures.
Related: Program Automation, Cron (Time-Based Scheduling)

Glossary Copilot

Ask grounded Solana questions without leaving the glossary.

Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.

Open full Copilot workspace

Question

Explain this code

Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.

Ask a glossary-grounded question

The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.

Concept graph

See the term as part of a network, not a dead-end definition.

These branches show which concepts this term touches directly and what sits one layer beyond them.

Branch

Program Automation

The pattern of scheduling and triggering on-chain program instructions based on time intervals, cron expressions, or conditional state changes without manual intervention. On Solana, automation was pioneered by Clockwork (now sunset) using on-chain Thread accounts and has evolved toward off-chain keeper bot architectures where backend services monitor chain state and submit transactions when trigger conditions are met.

Open term

Branch

Cron (Time-Based Scheduling)

A time-based job scheduling concept originating from Unix systems, where tasks are defined to run at specific intervals using cron expressions (e.g., '0 */6 * * *' for every 6 hours). In blockchain contexts, cron-like scheduling is used to trigger on-chain operations such as reward distributions, oracle updates, and automated rebalancing at regular intervals, typically implemented through off-chain keeper services or on-chain automation protocols.

Open term

Next concepts to explore

Keep the learning chain moving instead of stopping at one definition.

These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.

Infrastructure

Program Automation

The pattern of scheduling and triggering on-chain program instructions based on time intervals, cron expressions, or conditional state changes without manual intervention. On Solana, automation was pioneered by Clockwork (now sunset) using on-chain Thread accounts and has evolved toward off-chain keeper bot architectures where backend services monitor chain state and submit transactions when trigger conditions are met.

Open term

Programming Fundamentals

Cron (Time-Based Scheduling)

A time-based job scheduling concept originating from Unix systems, where tasks are defined to run at specific intervals using cron expressions (e.g., '0 */6 * * *' for every 6 hours). In blockchain contexts, cron-like scheduling is used to trigger on-chain operations such as reward distributions, oracle updates, and automated rebalancing at regular intervals, typically implemented through off-chain keeper services or on-chain automation protocols.

Open term

Infrastructure

DAS (Digital Asset Standard) API

A unified RPC API specification, originated by Metaplex and adopted by major RPC providers, that provides indexed, queryable access to Solana digital assets including regular NFTs, compressed NFTs (cNFTs), and fungible tokens through methods like getAsset, getAssetsByOwner, getAssetsByGroup, and searchAssets. DAS abstracts away the complexity of reading raw Metaplex account data and reconstructing compressed NFT state from concurrent Merkle trees, making it the standard NFT data layer for wallets and marketplaces.

Open term

Infrastructure

Blinks (Blockchain Links)

Client-side renderers and URL wrappers that convert Solana Actions endpoints into interactive, embeddable UI components — such as buttons, input fields, and transaction previews — that can appear inside wallets, browser extensions, and social media platforms without requiring users to navigate to a dApp. A Blink is essentially a URL prefixed with https://dial.to/?action= that signals to compatible clients to fetch and render the corresponding Action metadata, enabling one-click on-chain transactions from any webpage or feed.

Open term

Related terms

Follow the concepts that give this term its actual context.

Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.

Infrastructureprogram-automation

Program Automation

The pattern of scheduling and triggering on-chain program instructions based on time intervals, cron expressions, or conditional state changes without manual intervention. On Solana, automation was pioneered by Clockwork (now sunset) using on-chain Thread accounts and has evolved toward off-chain keeper bot architectures where backend services monitor chain state and submit transactions when trigger conditions are met.

Open term

Programming Fundamentalscron

Cron (Time-Based Scheduling)

A time-based job scheduling concept originating from Unix systems, where tasks are defined to run at specific intervals using cron expressions (e.g., '0 */6 * * *' for every 6 hours). In blockchain contexts, cron-like scheduling is used to trigger on-chain operations such as reward distributions, oracle updates, and automated rebalancing at regular intervals, typically implemented through off-chain keeper services or on-chain automation protocols.

Open term

Stay in the same layer and keep building context.

These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.

Infrastructure

RPC (Remote Procedure Call)

The JSON-RPC 2.0 protocol interface through which clients communicate with Solana nodes to query chain state, submit transactions, and subscribe to events. Solana exposes a rich set of HTTP and WebSocket endpoints (e.g., getAccountInfo, sendTransaction) that abstract direct peer-to-peer network participation, making RPC the primary integration point for wallets, dApps, and indexers.

Open term

Infrastructure

RPC Node

A Solana full node that stores ledger state and serves JSON-RPC and WebSocket requests from clients without participating in consensus or voting. RPC nodes must replay every transaction to maintain an accurate account state database, and high-throughput deployments typically run dedicated RPC nodes with large SSDs, high RAM (256 GB+), and high-bandwidth network connections to handle concurrent client load without impacting validator performance.

Open term

Infrastructure

RPC Methods

The enumerated JSON-RPC endpoints exposed by Solana nodes, covering account queries (getAccountInfo, getMultipleAccounts, getProgramAccounts), block and transaction retrieval (getBlock, getTransaction), cluster metadata (getEpochInfo, getSlot, getVersion), and transaction submission (sendTransaction, simulateTransaction). Methods accept a Commitment parameter (processed, confirmed, finalized) to control the recency-vs-safety tradeoff of returned data.

Open term

Infrastructure

getAccountInfo

An RPC method that returns the complete on-chain state of a single account identified by its base-58 public key, including its lamport balance, owner program, executable flag, rent epoch, and raw data payload encoded as base64 or base58. It is the most fundamental read primitive in Solana development and is called at the specified commitment level, with the data field being null if the account does not exist.

Open term