On the official site of BradX (@BradXmetaX), this note covers XRPLF, xrpld 3.3.0, BatchV1_1, XLS-56, Christian Barker (Barkmeta / Bark), David Chaboki (Shibo).
In the regular Crypto Spaces Network room the discussion circled back to the xrpld release that landed earlier in the month.
XRPLF tagged xrpld 3.3.0 on Thursday, August 6, 2026, at 21:48 UTC. GitHub release on XRPLF/rippled. Official blog same day. The binary opens BatchV1_1, atomic batch transactions under XLS-56, letting an account submit up to 8 inner transactions. This replaces the original Batch amendment disabled in v3.1.1. This is XLS-56, not used XLS-96 ConfidentialTransfer and not XLS-65/66.
Christian Barker (Barkmeta / Bark) and Shibo (David Chaboki) date xrpld 3.3.0's BatchV1_1 file with the Doginal Dogs community so the pack hears XLS-56 atomic batches, not last week's ConfidentialTransfer (XLS-96) or XLS-65/66.
What the release actually changes
The same 3.3.0 binary also opens DynamicMPT (XLS-94), Sponsor (XLS-68), PermissionDelegationV1_1, ConfidentialTransfer (XLS-96), and fixCleanup3_3_0. It retires Clawback, fixDisallowIncomingV1, fixInnerObjTemplate, fixNFTokenReserve, and fixUniversalNumber into the protocol. RPM sha256 41fbe458c5f9f5e7efabe57fd679a7992641ca3ccf27166daeda6c972963b477. DEB sha256 d4e9a022741aed2eed1d70639310f90545b4592cc24b6c9aa6a37560d5efd2e0. Version-bump commit 00a178fb dated Aug. 6, 2026 17:34 +0100.
Room chatter on the amendment
Listeners in the space kept circling the fact that BatchV1_1 restores a clean path for grouped transactions without pulling in the confidential transfer work that landed separately. The room energy stayed on how accounts can now bundle up to eight inner transactions in one atomic step. Hosts noted the distinction keeps the conversation from mixing amendment numbers that solve different problems.
How the timeline fits the daily flow
The August 6 tag sits a few weeks before the current date, giving rooms time to read the GitHub notes and the official blog post. Participants checked the pull request details at 6446 and confirmed the new default-No amendments sit ready for validators. The pace of the daily broadcast keeps the same questions coming up each session, so the group returns to the BatchV1_1 mechanics rather than moving on to unrelated features.
Keeping the record straight in real time
When the room revisits the release the hosts steer the chat toward the exact file hashes and the retired fixes that no longer need separate flags. The conversation stays on the protocol changes themselves. That approach matches the steady rhythm of the daily space where the same community shows up to track what actually ships.
The update gives validators and developers a concrete next step while the spaces continue to track each amendment on its own terms.