Trust, with the
evidence attached.
A technical view of how STAKYRA records Play and Cash Out events using its local SDDT verification layer. No broader claim is made here than the evidence supports.
Loading status
Reading the public status endpoint. We never infer availability when the endpoint is unavailable.
What is happening now
Latest anonymized events
Round identifiers onlyFrom event to decision
The local layer validates the structure of an event, normalizes its payload, creates a record identifier, and stores a SHA-256 payload hash alongside the result.
What a record contains
The local validator stores the fields returned by its API. Live player records and synthetic demonstration records remain separate.
verified_local from the local adapter.Downloadable records
Open a permitted verification record to download its PDF certificate. The certificate describes local evidence; it is not an external attestation.
View records →What this proves
Checking local policy status…
- Required event fields were checked locally.
- A normalized payload was hashed and stored.
- Demonstration records are stored separately from real game actions.
Separate layers, separate claims.
STAKYRA game engine runs the live round and payout workflow. SDDT local verification records structural evidence for Play and Cash Out actions.
Round fairness is documented separately through the Provably Fair details on the Play page. This Trust Center does not certify fairness.
Verification records
Precise by design.
STAKYRA uses a local SDDT-style implementation. It is not connected to an external SDDT API, and this implementation is not externally attested.
There is no independent fairness certification in this layer. “Verified locally” means the STAKYRA server validated and stored the event structure and hash evidence described above.