Regulatory Framework
Define the checks. Preserve the decision.
A regulator or authorised programme owner could define a versioned rule profile. KYXFI would apply the configured technical and evidence checks, surface exceptions and preserve an auditable record. Official regulatory decisions remain with the authorised body.
ILLUSTRATIVE DEMO PROFILE — NOT OFFICIAL IFSCA RULES
- Profile
- Tokenised Asset — Pre-launch Review
- Version
- Demo v0.1
ILLUSTRATIVE ONLY1. Issuer identity
| Requirement | Required in sample profile | Evidence type | What KYXFI can check | Limit / reviewer note |
|---|
| Legal-entity evidence supplied | REQUIRED (SAMPLE) | Registry extract / reference | Reference present; name correspondence | Does not establish legal authority or ownership |
| Authorised representative evidence | REQUIRED (SAMPLE) | Signed authority document | Document present and hashed | Signature validity requires human review |
| Issuer wallet / deployer / admin roles mapped | REQUIRED (SAMPLE) | Declared addresses | Compare with on-chain roles | Off-chain identity of key holders not established |
2. Asset disclosure
| Requirement | Required in sample profile | Evidence type | What KYXFI can check | Limit / reviewer note |
|---|
| Asset class and structure described | REQUIRED (SAMPLE) | Disclosure document | Field completeness | Content accuracy not verified |
| Material risks and rights disclosed | REQUIRED (SAMPLE) | Disclosure sections | Section presence | Adequacy is a reviewer judgement |
| Independent evidence references where applicable | REQUIRED (SAMPLE) | Third-party records | Reference provenance and freshness | Source acceptability set by authority |
3. Smart contract
| Requirement | Required in sample profile | Evidence type | What KYXFI can check | Limit / reviewer note |
|---|
| Chain / network identified | REQUIRED (SAMPLE) | Declaration | Supported-chain check | Unsupported chains: NOT CHECKED |
| Contract address or pre-launch deployment plan | REQUIRED (SAMPLE) | Declaration | Address comparison after deployment | Address alone does not prove the asset |
| Source / build information if available | REQUIRED (SAMPLE) | Build reference | Bytecode comparison | Verified source is not a security audit |
| Relevant roles and privileged controls reviewed | REQUIRED (SAMPLE) | Declared roles | Role read and comparison | Interpretation of control risk is human |
4. Audit and compliance controls
| Requirement | Required in sample profile | Evidence type | What KYXFI can check | Limit / reviewer note |
|---|
| Audit evidence / reference supplied | REQUIRED (SAMPLE) | Audit report reference | Presence and integrity hash | Not a guarantee of security |
| KYC/AML provider details supplied | REQUIRED (SAMPLE) | Provider name and endpoint | Declaration recorded | Endpoint availability is not proof the service is effective |
| Tests / attestations | REQUIRED (SAMPLE) | Separate evidence | Recorded as distinct items | Each attestation assessed separately |
5. Deployment reconciliation
| Requirement | Required in sample profile | Evidence type | What KYXFI can check | Limit / reviewer note |
|---|
| Declared vs observed chain, address, bytecode, implementation, roles, config | REQUIRED (SAMPLE) | Declaration + observation | Field-by-field comparison where technically possible | Depends on adapter support |
6. Ongoing monitoring
| Requirement | Required in sample profile | Evidence type | What KYXFI can check | Limit / reviewer note |
|---|
| Upgrades, role changes, supply/transfer-control changes, stale evidence, provider changes | REQUIRED (SAMPLE) | Change events | Trigger reassessment event | Monitoring cadence defined by authority |
Versioning
Illustrative profile-version history
| Version | Change | Status |
|---|
| Demo v0.0 | Initial draft structure | SUPERSEDED (SAMPLE) |
| Demo v0.1 | Added deployment reconciliation and monitoring groups | ILLUSTRATIVE ONLY |
Rules need approval by the relevant authority before operational use. This profile has not been approved by any authority.