BinaryOptionRanking symbolBinaryOptionRanking
Stake sizing strategy

D'Alembert Binary Options Strategy: Rules, Example and Risks

A gradual progression concept that increases one unit after loss and decreases one unit after win.

Education only: Strategy content does not provide trade instructions, market-direction recommendations, or profit claims. Test assumptions in a demo account, confirm broker rules, and stop when the setup fails.
D'Alembert Binary Options Strategy: Rules, Example and Risks visual
Pass it on

Share this research

Send the current page without personal or calculator inputs.

Share

More ways to share

Stake sizing framework

How the strategy works

This is a staking progression, not an entry signal or a method for predicting price direction.

D'Alembert increases one unit after a loss and decreases one unit after a win. It feels calmer than martingale because stake growth is slower, but long loss clusters can still create a large exposure trail.

01
Step 1

D'Alembert increases one unit after a loss and decreases one unit after a win. It feels slower than martingale, but long loss clusters still create exposure.

02
Step 2

Compare the maximum and average step size with results from fixed-amount demo testing.

03
Step 3

The broker should allow small amount adjustments and provide a transparent trade history.

Worked example

Use the example only as a planning model. It is not a market-direction recommendation, trade instruction, or profit claim.

RuleLoss +1 unit, win -1 unit
Risk fieldMaximum unit step
ComparisonFlat stake vs progression
Demo validation

Demo testing checklist

The broker should let the user adjust stake in small increments and review history without hiding the sequence path.

Use a paper worksheet or demo account to review the full stake path, payout, reset behavior, and cap breach. Do not treat the result as a threshold for funded trading.

01
Set unit size
02
Cap maximum step
03
Review average step and maximum step after demo
Market and expiry context

When the method can be observed—and when to stop

Market conditions and expiry must be written before a demo observation. They are test controls, not claims that a setup predicts direction.

Observe

Market conditions

D'Alembert has no market-state advantage. A fixed demo setup and stable payout are needed only to measure how the unit ladder behaves across wins and losses.

Skip

Do not test when

Stop when the next unit increase breaches the cap, contract terms change, an order is missing from history, or the session loss limit is reached even if the progression calls for another step.

Duration

Why expiry matters

Use one non-overlapping expiry across the worksheet. Rapid expiries can hide accumulated exposure behind frequent small adjustments, while changing durations prevents a fair flat-stake comparison.

Definitions used here

Key terms for this page

Open a definition when a broker uses the same label differently or leaves a condition unclear.

01
Payout rate

The percentage return displayed for a contract before confirmation, subject to product and account conditions.

02
Expected value

The probability-weighted average net result under stated win, loss, refund, and payout assumptions. A high payout alone does not establish positive expected value.

03
Loss limit

A voluntary or platform-enforced cap on losses over a session, day, week, or other period. Check how it is calculated and changed.

04
Full-loss settlement

The losing outcome returns none of the contract stake. It exposes the downside behind a headline payout.

Calculated example

Work through the assumptions

Input
Base unit 1; Loss, Loss, Win, Loss; stakes 1, 2, 3, 2; payout 80%
Math
Net result = -1 - 2 + (3 × 0.80) - 2
Result
-2.60 units
Study protocol

What to model before testing

D'Alembert changes stake by one unit after a loss or win. Slower growth does not remove sequence risk, especially when a payout below 100% makes recovery incomplete.

01
Record 1

Base unit and maximum unit step

02
Record 2

Average and maximum step reached in the demo sample

03
Record 3

Flat-stake result beside the progression result

Review metrics

Measure the process, not the story

Confirm that the product is available for the intended user and that the exact operating entity and domain can be verified before any demo study. Define net payout b, assumed win probability p, and full-loss result -1 explicitly. The simple expected value per unit is b × p - (1 - p), and break-even is 1 / (1 + b).

01
Cluster exposure

After k consecutive losses, the classical unit sequence produces cumulative stake k(k+1)/2 and next stake k+1.

02
Average and maximum stake

Report both measures because gradual escalation can hide sustained time above the base unit.

03
Drawdown and recovery length

Count the wins needed to return to base and whether sub-100% payouts leave a cash deficit.

04
Flat-stake difference

Compare the same outcomes without result-driven stake changes.

Platform requirements

What this strategy needs from a broker

For D'Alembert testing, check unit-step visibility, maximum exposure, and whether flat-stake results are easier to assess than progression results.

Check that the platform clearly shows the required contract, expiry, payout, order controls, and demo history before testing the method.

Sources

Sources and assumptions

These references support definitions, payout math, uncertainty, and market context. They do not prove that a strategy is profitable.

01
CFTC

Binary Options Fraud resources: platform, solicitation, registration, and payout-risk context. This source does not validate a strategy.

Open source
02
Investor.gov

Binary Options Fraud: withdrawal, identity, software-manipulation, and return-claim warnings.

Open source
03
Calculation policy

Worked examples use stated assumptions, actual payout fields, complete result paths, and explicit stop conditions. They are not performance claims.

Open source

Failure conditions

Avoid assuming gradual progression is safe. A slow progression can still become unsuitable if payout is below 100% or the losing run is long.

Test

Set a maximum unit step

Test

Stop after a predefined drawdown

Test

Compare flat-stake results against progression results