Introduction

What is BitSave?

BitSave is a non-custodial, on-chain savings protocol that enables users to create time-locked stablecoin savings positions secured entirely by smart contracts. Instead of relying on pooled vaults or custodial intermediaries, BitSave assigns each user a dedicated savings contract, ensuring that funds are isolated at the contract level and never commingled with other users’ assets.

The protocol is built around a parent–child contract architecture, where a lightweight parent contract coordinates user registration and routing, while each user’s funds and savings metadata are held in their own child contract. This design minimises systemic custody risk, simplifies accounting, and provides a predictable savings lifecycle enforced directly on-chain.

BitSave is designed for users who want a transparent, programmable alternative to traditional savings, without giving up control of their funds or relying on off-chain trust assumptions.

Why BitSave Exists

Most on-chain savings and yield products rely on pooled custody models, where multiple users deposit funds into a shared vault. While efficient, this approach introduces systemic risks: funds are commingled, accounting becomes complex, and a single failure can affect all users simultaneously.

BitSave exists to offer an approach: isolated savings by default.

By giving each user their own savings contract, BitSave:

• Eliminates fund commingling

• Reduces blast radius in the event of failures

• Makes savings behaviour easier to reason about and audit

• Preserves user sovereignty over funds throughout the savings lifecycle

The protocol also introduces time locks and optional early withdrawal penalties to encourage disciplined, long-term saving behaviour without removing the user’s ability to exit when needed.

In short, BitSave exists to make on-chain savings safer, simpler, and more predictable, especially for users who value capital preservation over complex yield strategies.

Target Users

BitSave is designed to serve multiple audiences within the on-chain ecosystem:

Individual Savers

Users who want to save stablecoins on-chain in a non-custodial and transparent way. These users may be:

• Saving toward specific goals

• Looking for time-locked discipline mechanisms

• Seeking an alternative to custodial savings platforms

Advanced DeFi Participants

Users who care about:

• Contract-level fund isolation

• Explicit custody guarantees

• Predictable withdrawal behaviour

• Manual interaction via block explorers when needed

Developers and Integrators

Developers building wallets, dashboards, or financial applications who want to:

• Integrate a savings primitive without managing pooled custody

• Rely on a clear and deterministic contract architecture

• Build savings experiences on top of BitSave’s parent–child model

How It Works

At a high level, BitSave operates through a parent–child smart contract system.

1. User Registration

A user registers through the Bitsave parent contract. During registration, a unique ChildBitsave contract is deployed and permanently mapped to the user’s address.

1. Savings Creation

When a user creates a savings position, funds are transferred to the parent contract and immediately forwarded to the user’s child contract in the same operation.

Each savings record:

• Principal amount

• Maturity time

• Penalty parameters (if applicable)

Protocol Fees

BitSave applies protocol-level fees during user registration and savings creation.

A $1 registration fee is charged once, when a user first registers with the protocol.

A $1 savings creation fee is charged each time a new savings plan is created.

Fees are deducted in native network ETH and enforced by the parent Bitsave contract as part of the execution flow.

1. Fund Custody

Once created, funds reside entirely in the user’s ChildBitsave contract. There is no shared vault and no pooled liquidity. Each child contract is a self-contained savings environment.

1. Savings Management

Users can create multiple savings or increment existing ones, all within their single child contract.

1. Withdrawal

Withdrawals are executed directly from the child contract back to the user:

• Early withdrawals apply the configured penalty

• Withdrawals at or after maturity return the full principal

Throughout the entire lifecycle, the parent contract acts only as a coordinator and router, while custody and savings state remain localised to the user’s child contract.