KVStore

Choose wallet-backed key-value storage for small user-owned app records, with a current LocalKVStore guide for fees, recovery and concurrency.

Key-value storage can keep small application records with the user's BRC-100 wallet instead of in a browser cache or an app-owned database.

Start with LocalKVStore: a complete SDK 4.0.0 example for reading, saving and removing encrypted values backed by wallet-tracked PushDrop outputs. The guide covers fees, approval, recovery, privacy and the limits of per-instance locking.

Saving on-chain state is a real wallet action. Keep the wallet's data/storage recovery available, read important writes back before acknowledging them, and do not treat separate-device updates as an atomic distributed transaction. Use overlays when public multi-user discovery is the goal.

In This Section

Local

Use SDK 4.0.0 LocalKVStore to read, save and remove encrypted wallet-backed values; understand fees, recovery, privacy and cross-device conflict limits.

Read more
Was this page helpful?