Contract Addresses & Deployment Information

This section provides all deployed contract addresses for reference for the BitSave Protocol.

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
Base	0x3593546078eECD0FFd1c19317f53ee565be6ca13
Celo	0x7d839923Eb2DAc3A0d1cABb270102E481A208F33
Lisk	0x3593546078eECD0FFd1c19317f53ee565be6ca13

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
Celo	USDGLO, GoodDollar, cUSD, USDC
Lisk	USDC.e

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