Anti-Nulling Overview

You can't make client code uncrackable — so the strategy is to make a nulled copy worthless and short-lived. Four layers:

1. Verification at activation — provider-routed (Envato / direct / extensible).
2. Domain lock — one code, one domain; second domain is rejected and logged.
3. Heartbeat → revocation — refund/dispute/subscription-cancel flips the license; the copy goes dark on its next call-home.
4. Remote execution / entitlement — high-value logic runs on our servers behind a short-lived entitlement; a ripped copy has nothing local to crack.

Every activate/heartbeat/entitlement/revoke is written to an append-only event trail (with IP), visible in the admin console for abuse hunting. Full detail: the product's docs/ANTI_NULLING.md.