Recover the private key for a historical Bitte or Mintbase NEAR passkey wallet using the passkey you already have. You do not need the old wallet website or its former backend which have both been shutdown suddenly, without any migration process.
Use at your own risk. This app is not affiliated with Bitte, Mintbase, NEAR, or any password manager. Password-based wallets and Windows/Safari launchers are not supported. There is no independent security audit. See privacy and limits and historical implementation evidence.
The app runs on your Mac. It never uploads the recovered NEAR private key and does not move funds, add keys, or modify your passkey.
- A Mac running macOS 13 or newer. Apple Silicon and Intel builds are included; Intel execution still needs validation.
- Google Chrome installed in Applications.
- Your NEAR account name, such as
example.near. - The original passkey created for
wallet.bitte.aiorwallet.mintbase.xyz.
A newly created passkey or an ordinary password cannot replace the original wallet passkey.
Download the ZIP ending in -macos-universal-preview.zip from Releases. Code → Download ZIP and Source code (zip) contain source code, not the ready-to-open app.
This is an experimental preview, ad-hoc signed and not notarized by Apple. macOS may block the first launch. Real provider/device compatibility and Intel execution still need validation. The app includes Node, so you do not need Terminal or a separate Node installation to use it.
- Extract the app ZIP and move Bitte Local Recovery.app to Applications.
- Double-click it. If macOS says the developer cannot be verified or Apple cannot check it, close that alert.
- If you trust this release, open System Settings → Privacy & Security, scroll to the blocked-app message, choose Open Anyway, and confirm Open. This creates an exception for this app. See Apple's opening instructions.
- Choose your passkey provider and follow the recovery steps below.
If macOS says the app is damaged or will harm your computer, stop rather than overriding that alert. Keep Gatekeeper enabled and leave Chrome certificate warnings intact. A SHA-256 checksum and file manifest accompany the download; they help detect changed files but are not an Apple signature or security audit.
You can also build and run from source:
Install Node.js 22 or newer (which includes npm). Chrome must also be installed as described above.
npm install
npm run buildYou can now run recovery directly from Terminal.
npm startThis opens Chrome using Apple Passwords mode. For another provider, specify it when starting; for example, Google Password Manager:
npm start -- --provider=googleProvider IDs are apple, google, 1password, bitwarden, proton, dashlane, other, security-key, and phone. Keep Terminal open during recovery. When finished, press Control+C in Terminal to stop the servers and close the dedicated Chrome process. Follow the recovery steps below; the Quit Recovery step is replaced by Control+C when running from Terminal.
- Choose your passkey provider. Select where the original passkey is stored and click Open Recovery. The app opens a separate Chrome profile for this provider.
- Set up the provider if needed. Google Password Manager users sign in to the correct Google account in that Chrome profile. Extension-manager users install their provider's official Chrome extension and unlock it. The page shows instructions. Enter passwords and PINs only in your provider's own interface; this app never asks for them.
- Choose your wallet. Enter the NEAR account name and choose the website shown on the passkey. Find the public access keys, select a FullAccess key, and click Prepare recovery. If there are several keys, you can try another in a new session.
- Use the existing passkey. Confirm the page says Local origin ready. Apple Passwords and hardware-key modes ask you to disconnect internet. Other modes can stay online for provider authentication. Confirm the readiness checkbox and click Use existing passkey.
- Save only a matching key. If the page reports a match, click Save recovered key. Choose a local folder outside iCloud Drive, Dropbox, Google Drive, or other synced storage. The file is unencrypted and gives control of your wallet. Keep it private.
- Quit Recovery. The app stops its servers and closes the Chrome process it opened. Verify all recovery windows have closed. For offline modes, do this before reconnecting internet.
The app preserves your passkeys and browser profiles. It only offers a download after the reconstructed key matches the selected existing public key.
Setup options include Apple Passwords, Google Password Manager, 1Password, Bitwarden, Proton Pass, Dashlane, other compatible managers, hardware security keys, and a passkey on your phone.
These are integration options, not a promise that every provider/version works. Provider setup has synthetic test coverage; genuine provider/device compatibility still needs validation. Internet access for a provider does not cause this app to upload your recovered key.
No passkey appears: check the selected website and provider. A separate Chrome profile does not automatically have your Google or extension-manager session. Unlock the correct provider, and keep the original passkey intact. Do not reset, delete, or recreate it.
No key matches: check the chosen FullAccess key and account. A different credential, unsupported signature type, or historical wallet version can also cause a mismatch. The app does not save any candidate key on failure.
macOS blocks the preview app: follow the per-app opening instructions above only if you trust this release. A damaged-app or malware alert needs investigation.
Chrome shows a certificate warning: stop. Do not bypass certificate warnings or install a certificate into Apple Keychain.
A recovery port is busy: close the other recovery session, then retry as instructed. After a crash, check that all dedicated recovery windows have closed before starting again.
When reporting a problem, share only the app version, macOS/Chrome version, selected provider and the plain error message. Never attach a private-key file, passkey data, provider password/PIN, browser profile, or screenshot showing secrets.
The setup step sends your public account name to a public NEAR RPC (https://rpc.mainnet.near.org) to find existing access keys. Your chosen passkey provider may contact its own services. Key reconstruction and saving happen on your device, and the recovery page has no upload route or analytics.
The old wallet design derives the NEAR key from the passkey's public point. A provider or historical service knowing that point could independently derive the same wallet key. This app cannot change that design or promise secrecy from the original provider, a malicious extension, or a compromised device.