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.

IDcronAliasCron JobAliasCron Expression

Plain meaning

Start with the shortest useful explanation before going deeper.

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.

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.

Serialization, memory, data structures, and core engineering basics.

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

AI handoff

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

Cron (Time-Based Scheduling) (cron)
Category: Programming Fundamentals
Definition: 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.
Aliases: Cron Job, Cron Expression
Related: Program Automation, Clockwork
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.

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

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.

Branch

Clockwork

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.

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.

Infrastructure

Clockwork

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.

Programming Fundamentals

Curve25519

An elliptic curve designed by Daniel Bernstein for efficient Diffie-Hellman key exchange. It operates on a Montgomery curve over a 255-bit prime field, offering 128-bit security. Solana uses the related Edwards form (Ed25519) for transaction signatures. Curve25519 is favored for its speed, constant-time implementation, and resistance to timing attacks.

Programming Fundamentals

Crash Fault vs Byzantine Fault

Two failure models in distributed systems. Crash faults assume nodes either work correctly or stop entirely (fail-stop). Byzantine faults assume nodes can behave arbitrarily — sending conflicting messages, lying, or acting maliciously. Blockchains must tolerate Byzantine faults, requiring BFT consensus (like Solana's Tower BFT) that works even with up to 1/3 malicious validators.

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.

Infrastructureclockwork

Clockwork

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.

More in category

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.

Programming Fundamentals

Rust

A systems programming language emphasizing memory safety, zero-cost abstractions, and concurrency without a garbage collector. Rust uses an ownership model with borrow checking at compile time to prevent data races and null pointer bugs. It is the primary language for Solana program development (via Anchor or native solana-program crate) and the Agave validator client.

Programming Fundamentals

TypeScript

A statically typed superset of JavaScript that compiles to plain JavaScript. TypeScript adds type annotations, interfaces, generics, and enums to catch errors at compile time. It is the standard language for Solana client-side development—wallet adapters, dApp frontends, test suites, and SDK interactions (web3.js, Anchor client) are typically written in TypeScript.

Programming Fundamentals

JavaScript

The ubiquitous scripting language for web development, running in browsers and Node.js. JavaScript is dynamically typed and event-driven. Most Solana dApp frontends and scripts use JavaScript/TypeScript with libraries like @solana/web3.js. Node.js enables server-side JS for backend services, indexers, and bot development.

Programming Fundamentals

Node.js

A JavaScript runtime built on Chrome's V8 engine that enables server-side JavaScript execution. Node.js uses an event-driven, non-blocking I/O model. In the Solana ecosystem, Node.js is used for: running Anchor tests (Mocha/Jest), backend services, transaction bots, indexers, and CLI tools. npm/yarn/pnpm manage JavaScript package dependencies.