import type { Metadata } from "next"; import { PageHero } from "@/components/marketing/page-hero"; import { PlaceholderNotice } from "@/components/marketing/placeholder-notice"; export const metadata: Metadata = { title: "Security", description: "How krypco separates private execution from public verification — honest model, no over-claims.", }; export default function SecurityPage() { return ( <>
Formal audits, bug-bounty programs, and threat-model documents will land as the network hardens. What follows is the architectural intent.

Private layer

Permissioned validators, access control, and confidential payloads. Not everyone can read or write. That is deliberate — commercial and operational data should not be fully public by default.

Public anchors

Cryptographic commitments (for example state roots) are posted to a public chain. Outsiders can verify that an anchor exists and matches expected structure; they do not automatically receive private transaction contents.

What this does not claim

No system is “unhackable.” Relayers, key custody, validator sets, and client software remain attack surfaces. Security maturity tracks implementation, review, and operations — not marketing slogans.

); }