DataSeal.net
Learning center

Guide

Confirmations & Merkle timing

After you create a timestamp, DataSeal.net watches the blockchain in the background. Here is what the statuses mean—and how long each step usually takes—without the infrastructure jargon.

Two different “proofs”

  • Transaction confirmation — has the anchor transaction been included in a block, and how deep is that inclusion?
  • Merkle inclusion proof — compact math that lets anyone verify that exact transaction is inside that block’s Merkle tree. Learn the ideas in Merkle proofs & paths.

Confirmation answers “is it on-chain?” Merkle proof answers “can I prove which block it belongs to?”

Typical timeline

Times depend on network conditions. DataSeal polls on a schedule, so you may see updates a few minutes after the chain itself moves.

1

Transaction signed & broadcast

Usually within minutes

Your fingerprint is anchored in a blockchain transaction. The certificate shows the transaction ID while the network includes it in a block.

Background worker

2

First confirmation

Typically minutes after broadcast

We poll the network about every five minutes. When the transaction appears in a block, status moves to initial confirmation and the count shows as 1+.

Background worker

3

Deep confirmation

~24 hours after first confirmation

About 24 hours later we check again and store a deeper confirmation count (shown as N+). That is when the status becomes fully confirmed.

Background worker

4

Merkle inclusion proof

Often within ~20–40 minutes after first confirmation (if a share exists)

For entries with a public proof page (or when you export a proof package), we fetch a TSC Merkle proof that shows the transaction is inside that block. The worker runs about every 20 minutes.

Background worker

Why wait ~24 hours for “confirmed”?

The first confirmation means the transaction made it into a block. Waiting about a day before the deep check gives the chain time to settle, then we record a stronger confirmation count on your certificate. Your proof is already useful after the first confirmation—deep confirmation is an extra durability signal, not a delay before the fingerprint is anchored.

When does the Merkle proof appear?

Merkle proofs are fetched for entries that need them on a public proof page (or when you request a portable proof package). Private-only timestamps do not pull a Merkle proof until you create a share or export a package.

  • After initial confirmation, if a public share already exists, the certificate is queued for a TSC Merkle fetch.
  • Creating a public share later for a confirmed entry also queues the fetch.
  • The Merkle worker runs about every 20 minutes, so “Ready” often shows up shortly after the first confirmation when a share is active.

More on live links: Public proof pages.

Status cheatsheet

Signed / pending
Transaction is on its way. Waiting for the first block.
Initial confirmation
Seen in a block (1+). Deep check is scheduled; Merkle proof can start if you have a public share.
Confirmed
Deep confirmation completed. Confirmation count reflects the later network check.
Merkle proof Ready
Inclusion path is available on the public certificate for independent verification.

Confirmation counts are shown as N+ (for example 1+ after the first block, then a higher number after the deep check).

Related guides