CRK, Bundles, Checksums, and Sync Queue
realPortable node replication and tamper-evident offline transfer.
Purpose
CRK view handles kit tiers, export/import bundles, SHA-256 checksum validation, cryptographic receipts, and the live offline sync queue.
When to Use
- Before moving data by USB
- After completing major interventions
- When flushing queued Nostr sync events
- When cloning or teaching another node
Best First Action
Export a bundle after a meaningful work session, then verify the checksum on import at the receiving node.
Content
Purpose
CRK view handles kit tiers, export/import bundles, SHA-256 checksum validation, cryptographic receipts, and the live offline sync queue.
When to Use
- Before moving data by USB
- After completing major interventions
- When flushing queued Nostr sync events
- When cloning or teaching another node
Best First Action
Export a bundle after a meaningful work session, then verify the checksum on import at the receiving node.
Best Practices
- Do not import bundles with failed checksums.
- Keep Nostr disabled until you intend to publish.
- Use owned keys in production, not ephemeral localStorage keys.
- Record receipts in History.
Common Mistakes
- Assuming export equals backup if the file is never copied off-device.
- Clearing the sync queue before confirming receipt.
- Treating one relay publish as durable federation.
Next Steps
- Flush queue when connected.
- Review Cryptographic Intake Ledger.
- Print or export knowledge-base guides with the bundle.
Best Practices
- Do not import bundles with failed checksums.
- Keep Nostr disabled until you intend to publish.
- Use owned keys in production, not ephemeral localStorage keys.
- Record receipts in History.
Common Mistakes
- Assuming export equals backup if the file is never copied off-device.
- Clearing the sync queue before confirming receipt.
- Treating one relay publish as durable federation.
Next Steps
- Flush queue when connected.
- Review Cryptographic Intake Ledger.
- Print or export knowledge-base guides with the bundle.