# Contract Addresses & Deployment Information

Always ensure you are interacting with the correct network before performing any transactions.

### Parent Contract

The parent contract (Bitsave) is the primary entry point to the protocol. It handles user registration, deploys user-specific child contracts, enforces fees, maintains protocol-wide accounting, and routes calls and funds. It does not act as a long-term custodian of user funds.

| Network             | Address (V1)                                                                                                                              | V2                                                                                                                    |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Base                | [0x3593546078eECD0FFd1c19317f53ee565be6ca13](https://basescan.org/address/0x3593546078eecd0ffd1c19317f53ee565be6ca13)                     | [0x67FFa7a1eb0D05BEaF9dB039c1bD604063040be9](https://basescan.org/address/0x67FFa7a1eb0D05BEaF9dB039c1bD604063040be9) |
| Celo                | [0x7d839923Eb2DAc3A0d1cABb270102E481A208F33](https://celo.blockscout.com/address/0x7d839923Eb2DAc3A0d1cABb270102E481A208F33)              |                                                                                                                       |
| Lisk                | [0x3593546078eECD0FFd1c19317f53ee565be6ca13](https://blockscout.lisk.com/address/0x3593546078eECD0FFd1c19317f53ee565be6ca13)              |                                                                                                                       |
| Avalanche           | [0x7d839923Eb2DAc3A0d1cABb270102E481A208F33](https://snowtrace.io/address/0x7d839923Eb2DAc3A0d1cABb270102E481A208F33/contract/43114/code) |                                                                                                                       |
| Binance Smart Chain | [0x0C4A310695702ed713BCe816786Fcc31C11fe932](https://bscscan.com/address/0x0C4A310695702ed713BCe816786Fcc31C11fe932)                      |                                                                                                                       |
| Hedera              | [0x2f33f1f07f6e56c11fd48a4f3596d9dadfe67409](https://hashscan.io/testnet/contract/0.0.7141595)                                            |                                                                                                                       |

### Child Contracts

Child contracts (ChildBitsave) are deployed dynamically per user at the time of registration. Each user has exactly one child contract, which serves as the sole location where their savings are stored and managed.

Because child contracts are created on demand, there is no single global address for ChildBitsave. Instead:

* Each child contract is permanently mapped to a specific user
* All savings creation, incrementing, and withdrawals occur within the user’s child contract

Only the parent Bitsave contract can call state-changing functions on a child contract

## Supported Tokens/Assets

At the protocol level, BitSave can support any ERC-20 token.

| Network             | Supported Tokens               |
| ------------------- | ------------------------------ |
| Base                | USDC, USDGLO, cNGN             |
| Celo                | USDGLO, GoodDollar, cUSD, USDC |
| Lisk                | USDC.e, cNGN                   |
| Avalanche           | USDC                           |
| Binance Smart Chain | USDC, USDT                     |

ERC-20 savings require prior token approval before funds can be transferred into the protocol.