mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-04 20:05:50 +00:00
Merge branch 'master' into ja-tx-example-tag
This commit is contained in:
Rome Reginelli
@@ -2,95 +2,70 @@
|
||||
[AMM entry]: /docs/references/protocol/ledger-data/ledger-entry-types/amm.md
|
||||
[AMMClawback amendment]: /resources/known-amendments.md#ammclawback
|
||||
[AMM object]: /docs/references/protocol/ledger-data/ledger-entry-types/amm.md
|
||||
[AMMエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/amm.md
|
||||
[AMMオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/amm.md
|
||||
[AMMBid transaction]: /docs/references/protocol/transactions/types/ammbid.md
|
||||
[AMMBid transactions]: /docs/references/protocol/transactions/types/ammbid.md
|
||||
[AMMBid]: /docs/references/protocol/transactions/types/ammbid.md
|
||||
[AMMBidトランザクション]: /docs/references/protocol/transactions/types/ammbid.md
|
||||
[AMMClawback transaction]: /docs/references/protocol/transactions/types/ammclawback.md
|
||||
[AMMCreate transaction]: /docs/references/protocol/transactions/types/ammcreate.md
|
||||
[AMMCreate transactions]: /docs/references/protocol/transactions/types/ammcreate.md
|
||||
[AMMCreate]: /docs/references/protocol/transactions/types/ammcreate.md
|
||||
[AMMCreateトランザクション]: /docs/references/protocol/transactions/types/ammcreate.md
|
||||
[AMMDelete transaction]: /docs/references/protocol/transactions/types/ammdelete.md
|
||||
[AMMDelete transactions]: /docs/references/protocol/transactions/types/ammdelete.md
|
||||
[AMMDelete]: /docs/references/protocol/transactions/types/ammdelete.md
|
||||
[AMMDeleteトランザクション]: /docs/references/protocol/transactions/types/ammdelete.md
|
||||
[AMMDeposit transaction]: /docs/references/protocol/transactions/types/ammdeposit.md
|
||||
[AMMDeposit transactions]: /docs/references/protocol/transactions/types/ammdeposit.md
|
||||
[AMMDeposit]: /docs/references/protocol/transactions/types/ammdeposit.md
|
||||
[AMMDepositトランザクション]: /docs/references/protocol/transactions/types/ammdeposit.md
|
||||
[AMMVote transaction]: /docs/references/protocol/transactions/types/ammvote.md
|
||||
[AMMVote transactions]: /docs/references/protocol/transactions/types/ammvote.md
|
||||
[AMMVote]: /docs/references/protocol/transactions/types/ammvote.md
|
||||
[AMMVoteトランザクション]: /docs/references/protocol/transactions/types/ammvote.md
|
||||
[AMMWithdraw transaction]: /docs/references/protocol/transactions/types/ammwithdraw.md
|
||||
[AMMWithdraw transactions]: /docs/references/protocol/transactions/types/ammwithdraw.md
|
||||
[AMMWithdraw]: /docs/references/protocol/transactions/types/ammwithdraw.md
|
||||
[AMMWithdrawトランザクション]: /docs/references/protocol/transactions/types/ammwithdraw.md
|
||||
[API v1]: /docs/references/http-websocket-apis/api-conventions/request-formatting.md#api-versioning
|
||||
[API v2]: /docs/references/http-websocket-apis/api-conventions/request-formatting.md#api-versioning
|
||||
[AccountDelete transaction]: /docs/references/protocol/transactions/types/accountdelete.md
|
||||
[AccountDelete transactions]: /docs/references/protocol/transactions/types/accountdelete.md
|
||||
[AccountDelete]: /docs/references/protocol/transactions/types/accountdelete.md
|
||||
[AccountDeleteトランザクション]: /docs/references/protocol/transactions/types/accountdelete.md
|
||||
[AccountRoot entry]: /docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md
|
||||
[AccountRoot object]: /docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md
|
||||
[AccountRootエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md
|
||||
[AccountRootオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/accountroot.md
|
||||
[AccountSet transaction]: /docs/references/protocol/transactions/types/accountset.md
|
||||
[AccountSet transactions]: /docs/references/protocol/transactions/types/accountset.md
|
||||
[AccountSet]: /docs/references/protocol/transactions/types/accountset.md
|
||||
[AccountSetトランザクション]: /docs/references/protocol/transactions/types/accountset.md
|
||||
[Address]: /docs/references/protocol/data-types/basic-data-types.md#addresses
|
||||
[Amendments entry]: /docs/concepts/networks-and-servers/amendments.md
|
||||
[Amendments object]: /docs/concepts/networks-and-servers/amendments.md
|
||||
[Amendmentsエントリ]: /docs/concepts/networks-and-servers/amendments.md
|
||||
[Amendmentsオブジェクト]: /docs/concepts/networks-and-servers/amendments.md
|
||||
[Batch amendment]: /resources/known-amendments.md#batch
|
||||
[Batch]: /docs/references/protocol/transactions/types/batch.md
|
||||
[Batch transaction]: /docs/references/protocol/transactions/types/batch.md
|
||||
[Batch transactions]: /docs/references/protocol/transactions/types/batch.md
|
||||
[Check entry]: /docs/references/protocol/ledger-data/ledger-entry-types/check.md
|
||||
[Check object]: /docs/references/protocol/ledger-data/ledger-entry-types/check.md
|
||||
[Checkエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/check.md
|
||||
[Checkオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/check.md
|
||||
[CheckCancel transaction]: /docs/references/protocol/transactions/types/checkcancel.md
|
||||
[CheckCancel transactions]: /docs/references/protocol/transactions/types/checkcancel.md
|
||||
[CheckCancel]: /docs/references/protocol/transactions/types/checkcancel.md
|
||||
[CheckCancelトランザクション]: /docs/references/protocol/transactions/types/checkcancel.md
|
||||
[CheckCash transaction]: /docs/references/protocol/transactions/types/checkcash.md
|
||||
[CheckCash transactions]: /docs/references/protocol/transactions/types/checkcash.md
|
||||
[CheckCashMakesTrustLine amendment]: /resources/known-amendments.md#checkcashmakestrustline
|
||||
[CheckCash]: /docs/references/protocol/transactions/types/checkcash.md
|
||||
[CheckCashトランザクション]: /docs/references/protocol/transactions/types/checkcash.md
|
||||
[CheckCreate transaction]: /docs/references/protocol/transactions/types/checkcreate.md
|
||||
[CheckCreate transactions]: /docs/references/protocol/transactions/types/checkcreate.md
|
||||
[CheckCreate]: /docs/references/protocol/transactions/types/checkcreate.md
|
||||
[CheckCreateトランザクション]: /docs/references/protocol/transactions/types/checkcreate.md
|
||||
[Checks amendment]: /resources/known-amendments.md#checks
|
||||
[Clawback amendment]: /resources/known-amendments.md#clawback
|
||||
[Clawbackの修正]: /resources/known-amendments.md#clawback
|
||||
[Clawback transaction]: /docs/references/protocol/transactions/types/clawback.md
|
||||
[Clawback transactions]: /docs/references/protocol/transactions/types/clawback.md
|
||||
[Clawbackトランザクション]: /docs/references/protocol/transactions/types/clawback.md
|
||||
[credentials]: /docs/concepts/decentralized-storage/credentials.md
|
||||
[Credentials amendment]: /resources/known-amendments.md#credentials
|
||||
[CredentialCreate transaction]: /docs/references/protocol/transactions/types/credentialcreate.md
|
||||
[CredentialCreate transactions]: /docs/references/protocol/transactions/types/credentialcreate.md
|
||||
[CredentialCreate]: /docs/references/protocol/transactions/types/credentialcreate.md
|
||||
[CredentialCreateトランザクション]: /docs/references/protocol/transactions/types/credentialcreate.md
|
||||
[CredentialAccept transaction]: /docs/references/protocol/transactions/types/credentialaccept.md
|
||||
[CredentialAccept transactions]: /docs/references/protocol/transactions/types/credentialaccept.md
|
||||
[CredentialAccept]: /docs/references/protocol/transactions/types/credentialaccept.md
|
||||
[CredentialAcceptトランザクション]: /docs/references/protocol/transactions/types/credentialaccept.md
|
||||
[CredentialDelete transaction]: /docs/references/protocol/transactions/types/credentialdelete.md
|
||||
[CredentialDelete transactions]: /docs/references/protocol/transactions/types/credentialdelete.md
|
||||
[CredentialDelete]: /docs/references/protocol/transactions/types/credentialdelete.md
|
||||
[CredentialDeleteトランザクション]: /docs/references/protocol/transactions/types/credentialdelete.md
|
||||
[Credential entry]: /docs/references/protocol/ledger-data/ledger-entry-types/credential
|
||||
[Credentialエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/credential
|
||||
[Crypto-Conditions Specification]: https://tools.ietf.org/html/draft-thomas-crypto-conditions-04
|
||||
[CryptoConditions amendment]: /resources/known-amendments.md#cryptoconditions
|
||||
[CryptoConditionsSuite amendment]: /resources/known-amendments.md#cryptoconditionssuite
|
||||
@@ -98,57 +73,46 @@
|
||||
[Currency Code]: /docs/references/protocol/data-types/currency-formats.md#currency-codes
|
||||
[DID amendment]: /resources/known-amendments.md#did
|
||||
[DID entry]: /docs/references/protocol/ledger-data/ledger-entry-types/did.md
|
||||
[DIDエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/did.md
|
||||
[DeletableAccounts amendment]: /resources/known-amendments.md#deletableaccounts
|
||||
[DeepFreeze amendment]: /resources/known-amendments.md#deepfreeze
|
||||
[Delegate ledger entry]: /docs/references/protocol/ledger-data/ledger-entry-types/delegate.md
|
||||
[DelegateSet]: /docs/references/protocol/transactions/types/delegateset.md
|
||||
[DelegateSet transaction]: /docs/references/protocol/transactions/types/delegateset.md
|
||||
[DelegateSet transactions]: /docs/references/protocol/transactions/types/delegateset.md
|
||||
[DepositAuth amendment]: /resources/known-amendments.md#depositauth
|
||||
[DepositPreauth amendment]: /resources/known-amendments.md#depositpreauth
|
||||
[DepositPreauth entry]: /docs/references/protocol/transactions/types/depositpreauth.md
|
||||
[DepositPreauth object]: /docs/references/protocol/transactions/types/depositpreauth.md
|
||||
[DepositPreauthエントリ]: /docs/references/protocol/transactions/types/depositpreauth.md
|
||||
[DepositPreauthオブジェクト]: /docs/references/protocol/transactions/types/depositpreauth.md
|
||||
[DepositPreauth transaction]: /docs/references/protocol/transactions/types/depositpreauth.md
|
||||
[DepositPreauth transactions]: /docs/references/protocol/transactions/types/depositpreauth.md
|
||||
[DepositPreauth]: /docs/references/protocol/transactions/types/depositpreauth.md
|
||||
[DepositPreauthトランザクション]: /docs/references/protocol/transactions/types/depositpreauth.md
|
||||
[DIDSet transaction]: /docs/references/protocol/transactions/types/didset.md
|
||||
[DIDSet transactions]: /docs/references/protocol/transactions/types/didset.md
|
||||
[DIDSet]: /docs/references/protocol/transactions/types/didset.md
|
||||
[DIDSetトランザクション]: /docs/references/protocol/transactions/types/didset.md
|
||||
[DirectoryNode entry]: /docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md
|
||||
[DirectoryNode object]: /docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md
|
||||
[DirectoryNodeエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md
|
||||
[DirectoryNodeオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/directorynode.md
|
||||
[DisallowIncoming amendment]: /resources/known-amendments.md#disallowincoming
|
||||
[DynamicNFT amendment]: /resources/known-amendments.md#dynamicnft
|
||||
[EnableAmendment pseudo-transaction]: /docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md
|
||||
[EnableAmendment pseudo-transactions]: /docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md
|
||||
[EnableAmendment]: /docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md
|
||||
[EnableAmendment疑似トランザクション]: /docs/references/protocol/transactions/pseudo-transaction-types/enableamendment.md
|
||||
[EnforceInvariants amendment]: /resources/known-amendments.md#enforceinvariants
|
||||
[Escrow amendment]: /resources/known-amendments.md#escrow
|
||||
[Escrow entry]: /docs/concepts/payment-types/escrow.md
|
||||
[Escrow object]: /docs/concepts/payment-types/escrow.md
|
||||
[Escrowエントリ]: /docs/concepts/payment-types/escrow.md
|
||||
[Escrowオブジェクト]: /docs/concepts/payment-types/escrow.md
|
||||
[EscrowCancel transaction]: /docs/references/protocol/transactions/types/escrowcancel.md
|
||||
[EscrowCancel transactions]: /docs/references/protocol/transactions/types/escrowcancel.md
|
||||
[EscrowCancel]: /docs/references/protocol/transactions/types/escrowcancel.md
|
||||
[EscrowCancelトランザクション]: /docs/references/protocol/transactions/types/escrowcancel.md
|
||||
[EscrowCreate transaction]: /docs/references/protocol/transactions/types/escrowcreate.md
|
||||
[EscrowCreate transactions]: /docs/references/protocol/transactions/types/escrowcreate.md
|
||||
[EscrowCreate]: /docs/references/protocol/transactions/types/escrowcreate.md
|
||||
[EscrowCreateトランザクション]: /docs/references/protocol/transactions/types/escrowcreate.md
|
||||
[EscrowFinish transaction]: /docs/references/protocol/transactions/types/escrowfinish.md
|
||||
[EscrowFinish transactions]: /docs/references/protocol/transactions/types/escrowfinish.md
|
||||
[EscrowFinish]: /docs/references/protocol/transactions/types/escrowfinish.md
|
||||
[EscrowFinishトランザクション]: /docs/references/protocol/transactions/types/escrowfinish.md
|
||||
[ExpandedSignerList amendment]: /resources/known-amendments.md#expandedsignerlist
|
||||
[FeeEscalation amendment]: /resources/known-amendments.md#feeescalation
|
||||
[FeeSettings entry]: /docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md
|
||||
[FeeSettings object]: /docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md
|
||||
[FeeSettingsエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md
|
||||
[FeeSettingsオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/feesettings.md
|
||||
[Flow amendment]: /resources/known-amendments.md#flow
|
||||
[FlowCross amendment]: /resources/known-amendments.md#flowcross
|
||||
[FlowV2 amendment]: /resources/known-amendments.md#flowv2
|
||||
@@ -164,98 +128,75 @@
|
||||
[LedgerStateFix transaction]: /docs/references/protocol/transactions/types/ledgerstatefix.md
|
||||
[LedgerStateFix transactions]: /docs/references/protocol/transactions/types/ledgerstatefix.md
|
||||
[LedgerStateFix]: /docs/references/protocol/transactions/types/ledgerstatefix.md
|
||||
[LedgerStateFixトランザクション]: /docs/references/protocol/transactions/types/ledgerstatefix.md
|
||||
[Marker]: /docs/references/http-websocket-apis/api-conventions/markers-and-pagination.md
|
||||
[MPTokenIssuanceSet]: /docs/references/protocol/transactions/types/mptokenissuanceset.md
|
||||
[MPTokenIssuanceSet transaction]: /docs/references/protocol/transactions/types/mptokenissuanceset.md
|
||||
[MPTokenIssuanceSet transactions]: /docs/references/protocol/transactions/types/mptokenissuanceset.md
|
||||
[MPTokensV1 amendment]: /resources/known-amendments.md#mptokensv1
|
||||
[MultiSign amendment]: /resources/known-amendments.md#multisign
|
||||
[MultiSignReserve amendment]: /resources/known-amendments.md#multisignreserve
|
||||
[NFTokenAcceptOffer transaction]: /docs/references/protocol/transactions/types/nftokenacceptoffer.md
|
||||
[NFTokenAcceptOffer transactions]: /docs/references/protocol/transactions/types/nftokenacceptoffer.md
|
||||
[NFTokenAcceptOffer]: /docs/references/protocol/transactions/types/nftokenacceptoffer.md
|
||||
[NFTokenAcceptOfferトランザクション]: /docs/references/protocol/transactions/types/nftokenacceptoffer.md
|
||||
[NFTokenBurn transaction]: /docs/references/protocol/transactions/types/nftokenburn.md
|
||||
[NFTokenBurn transactions]: /docs/references/protocol/transactions/types/nftokenburn.md
|
||||
[NFTokenBurn]: /docs/references/protocol/transactions/types/nftokenburn.md
|
||||
[NFTokenBurnトランザクション]: /docs/references/protocol/transactions/types/nftokenburn.md
|
||||
[NFTokenCancelOffer transaction]: /docs/references/protocol/transactions/types/nftokencanceloffer.md
|
||||
[NFTokenCancelOffer transactions]: /docs/references/protocol/transactions/types/nftokencanceloffer.md
|
||||
[NFTokenCancelOffer]: /docs/references/protocol/transactions/types/nftokencanceloffer.md
|
||||
[NFTokenCancelOfferトランザクション]: /docs/references/protocol/transactions/types/nftokencanceloffer.md
|
||||
[NFTokenCreateOffer transaction]: /docs/references/protocol/transactions/types/nftokencreateoffer.md
|
||||
[NFTokenCreateOffer transactions]: /docs/references/protocol/transactions/types/nftokencreateoffer.md
|
||||
[NFTokenCreateOffer]: /docs/references/protocol/transactions/types/nftokencreateoffer.md
|
||||
[NFTokenCreateOfferトランザクション]: /docs/references/protocol/transactions/types/nftokencreateoffer.md
|
||||
[NFTokenMint transaction]: /docs/references/protocol/transactions/types/nftokenmint.md
|
||||
[NFTokenMint transactions]: /docs/references/protocol/transactions/types/nftokenmint.md
|
||||
[NFTokenMint]: /docs/references/protocol/transactions/types/nftokenmint.md
|
||||
[NFTokenMintトランザクション]: /docs/references/protocol/transactions/types/nftokenmint.md
|
||||
[NFTokenOffer entry]: /docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md
|
||||
[NFTokenOffer object]: /docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md
|
||||
[NFTokenOfferエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md
|
||||
[NFTokenOfferオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/nftokenoffer.md
|
||||
[NFTokenPage entry]: /docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md
|
||||
[NFTokenPage object]: /docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md
|
||||
[NFTokenPageエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md
|
||||
[NFTokenPageオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/nftokenpage.md
|
||||
[NFToken]: /docs/references/protocol/data-types/nftoken.md
|
||||
[NegativeUNL amendment]: /resources/known-amendments.md#negativeunl
|
||||
[NegativeUNL entry]: /docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md
|
||||
[NegativeUNL object]: /docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md
|
||||
[NegativeUNLエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md
|
||||
[NegativeUNLオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/negativeunl.md
|
||||
[NonFungibleTokensV1 amendment]: /resources/known-amendments.md#nonfungibletokensv1
|
||||
[NonFungibleTokensV1_1 amendment]: /resources/known-amendments.md#nonfungibletokensv1_1
|
||||
[Offer entry]: /docs/references/protocol/ledger-data/ledger-entry-types/offer.md
|
||||
[Offer object]: /docs/references/protocol/ledger-data/ledger-entry-types/offer.md
|
||||
[Offerエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/offer.md
|
||||
[Offerオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/offer.md
|
||||
[OfferCancel transaction]: /docs/references/protocol/transactions/types/offercancel.md
|
||||
[OfferCancel transactions]: /docs/references/protocol/transactions/types/offercancel.md
|
||||
[OfferCancel]: /docs/references/protocol/transactions/types/offercancel.md
|
||||
[OfferCancelトランザクション]: /docs/references/protocol/transactions/types/offercancel.md
|
||||
[OfferCreate transaction]: /docs/references/protocol/transactions/types/offercreate.md
|
||||
[OfferCreate transactions]: /docs/references/protocol/transactions/types/offercreate.md
|
||||
[OfferCreate]: /docs/references/protocol/transactions/types/offercreate.md
|
||||
[OfferCreateトランザクション]: /docs/references/protocol/transactions/types/offercreate.md
|
||||
[OracleDelete transaction]: /docs/references/protocol/transactions/types/oracledelete.md
|
||||
[OracleDeleteトランザクション]: /docs/references/protocol/transactions/types/oracledelete.md
|
||||
[OracleDelete transactions]: /docs/references/protocol/transactions/types/oracledelete.md
|
||||
[OracleDeleteトランザクション]: /docs/references/protocol/transactions/types/oracledelete.md
|
||||
[Oracle entry]: /docs/references/protocol/ledger-data/ledger-entry-types/oracle.md
|
||||
[Oracleエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/oracle.md
|
||||
[Oracle object]: /docs/references/protocol/ledger-data/ledger-entry-types/oracle.md
|
||||
[Oracleオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/oracle.md
|
||||
[OracleSet transaction]: /docs/references/protocol/transactions/types/oracleset.md
|
||||
[OracleSetトランザクション]: /docs/references/protocol/transactions/types/oracleset.md
|
||||
[OracleSet transactions]: /docs/references/protocol/transactions/types/oracleset.md
|
||||
[OracleSetトランザクション]: /docs/references/protocol/transactions/types/oracleset.md
|
||||
[OwnerPaysFee amendment]: /resources/known-amendments.md#ownerpaysfee
|
||||
[PayChan amendment]: /resources/known-amendments.md#paychan
|
||||
[PayChannel entry]: /docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md
|
||||
[PayChannel object]: /docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md
|
||||
[PayChannelエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md
|
||||
[PayChannelオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/paychannel.md
|
||||
[Payment transaction]: /docs/references/protocol/transactions/types/payment.md
|
||||
[Payment transactions]: /docs/references/protocol/transactions/types/payment.md
|
||||
[PaymentChannelClaim transaction]: /docs/references/protocol/transactions/types/paymentchannelclaim.md
|
||||
[PaymentChannelClaim transactions]: /docs/references/protocol/transactions/types/paymentchannelclaim.md
|
||||
[PaymentChannelClaim]: /docs/references/protocol/transactions/types/paymentchannelclaim.md
|
||||
[PaymentChannelClaimトランザクション]: /docs/references/protocol/transactions/types/paymentchannelclaim.md
|
||||
[PaymentChannelCreate transaction]: /docs/references/protocol/transactions/types/paymentchannelcreate.md
|
||||
[PaymentChannelCreate transactions]: /docs/references/protocol/transactions/types/paymentchannelcreate.md
|
||||
[PaymentChannelCreate]: /docs/references/protocol/transactions/types/paymentchannelcreate.md
|
||||
[PaymentChannelCreateトランザクション]: /docs/references/protocol/transactions/types/paymentchannelcreate.md
|
||||
[PaymentChannelFund transaction]: /docs/references/protocol/transactions/types/paymentchannelfund.md
|
||||
[PaymentChannelFund transactions]: /docs/references/protocol/transactions/types/paymentchannelfund.md
|
||||
[PaymentChannelFund]: /docs/references/protocol/transactions/types/paymentchannelfund.md
|
||||
[PaymentChannelFundトランザクション]: /docs/references/protocol/transactions/types/paymentchannelfund.md
|
||||
[Payment]: /docs/references/protocol/transactions/types/payment.md
|
||||
[Paymentトランザクション]: /docs/references/protocol/transactions/types/payment.md
|
||||
[PermissionDelegation amendment]: /resources/known-amendments.md#permissiondelegation
|
||||
[PermissionedDEX amendment]: /resources/known-amendments.md#permissioneddex
|
||||
[PermissionedDomainSet transaction]: /docs/references/protocol/transactions/types/permissioneddomainset.md
|
||||
[PermissionedDomainSetトランザクション]: /@l10n/ja/docs/references/protocol/transactions/types/permissioneddomainset.md
|
||||
[PermissionedDomains amendment]: /resources/known-amendments.md#permissioneddomains
|
||||
[permissioned domain]: /docs/concepts/tokens/decentralized-exchange/permissioned-domains.md
|
||||
[許可型ドメイン]: /@l10n/ja/docs/concepts/tokens/decentralized-exchange/permissioned-domains.md
|
||||
[PriceOracle amendment]: /resources/known-amendments.md#priceoracle
|
||||
[MPToken entry]: /docs/references/protocol/ledger-data/ledger-entry-types/mptoken.md
|
||||
[MPTokenAuthorize transaction]: /docs/references/protocol/transactions/types/mptokenauthorize.md
|
||||
@@ -268,29 +209,20 @@
|
||||
[RequireFullyCanonicalSig amendment]: /resources/known-amendments.md#requirefullycanonicalsig
|
||||
[RippleState entry]: /docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md
|
||||
[RippleState object]: /docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md
|
||||
[RippleStateエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md
|
||||
[RippleStateオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/ripplestate.md
|
||||
[Rippleエポック以降の経過秒数]: /docs/references/protocol/data-types/basic-data-types.md#時間の指定
|
||||
[SHA-512Half]: /docs/references/protocol/data-types/basic-data-types.md#hashes
|
||||
[SHA-512ハーフ]: /docs/references/protocol/data-types/basic-data-types.md#ハッシュ
|
||||
[SHAMapV2 amendment]: /resources/known-amendments.md#shamapv2
|
||||
[Sequence Number]: /docs/references/protocol/data-types/basic-data-types.md#account-sequence
|
||||
[SetFee pseudo-transaction]: /docs/references/protocol/transactions/pseudo-transaction-types/setfee.md
|
||||
[SetFee pseudo-transactions]: /docs/references/protocol/transactions/pseudo-transaction-types/setfee.md
|
||||
[SetFee]: /docs/references/protocol/transactions/pseudo-transaction-types/setfee.md
|
||||
[SetFee疑似トランザクション]: /docs/references/protocol/transactions/pseudo-transaction-types/setfee.md
|
||||
[SetRegularKey transaction]: /docs/references/protocol/transactions/types/setregularkey.md
|
||||
[SetRegularKey transactions]: /docs/references/protocol/transactions/types/setregularkey.md
|
||||
[SetRegularKey]: /docs/references/protocol/transactions/types/setregularkey.md
|
||||
[SetRegularKeyトランザクション]: /docs/references/protocol/transactions/types/setregularkey.md
|
||||
[SignerList entry]: /docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md
|
||||
[SignerList object]: /docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md
|
||||
[SignerListエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md
|
||||
[SignerListオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/signerlist.md
|
||||
[SignerListSet transaction]: /docs/references/protocol/transactions/types/signerlistset.md
|
||||
[SignerListSet transactions]: /docs/references/protocol/transactions/types/signerlistset.md
|
||||
[SignerListSet]: /docs/references/protocol/transactions/types/signerlistset.md
|
||||
[SignerListSetトランザクション]: /docs/references/protocol/transactions/types/signerlistset.md
|
||||
[SingleAssetVault amendment]: /resources/known-amendments.md#singleassetvault
|
||||
[SortedDirectories amendment]: /resources/known-amendments.md#sorteddirectories
|
||||
[Specifying Currency Amounts]: /docs/references/protocol/data-types/basic-data-types.md#specifying-currency-amounts
|
||||
@@ -301,13 +233,10 @@
|
||||
[TickSize amendment]: /resources/known-amendments.md#ticksize
|
||||
[Ticket entry]: /docs/references/protocol/ledger-data/ledger-entry-types/ticket.md
|
||||
[Ticket object]: /docs/references/protocol/ledger-data/ledger-entry-types/ticket.md
|
||||
[Ticketエントリ]: /docs/references/protocol/ledger-data/ledger-entry-types/ticket.md
|
||||
[Ticketオブジェクト]: /docs/references/protocol/ledger-data/ledger-entry-types/ticket.md
|
||||
[TicketBatch amendment]: /resources/known-amendments.md#ticketbatch
|
||||
[TicketCreate transaction]: /docs/references/protocol/transactions/types/ticketcreate.md
|
||||
[TicketCreate transactions]: /docs/references/protocol/transactions/types/ticketcreate.md
|
||||
[TicketCreate]: /docs/references/protocol/transactions/types/ticketcreate.md
|
||||
[TicketCreateトランザクション]: /docs/references/protocol/transactions/types/ticketcreate.md
|
||||
[Tickets amendment]: /resources/known-amendments.md#tickets
|
||||
[TokenEscrow amendment]: /resources/known-amendments.md#tokenescrow
|
||||
[Transaction Cost]: /docs/concepts/transactions/transaction-cost.md
|
||||
@@ -315,102 +244,73 @@
|
||||
[TrustSet transactions]: /docs/references/protocol/transactions/types/trustset.md
|
||||
[TrustSetAuth amendment]: /resources/known-amendments.md#trustsetauth
|
||||
[TrustSet]: /docs/references/protocol/transactions/types/trustset.md
|
||||
[TrustSetトランザクション]: /docs/references/protocol/transactions/types/trustset.md
|
||||
[UNLModify pseudo-transaction]: /docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md
|
||||
[UNLModify pseudo-transactions]: /docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md
|
||||
[UNLModify]: /docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md
|
||||
[UNLModify疑似トランザクション]: /docs/references/protocol/transactions/pseudo-transaction-types/unlmodify.md
|
||||
[XChainAddAccountCreateAttestation transaction]: /docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md
|
||||
[XChainAddAccountCreateAttestation transactions]: /docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md
|
||||
[XChainAddAccountCreateAttestation]: /docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md
|
||||
[XChainAddAccountCreateAttestationトランザクション]: /docs/references/protocol/transactions/types/xchainaddaccountcreateattestation.md
|
||||
[XChainAddClaimAttestation transaction]: /docs/references/protocol/transactions/types/xchainaddclaimattestation.md
|
||||
[XChainAddClaimAttestation transactions]: /docs/references/protocol/transactions/types/xchainaddclaimattestation.md
|
||||
[XChainAddClaimAttestationトランザクション]: /docs/references/protocol/transactions/types/xchainaddclaimattestation.md
|
||||
[XChainBridge amendment]: /resources/known-amendments.md#xchainbridge
|
||||
[XChainCreateBridge transaction]: /docs/references/protocol/transactions/types/xchaincreatebridge.md
|
||||
[XChainCreateBridge transactions]: /docs/references/protocol/transactions/types/xchaincreatebridge.md
|
||||
[XChainCreateBridge]: /docs/references/protocol/transactions/types/xchaincreatebridge.md
|
||||
[XChainCreateBridgeトランザクション]: /docs/references/protocol/transactions/types/xchaincreatebridge.md
|
||||
[XChainCreateClaimID transaction]: /docs/references/protocol/transactions/types/xchaincreateclaimid.md
|
||||
[XChainCreateClaimID transactions]: /docs/references/protocol/transactions/types/xchaincreateclaimid.md
|
||||
[XChainCreateClaimID]: /docs/references/protocol/transactions/types/xchaincreateclaimid.md
|
||||
[XChainCreateClaimIDトランザクション]: /docs/references/protocol/transactions/types/xchaincreateclaimid.md
|
||||
[XChainOwnedClaimID entry]: /docs/references/protocol/ledger-data/ledger-entry-types/xchainownedclaimid
|
||||
[XRP, in drops]: /docs/references/protocol/data-types/basic-data-types.md#specifying-currency-amounts
|
||||
[XRPFees amendment]: /resources/known-amendments.md#xrpfees
|
||||
[XRP、drop単位]: /docs/references/protocol/data-types/basic-data-types.md#通貨額の指定
|
||||
[XRPのdrop数]: /docs/references/protocol/data-types/basic-data-types.md#通貨額の指定
|
||||
[account_channels command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md
|
||||
[account_channels method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md
|
||||
[account_channelsメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_channels.md
|
||||
[account_currencies command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md
|
||||
[account_currencies method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md
|
||||
[account_currenciesメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_currencies.md
|
||||
[account_info command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md
|
||||
[account_info method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md
|
||||
[account_infoメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_info.md
|
||||
[account_lines command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md
|
||||
[account_lines method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md
|
||||
[account_linesメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_lines.md
|
||||
[account_nfts command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md
|
||||
[account_nfts method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md
|
||||
[account_nftsメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_nfts.md
|
||||
[account_objects command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md
|
||||
[account_objects method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md
|
||||
[account_objectsメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_objects.md
|
||||
[account_offers command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md
|
||||
[account_offers method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md
|
||||
[account_offersメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_offers.md
|
||||
[account_tx command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md
|
||||
[account_tx method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md
|
||||
[account_txメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/account_tx.md
|
||||
[admin command]: /docs/references/http-websocket-apis/admin-api-methods/index.md
|
||||
[amm_info command]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md
|
||||
[amm_info method]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md
|
||||
[amm_infoメソッド]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/amm_info.md
|
||||
[base58]: /docs/references/protocol/data-types/base58-encodings.md
|
||||
[book_offers command]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md
|
||||
[book_offers method]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md
|
||||
[book_offersメソッド]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/book_offers.md
|
||||
[can_delete command]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md
|
||||
[can_delete method]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md
|
||||
[can_deleteメソッド]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete.md
|
||||
[channel_authorize command]: /docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md
|
||||
[channel_authorize method]: /docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md
|
||||
[channel_authorizeメソッド]: /docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize.md
|
||||
[channel_verify command]: /docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md
|
||||
[channel_verify method]: /docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md
|
||||
[channel_verifyメソッド]: /docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_verify.md
|
||||
[common fields]: /docs/references/protocol/transactions/common-fields.md
|
||||
[connect command]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md
|
||||
[connect method]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md
|
||||
[connectメソッド]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect.md
|
||||
[consensus_info command]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md
|
||||
[consensus_info method]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md
|
||||
[consensus_infoメソッド]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info.md
|
||||
[crawl_shards command]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md
|
||||
[crawl_shards method]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md
|
||||
[crawl_shardsメソッド]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/crawl_shards.md
|
||||
[crypto-condition]: https://tools.ietf.org/html/draft-thomas-crypto-conditions-04
|
||||
[crypto-conditions]: https://tools.ietf.org/html/draft-thomas-crypto-conditions-04
|
||||
[deposit_authorized command]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md
|
||||
[deposit_authorized method]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md
|
||||
[deposit_authorizedメソッド]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/deposit_authorized.md
|
||||
[download_shard command]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md
|
||||
[download_shard method]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md
|
||||
[download_shardメソッド]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/download_shard.md
|
||||
[drops of XRP]: /docs/references/protocol/data-types/basic-data-types.md#specifying-currency-amounts
|
||||
[feature command]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md
|
||||
[feature method]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md
|
||||
[featureメソッド]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature.md
|
||||
[fee command]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md
|
||||
[fee levels]: /docs/concepts/transactions/transaction-cost.md#fee-levels
|
||||
[fee method]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md
|
||||
[feeメソッド]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/fee.md
|
||||
[fetch_info command]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md
|
||||
[fetch_info method]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md
|
||||
[fetch_infoメソッド]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info.md
|
||||
[fix1201 amendment]: /resources/known-amendments.md#fix1201
|
||||
[fix1368 amendment]: /resources/known-amendments.md#fix1368
|
||||
[fix1373 amendment]: /resources/known-amendments.md#fix1373
|
||||
@@ -442,180 +342,110 @@
|
||||
[fixTakerDryOfferRemoval amendment]: /resources/known-amendments.md#fixtakerdryofferremoval
|
||||
[fixTrustLinesToSelf amendment]: /resources/known-amendments.md#fixtrustlinestoself
|
||||
[get_aggregate_price command]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md
|
||||
[get_aggregate_priceコマンド]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md
|
||||
[get_aggregate_price method]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md
|
||||
[get_aggregate_priceメソッド]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/get_aggregate_price.md
|
||||
[gateway_balances command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md
|
||||
[gateway_balances method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md
|
||||
[gateway_balancesメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/gateway_balances.md
|
||||
[get_counts command]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md
|
||||
[get_counts method]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md
|
||||
[get_countsメソッド]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts.md
|
||||
[hexadecimal]: https://en.wikipedia.org/wiki/Hexadecimal
|
||||
[identifying hash]: /docs/concepts/transactions/index.md#identifying-transactions
|
||||
[json command]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/json.md
|
||||
[json method]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/json.md
|
||||
[jsonメソッド]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/json.md
|
||||
[ledger command]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md
|
||||
[ledger format]: /docs/references/protocol/ledger-data/ledger-entry-types/index.md
|
||||
[ledger index]: /docs/references/protocol/data-types/basic-data-types.md#ledger-index
|
||||
[ledger method]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md
|
||||
[ledger_accept command]: /docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md
|
||||
[ledger_accept method]: /docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md
|
||||
[ledger_acceptメソッド]: /docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept.md
|
||||
[ledger_cleaner command]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md
|
||||
[ledger_cleaner method]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md
|
||||
[ledger_cleanerメソッド]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner.md
|
||||
[ledger_closed command]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md
|
||||
[ledger_closed method]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md
|
||||
[ledger_closedメソッド]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_closed.md
|
||||
[ledger_current command]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md
|
||||
[ledger_current method]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md
|
||||
[ledger_currentメソッド]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_current.md
|
||||
[ledger_data command]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md
|
||||
[ledger_data method]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md
|
||||
[ledger_dataメソッド]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_data.md
|
||||
[ledger_entry command]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md
|
||||
[ledger_entry method]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md
|
||||
[ledger_entryメソッド]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger_entry.md
|
||||
[ledger_request command]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md
|
||||
[ledger_request method]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md
|
||||
[ledger_requestメソッド]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request.md
|
||||
[ledgerメソッド]: /docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger.md
|
||||
[log_level command]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md
|
||||
[log_level method]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md
|
||||
[log_levelメソッド]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level.md
|
||||
[logrotate command]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md
|
||||
[logrotate method]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md
|
||||
[logrotateメソッド]: /docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate.md
|
||||
[manifest command]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md
|
||||
[manifest method]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md
|
||||
[manifestメソッド]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest.md
|
||||
[nft_buy_offers command]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md
|
||||
[nft_buy_offers method]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md
|
||||
[nft_buy_offersメソッド]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_buy_offers.md
|
||||
[nft_info command]: /docs/references/http-websocket-apis/public-api-methods/clio-methods/nft_info.md
|
||||
[nft_info method]: /docs/references/http-websocket-apis/public-api-methods/clio-methods/nft_info.md
|
||||
[nft_infoメソッド]: /docs/references/http-websocket-apis/public-api-methods/clio-methods/nft_info.md
|
||||
[nft_sell_offers command]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md
|
||||
[nft_sell_offers method]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md
|
||||
[nft_sell_offersメソッド]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/nft_sell_offers.md
|
||||
[node key pair]: /docs/concepts/networks-and-servers/peer-protocol.md#node-key-pair
|
||||
[node public key]: /docs/concepts/networks-and-servers/peer-protocol.md#node-key-pair
|
||||
[noripple_check command]: /docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md
|
||||
[noripple_check method]: /docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md
|
||||
[noripple_checkメソッド]: /docs/references/http-websocket-apis/public-api-methods/account-methods/noripple_check.md
|
||||
[path_find command]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md
|
||||
[path_find method]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md
|
||||
[path_findメソッド]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/path_find.md
|
||||
[peer reservation]: /docs/concepts/networks-and-servers/peer-protocol.md#fixed-peers-and-peer-reservations
|
||||
[peer reservations]: /docs/concepts/networks-and-servers/peer-protocol.md#fixed-peers-and-peer-reservations
|
||||
[peer_reservations_add command]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md
|
||||
[peer_reservations_add method]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md
|
||||
[peer_reservations_addメソッド]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add.md
|
||||
[peer_reservations_del command]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md
|
||||
[peer_reservations_del method]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md
|
||||
[peer_reservations_delメソッド]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del.md
|
||||
[peer_reservations_list command]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md
|
||||
[peer_reservations_list method]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md
|
||||
[peer_reservations_listメソッド]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list.md
|
||||
[peers command]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md
|
||||
[peers method]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md
|
||||
[peersメソッド]: /docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers.md
|
||||
[ping command]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md
|
||||
[ping method]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md
|
||||
[pingメソッド]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/ping.md
|
||||
[print command]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md
|
||||
[print method]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md
|
||||
[printメソッド]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print.md
|
||||
[public servers]: /docs/tutorials/public-servers.md
|
||||
[random command]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md
|
||||
[random method]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md
|
||||
[randomメソッド]: /docs/references/http-websocket-apis/public-api-methods/utility-methods/random.md
|
||||
[result code]: /docs/references/protocol/transactions/transaction-results/index.md
|
||||
[ripple-lib]: https://github.com/XRPLF/xrpl.js
|
||||
[ripple_path_find command]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md
|
||||
[ripple_path_find method]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md
|
||||
[ripple_path_findメソッド]: /docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find.md
|
||||
[seconds since the Ripple Epoch]: /docs/references/protocol/data-types/basic-data-types.md#specifying-time
|
||||
[リップルエポックからの秒数]: /docs/references/protocol/data-types/basic-data-types.md#specifying-time
|
||||
[server_definitions method]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_definitions.md
|
||||
[server_info command]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md
|
||||
[server_info method]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md
|
||||
[server_infoメソッド]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_info.md
|
||||
[server_state command]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md
|
||||
[server_state method]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md
|
||||
[server_stateメソッド]: /docs/references/http-websocket-apis/public-api-methods/server-info-methods/server_state.md
|
||||
[sign command]: /docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md
|
||||
[sign method]: /docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md
|
||||
[sign_for command]: /docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md
|
||||
[sign_for method]: /docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md
|
||||
[sign_forメソッド]: /docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for.md
|
||||
[signメソッド]: /docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign.md
|
||||
[stand-alone mode]: /docs/concepts/networks-and-servers/rippled-server-modes.md#stand-alone-mode
|
||||
[standard format]: /docs/references/http-websocket-apis/api-conventions/response-formatting.md
|
||||
[String Number]: /docs/references/protocol/data-types/currency-formats#string-numbers
|
||||
[stop command]: /docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md
|
||||
[stop method]: /docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md
|
||||
[stopメソッド]: /docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop.md
|
||||
[submit command]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md
|
||||
[submit method]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md
|
||||
[submit_multisigned command]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md
|
||||
[submit_multisigned method]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md
|
||||
[submit_multisignedメソッド]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit_multisigned.md
|
||||
[submitメソッド]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/submit.md
|
||||
[subscribe command]: /docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md
|
||||
[subscribe method]: /docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md
|
||||
[subscribeメソッド]: /docs/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md
|
||||
[transaction cost]: /docs/concepts/transactions/transaction-cost.md
|
||||
[transaction_entry command]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md
|
||||
[transaction_entry method]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md
|
||||
[transaction_entryメソッド]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/transaction_entry.md
|
||||
[tx command]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md
|
||||
[tx method]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md
|
||||
[tx_history command]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md
|
||||
[tx_history method]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md
|
||||
[tx_historyメソッド]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx_history.md
|
||||
[txメソッド]: /docs/references/http-websocket-apis/public-api-methods/transaction-methods/tx.md
|
||||
[universal error types]: /docs/references/http-websocket-apis/api-conventions/error-formatting.md#universal-errors
|
||||
[unsubscribe command]: /docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md
|
||||
[unsubscribe method]: /docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md
|
||||
[unsubscribeメソッド]: /docs/references/http-websocket-apis/public-api-methods/subscription-methods/unsubscribe.md
|
||||
[validation_create command]: /docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md
|
||||
[validation_create method]: /docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md
|
||||
[validation_createメソッド]: /docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create.md
|
||||
[validator_info command]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md
|
||||
[validator_info method]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md
|
||||
[validator_infoメソッド]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info.md
|
||||
[validator_list_sites command]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md
|
||||
[validator_list_sites method]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md
|
||||
[validator_list_sitesメソッド]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites.md
|
||||
[validators command]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md
|
||||
[validators method]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md
|
||||
[validatorsメソッド]: /docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators.md
|
||||
[wallet_propose command]: /docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md
|
||||
[wallet_propose method]: /docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md
|
||||
[wallet_proposeメソッド]: /docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose.md
|
||||
[アドレス]: /docs/references/protocol/data-types/basic-data-types.md#アドレス
|
||||
[シーケンス番号]: /docs/references/protocol/data-types/basic-data-types.md#アカウントシーケンス
|
||||
[スタンドアロンモード]: /docs/concepts/networks-and-servers/rippled-server-modes.md#スタンドアロンモード
|
||||
[トランザクションコスト]: /docs/concepts/transactions/transaction-cost.md
|
||||
[ノードキーペア]: /docs/concepts/networks-and-servers/peer-protocol.md#ノードキーペア
|
||||
[ノード公開鍵]: /docs/concepts/networks-and-servers/peer-protocol.md#ノードキーペア
|
||||
[ハッシュ]: /docs/references/protocol/data-types/basic-data-types.md#ハッシュ
|
||||
[ピアリザベーション]: /docs/concepts/networks-and-servers/peer-protocol.md#固定ピアとピアリザベーション
|
||||
[マーカー]: /docs/references/http-websocket-apis/api-conventions/markers-and-pagination.md
|
||||
[レジャーの指定]: /docs/references/protocol/data-types/basic-data-types.md#レジャーの指定
|
||||
[レジャーインデックス]: /docs/references/protocol/data-types/basic-data-types.md#レジャーインデックス
|
||||
[レジャーフォーマット]: /docs/references/protocol/ledger-data/index.md
|
||||
[レポートモード]: /docs/concepts/networks-and-servers/rippled-server-modes.md#レポートモード
|
||||
[公開サーバ]: /docs/tutorials/public-servers.md
|
||||
[共通フィールド]: /docs/references/protocol/transactions/common-fields.md
|
||||
[内部の型]: /docs/references/protocol/binary-format.md
|
||||
[手数料レベル]: /docs/concepts/transactions/transaction-cost.md#手数料レベル
|
||||
[時間の指定]: /docs/references/protocol/data-types/basic-data-types.md#時間の指定
|
||||
[標準フォーマット]: /docs/references/http-websocket-apis/api-conventions/response-formatting.md
|
||||
[汎用エラータイプ]: /docs/references/http-websocket-apis/api-conventions/error-formatting.md#汎用エラー
|
||||
[識別用ハッシュ]: /docs/concepts/transactions/index.md#トランザクションの識別
|
||||
[通貨コード]: /docs/references/protocol/data-types/currency-formats.md#通貨コード
|
||||
[通貨額]: /docs/references/protocol/data-types/basic-data-types.md#通貨額の指定
|
||||
[通貨額の指定]: /docs/references/protocol/data-types/basic-data-types.md#通貨額の指定
|
||||
|
||||
@@ -31,8 +31,8 @@ If the primary purpose of an account is to facilitate exchange of value between
|
||||
|------|-------------|
|
||||
| `defaultRipple` | Allow rippling on trust lines by default. Rippling is necessary in order for accounts to trade tokens you exchange with third-party accounts. See [Rippling](../tokens/fungible-tokens/rippling.md). |
|
||||
| `disallowIncomingNFTokenOffer` | Prevent other accounts from sending NFT buy or sell offers to this account. This avoids unsolicited offers unrelated to the primary purpose of the exchanger account. See [Trading NFTs](../tokens/nfts/trading.md). |
|
||||
| `disallowIncomingPayChan` | Prevent other accounts from creating payment channels to this account. While you might want to create payment channels to other accounts yourself, you typically wouldn't want other accounts to create a payment channel to an exchange account. See [Payment Channels](../payment-types/payment-channels). |
|
||||
| `requireDestinationTag` | Require that all incoming payments have a destination tag. Destination tags provide a more lightweight mechanism for sending payments to a specific customer at a general receiver account. See [Source and Destination Tags](../transactions/source-and-destination-tags). |
|
||||
| `disallowIncomingPayChan` | Prevent other accounts from creating payment channels to this account. While you might want to create payment channels to other accounts yourself, you typically wouldn't want other accounts to create a payment channel to an exchange account. See [Payment Channels](../payment-types/payment-channels.md). |
|
||||
| `requireDestinationTag` | Require that all incoming payments have a destination tag. Destination tags provide a more lightweight mechanism for sending payments to a specific customer at a general receiver account. See [Source and Destination Tags](../transactions/source-and-destination-tags.md). |
|
||||
|
||||
[](../../img/cpt-account-configurator2.png)
|
||||
|
||||
@@ -61,7 +61,7 @@ Multi-signing in the XRP Ledger is a method of authorizing transactions by using
|
||||
| `disallowIncomingCheck` | Prevent other accounts from sending checks to this account. See [Checks](../payment-types/checks.md).
|
||||
| `disallowIncomingNFTokenOffer` | Prevent other accounts from sending NFT buy or sell offers to this account. This avoids unsolicited offers unrelated to the primary purpose of the exchanger account. See [Trading NFTs](../tokens/nfts/trading.md). |
|
||||
| `disallowIncomingPayChan` | Prevent other accounts from creating payment channels to this account. While you might want to create payment channels to other accounts yourself, you typically wouldn't want other accounts to create a payment channel to an exchange account. See [Payment Channels](../payment-types/payment-channels.md). |
|
||||
| `disallowIncomingXRP` | Prevent other accounts from sending XRP to this account. (This is advisory, and not enforced by the protocol). See [Direct XRP Payments](../payment-types/direct-xrp-payments/). |
|
||||
| `disallowIncomingXRP` | Prevent other accounts from sending XRP to this account. (This is advisory, and not enforced by the protocol). See [Direct XRP Payments](../payment-types/direct-xrp-payments.md). |
|
||||
|
||||
[](../../img/cpt-account-configurator3.png)
|
||||
|
||||
@@ -71,7 +71,7 @@ All of the configuration flags can be helpful for specific use cases. The follow
|
||||
|
||||
| Flag | Description |
|
||||
|------|-------------|
|
||||
| `allowTrustLineClawback` | Allow account to claw back tokens it has issued. See [Clawing Back Tokens](../tokens/fungible-tokens/clawing-back-tokens). |
|
||||
| `allowTrustLineClawback` | Allow account to claw back tokens it has issued. See [Clawing Back Tokens](../tokens/fungible-tokens/clawing-back-tokens.md). |
|
||||
| `disableMasterKey` | Disallow use of the master key pair. Can only be enabled if the account has configured another way to sign transactions, such as a regular key or a signer list. See [Master Key Pair](./cryptographic-keys.md#master-key-pair). |
|
||||
| `disallowIncomingTrustLine` | Block incoming trust lines. See [Trust Lines](../tokens/fungible-tokens/index.md#trust-lines). |
|
||||
| `globalFreeze` | Freeze all tokens issued by this account. See [Global Freeze](../tokens/fungible-tokens/freezes.md#global-freeze).
|
||||
|
||||
@@ -19,14 +19,22 @@ After an account has been deleted, it can be re-created in the ledger through th
|
||||
To be deleted, an account must meet the following requirements:
|
||||
|
||||
- The account's `Sequence` number plus 256 must be less than the current [Ledger Index][].
|
||||
- The account must not be linked to any of the following types of [ledger entries](../../references/protocol/ledger-data/ledger-entry-types/index.md) (as a sender or receiver):
|
||||
- `Escrow`
|
||||
- `PayChannel`
|
||||
- `RippleState`
|
||||
- `Check`
|
||||
- The account must not have any "deletion blockers" in its owner directory. This includes cases where the account is a sender _or_ receiver of funds. See below for a full list of deletion blockers.
|
||||
- The account must own fewer than 1000 objects in the ledger.
|
||||
- The transaction must pay a special [transaction cost][] equal to at least the [owner reserve](reserves.md) for one item (currently {% $env.PUBLIC_OWNER_RESERVE %}).
|
||||
|
||||
### Deletion Blockers
|
||||
|
||||
The following [ledger entry types](../../references/protocol/ledger-data/ledger-entry-types/index.md) are deletion blockers:
|
||||
|
||||
- `Escrow`
|
||||
- `PayChannel`
|
||||
- `RippleState` (trust line)
|
||||
- `Check`
|
||||
- `PermissionedDomain` _(Requires the [PermissionedDomains amendment][] {% not-enabled /%})_
|
||||
|
||||
Any other types of ledger entries that an account owns are automatically deleted along with the account.
|
||||
|
||||
## Cost of Deleting
|
||||
|
||||
{% admonition type="danger" name="Warning" %}The [AccountDelete transaction][]'s transaction cost always applies when the transaction is included in a validated ledger, even if the transaction failed because the account does not meet the requirements to be deleted. To greatly reduce the chances of paying the high transaction cost if the account cannot be deleted, use the `fail_hard` option when submitting an AccountDelete transaction.{% /admonition %}
|
||||
|
||||
@@ -7,102 +7,67 @@ labels:
|
||||
status: not_enabled
|
||||
---
|
||||
# Permission Delegation
|
||||
XRPL accounts can delegate both transaction permissions and granular permissions to other accounts, enhancing flexibility and enabling use cases such as implementing role-based access control. This delegation is managed using the [`DelegateSet`](../../references/protocol/transactions/types/delegateset.md) transaction.
|
||||
|
||||
_(Requires the [PermissionDelegation amendment][] {% not-enabled /%})_
|
||||
Permission delegation is the function of granting various permissions to another account to send permissions on behalf of your account. You can use permission delegation to enable flexible security paradigms such as role-based access control, instead of or alongside techniques such as [multi-signing](./multi-signing.md).
|
||||
|
||||
## Assigning Permissions
|
||||
_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_
|
||||
|
||||
You can assign permissions to another account by submitting a `DelegateSet` transaction.
|
||||
|
||||
```json
|
||||
tx_json = {
|
||||
"TransactionType": "DelegateSet",
|
||||
"Account": "rDelegatingAccount",
|
||||
"Authorize": "rDelegatedAccount",
|
||||
"Permissions": [
|
||||
{
|
||||
"Permission": {
|
||||
"PermissionValue": "Payment"
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
## Background
|
||||
|
||||
| Field | Description |
|
||||
|-------|-------------|
|
||||
| `Account` | The address of the account that is delegating the permission(s). |
|
||||
| `Authorize` | The address of the account that is being granted the permission(s). |
|
||||
| `Permissions` | An array of permission objects, specifying the permissions to delegate. Each permission is defined within a `Permission` object, using the `PermissionValue` field. See [XLS-74d, Account Permissions] for a complete list of valid `PermissionValues`. |
|
||||
Managing your [cryptographic keys](./cryptographic-keys.md) is one of the more challenging parts of using a blockchain. As part of a defense-in-depth strategy, a secure configuration should limit the damage that can occur if a secret key is compromised. One way to do this is to rotate keys regularly and to keep master keys off of computers that are always connected to the internet and serving user traffic. However, many use cases involve frequently and automatically signing transactions, which typically requires having secret keys on an internet-connected server.
|
||||
|
||||
## Revoking Permissions
|
||||
Permission Delegation can reduce this problem by granting very limited permissions to separate accounts that have their keys available online for day-to-day tasks. Meanwhile, the keys with full control over the account can be kept offline, so that you only use them for special tasks, like issuing tokens. This is especially helpful when using compliance features like [Authorized Trust Lines](../tokens/fungible-tokens/authorized-trust-lines.md) that require a stablecoin issuer to individually approve each user after meeting regulatory requirements like Know Your Customer rules. With a proper configuration, you can minimize the consequences of a delegate's keys being compromized.
|
||||
|
||||
Permissions can be revoked using the `DelegateSet` transaction. There are two ways to revoke permissions:
|
||||
|
||||
### Revoke All Permissions
|
||||
## How It Works
|
||||
|
||||
To revoke all permissions previously granted to a delegated account, send a `DelegateSet` transaction with an empty `Permissions` array:
|
||||
The account on whose behalf transactions are being sent is called the _delegator_. The account sending the transactions is called the _delegate_.
|
||||
|
||||
```json
|
||||
tx_json = {
|
||||
"TransactionType": "DelegateSet",
|
||||
"Account": "rDelegatingAccount",
|
||||
"Authorize": "rDelegatedAccount",
|
||||
"Permissions": []
|
||||
}
|
||||
```
|
||||
The delegator first sends a [DelegateSet transaction][] to designate an account as its delegate and to specify which permissions the delegate has. The delegator can update or revoke the permissions at any time by sending another DelegateSet transaction. A delegator can have more than one delegate, and can grant different sets of permissions to each delegate.
|
||||
|
||||
### Revoke Specific Permissions
|
||||
A delegate can send transactions that execute as if they were sent by the delegator. These transactions specify both the delegator's information as well as the address of the delegate who is sending the transaction. The delegate can sign these transactions with any of the following:
|
||||
|
||||
To revoke specific permissions, send a `DelegateSet` transaction that includes _only_ the permissions that should remain active. Any permissions previously granted to the `Authorize` account that aren't included in the `Permissions` array are revoked.
|
||||
- The delegate's master key pair
|
||||
- A regular key pair that the delegate has authorized
|
||||
- A multi-signing list that the delegate has authorized
|
||||
|
||||
## Sending Transactions with Delegated Permissions
|
||||
The delegate can only send transactions that match the permissions it has. Permissions come in two types:
|
||||
|
||||
When an account has been granted permissions, it can send transactions on behalf of the delegating account using the `Delegate` field.
|
||||
- **Transaction Type Permissions** - Permission to send transactions of a specific [transaction type](/docs/references/protocol/transactions/types/index.md). Some types cannot be delegated.
|
||||
- **Granular Permissions** - Permission to send transactions with a specific subset of functionality.
|
||||
|
||||
For example, if `rDelegatingAccount` has delegated the `TrustSet` permission to `rDelegatedAccount`, then `rDelegatedAccount` can submit a `TrustSet` transaction on behalf of `rDelegatingAccount` as follows:
|
||||
For a complete list of transaction types that can or cannot be delegated as well as a list of granular permissions, see [Permission Values](/docs/references/protocol/data-types/permission-values.md).
|
||||
|
||||
```json
|
||||
transaction_json = {
|
||||
"TransactionType": "TrustSet",
|
||||
"Account": "rDelegatingAccount",
|
||||
"Delegate": "rDelegatedAccount",
|
||||
"LimitAmount": {
|
||||
"currency": "USD",
|
||||
"issuer": "rIssuerAccount",
|
||||
"value": "1000"
|
||||
}
|
||||
}
|
||||
```
|
||||
### Limitations
|
||||
|
||||
| Field | Description |
|
||||
|-------|-------------|
|
||||
| `Account` | The address of the account that granted permission for the transaction (the _delegating_ account). |
|
||||
| `Delegate` | The address of the account submitting and signing the transaction. This must be the account that was granted permission (the _delegated_ account). |
|
||||
The main limiting factor on how many delegates you can have is that you must hold enough XRP to meet the [reserve requirement](./reserves.md). Each delegate's permissions are tracked with a [Delegate ledger entry][], which counts as one item towards the delegator's owner reserve.
|
||||
|
||||
The account that sends this transaction is _rDelegatedAccount_, although the Account field is the _rDelegatingAccount_. The secret for this transaction is the _rDelegatedAccount_ secret, which means _rDelegatedAccount_ signs the transaction.
|
||||
Each delegate can be granted up to 10 permissions.
|
||||
|
||||
## Error Cases
|
||||
Some permissions cannot be delegated, especially permissions that would allow the delegate to change cryptographic keys or grant additional permissions.
|
||||
|
||||
- If the `PermissionDelegation` feature is not enabled, return `temDISABLED`.
|
||||
The available set of granular permissions is hard-coded, and the permissions cannot be customized. For example, you cannot grant permission to send only certain currencies and not others.
|
||||
|
||||
- If the _rDelegatedAccount_ is not authorized by the _rDelegatingAccount_ for the transaction type or satisfying the granular permissions given by _rDelegatingAccount_, the transaction returns `tecNO_DELEGATE_PERMISSION`.
|
||||
## Comparison with Multi-Signing
|
||||
|
||||
- If the _rDelegatedAccount_ does not have enough balance to pay the transaction fee, the transaction returns `terINSUF_FEE_B` . (_rDelegatedAccount_ pays the fee, which is the sender in `Delegate` field, not the `Account` field).
|
||||
Permission delegation is similar to multi-signing in that it allows other key pairs to sign transactions that "come from" your account. However, there are key differences in functionality between the two, as summarized in the following table:
|
||||
|
||||
- If the transaction creates a ledger object, but _rDelegatingAccount_ does not have enough balance to cover the reserve, the transaction returns `tecINSUFFICIENT_RESERVE`.
|
||||
| | Permission Delegation | Multi-Signing |
|
||||
|------------------|-----------------------|---------------|
|
||||
| Transaction cost | Paid by the delegate | Paid by the account that owns the list |
|
||||
| Permission control | Can only send transactions matching specific permissions granted | Can send any transactions except [specific cases that require the master key pair](./cryptographic-keys.md#special-permissions) |
|
||||
| M-of-N permission | Not supported | Configurable quorum and weights with up to 32 signers |
|
||||
| Unfunded accounts | Delegates must have funded accounts on ledger | Signers can be funded accounts or key pairs with no account on ledger. |
|
||||
| Key management | Delegate manages their own keys, including multi-signing | Signers with funded accounts can manage their own keys but cannot perform nested multi-signing. |
|
||||
|
||||
- If the key used to sign this account does not match with _rDelegatedAccount_, the transaction returns `rpcBAD_SECRET`.
|
||||
|
||||
- If the `TradingFee` is invalid (non-XRP currency or negative value), return `temBAD_FEE`.
|
||||
## See Also
|
||||
|
||||
Any other errors are the same as when the _rDelegatingAccount_ sends transaction for itself.
|
||||
|
||||
{% admonition type="warning" name="Important" %}
|
||||
* Delegating permissions grants significant control. Ensure you trust the delegated account.
|
||||
* The account specified in the `Delegate` field is responsible for paying the transaction fee.
|
||||
* A delegated account can only perform actions that have been explicitly permitted.
|
||||
{% /admonition %}
|
||||
- **References:**
|
||||
- [DelegateSet transaction][] - Grant, update, or revoke permissions to a specific delegate.
|
||||
- [Delegate ledger entry][] - Data structure on the ledger that records which permissions have been granted.
|
||||
- **Code Samples:**
|
||||
- {% repo-link path="_code-samples/delegate-permissions/" %}**Delegate Permissions**{% /repo-link %}
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
|
||||
@@ -50,4 +50,4 @@ Next: [Transactions and Requests](transactions-and-requests.md)
|
||||
|
||||
## See Also
|
||||
|
||||
For more information on which wallets are supported on the XRP Ledger, see [Wallets](../../about/xrp#wallets).
|
||||
For more information on which wallets are supported on the XRP Ledger, see [Wallets](../../about/xrp.page.tsx#wallets).
|
||||
|
||||
@@ -8,7 +8,8 @@ seo:
|
||||
|
||||
These client libraries simplify some of the common work of accessing and processing XRP Ledger data, and present it in a form that matches with the native conventions of their respective programming languages.
|
||||
|
||||
For other programming languages, you can access the XRP Ledger through the [HTTP APIs](http-websocket-apis/index.md).
|
||||
- To stay up-to-date on JavaScript/TypeScript and Python library updates, join the [xrpl-announce mailing list](https://groups.google.com/g/xrpl-announce).
|
||||
- For other programming languages, you can access the XRP Ledger through the [HTTP APIs](http-websocket-apis/index.md).
|
||||
|
||||
| Language | Library Name | Get Started | API Reference | Source Code |
|
||||
|---------------------------------|---------------------------|-------------|--------------|-------------|
|
||||
|
||||
@@ -12,7 +12,8 @@ Currently, there are two API versions: `1` and `2` {% badge href="https://github
|
||||
|
||||
Separate API requests can use different API versions even on the same persistent connection. For example, if you connect through WebSocket to a server that supports API versions 1 and 2, you can make an `account_tx` request using API version 2 and then make another `account_tx` request using API version 1 from the same connection.
|
||||
|
||||
For a full list of the differences between API versions, see [API-CHANGELOG on GitHub](https://github.com/xrplf/rippled/blob/develop/API-CHANGELOG.md).
|
||||
- For a full list of the differences between API versions, see [API-CHANGELOG on GitHub](https://github.com/xrplf/rippled/blob/develop/API-CHANGELOG.md).
|
||||
- To stay up-to-date with API changes, join the [ripple server mailing list](https://groups.google.com/g/ripple-server).
|
||||
|
||||
|
||||
## Default API Versions
|
||||
|
||||
@@ -163,6 +163,5 @@ An example of the response format:
|
||||
- `internal` - The `trim_threshold` setting removed all prices.
|
||||
- `objectNotFound` - There are no prices in the dataset.
|
||||
- `oracleMalformed` - The `oracles` array is malformed. At least one object field is specified incorrectly or missing, or the number of objects is outside the bounds of 1 to 200.
|
||||
-
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
|
||||
84
docs/references/protocol/data-types/permission-values.md
Normal file
84
docs/references/protocol/data-types/permission-values.md
Normal file
@@ -0,0 +1,84 @@
|
||||
---
|
||||
seo:
|
||||
description: Format for permissions that can be granted to other accounts.
|
||||
label:
|
||||
- Permissions
|
||||
---
|
||||
# Permission Values
|
||||
|
||||
[Permission delegation](/docs/concepts/accounts/permission-delegation.md) defines permissions that can be granted to other accounts. These permissions fall into the following categories:
|
||||
|
||||
- **Transaction Type Permissions** - Permission to send transactions with the specified [transaction type](../transactions/types/index.md).
|
||||
- **Granular Permissions** - Permission to send transactions with a specific subset of functionality.
|
||||
|
||||
_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_
|
||||
|
||||
## Numeric and String Values
|
||||
|
||||
In the [canonical binary format](../binary-format.md) for transactions and ledger data, permission values are stored in a numeric form (specifically, as a 32-bit unsigned integer). However, in JSON they can be specified and returned in string format for convenience, similar to how transaction type names (`TransactionType` fields) work.
|
||||
|
||||
When specifying a permission value in JSON, you can use either the numeric value or the string value. When serving data, the server supplies the string value if it is known, and falls back to the numeric value otherwise.
|
||||
|
||||
{% admonition type="warning" name="Caution" %}
|
||||
Not all client libraries support numeric PermissionValue types. In most cases, you should use the string names of the permissions you want to grant.
|
||||
{% /admonition %}
|
||||
|
||||
- For **transaction type permissions**, the string is the name of the transaction type exactly (case-sensitive). For example, a permission value of `"PaymentChannelClaim"` grants permission to send [PaymentChannelClaim transactions][].
|
||||
- For **granular permissions**, the string is the name of the granular permission (case-sensitive). For example, a permission value of `"TrustlineAuthorize"` grants permission to send TrustSet transactions that authorize trust lines (but not ones that modify other settings such as the trust line limit or freeze status).
|
||||
|
||||
The numeric value `0` is reserved for "full permissions", meaning permission to send transactions of all types, but it is not possible to delegate full permissions.
|
||||
|
||||
## Transaction Type Permissions
|
||||
|
||||
Transaction Type Permissions have numeric values from 1 to 65536 (that is, 2<sup>16</sup>), inclusive. They correspond with known transaction types, except you add 1 when specifying a transaction type as a permission value. For example, the string `"Payment"` corresponds to a `TransactionType` value of `0`, but a `PermissionValue` value of `1`. To grant permissions to make Payment transactions, you can specify either `"PermissionValue": "Payment"` or `"PermissionValue": 1`.
|
||||
|
||||
For a mapping of transaction types known by a server and their corresponding numeric transaction type values, check the `TRANSACTION_TYPES` field in the [server_definitions method][].
|
||||
|
||||
### List of Non-Delegatable Permissions
|
||||
|
||||
Some transaction types can't be delegated. If you attempt to grant these permissions to a delegate, the transaction fails with a [result code](../transactions/transaction-results/) such as `tecNO_PERMISSION`. This includes all transaction types that can be used to grant other permissions to different key pairs or accounts. Additionally, all [pseudo-transaction types](/docs/references/protocol/transactions/pseudo-transaction-types/pseudo-transaction-types) can't be delegated since they can't be sent by normal accounts anyway.
|
||||
|
||||
The following permissions cannot be delegated:
|
||||
|
||||
| Transaction Type | Permission Value |
|
||||
|:--------------------|:-----------------|
|
||||
| [AccountSet][] | `4` |
|
||||
| [SetRegularKey][] | `6` |
|
||||
| [SignerListSet][] | `13` |
|
||||
| [AccountDelete][] | `22` |
|
||||
| [LedgerStateFix][] | `54` |
|
||||
| [DelegateSet][] | `65` |
|
||||
| [EnableAmendment][] | `101` |
|
||||
| [SetFee][] | `102` |
|
||||
| [UNLModify][] | `103` |
|
||||
|
||||
{% admonition type="warning" name="Known Issue" %}
|
||||
With only the PermissionDelegation amendment, it's possible to assign permissions for transaction types that are reserved, unassigned, or part of amendments that are not currently enabled; it's also possible to assign PermissionValue `0` for full permissions. However, these values do not actually grant any permissions. This is a bug, and a future amendment will prevent assigning values outside of currently-enabled, delegatable transaction types or known granular permissions.
|
||||
{% /admonition %}
|
||||
|
||||
## Granular Permissions
|
||||
[[Source]](https://github.com/XRPLF/rippled/blob/master/include/xrpl/protocol/detail/permissions.macro "Source")
|
||||
|
||||
Granular Permissions have numeric types of 65537 and up, corresponding to specific names of permissions. Values that are not defined are not allowed. Each granular permission is a subset of a single transaction type's functionality.
|
||||
|
||||
| Numeric Value | Name | Transaction Type | Description |
|
||||
|:--------------|:-------------------------|:-----------------------|:------------|
|
||||
| `65537` | `TrustlineAuthorize` | [TrustSet][] | Can [authorize individual trust lines](/docs/concepts/tokens/fungible-tokens/authorized-trust-lines). |
|
||||
| `65538` | `TrustlineFreeze` | [TrustSet][] | Can [freeze individual trust lines](/docs/concepts/tokens/fungible-tokens/freezes). |
|
||||
| `65539` | `TrustlineUnfreeze` | [TrustSet][] | Can [unfreeze individual trust lines](/docs/concepts/tokens/fungible-tokens/freezes). |
|
||||
| `65540` | `AccountDomainSet` | [AccountSet][] | Can set the `Domain` field of the account. |
|
||||
| `65541` | `AccountEmailHashSet` | [AccountSet][] | Can set the `EmailHash` field of the account. |
|
||||
| `65542` | `AccountMessageKeySet` | [AccountSet][] | Can set the `MessageKey` field of the account. |
|
||||
| `65543` | `AccountTransferRateSet` | [AccountSet][] | Can set the [transfer fee of fungible tokens issued by the account](/docs/concepts/tokens/transfer-fees). |
|
||||
| `65544` | `AccountTickSizeSet` | [AccountSet][] | Can set the [tick size of fungible tokens issued by the account](/docs/concepts/tokens/decentralized-exchange/ticksize). |
|
||||
| `65545` | `PaymentMint` | [Payment][] | Can send payments that mint new fungible tokens or MPTs. |
|
||||
| `65546` | `PaymentBurn` | [Payment][] | Can send payments that burn fungible tokens or MPTs. |
|
||||
| `65547` | `MPTokenIssuanceLock` | [MPTokenIssuanceSet][] | Can lock the balances of a particular MPT issued by the account. _(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_ |
|
||||
| `65548` | `MPTokenIssuanceUnlock` | [MPTokenIssuanceSet][] | Can unlock the balances of a particular MPT issued by the account. _(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_ |
|
||||
|
||||
### Limitations to Granular Permissions
|
||||
|
||||
The set of granular permissions is hard-coded. No custom configurations are allowed. For example, you cannot add permissions based on specific currencies. Adding a new granular permission requires an amendment.
|
||||
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
@@ -0,0 +1,68 @@
|
||||
---
|
||||
seo:
|
||||
description: A record of which permissions have been granted to another account.
|
||||
labels:
|
||||
- Accounts
|
||||
- Permissions
|
||||
---
|
||||
# Delegate
|
||||
[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/include/xrpl/protocol/detail/ledger_entries.macro#L475-L482 "Source")
|
||||
|
||||
A `Delegate` ledger entry stores a set of permissions that an account has delegated to another account. You create a `Delegate` entry by sending a [DelegateSet transaction][].
|
||||
|
||||
_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_
|
||||
|
||||
## Example {% $frontmatter.seo.title %} JSON
|
||||
|
||||
```json
|
||||
{
|
||||
"Account": "rG8uoRH9uA6AJ6NRj8P4cJG1HNfYcnMPrt",
|
||||
"Authorize": "r9GAKojMTyexqvy8DXFWYq63Mod5k5wnkT",
|
||||
"Flags": 0,
|
||||
"LedgerEntryType": "Delegate",
|
||||
"OwnerNode": "0",
|
||||
"Permissions": [
|
||||
{
|
||||
"Permission": {
|
||||
"PermissionValue": "AccountDomainSet"
|
||||
}
|
||||
}
|
||||
],
|
||||
"PreviousTxnID": "08DB1BD6ECFC9E8CBD8D954F4EFF6EFD155A392C5060D767B5621CE18951983A",
|
||||
"PreviousTxnLgrSeq": 4748731,
|
||||
"index": "749D3DCDF9F032DDDB8AC49641BACBFDD398C4B6C231C4AB325B7755962329A2"
|
||||
}
|
||||
```
|
||||
|
||||
## {% $frontmatter.seo.title %} Fields
|
||||
|
||||
In addition to the [common fields](../common-fields.md), {% code-page-name /%} entries have the following fields:
|
||||
|
||||
| Field | JSON Type | [Internal Type][] | Required? | Description |
|
||||
|:--------------------|:---------------------|:------------------|:----------|:-------------|
|
||||
| `Account` | String - [Address][] | AccountID | Yes | The account delegating permissions to another, also called the _delegating account_. |
|
||||
| `Authorize` | String - [Address][] | AccountID | Yes | The account receiving permissions, also called the _delegate_. |
|
||||
| `Permissions` | Array | Array | Yes | A list of permissions granted, with at least 1 and at most 10 items. Each item in the list is a [Permission Object](#permission-objects). |
|
||||
| `OwnerNode` | String - Hexadecimal | UInt64 | Yes | A hint indicating which page of the delegating account's owner directory links to this object, in case the directory consists of multiple pages.
|
||||
| `PreviousTxnID` | String - Hexadecimal | UInt256 | Yes | The identifying hash of the transaction that most recently modified this object. |
|
||||
| `PreviousTxnLgrSeq` | Number | UInt32 | Yes |The [index of the ledger][Ledger Index] that contains the transaction that most recently modified this object. |
|
||||
|
||||
### Permission Objects
|
||||
|
||||
Each item in the `Permissions` array is an inner object with the following nested field:
|
||||
|
||||
| Field | JSON Type | [Internal Type][] | Required? | Description |
|
||||
|:------------------|:---------------------|:------------------|:----------|:----------------|
|
||||
| `PermissionValue` | String or Number | UInt32 | Yes | A permission that has been granted to the delegate, which can be either a transaction type or a granular permission. See [Permission Values](../../data-types/permission-values.md) for a full list. |
|
||||
|
||||
## {% $frontmatter.seo.title %} Flags
|
||||
|
||||
There are no flags defined for {% code-page-name /%} entries.
|
||||
|
||||
## {% $frontmatter.seo.title %} Reserve
|
||||
|
||||
{% code-page-name /%} entries count as one item towards the owner reserve of the delegating account, as long as the entry is in the ledger, regardless of how many permissions are delegating. Removing all permissions deletes the entry and frees up the reserve.
|
||||
|
||||
{% code-page-name /%} entries are not deletion blockers. If the owner (delegating) account is deleted, all such ledger entries are deleted along with them. However, the `Authorize`
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
@@ -62,43 +62,14 @@ The [`Paths` field](types/payment.md#paths) of the [Payment transaction][] type
|
||||
|
||||
## Delegate
|
||||
|
||||
The `Delegate` ledger object stores a set of permissions that an XRPL account has delegated to another account. You create `Delegate` objects using the [`DelegateSet`](./types/delegateset.md) transaction.
|
||||
If the `Delegate` field is provided, this transaction is being sent by a different account on behalf of the account in the `Account` field. The account in the `Account` is the _delegating account_ and the account in the `Delegate` field is the _delegate_ account. The transaction functions as if it was sent by the delegating account, with the following exceptions:
|
||||
|
||||
### Structure
|
||||
- The signature must be valid for the delegate account. (It can by signed with a master key, regular key, or multi-signing list that is authorized by the delegate.)
|
||||
- The transaction cost (in the `Fee` field) is paid by the delegate account.
|
||||
|
||||
A `Delegate` object has the following fields:
|
||||
Sending a transaction this way is only possible if the delegating account has granted the appropriate transaction permissions to the delegate account. For more information, see [Permission Delegation](/docs/concepts/accounts/permission-delegation.md).
|
||||
|
||||
| Field Name | Required? | JSON Type | Internal Type | Description |
|
||||
|------------|-----------|-----------|---------------|-------------|
|
||||
| `LedgerIndex` | ✔️ | string | Hash256 | The unique ID of the ledger object. |
|
||||
| `LedgerEntryType` | ✔️ | string | UInt16 | The ledger object's type (`Delegate`) |
|
||||
| `Account` | ✔️ | string | AccountID | The account that delegates permissions to another account. |
|
||||
| `Authorize` | ✔️ | string | AccountID | The account to which permissions are delegated. |
|
||||
| `Permissions` | ✔️ | string | STArray | The transaction permissions that the `Authorize` account has been granted. |
|
||||
| `OwnerNode` | ✔️ | string | UInt64 | A hint indicating which page of the sender's owner directory links to this object, in case the directory consists of multiple pages. |
|
||||
| `PreviousTxnID` | ✔️ | string | Hash256 | The identifying hash of the transaction that most recently modified this object. |
|
||||
| `PreviousTxnLgrSeqNumber`| ✔️ | number | UInt32 |The index of the ledger that contains the transaction that most recently modified this object. |
|
||||
|
||||
### Retrieving Delegate Objects
|
||||
|
||||
You can retrieve `Delegate` ledger objects using the `ledger_entry` RPC method. The unique ID of a `Delegate` object is a hash of the `Account` and `Authorize` fields, combined with the unique space key for Delegate objects.
|
||||
|
||||
### Account Deletion
|
||||
|
||||
A `Delegate` object is not a deletion blocker. This means that deleting an account removes any `Delegate` objects associated with it.
|
||||
|
||||
### Example Delegate JSON
|
||||
|
||||
This sample `Delegate` object shows that the _rISAAC_ account has delegated `TrustLineAuthorize` permission to the _rKYLIE_ account.
|
||||
|
||||
```json
|
||||
{
|
||||
"LedgerEntryType": "Delegate",
|
||||
"Account": "rISAAC......",
|
||||
"Authorize": "rKYLIE......",
|
||||
"Permissions": [{"Permission": {"PermissionValue": "TrustlineAuthorize"}}],
|
||||
}
|
||||
```
|
||||
_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_
|
||||
|
||||
## Flags Field
|
||||
|
||||
|
||||
@@ -42,6 +42,7 @@ A transaction that fails with a `tec` code destroys the XRP paid as a [transacti
|
||||
| `tecINSUFFICIENT_PAYMENT` | 161 | The amount specified is not enough to pay all fees involved in the transaction. For example, when trading a non-fungible token, the buy amount may not be enough to pay both the broker fee and the sell amount. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ |
|
||||
| `tecINSUFFICIENT_RESERVE` | 141 | The transaction would increase the [reserve requirement](../../../../concepts/accounts/reserves.md) higher than the sending account's balance. [SignerListSet][], [PaymentChannelCreate][], [PaymentChannelFund][], and [EscrowCreate][] can return this error code. See [Signer Lists and Reserves](../../ledger-data/ledger-entry-types/signerlist.md#signer-lists-and-reserves) for more information. |
|
||||
| `tecINTERNAL` | 144 | Unspecified internal error, with transaction cost applied. This error code should not normally be returned. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). |
|
||||
| `tecINVALID_UPDATE_TIME` | 188 | The [OracleSet transaction][] failed because the `LastUpdateTime` is invalid. This can occur when the time is more than 300 seconds before or after the ledger close time, or when updating an existing oracle, the new `LastUpdateTime` is not greater than the previous value. _(Added by the [PriceOracle amendment][])_ |
|
||||
| `tecINVARIANT_FAILED` | 147 | An invariant check failed when trying to execute this transaction. Added by the [EnforceInvariants amendment][]. If you can reproduce this error, please [report an issue](https://github.com/XRPLF/rippled/issues). |
|
||||
| `tecKILLED` | 150 | The [OfferCreate transaction][] specified the `tfFillOrKill` flag and could not be filled, so it was killed. _(Added by the [fix1578 amendment][].)_ |
|
||||
| `tecMAX_SEQUENCE_REACHED` | 153 | A sequence number field is already at its maximum. This includes the `MintedNFTokens` field. _(Added by the [NonFungibleTokensV1_1 amendment][].)_ |
|
||||
|
||||
@@ -54,7 +54,7 @@ _(Added by the [AMMClawback amendment][].)_
|
||||
|
||||
## Error Cases
|
||||
|
||||
Besides errors that can occur for all transactions, `AMMClawback` transactions can result in the following [transaction result codes](https://xrpl.org/docs/references/protocol/transactions/transaction-results):
|
||||
Besides errors that can occur for all transactions, `AMMClawback` transactions can result in the following [transaction result codes](../transaction-results/index.md):
|
||||
|
||||
| Error Code | Description |
|
||||
|:-------------------|:------------|
|
||||
|
||||
@@ -7,139 +7,71 @@ labels:
|
||||
- Delegate
|
||||
status: not_enabled
|
||||
---
|
||||
# DelegateSet
|
||||
[[Source]](https://github.com/XRPLF/rippled/blob/1e01cd34f7a216092ed779f291b43324c167167a/src/xrpld/app/tx/detail/DelegateSet.cpp "Source")
|
||||
|
||||
# DelegateSet
|
||||
The `DelegateSet` transaction creates, modifies, or deletes a `Delegate` ledger object, thereby granting, changing, or revoking delegated permissions between accounts.
|
||||
[Delegate permissions](/docs/concepts/accounts/permission-delegation) to another account to send transactions on your behalf. This transaction type can grant, change, or revoke permissions; it creates, modifies, or deletes a [Delegate ledger entry][] accordingly.
|
||||
|
||||
_(Requires the [PermissionDelegation amendment][] {% not-enabled /%}.)_
|
||||
|
||||
## Example `DelegateSet` JSON
|
||||
|
||||
```json
|
||||
{
|
||||
"TransactionType": "DelegateSet",
|
||||
"Account": "rDelegatingAccount",
|
||||
"Authorize": "rDelegatedAccount",
|
||||
"Permissions": [
|
||||
{
|
||||
"Permission": {
|
||||
"PermissionValue": "Payment"
|
||||
}
|
||||
},
|
||||
{
|
||||
"Permission": {
|
||||
"PermissionValue": "TrustSet"
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
## `DelegateSet` Fields
|
||||
|
||||
In addition to the common fields, `DelegateSet` transactions have the following fields:
|
||||
|
||||
| Field | Required? | JSON Type | Internal Type | Description |
|
||||
|-------|-----------|-----------|---------------|-------------|
|
||||
| `TransactionType` | Yes | string | UInt16 | The transaction type (DelegateSet). |
|
||||
| `Account` | Yes | string | AccountID | The address of the account that is delegating the permission(s). |
|
||||
| `Authorize`| Yes | string | AccountID | The address of the account that is being granted the permission(s).
|
||||
| `Permissions` | Yes | string | STArray | An array of permission objects. Each object contains a `Permission` object with a `PermissionValue` field specifying the permission being granted. To modify permissions, include all desired permissions in the `Permissions` array. Omitted permissions are revoked. |
|
||||
|
||||
## Updating Permissions
|
||||
|
||||
Sending a new `DelegateSet` with the same `Account` and `Authorize` fields updates and replaces the permission list.
|
||||
|
||||
|
||||
## Revoking Permissions
|
||||
|
||||
Permissions are revoked using the `DelegateSet` transaction by specifying only the desired permissions and omitting any previous permissions that are no longer needed.
|
||||
|
||||
### Revoke All Permissions
|
||||
|
||||
To revoke all permissions, send a `DelegateSet` transaction with an empty `Permissions` array:
|
||||
## Example {% $frontmatter.seo.title %} JSON
|
||||
|
||||
```json
|
||||
{
|
||||
"TransactionType": "DelegateSet",
|
||||
"Account": "rDelegatingAccount",
|
||||
"Authorize": "rDelegatedAccount",
|
||||
"Permissions": []
|
||||
"TransactionType": "DelegateSet",
|
||||
"Account": "rw81qtsfF9rws4RbmYepf5394gp81TQv5Y",
|
||||
"Authorize": "r9GAKojMTyexqvy8DXFWYq63Mod5k5wnkT",
|
||||
"Fee": "1",
|
||||
"Flags": 0,
|
||||
"LastLedgerSequence": 4747822,
|
||||
"Permissions": [
|
||||
{
|
||||
"Permission": {
|
||||
"PermissionValue": "AccountDomainSet"
|
||||
}
|
||||
}
|
||||
],
|
||||
"Sequence": 4747802
|
||||
}
|
||||
```
|
||||
|
||||
### Revoke Specific Permissions
|
||||
{% tx-example txid="13E1C2CE2BCECB6223AEA39407169C5429FE9A126825CDD6952E3FF4C728F603" server="devnet" /%}
|
||||
|
||||
To revoke specific permissions, include only the permissions that should remain active in the `Permissions` array.
|
||||
{% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%}
|
||||
|
||||
## Security
|
||||
| Field | Required? | JSON Type | Internal Type | Description |
|
||||
|:--------------|-----------|----------------------|---------------|-------------|
|
||||
| `Authorize` | Yes | String - [Address][] | AccountID | The account being granted permissions, also called the _delegate_. |
|
||||
| `Permissions` | Yes | Array | Array | A list of up to 10 [Permission objects](#permission-objects) each specifying a different permission granted to the delegate. The delegate's permissions are updated to match this set of permissions exactly. To revoke all permissions, use an empty array. |
|
||||
|
||||
Giving permissions to other parties requires a high degree of trust, especially when the delegated account can potentially access funds (the `Payment` permission) or charge reserves (any transaction that can create objects). In addition, any account that has permissions for the entire `AccountSet`, `SetRegularKey`, or `SignerListSet` transactions can give themselves any permissions even if this was not originally part of the intention.
|
||||
If a [Delegate ledger entry][] does not exist to record the granted permissions, this transaction creates one. If it already exists, the transaction updates the set of permissions to match the list in the transaction: any permissions not listed are revoked. If all permissions are revoked, the transaction deletes the Delegate ledger entry.
|
||||
|
||||
With granular permissions, however, users can give permissions to other accounts for only parts of transactions without giving them full control. This is especially helpful for managing complex transaction types like `AccountSet`.
|
||||
{% admonition type="success" name="Tip" %}
|
||||
If you want to delegate more than 10 permissions, consider using [multi-signing](/docs/concepts/accounts/multi-signing.md) instead.
|
||||
{% /admonition %}
|
||||
|
||||
### Granular Permissions
|
||||
### Permission Objects
|
||||
|
||||
These permissions support control over some smaller portion of a transaction, rather than being able to do all of the functionality that the transaction allows.
|
||||
Each item in the `Permissions` array is an inner object with the following nested field:
|
||||
|
||||
These permissions fall into the gap between the size of the `UInt16` and the `UInt32` (the size of the `SignerListID` field).
|
||||
| Field | JSON Type | [Internal Type][] | Required? | Description |
|
||||
|:------------------|:---------------------|:------------------|:----------|:----------------|
|
||||
| `PermissionValue` | String or Number | UInt32 | Yes | A permission to grant to the delegate, which can be either a transaction type or a granular permission. See [Permission Values](../../data-types/permission-values.md) for a full list. |
|
||||
|
||||
| Value | Name | Description |
|
||||
|-------|-------|-------------|
|
||||
|`65537`|`TrustlineAuthorize`|Authorize a trustline.|
|
||||
|`65538`|`TrustlineFreeze`|Freeze a trustline.|
|
||||
|`65539`|`TrustlineUnfreeze`|Unfreeze a trustline.|
|
||||
|`65540`|`AccountDomainSet`|Modify the domain of an account.|
|
||||
|`65541`|`AccountEmailHashSet`|Modify the `EmailHash` of an account.|
|
||||
|`65542`|`AccountMessageKeySet`|Modify the `MessageKey` of an account.|
|
||||
|`65543`|`AccountTransferRateSet`|Modify the transfer rate of an account.|
|
||||
|`65544`|`AccountTickSizeSet`|Modify the tick size of an account.|
|
||||
|`65545`|`PaymentMint`|Send a payment for a currency where the sending account is the issuer.|
|
||||
|`65546`|`PaymentBurn`|Send a payment for a currency where the destination account is the issuer.|
|
||||
|`65547`|`MPTokenIssuanceLock`|Use the `MPTIssuanceSet` transaction to lock (freeze) a holder.|
|
||||
|`65548`|`MPTokenIssuanceUnlock`|Use the `MPTIssuanceSet` transaction to unlock (unfreeze) a holder.|
|
||||
|
||||
For example, if an account is authorized by `TrustlineFreeze`, it can freeze a trust line by sending a `TrustSet` transaction. However, since it is only authorized to freeze trust lines, it cannot perform other `TrustSet` operations such as unfreezing a trust line, setting No Ripple, applying Deep Freeze, etc.
|
||||
When an account is authorized by both `TrustlineFreeze` and `TrustSet`, the delegation is still valid, but the granular permission `TrustlineFreeze` has no effect, since the account is already permitted to perform all actions under `TrustSet`.
|
||||
|
||||
For multi-signing a delegation transaction, which is sent by a delegated account, the multi signers must be the delegated account's signers instead of the delegating account's multi signers.
|
||||
|
||||
### Limitations to Granular Permissions
|
||||
|
||||
The set of permissions must be hard-coded. No custom configurations are allowed. For example, you cannot add permissions based on specific currencies.
|
||||
|
||||
In addition, each permission needs to be implemented on its own in the source code. Adding a new permission requires an amendment.
|
||||
|
||||
|
||||
## Failure Conditions
|
||||
|
||||
The `DelegateSet` transaction fails if:
|
||||
|
||||
- The `Permissions` array contains more than 10 entries.
|
||||
- The `Permissions` array contains duplicate entries.
|
||||
- Any of the specified `PermissionValues` are invalid.
|
||||
- The `Authorize` account does not exist.
|
||||
|
||||
## State Changes
|
||||
|
||||
A successful `DelegateSet` transaction results in the creation, modification, or deletion of a `Delegate` ledger object.
|
||||
|
||||
- If no `Delegate` object exists for the given `Account` and `Authorize` pair, a new one is created.
|
||||
- If a `Delegate` object already exists, its `Permissions` field is updated.
|
||||
- If the `Permissions` array is empty, the `Delegate` object is deleted.
|
||||
|
||||
## Error Cases
|
||||
|
||||
- If the `Account` is the same as `Authorize`, return `temMALFORMED`.
|
||||
Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md):
|
||||
|
||||
- If the `Authorize` account does not exist, return `tecNO_TARGET`.
|
||||
| Error Code | Description |
|
||||
|:--------------------------|:------------|
|
||||
| `tecDIR_FULL` | The sender owns too many items in the ledger already. |
|
||||
| `tecINSUFFICIENT_RESERVE` | The sender does not have enough XRP to meet the [reserve requirement](/docs/concepts/accounts/reserves.md) of creating a new Delegate ledger entry. |
|
||||
| `tecNO_PERMISSION` | At least one permission in the `Permissions` list is not delegatable. See [Permission Values](../../data-types/permission-values.md) for which permissions are not delegatable. |
|
||||
| `tecNO_TARGET` | The account specified in the `Authorize` field does not exist in the ledger. |
|
||||
| `temARRAY_TOO_LARGE` | The `Permissions` list is too large. It cannot contain more than 10 entries. |
|
||||
| `temDISABLED` | The [Permission Delegation amendment][] is not enabled. |
|
||||
| `temMALFORMED` | The transaction was invalid. For example, the `Authorize` account is the same as the sender of the transaction, the `Permissions` list contains duplicate entries, or one of the permissions in the list is not a valid permission. |
|
||||
|
||||
- If the `Permissions` list size exceeds 10, return `temARRAY_TOO_LARGE`.
|
||||
|
||||
- If `Permissions` contains a duplicate value, return `temMALFORMED`.
|
||||
|
||||
- If `Permissions` contains transactions that are disabled for delegation, return `tecNO_PERMISSION`.
|
||||
The transactions disabled for delegation include: `AccountSet`, `RegularKeySet`, `SignerListSet`, `AccountDelete`, `DelegateSet`, `EnableAmendment`, `SetFee`, `UNLModify`, `LedgerStateFix`.
|
||||
|
||||
- If the Account does not have enough balance to meet the reserve requirement, (because `DelegateSet` will create a ledger object `ltDELEGATE`, whose owner is `Account`), return `tecINSUFFICIENT_RESERVE`.
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
|
||||
@@ -45,7 +45,7 @@ _(Added by the [PriceOracle amendment][].)_
|
||||
| `OracleDocumentID` | Number | UInt32 | Yes | A unique identifier of the price oracle for the `Account`. |
|
||||
| `Provider` | String | Blob | Variable | An arbitrary value that identifies an oracle provider, such as Chainlink, Band, or DIA. This field is a string, up to 256 ASCII hex encoded characters (0x20-0x7E). This field is required when creating a new `Oracle` ledger entry, but is optional for updates. |
|
||||
| `URI` | String | Blob | No | An optional Universal Resource Identifier to reference price data off-chain. This field is limited to 256 bytes. |
|
||||
| `LastUpdateTime` | Number | UInt32 | Yes | The time the data was last updated, in seconds since the UNIX Epoch. |
|
||||
| `LastUpdateTime` | Number | UInt32 | Yes | The time the data was last updated, in seconds since the [UNIX Epoch](https://en.wikipedia.org/wiki/Unix_time). The value must be within 300 seconds (5 minutes) of the ledger's close time. |
|
||||
| `AssetClass` | String | Blob | Variable | Describes the type of asset, such as "currency", "commodity", or "index". This field is a string, up to 16 ASCII hex encoded characters (0x20-0x7E). This field is required when creating a new `Oracle` ledger entry, but is optional for updates. |
|
||||
| `PriceDataSeries` | Array | Array | Yes | An array of up to 10 `PriceData` objects, each representing the price information for a token pair. More than five `PriceData` objects require two owner reserves. |
|
||||
|
||||
@@ -66,6 +66,13 @@ _(Added by the [PriceOracle amendment][].)_
|
||||
- Token pairs in the transaction with a missing `AssetPrice` field delete corresponding token pairs in the object.
|
||||
- Token pairs that only appear in the object have `AssetPrice` and `Scale` removed to signify that the price is outdated.
|
||||
|
||||
When updating fewer entries than the existing oracle contains, the `LastUpdateTime` applies to all entries. Entries not included in the update have their prices removed to indicate they are out of date for the given `LastUpdateTime`. To access historical price data for these entries, you can:
|
||||
|
||||
- Use the `ledger_entry` method with `PreviousTxnLgrSeq` to traverse previous Oracle objects
|
||||
- Use the `tx` method with `PreviousTxnID` to find historical transactions
|
||||
|
||||
This design choice saves space by having a single `LastUpdateTime` for all entries rather than tracking update times per token pair.
|
||||
|
||||
{% admonition type="info" name="Note" %}
|
||||
The order of token pairs in the transaction isn't important because each token pair uniquely identifies the location of the `PriceData` object in the `PriceDataSeries`.
|
||||
{% /admonition %}
|
||||
@@ -79,7 +86,7 @@ Besides errors that can occur for all transactions, `OracleSet` transactions can
|
||||
|---------------------------|-------------|
|
||||
| `temARRAY_EMPTY` | The `PriceDataSeries` has no `PriceData` objects. |
|
||||
| `tecARRAY_TOO_LARGE` | The `PriceDataSeries` exceeds the ten `PriceData` objects limit. |
|
||||
| `tecINVALID_UPDATE_TIME` | The `Oracle` object has an invalid `LastUpdateTime` value. |
|
||||
| `tecINVALID_UPDATE_TIME` | The `LastUpdateTime` is invalid. This can occur when the time is more than 300 seconds before or after the ledger close time, or when updating an existing oracle, the new `LastUpdateTime` is not greater than the previous value. |
|
||||
| `tecTOKEN_PAIR_NOT_FOUND` | The token pair you're trying to delete doesn't exist in the `Oracle` object. |
|
||||
| `tecARRAY_EMPTY` | The `PriceDataSeries` has no `PriceData` objects. |
|
||||
| `temARRAY_TOO_LARGE` | The `PriceDataSeries` exceeds the ten `PriceData` objects limit. |
|
||||
|
||||
@@ -38,7 +38,7 @@ There are no flags defined for {% $frontmatter.seo.title %} transactions.
|
||||
|
||||
## Error Cases
|
||||
|
||||
Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](https://xrpl.org/docs/references/protocol/transactions/transaction-results):
|
||||
Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md):
|
||||
|
||||
| Error Code | Description |
|
||||
|:--------------|:---------------------------------------------|
|
||||
|
||||
@@ -50,7 +50,7 @@ There are no flags defined for {% $frontmatter.seo.title %} transactions.
|
||||
|
||||
## Error Cases
|
||||
|
||||
Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](https://xrpl.org/docs/references/protocol/transactions/transaction-results):
|
||||
Besides errors that can occur for all transactions, {% $frontmatter.seo.title %} transactions can result in the following [transaction result codes](../transaction-results/index.md):
|
||||
|
||||
| Error Code | Description |
|
||||
|:--------------------------|:------------|
|
||||
|
||||
@@ -63,7 +63,7 @@ Send issued tokens from the operational account to the standby account. In the o
|
||||
|
||||
1. Select **Allow Rippling** and click **Configure Account**.
|
||||
{% admonition type="info" name="Note" %}
|
||||
This enables the `defaultRipple` flag on the issuing account, which is set to `false` by default. You need to enable this in order to trade tokens issued by the account. See [Configure Issuer Settings](../../how-tos/use-tokens/issue-a-fungible-token#3.-configure-issuer-settings) to learn more.
|
||||
This enables the `defaultRipple` flag on the issuing account, which is set to `false` by default. You need to enable this in order to trade tokens issued by the account. See [Configure Issuer Settings](../../how-tos/use-tokens/issue-a-fungible-token.md#3-configure-issuer-settings) to learn more.
|
||||
{% /admonition %}
|
||||
2. Enter a value in the **Amount** field, up to the maximum transfer amount you set in the trustline.
|
||||
3. Enter the standby account address in the **Destination** field.
|
||||
|
||||
Reference in New Issue
Block a user