Asset wallets and records
Account activity you can follow
For an operations team, knowing a balance is not enough. They need to know which asset it is, which account holds it and which operation produced it. HOLD OS organizes wallets and records to answer exactly those questions.
Asset balances and cash, kept apart
Each account has a separate wallet for every asset it holds: Gold in a Gold wallet, Silver in a Silver wallet and each Custom asset in its own wallet. Alongside them, every account has one shared cash wallet.
Cash in HOLD OS is recorded in whole toman. Opening a Silver or Custom wallet never creates a hidden Gold wallet, and every new wallet starts from zero.
Account Owner of all the wallets below
- Gold wallet Gold balance in Gold’s unit and precision
- Silver wallet Silver balance in Silver’s unit and precision
- Custom asset wallet In the unit the institution defined
Shared cash wallet Whole toman, shared by the account’s assets
Records tied to account and asset
Every record in HOLD OS has two fixed coordinates: the account it was recorded in and the asset it concerns. Neither changes when someone switches pages, changes their selection or changes the default asset.
Seeing and acting on a wallet is also a matter of authority. Whether a user can view an account’s records or perform an operation on it depends on their role, the current account and the asset concerned.
Every balance has an explainable path
A wallet balance is the result of recorded events, so it is always possible to explain how it reached its current figure.
-
Start from zero
Every new wallet starts at zero; no balance appears without a recorded event.
-
Recorded event
An approved trade or a contract event records the change in the same wallet and asset.
-
Fixed identity
The event keeps the identity and unit it had when it was recorded.
-
Follow it back
Today’s balance can be traced to the events that produced it.
How operations relate to records
Not every operation affects a wallet in the same way. HOLD OS makes those differences explicit.
| What to evaluate | How HOLD OS approaches it |
|---|---|
| Trade request | Does not change balances until it is approved and recorded. |
| Approved trade | The result is recorded in the same account’s wallets, under the same asset identity. |
| Rent | An obligation separate from the contract principal; paying it never reduces the principal. |
| Physical receipt or return of principal | In leasing, it does not increase a wallet balance. |
A readable example
A customer of an institution holds Gold and Silver in one account. A request to buy Silver is recorded; until someone with authority approves it, the balances stay exactly as they were. Once approved, the result is recorded in that account’s wallets under the Silver identity.
Months later, if the institution changes its default asset, this remains a Silver trade, shown in the same unit. This is an illustrative example; it contains no real quantities, amounts or names.
See wallets and records in the product
In a walkthrough we examine the wallet structure and how records are followed, using your institution’s scenario.