The 2026-07-29 upstream sweep found drift on the ant-client record on this page that needs a human decision before the page is stamped or rewritten. The verification block is left byte-identical to base on the sweep branch.
Record
docs/rust/library-reference.md:3 — ant-client, 81848a09..6f0c9572
Verification block (unchanged on the sweep branch)
<!-- verification:
source_repo: ant-client
source_ref: main
source_commit: 81848a0900fa9972e9af2d323bf3b49bf8d382aa
verified_date: 2026-07-28
verification_mode: current-merged-truth
-->
Upstream change
This page documents the native merkle external-payment helpers prepare_merkle_batch_external and finalize_merkle_batch, the PaymentMode enum (Auto, Merkle, Single), PreparedMerkleBatch, and file_upload_with_mode(PaymentMode::Merkle). All of those symbols still exist with unchanged signatures at the pinned head, so no rendered claim is wrong. However, the same ant-client rework changes what those helpers do:
- merkle cost estimation now bills the padded (power-of-two) leaf count (
merkle_billable_leaves),
- external merkle preparation now refuses batches over
MAX_LEAVES (256) with the new Error::MerkleBatchTooLarge variant,
- merkle settlement now applies the 3x median multiplier.
Why this is ambiguous rather than a straightforward prose update
The documented symbols are intact, so this could be a metadata-only stamp — but the helpers this page points developers at now carry a new hard limit and a changed cost model that a reader building against them would want to know. That content is the same mid-rollout, sign-off-pending merkle change tracked by the payment-model.md and use-external-signers manual-review issues. A reviewer should decide whether this page needs a note about the external merkle batch-size limit and padded-leaf billing, or whether it should simply be stamped once the pricing decision is settled.
Fingerprint: docs/rust/library-reference.md:3|ant-client|81848a0900fa9972e9af2d323bf3b49bf8d382aa..6f0c957289371cc0b0e766f2c580adc8ecb69074
The 2026-07-29 upstream sweep found drift on the
ant-clientrecord on this page that needs a human decision before the page is stamped or rewritten. The verification block is left byte-identical to base on the sweep branch.Record
docs/rust/library-reference.md:3—ant-client,81848a09..6f0c9572Verification block (unchanged on the sweep branch)
Upstream change
This page documents the native merkle external-payment helpers
prepare_merkle_batch_externalandfinalize_merkle_batch, thePaymentModeenum (Auto,Merkle,Single),PreparedMerkleBatch, andfile_upload_with_mode(PaymentMode::Merkle). All of those symbols still exist with unchanged signatures at the pinned head, so no rendered claim is wrong. However, the same ant-client rework changes what those helpers do:merkle_billable_leaves),MAX_LEAVES(256) with the newError::MerkleBatchTooLargevariant,Why this is ambiguous rather than a straightforward prose update
The documented symbols are intact, so this could be a metadata-only stamp — but the helpers this page points developers at now carry a new hard limit and a changed cost model that a reader building against them would want to know. That content is the same mid-rollout, sign-off-pending merkle change tracked by the payment-model.md and use-external-signers manual-review issues. A reviewer should decide whether this page needs a note about the external merkle batch-size limit and padded-leaf billing, or whether it should simply be stamped once the pricing decision is settled.
Fingerprint: docs/rust/library-reference.md:3|ant-client|81848a0900fa9972e9af2d323bf3b49bf8d382aa..6f0c957289371cc0b0e766f2c580adc8ecb69074