---
# System prepended metadata

title: Jeremiah

---

* https://app.integration.knoxnetworks.io/issuers/view/clczcturj000w0ir54iphh0b1/wallets


# Jeremiah
## High Level Context
* As you know CPFS always represent a fixed denomination. In order to make a payment of any arbitrary amount you need to have the exact denoms in your wallet, and if you dont have the exact denoms you cannot make the payment. 
* The Funds change request addresses this with a new Funds Change Request txn that allows a wallet to obtain the right denoms needed from and a new Treasury service that can actually fulfil this request
* We’ve introduced a new Funds Change transaction type for this purpose.
* Importantly, the FC Request triggers and uses 2 Simple Payment Transactions to obtain the change. This is important because it shows how the foundational simple payment can be used by other transactions. 
* We use the “Related transaction" capability to link the Funds change with the Simplepayment that actually gets the change

## Two ways you can ask for change
* For a SP where you don't have the right denominations, you get a button to request change
* If you just want to obtain change directly from the wallet
* The input to the request should always be an amount you would like to pay, and the system will figure out what is the smallest denom you need to break in order to make that payment (in combination with other denoms that already exist in yout wallet)

## Actions
* give money from issuer vault exactly $500 (or preload with single $500)
* give Bob $250 -fails-
* request FC for $250 exact amount
    - mention that it is selecting smallest promissory that it needs
* show promissory amount
* give Bob $250 -succes-

# Jason
## Actions
* [Present funds change diagram](https://github.com/knox-networks/core/blob/196f33db2c2c96ac2525f144baf6a9dc7095a111/docs/design/funds-change-state-machine-simple.md#L13)

# Mikhail
## Context
* we don't always have the right denominations to fulfill payments
* how this extends the current functionality
* From treasury's perspective

## Actions
* show the mermaid diagram
* open `psql` 
* `select * from transactions  order by created desc limit 3;`
* `select * from transactions  where uetr = 'eb0490dd-19b7-439f-936a-e0e922f30bd4';`
* `monetae get verifier "https://treasury.integration.knoxnetworks.io:443"`
* first simple payment has one promissory id
* second SP has multiple promissory IDs

## Given 3 uetrs
* `uetr1`: `FundsChangeRequest` started by Alice
* `uetr2`: `SimplePaymentRequest` started by Alice
* `uetr3`: `SimplePaymentRequest` started by Treasury

```mermaid
sequenceDiagram
    title Funds Change flow
    autonumber
    participant A as Alice<br>TransactionClient
    participant T as Treasury<br>TransactionClient
    A->>T: Funds Change Request<Transaction ID 1>
    T->>A: Funds Change Ack<Transaction ID 1>
    A->>T: Simple Payment<Transaction ID 2>
    T->>A: Simple Payment<Transaction ID 3>
    A->>A: <Transaction ID 1>Starter: COMPLETED<br> | 
    T->>T: <Transaction ID 1>Responder: COMPLETED<br> |
```