Solutions
Reporting, smart contracts, and on-chain security.
A figure that is nearly right is not right. A contract that usually keeps its balance is not safe to hold funds. Underneath, these are the same engineering problem: a rule that has to hold every time, with evidence a person can read.
Investment reporting
Reports a CFO can trace, figure by figure
Haruno brings a company's QuickBooks Online data together and drafts the statements, the management report and the investor report for a CFO to review. It explains what moved a line by naming the transactions behind it, tracks cash, burn and runway across a portfolio, and analyses actuals against budget and forecast. When an input is missing it names the input instead of estimating around it.
$300 per company, per month
Smart contracts
Money arithmetic that cannot round or wrap
Inference is a programming language for the logic that holds and moves funds. Amounts are integers, overflow stops the program instead of wrapping, and there is no floating point to round a balance. You write the rules a contract must keep, and they are checked against every possible input rather than a sample. It compiles to WebAssembly and deploys on Stellar.
v0.0.6 available now
On-chain finance security
Tools for reviewing the contracts that hold assets
We build and maintain the Stellar Security Portal, a public record of audit reports and vulnerabilities for smart contracts on Stellar. We publish a decompiler that recovers readable Rust from a deployed contract, and we have verified properties of Polkadot's balances module in public. The work is open, including the parts that did not go to plan.
Open source, in a live ecosystem
The method behind all of it
- 01
Write the rule down.
We start from what has to be true, not from the code or the spreadsheet. What must always hold, what must never happen, what a total has to equal.
- 02
Check it mechanically.
A machine checks the rule, not a reviewer's judgement. In Inference the rule is checked against every possible input. In Haruno every figure is traced to the transactions behind it.
- 03
Report the specifics, not a verdict.
A green tick tells you nothing you can act on. We report the input that breaks a rule, the transactions behind a movement, or the piece of data that is missing.
- 04
Keep it checked as things change.
Correctness is not a milestone. The checks run again when the code changes and when new data arrives, not once in a report.
What we will not claim
Inference does not cover floating-point arithmetic or machine-learning models, and we will say so in the first conversation rather than the third. Haruno is not an audit and does not make the judgment calls for you. We do not issue security certificates or stamps of approval, we do not manage money or give investment advice, and we do not take on work we cannot staff properly.
Start a conversation
A figure that is nearly right is not right. A contract that usually keeps its balance is not safe to hold funds. Underneath, these are the same engineering problem: a rule that has to hold every time, with evidence a person can read.