diff --git a/assets/js/test-net.js b/assets/js/test-net.js index c879d8046f..f5f3ab07cd 100644 --- a/assets/js/test-net.js +++ b/assets/js/test-net.js @@ -1,39 +1,52 @@ -function rippleTestNetCredentials() { +function rippleTestNetCredentials(url, altnet_name) { - var credentials = $('#your-credentials'); - var address = $('#address'); - var secret = $('#secret'); - var balance = $('#balance'); - var loader = $('#loader'); + const credentials = $('#your-credentials') + const address = $('#address') + const secret = $('#secret') + const balance = $('#balance') + const loader = $('#loader') //reset the fields initially and for re-generation - credentials.hide(); - address.html(''); - secret.html(''); - balance.html(''); - loader.css('display', 'inline'); + credentials.hide() + address.html('') + secret.html('') + balance.html('') + loader.css('display', 'inline') //call the alt-net and get key generations $.ajax({ - url: "https://faucet.altnet.rippletest.net/accounts", + url: url, type: 'POST', dataType: 'json', success: function(data) { //hide the loader and show results loader.hide(); - credentials.hide().html('

Your Credentials

').fadeIn('fast'); - address.hide().html('

Address

' + data.account.address).fadeIn('fast'); - secret.hide().html('

Secret

' + data.account.secret).fadeIn('fast'); - balance.hide().html('

Balance

' + Number(data.balance).toLocaleString('en') + ' XRP').fadeIn('fast'); + credentials.hide().html('

Your Credentials

').fadeIn('fast') + address.hide().html('

Address

' + + data.account.address).fadeIn('fast') + secret.hide().html('

Secret

' + + data.account.secret).fadeIn('fast') + balance.hide().html('

Balance

' + + Number(data.balance).toLocaleString('en') + ' XRP').fadeIn('fast') }, error: function() { loader.hide(); - alert("There was an error with the Ripple Test Net, please try again."); + alert("There was an error with the "+altnet_name+" faucet. Please try again."); } - }); + }) } $(document).ready(function() { - $('#generate-creds-button').click(rippleTestNetCredentials); -}); + function testnet_click(evt) { + rippleTestNetCredentials("https://faucet.altnet.rippletest.net/accounts", + "Testnet") + } + function devnet_click(evt) { + rippleTestNetCredentials("https://faucet.devnet.rippletest.net/accounts", + "Devnet") + } + + $('#testnet-creds-button').click(testnet_click) + $('#devnet-creds-button').click(devnet_click) +}) diff --git a/content/concepts/consensus-network/parallel-networks.md b/content/concepts/consensus-network/parallel-networks.md index 4190e62eef..4075e0400c 100644 --- a/content/concepts/consensus-network/parallel-networks.md +++ b/content/concepts/consensus-network/parallel-networks.md @@ -1,30 +1,43 @@ # Parallel Networks -Most of the time, we describe the XRP Ledger as one collective, singular entity -- and that's mostly true. There is one production XRP Ledger peer-to-peer network, and all business that takes place on the XRP Ledger occurs within the production network. +There is one production XRP Ledger peer-to-peer network, and all business that takes place on the XRP Ledger occurs within the production network—the Mainnet. -However, sometimes you may want to do tests and experiments without interacting with the core network. That's why Ripple started the [Ripple Test Net](xrp-test-net-faucet.html), an "alternate universe" network, which can act as a testing ground for applications and the `rippled` server itself, without impacting the business operations of everyday XRP Ledger users. The Ripple Test Net (also known as the AltNet) has a separate supply of TestNet-only XRP, which Ripple [gives away for free](xrp-test-net-faucet.html) to parties interested in developing applications on the Test Net. +To help members of the XRPL community interact with XRPL technology without affecting anything on the Mainnet, Ripple hosts two alternative networks, or altnets: the Testnet and the Devnet. Here's a breakdown of all three networks: -**Caution:** Ripple makes no guarantees about the stability of the test network. It has been and continues to be used to test various properties of server configuration, network topology, and network performance. +| Network | Upgrade Cadence | Description | +|:--------|:----------------|:-------------------------------------------------| +| Mainnet | Stable releases | _The_ [XRP Ledger](xrp-ledger-overview.html), a decentralized cryptographic ledger powered by a network of peer-to-peer servers and the home of [XRP](xrp.html). | +| Testnet | Stable releases | An "alternate universe" network that acts as a testing ground for software built on the XRP Ledger, without impacting production XRP Ledger users and without risking real money. The [amendment status](known-amendments.html) of the Testnet is intended to closely mirror the Mainnet, although slight variations in timing may occur due to the unpredictable nature of decentralized systems. | +| Devnet | Beta releases | A preview of coming attractions, where unstable changes to the core XRP Ledger software may be tested out. Developers can use this altnet to interact with and learn about planned new XRPL features and amendments that are not yet enabled on the Mainnet. | + +Testnet and Devnet each have their own separate supply of test XRP, which Ripple [gives away for free](xrp-testnet-faucet.html) to parties interested in experimenting with the XRP Ledger and developing applications and integrations. Test XRP does not have real-world value and is lost when the network is reset. + +**Caution:** Ripple makes no guarantees about the stability of altnets. These networks have been and continue to be used to test various properties of server configuration, network topology, and network performance. -Over time, there may also be smaller, temporary test networks for specific purposes. ## Parallel Networks and Consensus There is no `rippled` setting that defines which network it uses. Instead, it uses the consensus of validators it trusts to know which ledger to accept as the truth. When different consensus groups of `rippled` instances only trust other members of the same group, each group continues as a parallel network. Even if malicious or misbehaving computers connect to both networks, the consensus process overrides the confusion as long as the members of each network are not configured to trust members of another network in excess of their quorum settings. +Ripple operates the main servers in the Testnet and Devnet; you can also [connect your own `rippled` server to the Testnet](connect-your-rippled-to-the-xrp-test-net.html). The Testnet and Devnet do not use diverse, censorship-resistant sets of validators. This makes it possible for Ripple to reset the Testnet or Devnet on a regular basis. + + +## See Also + - **Tools:** - - [XRP Test Net Faucet](xrp-test-net-faucet.html) + - [XRP Testnet Faucet](xrp-test-net-faucet.html) - **Concepts:** - [Introduction to Consensus](intro-to-consensus.html) - [Amendments](amendments.html) - **Tutorials:** - - [Connect Your `rippled` to the XRP Test Net](connect-your-rippled-to-the-xrp-test-net.html) + - [Connect Your `rippled` to the XRP Testnet](connect-your-rippled-to-the-xrp-test-net.html) - [Use rippled in Stand-Alone Mode](use-stand-alone-mode.html) - **References:** - [server_info method][] - [consensus_info method][] - [validator_list_sites method][] - [validators method][] + - [Daemon Mode Options](commandline-usage.html#daemon-mode-options) diff --git a/content/dev-tools/dev-tools.md b/content/dev-tools/dev-tools.md index 1b453f1860..82db637d54 100644 --- a/content/dev-tools/dev-tools.md +++ b/content/dev-tools/dev-tools.md @@ -15,9 +15,9 @@ Ripple provides a set of developer tools to help you test, explore, and validate Need to see the Data API v2 in action ASAP? Use this tool to send prepopulated sample requests and get responses. No setup required. -* **[XRP Ledger Test Net Faucet](xrp-test-net-faucet.html)** +* **[XRP Ledger Testnet Faucet](xrp-testnet-faucet.html)** - Use the WebSocket and JSON-RPC Test Net endpoints to test software built on the XRP Ledger without using real funds. Generate Test Net credentials and funds for testing purposes. Test Net ledger and balances are reset on a regular basis. + Get credentials and test XRP for XRP Ledger Testnet or Devnet, and connect to servers in these parallel networks to test building software on the XRP Ledger without using real funds. * **[xrp-ledger.toml Checker](xrp-ledger-toml-checker.html)** @@ -25,11 +25,11 @@ Ripple provides a set of developer tools to help you test, explore, and validate * **[Transaction Sender](tx-sender.html)** - Test how your code handles various XRP Ledger transactions by sending them over the Test Net to the address of your choice. - + Test how your code handles various XRP Ledger transactions by sending them over the Testnet to the address of your choice. + * **[XRP Ledger Explorer](https://livenet.xrpl.org/)** - View validations of new ledger versions in real-time, chart the geographic location of servers in the XRP Ledger network, and explore the state of the ledger. [Test Net Explorer](https://testnet.xrpl.org/) also available! + View validations of new ledger versions in real-time, chart the geographic location of servers in the XRP Ledger network, and explore the state of the ledger. [Testnet Explorer](https://testnet.xrpl.org/) also available! Have an idea for a tool not provided here? [Contact us >](mailto:docs@ripple.com) diff --git a/content/tutorials/get-started/get-started-with-the-rippled-api.md b/content/tutorials/get-started/get-started-with-the-rippled-api.md index 6c2fd20504..70f72ebeba 100644 --- a/content/tutorials/get-started/get-started-with-the-rippled-api.md +++ b/content/tutorials/get-started/get-started-with-the-rippled-api.md @@ -24,10 +24,12 @@ The response comes as a JSON object. Currently Ripple (the company) maintains a set of public WebSocket servers at: -| `Domain` | Port | Notes | -|:----------------|:-----|:--------------------------------------| -| `s1.ripple.com` | 443 | `wss://` only; general purpose server | -| `s2.ripple.com` | 443 | `wss://` only; full-history server | +| URL | [Network](parallel-networks.html) | Notes | +|:--------------------------------------|:----------------------------------|:--| +| `wss://s1.ripple.com/` | Mainnet | General purpose server cluster | +| `wss://s2.ripple.com/` | Mainnet | [Full-history server](ledger-history.html#full-history) cluster | +| `wss://s.altnet.rippletest.net:51233` | Testnet | Testnet public server | +| ***TBD*** | Devnet | Devnet public server | These public servers are not for sustained or business use, and they may become unavailable at any time. For regular use, you should run your own `rippled` server or contract someone you trust to do so. @@ -55,10 +57,12 @@ The response is also a JSON object. Currently, Ripple (the company) maintains a set of public JSON-RPC servers at: -| `Domain` | Port | Notes | -|:----------------|:------|:-----------------------| -| `s1.ripple.com` | 51234 | General purpose server | -| `s2.ripple.com` | 51234 | Full-history server | +| URL | [Network](parallel-networks.html) | Notes | +|:----------------------------------------|:----------------------------------|:--| +| `https://s1.ripple.com:51234/` | Mainnet | General purpose server cluster | +| `https://s2.ripple.com:51234/` | Mainnet | [Full-history server](ledger-history.html#full-history) cluster | +| `https://s.altnet.rippletest.net:51234` | Testnet | Testnet public server | +| ***TBD*** | Devnet | Devnet public server | These public servers are not for sustained or business use, and they may become unavailable at any time. For regular use, you should run your own `rippled` server or contract someone you trust to do so. diff --git a/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md b/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md index 9499f73fde..f077c157b3 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md +++ b/content/tutorials/manage-the-rippled-server/configuration/connect-your-rippled-to-the-xrp-test-net.md @@ -1,4 +1,4 @@ -# Connect Your rippled to the XRP Test Net +# Connect Your rippled to an XRPL Altnet Ripple has created the [XRP Test Network](parallel-networks.html) to provide a testing platform for the XRP Ledger. XRP Test Net funds are not real funds and are intended for testing only. You can connect your `rippled` server to the XRP Test Net to test out and understand `rippled` functionality before connecting to the production XRP Ledger Network. You can also use the XRP Test Net to verify that your own code interacts correctly with `rippled`. @@ -52,7 +52,7 @@ To connect your `rippled` server to the XRP Test Net, set the following configur ## See Also - [Parallel Networks](parallel-networks.html) -- [XRP Test Net Faucet](xrp-test-net-faucet.html) +- [XRP Testnet Faucet](xrp-test-net-faucet.html) {% include '_snippets/rippled-api-links.md' %} diff --git a/dactyl-config.yml b/dactyl-config.yml index 6ece65e835..daba78a136 100644 --- a/dactyl-config.yml +++ b/dactyl-config.yml @@ -3035,16 +3035,16 @@ pages: - local template: template-xrp-ledger-toml-checker.html - - name: XRP Test Net Faucet - funnel: Dev Tools + - name: XRPL Testnet Faucet html: xrp-testnet-faucet.html + funnel: Dev Tools + template: template-test-net.html targets: - local - template: template-test-net.html - name: XRP Test Net Faucet # Redirect from old URL - funnel: Dev Tools html: xrp-test-net-faucet.html + funnel: Dev Tools template: template-redirect.html redirect_url: xrp-testnet-faucet.html targets: diff --git a/tool/template-test-net.html b/tool/template-test-net.html index 5e781ae5c5..4f3e4673c7 100644 --- a/tool/template-test-net.html +++ b/tool/template-test-net.html @@ -15,6 +15,18 @@ 
https://s.altnet.rippletest.net:51234
+
+
+

Devnet Servers

+
+
+

Use the following URLs to connect to the XRP Devnet.

+
Websockets and Ripple API
+ 
wss://s.devnet.rippletest.net:51233
+
JSON-RPC
+ 
https://s.devnet.rippletest.net:51234
+
+
{% endblock %} {% block main %} @@ -22,9 +34,13 @@

XRP Testnet Faucet

-

Ripple runs this parallel XRP Ledger test network, or Testnet, to provide a testing platform for any software products built on the XRP Ledger without using real funds.

-

Testnet funds are intended for testing only. The Testnet ledger and balances will be reset approximately every 90 days, or when otherwise necessary.

- +

Ripple runs these parallel XRP Ledger test networks, the Testnet and Devnet, to provide a testing platform for any software products built on the XRP Ledger without using real funds.

+

These funds are intended for testing only. The Testnet ledger and balances will be reset approximately every 90 days, or when otherwise necessary. Devnet funds may be reset without warning as needed.

+

Testnet and Devnet balances are separate. As a precaution, do not use the Testnet or Devnet credentials on the Mainnet.

+