Back to collectionHorizen’s selective privacy keeps familiar tools but changes testing
Confidential application state needs explicit reveal, documentation and recovery behavior.
Horizen’s builder invitation proposes selective confidentiality within familiar smart-contract tools, alongside documentation designed for AI-assisted development. The product choice is which state stays private, who may reveal it and what evidence is available in a dispute. Public ownership and private strategy can coexist, but indexing, support and analytics must respect that split. Machine-readable guidance also needs accurate versions and parameters so generated code preserves the intended property. Missing keys, failed reveals and proving a result without exposing its underlying record belong in the test plan, even when the development tools themselves remain familiar.