Hive Keeper v3.17.x - Release Notes

avatar

A major release introducing the Hive Unified Wallet Protocol, on-chain swaps, and first-class integration with Ecency products.

After our initial release announcement, we have got few feedbacks and improvement suggestions, so this release delivers those and hardens integrations.

New Features ✨

Hive Unified Wallet Protocol

  • New window.hive API with identity flags exposes a standard provider registry (window.hive.providers[]) so dApps can detect and select between Hive Keeper, Keychain, Peak Vault, and others without per-extension globals.

  • Multi-Wallet Discovery Protocol specification published for ecosystem-wide adoption.

  • Hive Keychain dApp compatibility shim - existing Keychain-integrated dApps work with Hive Keeper out of the box, no code changes required.

  • Still waiting Keychain team to review proposed unification: https://github.com/hive-keychain/hive-keychain-extension/pull/595

  • Same unification proposal on Vault extension: https://gitlab.com/peakd/peak-vault/-/merge_requests/42

On-chain Swaps

  • HIVE ↔ HBD swaps and Hive Engine token swaps fill instantly against the existing order book.

  • Swap engine hardening - fixed stale-estimate race, dead validator removed, estimate sequence bumps on every input change.

Firefox Add-on

  • Proper Firefox manifest with data_collection_permissions and a clean unique add-on ID.

  • Privacy Policy + Terms of Service pages now hosted on GitHub Pages.

Fixes & Improvements 🐛

  • Vault persistence - accounts/keys reliably survive restarts.

  • Light theme polish across screens.

  • Account import flow fixes.

  • Splashscreen rendering.

  • Reduced build size and tightened production-build/audit pipeline.

  • Removed unused offscreen permission for a smaller permissions surface.

Integrations 🔌

Ecency Web

  • Unified extension abstraction consumes window.hive.providers[] first, with legacy global fallback.

  • Hive Keeper is recognised via rdns: com.ecency.keeper and surfaced alongside Keychain & Peak Vault in the login flow, with an install link to the Chrome Web Store listing.

  • Single detection + broadcast/sign API across all supported extensions.

Ecency Mobile

  • The in-app dApp browser bridge speaks the unified protocol, so any dApp opened inside the Ecency mobile app can transact through the same flow Hive Keeper exposes on desktop.

  • HiveAuth path remains supported for cross-device signing.

What's Next 📣

Continued protocol adoption across Hive dApps, deeper Ecency integration, and ongoing swap UX refinements. Simplified unity of extensions already visible on Ecency.com and it follows similar standard how Ethereum extensions stay united while offer different UX.

Get your extension

Finally after months of back and forth, Firefox addon also accepted.

Chrome: https://chromewebstore.google.com/detail/hive-keeper/eehlplhgiofbbanbjiodipefljadfehe?authuser=0&hl=en

Firefox: https://addons.mozilla.org/en-GB/firefox/addon/hive-keeper/

Support us

https://ecency.com/proposals/379

hive-139531 hive extension dapps wallet ecency browser hiveonly keeper security
0
0
0.000
6 comments
avatar

Buen contenido! De los mejores que vi hoy en Hive. Ahí va mi voto, seguí publicando!

0
0
0.000
Reply
avatar

Congratulations on the progress of the work.

!BBH !ALIVE !PIZZA !HOP

0
0
0.000
Reply
avatar

Congratulations ecency, great to see that finally cross the finish line after all that waiting

0
0
0.000
Reply
avatar

The provider registry idea is the part I keep coming back to here.

Hive has had strong wallet tools for a long time, but dApp integration has often depended on knowing which extension or signing flow the user has installed. A standard window.hive.providers[] layer makes the ecosystem feel more like a platform and less like a collection of separate wallet assumptions.

That matters for developers. If dApps can detect Hive Keeper, Keychain, Peak Vault, and future wallets through one predictable interface, integration work gets less fragile. It also reduces the cost of supporting multiple user preferences without forcing every app to write special cases.

The Keychain compatibility shim is also practical. Standards are easier to adopt when old integrations do not break immediately. That bridge between existing behavior and a cleaner provider model is probably what gives this release real ecosystem value.

0
0
0.000
Reply