# Account {% embed url="" %} thread.rs {% endembed %} On Solana, we often say that everything is an account. Threads are no different. A thread account simply holds the on-chain state needed to schedule and execute a series of static and/or dynamic instructions on Solana. ```rust pub struct Thread { /// The owner of this thread. pub authority: Pubkey, /// The bump, used for PDA validation. pub bump: u8, /// The cluster clock at the moment the thread was created. pub created_at: ClockData, /// The context of the thread's current execution state. pub exec_context: Option, /// The number of lamports to payout to workers per execution. pub fee: u64, /// The id of the thread, given by the authority. pub id: Vec, /// The instructions to be executed. pub instructions: Vec, /// The name of the thread. pub name: String, /// The next instruction to be executed. pub next_instruction: Option, /// Whether or not the thread is currently paused. pub paused: bool, /// The maximum number of execs allowed per slot. pub rate_limit: u64, /// The triggering event to kickoff a thread. pub trigger: Trigger, } ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.clockwork.xyz/reference/threads/account.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.