Closed WietseWind closed 5 months ago
yep good catch, we'll add to server definitions
I would like to see flags included on XRPL also.
I would like to see flags included on XRPL also.
Yep we should definitely PR this into xrplf/rippled
@N3TC4T This will be in the upcoming xahaud release :) So we can include the right flag names in 3.0 :)
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 isasfAllowTrustLineClawback
while on XahauasfDisallowIncomingRemit
.https://github.com/Xahau/xahaud/blob/88308126ccf5eb1d15010e790c810f1548158832/src/ripple/protocol/TxFlags.h#L88
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).
or
Prio
This is needed for: