Web3 · Smart Contract Audit

Bitburo Security Audit

softstack completed a smart contract audit of Bitburo's Rebalancer Contract & Keeper in October 2026, reporting 4 findings (1 low and 3 informational), of which 2 were resolved or mitigated before the final report. The full report is published in the softstack public audit archive.

Key facts

Client
Bitburo
Completed
Chains
Base
Languages
Solidity, TypeScript
Commit
b5ed2cb2b42a

About the project

Bitburo is a non-custodial savings application developed by Pinhead B.V. in Eindhoven. It keeps a balance at a fixed split of 80 percent Bitcoin and 20 percent euros, and rebalances when that split drifts, at most once a day. Deposits are in EURC, and the application buys cbBTC through an immutable contract on Base. The user holds the keys, and the application can swap but cannot withdraw.

Scope

Source repositorygithub.com/pinhead-io/bitburo_contracts

Components reviewed

2 modules · 2 files
  1. src/Rebalancer.sol
  2. keeper/keeper.ts

Findings

0Critical
0High
0Medium
1Low
3Informational

2 of 4 findings resolved before the final report.

IDTitleSeverityStatus
6.2.4Availability under oracle/pool divergence is intentionally limited (reverts, never mispriced), verified harmless

Three documented availability edges were re-verified by this audit and confirmed to be revert-only, never lossy: MAX_FEED_AGE of 1500 s allows a feed up to 25 minutes stale, which in a fast market can exceed the ±0.55% execution bound, so…

Informationalacknowledged
6.2.1Chainlink round data is not fully validated: answeredInRound/roundId are ignored for both feeds

_quote() is the single price authority for every run. It discards roundId and answeredInRound from both latestRoundData() calls and validates only answer and updatedAt (and, for the sequencer, startedAt).

Lowmitigated
6.2.2Keeper: a persistent out-of-gas failure is classified as transient ("skipped") and never enters the cool-down ladder; a send exception aborts the remaining…

The keeper sends execute with a fixed GAS_LIMIT (default 500,000). If a transaction reverts on chain because it ran out of that fixed gas (not a contract revert), the post-mortem re-simulation runs via eth_call, which applies no gas cap,…

Informationalmitigated
6.2.3A Circle blacklist of the Rebalancer contract itself permanently halts all runs and freezes collected fees

USDC on Base is a blacklistable FiatToken. The run flow pulls both legs through the contract (safeTransferFrom(owner, address(this), …) for the input; router payout to the contract for the output), so if Circle blacklists the Rebalancer…

Informationalacknowledged

About this engagement

A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.

How softstack runs smart contract audits

Methodology

Review process

  1. Scoping and threat modelling

    The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.

  2. Automated analysis

    Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.

  3. Manual code review

    Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.

  4. Adversarial testing

    Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.

  5. Reporting

    Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.

  6. Remediation verification

    Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.

FAQ

Bitburo was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack completed a smart contract audit for Bitburo in October 2026. The full report is linked on this page and published in the softstack public audit archive.

The review reported 4 findings: 1 low and 3 informational. 2 of 4 were resolved or mitigated before the final report.

2 source files were reviewed in github.com/pinhead-io/bitburo_contracts at commit b5ed2cb. The published report lists every file covered.

This report covers the code as reviewed in October 2026 at commit b5ed2cb. Any code changed after that point is outside the reviewed scope.

Related audits

Browse all security audits

Disclaimer

This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.