[Bug] Light node can appear healthy without verifiable data availability proof

[maslitti]

Celestia Node version

N/A (design-level issue, independent of specific node version)

OS

Linux (generic)

Install tools

No response

Others

Summary

A Celestia light node can appear healthy and running while there is no clear or verifiable indication that data availability sampling is actually being performed successfully.

This makes it difficult for operators to determine whether the node is effectively contributing to data availability verification.

Expected behavior

When a light node is running and reported as healthy, operators should be able to verify that:

• data availability sampling is actively occurring
• samples are being successfully verified
• the node is meaningfully contributing to the network

Actual behavior

In the current setup:

• the light node process can be running normally
• RPC endpoints respond correctly
• logs may not show explicit errors

However:

• there is no explicit DA proof or verification output
• no clear metric indicating successful sampling
• no public or standardized method to confirm DA participation

As a result, the node can appear healthy while its actual data availability verification status is unclear.

Impact

Node operators may assume their light node is functioning correctly while being unable to confirm whether it is truly performing data availability sampling.

This can lead to:

• false assumptions about node health
• reduced confidence in light node participation
• difficulty validating uptime or incentive eligibility in testnet environments

Steps to reproduce

1. Run a Celestia light node following official documentation.
2. Observe the node reporting healthy status and responding via RPC.
3. Attempt to verify whether data availability sampling is being performed.
4. Note the lack of a clear, verifiable DA proof or sampling indicator.

Suggested solution

Provide clearer visibility into data availability participation, such as:

• explicit sampling success metrics
• RPC endpoints exposing DA verification status
• standardized logs or status indicators confirming active sampling

Steps to reproduce it

1. Install and run a Celestia light node following the official documentation.
2. Start the node and allow it to run normally.
3. Verify that the node reports healthy status.
4. Observe that there is no clear or verifiable indication that data availability sampling is actively occurring.
5. No errors are reported even though sampling activity cannot be confirmed.

Expected result

The node should provide a clear and verifiable indication that data availability sampling is actively being performed.

This may include explicit sampling status metrics, API endpoints exposing DA verification progress, or standardized logs confirming successful participation in data availability checks.

Actual result

The node reports a healthy and running status, but there is no observable or verifiable evidence that data availability sampling is actively occurring.

No metrics, API endpoints, or logs are available to confirm successful participation in data availability verification, making it impossible for operators to determine whether the node is effectively contributing to the network.

Relevant log output

Is the node "stuck"? Has it stopped syncing?

No response

Notes

No response

[linear]

CEL-975