Quick reference to Seed Cycle Proofs

November 5th, 2024 - Verification Proof For Seed Cycle #2

Games 200,001-500,000

https://jsfiddle.net/deca506/k4vdop8u/2/

Full Write Up @

BlastCrash Provably Fair Seed Cycle #2


September 10th, 2024 - Verification Proof For Seed Cycle #1

Games 1-200,000

https://jsfiddle.net/deca506/zy3uckv2/

Client Seed for Cycle #1 Generated @—> https://blastscan.io/tx/0xcbf3ac6399cab1d7b17895e8787658ea93bab67086a2701f29961147343b5aab#eventlog


Blast Crash Provably Fair Seed Cycle’s Explained

This post will explain how the BlastCrash provably fair system works. The goal of this system is to prove, without a doubt, that the crash points used for our game are selected fairly. More specifically, we must prove that no one (the house or anyone else) has influenced the crash point selection to numbers that would benefit them.

Overview

In case you’ve done this kind of thing before, our provably fair system is based off the original BustaBit system in which we select and commit to a series of games where the crash points are derived from a secret Server Seed.

The hashes from the Server Seed chain are then salted with a Client Seed that has been generated independent of the house. While those fundamental components are the same as the traditional BaB crash game seeding, we have made some changes to the system that allows us to be more nimble and secure.