You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`LedgerStateFix` is a general purpose transaction used to fix specific issues affecting the XRP ledger. You submit the transaction with the `LedgerFixType` value set to indicate the particular error state to correct.
12
+
13
+
_(Added by the [fixNFTokenPageLinks amendment][])_
|`LedgerFixType`| Number | UInt16 | Yes | The type of fix to apply. See [LedgerFixType](#ledgerfixtype) for possible values. Currently the only type is `1`, which fixes the NFToken directory for a single account. |
34
+
|`Owner`| String - [Address][]| Account | No |_(Required if `LedgerFixType` is `1`.)_ The account that owns the NFToken directory to fix. Does not need any relationship to the sender of the transaction. |
35
+
36
+
37
+
## LedgerFixType
38
+
39
+
`LedgerStateFix` transactions are targeted solutions for rare and specific issues. They can only be used to fix a specific type of ledger corruption, described below.
40
+
41
+
### Type 1
42
+
43
+
Corrupt NFT directories resulting from these conditions:
44
+
45
+
- At least two NFToken pages were in the directory.
46
+
- The next-to-last page was completely full, holding 32 NFTokens.
47
+
- The last page of the directory contained only one NFToken.
48
+
- A transaction removed the last remaining token from the last page, causing the directory to delete the page.
49
+
50
+
When these conditions were met, the NFToken directory didn't properly update page links, causing holes in the directory when new last pages were created for additional NFTokens.
51
+
52
+
The [fixNFTokenPageLinks amendment][] prevents new instances of this type of ledger corruption from happening.
53
+
54
+
55
+
## Special Transaction Cost
56
+
57
+
The `LedgerStateFix` transaction is rare and potentially compute intensive, so the transaction must pay a special [transaction cost][] equal to at least the [owner reserve](../../../../concepts/accounts/reserves.md) for one item (currently {% $env.PUBLIC_OWNER_RESERVE %}).
58
+
59
+
The transaction cost always applies when a transaction is included in a validated ledger, even if the transaction fails. (See [Error Cases](#error-cases).) To greatly reduce the chances of paying the high transaction cost if the transaction fails, [submit the transaction](../../../http-websocket-apis/public-api-methods/transaction-methods/submit.md) with `fail_hard` enabled.
60
+
61
+
62
+
## Error Cases
63
+
64
+
Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md):
65
+
66
+
| Error Code | Description |
67
+
|:-----------------------------|:------------|
68
+
|`tecFAILED_PROCESSING`| The transaction failed to apply the fix. For example, the transaction attempted to repair an NFT directory that was not broken. |
69
+
|`tecOBJECT_NOT_FOUND`| A ledger entry specified in the transaction does not exist. For example, the transaction tried to repair the NFT directory of an account that does not hold any NFTs. |
70
+
|`tefINVALID_LEDGER_FIX_TYPE`| The [`LedgerFixType`](#ledgerfixtype) value specified in the transaction is not valid. Currently, the only valid type is `1`. |
0 commit comments