Your token, issued on Chaingentic, checked on every move.
A platform that builds on Chaingentic issues its own token here. From the moment it exists, every transfer of that token is read by AIERC before the value moves, and the reasoning is written down where anyone can check it. Nothing to install, nothing to integrate. The check lives inside the token.
Three things happen, in this order.
1. The token is issued through the evaluated mint. Before your contract exists, AIERC reads the exact code that will be deployed, every file behind it included, and answers CLEAN or FLAGGED. CLEAN deploys it, byte for byte. FLAGGED and it is never born. A FLAGGED contract is refused outright, never deployed: a contract that never exists harms nobody.
2. Every transfer asks for its verdict. A token issued this way will not move without a signed verdict for that exact move: this holder, this recipient, this amount, this chain, once. AIERC reads the transfer, checks both wallets against everything it already knows, and signs. CLEAN settles silently. FLAGGED follows the holder's own block preference: stop the transfer, or surface the flag with the facts so the holder decides. Stopping is the default.
3. The record follows the transaction. The verdict is written to the Chaingentic activity ledger before anything moves. When the token moves, a second record ties the verdict to the transaction that moved the value. Paste that transaction's hash into the report and you get both, in plain words.
Issue it here. It is protected from its first block.
The evaluated mint runs on the Chaingentic testnet today, from the Remix editor or from your own script. Two reference tokens are ready to issue: a fungible token and a collectible, each with the check already wired into its transfer. You can also bring your own contract code; the same evaluation reads it before it deploys.
The mint is open on the testnet by request while its price is being set. Write to contact@chaingentic.io with what you are issuing, and you get the evaluator's address, the two reference contracts, and a walk through your first transfer and its record.
Every verdict, by the transaction that consumed it.
Two doors, both public. The report page on the explorer: paste a transaction hash and read the record in plain words, newest first. The lookup: GET https://api.paygentic.online/record?tx=0x… returns every record naming that hash, where it is inscribed, and the link to the report. No account, no key.
The protection travels with the asset.
A wallet plugin protects one wallet. A firewall protects one app. A token issued on Chaingentic protects itself: whichever wallet holds it and whichever app calls it, the transfer asks for its verdict first. Your platform does not add code to get this. It issues its token here, and the network does the rest.