@blazeapps/dsteem

Modernized fork of dsteem — a robust Steem blockchain RPC client for Node.js and browsers. Published as @blazeapps/dsteem so the original dsteem@0.11.x on npm is untouched; the public API is unchanged so a drop-in import-rename is the only consumer change.

• Pure-JS cryptography (@noble/curves, @noble/hashes) — no native bindings, no node-gyp, no prebuilds to verify
• Dual ESM + CommonJS distribution with TypeScript declarations
• Single-file browser bundle (UMD/IIFE, global dsteem)
• Same public API as v0.11.x — drop-in upgrade

Install

npm install @blazeapps/dsteem

Requires Node.js 22 LTS or newer. (v0.11.x supported older Node; v0.12 dropped the native secp256k1 build and the dead browser polyfills along with it.)

Migrating from the legacy dsteem: rename every 'dsteem' import to '@blazeapps/dsteem'. The public API is identical — no other changes needed. See What changed in v0.12 for the under-the-hood swaps.

Quick start (Node)

import {Client} from '@blazeapps/dsteem'

const client = new Client('https://api.steemit.com')
// or, if the primary is down:
// const client = new Client('https://api.moecki.online')

for await (const block of client.blockchain.getBlocks()) {
    console.log(`New block, id: ${block.block_id}`)
}

const {Client, PrivateKey} = require('@blazeapps/dsteem')

const client = new Client('https://api.steemit.com')
const key = PrivateKey.fromLogin('username', 'password', 'posting')

client.broadcast.vote({
    voter: 'username',
    author: 'almost-digital',
    permlink: 'dsteem-is-the-best',
    weight: 10000
}, key).then(({block_num}) => console.log('Included in block:', block_num))

Quick start (browser)

<script src="https://unpkg.com/@blazeapps/dsteem@^0.12/dist/dsteem.browser.global.js"></script>
<script>
    const client = new dsteem.Client('https://api.steemit.com')
    client.database.getDiscussions('trending', {tag: 'writing', limit: 1}).then(([post]) => {
        document.body.innerHTML = `<h1>${post.title}</h1><h2>by ${post.author}</h2>`
    })
</script>

The browser bundle inlines a Node Buffer polyfill (~20 KB) — consumers don't need to set anything up. The IIFE bundle still exposes the global as window.dsteem for drop-in compatibility with v0.11.x browser snippets.

When using a bundler (webpack/vite/rollup), import {Client} from '@blazeapps/dsteem' resolves to the ESM build automatically.

Quick start (React Native / Expo)

React Native's JS runtime (Hermes/JSC) doesn't ship Web Crypto's getRandomValues, which @noble/curves needs for ECDSA entropy. As of v0.12.2, the package's react-native / browser exports resolve to a fully-polyfilled bundle — Node built-ins (Buffer, stream, util, assert) are inlined inside the package itself, so consumers no longer have to ship a Buffer polyfill or shim global.Buffer. Only one polyfill is still required:

npm install @blazeapps/dsteem react-native-get-random-values

At the very top of your app entry (index.js or App.tsx), before any other import:

import 'react-native-get-random-values'

Then use the library normally:

import {Client, PrivateKey} from '@blazeapps/dsteem'

const client = new Client('https://api.steemit.com')
const key = PrivateKey.fromString(WIF_FROM_SECURE_STORE)
await client.broadcast.vote({voter: 'me', author: 'a', permlink: 'b', weight: 10000}, key)

After upgrading, clear Metro's cache once so it picks up the new react-native entry:

npx expo start --clear

No metro.config.js tweaks are needed. Verified on Expo SDK 50–55 / RN 0.83. (If you're upgrading from v0.12.1, you can delete the global.Buffer = Buffer shim line — it's no longer necessary.)

Why this works in v0.12.2 but not in v0.12.0/0.12.1

The Node CJS/ESM builds (dist/index.cjs, dist/index.mjs) externalize Node built-ins via esbuild's dynamic __require("buffer") shim. Metro can't statically analyze indirect requires, so it failed to bundle buffer and crashed at runtime with Requiring unknown module "buffer". v0.12.2 ships a parallel polyfilled module build (dist/index.browser.{mjs,cjs}) emitted as real modules with all Node built-ins inlined, and the exports map now routes react-native and browser conditions to that build. Verified: grep -oE '__require[0-9]?\("(buffer|stream|util|assert|crypto)"\)' dist/index.browser.* returns zero matches.

Browser Testing Harness

A static HTML harness for manual, form-driven testing of every dsteem operation lives in Browser Testing/ and is deployed alongside the docs:

• Live: https://blazeapps007.github.io/dsteem/harness/
• Coverage: forms for all 47 Steem operations (account, content, wallet, power, market, escrow, witness, custom, governance, recovery/legacy)
• Lookup panel: getAccounts, getDynamicGlobalProperties, RC/VP mana, raw client.call — no key required
• Safety: defaults to Build & Sign only; broadcasting requires a per-form opt-in; keys are never persisted
• Install model: pulls dsteem from the local repo via "dsteem": "file:.." — never from the npm registry — so the harness always tests what's in this tree

Run it locally:

npm install && npm run build         # at repo root — produces dist/
cd "Browser Testing" && npm install  # postinstall copies the IIFE bundle into lib/
npm run serve                        # → http://localhost:8080

The Pages workflow (.github/workflows/pages.yml) builds the harness in CI and serves it under /harness/. See Browser Testing/README.md for full safety rules and per-op notes.

API

Full API reference: https://blazeapps007.github.io/dsteem/

Public surface (everything v0.11.x exported is still exported the same way):

• Core: Client, PrivateKey, PublicKey, Signature, cryptoUtils
• Domain types: Asset, Price, Transaction, SignedTransaction, Operation, Types, all of the *Operation interfaces
• API helpers: Blockchain, DatabaseAPI, BroadcastAPI, RCAPI
• Utility helpers: the utils namespace (including buildWitnessUpdateOp)

New in v0.12.0 — additive only (no breaking changes): BroadcastAPI, CreateAccountOptions, and the resource-credit interfaces (RCAccount, RCParams, RCPool, Manabar, Resource, Pool, DynamicParam, PriceCurveParam) are now directly importable from the package root, so TypeScript consumers can write import type {Manabar} from '@blazeapps/dsteem' instead of digging the type out of a class signature.

Network

Default RPC for code samples is https://api.steemit.com. A community-maintained fallback is https://api.moecki.online. Set the URL when constructing Client.

What changed in v0.12

• Crypto: native secp256k1 (high-severity CVE in 3.x) + Node:crypto.createHash → pure-JS @noble/curves + @noble/hashes. Public API unchanged; signatures are still canonical (isCanonicalSignature) and accepted by Steem nodes. Old on-chain signatures still verify with the new backend.
• Bundle: browserify + tsify + babelify + uglifyjs + dts-generator → tsup (esbuild). Browser bundle dropped from 782 KB → 351 KB.
• Polyfills: core-js@2, regenerator-runtime, whatwg-fetch, node-fetch — all removed. Modern browsers and Node 22+ provide everything natively.
• Module format: dual ESM + CJS via the exports map; no more lib/ directory or build-time version.js rewrite.
• TypeScript: 3.1 → 5.x, with strict mode (strictNullChecks, noImplicitAny, noImplicitThis).
• Lint: tslint (deprecated) → ESLint 9 flat config + typescript-eslint 8.
• Tests: mocha 5 → 11, nyc → c8 (70 % coverage gate). Karma + Sauce Labs browser tests → Playwright (Chromium/Firefox/WebKit headless).
• CI: CircleCI + Travis → GitHub Actions, matrix on Node 22 + Node 24.

dist/ contents:

File	Purpose
dist/index.mjs	ESM entry (Node)
dist/index.cjs	CommonJS entry (Node)
dist/index.d.ts	TypeScript declarations
dist/dsteem.browser.global.js	Browser IIFE (global dsteem), inlines all deps + Buffer polyfill

License

BSD-3-Clause — see LICENSE.

---

Share and Enjoy!