Skip to content
KYXFIThe compliance and evidence layer for tokenized assets.Guided Demo

Evidence Review · Demonstration Mode

See which claims the evidence supports.

Each issuer claim is listed with the evidence reference attached to it. References are illustrative labels — this demo never asks for real documents or sensitive uploads.

Demonstration Mode · Simulated data · No regulatory approval is represented.

Scenario
Deployment matches declaration
Evidence items
9 simulated references
MATCH — CONFIGURED TECHNICAL CHECKS PASSED
Issuer claimEvidence reference (simulated)StatusWhat the evidence does not establish
Issuer identity evidenceSimulated registry reference DEMO-REG-1042MATCHDoes not establish beneficial ownership or legal authority.
Asset disclosureIssuer-supplied document, integrity hashMATCHHash confirms the file is unchanged, not that its content is true.
Chain / networkSimulated chain adapter observationMATCHTestnet demo; no live query performed.
Contract addressSimulated deployment observationMATCHAn address does not prove the underlying asset.
Source / build matchSimulated bytecode comparisonMATCHVerified source is not an audit of behaviour.
Implementation / proxySimulated EIP-1967 slot readMATCHUpgradeable proxies can change after assessment.
Audit evidenceIssuer-supplied referenceMATCHPresence of an audit report is not a guarantee of security.
Compliance-provider endpointIssuer declarationCLAIMED ONLYEndpoint availability is not proof that the control is effective.
Privileged rolesSimulated role readMATCHRole holder identity off-chain is not established.

Issuer-supplied references remain claims until independently assessed. A document hash can show a file is unchanged; it cannot show the content is true.