Contact

Community: Community channels are planned; for now the inbox is the forum — we read everything, answer most things, and say so when we don't know. Email us and we'll loop you in when the community channels open.

Registry integrity

Prepare a Complaint

Anyone may prepare a complaint about an OMLA model registration, wallet, payment pointer, or registry-integrity issue. This form downloads a JSON record that you must email to OMLA. Complaints are reviewed manually; filing one does not automatically change any model's registry status.

When should I file a complaint (and when shouldn't I)?

File one if:

A published payment pointer is invalid, hijacked, sanctioned, or cannot accept funds.
Someone has claimed ownership of a wallet that actually belongs to you or your organisation.
A model's declared lineage misattributes contribution — your model was used as a base but you're not credited.
A model's REVOKED or DELISTED status seems wrong — appeals use this same form.
There's impersonation or fraud in the registry.

Don't file for:

Disagreements about license terms themselves — contact board@omla-ai.org.
DMCA / copyright claims unrelated to OMLA registrations — contact legal@omla-ai.org.
A commercial user who isn't paying — OMLA doesn't track payments; non-payment is a License breach you (and your upstream creators) enforce directly under License v2.0 §8. Email legal@omla-ai.org if you want guidance.

Subject

Which type should I pick?

Invalid / non-payable pointer — a published payment pointer cannot receive funds for any technical or policy reason.
Wallet ownership dispute — you believe a wallet is registered to the wrong person.
Lineage misattribution — your model is being claimed as the work of someone else, or a downstream model fails to credit you.
Registry status appeal — you believe a REVOKED or DELISTED status on your model (or another's) is wrong.
Fraud / impersonation — someone is registering your work as their own, or faking a legitimate identity.
Other — anything else that materially affects the OMLA ecosystem.

The type helps a reviewer understand the issue and decide what evidence may be relevant. There is no automated routing.

Complaint type *

Target model ID or wallet address *

Details

What evidence should I include?

Be specific. Specifics win cases. Useful things to include:

Dates and events: when did the issue become apparent? What triggered your complaint?
URLs: links to the OMLA model page, the commercial product deploying it, or any web content substantiating your claim.
Identifiers: OMLA model UUIDs, wallet addresses, commercial user IDs, transaction references.
Cryptographic proof: if you're disputing ownership, a signature over a challenge string from your registered signing key (Ed25519 today; hybrid Ed25519 + ML-DSA-65 is also accepted) demonstrates control.
Contact context: have you tried to contact the other party directly? What happened?

Your email is used only to follow up with you; it's not published.

Describe the issue *

Your name (optional)

Contact email * (for follow-up)

I affirm the information above is accurate to the best of my knowledge. Knowingly false complaints are disregarded and the complainant may be flagged.

What happens next

A reviewer checks the emailed complaint and available registry evidence.
OMLA may contact the affected parties for documentation.
Any registry-status change is a separate, audited reviewer action with a recorded reason. Filing alone changes nothing.
A request for reconsideration is also reviewed manually, with no fixed response time currently promised.
Status changes (REVOKED / DELISTED) appear in the model's manifest and the next signed registry snapshot.