diff options
| author | fiatjaf_ <fiatjaf@gmail.com> | 2025-01-31 13:01:27 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-31 13:01:27 -0300 |
| commit | 6e040513e06f336e9fc5344830e9232519afca33 (patch) | |
| tree | c994957af22553e0389b484dd34ef3524efd9472 | |
| parent | 1fe24a6149006649a471f2245ad8f66f87595498 (diff) | |
remove balance here too
Co-authored-by: Tiago Balas <eskema23@gmail.com>
| -rw-r--r-- | 60.md | 1 |
1 files changed, 0 insertions, 1 deletions
| @@ -50,7 +50,6 @@ Tags: | |||
| 50 | * `unit` - Base unit of the wallet (e.g. "sat", "usd", etc). | 50 | * `unit` - Base unit of the wallet (e.g. "sat", "usd", etc). |
| 51 | * `name` - Optional human-readable name for the wallet. | 51 | * `name` - Optional human-readable name for the wallet. |
| 52 | * `description` - Optional human-readable description of the wallet. | 52 | * `description` - Optional human-readable description of the wallet. |
| 53 | * `balance` - Optional best-effort balance of the wallet that can serve as a placeholder while an accurate balance is computed from fetching all unspent proofs. | ||
| 54 | * `privkey` - Private key used to unlock P2PK ecash. MUST be stored encrypted in the `.content` field. **This is a different private key exclusively used for the wallet, not associated in any way to the user's Nostr private key** -- This is only used for receiving [NIP-61](61.md) nutzaps. | 53 | * `privkey` - Private key used to unlock P2PK ecash. MUST be stored encrypted in the `.content` field. **This is a different private key exclusively used for the wallet, not associated in any way to the user's Nostr private key** -- This is only used for receiving [NIP-61](61.md) nutzaps. |
| 55 | 54 | ||
| 56 | The client or user MAY decide to put some tags either inside the encrypted `.content` or under the public `.tags`, `name` and `description`, for example. However, `d` MUST always be a public tag, and `mint` and `unit` must be public if the user intends to receive [NIP-61](61.md) nutzaps. | 55 | The client or user MAY decide to put some tags either inside the encrypted `.content` or under the public `.tags`, `name` and `description`, for example. However, `d` MUST always be a public tag, and `mint` and `unit` must be public if the user intends to receive [NIP-61](61.md) nutzaps. |