Hey everyone!
Today, I’m excited to announce that both hive-nectar v1.0.0 and nectarengine v1.0.0 are officially live.
Even bigger news: to ensure their long-term growth and maintenance, I have moved both repositories from my personal GitHub (@thecrazygm) to the @srbde organization.
Here is what went into these major v1.0.0 releases.
1. hive-nectar v1.0.0: Under the Hood
This release isn't just a version bump. We completely ripped out the brittle, legacy components and replaced them with modern, secure standards.
Cryptography Rebuilt from Scratch
We completely removed unmaintained cryptographic dependencies like ecdsa, pycryptodomex, and scrypt. They represented real supply-chain vulnerabilities. In their place, we introduced:
coincurve: A Python binding to the audited C librarylibsecp256k1(used by Bitcoin Core). This makes transaction signing and public key recovery blazingly fast.cryptography: Python’s standard library for ciphers, password hashing, and DER serialization.- BIP32/BIP38 fixes: Resolved legacy key derivation and address encoding issues so HD keys work exactly as expected.
The "Runs Anywhere" Docker Fallback
Standard wallet libraries assume they can write to the host filesystem. If you try to deploy them in restricted, unprivileged Docker containers or Kubernetes pods, they crash on startup.
We built a transparent in-memory fallback for the SQLite keystore. If Nectar detects it doesn't have directory write permissions, it silently falls back to an in-memory database (file:...mode=memory&cache=shared). It just works.
HTTPX2 Client Upgrade
We upgraded our underlying network layer library to httpx2 to ensure modern HTTP protocol support, better connection pooling, and resilient retry behaviors.
2. nectarengine v1.0.0: Parity and Performance
Our companion command-line tool and library for managing Hive Engine tokens has been upgraded to matching standards.
- HTTPX2 Support: Upgraded the client to use
httpx2for all contract queries and node list fetches. - Default RPC Domain Update: Updated the default fallback Hive Engine RPC endpoint to
https://enginerpc.com/. - Resilient Caching: Improved node list caching logic. If the PeakD beacon API goes down, the engine falls back to local cached nodes gracefully instead of throwing exceptions.
What about Legacy Scripts?
I know some of you have python scripts that are almost 10 years old. The core philosophy of this modernization is that we do not break the existing API shapes.
Check Out the Repos
Both v1.0.0 releases are live on PyPI, and the source code is hosted on the srbde GitHub organization:
- 🍯 hive-nectar: https://github.com/srbde/hive-nectar
- ⚙️ nectarengine: https://github.com/srbde/nectarengine
Grab the new versions, take them for a spin, and let me know if anything weird happens.
As always,
Michael Garcia a.k.a. TheCrazyGM
Awesome update.
$PIZZA slices delivered:
@ecoinstant(1/20) tipped @thecrazygm
Join us in Discord!
Incredible work lately! I know we jumped a few numbers - but I am happy to reach 1.0.0!
!PAKX
!PIMP
!PIZZA
View or trade
PAKXtokens.Use !PAKX command if you hold enough balance to call for a @pakx vote on worthy posts! More details available on PAKX Blog.
I'm slowly working with my Hermes (AI) Agent to be able to connect to, and transact within the Hive ecosystem, and hive-nectar and nectarengine are core parts of that. 😁🙏💚✨🤙
Thank you for making all the updates. I initially looked up beem and one of the devs helpfully suggested hive-nectar instead.
Perfect timing as I'm about to do some tests.
Congratulations @thecrazygm! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next payout target is 16000 HP.
The unit is Hive Power equivalent because post and comment rewards can be split into HP and HBD
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out our last posts: