@blinklabs/dingo 0.32.3 → 0.34.0

package/RELEASE_NOTES.md

@@ -1,6 +1,77 @@
 # Release Notes
 
 
+## v0.33.0 (April 13, 2026)
+
+**Title:** Blockfrost-compatible address endpoints
+
+**Date:** April 13, 2026
+
+**Version:** v0.33.0
+
+Hi folks! Here’s what we shipped in v0.33.0.
+
+### ✨ What's New
+
+- **Blockfrost-compatible address endpoints:** Plugging Dingo into existing Blockfrost-based tooling is easier because you can now query address UTxOs and transactions via Blockfrost-compatible HTTP endpoints.
+- **Epoch-scoped protocol parameters:** Clients can fetch the exact settings they need for historical or upcoming validation because protocol parameters can now be requested for a specific epoch.
+
+### 💪 Improvements
+
+- **Node internals split into focused files:** The codebase is easier to navigate because chainsync recycling, forging, and shutdown logic moved out of `node.go` into dedicated files.
+- **Makefile help and lint targets:** Build and contributor workflows are easier to run consistently because the Makefile now includes `help` and `lint` targets with inline target descriptions.
+- **Dependency and CI refresh:** Compatibility stays smoother because Go module dependencies (including `golang.org/x`), key CI actions, and the txtop Docker image were updated.
+- **Clearer package docs and licensing:** Development is simpler because core packages now include Apache 2.0 headers, richer package docs, and conformance test suite docs under `internal/test/conformance`.
+- **More complete `dingo.yaml.example`:** Getting started is easier because the example config now includes a default `databasePath` that matches the expected on-disk layout.
+
+### 🔧 Fixes
+
+- **Safer chainsync recycling on small topologies:** Small networks are less likely to lose their only workable connection because the recycler now avoids recycling the only eligible peer.
+
+### 📋 What You Need to Know
+
+- **No action required:** You're all set—just upgrade to v0.33.0.
+
+### 🙏 Thank You
+
+Thank you for trying!
+
+---
+
+
+## v0.32.3 (April 10, 2026)
+
+**Title:** Certificate-aware transaction matching
+
+**Date:** April 10, 2026
+
+**Version:** v0.32.3
+
+Hi folks! Here’s what we shipped in v0.32.3.
+
+### ✨ What's New
+
+- **Certificate-aware transaction pattern matching (`has_certificate`):** Filtering certificate-related transactions is easier because you can now match and validate Cardano certificates directly in transaction pattern rules.
+
+### 💪 Improvements
+
+- **More reliable persistent-fork recovery:** Sync is more rock-solid because chain sync now closes the affected connection when it detects a persistent fork.
+
+### 🔧 Fixes
+
+- **No user-facing fixes:** This patch focuses on new features and improvements.
+
+### 📋 What You Need to Know
+
+- **Transaction-pattern configs:** If you maintain custom transaction-pattern rules, you can start using `has_certificate` to filter or detect certificate-related transactions.
+
+### 🙏 Thank You
+
+Thank you for trying!
+
+---
+
+
 ## v0.32.2 (April 9, 2026)
 
 **Title:** Stability and polish updates

package/dingo.yaml.example

@@ -11,6 +11,11 @@ bindAddr: "0.0.0.0"
 # Can be overridden with the config environment variable
 cardanoConfig: "./config/cardano/preview/config.json"
 
+# Global data directory for both blob and metadata storage plugins.
+# Can be overridden with CARDANO_DATABASE_PATH or --data-dir.
+# Plugin-specific data-dir settings below override this value.
+databasePath: ".dingo"
+
 # Database configuration
 database:
   # Blob storage plugin configuration

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blinklabs/dingo",
-  "version": "0.32.3",
+  "version": "0.34.0",
   "description": "Dingo is a Cardano blockchain data node",
   "main": "index.js",
   "bin": {