Sealed deck windows
The deck is committed and released through protocol-bound stages instead of a generic black-box shuffle claim.
Technical Brief
Poker-specific verification, not generic RNG theater.
The investor technical brief should explain PFP-v3, sealed windows, signed releases, privacy-safe verification, self-verify, attestation posture, and proof artifacts without becoming an operations runbook.
TEE BoundaryAttestation lane
ProtocolPFP-v3
PrivacyRedacted proof
AttestationTEE posture
StatusProvisional filed
AlgorithmLive
pfp-v3
The SNARK package identifies the hidden-consistency circuit as PFP-v3 Noir UltraHonk 1.0.0.
Runtime boundaryDiligence
Nitro Enclave
Docs describe enclave-local fairness signer identity and KMS attestation-aware policy gates.
Parent hostDiligence
No signer key
The architecture states the parent EC2 proxy should not hold the fairness signing key.
Rollout evidenceDiligence
Open items
PCR snapshots, policy hashes, and attestation-chain validation remain diligence artifacts.
Moat Detail
A moat investors can inspect.
The technical brief should make the diligence path obvious without giving away sensitive operational internals.
The strongest investor story is specific: Flux is solving poker's hidden-information trust problem.
The public technical page should be credible and bounded. It should tell investors what exists, what to request, and what not to overclaim.
Any future updates should separate live production facts, private diligence facts, and planned roadmap items.
Architecture Lines
What can be verified, attested, and reviewed.
Signed release layer
Each reveal can be tied to a signed chain of custody for completed-hand inspection.
Privacy boundary
Public proof must not disclose folded cards or private strategy that poker depends on.
Diligence posture
The public page should point to deeper artifacts instead of exposing sensitive implementation details.
Technical Packet
Verified versus attested
The technical brief separates browser-checkable proof from infrastructure claims that belong in diligence.
05Artifacts to prepare
01Protocol diagrams
02Attestation explanation
03Verification sample
04Security review scope
05Patent posture memo