Scheduled
5 min read By NT²
A proximity session is not a peer connection
Tech
Connecting beside someone is a short-lived session. Recognizing them as a vault contact—and accepting a share into your vault—are still separate acts.
Tagged: zero-knowledge
26 posts
Scheduled
5 min read By NT²
Share file, deep link, and machine-handoff passphrase
Tech
Ciphertext and the secret that opens it should not travel as one convenient email. NT² splits carriers—file or link—from OOB passphrase delivery, and treats Strong as machine-handoff.
Scheduled
5 min read By NT²
Delayed legacy release is not password recovery
Tech
Estate and emergency access tempt products to hold a second key “just in case.” NT² refuses that oracle. Legacy is a sealed package on a delay—not a support console unlock.
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.
Scheduled
6 min read By NT²
A peer connection is not a phone contact
Tech
Sharing to “someone in Contacts” only works if the row holds encryption material for that vault—not a phone number you hope matches the right person.
Scheduled
4 min read By NT²
Searchable metadata, sealed field values
Tech
A vault that cannot find a title is unusable. A vault that full-text indexes every password on a server is not a vault. The boundary is projected metadata versus sealed field values.
Scheduled
6 min read By NT²
Slots, not a blank page
Tech
A passport, a bank account, an API key, and a seed phrase are not the same kind of text. A vault that treats them as one blank page will always ask you to remember the structure yourself.
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
8 min read By NT²
Threat model, 2026: browsers and extensions
Tech
Threat models age with browsers. This 2026 refresh keeps the residual risks named—XSS, unlocked theft, hostile extensions, origin supply chain—and checks which defenses still hold when the client world moves.
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²
XSS steals sessions elsewhere; here keys are non-extractable
Tech
A vault that advertises invincibility is selling theater. NT² names the residual risks—XSS while unlocked, a stolen unlocked device, a hostile extension—and designs so those failures do not also become password oracles or exportable key dumps.
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²
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²
CBF is how structured fields leave RAM
Tech
A credential is a map of fields while you edit it. The moment those fields must survive a lock, a restart, or a replica, they need a portable ciphertext shape—not a JSON dump waiting for the next reader.
Scheduled
9 min read By NT²
Auto-lock is a memory hygiene problem
Tech
Encryption at rest is incomplete if the decrypted key handle outlives the unlocked session. NT² treats auto-lock as memory hygiene: non-extractable CryptoKeys, in-memory only, cleared on idle, refresh, and tab close.
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²
Share passphrase ≠ master password
Tech
A share that opens with the same secret that unlocks the vault is not a handoff. It is a remote unlock of everything. NT² keeps those boundaries apart.
Scheduled
9 min read By NT²
Challenge–response, not bearer email
Tech
Cloud services often treat an email inbox as the root of an account. An encrypted vault needs a different proof: control of a signing key, shown by answering a one-time challenge.
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²
No password reset, by design
Tech
“Contact support to reset your password” sounds reassuring. For an encrypted vault, it also reveals who ultimately controls access. NT² chooses a harder promise: recovery material stays with you, not our help desk.
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?