# Executor Reference Concepts ### **Executor Basic Concepts:** #### **Core Responsibilities** * Identify and submit GEB-related Bitcoin transactions to the network * Increase transaction processing priority by paying gas fees * Bear the risk of transaction failure (gas fees must still be paid for unsuccessful transactions) **Incentive Mechanism** * **Revenue Source:** Number of successfully submitted and verified valid transactions × reward coefficient per transaction * **Gas Strategy:** Paying higher gas can increase transaction ordering priority, but costs and benefits must be balanced * **Zero-sum Competition:** For identical transactions within the same block, only the first high-gas transaction receives rewards, other executors' gas payments are non-refundable ### Executor performance concepts: **Trust:** * **Meaning:** Trust represents a score reflecting the confidence in an executor's behavior audited by auditors. Its full name is Executor Trust. * **Calculation:** Weighted average according to the stake value of the auditor. * **Troubleshooting:** If this value deviates significantly from 1, observation is needed. If it decreases, check for updates in the corresponding `agere` codebase, run with more tips and remove `time.sleep` in miner.py, and verify the health of your VPS network and scripts. **Incentives:** * **Meaning:** Represents the proportion of earnings an executor receives. The sum of all executor incentives equals 1. * **Calculation:** It's calculated by the difference of Trust. --- # 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://documents.geb.network/learn/bitagere-guide/executor-reference-concepts.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.