Known Issues¶

This page lists the major known issues affecting the DataHaven StorageHub SDK (as of version v0.3.1). It’s updated regularly as issues are identified or resolved.

If you encounter a problem not listed here, please join the DataHaven Discord and use the Support Ticket chat to report it. This will create a private channel where our support team can respond directly.

Bucket sharing is not yet permitted. For now, only the bucket owner can access a bucket, regardless of whether it’s set to Public or Private. A future release will enable true public access for public buckets and allow private buckets to be shared with permitted users beyond the owner.

BSPs Unable to Accept Files for Replication¶

While uploads to Main Storage Providers (MSPs) happen successfully, Backup Storage Providers (BSPs) are not accepting new requests right now, so network-level replication doesn’t complete. This can cause file storage requests to transition from upload successful to expired. Although the requests show as expired, the files are still successfully uploaded to the MSP. Still, they are not considered to be in their final state of being secured by the network, given that BSP replication is unavailable.

Get Profile Method Returns Hardcoded Placeholder¶

The auth.getProfile() client method returns the correct address but a hardcoded placeholder of user.eth in the ens field.

{
    ...
    ens: 'user.eth'
}

File Deletion Not Supported on Devnet¶

File deletion is not yet supported when running a local DataHaven development network. As a workaround, you can shut down the network and spin it back up again, which will result in the network state being reset, including deletion of all buckets and files.

Get Info Method Returns Hardcoded Placeholder Values¶

When querying the getInfo() method, you'll see the following hardcoded placeholder values that do not reflect the uptime statistics.

{
    ...
    activeSince: 123,
    uptime: '2 days, 1 hour'
}

Get Bucket Method Returns Hardcoded Placeholder Values¶

When querying for information about a bucket with the method getBucket(bucketId), you'll see the following hardcoded placeholder values that do not reflect the actual file count or file size in bytes.

{
    ...
    sizeBytes: 0,
    valuePropId: 'unknown',
    fileCount: 0  
}

Replication Window and Deletion Timing¶

After a file is uploaded to a Main Storage Provider (MSP), the network allows a 10-minute window for Backup Storage Providers (BSPs) to replicate the file to the required count. If the replication target is not met within this window, the request transitions to expired even though the upload to the MSP succeeded.

File deletion is only permitted once the request is in the expired state. Because BSP replication is currently unavailable (see BSPs Unable to Accept Files for Replication), new uploads will consistently expire after ~10 minutes, after which you will be able to delete the file.

Last update: November 11, 2025
| Created: November 6, 2025