← All strategies
Orestack

Shadow

Late in the round, match a percentage of each occupied tile’s current SOL. You pick how many solo and split tiles. Skips a quiet board. Volume-share, not EV. Type 2 mode 9.

What it does

Shadow waits until late, looks at tiles that already have SOL, and deploys a percentage of each occupied tile’s current stake — walking the board until your bankroll cap is spent. Empty tiles are skipped. This is volume-share mirroring, not an EV ranker.

In plain english

Follow occupied tiles at a fraction of their size. Quiet boards → sit out. Busy boards → shadow the crowd up to your cap.

Not the retired Percentage strategy

Older docs described Shadow as retired on-chain type 1 / type 4. The live picker Shadow is Type 2 manual mode 9. Ignore any “Shadow is retired” banner on old copies of this page.

Settings

Bankroll cap

Maximum SOL this miner spends matching occupied tiles in a round. Clamped to your on-chain balance.

Solo tiles / Split tiles

How many of the most-crowded solo (0–10) and split (0–15) tiles to take. Default 10 / 15 (all).

Match occupancy

Deploy this share of each occupied tile’s current SOL. Example: 5% means roughly amount = P × T / (10000 − P) on each occupied tile until the bankroll cap is hit.

Occupied tile stake: 1.0000 SOL
Match occupancy: 5%
Shadow adds about: ~0.0526 SOL
Empty tiles: skipped
Starting recommendation

Start with match occupancy around 5%, defaults 10 / 15, and a bankroll cap you are willing to spend on a busy board.

Gates

Optional skip gates in the strategy picker (off by default). They do not change tiles or amounts — only whether this round fires.

How to set up

  1. Connect your Solana wallet on the Mining page.
  2. Create a miner and choose Shadow in the strategy picker. Set bankroll cap, solo/split counts, and match-occupancy %.
  3. Sign the transaction. This creates your miner accounts on-chain (Manager + Strategy Deployer + ORE Miner). Cost ≈ 0.005 SOL (account setup).
  4. Deposit SOL. Transfer SOL into your miner’s autodeploy balance. Minimum 0.03 SOL; 0.3 SOL or more gives runway for many rounds.
  5. Done. The crank runs this strategy each round. Activity shows deploys and skip reasons.

When it skips a round

Things to know

Worked example

Late occupancy match: take a % of each occupied tile’s SOL until the bankroll cap is spent.

A · Config
StrategyShadow (Type 2 / mode 9)
Bankroll cap0.2000 SOL
Solo / split10 / 15
Match occupancy5%
Motherlode range gateoff
B · Algorithm thinking
TilePoolT (SOL)Match 5%Spend
7split1.20000.06320.0632
11split0.90000.04740.1106
3solo0.80000.04210.1527
14solo0.60000.03160.1843
22split0.50000.0263cap → 0.2000
Empty tiles—skipped
DecisionFIRE
C · Activity log
RoundR372106
Line 1Sent 0.2000 SOL
StatusDeploy settled
D · Results
Returned SOL+0.1782 SOL
ORE earned+0.0015 ORE
BadgesWON
Sessionsvolume-share · cap 0.2000

Activity (C) and Results (D) match what you see in the Mining Activity / Sessions panels. Thinking (B) illustrates what the crank evaluates that round — only EV Gate has a live Strategy Insight table in-app.

Skip variant (same config)

When the late board has no occupied tiles to mirror, Shadow sits out — empty tiles alone never trigger a deploy.

B · Algorithm thinking
CheckValueOutcome
Occupied tiles0none
Match occupancy5%n/a
Spendable0.0000 SOLempty plan
DecisionSKIPno_eligible_squares
C · Activity log
RoundR372116
Line 1SKIPPED
ReasonNo occupied tiles to match
D · Results
Deployed0.0000 SOL
ORE earned+0.0000 ORE
Badges—
Sessionsround skipped

Skip variant (Crowded-round skip gate on)

With Crowded-round skip gate enabled, occupancy matching never starts when recent network deploy averages above your cap.

B · Algorithm thinking
CheckValueOutcome
Crowded-roundavg 1.8000 > cap 1.0000FAIL
Occupancy matchnot started—
DecisionSKIPrecent_deployment_cap
C · Activity log
RoundR372205
Line 1SKIPPED
ReasonCrowded-round skip: recent deploys above your cap.
D · Results
Deployed0.0000 SOL
ORE earned+0.0000 ORE
Badges—
Sessionsround skipped

Skip variant (Motherlode range gate on)

With Motherlode range enabled, occupancy matching never starts when the live pool is outside your min/max.

B · Algorithm thinking
CheckValueOutcome
Live motherlode0.1200 OREbelow min
Your range0.2500–2.0000 ORE0.12 < 0.25
Occupancy matchnot started—
DecisionSKIPmotherlode_range
C · Activity log
RoundR372128
Line 1SKIPPED
ReasonMotherlode outside your min/max.
D · Results
Deployed0.0000 SOL
ORE earned+0.0000 ORE
Badges—
Sessionsround skipped