renatosbispo / blaze-crash-simulator

Collect crash points data from blaze.com's Crash game, define betting strategies and simulate their outcomes.

blaze-crash-simulator

Collect crash points data from blaze.com's Crash game, define betting strategies and simulate their outcomes.

blaze-crash-simulator's Issues

Define the data structures

Crash Point

Definitions (where not self-explanatory):

• crashPoint.isGood: 'good', true if the crash point value is greater than or equal to 2, or 'false' otherwise.

Structure:

crashPoint: {
  isGood: boolean,
  value: number
}

Crash Points History Sample

Definitions (where not self-explanatory):

• crashPointsHistorySample.dataCollectionStartDate / crashPointsHistorySample.dataCollectionEndDate: date objects representing when the sample collection started and when it ended respectively (these values should be useful to estimate the hourly earnings of each strategy according to the simulation ran against this sample).

Structure:

crashPointsHistorySample: {
  id: string,
  dataCollectionStartDate: Date,
  dataCollectionEndDate: Date,
  data: [crashPoint]
}

Betting Strategy Simulation

Definitions (where not self-explanatory):

• Run: a sequence of rounds entered that ends when bettingStrategy.parameters.stopOnProfit or bettingStrategy.parameters.stopOnLoss (see next section) is reached.
• bettingStrategySimulation.results.successRate: a number indicating the percentage of runs that ended because bettingStrategy.parameters.stopOnProfit (see next section) was reached.

Structure:

bettingStrategySimulation: {
  sampleId: string,
  date: string,
  results: {
    profit: number,
    hourlyEarnings: number,
    successRate: number
  }
}

Betting Strategy

Definitions (where not self-explanatory):

• bettingStrategy.parameters.betValue: how much will be bet on each round entered (defined as a percentage of the stopOnLoss value).
• bettingStrategy.parameters.entrySignals: an array of arrays of numbers (zeros and ones) where 0 represents a bad crash point and 1 a good crash point. Each array of zeros and ones represents a sequence of crash points after which a round should be entered.

Structure:

bettingStrategy: {
  id: string,
  name: string,
  creationDate: string,
  parameters: {
    cashoutAt: number,
    stopOnProfit: number,
    stopOnLoss: number,
    betValue: number,
    entrySignals: [[number]],
  },
  simulations: [bettingStrategySimulation]
}

Define the program data directory structure

Location

User's home directory.

Structure

.blaze-crash-simulator
├── crash-points-history-samples.json
└── betting-strategies.json

To do

• Planning
  • Define the program flow
  • Define the project tasks
  • Define the data structures
  • Define the program data directory structure
  • Decide whether the program data should be loaded entirely at once or individually where needed

---

• Main program flow
  • Setup program data directory
  • Initiate sample collection
  • Save sample
  • Ask for strategy
  • Initiate strategy simulation
  • Save strategy
  • Show all strategies with respective simulation results
  • Add option to add new strategy
  • Add option to exit by pressing <Esc>

---

• Crash points sample collection
  • Setup automated browser
  • Collect sample data
  • Build sample structure

---

• Betting strategy simulation
  • Load sample
  • Execute strategy on sample
  • Add simulation results to strategy

---

• Refactoring
  • Create internal lib for dealing with console output

---

• Improvements
  • Simulate existing strategies after new sample collection

Define the program flow

You can edit a copy of this diagram using the tool with which it was created (diagrams.net) by going here and clicking on the edit button at the bottom of page.