Acceptable Use Policy

1. Scope of Applicability

This AUP applies to all interactions with Enerdex.org and its technical subdomains, including but not limited to explorer.enerdex.org, grid.enerdex.org, epoch.enerdex.org, and mesh.enerdex.org. By engaging with these systems, you affirm that your activity is governed not by civil contract, but by Enerdex’s Verifier Mesh invariants, XRPL Hook determinism, and nonce-chain continuity requirements.

2. Prohibited Conduct (Protocol Layer)

Participants are strictly forbidden from:

  • Replaying StorageProofs outside their original epoch window, thereby inducing nonce discontinuity.
  • Submitting fabricated Merkle roots or slope-violating discharge curves.
  • Forging or truncating signer bitmaps in Quorum Certificates (QCs).
  • Injecting invalid AnchorCommits to XRPL that bypass Hook uniqueness checks.
  • Manipulating policy_hash bindings, including mid-epoch substitution or retroactive drift.
  • Exploiting Hook rejection outcomes (e.g., ESSeen duplication, MintLock) for simulated arbitrage or telemetry falsification.

3. Prohibited Conduct (Consensus Layer)

Within the Enerdex Verifier Mesh:

  • No node may introduce vote storms that exceed Byzantine fault thresholds.
  • No verifier may withhold votes to deliberately induce view changes.
  • No participant may attempt to bias Anchor Agent rotation randomness.
  • No party may simulate UNL membership outside the canonical Enerdex UNL, which is distinct from XRPL’s UNL.

4. Prohibited Conduct (Ledger Layer)

When interfacing with XRPL anchoring:

  • No AnchorCommit may regress an epoch index (epoch monotonicity is absolute).
  • No Enerdex Unit may be minted twice for the same ES identifier.
  • No ledger-index hint may be falsified or advanced beyond XRPL validated close.
  • No Hook state variable (seen[ES], last_epoch[storage_id], policy_hash) may be interfered with or spoofed at the UI layer.

5. System Abuse & Exploitation

You must not:

  • Perform reverse engineering of aggSig constructs to infer verifier keys.
  • Inject malformed JSON into Enerdex explorers to produce misleading telemetry.
  • Generate synthetic anomalies (e.g., slope violations, clock skew) for the purpose of deceiving observers.
  • Attempt to derive personally identifiable data from non-reversible Merkle roots.
  • Leverage Enerdex explorers for off-ledger trading or valuation claims.

6. Enforcement Mechanisms

Violations of this AUP result not in account suspension, but in protocol-level rejection:

  • Duplicate ES → automatically rejected by XRPL Hooks.
  • Nonce discontinuity → invalidation of entire StorageProof chain.
  • Forged QC → unrecognized by Anchor Agents; never posted to XRPL.
  • Anchor tampering → Hook-level REJECT state, non-reversible.
  • Policy tampering → policy_hash mismatch, resulting in epoch-wide voiding.

Enerdex itself cannot “ban” you; the mathematical invariants of XRPL and verifier meshes enforce all prohibitions automatically.