Hey everyone,
I'm excited to announce the release of NectarEngine version 0.1.3! This update is special because it comes directly from community feedback.
Shoutout to @ben.haase for asking if NectarEngine had a way to retrieve node metadata from @flowerengine. The answer was "No! But I will add it asap, that would only make sense! 😅". This feature, a utility to handle Hive Engine node lists, was actually one of the first things I built when I started the library, but I never got around to integrating it properly. Ben's question was the perfect nudge to finally get it done.
Introducing the Nodes Utility
The core of this release is the new Nodes utility, now available in the nectarengine.nodeslist module. This class automatically fetches the latest Hive Engine node benchmark data directly from the @flowerengine account's JSON metadata. It parses this data, ranks the nodes based on performance and reliability, and provides convenient methods to access the best available nodes.
No more hardcoding node URLs or manually checking which ones are reliable! The Nodes object handles it for you, giving you easy access to things like the fastest nodes or the top URL.
Here's how easy it is to use:
You can simply instantiate Nodes() and pass it directly to the Api class, or use methods like .fastest(3) to get a list of the top 3 nodes.
Seamless API Integration
To make this work smoothly, the Api class initialization has been updated. It now intelligently handles being passed various types of node inputs:
- A
Nodesobject itself. - A list or tuple containing URLs (as strings) or
Nodeobjects. - A single URL string or
Nodeobject.
The Api class will automatically extract the primary/best URL based on the input provided and ensure it's correctly formatted.
Release and Availability
After adding the new feature and writing some tests (which all passed!), I've built and published version 0.1.3 to PyPI.
You can grab the latest version now using pip or uv:
pip install nectarengine
# or
uv add nectarengine
This was a fun addition driven by the community!
As always,
Michael Garcia a.k.a. TheCrazyGM
Now nectarengine users can weather the next ddos story better.
🎩!BBH !ALIVE !LOLZ
lolztoken.com
now we just call him Phil.
Credit: reddit
@thecrazygm, I sent you an $LOLZ on behalf of ben.haase
(1/10)
No, it’s all way more reliable now! 🙌 I used my local list of nodes I discovered in the past — worked well, but wow, with the new benchmark and ranking system, it’s on another level. 🔥 Great stuff, keep it up! 💪
!BBH !PIZZA
Wow! This is the perfect addition, combining two things we have already done - and exactly why we need community feedback as part of the development process because, "DUH!" - so obvious, and now its done! Great work!
!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.
Thanks to Ben and you for your curiosity to improve and develop better updates.
$PIZZA slices delivered:
ecoinstant tipped thecrazygm
@master-lamps(1/10) tipped @thecrazygm
Come get MOONed!
This is very good news, my friend! Thank you for making Hive better and more functional! 😁🙏💚✨🤙
Have you seen the Beacon API?
It tests all the nodes with multiple tests and provides an API.
None of these tools properly test for a node being behind though, just if they are responding to API requests, but doesn't mean they haven't forked. I have my own test I run.