The contracts and supporting application have undergone multiple rounds of in-house security review and testing.
Our September 23 code candidate recorded:
• 280 passing smart-contract tests, including regression and integration checks.
• All 40 server test files passing, plus 3 PostgreSQL tests.
• Four Echidna fuzzing campaigns covering payout and royalty accounting, totaling over 800,000 calls.
• 10 Halmos symbolic checks covering claim authorization and artwork reveal mapping, under documented assumptions and bounds.
• Static analysis using Slither, Semgrep, Aderyn and 4naly3er, with findings reviewed and documented.
• 100% statement, function and line coverage, with 94.44% branch coverage across production contracts.
Earlier work included AI-assisted contract review across 12 specialties, entry-point and code-maturity reviews, and Sepolia mint, reveal, settlement and claim rehearsals.
These are in-house checks, not an independent third-party audit or a guarantee of safety. Historical testnet rehearsals do not establish acceptance of the final release.
We’ve missed so many seasons already.
Let’s focus on the FOMO season now.
Fomies join : https://t.co/qGmJOrPL2n
Fomoater join : https://t.co/VrVLL09nrx
Both projects are looking strong. Try to stay active with these two projects, as they could perform well in the upcoming season.
@BFlTCH You’ve clearly put a lot of work into the engineering side. Curious how you’re approaching early developer adoption once the final release is ready
And which WaaS providers are you guys currently considering?
Hello Ian, I’m Josh.
I took some time to research Okrin and saw that you’re building a global crypto-fiat wallet. I have a few questions about the product and would love to learn more about what you’re building.
Could you follow me back so I can send you a DM? I’d really appreciate it.
@disorderly_AI Really interesting concept.
Quick question, since your AI agents will be interacting with wallets and executing approved work, are you building the wallet/transaction infrastructure in-house or are you considering a WaaS provider for the agent wallet layer?