> 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/bsv-theory/combining-and-splitting-value/dynamically-sized-coins.md).

# Dynamically Sized Coins

> "Although it would be possible to handle coins individually, it would be unwieldy to make a separate transaction for every cent in a transfer."
>
> \- Satoshi Nakamoto, Bitcoin Whitepaper

![](/files/Q7LEi8r0Mdv50ynpqz7F)

Each time a bitcoin transaction takes place, one or more unspent transaction outputs are gathered into the transaction as inputs and spent into a new combination of outputs scripts. A Bitcoin transaction can handle as many or as few Satoshi tokens as are needed by the user and supported by network nodes.

Without this ability to merge and split outputs via a single transaction, the requirement to sign a new output for each satoshi in the transaction would make it economically unfeasible to manage the ledger. This approach gives the necessary balance required to manage bitcoins on the ledger without creating an undue burden through breaking down the outputs into arbitrarily sized pieces.


---

# 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/bsv-theory/combining-and-splitting-value/dynamically-sized-coins.md?ask=<question>&goal=<endgoal>
```

`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.