Activity

Sent first. Failed only when it is real.

When Orestack submits a strategy deploy for your miner, Activity shows Sent right away. The SOL amount may be blank for a moment. If that same transaction later fails on-chain, the same line becomes Failed. You should never see a false Deploy Failed that later flips to Sent.

What you see on Activity

The Activity list on /mine is tied to your miner’s Auth PDA — the public address shown on the page. Each deploy is one row for one transaction.

The one-sentence rule

Submitted → Sent right away. Confirmed → that same Sent line fills in the SOL amount. Real failure → that same line becomes Failed (amount cleared). Waiting a bit longer for confirmation does not mean Failed.

The flow, in order

One row the whole way. Nothing is created, deleted, then recreated.

Deploy submitted

Orestack sends your strategy deploy for the round. The transaction has a signature as soon as it is submitted.

Sent — immediately

That deploy appears in Activity as Sent. The amount may stay empty until the network confirms how much SOL was spent on tiles.

Confirmed

Same Sent row fills in

When the transaction lands, the SOL amount appears on that Sent line. If a retry in the same round is what actually spends, that successful spend is the one you keep.

Did not land

Same row becomes Failed

If the transaction reverts, never lands, or expires, that same line turns Failed and the amount is cleared. No Failed→Sent flash.

⏱

Still confirming is not Failed

A deploy can sit as Sent for a short time while the network finishes confirming it. Activity does not mark Failed just because confirmation took longer than usual.

What each status means

Sent with no amount yet — normal. The deploy was just submitted; spend is measured after it lands.
Sent with an amount — the transaction confirmed and the tile SOL is known.
Failed — that exact transaction did not succeed on-chain. Not “still processing.”
Same-round retries — if a later retry in the same round lands, the successful spend is the one that remains. Duplicate same-round rows collapse to the spend that counted.

Before vs after

Previously, a deploy that was still settling could briefly show as Failed, then flip to Sent once it confirmed. That flash is gone: Sent comes first, and Failed only replaces that same line when the transaction truly does not land.

Moment	Before	Now
Deploy is submitted	Often Deploy Failed first	Sent immediately (amount maybe empty)
Still settling on the network	Could look like a failure	Still Sent — not a failure
Transaction confirms	Failed row flips to Sent	Same Sent row fills in the amount
Transaction reverts or expires	Failed (sometimes after a false Failed already)	That same Sent row becomes Failed
Confirmation takes longer than usual	Could look like a fail	Stays Sent until it confirms or truly fails