ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-20 11:45:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixes per review.

Browse Source
This commit is contained in:
Dennis Dawson
2025-03-27 09:02:40 -07:00
parent 39fd0d782e
commit 753c092bc7
3 changed files with 18 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
docs/concepts/accounts/configuring-accounts.md
View File

@@ -15,7 +15,7 @@ There are three basic account configurations on the XRP Ledger.
Each of these accounts has different operational and security requirements for their function. You can start by configuring special behaviors that support the use case for each.
You can use the [Account Configurator](#using-the-account-configurator) to create new accounts on Testnet or Devnet and try out different permissions and configurations. You can also get information about accounts on Mainnet and see their real time settings.
You can use the [Account Configurator](#using-the-account-configurator) to create new accounts on Testnet or Devnet and try out different permissions and configurations. You can also get information about accounts on Mainnet and see their real-time settings.
## Holder
@@ -29,7 +29,7 @@ If the primary purpose of an account is to facilitate exchange of value between
| Flag | Description |
|------|-------------|
| `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) |
| `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). |
@@ -44,13 +44,13 @@ An account intended for issuing tokens requires configuration of both fields and
| Field | Description |
|-------|-------------|
| `Domain` | The domain is the URL to the server where you serve the xrp-ledger.toml file. It is recommended that you serve a human-readable website from the same domain as the xrp-ledger.toml file. The website can provide further information about your identity and how you use the XRP Ledger, which helps to build trust toward you and your services. See [Domain](../../references/xrp-ledger-toml.md). |
| `Domain` | The domain is the URL to the server where you serve the xrp-ledger.toml file. It is recommended that you serve a human-readable website from the same domain as the `xrp-ledger.toml` file. The website can provide further information about your identity and how you use the XRP Ledger, which helps to build trust toward you and your services. See [Domain](../../references/xrp-ledger-toml.md). |
| `TransferRate` | The `TransferRate` value specifies a fee to charge whenever counterparties transfer the currency you issue. The value is sent in 1 billion units. For example, 1200000000 represents a transfer fee of 20%. Note that the values _0_ and _1000000000_ represent the default (no fee); if you explicitly set either value, the value is not stored, but assumed. See [Transfer Fees](../tokens/transfer-fees.md). |
| `TickSize` | The `TickSize` value truncates the number of significant digits in the exchange rate of an offer when it gets placed in an order book. See [TickSize](../tokens/decentralized-exchange/ticksize.md). |
### Signers
Multi-signing in the XRP Ledger is a method of authorizing transactions by using a combination of multiple secret keys. You create a list of signer accounts. Each signer has a weight, representing the relative authority of that signer account. The signer quorum represents the minimum weight total required to authorize a transaction. For example, if Ashad and Betty each have a signer weight of 1, Ceresia has a signer weight of 2, and the signer quorum is 3, Ashad and Ceresia can approve a transaction (weight total of 3), Betty and Ceresia can approve a transaction (weight total of 3), but Ashad and Betty cannot approve a transaction on their own (their combined signer weight is 2, 1 less than the required signer weight). See [Multi-Signing](./multi-signing.md).
Multi-signing in the XRP Ledger is a method of authorizing transactions by using a combination of multiple secret keys. You create a list of signer accounts. Each signer account has a weight that represents its relative authority. The signer quorum represents the minimum weight total required to authorize a transaction. For example, if Ashad and Betty each have a signer weight of 1, Ceresia has a signer weight of 2, and the signer quorum is 3, Ashad and Ceresia can approve a transaction (weight total of 3), Betty and Ceresia can approve a transaction (weight total of 3), but Ashad and Betty cannot approve a transaction on their own (their combined signer weight is 2, 1 less than the required signer weight). See [Multi-Signing](./multi-signing.md).
### Issuer Flags
@@ -156,7 +156,6 @@ async function getAccount() {
const my_wallet = (await client.fundWallet(null, { faucetHost })).wallet
results += '\nGot a wallet.'
// ------------------------------------------------------Get the current balance.
const my_balance = (await client.getXrpBalance(my_wallet.address))
accountField.value = my_wallet.address
seedField.value = my_wallet.seed
results += '\nAccount created.'
@@ -247,7 +246,6 @@ async function configureAccount() {
account: accountField.value,
ledger_index: "validated",
})
// client.disconnect()
json_results = JSON.stringify(my_acct_info, null, 2)
var parsedResults = JSON.parse(json_results)
let defRipBool = document.getElementById("defaultRipple").checked
@@ -487,8 +485,7 @@ async function configureAccount() {
/*****************************************
************* Set Holder *****************
*****************************************/
function setHolder()
{
function setHolder() {
document.getElementById("defaultRipple").checked = false
document.getElementById("allowTrustLineClawback").checked = false
document.getElementById("depositAuth").checked = false
@@ -529,11 +526,11 @@ async function removeSigners() {
"Fee": "12",
"SignerQuorum": 0
}
const preparedSigner = await client.autofill(my_signers)
const signedSigner = my_wallet.sign(preparedSigner)
const resultSigner = await client.submitAndWait(signedSigner.tx_blob)
resultField.value += JSON.stringify(resultSigner, null, 2)
client.disconnect()
const preparedSigner = await client.autofill(my_signers)
const signedSigner = my_wallet.sign(preparedSigner)
const resultSigner = await client.submitAndWait(signedSigner.tx_blob)
resultField.value += JSON.stringify(resultSigner, null, 2)
client.disconnect()
}
</script> -->
<!-- ************************************************************** -->
@@ -802,7 +799,7 @@ client.disconnect()
You can use the Account Configurator to view information about accounts on Mainnet, Testnet, and Devnet.
#### To get Account information
To get Account information:
1. Choose the account's ledger instance (_Mainnet_, _Testnet_ or _Devnet_).
2. Enter the account number in the **Account** field.
@@ -816,7 +813,7 @@ The response is displayed in the **Results** field.
You can create sandbox accounts on _Testnet_ or _Devnet_. To create an account on _Mainnet_, see [Creating Accounts](../accounts/index.md#creating-accounts).
#### To get a new Account
To get a new Account:
1. Choose the account's ledger instance (_Testnet_ or _Devnet_).
2. Click **Get New Account**.
@@ -827,7 +824,7 @@ Be sure to capture the **Seed** value for your new account so that you can easil
You can reload information for an existing account based on its seed value.
#### To get an account from its seed
To get an account from its seed:
1. Choose the account's ledger instance (_Testnet_ or _Devnet_).
2. Enter the value in the **Seed** field.
@@ -839,7 +836,7 @@ You can reload information for an existing account based on its seed value.
A Holder account requires no configuration (default settings). If the account previously had configuration changes, you can revert them and return the account to default status.
#### To configure a Holder account
To configure a Holder account:
1. Choose the account's ledger instance (_Testnet_ or _Devnet_).
2. Click **Get New Account**
@@ -857,7 +854,7 @@ If the account has never been configured, the response in the **Results** field
The standard Exchanger account configuration requires only four flags.
#### To configure an Exchanger account
To configure an Exchanger account:
1. Choose the account's ledger instance (_Testnet_ or _Devnet_).
2. Click **Get New Account**.
@@ -874,12 +871,11 @@ The standard Exchanger account configuration requires only four flags.
Configure an Issuer account by filling in additional fields and selecting flags that serve your needs.
#### To configure an Issuer account
To configure an Issuer account:
1. Choose the account's ledger instance (_Testnet_ or _Devnet_).
2. Click **Get New Account**.
OR
1. Enter a value in the **Seed** field.
2. Click **Get New Account** or:
1. Enter an existing seed value in the **Seed** field.
2. Click **Get Account From Seed**.
3. Choose the _Issuer_ **Account Configuration Template**.
The configuration flag checkboxes update with the 6 standard configuration choices. You can choose more or fewer
@@ -890,8 +886,6 @@ Configure an Issuer account by filling in additional fields and selecting flags
7. If you choose to include signers, this example module requires that you add valid account IDs in **Signer1 Account**, **Signer2 Account**, and **Signer3 Account**, a **Signer Weight** for each, and a **Signer Quorum** value.
8. Click **Configure Account**.
<!-- {% admonition type="info" name="Note" %}Admitting to laziness on the author's part (and avoiding scope creep), setting Signers for an account requires changing all of them in a single transaction. The additional programming required to allow for an indeterminate number of signers and updates to individual signer weights is not essential to understanding account configuration. The sample code is easy to manipulate if you want your own example to add more or fewer than 3 signers.{% /admonition %} -->
[![Account Configurator Issuer Results](../../img/cpt-account-configurator3.png)](../../img/cpt-account-configurator3.png)
### Removing Signers