> For the complete documentation index, see [llms.txt](https://bulla-network.gitbook.io/bulla-network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bulla-network.gitbook.io/bulla-network/welcome-to-bullanetwork/bulla-protocol/how-does-it-work.md).

# How does it work?

There are two ways a user can create a Bulla Claim token.

1. Via the [BullaBanker](https://banker.bulla.network) interface.
2. Via the BullaClaim interface (coming soon)
3. Directly on the [smart contracts](https://polygonscan.com/address/0xbe08f907650503710d9247c5f5dcec9f5aea2c9a#code#L1581).

![Flow chart of possible actions on a Bulla Claim](/files/DwT6u7ozY6FGrsnOluNN)

### Bulla Claims - Technical Overview

Bulla Claims are inherently very simple. A step-by-step technical description of commerce via Bulla Claims are as follows:

1. A user creates a claim with a creditor and debtor for `x` amount.
2. A claim NFT is minted to the creditor.
3. The debtor or any other party can pay the creditor via the claim.
4. `X` amount of ERC20 tokens are transferred via the claim.
5. The claim is closed

To expound on this: consider the following example where Alice must invoice Bob.

1. Alice has done commerce with Bob. Alice now needs to invoice Bob for 60 DAI.
2. Alice uses the [BullaBanker](https://banker.bulla.network) interface to create a Bulla Claim for 60 DAI. The claim details are as follows:
   1. Creditor: Alice's wallet address.
   2. Debtor: Bob's wallet address.
   3. Due date: any future date (i.e. end of the month).
   4. Amount and token: 60 DAI.
   5. Attachment: an included IPFS hash pointing to Alice's SOW, receipt, deliverables, etc.
3. Alice creates the claim on and it is 1 CLAIM token is minted to her as a creditor. As a creditor, she can do with the NFT what she'd like; keep it and await payment, transfer it to another user or wallet, or even sell it on OpenSea to liquidate at a reduced price.
4. Since Alice chose to send an email notification to Bob about his invoice, Bob sees this and opens BullaBanker and pays the claim.
5. 60 DAI + a small fee leaves Bob's wallet and is transferred directly to Alice's wallet. The claim's status is now "Paid".


---

# 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://bulla-network.gitbook.io/bulla-network/welcome-to-bullanetwork/bulla-protocol/how-does-it-work.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.