KXCO Verified seals your domain with ML-DSA-65 and anchors it on KXCO Chain. No central authority. No expiry unless you choose one.
Clarity about scope makes the credential stronger, not weaker. KXCO Verified is precise by design.
Verification is quick. The cryptographic proof is permanent.
Provide your domain, document hash, or article URL at chain.kxco.ai/verify. The system generates the cryptographic payload for signing.
An ML-DSA-65 signature is applied to your domain or document hash. No classical RSA or ECDSA — quantum-resistant from the first byte.
The seal ID, domain hash, signature, and timestamp are registered in the KXCOVerifiedRegistry contract on KXCO Chain. Permanent. Independently verifiable.
No hidden fees. No lock-in. The credential lives on-chain regardless of your subscription status.
No reliance on KXCO infrastructure to verify a seal. Any party with RPC access can confirm a credential independently.
// 1. Encode the verify() call
// function verify(uint256 sealId, string domain, string docHash)
// returns (bool valid, uint256 timestamp)
const payload = {
jsonrpc: "2.0",
method: "eth_call",
params: [{
to: "0x17E0DE1f1DdE7BFC149f979f554865ABf11b57b2",
data: encodeVerify(sealId, domain, docHash)
}, "latest"],
id: 1
};
// 2. POST to the RPC endpoint
const res = await fetch("https://chain.kxco.ai/rpc", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify(payload)
});
// 3. Decode result
const { result } = await res.json();
// result → [bool valid, uint256 timestamp]
verify() function returns a boolean and the original registration timestamp.
view method, it requires no gas and can be called from any standard EVM JSON-RPC client — MetaMask, ethers.js, web3.py, curl — against the public RPC endpoint.
getSeal(sealId) for offline signature verification using any FIPS 204-compatible library.
Nothing. The seal exists in the KXCOVerifiedRegistry smart contract on KXCO Chain, which is a decentralised blockchain. The contract state is permanent and independent of KXCO as a company. Anyone can run a node and verify your seal without any involvement from KXCO.
RSA and ECDSA are broken by Shor's algorithm running on a sufficiently powerful quantum computer. ML-DSA-65 (NIST FIPS 204) is based on module lattice hardness assumptions, which have no known quantum algorithm that breaks them. A seal signed today remains valid in the post-quantum era.
Yes. The contract address is public, the ABI is documented, and KXCO Chain's RPC endpoint is open. You can call the verify() function directly using any EVM-compatible tool. The verify.kxco.ai interface is a convenience layer only.
Yes. A Domain Trust seal for kxco.ai covers kxco.ai, chain.kxco.ai, verify.kxco.ai, and all other subdomains. The seal is registered against the apex domain and the verifier matches on the root.
Domain Trust seals your domain as an entity — proving that the domain owner registered it at a point in time. Document Trust seals the SHA3-256 hash of a specific file or content blob, proving it existed in that exact form at registration. They serve different purposes and can be used together.