No automatic posting.
GWAP generates the verification text, but the user chooses whether to publish it from X. GWAP does not require write or Direct Message permission for Public Proof.
GWAPGrind With A PurposeGWAP OS Prove control of an X account with a public challenge.
GWAP Public Proof is a read-only X integration for account verification. Users publish a one-time challenge themselves; GWAP then retrieves the submitted public post through X API v2 to verify who authored it. GWAP does not post to X on the user's behalf.
X API v2 integration
Public post read access is used only to verify Proof of Control.
When a user submits an X post URL, the GWAP server requests that specific public post by ID and reads the author relationship needed to confirm that the claimed account published the one-time GWAP challenge.
GET /2/tweets/:idtweet.fields=author_id
expansions=author_id
user.fields=username
The pasted link is not trusted by itself.
GWAP independently checks the returned X post author and binds a successful verification to the stable X account ID, not only to a mutable username.
Verification data stays scoped to trust provenance.
Public Proof records the challenge, submitted post reference, visible handle, verification status, method, and timestamps required to explain how the relationship was verified.
Verification flow
Simple for users. Strict underneath.
A social account is never marked verified because a username looks similar, a profile image matches, or a user simply says they control it.
- 01Claim the X handle you control inside GWAP OS.
- 02Choose a GWAP share theme and generate a one-time Public Proof challenge.
- 03Publish the generated verification message from the claimed X account.
- 04Paste the public X post URL back into GWAP OS.
- 05GWAP reads that public post through X API v2 and verifies the exact challenge, author handle, and stable X account ID.
- 06A successful check creates Proof-of-Control provenance in the GWAP Trust Graph and Relationship Graph.