CrossBar Ostros · Security

Tell us what you found.

We read every report and reply within five working days.

Write to security@crossbar-inc.com.

Tell us what you found, how to reproduce it, and which layer it sits in. A short proof of concept helps more than a long description.

In scope: everything we publish and ship.

The chip's compute logic, the bao1x boot chain and drivers, Xous and its services, the app framework, the Ethereum signer, the web signer, the firmware images we publish, and the Founders Edition hardware. Reports about third-party sites, phishing that imitates us, or social engineering of our staff are welcome too, at the same address.

Give us ninety days before you publish.

We confirm receipt within five working days, tell you what we think the issue is and when we expect to fix it, and credit you in the published firmware notes and on this page unless you ask us not to. After ninety days, or earlier if the fix has shipped, publish what you like. We do not take legal action against good-faith research on our published stack or on a unit you own.

Found something on the chip itself?

Issues in the Daric compute logic, published as Baochip-1x, are shared with Baochip, who maintain the design. If your finding concerns the closed blocks (bus fabric, USB PHY, PLL, regulators, pads) or the package, tell us anyway; we route it to the right team and tell you who has it.

Rewards

Every confirmed finding gets credit here and in the firmware notes. A paid programme with published scope and amounts opens later.

Acknowledgements

This list starts with the first confirmed report.

Verify it's us

We message you only after you apply or write to us, and we quote the e-mail address you used. We never ask for seed phrases or PINs. Staff never message you first on Discord.

Questions first?

Ask in the Discord server, read how to verify a unit, or open an issue on GitHub for anything that is not a security matter.