Sensitive scope?
Email before sharing confidential code. NDA and publication expectations should be agreed before kickoff.
contact@taichiaudit.com Review services first
Audit intake
Tell us what needs to survive production.
Share enough context to understand the system, the risk, and the schedule. We normally reply with fit, availability, and next steps within 24–48 hours.
Scope checklist
The inputs behind an accurate proposal.
You do not need a polished document. Links and concise notes are enough if they make the review surface and deadline clear.
- 01
Repository or representative code and target commit
- 02
Target chain, language, framework, and deployment status
- 03
Architecture notes and the invariants the system must preserve
- 04
External protocols, tokens, or proof systems in scope
- 05
Approximate code-freeze, remediation, and launch dates
- 06
Known concerns, prior reviews, and confidentiality needs
After submission
No black-box handoff.
An audit request starts a scoping conversation. It does not commit either team until scope and terms are agreed.
- 01
We review the brief
We check technical fit, scope clarity, schedule, and which researchers should evaluate the system.
- 02
We close scope gaps
If key inputs are missing, we ask focused questions before estimating cost or review time.
- 03
You receive a proposal
The proposal defines target code, coverage, staffing, schedule, remediation window, and commercial terms.
Time-sensitive question?
Use the direct Telegram channel for a launch-critical timing question. Availability is still confirmed after scope review.
Open TelegramStill evaluating fit?
Review the engagement model, deliverables, preparation checklist, and FAQ before sending a repository.
Read audit servicesIntake open
Ready to make the scope concrete?
Send the checklist items by email. If the scope is sensitive, contact us first and agree the confidentiality process before sharing code.
Email the audit scope