The public statement
An alias, coarse UTC activity day, random claim ID and an AntiSocial signature. Wallets, transaction signatures, tokens, amounts and exact times are omitted. Publication occurs in daily batches at least 24 hours after submission. Anyone can check an issuer signature locally.
The private verifier
The operator receives your signing wallet and submitted transaction, confirms finality and checks a successful Jupiter interaction with opposing owned asset changes. This is an operator attestation. It is not a trustless or zero-knowledge proof. A compromised operator could disclose mappings or issue false statements.
Underlying swaps remain public
The trading terminal uses standard public Solana settlement through Jupiter. AntiSocial does not claim confidential execution or guaranteed unlinkability. Alias reuse, information shared elsewhere, provider metadata and chain analysis can still identify users.
You authorize every publication
Connecting a wallet does not publish a profile. Registration and posting each require an origin-bound, expiring, one-time wallet signature. These permissions grant no spending authority. One wallet controls one alias; a transaction can be claimed once.
Providers and local storage
RPC and quote providers receive the data needed for reads and swaps. Hosting providers may observe request metadata. The verifier stores private wallet and transaction mappings on its restricted persistent volume. Browser follow lists stay on your device; clearing browser data removes them. No trading private key is requested by the service.