Deployment
No supported public deployment has been published. Each field remains Pending until the corresponding deployment evidence is published.
- Status
- Pending
- Network
- Base
- Chain ID
- 8453
- Contract Address
- Pending
- Contract Version
- Pending
- Contract License
- Pending
- Deployment Transaction
- Pending
- Deployment Block
- Pending
- Deployment Timestamp
- Pending
- Deployer Address
- Pending
- Source Revision
- Pending
- Solidity Compiler
- Pending
- Compiler Optimization
- Pending
- BaseScan Verification
- Pending
- Verified Source
- Pending
- ABI
- Pending
- Runtime Bytecode Hash
- Pending
- Deployment Manifest
- Pending
- Manifest Checksum
- Pending
- Documentation Version
- Pending
- Contract Ownership
- Pending
- Upgradeability
- Pending
- Proxy Status
- Pending
- Permission Model
- Pending
- Security Review
- Pending
- Last Reviewed
- Pending
Contract
What ALXAnchor accepts and records.
- Commitment Type
- bytes32
- Submission
- Permissionless
- Administration
- None
- Upgradeability
- None
- Proxy
- No
- Recorded Evidence
- First timestamp and submitting address
- Duplicate Handling
- Defined by the deployed contract version
Onchain Data
Base records a commitment derived from ALX data. The ALX Block retains its existing content, deterministic identity, and declared lineage.
- 1OffchainALX Block
- 2OffchainblockHash or Merkle Root
- 3BaseALXAnchor
- 4BaseBase Record
Verification Scope
Confirms that a commitment was recorded by the specified contract on Base.
Confirms
- Commitment was recorded
- Contract and chain context
- First recorded timestamp
- Submitting address
Does Not Confirm
- Content truth
- Authorship or ownership
- Approval or authorization
- Content availability
What is ALX on Base?
ALX on Base provides a public-chain layer for anchoring ALX Blocks. Its contract records commitments derived from ALX data, either an individual blockHash or a Merkle root, as public evidence on Base.
Is ALX on Base deployed?
Not yet. No supported public deployment has been published, so the contract address and every deployment field read Pending until reviewed deployment evidence is published.
Do I need ALX on Base to use ALX?
No. Blocks are created, identified, and verified locally, with no blockchain involved. A commitment on Base is optional public evidence.
What does a commitment record?
One bytes32 value, an individual blockHash or a Merkle root, with the first chain timestamp and the submitting address. Block content stays offchain.
Does anchoring change a Block?
No. The Block keeps its content, deterministic identity, and declared lineage. Base holds only the commitment value.
What does a successful lookup establish?
That the supplied commitment was recorded by the identified contract on Base, with its first timestamp and submitting address. Content truth, authorship, ownership, approval, and availability stay with application policy.
Should I commit a blockHash or a Merkle root?
Commit a blockHash when each Block needs its own record. Commit a Merkle root when one record should represent a complete collection, then verify each Block against it with a Merkle proof.
Who can submit a commitment?
Anyone. Submission is permissionless, and the contract has no administrator, upgrade mechanism, or proxy.