Scheduled
5 min read By NT²
Revoke what you already sent
Tech
After a share leaves your vault, “did they open it?” and “can I kill it?” are sender questions. The answers live in a local outbox—not a cloud mailbox of readable mail.
Tagged: architecture
19 posts
Scheduled
8 min read By NT²
Replica batch under the hood — packet shapes
Tech
Blind sync is easier to trust when you can picture the packet. The edge sees shapes, sizes, and progress—not titles, notes, or a searchable attic of your secrets.
Scheduled
9 min read By NT²
Benchmarks from a 10k-item OPFS vault
Tech
A large local vault is not proven by a slogan. It is proven by measuring the paths people actually use—first page after unlock, debounced search, FTS versus filter queries—and by being honest about what those numbers do not mean.
Scheduled
8 min read By NT²
Offline-capable is not sync later if lucky
Tech
Many apps call themselves offline-capable when they mean a read-only cache and a queue that hopes the tower returns. A local-first vault puts full CRUD on the device first. Sync is an optional second path.
Scheduled
8 min read By NT²
What the Workers are allowed to see
Tech
Zero-knowledge is not a slogan about HTTPS. It is a permission list for the edge: what Workers may store, route, and bill for—and what they are never allowed to learn.
Scheduled
8 min read By NT²
.nt2backup as a sovereignty format
Tech
Local-first only means ownership if you can leave with an encrypted snapshot the cloud never had to hold. .nt2backup is that snapshot: portable vault profile sections and sealed payloads in a file you control.
Scheduled
8 min read By NT²
Vault profile is section KV, not one mega-row
Tech
Salt, Key DID public material, sync cursors, and onboarding prefs are not one fat SQL row. They live as named vault profile sections—so backup, sync, and unlock can each touch only what they need.
Scheduled
8 min read By NT²
Schema v60 and incremental migration
Tech
A local vault is a real SQLite database on your device. When the product ships schema v60, launch-era vaults must upgrade in place—not force a wipe because the CREATE statement changed in the source tree.
Scheduled
8 min read By NT²
Wrong password must fail closed
Tech
Unlock is not a best-effort decrypt of everything you own. NT² checks a small local verifier first. Wrong password fails closed: the vault stays locked, and the UI stays honest.
Scheduled
9 min read By NT²
Selective SSI — not a general DIDComm wallet
Tech
Self-sovereign identity is useful when you take the parts that fit a zero-knowledge vault—and refuse the parts that turn the product into a general DID wallet.
Scheduled
9 min read By NT²
Relay indexes ciphertext; Inbox stays local
Tech
A cloud can help deliver sealed packages without becoming the place where pending shares live as readable mail. Relay indexes ciphertext. Inbox stays on the device.
Scheduled
8 min read By NT²
One unlocked vault per tab — by design
Tech
Opening the same vault in two browser tabs is normal. Letting both tabs write the same on-device SQLite file is not. NT² Vault elects one Writer and keeps every other unlocked tab as a follower.
Scheduled
8 min read By NT²
FTS5 for titles; table scan when filters win
Tech
Local search is not one query shape. Free-text wants a full-text index on titles and search text. Category, trash, archive, and similar filters want ordinary table predicates. The product switches strategy so the UI never has to ship the whole vault into memory to feel searchable.
Scheduled
8 min read By NT²
Never load the whole vault into Svelte state
Tech
A local vault can hold thousands of structured items without becoming a giant in-memory array. The durable store stays in SQLite. The UI holds only a paged window of lightweight list rows, rendered through a virtual list.
Scheduled
10 min read By NT²
The account database must not become a password oracle
Tech
An account table can contain no plaintext vault items and still create a dangerous password-testing surface. We removed the columns that could turn a database copy into an offline guessing or recovery system.
Scheduled
9 min read By NT²
One sync hub for one vault identity
Tech
A vault does not need to enter a shared plaintext mailbox to sync. Its public cryptographic identity can name a dedicated edge coordinator that notifies replicas and points them to encrypted frames it cannot open.
Scheduled
9 min read By NT²
Blind replica sync on the edge
Tech
Sync does not have to turn a local vault into a cloud database. The edge can identify an account, store opaque replica frames, and deliver updates without learning what those updates contain.
9 min read By NT²
The KDF salt stays on your device
Tech
A salt is not a secret. Still, where it lives changes who can assemble a password-guessing system. NT² keeps the KDF salt and password verifier with the local vault, so unlocking begins and ends on the device.
6 min read By NT²
Why host a heavy server when a PWA can do everything locally? Built a zero-server privacy vault.
Tech
In the era of massive cloud-first applications, we often overlook a powerful alternative: the Progressive Web App (PWA). Why maintain a heavy, expensive, and potentially vulnerable server infrastructure when the modern browser is capable of running a full-featured, secure, and high-performance application entirely on the user's device?