Include Flags in Server Definitions

[WietseWind]

With different amendments not only come different TX types and fields, but also different flags. As we see right now, even the same flag numbers with different meanings. For example, AccountSet flag 16 on XRPL mainnet is asfAllowTrustLineClawback while on Xahau asfDisallowIncomingRemit.

• xahaud/src/ripple/protocol/TxFlags.h

  Line 88 in 8830812

  constexpr std::uint32_t asfDisallowIncomingTrustline = 15;

  
  

• https://github.com/XRPLF/rippled/blob/4bcbf70cae6dc4883c4e695e25a90267b32effa4/src/ripple/protocol/TxFlags.h#L90
  

I propose the flags are included in the RPC server_definitions calls, so explorers & clients like Xaman can adapt ther screens (e.g. Sign Request & TX Details information) to a specific network.

I propose an object added to the definitions with an array with e.g. Flags per TX Type, or even an object with TX Type » Flag » integer. (Or any other format).

[
  { transactor: 'AccountSet', flagName: 'asfAllowTrustLineClawback', flag: 16 }
]

or

{
  AccountSet: {
    asfAllowTrustLineClawback: 16
  }
}

Prio

This is needed for:

• [Feature] (PRIO!) Dynamic Flags based on server definitions XRPL-Labs/Xaman-Issue-Tracker#492

[RichardAH]

yep good catch, we'll add to server definitions

[zgrguric]

I would like to see flags included on XRPL also.

[WietseWind]

I would like to see flags included on XRPL also.

Yep we should definitely PR this into xrplf/rippled

[WietseWind]

@N3TC4T This will be in the upcoming xahaud release :) So we can include the right flag names in 3.0 :)

[RichardAH]

#304
#306