Specification and code
Describe intended behavior and whether an implementation follows the specification.
External research
Sources explain methods; they do not replace implementation or audit evidence
The protocols and papers listed here illustrate recurring privacy-system questions. They do not mean HUNCHI.CASH copies the same mechanism or inherits another project’s security conclusions.
Public linkage
A privacy system must first define what an observer can see
Public chains do not erase history. Privacy designs commonly reduce direct linkage by enlarging anonymity sets, separating bearer authority from output, and avoiding predictable timing and amount patterns.
Those principles establish direction only. Real security depends on the state machine, keys, exception handling, privilege isolation, testing, and independent review.
Evidence boundary
Code, runtime state, and independent conclusions are different evidence
Runtime evidence
Shows whether production state, configuration, recovery, and access boundaries actually operate.
Independent review
Provides an external conclusion for a defined scope and version. One layer cannot substitute for another.
FAQ
Frequently asked questions
Does an audit of an external protocol prove HUNCHI.CASH is safe?
No. Dependency versions, composition, business state, and runtime environments differ, so an external audit does not automatically cover HUNCHI.CASH.
Does this page make an operational promise?
No. It explains public-domain methods and evidence boundaries; external material is not proof of this service implementation, audit, or security.