Cohort ended · self-paced
beginner 10 min

Practical Guidance & Resources for the XRPL AI Hack

Everything you need for the day itself: how the UKCBT XRPL AI Hack runs, how to scope a project you can finish in six hours, a reference detection pipeline, how to evaluate a model without labels, a five-minute pitch structure, responsible analysis, and every resource from this course in one place.

Prerequisites

Complete these before starting this module:

What you'll learn

  • Know the hackathon format, timings, team rules and submission deadline.
  • Scope a narrow, finishable detection project and plan the six hacking hours.
  • Follow a reference pipeline from ingestion to explainable detection.
  • Evaluate a detector without labels using case studies, incident replay, synthetic injection and stability checks.
  • Structure a five-minute pitch and present findings responsibly.
Complete this module by self-assessment. Jump to assessment

Overview

You have the XRPL fundamentals, you can read transactions as data, you can download them, and you know what laundering looks like. This last module turns all of that into a plan for the day: how the hackathon runs, how to scope a project you can actually finish in six hours, a reference architecture for a detection pipeline, how to evaluate a model without labels, how to pitch it, and every resource from this course in one place.

Before the day

Everything you can do in advance is time you get back for modelling:

  • Finish this course, including the exercises, so the scripts already run on your laptop.
  • Set up your environment: Python 3.10 or later with xrpl-py==5.2.0, pandas, networkx and scikit-learn, or a Google Colab notebook with them installed.
  • Agree team roles if you already have a team: data, features and rules, model, and story and slides.
  • Have a fallback dataset: venue Wi-Fi and public servers will both be busy. Download a modest ledger range at home and keep it on disk.

A reference pipeline

You don't have to follow this, but it works:

  1. Ingest: ledger sweep or account crawl with xrpl-py, retries and back-off, written to CSV or Parquet.
  2. Clean: keep tesSUCCESS, read delivered_amount, convert drops to XRP, key tokens by currency.issuer, set dust aside.
  3. Enrich: account age and funding parent, account_info flags, explorer labels for known services.
  4. Features: per-account behaviour (degree, totals, pass-through ratio, time to forward, amount uniformity) and graph features (cycles, PageRank, community).
  5. Detect: transparent rules first, then a model (Isolation Forest, clustering, or a graph neural network if you're confident).
  6. Explain: for each flagged account, show why: which features, which transactions, a small subgraph.

Evaluating without labels

There's no answer key. You can still show your model is meaningful:

  • Case studies: walk through two or three flagged accounts with real transaction hashes and explain what you see.
  • Known-incident replay: check whether your approach would have flagged the flows in a publicly reported incident.
  • Synthetic injection: inject artificial patterns (a fake peel chain, a fan-out) into real data and measure whether you recover them. State clearly that they're synthetic.
  • Stability: does the ranking stay similar across different time windows?
  • False positives: show what you deliberately don't flag (exchanges, market makers, dust bots) and why.

Responsible analysis

On-chain data is public, but the people behind addresses are real:

  • Say "flagged for review", never "criminal", in slides, code and demos.
  • Don't try to de-anonymise individuals, and don't contact or accuse account holders.
  • Treat explorer labels as evidence, not truth, and say where each label came from.
  • Read-only analysis needs no keys. If you ever touch a wallet, use Testnet and never share a seed.

Resources

XRPL fundamentals and data

AML and detection

Tools

  • pandas, NetworkX, scikit-learn, PyTorch Geometric for graph neural networks, Gephi or pyvis for graph visualisation.

Event

Check

You're done when your team has a one-sentence project question, a working pipeline on a small cached dataset, agreed roles, and a draft outline of your five-minute pitch. Submit your team plan.

Assignments

0 of 2 complete