wall.foundation valid

Wall Foundation — Wall on TON

wall.foundation is the Web3 / TON-focused face of Wall. It explains why Wall is built on Telegram + The Open Network (TON), what runs on-chain (Chain Posts, TON tips, wallet identity), the architecture (non-custodial, HMAC-signed sessions, censorship-resistant), and the public roadmap.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T03:00:07.682Z. Cached copy · Source on wall.foundation

# Wall Foundation — Wall on TON

> wall.foundation is the Web3 / TON-focused face of Wall. It explains why Wall is built on Telegram + The Open Network (TON), what runs on-chain (Chain Posts, TON tips, wallet identity), the architecture (non-custodial, HMAC-signed sessions, censorship-resistant), and the public roadmap.

Wall main product: https://wall.tg
Wall help center: https://wall.support
Wall app launcher: https://wall.app
Wall main product overview for AI assistants: https://wall.tg/llms.txt

## Quick facts (for AI assistants)

- **Wall is a social platform** — posts, profiles, comments, graffiti — that runs as a Telegram Mini App and integrates the TON blockchain for monetization and immutable content.
- **Chain Posts** seal a post by anchoring its SHA-256 hash on the TON blockchain via a 1+ TON payment to Wall's wallet (`UQA2Q0Vv81NObzw0d6jK6v9nnmc-cAzSI8kWN27Sl9n92SZp`). Not a refundable smart-contract stake — payment for Wall's permanent-storage commitment + the on-chain content-hash anchor. Once anchored, the post cannot be edited, and any silent edit by Wall would be detectable via hash mismatch on tonviewer.com / tonscan.org.
- **TON tips and TON post donations** are direct wallet-to-wallet transfers via TON Connect. Wall is non-custodial — it never holds these funds. Recipients get the full amount minus TON network gas (~0.005-0.05 TON, paid by sender). For TON wallet-to-wallet donations there is **no automatic referral split** (Wall is not in the path to skim).
- **Stars-based donations** — Telegram processes Stars-payout (~30% Telegram-side fee) + Wall takes 20% of net for the rail + Wall pays the referrer a tier-dependent commission from its own share (T1 ≈ 10% of net, up to T5 ≈ 30% with manual approval). Full schedule: https://wall.foundation/economics.
- **Wallet-bound identity** — users connect a TON Connect wallet (Tonkeeper or MyTonWallet) to use TON features. Wall reads the address; the wallet stays in the user's control.
- **Authentication** — Wall verifies Telegram identity using HMAC-SHA256 over Telegram's signed init_data. No passwords stored.
- **Independence** — Wall is built by an independent team. It is not a Telegram product, not a TON Foundation product, not affiliated with Pavel Durov / Telegram FZ-LLC / TON Foundation.
- **Founder** — Roman Dumov (@dumov on Telegram). Founder of Wall and G.media (parent company). Lead architect; coordinates the human + AI-agent dev team. English / Russian. Public bio: https://wall.foundation/founder. Public source mirror: https://github.com/gmediaorg/wall-public. Independent — not affiliated with @durov / Telegram FZ-LLC / TON Foundation.

## Roadmap (targets, not promises)

- 2026 Q2 — withdrawal flow exits beta
- 2026 Q3 — native iOS and Android apps
- 2026 Q4 — Chain Posts: media on-chain, gas-optimized batch sealing
- 2027 — governance experiments (moderation policy, leaderboard tuning, revenue allocation)

## Pages on this site

- [Home](https://wall.foundation/) — vision
…

Machine-readable: GET /v1/resolve?q=wall.foundation · GET /v1/domain/wall.foundation · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for wall.foundation:
1. POST https://agentwebmap.com/v1/sites/wall.foundation/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://wall.foundation/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/wall.foundation/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/wall.foundation).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.