申し訳ありませんが、このページはお使いの言語では提供されていません。
XRP Ledger Dev Portalをさまざまな言語で提供するよう取り組んでいますが、すべてのページがすべての言語で提供されているわけではありません。ご協力いただける場合は、ぜひ貢献をお願いいたします
UNLModify
(Requires the NegativeUNL amendment )
A UNLModify pseudo-transaction marks a change to the Negative UNL, indicating that a trusted validator has gone offline or come back online.
Note: You cannot send a pseudo-transaction, but you may find one when processing ledgers.
Example UNLModify JSON
{
"Account": "",
"Fee": "0",
"LedgerSequence": 1600000,
"Sequence": 0,
"SigningPubKey": "",
"TransactionType": "UNLModify",
"UNLModifyDisabling": 1,
"UNLModifyValidator": "ED6629D456285AE3613B285F65BBFF168D695BA3921F309949AFCD2CA7AFEC16FE",
}
UNLModify Fields
UNLModify Fields
In addition to the common fields, a UNLModify pseudo-transaction uses the following fields:
| Name | JSON Type | Internal Type | Description |
|---|---|---|---|
TransactionType |
String | UInt16 | The value 0x0066, mapped to the string UNLModify, indicates that this object is an UNLModify pseudo-transaction. |
LedgerSequence |
Number | UInt32 | The ledger index where this pseudo-transaction appears. This distinguishes the pseudo-transaction from other occurrences of the same change. |
UNLModifyDisabling |
Number | UInt8 | If 1, this change represents adding a validator to the Negative UNL. If 0, this change represents removing a validator from the Negative UNL. (No other values are allowed.) |
UNLModifyValidator |
String | Blob | The validator to add or remove, as identified by its master public key. |