PHYSICAL RANDOMNESS

Entropy Contribution

Physical devices contribute hardware-sourced entropy from supported device sensors and system sources, creating geographically distributed randomness with traceable physical provenance.

Who it is for and what it answers

Who it is for

Gaming and lottery technology teams, and teams building systems where the provenance of randomness matters.

What it answers

Can we source randomness from distributed physical hardware with evidence of where the contribution came from?

How it works

From question to evidence

Randomness with physical provenance.

01

Define the requirement

Specify the entropy contribution required by the supported workload, including any relevant volume, endpoint or collection requirements.

02

Target the device population

Define the supported device and attestation requirements for the workload. Unetwork identifies suitable physical endpoints capable of contributing to the task.

03

Physical hardware contributes

Supported entropy is gathered from participating physical devices operating under real-world conditions.

04

Entropy and provenance come back

The contribution is returned with the supported task and endpoint metadata, including the applicable attestation state.

Evidence

What a run returns

Depending on the implementation, an Entropy Contribution returns:

Entropy contributionEndpoint identifier and task identifierTimestampAttestation stateTask statusSupported device context
A concrete run

Example

See an example Entropy Contribution run
Endpoint

Android handset · endpoint identifier recorded

Attestation

Hardware attested

Contribution

Hardware-sourced entropy from supported device sensors and system sources

Timestamp

2026-08-25 14:02:11 UTC

Task status

COMPLETE

Device context

Supported device context included with the return

Attestation state is recorded for each contribution. No attestation is a recorded state, not a failure and not a quality grade.

Next step

Tell us what your workload requires.

Check where participating devices can contribute today, or start a conversation about the entropy contribution your system needs.

Provenance

Endpoint attestation

Unetwork supports three endpoint attestation states, allowing the platform to record which attestation state applied to the participating endpoint.

No attestation

A physical Unetwork endpoint without an additional software or hardware attestation result.

Software attested

The endpoint has passed the supported software-based attestation process.

Hardware attested

The endpoint has passed the supported hardware-backed attestation process.

Workloads can target endpoints by attestation state where that requirement is relevant to the task.

  • Any
  • No attestation required
  • Software attested
  • Hardware attested
Entropy Contribution | Unetwork