> For the complete documentation index, see [llms.txt](https://docs.getrekt.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getrekt.trade/testnet-wallet-setup.md).

# testnet wallet setup

Checked on **2026-10-16**. This guide prepares user-controlled wallets for a testnet trial. No GetRekt deployment or completed two-route bridge test is recorded. The requested 2000× ceiling, $REKT issuance schedule, and referrals are not yet implemented; review [implementation status](broken://pages/c7eabe8af8c3f2ae7c1c1dce69dad717e5d1ac7a) before signing a candidate deployment.

The intended product domain is [getrekt.trade](https://getrekt.trade/). Its connection is unverified. Open the setup and signing pages only from the separately confirmed project preview or your reviewed local build.

{% stepper %}
{% step %}

## Create the accounts

Install the extension through [Slush's official website](https://slush.app/). Create key-based accounts, set the password, and back up recovery material inside your own wallet workflow. Open `/setup.html` in the same browser as the extension; an embedded browser may not detect it.

| Account label    | Purpose                                   | Custody                                                  |
| ---------------- | ----------------------------------------- | -------------------------------------------------------- |
| GetRekt Admin A  | First administrator; may also be Guardian | First administrator                                      |
| GetRekt Admin B  | Second administrator                      | Second administrator                                     |
| GetRekt Admin C  | Third administrator                       | Third administrator                                      |
| GetRekt Deployer | Publish packages and create the Vault     | Separate test account                                    |
| GetRekt Oracle   | Operate OracleCap only                    | Separate service account; current local CLI uses Ed25519 |

One person may use three test accounts for rehearsal, but accounts controlled by one person or one recovery phrase do not provide independent custody. Do not treat that rehearsal as production governance.

A trader may use a separate wallet, or temporarily use Deployer for the first receiving and trading test. Receiving USDC does not supply SUI gas.
{% endstep %}

{% step %}

## Derive the multisig from public keys

Connect the wallet on the setup page, select each authorized admin account, and capture its public key in the corresponding A/B/C slot. The helper verifies that the key derives the selected address. It supports Ed25519, Secp256k1, and Secp256r1. Accounts that cannot pass this key-to-address check, including unsupported social-login accounts, cannot be used by this helper.

Each signer has weight 1; the threshold is 2, and ordering is A, B, C. Deriving a multisig address requires no transaction and costs no gas. See [Sui's multisig documentation](https://docs.sui.io/develop/transactions/transaction-auth/multisig).

Enter the Deployer, Oracle, and Guardian public addresses. The fee recipient may be the administration multisig. Every administrator should independently verify the keys, ordering, and final multisig address before downloading the public files:

* `only21m-testnet-setup.json`: the complete public setup record.
* `only21m-testnet-input.json`: the smaller input consumed by the deployment CLI.

These are the current tool's literal filenames; the legacy name does not change the product brand. Share only these public records. Never share recovery phrases, private keys, keystores, or API keys.

Address derivation is not a completed multisig signing test. Two administrators must sign the same TransactionData and combine signatures in the fixed order. A single-account Wallet Standard interface may not support that flow. The local procedure is in `contracts/21x/TESTNET-SETUP.md`.
{% endstep %}

{% step %}

## Obtain test assets

Use **Sui Testnet, Ethereum Sepolia, and Base Sepolia**. Real SUI, ETH, or USDC purchases are unnecessary for this trial.

| Purpose                      | Suggested reserve                      | Basis and limitations                                                                                                                                                                                |
| ---------------------------- | -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Deployer                     | 1 test SUI                             | Earlier RPC estimates: 0.0258976 SUI for governance publication and 0.1331456 SUI for market publication alone; 0.1590432 SUI combined, excluding installation, Vault creation, and later operations |
| Sui receiving/trading wallet | 1 test SUI                             | Reserve for Circle receiving and two trading trials; no measured complete E2E total exists                                                                                                           |
| Oracle                       | A separate 7 test SUI                  | Conservative declared budget reserve for a first window of at most 30 seconds, not an actual fee quote; simulate again with a current Pyth proof                                                     |
| Ethereum Sepolia             | 0.01 test ETH and at least 5 test USDC | Reserve for approval and burn; estimate gas again before signing                                                                                                                                     |
| Base Sepolia                 | 0.01 test ETH and at least 5 test USDC | A separate chain balance; Ethereum Sepolia funds do not substitute for it                                                                                                                            |

The publication measurements apply to earlier artifacts, not the unimplemented GetRekt changes. Storage rebates, gas prices, state, and service frequency affect actual costs. Each final transaction needs simulation with its real sender and gas source.

### Faucets

* [Sui faucet](https://faucet.sui.io/): select Testnet and enter the public Sui address. The checked PoW v3 flow credits **address balance**; the setup page separates that balance from Coin objects. See the [faucet guide](https://faucet.sui.io/how-to-use/).
* [Circle faucet](https://faucet.circle.com/): request USDC separately for Ethereum Sepolia and Base Sepolia using the EVM address. At the check date, the page allowed up to 20 test USDC per address/chain every two hours; current limits are shown there.
* [Ethereum Sepolia ETH faucet](https://faucets.chain.link/sepolia) and [Base Sepolia ETH faucet](https://faucets.chain.link/base-sepolia): eligibility and rate limits depend on the current provider rules.
  {% endstep %}

{% step %}

## Review and sign three deployment stages

After receiving public inputs, the preparation CLI can inspect balances, simulate, and build unsigned transaction plans. On `/deploy.html`, connect Deployer, load the public input and stage plan, review it, and approve the wallet yourself. Plans expire after 15 minutes; expired plans or changed gas/capability versions must be rebuilt.

{% stepper %}
{% step %}

### Publish the governance package

Deployer temporarily owns its UpgradeCap.
{% endstep %}

{% step %}

### Publish and install the market package

In one atomic transaction, publish the market, install its UpgradeCap in the 48-hour timelock, and destroy the governance package's own UpgradeCap. A plain market publish is not a substitute.
{% endstep %}

{% step %}

### Create the native Circle USDC Vault

Deliver AdminCap to the 2-of-3 multisig, OracleCap to Oracle, and GuardianCap to Guardian.
{% endstep %}
{% endstepper %}

Keep every confirmed digest and obtain the next stage's actual IDs from the receipt. The validator checks reviewed bytecode, exact commands, roles, testnet genesis, and gas rather than trusting a plan's text summary. An unknown result must be reconciled using the saved digest before another publication is attempted.

The earlier setup helper defaults to 100 USDC maximum position notional, 1,000 USDC total notional, and 2100× maximum configured leverage. Those defaults are unchanged code, not the new GetRekt specification. A GetRekt candidate must use a verified 2000× ceiling across code and tooling. The first trading trial uses 1× regardless of the ceiling.
{% endstep %}

{% step %}

## Run the oracle and both deposit trials

Obtain a Pyth API key through [Pyth Terminal](https://pythdata.app/) and store it in your own local secret file or secret manager. Do not paste it into chat or a public website. Hermes authentication requirements are described in [Pyth's upgrade guidance](https://docs.pyth.network/price-feeds/core/upgrade/preparing).

Oracle transactions currently require source data no older than two seconds at execution. That requires a fast local or external signer rather than a manual wallet prompt for each update. Start with dry-run, then at most a 30-second test window with the configured transaction and hourly gas limits. Commands and local secret handling are documented in `services/TESTNET-E2E.md`.

The 2026-10-16 sample failed Pyth confidence and Lighter/Kraken deviation checks. Even 1× would not bypass those component limits. Obtain a current verified proof, update the price, and confirm that every check passes before opening.

For each source chain, preserve the complete evidence chain: approve → burn → Iris attestation → Sui receive/mint → verified USDC owner and amount → fresh oracle → 1 USDC / 1× open → close. Begin with 5 USDC on each route. Receiving, opening, and closing each require their own successful evidence.

The sampled Circle sandbox fee endpoint returned HTTP 400 for Sui. That does not establish that the bridge is unsupported. The automatic fee path remains disabled; the restricted testnet Standard path requires verified official behavior, fixed Standard finality, zero maximum fee, and current source/destination checks. Do not silently substitute another route's fee or Fast mode.

The first bridge trial uses a restricted operator testnet mode after actual deployment data and governance checks are complete. The exact configuration hash is pinned into the website build. `bridgeEnabled` stays false and `cctpE2eDigest` stays null until the trial succeeds; mainnet cannot use this bootstrap mode.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.getrekt.trade/testnet-wallet-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.