> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-primitives-digital-signatures/bsv-and-digital-signatures/summary-of-bsv-transactions.md). # Summary of BSV Transactions Understanding BSV transactions can feel overwhelming at first. Let’s break down the key points covered so far in a simpler way. ### 1. Digital Signatures in BSV All **BSV transactions** are signed using **ECDSA (secp256k1)**. This ensures that only the rightful owner of the private key can authorize a transaction. ### 2. Inputs and Outputs Transactions can have **multiple inputs and outputs**. * Each **input** contains an **unlocking script**. * Each **output** contains a **locking script**. Think of the output’s locking script as a digital padlock, and the input’s unlocking script as the matching key. ### 3. Signature and Verification The process of **signing and verifying** a transaction is handled through **arguments in script**. This ensures that signatures are checked directly within the Bitcoin system, without relying on outside validators. ### 4. Locking Scripts A **locking script** in the transaction’s output ties the funds to a **public key**. This means only the person holding the corresponding private key can later unlock and spend those funds. ### 5. Unlocking Scripts The **unlocking script** in the transaction input provides proof of control. It contains a **signature** created with the **private key** that corresponds to the public key used in the locking script. ### 6. Signature Format in BSV BSV transactions use the format **\[DER, SIGHASH]** instead of just r,sr,s. * **DER** encodes the signature values. * **SIGHASH flags** specify which parts of the transaction (inputs and outputs) are signed. This adds flexibility and precision in transaction validation. ### Key Takeaway BSV transactions are secured by **ECDSA signatures** and a system of **locking and unlocking scripts**. The combination of these scripts ensures that only the rightful key holder can spend funds, while the **SIGHASH format** provides fine control over what parts of a transaction are signed and verified. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-primitives-digital-signatures/bsv-and-digital-signatures/summary-of-bsv-transactions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.