The Scripting Language: Forth-like Logic and Opcodes

37. The Scripting Language: Forth-like Logic and Opcodes

Every Bitcoin transaction contains a tiny "Program" written in a language called Script. This language is "Stack-Based," meaning it works like a pile of plates. You put things on the pile (PUSH) and take them off (POP). This language is intentionally "Simple" to prevent people from writing "Infinite Loops" that would crash the network. It is the "Logic of the Ledger." It is the "Grammar of the Gain." It is the "Syllables of the Sovereignty."

The Interpreter Logic

In src/script/interpreter.cpp, the node "Runs" the program. It executes commands like OP_DUP, OP_HASH160, and OP_EQUALVERIFY. If the program ends with a "True" value, the transaction is valid. It is the "Judgment of the Joint."

/**
 * Executes a Bitcoin Script program.
 * Verifies the conditions for spending a transaction.
 */
bool EvalScript(vector<vector<unsigned char>>& stack, const CScript& script)
{
    // Walking through every "Opcode" (Command) in the script.
    while (pc < script.end()) {
        // Executing the command (e.g. OP_ADD, OP_CHECKSIG).
        ExecuteOpcode(opcode, stack);
    }
}

Explaining the Code: The Logic of the Lock

1. ExecuteOpcode: This is the "Action." The node does exactly what the script says. It adds numbers, hashes data, or checks signatures. It is the "Robotic Obedience" of the code. It is the "Certainty of the Script."

2. stack: The "Workspace." It is a temporary memory where the node does its math. Once the script is finished, the workspace is deleted. It is the "Ephemeral Mind of the Transaction." It is the "Sand of the Scribe."