# TIMING_CONSTANTS

> `const` **TIMING\_CONSTANTS**: `object`

Defined in: [packages/synapse-sdk/src/utils/constants.ts:59](https://github.com/FilOzone/synapse-sdk/blob/32f86959b0bf15557657ea412e31a0897440ca98/packages/synapse-sdk/src/utils/constants.ts#L59)

Timing constants for blockchain operations

## Type Declaration

### DATA\_SET\_CREATION\_POLL\_INTERVAL\_MS

> `readonly` **DATA\_SET\_CREATION\_POLL\_INTERVAL\_MS**: `2000` = `2000`

How often to poll for data set creation status

### DATA\_SET\_CREATION\_TIMEOUT\_MS

> `readonly` **DATA\_SET\_CREATION\_TIMEOUT\_MS**: `number`

Maximum time to wait for a data set creation to complete
This includes transaction mining and the data set becoming live on-chain

### PERMIT\_DEADLINE\_DURATION

> `readonly` **PERMIT\_DEADLINE\_DURATION**: `3600` = `3600`

Default expiry time for EIP-2612 permit signatures (in seconds)
Permits are time-limited approvals that expire after this duration

### PIECE\_ADDITION\_POLL\_INTERVAL\_MS

> `readonly` **PIECE\_ADDITION\_POLL\_INTERVAL\_MS**: `1000` = `1000`

How often to poll for piece addition status

### PIECE\_ADDITION\_TIMEOUT\_MS

> `readonly` **PIECE\_ADDITION\_TIMEOUT\_MS**: `number`

Maximum time to wait for a piece addition to be confirmed and acknowledged
This includes transaction confirmation and server verification

### PIECE\_PARKING\_POLL\_INTERVAL\_MS

> `readonly` **PIECE\_PARKING\_POLL\_INTERVAL\_MS**: `5000` = `5000`

How often to poll for piece parking status
Less frequent than blockchain polling as uploads take longer

### PIECE\_PARKING\_TIMEOUT\_MS

> `readonly` **PIECE\_PARKING\_TIMEOUT\_MS**: `number`

Maximum time to wait for a piece to be parked (uploaded) to storage
This is typically slower than blockchain operations as it involves data transfer

### TRANSACTION\_CONFIRMATIONS

> `readonly` **TRANSACTION\_CONFIRMATIONS**: `1` = `1`

Number of confirmations to wait for when calling transaction.wait()
Set to 1 by default to ensure the transaction is mined, could be increased
in the future, or aligned to F3 expectations

### TRANSACTION\_PROPAGATION\_POLL\_INTERVAL\_MS

> `readonly` **TRANSACTION\_PROPAGATION\_POLL\_INTERVAL\_MS**: `2000` = `2000`

How often to poll when waiting for a transaction to appear

### TRANSACTION\_PROPAGATION\_TIMEOUT\_MS

> `readonly` **TRANSACTION\_PROPAGATION\_TIMEOUT\_MS**: `180000` = `180000`

How long to wait for a transaction to appear on the network
This is used when we have a transaction hash but need to fetch the transaction object
Filecoin has 30-second epochs, so this gives six full epochs for propagation
Matches viem's standard timeout for transaction receipt (180s)