blockchain/apps/portal/app/(marketing)/security/page.tsx

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 (
    <>
      <PageHero
        eyebrow="Security"
        title="What is private. What is proven."
        description="This page describes the intended hybrid security model. It is not a completed audit report or a guarantee against all risk."
      />

      <section className="section-pad">
        <div className="mx-auto max-w-3xl space-y-10 px-5 lg:px-8">
          <PlaceholderNotice>
            Formal audits, bug-bounty programs, and threat-model documents will
            land as the network hardens. What follows is the architectural
            intent.
          </PlaceholderNotice>

          <div>
            <h2 className="font-display text-2xl font-semibold tracking-tight">
              Private layer
            </h2>
            <p className="mt-3 text-sm leading-relaxed text-muted-foreground sm:text-base">
              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.
            </p>
          </div>

          <div>
            <h2 className="font-display text-2xl font-semibold tracking-tight">
              Public anchors
            </h2>
            <p className="mt-3 text-sm leading-relaxed text-muted-foreground sm:text-base">
              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.
            </p>
          </div>

          <div>
            <h2 className="font-display text-2xl font-semibold tracking-tight">
              What this does not claim
            </h2>
            <p className="mt-3 text-sm leading-relaxed text-muted-foreground sm:text-base">
              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.
            </p>
          </div>
        </div>
      </section>
    </>
  );
}