Change domain from obscu.ro to ten.xyz (#1733)

.github/workflows/manual-deploy-testnet-validator.yml

@@ -6,7 +6,7 @@
 # # # # README # # # #
 #
 # 1 - Fetch the Management, Msg Bus Contract addresses and L1 Start Hash from:
-# curl -X POST erpc.dev-testnet.obscu.ro:80  -H 'Content-Type: application/json'  \
+# curl -X POST erpc.dev-testnet.ten.xyz:80  -H 'Content-Type: application/json'  \
 # -d '{"jsonrpc":"2.0","method":"obscuro_config","params":[],"id":1}'
 #
 # 2 - Update the secrets in Github

.github/workflows/runner-scripts/wait-node-healthy.sh

@@ -9,7 +9,7 @@ help_and_exit() {
     echo ""
     echo "Usage: "
     echo "   ex: "
-    echo "      -  $(basename "${0}") --host=erpc.uat-testnet.obscu.ro --port=80"
+    echo "      -  $(basename "${0}") --host=erpc.uat-testnet.ten.xyz --port=80"
     echo ""
     echo "  node             *Required* Set the host address"
     echo ""

README.md

@@ -1,6 +1,6 @@
 # Go Ten
 
-This repository contains the reference implementation of the [Ten Protocol](https://whitepaper.obscu.ro/).
+This repository contains the reference implementation of the [Ten Protocol](https://whitepaper.ten.xyz/).
 
 *Note that this is still very much a work in progress, so there are many rough edges and unfinished components.*
 
@@ -62,7 +62,7 @@ extracts useful information from them, such as published rollups, deposits to th
 at this level to rollback the Ten state accordingly.
 
 To avoid the risk of the Enclave being fed invalid blocks which an attacker can use to probe for information, or to shorten the 
-[revelation period](https://whitepaper.obscu.ro/ten-whitepaper/detailed-design.html#revelation-mechanism), the blocks have to be checked for validity, which includes checking that enough "work" went into them.
+[revelation period](https://whitepaper.ten.xyz/ten-whitepaper/detailed-design.html#revelation-mechanism), the blocks have to be checked for validity, which includes checking that enough "work" went into them.
 To achieve this we depend on the [Blockchain](https://github.com/ethereum/go-ethereum/blob/e6fa102eb08c2b83ab75e85ca7860eea3a10dab0/core/blockchain.go) 
 logic.
 
@@ -183,7 +183,7 @@ The missing link to achieving fully private transactions while allowing end-user
 wallets (like MetaMask). This is a very thin component that is responsible for encrypting and decrypting traffic 
 between the Ten node and its clients.
 
-See the [docs](https://docs.obscu.ro/wallet-extension/wallet-extension/) for more information.
+See the [docs](https://docs.ten.xyz/wallet-extension/wallet-extension/) for more information.
 
 
 ## Repository Structure
@@ -388,7 +388,7 @@ Remix (see[docs/testnet/deploying-a-smart-contract.md](docs/testnet/deploying-a-
 e.g. using web3.py(see [docs/testnet/deploying-a-smart-contract-programmatically.md](docs/testnet/deploying-a-smart-contract-programmatically.md)). 
 
 Note that in order to interact with the main cloud hosted testnet, all that needs to be changed is to start the wallet 
-extension using the default parameters, where the `nodeHost` will default to the testnet host URL `erpc.sepolia-testnet.obscu.ro` i.e. 
+extension using the default parameters, where the `nodeHost` will default to the testnet host URL `erpc.sepolia-testnet.ten.xyz` i.e. 
 
 ```
 cd ./tools/walletextension/main/

design/README.md

@@ -1,6 +1,6 @@
 # Ten design documents
 
-Ten started based on a (whitepaper)[https://whitepaper.obscu.ro/] published in Nov. 2021.
+Ten started based on a (whitepaper)[https://whitepaper.ten.xyz/] published in Nov. 2021.
 
 As we started development, we started thinking more deeply about some aspects and also getting feedback from the community
 and the users.

design/architecture/overall_design.md

@@ -3,7 +3,7 @@
 ## Scope
 
 The purpose of this document is to describe aspects of Ten's technical design that are not addressed in the 
-[Ten whitepaper](https://whitepaper.obscu.ro/).
+[Ten whitepaper](https://whitepaper.ten.xyz/).
 
 ## Overview
 
@@ -17,7 +17,7 @@ The following additional components must be developed:
 * **The enclave:** The trusted part of the Ten node that runs inside a trusted execution environment (TEE)
 * **The host:** The remainder of the Ten node that runs outside the TEE
 * **The Ten management contract:** The Ethereum mainnet contracts required by the Ten protocol, described 
-  [here](https://whitepaper.obscu.ro/ten-whitepaper/l1-contracts)
+  [here](https://whitepaper.ten.xyz/ten-whitepaper/l1-contracts)
 * **Client apps:** Applications that interact with the Ten node (e.g. Ten wallets)
 
 ## Host/enclave split

docs/README.md

@@ -1,6 +1,6 @@
 # Ten Doc Site
 
-This is the Ten Doc Site and it looks like [this](https://docs.obscu.ro/).
+This is the Ten Doc Site and it looks like [this](https://docs.ten.xyz/).
 
 ## Adding New Doc Site Pages
 
@@ -14,7 +14,7 @@ This is the Ten Doc Site and it looks like [this](https://docs.obscu.ro/).
 4. Push your changes to tennet/go-ten
 5. GitHub Pages will trigger a GitHub Action to use a Jekyll build job to create the static content and then publish 
    the pages at the custom URL.
-6. Browse to https://docs.obscu.ro/ and check your content. Remember your browser will cache some of the pages so hit 
+6. Browse to https://docs.ten.xyz/ and check your content. Remember your browser will cache some of the pages so hit 
    refresh a few times if it looks like the content is missing or the navigation menu is incorrect.
 
 ## Updating Existing Doc Site Pages

docs/_config.yml

@@ -6,7 +6,7 @@ minimal_mistakes_skin: "default"
 locale: "en-UK"
 title: "Obscuro"
 description: "Obscuro is an Ethereum-compatible confidential smart contract L2 network."
-url: "https://obscu.ro"
+url: "https://ten.xyz"
 name: "Obscuro"
 repository: "obscuronet/obscuro.github.io"
 

docs/_data/navigation.yml

@@ -1,10 +1,10 @@
 main:
   - title: "Whitepaper"
-    url: https://whitepaper.obscu.ro
+    url: https://whitepaper.ten.xyz
   - title: "Tokenomics"
     url: https://github.com/obscuronet/foundation/blob/main/token-utility-whitepaper.md
   - title: "Community Contributions"
-    url: https://docs.obscu.ro/community/contributions
+    url: https://docs.ten.xyz/community/contributions
   - title: "Get Help"
     url: https://discord.gg/yQfmKeNzNd
 

docs/_docs/api/sensitive-apis.md

@@ -7,7 +7,7 @@ Ten supports a subset of Ethereum's [JSON-RPC API](https://ethereum.org/en/devel
 Some of these methods deal with sensitive information. For example, the response to an `eth_getBalance` request will 
 contain the balance of an account. An attacker could intercept this response to discover a user's balance. To avoid 
 this, the requests and responses for methods deemed sensitive are encrypted and decrypted by the 
-[wallet extension](https://docs.obscu.ro/wallet-extension/wallet-extension). To ensure a good user experience, this process is 
+[wallet extension](https://docs.ten.xyz/wallet-extension/wallet-extension). To ensure a good user experience, this process is 
 invisible to the end user.
 
 This page details which JSON-RPC API methods are deemed sensitive, and the rules governing who is able to decrypt the 

docs/_docs/community/contributions.md

@@ -4,7 +4,7 @@
 
 Ten will evolve to be *the* solution for privacy on Ethereum through the strength and dedication of the Ten community. Together we'll make Ten the most community-driven project in crypto.
 
-As detailed in the [whitepaper](https://whitepaper.obscu.ro), Ten is powered by TEN, a native utility token that provides security to the Ten network while allowing holders to pay transaction fees.
+As detailed in the [whitepaper](https://whitepaper.ten.xyz), Ten is powered by TEN, a native utility token that provides security to the Ten network while allowing holders to pay transaction fees.
 
 2% of tokens are set aside for early contributors. Each contributor's allocation is a percentage of their total contributions against the entire community contribution.
 

docs/_docs/testnet/Introduction.md

@@ -5,11 +5,11 @@ This section contains detailed on how to connect, build and deploy on Evan's Cat
 
 Evan's Cat can also be used by end users to help test Ten and test developer dApps. Evan's Cat does not focus on node operators. Support for node operators will arrive in the next version of testnet. 
 
-Developers can expect frequent updates which will be communicated [here](https://docs.obscu.ro/testnet/changelog). The trade-off is that in the early days Testnet will have some sharp edges and unexpected surprises. More specifically, whilst Testnet is in its infancy:
+Developers can expect frequent updates which will be communicated [here](https://docs.ten.xyz/testnet/changelog). The trade-off is that in the early days Testnet will have some sharp edges and unexpected surprises. More specifically, whilst Testnet is in its infancy:
 * Ten Testnet will crash from time to time, and will frequently be updated with new features.
 * When Ten Testnet restarts expect to lose everything.
 * Ten Testnet code has not been optimised or audited yet. (Mainnet code will be audited prior to launch.)
-* The [Wallet extension](https://docs.obscu.ro/wallet-extension/wallet-extension) is still being improved.
+* The [Ten Gateway](https://docs.ten.xyz/docs/tools-infrastructure/hosted-gateway) is still being improved.
 * The decryption key is known by all allowing you to decrypt and view everything. This also allows the wider community to support you in development.
 
 All Ten code is under an open source licence. If you see something you think could be improved or reworked feel free to submit a PR in the [go-ten repo](https://github.com/ten-protocol/go-ten), or to let us know about your suggestion on [Discord](https://discord.com/channels/916052669955727371/945360340613484684). 

docs/_docs/testnet/changelog.md

@@ -787,22 +787,22 @@
 * The list of sensitive RPC API methods, where the request and response is encrypted in transit, now covers
   `eth_call`, `eth_estimateGas`, `eth_getBalance`, `eth_getLogs`, `eth_getTransactionByHash`, `eth_getTransactionCount`,
   `eth_getTransactionReceipt` and `eth_sendRawTransaction`. See the Obscuro
-  [documentation](https://docs.obscu.ro/api/sensitive-apis/) for more details.
+  [documentation](https://docs.ten.xyz/api/sensitive-apis/) for more details.
 * Calls to wait for a transaction receipt are now blocking, whereas previously they would return an error meaning the
   client side code needed to perform a specific wait and poll loop. The example on how to [programmatically deploy
-  a contract](https://docs.obscu.ro/testnet/deploying-a-smart-contract-programmatically/) has been updated accordingly.
+  a contract](https://docs.ten.xyz/testnet/deploying-a-smart-contract-programmatically/) has been updated accordingly.
 * The ability to start a faucet server against a local testnet deployment is now supported via a docker
   container. For more information see the Obscuro
   [readme](https://github.com/ten-protocol/go-ten#building-and-running-a-local-faucet).
 * Updates to the [Events](https://github.com/ten-protocol/go-ten/blob/main/design/ux/Events_design.md) design
   inclusion of the [Fast Finality](https://github.com/ten-protocol/go-ten/blob/main/design/finality_protocol/fast_finality.md) design.
-* The [Obscuro docs site](https://docs.obscu.ro/) is now searchable.
+* The [Obscuro docs site](https://docs.ten.xyz/) is now searchable.
 * Testnet is now officially termed `Evan's Cat`.
 
 * ObscuroScan:
   * ObscuroScan supports a single API at [/rollup/](http://testnet.obscuroscan.io/rollup/) which allows web clients to
     access a JSON representation of rollups and encrypted transactions. Further details
-    [here](https://docs.obscu.ro/testnet/obscuroscan)
+    [here](https://docs.ten.xyz/testnet/obscuroscan)
 
 ## October 2022-10-21 (v0.5)
 * Event Subscriptions:
@@ -814,7 +814,7 @@
 * Wallet extension:
   * The wallet extension now supports separate ports for HTTP and WebSocket connections. Use the `--port` and `--portWS`
     command line options respectively for each. For more information see the
-    [Wallet extension](https://docs.obscu.ro/wallet-extension/wallet-extension) documentation.
+    [Wallet extension](https://docs.ten.xyz/wallet-extension/wallet-extension) documentation.
 * Event subscription:
   * An early preview of event subscriptions is available in this release, though note that this is still undergoing
     testing and feature enhancements and therefore is liable to issues and instability. For more information on the

docs/_docs/testnet/deploying-a-smart-contract-programmatically.md

@@ -13,7 +13,7 @@ the local host with default values `WHOST=127.0.0.1` and `WPORT=3000`.
 A walk through and explanation of the steps performed is given below;
 
 ## Connect to the network and create a local private key
-The [wallet extension](https://docs.obscu.ro/wallet-extension/wallet-extension/) acts as an HTTP server to mediate RPC requests. In the 
+The [wallet extension](https://docs.ten.xyz/wallet-extension/wallet-extension/) acts as an HTTP server to mediate RPC requests. In the 
 below a connection is made on the wallet extension host and port, a private key is locally created and the associated 
 account stored for later usage.
 

docs/_docs/testnet/deploying-a-smart-contract.md

@@ -5,12 +5,12 @@ Using the steps below you will add an extension to your MetaMask wallet so it ca
 
 ## Prerequisites
 * [MetaMask](https://metamask.io/) wallet installed in your browser.
-* A local copy of the [Ten MetaMask wallet extension](https://docs.obscu.ro/wallet-extension/wallet-extension/)
+* A local copy of the [Ten MetaMask wallet extension](https://docs.ten.xyz/wallet-extension/wallet-extension/)
 
 ## Prepare Your MetaMask Wallet for Ten Testnet
 An essential part of how Ten provides full privacy is the encryption of communication between an Ten application and Ten nodes on the network.
 
-Follow the steps [here](https://docs.obscu.ro/wallet-extension/wallet-extension/) to configure and start the wallet extension and 
+Follow the steps [here](https://docs.ten.xyz/wallet-extension/wallet-extension/) to configure and start the wallet extension and 
 generate a viewing key. 
 
 
@@ -32,7 +32,7 @@ You can now go ahead and deploy your smart contract to the Ten Testnet.
 
 1. Compile your smart contract using the Remix Solidity Compiler.
 
-1. Log in to MetaMask and confirm you are connected to Ten Testnet network. The parameters for the Ten Testnet can be found [here](https://docs.obscu.ro/testnet/essentials/).
+1. Log in to MetaMask and confirm you are connected to Ten Testnet network. The parameters for the Ten Testnet can be found [here](https://docs.ten.xyz/testnet/essentials/).
 
 1. In the _Deploy & Run Transactions_ section of Remix change the Environment to _Injected Web3_. This tells Remix to use the network settings currently configured in your MetaMask wallet, which in this case is the Ten Testnet. If the connection to Ten Testnet is successful you will see the text _Custom (443) network_ displayed under _Injected Web3_.
 
@@ -48,4 +48,4 @@ Congratulations, your smart contract is now deployed to Ten Testnet!
 
 Because Ten provides full privacy, the details of your transaction are encrypted and only visible to you, as the holder of your wallet's private key.
 
-Now head over to the [TenScan page](https://docs.obscu.ro/testnet/tenscan/) to see how you can view the transaction details.
+Now head over to the [TenScan page](https://docs.ten.xyz/testnet/tenscan/) to see how you can view the transaction details.

docs/_docs/testnet/essentials.md

@@ -14,8 +14,8 @@ These are the key limitations to be aware of when developing for the Evan's Cat
 1. The "Wallet Extension" is not fully polished yet. You can expect a better UX as Ten develops
 
 ## Connection to an Ten Node
-- **RPC http address:** `erpc.sepolia-testnet.obscu.ro:80`
-- **RPC websocket address:** `erpc.sepolia-testnet.obscu.ro:81`
+- **RPC http address:** `erpc.sepolia-testnet.ten.xyz:80`
+- **RPC websocket address:** `erpc.sepolia-testnet.ten.xyz:81`
 
 ## Rollup Encryption/Decryption Key
 The symmetric key used to encrypt and decrypt transaction blobs in rollups on the Ten Testnet:

docs/_docs/testnet/example-dapps.md

@@ -11,7 +11,7 @@ Consider for a moment how a secret number could be created without divulging it.
 Building the guessing game in Ten addresses both scenarios described above. The guessing game smart contract generates a random secret number when it is deployed. This number is never revealed to a player or node operator, or indeed anybody because it is generated within a Trusted Execution Environment. And when players make their guesses the transactions carrying the guesses are encrypted and therefore obscured in a block explorer.
 
 ### How to Play
-1. Start up the wallet extension. Follow instructions [here](https://docs.obscu.ro/wallet-extension/wallet-extension).
+1. Start up the wallet extension. Follow instructions [here](https://docs.ten.xyz/wallet-extension/wallet-extension).
 1. For the moment, the Guessing Game includes an ERC20 token (called OGG, short for Ten Guessing Game). This is partly because OGG is modified to have a built-in faucet: It allocates tokens to addresses as they make a request to allow other addresses to take tokens from their account.
 1. If you want to see this balance in your wallet, you have to import a new Token with the address: ``0x5FbDB2315678afecb367f032d93F642f64180aa3``
 1. Browse to [the number guessing game](http://tennet.github.io/sample-applications/number-guessing-game). Check you see `Network ID: 443` at the top of the game window to confirm you are connected to Ten Testnet.
@@ -36,4 +36,4 @@ Once the guess transaction is completed you can check the guess transaction on T
 ### Next Steps
 
 Now you have enjoyed playing the guessing game you are invited to make it even better! Go ahead and fork the guessing game code in this [GitHub repository](https://github.com/ten-protocol/number-guessing-game) and bring your own contributions to Ten Testnet.
-Of course, you are free to [deploy any smart contract](https://docs.obscu.ro/testnet/deploying-a-smart-contract) to the testnet.   
+Of course, you are free to [deploy any smart contract](https://docs.ten.xyz/testnet/deploying-a-smart-contract) to the testnet.   

docs/_docs/testnet/faucet.md

@@ -6,7 +6,7 @@ Using the steps below you will request testnet ETH from the faucet available on
 ## Prerequisites
 * Access to the [Ten Discord server](https://discord.gg/yQfmKeNzNd).
 * (Optional) [MetaMask](https://metamask.io/) wallet installed in your browser.
-* (Optional) A local copy of the [Ten MetaMask wallet extension](https://docs.obscu.ro/wallet-extension/wallet-extension/).
+* (Optional) A local copy of the [Ten MetaMask wallet extension](https://docs.ten.xyz/wallet-extension/wallet-extension/).
 
 ## Requesting Testnet ETH
 1. Make a note of your wallet address or copy it to your clipboard.
@@ -21,7 +21,7 @@ Using the steps below you will request testnet ETH from the faucet available on
 ## Viewing Your Wallet Balance
 To view the balance of your wallet you will need to establish a connection from your wallet to the Ten Testnet. An essential part of how Ten provides full privacy is the encryption of communication between an Ten application and Ten nodes on the network. As a result, you will need to use the wallet extension to allow your wallet to communication with the Ten Testnet.
 
-Use the steps [here](https://docs.obscu.ro/testnet/deploying-a-smart-contract/#prepare-your-metamask-wallet-for-ten-testnet) to prepare your MetaMask wallet for Ten Testnet.
+Use the steps [here](https://docs.ten.xyz/testnet/deploying-a-smart-contract/#prepare-your-metamask-wallet-for-ten-testnet) to prepare your MetaMask wallet for Ten Testnet.
 
 ## Requesting Testnet ETH directly
 In the event that you do not have access to Discord, or the faucet bot is not working, you can request ETH directly from