Schedule lock
The table, seats, dealer, dealing order, and branch eligibility are bound before deck sealing.
Technical Brief
PFP-v3 is built for poker, not generic randomness.
Flux's technical trust stack combines a PFP-v3 street-locked ladder, deterministic deck sealing, signed releases, redacted verification, TEE hidden-hand verdicts, Noir / UltraHonk hidden-card consistency proof, and seat-owner self-verify.
TEE BoundaryAttestation lane
ProtocolPFP-v3
PrivacyRedacted mode
AttestationTEE verdict
IP2 provisionals
Proof circuitDiligence
Noir
The hidden-consistency circuit is designed for browser-verifiable proof using Barretenberg UltraHonk.
SNARK rolloutDiligence
Staged
The technical brief separates legacy binding, shadow generation, and enforced verification paths.
Runtime boundaryDiligence
Nitro/KMS
The architecture separates browser-verifiable cryptography from Nitro and KMS attestation evidence.
Admin boundaryDiligence
No open reveal
The product design does not expose a normal admin path to pull another player's folded cards.
Moat Detail
The moat is inspectable.
A qualified technical investor can move from public thesis to proof artifacts, test coverage, patent posture, and deployment evidence.
The strongest technical claim is not that Flux uses cryptography. It is that the cryptography is mapped to poker's real failure modes: timing, hidden state, absent contributions, folded cards, and historical edits.
The public page can be specific without exposing an operations runbook. Investors get the artifact chain first, then request the deeper packet for manifests, test evidence, attestation detail, and rollout controls.
This is the difference between an RNG badge and a trust architecture. Flux makes the deal story reviewable as a sequence of artifacts.
Architecture Lines
What can be verified, attested, reviewed, and scoped.
Deterministic shuffle
The combined seed drives Fisher-Yates with rejection sampling so the sealed deck can be replayed without modulo bias.
Signed custody chain
Release packages, transcript roots, and service identity make the completed-hand record reviewable.
Audience-safe verification
Full public replay and redacted attested verification are different public contracts from the same fairness engine.
Proof Boundary
Separate what the browser can verify from what infrastructure attests.
Flux separates browser-verifiable evidence, privacy proofs, and infrastructure attestation so diligence can review each trust boundary clearly.
BrowserDeterministic replay
Commitments, signatures, transcript root, table ratchet, and street releases.
PrivacyHidden-card consistency
Noir / UltraHonk proof lane for redacted completed-hand verification.
TEEAttested execution
Infrastructure verdicts are presented as a distinct review surface.
OwnerSeat self-verify
Seat-owner material lets a player verify the cards only they were allowed to see.
Technical Packet
Verified versus attested
The technical brief separates browser-checkable proof, privacy evidence, and attestation boundaries for review.
05Technical packet contents
01PFP-v3 artifact map
02Redacted proof contract
03TEE verdict posture
04Noir / UltraHonk proof path
05Patent and rollout memo