dangell7

Starter

Starter is the simplest possible hook: it just accepts all transactions and logs that it is running.

to test:

• in the develop pane, compile starter.c
• in the deploy pane, deploy it to Alice account
• set up payment transaction from Alice to Bob
• run it and see in the debug stream 'Accept.c: Called.'

dangell7

Starter

Starter is the simplest possible hook: it just accepts all transactions and logs that it is running.

to test:

• in the develop pane, compile starter.c
• in the deploy pane, deploy it to Alice account
• set up payment transaction from Alice to Bob
• run it and see in the debug stream 'Accept.c: Called.'

dangell7

Starter

Starter is the simplest possible hook: it just accepts all transactions and logs that it is running.

to test:

• in the develop pane, compile starter.c
• in the deploy pane, deploy it to Alice account
• set up payment transaction from Alice to Bob
• run it and see in the debug stream 'Accept.c: Called.'

dangell7

Starter

Starter is the simplest possible hook: it just accepts all transactions and logs that it is running.

to test:

• in the develop pane, compile starter.c
• in the deploy pane, deploy it to Alice account
• set up payment transaction from Alice to Bob
• run it and see in the debug stream 'Accept.c: Called.'

dangell7

Starter

Starter is the simplest possible hook: it just accepts all transactions and logs that it is running.

to test:

• in the develop pane, compile starter.c
• in the deploy pane, deploy it to Alice account
• set up payment transaction from Alice to Bob
• run it and see in the debug stream 'Accept.c: Called.'

dangell7

Starter

Starter is the simplest possible hook: it just accepts all transactions and logs that it is running.

to test:

• in the develop pane, compile starter.c
• in the deploy pane, deploy it to Alice account
• set up payment transaction from Alice to Bob
• run it and see in the debug stream 'Accept.c: Called.'

dangell7

IOU vs MPT on the XRPL — Ecosystem Review and Client Decision Guide

Date: July 14, 2026 Scope: Protocol comparison (grounded in rippled source), XRPL ecosystem adoption 2024–mid-2026, tradfi/RWA tokenization landscape, and a client-facing decision matrix. Thesis under test: "the future is MPT."

---

1. Executive summary

• MPT (XLS-33, Multi-Purpose Tokens) is the institutional token standard on XRPL. Its flag set — RequireAuth allowlisting, per-holder and global lock, clawback, fixed supply caps, integer amounts, on-chain metadata, per-issuance transfer fees — maps one-to-one onto what regulation now requires (GENIUS Act seize/freeze/burn, MiCA EMT controls, SEC transfer-agent regimes).

dangell7

XRPL 2027 Amendment Portfolio — Feasibility Assessment

Why each proposed amendment is worth building, or is not. For every item: the addressable market with a real number, what already solves the problem, and a verdict. Figures researched August 2026 with sources named. Where a market is small or the demand is speculative, this says so.

Verdicts: SHIP (build it, the case is made), GATE (real but needs a decision first), PARK (defensible idea, wrong year).

dangell7

  xls: XX
  title: Repo
  description: Bilateral repurchase agreements with on-ledger collateral and time-proportional interest.
  author: Denis Angell (@dangell7)
  category: Amendment
  status: Draft
  proposal-from: TBD
  requires: XLS-85
 created: 2026-08-04

dangell7

xls: TBD (draft, candidate XLS-104)
title: Destinationless Payment Channels & Escrow
description: Allow PaymentChannelCreate and EscrowCreate without a Destination; the destination is bound at claim/finish time.
implementation: none yet
author: Denis Angell <dangell7@xrpl-labs.com> (XRPL-Labs)
category: Amendment
status: Draft
requires: XLS-85 (token escrow, referenced), XLS-93 (token paychan, referenced)
created: 2026-08-05