How to read the Stake game data
This profile connects Stake's captured Plinko table with the tools and replay evidence available on ProvablyHero. The current table version is 2026-10-20, recorded as checked on 2026-10-20. That date identifies the snapshot used for calculations; it is not a guarantee that every live configuration remains unchanged.
The replay evidence label for the supported Plinko adapter is reference. Table capture and replay status answer different questions. The table supports calculations about payouts, while the adapter supports reconstructing outcomes under its stated algorithm and mode. Neither is an overall rating of the operator.
Stake reference implementation and historical evidence
The Stake Plinko adapter implements the published HMAC-SHA256 scheme and converts four-byte groups into directions. Its replay tests include historical community examples, but those reports were not independently captured by ProvablyHero and lack recorded pre-bet commitments. The adapter therefore remains Reference, rather than inheriting Verified status from a matching published example.
The captured payout tables are separate evidence from those historical paths. The source preserves the API's risk names, which may differ from interface labels. A multiplier lookup in the current captured snapshot does not establish the table used for an older bet or confirm real-money settlement.
| Record | Match against | Why |
|---|---|---|
| Board size | 8, 9, 10, 11, 12, 13, 14, 15, 16 rows | Use a configuration actually present in this snapshot. |
| Risk label | low, medium, high, expert | Operator-specific labels are not interchangeable. |
| Table record | 2026-10-20, checked 2026-10-20 | A source date is not a guarantee that the live game is unchanged. |
Use a complete configuration for calculations
Select a row count and one of the provider's captured risk settings before comparing RTP or target-payout probability. The displayed RTP range combines different configurations; its endpoints should not be interpreted as uncertainty around one selected setting. The multiplier explorer shows each table and its source context.
For a session question, keep bet size and starting bankroll consistent and run the simulator. A larger stake relative to the bankroll can stop a session quickly even when its table is unchanged. The comparison helps separate table differences from settings introduced by the user.
Replay evidence is not an account-service review
The profile reports recorded availability rules, which can change and may depend on location or specific conditions. A mathematical check does not assess deposits, withdrawals, licensing or customer support. Refer to the applicable operator terms for account and regional questions rather than interpreting an adapter label as permission to use a service.
Open the Stake Plinko verifier for supported inputs and limitations. Read the methodology for evidence standards and affiliate disclosure for the role of outbound operator links. A commission does not change the captured payout table or the engine's calculation.