0064 XLS - 64d: Pseudo-Account

[Tapanito]

    
Title:        Pseudo-Account
Revision:     1 (2024-04-05)

  Authors:    
  Aanchal Malhotra
  Vytautas Vito Tumas

Affiliation: 
  Ripple

Pseudo-Account

Abstract

In this document, we propose a standard for a pseudo-account, an AccountRoot object that can be associated with one or more other ledger entries. This feature allows one to link an account with multiple ledger entries to track XRP and Token Balances or issue Fungible Tokens on behalf of the linked ledger entries.

1. Introduction

The XLS-30 specification introduced an AMMID field to the AccountRoot ledger entry. It associates a pseudo-account with an AMM instance to track XRP and Token balances in the pool and issue LPTokens on behalf of the AMM Instance. However, the AMMID DOES NOT allow us to associate the AccountRoot with other ledger entries.

This proposal addresses this limitation by introducing a new PseudoOwner field to the AccountRoot that allows linking the object with one another ledger entry. Implementing this specification will deprecate the AMMID.

Furthermore, the proposal introduces minimum requirements for any protocol creating a pseudo-account.

2. Changes to the AccountRoot

The PseudoOwner field links the AccountRoot object with one ledger object entry..

2.1 New fields

---

Field Name	Required?	JSON Type	Internal Type	Description
PseudoOwner	No	string	HASH256	An ID of a ledger object with which the AccountRoot is associated.

---

3. Creating a pseudo-account

The address of the AccountRoot must be randomized to prevent users from identifying and funding the address before its creation. The protocol that creates an AccountRoot must ensure the account address is unoccupied.

The AccountRoot object for a pseudo-account MUST have the following settings:

• lsfDisableMaster enabled to ensure that no one can control the account directly and send transactions on its behalf.

• lsfDepositAuth enabled to ensure that the only way to add funds to the account is by using a deposit transaction.

The unique ID of the AccountRoot object, a.k.a. AccountRootID is computed as follows:

• for (i = 0; i <= 256; i--)
  • Compute AccountRootID = SHA512-Half(i || Parent Ledger Hash || PseudoOwner)
  • If the computed AccountRootID exists, repeat
    • else, return AccountRootID

4. Special Creation Cost

A transaction that creates a _pseudo-account_ MUST charge a higher than usual transaction fee to deter ledger spam. The transaction MUST destroy at least the incremental owner reserve amount, currently 2 XRP.

[dangell7]

Why do you need LedgerEntries? Can you not just use the ownerDir?

[mvadari]

The owner directory can have many additional objects in it. For example, an AMM account has one AMM object and lots of trustlines.