Estimating Cost
Before you launch anything, Skrybit answers the question every marketer asks first: “what would it cost to inscribe this whole campaign?”
Fee tiers: slow / normal / fast
Bitcoin transaction fees float with demand. Skrybit’s fee oracle tracks the live mempool and quotes three tiers:
| Tier | What it means |
|---|---|
| slow | Cheapest — confirmations may wait several blocks |
| normal | The balanced default |
| fast | Priority — pay more, confirm next block(s) |
The campaign cost estimate prices your entire campaign at each tier:
inscriptions = audience addresses × collection items (per distribution mode)
tier total = inscriptions × (fee rate × inscription size + postage)
- Inscription size comes from your actual media — bigger payloads cost more per inscription.
- Postage is the small amount of sats that rides with each inscription into the recipient’s wallet (an inscription lives on real sats).
- The estimate may also include a cheapest-window hint from Skrybit’s fee forecaster — e.g. “inscribing in ~N hours could save X%” — useful when the drop is not time-critical.
The estimate excludes the platform service fee. The authoritative, all-in price (network cost + service fee) is fixed when the batch is created at launch — that is the exact amount you fund, and it will not change after you see it.
Dry-run the delivery plan
Separately from pricing, you can simulate a launch (dry-run). This runs the full planning path — audience resolution, distribution mapping, batch composition — and returns the plan without creating a batch or touching the chain:
- exactly which addresses receive exactly which items,
- the total inscription count,
- anything that would be skipped and why.
Make the dry-run your pre-flight check: if the plan looks wrong (audience too big, wrong collection linked, unexpected distribution), fix it now — after funding, the batch is in motion.
Next: Launching & Funding.