Skip to content
Satnam SatoshiIn service of humanityFind your place ↗
Menu

Sikh Bitcoin · Expert · Lesson 19 of 21

Treasury accounting and restricted funds

Make obligations and permissions visible beside asset balances.

About 14 minutes with practice. You only need something to take notes with. No real wallet details or payments are part of this lesson.

Course contents · Lesson 19 of 21
  1. Threat model before tools
  2. Design a custody architecture
  3. Entropy, mnemonics and passphrase tradeoffs
  4. Hardware signing and trusted displays
  5. Multisig and independent control
  6. Recovery and continuity across people
  7. Coin control and privacy tradeoffs
  8. Lightning operations and recovery
  9. Payment operations and reconciliation
  10. Native bitcoin and wrapped claims
  11. USDC, reserves and redemption
  12. Identify a Morpho market precisely
  13. Oracles, prices and measurement risk
  14. LTV, liquidation and nonlinear losses
  15. Variable rates and growing debt
  16. Vaults, allocation and exit liquidity
  17. Arc, Base and cross-chain dependencies
  18. Allowances, signing and simulation
  19. Treasury accounting and restricted funds
  20. Incident response with clear human authority
  21. Capstone: a defensible treasury design

What you will learn

  • Separate holdings, valuation, liabilities and restricted purposes.
  • Design a human-accountable reconciliation record.

A balance is only one part of the story

A community ledger needs asset quantities, valuation methods, obligations and permitted uses. An increase in a BTC price estimate is different from a donation arriving. Borrowed USDC creates both an asset and a liability; it is not donation income. Funds restricted to food purchases cannot silently become experimental collateral because a dashboard offers a lending feature.

Reconcile evidence without exposing people

Maintain dated records that connect authorized decisions, payment evidence and bookkeeping entries. Public reporting can show aggregate receipts and expenditure while protecting guests, volunteers and donors. A blockchain transaction does not prove that meals were served or that a particular person consented to publication. Those are separate human records with their own verification and retention rules.

Assign accountable roles

In a fictional treasury, a human owner approves policy, authorized signers review spending and a separate reviewer reconciles records. An agent can flag mismatches and prepare explanations from permitted data. It must not infer permission to allocate capital or claim to manage funds. Build a report with separate columns for available operating funds, restricted balances, outstanding liabilities and uncertain valuations. Real accounting and reporting obligations require appropriate qualified review for the organization and jurisdiction.

Practice on paper

A fictional ledger receives 1,000 USDC from a loan and lists it as 1,000 of new community wealth. What correction is needed?

Reveal the worked answer

Record the received asset and the corresponding debt, then account separately for costs and any restricted purpose. Gross holdings increased, but net assets did not increase by 1,000 merely because the organization borrowed.

Check your understanding

Choose an answer in your head or on paper, then reveal the explanation. Retry whenever you like. Answers are not submitted or scored; completion marks are your own learning notes.

1. Does an on-chain transfer prove a meal was delivered?

  • Yes
  • No
Reveal answer 1

No. Service evidence is separate from payment evidence.

2. May an agent reinterpret restricted donations as trading capital?

  • Yes
  • No
Reveal answer 2

No. Purpose, authorization and human accountability remain binding.

Take this with you

Report what is owned, owed, available and authorized for use.

Your learning, at your pace

Read every lesson freely. Optional progress tracking needs JavaScript and browser storage; it does not require an account or wallet.