Bitwork estimator

Bitwork estimator

Probabilistic. Not a schedule

Prefix Hexadecimal characters only. Each additional character multiplies the expected attempts by sixteen.

Partial next character None One extra bit of the next character Two extra bits Three extra bits Some configurations allow a partial next character, which sits between two whole character levels.

Attempts per second you can sustain Your own measured rate. This tool has no idea what hardware you have, and does not estimate cost or profitability.

Attempts are independent, so a run can finish far under or far over the expected count. No amount of work guarantees a result in any particular time. Nothing here is a profitability statement.

How the numbers are derived

Each hexadecimal character of prefix fixes four bits of the transaction id, so the expected number of attempts is two to the power of the fixed bits. A partial next character fixes whole bits between two character levels.

The probability of having finished after a given number of attempts assumes independent attempts, each succeeding with probability two to the negative power of the fixed bits.

Expectation is not a schedule

There is a real chance of finishing in a fraction of the expected time, and a real chance of taking several times longer. Plan for the range, not the average.

What this does not tell you

• Your actual attempt rate. Measure it; the tool takes your figure.
• Electricity, hardware, or opportunity cost.
• Whether the mint will still have quota left when you finish.
• Whether a perpetual deployment’s requirement will have progressed by then.

For deployers

Setting a mint Bitwork requirement raises the cost of automated claiming, and it raises the cost for every ordinary participant equally. Model the level you are considering before publishing it, because it cannot be changed afterwards for a fixed deployment.

See ARC-20 Bitwork requirements.