EYES ONLY // CLEARANCE LEVEL 4 // OAP-DOC-001
Deterministic hardware attestation across any blockchain. The proof layer that bridges physical silicon to on-chain trust — without revealing device internal state.
OAP-DOC-002 // DECLASSIFIED SUMMARY
OAP provides deterministic hardware attestation across any blockchain. The platform proves that a physical device produced a specific cryptographic output — without revealing the device's internal state.
Every device enrolled in OAP produces a deterministic, reproducible proof. The same hardware, the same inputs, the same proof — every time. This is not probabilistic. It is cryptographic certainty anchored to physical silicon.
CAPABILITY-01
Same device. Same inputs. Same proof. Always. OAP outputs are reproducible and verifiable by any third party without access to the device.
CAPABILITY-02
OAP proofs are blockchain-neutral. Deploy the verifier on Arbitrum, Solana, TON, Polygon, or any EVM chain. The proof format is universal.
CAPABILITY-03
Attested hardware targets: ESP32-S3 eFuse, TPM 2.0, REDACTED. The proof binds to the physical device — not a key that can be copied.
CAPABILITY-04
OAP proof outputs are structured for zero-knowledge system compatibility. Proofs can be consumed by ZK circuits without access to the source device.
CAPABILITY-05
Device identity keys are burned into write-once hardware memory. They cannot be extracted, exported, or cloned. Physical possession does not imply key access.
CAPABILITY-06
Attestation proofs are computed such that verifiers confirm device authenticity without learning anything about the device's internal configuration or state.
OAP-DOC-003 // LEVEL 3 ACCESS REQUIRED
The internal architecture of the OAP Attestation Engine is proprietary and classified. What is published here is the external interface only — inputs accepted, outputs produced, and the verification pathway available to integrators. Internal gate logic, hash construction, and proof compression algorithms are not disclosed.
Interface: Input
Interface: Output
OAP-DOC-004 // PROTOCOL INTEGRATION
OAP sits at the attestation layer of the Orthonode dependency chain. Protocols that require verified hardware identity consume OAP proofs directly. Additional integrations are undisclosed pending NDA execution.
// OAP public verifier interface — published
// Internal attestation engine: PROPRIETARY, not shown
interface IOAPVerifier {
/// @notice Verify a hardware attestation proof on-chain
/// @dev Internal proof construction: CLASSIFIED
function verifyAttestation(
bytes32 deviceId,
bytes32 proofRoot, // 0xA3F7C1D9... deterministic
bytes4 gateBitmap, // 4-gate result bitmap
uint256 nonce,
bytes calldata sig
) external view returns (bool valid);
/// @notice Get canonical proof root for enrolled device
function getProofRoot(
bytes32 deviceId
) external view returns (bytes32);
// Gate logic: ████████████████████ [REDACTED]
// Hash construction: ████████████████████ [REDACTED]
// Proof compression: ████████████████████ [REDACTED]
}
// SHA usage pattern (Arbitrum Stylus)
contract SHAIdentity {
IOAPVerifier public immutable oap;
function enroll(
bytes32 deviceId,
bytes32 proof,
bytes4 gates,
uint256 nonce,
bytes calldata sig
) external {
require(
oap.verifyAttestation(deviceId, proof, gates, nonce, sig),
"OAP: invalid attestation proof"
);
_enrollDevice(deviceId);
}
}
OAP-DOC-005 // ZERO PROPRIETARY EXPOSURE
The OAP attestation proof is designed around a core structural invariant:
A verifier can confirm authenticity but cannot infer eFuse configuration, firmware version, key material, or any internal device parameter from the proof alone. This is a structural property of the proof system — not a policy or configuration option.
OAP-DOC-006 // RELEASE STATUS