> For the complete documentation index, see [llms.txt](https://docs.giwa.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giwa.io/giwa-chain/en/giwa-ecosystem/bojagi.md). # Bojagi GIWA’s privacy protocol protects sensitive transaction information while keeping transactions verifiable. Bojagi is a privacy protocol built on EVM smart contracts, designed to enable private digital asset transfers within the GIWA ecosystem. On public blockchains, wallet addresses, asset balances, transfer amounts, counterparties, and transaction histories can be publicly visible. When linked together, this information can reveal not only individuals' financial activities but also sensitive business information, such as settlement records, payroll details, and relationships with business partners. *** #### Verifiable Privacy Once assets are deposited into Bojagi, transactions take place by transferring ownership of those assets within the protocol. Bojagi uses zero-knowledge proofs to prove the validity of these transactions without publicly revealing sensitive transaction information, including sender and recipient details and transfer amounts. Smart contracts verify these proofs to confirm conditions such as whether the sender is authorized to spend the assets. They also check that the assets have not already been spent, preventing double-spending. Bojagi is designed with both privacy and compliance in mind. It preserves transaction verifiability and integrity while allowing access to transaction history to be managed separately from the authority to spend assets. It enables individuals and businesses to transfer digital assets without publicly disclosing sensitive details about their financial activities or counterparties. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.giwa.io/giwa-chain/en/giwa-ecosystem/bojagi.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.