News · Learn · November 8, 2026
Security and audits: what is done, what is pending
CertiK completed a security audit of DRIVE369 in 2025. The Ghostdrive contracts have an audit pending, and audits continue in public until mainnet.
DRIVE 369 DAO
Trust in a network that holds your memory should rest on checks you can read, not on promises. This is where the security work stands today, and how we will keep it public.
Done
A CertiK security audit of the DRIVE369 project was completed, with its final report delivered on 5 September 2025. CertiK's public profile lists the audit as completed and the report as not disclosed: DRIVE369 on CertiK Skynet. The scores on that page are CertiK's monitoring data. They are not a guarantee.
Pending
The contracts that run on the Base Sepolia testnet today have an audit pending: the storage market, the registry anchor, the mining vaults, the staking vault, and the DAO's kernel board and governor. Until that audit is done we say so everywhere, next to every testnet feature. Test DRIVE has no value, and none of these contracts is on mainnet.
What happens until March
Security work continues until mainnet, which is planned for March 6, 2027, and only after an external audit. We keep that work public:
- reports, findings and fixes are published as they land, here on News and in the project's repository;
- a finding that says wait means we wait, and the date moves;
- our own reviews run in parallel with the external ones, and what they find is fixed through pull requests.
What an audit does and does not do
An audit is a careful look at the code at one point in time. It lowers risk. It does not remove it, and code written after it is not covered by it. That is why the new contracts get their own audit, and why we label testnet features until they have one.
Help us find problems
Accepted bug reports earn testnet points, because finding a flaw before mainnet is work worth paying for. Join the testnet, read the code and tell us what you find.