mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-28 23:55:49 +00:00
Apply suggestions from @tequdev review
Co-authored-by: tequ <git@tequ.dev>
This commit is contained in:
Rome Reginelli
@@ -4,7 +4,7 @@ seo:
|
||||
---
|
||||
# Credential
|
||||
|
||||
A `Credential` entry represents a [credential](../index.md), which contains an attestation about a _subject_ account from a _credential issuer_ account. The meaning of the attestation is defined by the issuer.
|
||||
A `Credential` entry represents a [credential](../../../../concepts/decentralized-storage/credentials.md), which contains an attestation about a _subject_ account from a _credential issuer_ account. The meaning of the attestation is defined by the issuer.
|
||||
|
||||
## Example Credential JSON
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ labels:
|
||||
# DepositPreauth
|
||||
[[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/LedgerFormats.cpp#L172-L178 "Source")
|
||||
|
||||
A `DepositPreauth` entry tracks a preauthorization from one account. You can always create a preauthorization by sending a [DepositPreauth transaction][], but it has no effect unless you are using [Deposit Authorization](https://xrpl.org/docs/concepts/accounts/depositauth).
|
||||
A `DepositPreauth` entry tracks a preauthorization from one account. You can always create a preauthorization by sending a [DepositPreauth transaction][], but it has no effect unless you are using [Deposit Authorization](../../../../concepts/accounts/depositauth.md).
|
||||
|
||||
A preauthorization allows specific others to send money directly to you even if you have Deposit Authorization enabled. Preauthorizations are one-directional, and have no effect on payments going the opposite direction.
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
seo:
|
||||
description: Accept a credential provisionally issued to your account.
|
||||
---
|
||||
# CredentialAccept Transaction
|
||||
# CredentialAccept
|
||||
|
||||
A CredentialAccept transaction accepts a credential, which makes the credential valid. Only the subject of the credential can do this.
|
||||
|
||||
@@ -42,7 +42,7 @@ The combination of `Account`, `Issuer`, and `CredentialType` must match a `Crede
|
||||
| `tecEXPIRED` | The specified credential has an expiration time in the past. (In this case, the transaction also deletes the expired credentials from the ledger.) |
|
||||
| `tecNO_ENTRY` | The credential uniquely identified by the `Account`, `Issuer`, and `CredentialType` fields of the transaction does not exist in the ledger. |
|
||||
| `temDISABLED` | The related amendment is not enabled. |
|
||||
| `temINVALID_ACCOUNT_ID` | The provided `Issuer` field is invalid. For example, it contains [ACCOUNT_ZERO][]. |
|
||||
| `temINVALID_ACCOUNT_ID` | The provided `Issuer` field is invalid. For example, it contains [ACCOUNT_ZERO](../../../../concepts/accounts/addresses.md#special-addresses). |
|
||||
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
|
||||
@@ -3,7 +3,7 @@ seo:
|
||||
description: Provisionally issue a credential to a subject account.
|
||||
---
|
||||
|
||||
# CredentialCreate Transaction
|
||||
# CredentialCreate
|
||||
|
||||
A CredentialCreate transaction creates a credential in the ledger. The issuer of the credential uses this transaction to provisionally issue a credential. The credential is not valid until the subject of the credential accepts it with a [CredentialAccept transaction][].
|
||||
|
||||
@@ -37,7 +37,7 @@ The `Account` field (the sender) of the transaction is the issuer of the credent
|
||||
|
||||
## Error Cases
|
||||
|
||||
Besides errors that can occur for all transactions, CredentialCreate transactions can result in the following [transaction result codes][]:
|
||||
Besides errors that can occur for all transactions, CredentialCreate transactions can result in the following [transaction result codes](../transaction-results/index.md):
|
||||
|
||||
| Error Code | Description |
|
||||
|:-----------|:------------|
|
||||
@@ -45,7 +45,7 @@ Besides errors that can occur for all transactions, CredentialCreate transaction
|
||||
| `tecEXPIRED` | The credential's expiration time is in the past. |
|
||||
| `tecNO_TARGET` | The account specified in the `Subject` field is not a funded account in the ledger. |
|
||||
| `temDISABLED` | The related amendment is not enabled. |
|
||||
| `temINVALID_ACCOUNT_ID` | The provided `Subject` field is invalid. For example, it contains [ACCOUNT_ZERO][]. |
|
||||
| `temINVALID_ACCOUNT_ID` | The provided `Subject` field is invalid. For example, it contains [ACCOUNT_ZERO](../../../../concepts/accounts/addresses.md#special-addresses). |
|
||||
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
seo:
|
||||
description: Remove a credential from the ledger, effectively revoking it.
|
||||
---
|
||||
# CredentialDelete Transaction
|
||||
# CredentialDelete
|
||||
|
||||
A CredentialDelete transaction removes a credential from the ledger, effectively revoking it. Users may also want to delete an unwanted credential to reduce their [reserve requirement][].
|
||||
A CredentialDelete transaction removes a credential from the ledger, effectively revoking it. Users may also want to delete an unwanted credential to reduce their [reserve requirement](../../../../concepts/accounts/reserves.md).
|
||||
|
||||
## Example CredentialDelete JSON
|
||||
|
||||
@@ -41,7 +41,7 @@ This transaction looks for a [Credential ledger entry](../../ledger-data/ledger-
|
||||
| Error Code | Description |
|
||||
|:-----------|:------------|
|
||||
| `temDISABLED` | The related amendment is not enabled. |
|
||||
| `temINVALID_ACCOUNT_ID` | A provided `Subject` or `Issuer` field is invalid. For example, it contains [ACCOUNT_ZERO][]. |
|
||||
| `temINVALID_ACCOUNT_ID` | A provided `Subject` or `Issuer` field is invalid. For example, it contains [ACCOUNT_ZERO](../../../../concepts/accounts/addresses.md#special-addresses). |
|
||||
| `tecNO_PERMISSION` | The sender is neither the issuer nor subject of the credential, and the credential is not expired. |
|
||||
| `tecNO_ENTRY` | The specified credential does not exist in the ledger. |
|
||||
|
||||
|
||||
@@ -83,7 +83,7 @@ In addition to error types that can occur for all transactions, DepositPreauth t
|
||||
| Error Code | Description |
|
||||
|:--------------------------|:------------|
|
||||
| `tecDUPLICATE` | The transaction would create a preauthorization that already exists. |
|
||||
| `tecINSUFFICIENT_RESERVE` | The sender would not meet the [reserve requirement][] after adding another entry to the ledger. (A DepositPreauth entry counts as one item towards the authorizer's owner reserve.) |
|
||||
| `tecINSUFFICIENT_RESERVE` | The sender would not meet the [reserve requirement](../../../../concepts/accounts/reserves.md) after adding another entry to the ledger. (A DepositPreauth entry counts as one item towards the authorizer's owner reserve.) |
|
||||
| `tecNO_ENTRY` | The transaction tried to revoke a preauthorization that does not exist in the ledger. |
|
||||
| `tecNO_ISSUER` | One or more specified credential issuers does not exist in the ledger. |
|
||||
| `tecNO_TARGET` | The transaction tried to authorize an account that is not a funded account in the ledger. |
|
||||
|
||||
Reference in New Issue
Block a user