Experimental integrity records. Understand their limits.
Beta on-chain features use Base Sepolia testnet and may be unavailable. A genuine attestation can support a specific integrity check; it does not verify every identity, response or creative record. Simulated records are not on-chain proof.
Integrity checks, with clear limits.
Report hashes and genuine blockchain receipts can help readers check whether a specific payload matches an attested version. They do not establish that its inputs are true, that a person has a verified legal identity, or that a project will succeed. Beta on-chain features are experimental and use Base Sepolia testnet; simulated records are not on-chain evidence.
- Input quality and selective reporting still require independent review
- A digest checks its specific payload, not every exported document
- Identity and credit checks are separate from wallet linking
- A simulated receipt is not a genuine chain transaction
An activity-based reputation indicator.
ProofPoint records platform activity as a reputation indicator. A score is not independent proof of identity, authenticity, taste accuracy or future performance. Scores and anti-abuse rules can change during Beta, and the presence of a score does not mean that every contributing action has been broadcast on-chain.
- Based on recorded platform activity
- Not a guarantee of genuine participation or future results
- No claim of immunity to manipulation
- Beta scoring and feature availability may change
An experimental account-activity attestation.
ProofPass is an experimental EAS account-activity attestation, not legal identity or credit verification. Genuine Beta broadcasts use Base Sepolia testnet and may be unavailable. Read the issuer, recipient, network, schema and transaction details before relying on a receipt. A simulated record is not a production credential.
- Experimental EAS integration on Base Sepolia testnet
- A wallet address is not a verified human identity
- Issuer assertions still require independent scrutiny
- No guaranteed third-party acceptance or future portability
Check the attested report payload.
A SHA-256 digest identifies the specific payload used to create it. Where a genuine attestation is available, compare that payload's digest with the receipt on the stated network. This does not automatically verify an exported PDF, the truth of audience responses, or the time at which the original content was created. Beta receipts use a testnet and should not be presented as production assurances.
- Verify the exact payload covered by the digest
- Check that the transaction is genuine, not simulated
- Confirm the issuer, schema and Base Sepolia network
- Publication time is not proof of original creation time
Optional wallet linking.
Wallet linking is optional and depends on browser, provider and deployment configuration. It is not a guarantee of attestation issuance or verified identity. Public-chain records can expose wallet addresses, timestamps and associated data; disconnecting a wallet or deleting an account cannot erase a published transaction. Do not publish private writing, personal information or secrets on-chain.
- Provider and browser support varies
- Linking does not guarantee a genuine chain broadcast
- On-chain wallet addresses and associated records can be public
- Disconnecting does not remove already published transactions
Built on Base — Coinbase's Ethereum L2
GreenLightOS anchors all on-chain records on Base — a low-cost, high-throughput Ethereum Layer 2 built by Coinbase. Base is fully EVM-compatible, secured by Ethereum, and built to scale. Currently running on Base Sepolia testnet during PoC phase — moving to Base mainnet at launch.