英語 での Accountset transaction の使用例とその 日本語 への翻訳
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Programming
These options can be changed with an AccountSet transaction.
An AccountSet transaction modifies the properties of an account in the XRP Ledger.
You can disable orenable the master key pair using an AccountSet transaction.
In this way, an AccountSet transaction with no options is the canonical"no-op" transaction. .
If you do not want the replacement transaction to do anything,send an AccountSet transaction with no options.
Note: The AccountSet transaction type has its own non-bitwise flags, which serve a similar purpose to type-based flags.
If none of these options are provided, then the AccountSet transaction has no effect(beyond destroying the transaction cost).
The preferred way to enable and disable Account Flags is using the SetFlag andClearFlag parameters of an AccountSet transaction.
A financial institution can submit an AccountSet transaction from its issuing address to change the TransferRate for its issuances.
This could be a SetRegularKey transaction to remove the regular key,a SignerListSet transaction to delete a SignerList, or an AccountSet transaction to disable the master key.
To enable No Freeze on an address, send an AccountSet transaction with the asfNoFreeze flag value in the SetFlag field.
The AccountSet transaction type has several transaction flags(prefixed tf) that can be used to enable or disable specific account options when passed in the Flags parameter.
TemBAD_TRANSFER_RATE The TransferRate field of an AccountSet transaction is not properly formatted or out of the acceptable range.
The AccountSet transaction type has several"AccountSet Flags"(prefixed asf) that can enable an option when passed as the SetFlag parameter, or disable an option when passed as the ClearFlag parameter.
The following Transaction flags, specific to the AccountSet transaction type, serve the same purpose, but are discouraged:.
Here's an example error response for an AccountSet transaction signed using the regular private key removed by the SetRegularKey transaction above.
TelBAD_PUBLIC_KEY The transaction specified a public key value(for example,as the MessageKey field of an AccountSet transaction) that cannot be used, probably because it is too long.
To verify that your account has the regular key pair set correctly,submit an AccountSet transaction from your account, signing it with the regular private key you assigned to your account in step 2. As in step 1, this tutorial uses a local rippled server as a way of securely signing transactions. .
TelBAD_DOMAIN The transaction specified a domain value(for example,the Domain field of an AccountSet transaction) that cannot be used, probably because it is too long to store in the ledger.
To enable Global Freeze on an address, send an AccountSet transaction with the asfGlobalFreeze flag value in the SetFlag field.
The following is an example of using alocally-hosted rippled's submit method to send an AccountSet transaction to enable the RequireAuth flag:(This method works the same way regardless of whether the address is an issuing address, operational address, or standby address.).
(This includes all SetRegularKey and SignerListSet transactions, as well as AccountSet transactions that change the RequireAuth/OptionalAuth, DisableMaster, or AccountTxnID flags.) You can try again later, or try submitting to a different server.