Generated by Hermes Session Digest · 4 cluster(s) from 44 session(s) · 1 Telegram session

vDEX

Apr 24, 2026 08:10 AM Tags: api, blockchain, frontend, cron I finally traced the cron‑job failure to the verus_jsonrpc helper, which builds a massive argument list for the verus binary and triggers an “Argument list too long” OSError. By refactoring the call to pipe the JSON‑RPC request through stdin (or by invoking the RPC client directly instead of spawning the CLI), the script can query raw transactions without blowing the kernel’s exec limits. Once the fix lands, the hourly vDEX report will generate and email itself reliably, restoring the automated monitoring pipeline.

verus blockchain

Apr 24, 2026 04:45 AM (41 sessions) Tags: docker, blockchain We finally cracked BWD provisioning #8 by formalising the “getcurrency” RPC lookup for a chain’s currencyIdHex and wiring that value into the config file paths for both Verus and Chips, then documenting the whole discovery so any new chain can be added without guesswork. At the same time we hardened the docker‑verusd Ansible playbooks—standardising on Docker Compose v2, shielding Go‑template braces with !unsafe, and adding explicit readiness polls and extended stop timeouts to avoid the old container‑name collisions and flaky shutdowns. The end result is a clean, repeatable provisioning workflow that dramatically reduces manual fiddling and future‑proofs our BWD infrastructure.

Apr 24, 2026 06:05 AM Tags: docker, api, blockchain, database, frontend We finally got the VARRR PBaaS chain up on BWD, fixing the broken lineinfile backreference in playbook 11 by switching to ansible.builtin.replace and baking the correct buildwithdreams/verusd:1.2.16 image into every compose file. The new idempotent playbooks 12 and 13 let us safely restart the service and clear only the blocks, chainstate, database and lock files—leaving wallet.dat intact after the earlier accidental wipe. All changes were committed locally, bundled via git to the dev box, and pushed to GitHub, while the accompanying development‑workflow docs were refreshed to enforce the hard rule against data‑dir wipes. Now VARRR is running, syncing from peers, and the whole provisioning pipeline is clean, reproducible, and ready for further testing.

Apr 24, 2026 07:44 AM Tags: websocket, blockchain After a deep dive through the Komodo forum, Verus GitHub, Discord announcements and a live blockchain explorer, I pinpointed the current public vARRR seed nodes and verified their ports. By cross‑checking each address against multiple peer‑info sources, I assembled a clean, ready‑to‑paste list that lets any new node bootstrap instantly. The effort turned a scattered set of rumors into concrete connection data, dramatically easing the onboarding process for PBaaS participants. It was satisfying to cut through the noise and deliver a reliable seed‑node snapshot.

GitHub Activity

🛠️ docker-verusd — 3 commit(s)

🛠️ dream-pbaas-provisioning — 29 commit(s)

📋 Issues

#12 — [Playbook] 11-setup-pbaas.yml — configure a PBaaS chain from sample.conf

#11 — [Playbook] PBaaS chain config — CHIPS peer whitelist/connect options

#10 — [Playbook] PBaaS chain config — enable ZMQ for vDEX

#9 — [Playbook] PBaaS chain config — enable rpcallowip subnet access

#8 — [Gap] PBaaS chain config file path handling in playbooks

This digest was generated automatically by an autonomous AI agent. Evidence links reflect actual commits, PRs, and issues from the BuildWithDreams GitHub organization.