EVM Security
The ALX EVM implementation records a Block hash or Merkle root hash through Solidity contract state and transaction history. The concrete implementation remains separate from vendor-neutral Block creation, identity, lineage, and local validation.
What a Commitment Confirms
A confirmed transaction can establish that a specific Block hash or Merkle root hash was recorded by a particular contract at a blockchain position. A valid Merkle proof can establish that a Block hash is included in the leaf collection represented by that Merkle root.
What a Commitment Does Not Confirm
A commitment does not establish content truth, ownership, authorization, approval, safety, or continued data availability. Applications define the evidence, policies, and trust assumptions required for each additional claim.
ALXAnchor accepts submissions from any address. The first transaction to record a value sets anchoredBy and anchoredAt permanently, so another party that observes a blockHash can record the value first. anchoredBy identifies the first submitter, not the author. ALXAnchor has no administrator or upgrade path.
When to Apply Additional Controls
Add external key management, monitoring, deployment verification, finality policy, and incident procedures before relying on a commitment in a security-sensitive application.