BSV Go SDK v1.7.3 Fixes Excessive CPU Use in BEEF Transaction Processing

Developer Tools

In Brief

The BSV Blockchain Go SDK has released version 1.7.3, fixing a transaction-processing problem that could cause excessive CPU use when handling BEEF transaction packages with shared ancestry.

The release also updates numeric decoding for three Script operations to match SV Node 1.2.3. It brings both a processing-efficiency fix and a behavior change for developers to review.

News Report

Go SDK v1.7.3 was published on October 20, 2026, at 16:04 UTC.

The release includes a correction to transaction-ancestry processing, an upgrade to GoBDK v1.3.1, and changes to the SDK’s Script interpreter. Both substantive contributions merged earlier that day.

The SDK supplies Go developers with tools for transaction construction, BEEF handling, script evaluation and SPV verification.

Repeated Work in Transaction Ancestry

BEEF packages carry transactions together with supporting transaction and proof information. Processing a package can require following a transaction’s inputs backward through earlier transactions.

Those paths can overlap: several inputs may ultimately refer to the same earlier transaction.

The previous ancestry routine followed each path before removing duplicate results. When unconfirmed transactions shared ancestors, it could repeatedly process the same history, causing the amount of work to grow exponentially in the worst case.

The updated routine records which transactions it has already visited and skips repeated visits. This makes the work grow with the number of transactions and inputs being processed.

The change preserves the existing ancestor ordering and serialized BEEF and Atomic BEEF output.

Reported Impact on an ARC Server

In the contribution introducing the fix, Michael Boyd reports that transaction submissions triggered heavy CPU use on an ARC server operating on mainnet.

He says the affected processing continued until the service was restarted. After applying the same correction to the earlier SDK version used by that server, CPU use fell sharply and normal transaction-submission traffic resumed.

These are contributor-reported results from the affected deployment.

The committed regression tests exercise a deep chain with shared ancestry and compare the updated routine against the previous implementation across 200 generated transaction graphs. The comparisons check that transaction ordering and collected transaction records remain consistent.

Script-Decoding Compatibility Changes

Version 1.7.3 also updates how the interpreter reads numeric operands for OP_SUBSTR, OP_LEFT and OP_RIGHT, operations used to extract portions of byte strings.

The change follows SV Node 1.2.3’s handling of these values. Certain oversized operands that previously passed are now rejected, and the sign of certain nine-byte operands is applied correctly.

The contribution identifies this as a breaking behavioral change for affected scripts. Developers using the interpreter should therefore review the compatibility notes when adopting the release.

The maintainer reports rechecking test vectors against the node implementation embedded in GoBDK v1.3.1. The contribution also records a separate OP_SPLIT discrepancy involving very large stack elements as follow-up work.

The GoBDK batch-validation adapter additionally returns errors when the underlying library rejects an entry, recording the entry only after acceptance.

BSV TIMES Read

The ancestry correction addresses a practical requirement for services that accept transaction evidence from outside their own systems: processing costs must remain manageable when the supplied transaction history contains overlapping paths.

Portable evidence becomes more useful when software can handle it efficiently while preserving the expected format and ordering.

This release also illustrates why application-side validation needs careful compatibility work. A library’s interpretation of a script affects what an application accepts, even though the library itself does not determine the network’s rules.

For operators and developers, the immediate task is to review the ancestry fix together with the interpreter changes. Adoption will depend on individual wallets and services updating their SDK dependency.

Developer Context

Michael Boyd, using the GitHub account mboyd1, contributed the ancestry-processing correction and documented its reported operational impact.

Mr. Z, using mrz1836, authored the GoBDK and script-decoding update. He is also listed among the Go SDK’s maintainers.

Source Links

Posted on October 21, 2026 (UTC)