---
title: "Niv 0.3.54"
description: "O que mudou no Niv 0.3.54 para desktop, lançado em 2026-10-10."
canonical: https://niv.md/pt-br/changelog/desktop/0-3-54
language: pt-BR
last_updated: 2026-10-10
---

# Niv 0.3.54

Desktop · 2026-10-10

As notas de cada versão são escritas em inglês.

- A note's History tab finds the same overlaps as Home
- What is and isn't encrypted, on an unlisted page
- Concurrent offline edits in an encrypted note are recorded as an overlap
- A member of an encrypted Space receives its notes and folders
- A Space waiting for a member is asked again, a member let in catches up, and plaintext_left counts only unsealed values
- Every Space an enabled account owns ends up encrypted
- Only the people who can let others in ask who is waiting
- The sealed-name client forwards calls synchronously
- The encryption surfaces get their polish
- End-to-end encryption is enabled per account, at runtime
- The interpreter probe waits for stderr long enough to name a missing interpreter
- An encrypted restore says its history follows on sync, and the History list meets contrast
- A device is named after its Mac until it is renamed
- A failed copy of a pasted sealed image is tried again
- A sealed image pasted from another Space is copied into this one
- The desktop says Ajustes everywhere
- Emails speak the recipient's language
- The encrypting stage starts and resumes migrations and names the note that stopped one
- A migration retires every public upload it replaced, in confirmed chunks
- Encrypted history: the diff checks generations from the base, and Home replays incrementally
- A second agent identifier for two-instance proofs
- Encrypted invitations read as held on every desktop surface
- Encrypted notes have versions, diffs, overlaps and since-your-last-visit on the desktop
- The migration re-uploads a note's public images sealed
- One migration pull at a time; a note-named stop gives the Space back
- The desktop publishes encrypted Spaces as device-built pages
- The desktop uploads and downloads sealed attachments
- The exported appTrpc has an explicit type
- One serialized config write per vault
- Engine mode read from status; the opened Space name is stored
- A let-in invitee sees the Space name without restarting
- Space names, history and Home open on the device
- Devices show their names, with Rename
- A device label is sealed only under the current account key
- The pt-BR encrypted pass says cifradas
- Note metadata, settings and rules are sealed on the device
- Encrypted creates use device ids and sealed names
- The socket typechecks again and clippy is clean
- The desktop seals and opens attachments
- Links are repaired on the device in encrypted Spaces
- A stopped encrypted Sync now reads as failed
- Sync now works in encrypted Spaces
- Closed encrypted notes push their changes
- The desktop seals names before they reach the server
- Closed encrypted notes catch up
- The sync engine's encrypted mode
- The desktop names its devices, sealed under the account key
- An open encrypted note syncs through the relay
- Unlock says why, and the upgrade promises no time
- The desktop understands content.sealed.touch
- Overlaps and restore checks run in the editor package
- The 'Encrypting your Spaces' stage
- The Space switcher never shows an empty emoji slot
- Version diffs and per-block authors run in the editor package
- The desktop understands keys.touch in the Space feed
- Key changes surface in the app
- Letting members in, one person at a time
- The desktop knows its own key fingerprint and device id
- An earlier account key signs only within the generations it was granted
- A refused recovery file is settled on disk
- The desktop half of the encrypted relay
- Removing a device calls the one server transaction
- The encryption screens present the wrap proof
- A recovery file the server refused is deleted
- A pin remembers whether the person let that member in
- The desktop lets members in and rotates Space keys
- The desktop proves the current wrap, and removing a device rotates the account key
- The encryption screens run on the real key commands
- The desktop pins members' account keys
- Wrap-auth proof for rotations and wrap replacements
- Rust Space keys: seal and open encrypted updates
- Rust rotation statements and sealed device labels
- An encrypted note's relay client and member snapshots
- Removing a device changes the account key, and key changes say what they mean
- The desktop key manager: keychain, unlock and signed wraps
- The encryption screens, built behind the switch
- The desktop's Rust crypto module
- One switch keeps end-to-end encryption off until it is ready

---

Mais: [Niv](https://niv.md/pt-br) · [Sobre](https://niv.md/pt-br/about) · [Contato](https://niv.md/pt-br/contact) · [Privacidade](https://niv.md/pt-br/privacy) · [Criptografia](https://niv.md/pt-br/encryption) · [Termos](https://niv.md/pt-br/terms) · [llms.txt](https://niv.md/llms.txt) · [English](https://niv.md/changelog/desktop/0-3-54)
