Back to SocialWTF
Public before sign-in

Trust should be verifiable, not assumed.

This is the authoritative public record for what SocialWTF does, what it does not do, and which protections have or have not received independent review. Read it before connecting a wallet, creating an account or sharing information.

Record version 1 · Updated October 29, 2026

Social platform

Live

AI Commons

Testing

Real payment execution

Disabled

Independent security audit

Not completed

Messenger end-to-end encryption

Not available

Wallet actions explained

Connect: identifies the selected public wallet account. It does not move funds.

Sign-in signature: proves address control for authentication or linking. It does not move funds or reveal a private key.

Approval: can authorize a contract to spend a token allowance. SocialWTF’s current sign-in does not require a token approval.

Transaction: can move assets. Real SocialWTF payment execution is currently disabled.

Wallets are optional for ordinary social access. SocialWTF never needs your private key, recovery phrase or seed words. Always read the wallet prompt, network, destination and amount.

Privacy without euphemisms

  • Profiles and posts support public, contacts-only and private visibility.
  • Blocks, mutual friendship and group membership are enforced by the server.
  • Messenger is access-controlled but is not end-to-end encrypted.
  • Linking a blockchain address may let outside observers correlate public transactions with a profile.
  • Vercel Web Analytics and Speed Insights measure site usage and performance.
  • There is not yet a universal retention schedule or self-service account deletion.
Read the privacy notice

Sentinel boundaries

Sentinel uses deployment-controlled model assets and provider adapters for conversation, translation, summaries and explicitly gated tools. Users cannot upload an arbitrary model package or model URL for the server to execute. Model output does not grant account, owner, wallet or payment authority; consequential actions require server authorization and explicit approval.

Sentinel statusAI Commons

Security evidence and limits

The current release passed 98 required automated adversarial security suites, TypeScript validation, secret scanning and Vercel builds. These are internal controls—not an independent penetration test, certification or smart-contract audit.

The repository Security Advisory form is currently available only to authorized repository collaborators because the source repository is private. A public confidential intake channel is not yet available. Do not place vulnerabilities, credentials or private evidence in a public issue.

Public security status

Verify the project

SocialWTF is independently developed. Its source repository is private; public product facts, policies, machine-readable contracts and release records are published on SocialWTF. It does not claim a corporate security certification or completed independent audit.

Open public verification record

Never send these

  • private key
  • recovery phrase
  • seed words
  • wallet secret
  • bearer session token
  • API key
  • hidden prompt
  • private AI memory

Machine-verifiable record

Search engines, assistants and security tools can read the same factual status.

Open trust APIPlatform termsLiving roadmap