Introducing the SRBDE SDK Layer: Open Infrastructure for Hive Builders
When you build something on Hive, you need to talk to the chain. You need to sign transactions, query accounts, interact with Layer 2 tokens, and do it all reliably — in production, in containers, across environments you don't control.
That infrastructure should already exist. Clean, maintained, and honestly documented. That's what SRBDE set out to build.
Today we want to introduce the SRBDE SDK Layer: a suite of open-source Hive blockchain libraries covering four programming languages, a sidechain companion library, and more tools to come. All of it lives under the @srbde GitHub organization, maintained by the same team that uses these libraries every day.
Why SRBDE Maintains These Libraries
SRBDE — the Sustainable Resource and Business Development Enterprise — is an independent software organization. We don't have investors to answer to. We build tools because the ecosystem needs them and because we need them ourselves for the products and services we operate.
Our philosophy borrows from sustainable agriculture: the goal is always to return more to the soil than you take. Open source is not a business model for us — it's a value. The commercial work we do funds the open work. The open work is the mission.
The Hive ecosystem has historically had strong Python tooling, some TypeScript coverage, and gaps in a lot of other places. We decided to address those gaps systematically, across languages, with a consistent standard of care.
The SDK Layer at a Glance
Here's what's live and maintained in the SRBDE org right now:
🍯 hive-nectar — Python SDK
The flagship library. Nectar is the modern Python SDK for Hive, and the direct successor to beem. If you're writing Python that talks to Hive, this is where you start.
beem built the foundation. Nectar carries it forward — with legacy cryptographic dependencies stripped out, a transparent in-memory fallback for containerized deployments, and a clean consolidated RPC surface built on httpx2. Version 1.0.0 shipped in May 2026.
pip install hive-nectar
⚙️ nectarengine — Hive-Engine Python SDK
The companion library for Hive Engine — the token and smart contract sidechain layer. nectarengine handles contract queries, token operations, and node list management, with the same httpx2 transport backbone as Nectar and resilient local caching when the PeakD beacon API is unavailable. Version 1.0.0 shipped alongside Nectar.
pip install nectarengine
🌸 hive-pollen — TypeScript SDK
dhive built the foundation of JavaScript development on Hive — but it carries a decade of legacy: unmaintained cryptography, thousands of transient vulnerabilities, and a build system stuck in the past. Pollen is its spiritual successor, rebuilt for security, performance, and the environments developers actually build for today.
npm install @srbde/pollen
🌿 hive-anther — Go SDK
Our Go library for Hive. Built for backend services, microservices, and high-performance tooling where Go's concurrency model and deployment characteristics are an advantage.
go get github.com/srbde/hive-anther@latest
🧬 hive-xylem — Rust SDK
Our Rust library for Hive. For systems-level work, WASM targets, and anything where you need Rust's safety guarantees and performance profile alongside Hive blockchain interaction.
cargo add hive-xylem
What "Maintained" Actually Means
A library listed on PyPI with a last commit from three years ago is not maintained. We want to be clear about what we mean when we say these libraries are maintained:
- We use them ourselves. The tools we build for the Hive ecosystem and for SRBDE's own products depend on these SDKs. When something breaks in production, we feel it.
- We track the chain. When Hive protocol changes, we update. When dependencies develop vulnerabilities, we act on them.
- We don't break existing API shapes. Some of you have Python scripts that are close to a decade old. The modernization work in Nectar v1.0.0 was done without changing the external API surface that existing code depends on.
- We document honestly. The README tells you what the library does, what it requires, and what its limitations are. We don't overstate.
For Developers: Getting Started
Python — hive-nectar
Full docs: hive-nectar.readthedocs.io
pip install hive-nectar
from nectar import Hive
from nectar.account import Account
hive = Hive()
account = Account("youraccount", blockchain_instance=hive)
print(account.balances)
The ReadTheDocs site covers the full API surface, including examples for signing and broadcasting transactions, deploying in containerized environments, and Ledger hardware wallet support. The changelog and repo are at github.com/srbde/hive-nectar.
Rust — hive-xylem
Full docs: docs.rs/hive-xylem · Crate: crates.io/crates/hive-xylem
[dependencies]
hive-xylem = "0.1.0"
tokio = { version = "1.0", features = ["full"] }
use hive_xylem::Client;
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let client = Client::new(vec!["https://api.hive.blog".to_string()], 30);
let accounts = client.get_accounts(&["youraccount".to_string()]).await?;
if let Some(acc) = accounts.first() {
println!("Account: @{}", acc.name);
println!("HIVE Balance: {}", acc.balance);
println!("HBD Balance: {}", acc.hbd_balance);
}
Ok(())
}
Xylem is fully async (Tokio), uses audited RustCrypto cryptography (secp256k1, bs58, sha2, ripemd), and handles offline transaction serialization natively — no RPC-based get_transaction_hex dependency. The repo includes examples for signing and broadcasting transactions. Source and examples at github.com/srbde/hive-xylem.
TypeScript & Go — hive-pollen and hive-anther
Both libraries are built and active. Hosted documentation is coming — for now, the READMEs in each repo are the starting point:
- github.com/srbde/hive-pollen — TypeScript
- github.com/srbde/hive-anther — Go
The Bigger Picture
The SDK layer is one piece of what SRBDE builds. We also operate community publishing tools, TTRPG content platforms under TheCrazyGM, and the Mithril Destiny creative publishing arm. The SRBDE corporate hub lives at ecoinstats.net.
The technical work detailed in each library's release notes is documented by our lead developer @thecrazygm — if you want the deep engineering breakdown of what went into Nectar v1.0.0, his recent post covers it thoroughly.
This post is about the layer as a whole: what it is, what it covers, and the commitment behind it.
Now Build Something
If you're writing Hive tooling in Python, TypeScript, Go, or Rust — these libraries are for you. Fork them, use them, open issues, and contribute.
Our repos live at github.com/srbde.
Brought to you by the Sustainable Resource and Business Development Enterprise
Leave Introducing the SRBDE SDK Layer: Open Infrastructure for Hive Builders to:
Best Posts From open.mithril
We have not curated any of open.mithril's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.