BUILD runs one pipeline: developer training, summer buildathon, core-dev training, then the Swell hackathon. Underneath it, the protocol work heading to Swell continues.
- Academy launch (dev training, online, Jun 22–23)
- Summer buildathon (Jun 21 – Sep 21)
- Core-dev bootcamp (online, Jul 1 – Aug 1)
- Office hours every Friday
- Swell hackathon
- Two XRPL clients heading toward Swell
- Two amendment position papers published (XLS-65, XLS-66)
- Amendment audit harness still surfacing bugs
- Infrastructure migration nearing completion
Since the last committee
Days of activity in May (May 1 – June 1, 2026). Each box is one calendar day, shaded by that day's commit volume; the number on the right is the count of distinct active days.
The sequence
The summer buildathon runs June 21 to September 21: a three-month build window with office hours every Friday. Two programs run inside it, building toward Swell.
Developer training, online.
Online, protocol depth.
Where the cohort ships.
Summer buildathon (June 21 – September 21)
The three-month build window. Trained builders ship, with office hours every Friday. Reuses the Hack the Block template: SourceTag-tracked teams, mentor and judge structure, partner bounties.
Academy launch: developer training (online, June 22–23)
Complete rebuild of builder training, delivered online over two days: new delivery, content, starter kits, and builder tools (dev-training-june-2026 ↗). Builder resources from Aurelien's XRPL Builder Suite:
Core-dev bootcamp (online, July 1 – August 1)
Deep protocol track for the strongest builders: internals, client work, amendments.
Swell hackathon
Where the cohort ships. We bring trained builders, two client implementations, and a proven event template.
The buildathon runs on the hackathon app
The summer buildathon runs on our own hackathon app (hackathons.xrpl-commons.org ↗): registration, teams, judging, and bounty disbursement, proven at Hack the Block during Paris Blockchain Week. We are hardening it ahead of the buildathon. The 20 open issues, grouped:
Judging & event operations
- #250 Live judging board: real-time room/project status, judging rooms per bounty
- #276 Judge role system: restrict evaluation categories per judge
- #251 Capture judge feedback to share with hackers
- #272 Fix CSV export on final-decisions (missing emails and score fields)
Stability & performance
- #269 Fatal JavaScript heap out-of-memory error
- #270 API bottleneck on /api/projects and /api/teams (response times)
Functional bugs
- #275 Announcements system not working
- #273 Profile: social links auto-save without confirmation, broken external-link button
- #271 Links not natively navigable (open in new tab)
UI / UX polish
- #277 Unreadable text: dark text over dark background image
- #279 Search tooltip overflows screen on /projects
- #274 Harmonize buttons, page widths, and card borders
- #278 Remove XRPL logo from login page (style inconsistency)
Customization (multi-event)
- #280 Custom background image upload per hackathon
SEO, DNS & naming
- #267 URL slugs, title harmonization, and meta-tag improvements
- #266 CNAME redirects for common misspellings → hackathons.xrpl-commons.org
- #239 Rename GitHub app from hackathons_app to hackathons
Refactors / tech debt
Toward Swell: protocol and client work
The engineering work we intend to show at Swell.
Two XRPL clients
Two implementations in two languages: the strongest signal the protocol spec is real. goXRPL is closing on full transaction-type coverage.
Proving it interoperates
Two efforts confirm goXRPL agrees with rippled at the protocol level:
- xrpl-confluence (18 active days): orchestrates mixed networks of rippled and goXRPL nodes to validate p2p messaging, transaction propagation, ledger sync, and consensus.
- xrpl-state-compare: diffs ledger state between implementations to catch divergence.
Amendment audit and vote positions
automate-ammendment-tests (9 active days in May, Romain): an AI audit harness that generates adversarial tests from an XLS spec, runs them against rippled, and produces an audit report. This period it produced two formal Commons position papers, audited against rippled 3.1.3. On both, our stance is the same: not voting at this time, neither yes nor no.
- XLS-65 Single Asset Vault — position paper ↗. The reasoning: a medium-leaning-high conformance defect (a zero-cost griefing primitive against any deployed Vault), with a one-line upstream fix. We will revisit once it is patched.
- XLS-66 Lending Protocol — position paper ↗. Lending itself is technically mature (no exploit-grade vulnerability found), but it carries a formal dependency on the unpatched Single Asset Vault.
Publishing the reasoning makes the position legible to the community and sets the standard for how we approach amendments. Coverage continues across others:
Infrastructure
Scaleway migration
Migration issues nearing resolution. New rack commissioned; servers migrating.
Hub failures
Peering node failures handled; replacement in progress.
Promotable content
XRP Ledger game
A retro arcade game: pilot your ship and survive the many XRPL transactions. Playable now at space.xrpl.at ↗. A playful way to show how the ledger works, ready to share across community channels.
XRPL News
A community link board (Hacker News style) at news.xrpl-commons.org ↗: share updates, spark conversations, and highlight what's new in the XRPL community. Popular, latest, ask, jobs, and groups. Ready to promote across channels.
