> For the complete documentation index, see [llms.txt](https://docs.rip.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rip.xyz/marketplace-guides/contracts-and-networks.md).

# Contracts and networks

Identify the marketplace environment and verify its public contract configuration.

The addresses below identify the production marketplace on HyperEVM. The rHYPURR investment vault has its own [contract reference](https://docs.rip.xyz/hypurr-vault/contract-addresses.md).

| Network field  | Value                                                                   |
| -------------- | ----------------------------------------------------------------------- |
| Chain          | <code class="expression">space.vars.marketplace\_chain\_name</code>     |
| Chain ID       | <code class="expression">space.vars.marketplace\_chain\_id</code>       |
| Gas token      | <code class="expression">space.vars.marketplace\_native\_symbol</code>  |
| Explorer       | <code class="expression">space.vars.marketplace\_explorer\_url</code>   |
| Release status | <code class="expression">space.vars.marketplace\_release\_status</code> |

Production uses the main HyperEVM chain. Confirm the contract address in the wallet before approving or submitting a transaction.

## Production contracts

| Contract                                                                                         | Address                                                                                        |
| ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
| NFT marketplace                                                                                  | <code class="expression">space.vars.marketplace\_production\_address</code>                    |
| Collection, <code class="expression">space.vars.marketplace\_production\_collection\_name</code> | <code class="expression">space.vars.marketplace\_production\_collection\_address</code>        |
| Discount token                                                                                   | <code class="expression">space.vars.marketplace\_production\_discount\_token\_address</code>   |
| Wrapped native token                                                                             | <code class="expression">space.vars.marketplace\_wrapped\_address</code>                       |
| Seller-vault factory                                                                             | <code class="expression">space.vars.marketplace\_production\_factory\_address</code>           |
| Vault registry                                                                                   | <code class="expression">space.vars.marketplace\_production\_registry\_address</code>          |
| Seller-vault beacon                                                                              | <code class="expression">space.vars.marketplace\_production\_beacon\_address</code>            |
| Marketplace owner                                                                                | <code class="expression">space.vars.marketplace\_production\_owner\_address</code>             |
| Marketplace fee recipient                                                                        | <code class="expression">space.vars.marketplace\_production\_fee\_recipient\_address</code>    |
| Native-deposit helper                                                                            | <code class="expression">space.vars.marketplace\_production\_native\_depositor\_address</code> |

The fee recipient is read from the marketplace; the native-deposit helper is a separately maintained deployment reference. A seller's individual vault is found by calling `vaultFor(owner)` on this deployment's factory. Use the explorer's address search for the address shown above.

Production app:

<code class="expression">space.vars.marketplace\_production\_app\_url + space.vars.marketplace\_collection\_path</code>

Production marketplace API:

<code class="expression">space.vars.marketplace\_production\_api\_url</code>

## Daily onchain settings

Getter values were last read at <code class="expression">space.vars.marketplace\_observed\_at</code>, block <code class="expression">space.vars.marketplace\_observed\_block</code>. These read-only observations refresh daily. Confirm the address and current transaction details in your wallet.

| Setting                       | Observed value                                                                                     |
| ----------------------------- | -------------------------------------------------------------------------------------------------- |
| Trading paused                | <code class="expression">space.vars.marketplace\_production\_paused</code>                         |
| Configured collection allowed | <code class="expression">space.vars.marketplace\_production\_collection\_allowed</code>            |
| Community-discount collection | <code class="expression">space.vars.marketplace\_production\_community\_collection\_address</code> |

## About these values

The production app configuration was checked against the named public production parameters before publication. The address and settings tables follow daily onchain reads. They describe contract configuration at the displayed block, rather than service availability or successful trade execution.

Discount tiers, price increments and other source rules are maintained through reviewed documentation changes. Daily getter reads do not verify deployed bytecode against a source revision.

## Administrative controls and dependencies

The marketplace owner can pause trading, change the base fee and fee recipient, manage allowed collections and payment tokens, set the vault factory, and authorize a marketplace implementation upgrade. The reviewed implementation caps the configured base fee at <code class="expression">space.vars.marketplace\_max\_fee\_bps / 100 + "%"</code>; an implementation upgrade can change contract rules. Factory, registry, helper, and seller-vault beacon upgrades depend on their own ownership. Those owners must be checked separately; the marketplace-owner row is not a claim that one account controls every contract.

Availability also depends on the NFT contract, payment-token behavior, RPC service, and the website's API and indexer. Smart-contract wallets must be able to receive the relevant NFT and payment token. Read [payment recovery](https://docs.rip.xyz/marketplace-guides/payments-and-recovery.md) for the supported failure paths.
