# ETH

Catcoin Token - <https://etherscan.io/token/0xd4b92b1700615afae333b9d16d28eb55e8e689b8>

Marketing Wallet (Multisignature) - <https://etherscan.io/tokenholdings?a=0x8553a1ed5c71d6223b5854077a8eca8e4d01b44f>

Development Wallet 1 (Multisignature) - <https://etherscan.io/tokenholdings?a=0xAF7AF776fd141d8A58708C7FB2EcaE26b6CE2203>

Development Wallet 2 (Multisignature) - <https://etherscan.io/tokenholdings?a=0x1F2BDe4F663f642f3a02DC952147c45D69217799>

Deployer Wallet - <https://etherscan.io/tokenholdings?a=0x3f99d16166948455329f96E97369A77DdCf31a2E>

## What is MultiSig?

Most crypto users for example those who own ETH or BNB are used to a single key wallet, often referred to as an externally owned account (EOA). Examples include; MetaMask, Trustwallet, Exodus etc. These accounts are secured with 12 word “seed phrase”, which can be transformed into a private key for the user. If that private key is compromised in any way, the funds can be stolen.

If your project comprises of more than 1 person, an externally owned account is not a secure way to manage your business’s crypto funds If an employee goes rogue or is careless with the private key, the funds are gone forever. Even if your business is made up of just yourself, I’d argue it’s still a poor way to manage funds. So, what is the better solution?

Enter the Multisig. Safe is a smart contract wallet running on a number of blockchains that requires a minimum number of people to approve a transaction before it can occur (M-of-N). If for example you have 3 main stakeholders in your business, you are able to set up the wallet to require approval from 2 out of 3 (2/3) or all 3 people before the transaction is sent. This assures that no single person could compromise the funds.

Catcoin have 5 people from Core who manage with safe care about community funds.

On top of that, Safe gives you complete self custody over your funds. There is no risk of a bank giving you a hassle for running a crypto business and the smart contract that is deployed is completely trustless and in your control.

Here's an overview, comparing the Safe to other digital asset storage solutions:

![](/files/IugGAN1YjawnvaXcpRWT)

## Supported Networks

The canonical versions of the Safe smart contracts are deployed to many networks including:

* Ethereum Mainnet (Etherscan provides a good overview [here](https://etherscan.io/accounts/label/gnosis-safe).)
* Ethereum Testnets: Rinkeby, Kovan, Ropsten, Görli
* Arbitrum
* Aurora
* Avalanche
* Binance Smart Chain
* Gnosis Chain (formerly xDai)
* Optimism
* Polygon

The full list with all the addresses can be found in the [Safe deployments](https://github.com/gnosis/safe-deployments) repository on Github (e.g. for [v.1.3.0](https://github.com/gnosis/safe-deployments/tree/main/src/assets/v1.3.0)).

To deploy the Safe contracts version 1.3.0 on another EVM-based chain, follow the instructions in the [safe-contracts repository](https://github.com/gnosis/safe-contracts/blob/v1.3.0/README.md#custom-networks). *Please note: The chain needs to be fully compatible, i.e. support all opcodes used by the Safe contracts.*

In order to run the [Safe Web interface](https://docs.gnosis.io/safe/docs/contracts_other_evm/gnosis-safe.io/app/) ([Code](https://github.com/gnosis/safe-react/)), you would need to also run the backend services, in particular the [Safe client gateway](https://github.com/gnosis/safe-client-gateway/) and the [Safe transaction service](https://github.com/gnosis/safe-transaction-service) including a tracing node (see [Service Architecture](https://help.gnosis-safe.io/infrastructure/service-architecture)).

The Safe team does not have the capacity to spin up and maintain full frontend and backend support for all EVM-based networks. All Safe related source code is open source. We encourage everyone to [deploy the canonical versions](https://github.com/gnosis/safe-contracts/blob/v1.3.0/README.md#custom-networks) of the Safe contracts to their respective networks and run the required backend and frontend parts themselves.

To add another supported network to the [safe-deployments repository](https://github.com/gnosis/safe-deployments) follow the steps outlined in the [safe-contracts repository](https://github.com/gnosis/safe-contracts/blob/v1.3.0/README.md#deployments).

Please let know about any questions via Safe [Discord](https://chat.safe.global/).

## Catcoin Github repositories

<table><thead><tr><th>Project</th><th>GitHub</th><th data-hidden></th></tr></thead><tbody><tr><td>Catcoin Token</td><td><a href="https://github.com/Catcoin-Official/catcoin-token">https://github.com/Catcoin-Official/catcoin-token</a></td><td></td></tr><tr><td>Audit</td><td><a href="https://github.com/Catcoin-Official/Audit">https://github.com/Catcoin-Official/Audit</a></td><td></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.catcoin.io/whitepaper/developers/deployed-contracts/eth.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
