Towns Protocol is an open messaging protocol built on Base, and TOWNS is its ERC-20 token, deployed on both Base and Ethereum. Its official front door does not present it as neutral community infrastructure: the homepage headline sells money making group chats, and the featured slots include a paid trading-signals group and a betting group. This article covers what the protocol is, what TOWNS does, what the official documents say, and where two of those documents contradict each other.
What Is Towns Protocol
Towns Protocol is an open messaging protocol for group chat and community coordination. Its own site calls it an open messaging protocol built on Base that powers private groups and decentralized finance, and the documentation adds that it consists of an EVM-compatible layer 2 chain, a network of off-chain stream nodes, and smart contracts on Base. Communities are called Spaces, and membership in a Space is an ERC-721 token. The protocol token is TOWNS, an ERC-20 with 18 decimals.
How the project sells itself differs sharply from that neutral framing. Read on 14 August 2026, the towns.com landing page leads with the line Discover the best money making group chats above a counter labelled TOTAL EARNINGS, and its Featured and Top Staking rails name specific communities: Sistine Research, described as the number one trading group for crypto, stocks, and metals and carrying no free tag; Let's TRADE, tagged Stop Gambling. Let's TRADE.; and BrazyBet, tagged When the fun stops, deposit more LOL. Paid trading-signal groups and betting groups are not an edge case here. On that date they were the promoted examples.
Three entities should be kept apart. Towns Labs is the development company, formerly HNT Labs (Here Not There Labs) and founded by Ben Rubin, and it builds the commercial app. The River Eridanus Association is a Swiss association, named in the towns.com footer as copyright holder and described in the documentation as established in the first quarter of 2024. Towns Lodge is the governance venue, with a forum at gov.towns.com that on 14 August 2026 listed 44 topics in General, 15 in Site Feedback and 1 in Privacy Policy.
What Problem Towns Says It Solves
Before this design, a group chat lived inside one company's servers. The operator held the member list, the history and the moderation switch, so a community could not take its membership graph anywhere, could not price access without a third-party payment product, and could not prove to an outsider who its members were. The usual workaround was a token-gating bot bolted onto a hosted chat product, which left the account system, and the power to delete it, with the host.
Towns states its answer as follows: Spaces are deployed on chain, the creator holds an owner token, access rules are contracts that can call other EVM contracts, memberships are ERC-721 tokens, and messages are end-to-end encrypted so node operators cannot read them. That is the project's claim about its own design, not a verified outcome. The documentation frames the economics in the same breath: paid memberships pay a protocol fee, free Spaces do not, and both owners and members are described as earning protocol rewards.
How Towns Protocol Works
The stack has three parts. Smart contracts on Base mainnet, chain id 8453, govern Spaces, memberships, entitlements, node registration and rewards. Towns Chain, chain id 550, is an app-specific Ethereum layer 2 that uses Celestia for data availability, and stream nodes produce mini-blocks finalised there. Those off-chain stream nodes validate, sequence, store and propagate the encrypted messages. The official contracts page, read on 14 August 2026, lists Base Sepolia and a Towns Chain testnet alongside the two mainnet networks.
Messages are organised as streams. Encryption is end-to-end: the documentation describes Curve25519 device key pairs with public keys registered on chain and private keys held client side, plus a shared AES session key for channel and group messages. Entitlement checks, meaning who may read and who may write, are settled by contracts on Base rather than inside the message network, and cross-chain entitlement checking lets a Space gate on assets held on other EVM chains.
Nodes cannot simply join. An operator must have a minimum amount of TOWNS delegated to it before it can operate, that minimum can be met by tokens delegated directly or pointed at the node by a Space, and operators with more stake take priority because the number of active nodes is capped. Operator approval runs through Towns Lodge. Rewards are distributed bi-weekly, each operator keeps a commission it sets itself, and the remainder passes to delegators pro rata.
What TOWNS Does in the Network
TOWNS is an ERC-20 token deployed on two networks. The official documentation gives the Base address as 0x00000000A22C618fd6b4D7E9A335C4B96B189a38 and the Ethereum mainnet address as 0x000000Fa00b200406de700041CFc6b19BbFB4d13, and the same pair appears on the node operator contracts page. Initial supply is stated as 10 billion tokens with a designed inflationary model, and the technical overview gives the more precise genesis figure of 10,128,333,333. On BaseScan on 14 August 2026 the Base contract showed 49,389 holders and a proxy implementation, while a Blockscout read of the Ethereum contract on the same date showed 731 holders.
The documented uses are delegation, staking and governance, and nothing else. Holders delegate to a node operator or to a Space, a Space can point delegated tokens at a node while keeping its own voting power, and governance is driven exclusively by delegated tokens. Node rewards and the yield delegators receive are not paid out of protocol revenue: they are paid by inflation. The economics page states an annual inflation rate of 8% beginning after year one, decreasing linearly over 20 years to a final rate of 2%, with the DAO able to vote inflation down but not up. Fee-funded buy-and-burn is written in the future tense and should be read as a plan, not a running mechanism.
Distribution and lock-ups are published. Roughly 35% of tokens go to the team and investors, 5% to HNT Labs and the remaining 60% to the association, and the initial team and investor allocations are subject to a one-year lock-up followed by a two-year linear vesting schedule. The genesis table in the technical overview is consistent with that summary, listing 21.46% for the team and 13.74% for investors, which is where the approximately 35% comes from.
Two official pages disagree about how long tokens are locked after you undelegate, and the disagreement was still there on 14 August 2026. The utility page states that once delegated, tokens become non-transferable for a 30-day cooling-off period starting when the unstake function is called. The token-governance page states that when tokens are undelegated, a 60-day countdown is initiated before they are transferable again. The staking page repeats the 30-day figure. The documents also make a negative claim worth reading literally: the technical overview states that TOWNS does not grant any rights to financial returns, profit, or capital reimbursement, and does not represent equity, debt or ownership in the protocol, the association or the DAO.
The Towns Ecosystem and Adoption Today
Almost every adoption number on the official surface is self-reported, and one is demonstrably not live. The homepage carries a counter reading TOTAL EARNINGS $31,232,500. That figure was identical when the site was read months earlier and again on 14 August 2026, so it should be treated as a static claim about cumulative earnings, not a real-time metric. The member counts beside each featured Space, and the star ratings next to them, are equally the platform's own numbers with no stated methodology.
What can be checked independently is thinner and more useful. On 14 August 2026 the Base token contract recorded 49,389 holders and 4,742 transfers in the preceding 24 hours, and the Ethereum contract recorded 731 holders. The governance forum listed 60 topics in total across its three categories on the same date. The documentation names two clients building on the protocol, Towns and LateCheckout, and points developers at a React SDK, a bots SDK and a mini-apps SDK.
The character of the visible ecosystem is worth stating plainly, because it is what a reader actually meets. On the date checked, the promoted Spaces were dominated by paid trading and market-commentary groups, with hobby and creator communities alongside them, and the most-staked Space was the trading group named above. A protocol can be neutral while its flagship application is not, and the two should not be described as one thing.
How Towns Differs from Other Messaging Designs
The first mechanical difference is where the account system lives. In a hosted chat product, membership is a database row the operator controls. In Towns, membership is an ERC-721 token and the Space itself is a contract with an owner token, so the access rules are executed by contracts on Base and can read state from other EVM chains. That relocates authority over who may read and write, and it also means those rules are public and that a Space's membership is discoverable on chain.
The second is how message delivery is separated from settlement. Towns does not put messages on Base: it runs a separate network of stream nodes producing mini-blocks on an app-specific chain, and keeps only entitlements and payments on Base. Other designs either put every message on a general-purpose chain, or stay entirely off chain and use a chain only for identity. Those are different trade-offs, not a ranking.
Risks and Limitations
The first limitation is documentary. Two official pages state different lock-up periods for undelegated tokens, 30 days and 60 days, and as of 14 August 2026 neither had been corrected. A parameter that decides when your tokens move again is exactly the kind of number that should not have two published values, and until it is reconciled the only reliable answer is whatever the contract enforces on chain.
The second is that no public audit report could be found. On 14 August 2026 the docs site published no audit page, BaseScan's contract tab for the Base token showed no security audit submitted, and the Bug Bounty link in the towns.com footer resolved to a HackenProof error page. The contracts are upgradeable, and the Base token is a proxy whose implementation has already been changed three times, so whoever controls the upgrade path can change behaviour after you read the code.
The third is economic. Node rewards and delegator yield are inflation, not revenue, so supply expands to pay them and what a delegator receives depends on how many tokens are staked against a fixed issuance. Concentration is a related risk: roughly 35% of genesis supply went to the team and investors under a lock-up that unwinds over three years, and the association holds the large remainder. Fees are collected only on paid memberships, so free Spaces contribute nothing there.
The fourth is what the product is used for, and the regulatory exposure that follows. The official front door promotes paid trading-signal groups and gambling-themed Spaces, which puts consumer-protection, financial-promotion and gambling rules in scope in several jurisdictions. Separately, the project states that Swiss and Korean legal opinions treat TOWNS as a utility token and not a security. That is the position of the project and its advisers, not a ruling that binds any regulator, and this article makes no claim about how TOWNS is classified.
How to Verify Towns Protocol
Start from the official domain, typed into the address bar, not from a search result or an advertisement. Use towns.com and docs.towns.com as the origin for every other link, including social accounts and the app, because only the direction from the official domain outward is evidence. Compare any domain you land on character by character, and stop if a page reached from a message or an advertisement asks you to connect a wallet to claim, migrate or verify anything.
Pin the contract before anything else. The token-governance page and the node operator contracts page both list the addresses, and they must agree: Base 0x00000000A22C618fd6b4D7E9A335C4B96B189a38 and Ethereum mainnet 0x000000Fa00b200406de700041CFc6b19BbFB4d13. An address quoted without its network is not an answer, because the same ticker exists on two chains here. Paste each address into a block explorer for that exact chain, BaseScan for Base and an Ethereum explorer for mainnet, and confirm the name, the symbol, 18 decimals, that the source code is verified, and the holder count.
Read the token mechanics from the documentation rather than a summary, and read all of the token pages instead of one. That is how the 30-day and 60-day lock-up conflict becomes visible. Where pages disagree, treat the deployed contract as the authority: the staking documentation names the RewardsDistribution facet on the BaseRegistry diamond, whose parameters can be read directly. Take supply and unlock data from the chain and the official schedule, not from a price aggregator.
Grade the remaining claims by who is making them. Any earnings counter, member count or rating on the official site is the project's own number, so record the date you read it and check whether it has moved. For audits, look for a report on an auditing firm's own site: a link that leads to an error page is not evidence of a bug bounty. If a Space charges for trading signals or offers betting, that is a commercial relationship with that Space's operator, and nothing about the protocol underwrites it.
Conclusion
Towns Protocol is an open messaging protocol on Base whose Spaces are on-chain contracts and whose memberships are ERC-721 tokens, developed largely by Towns Labs alongside a Swiss association and a token-governed lodge. TOWNS is an ERC-20 on Base and Ethereum used for delegation, staking and governance, its node and delegator rewards come from inflation starting at 8% and falling to 2% over 20 years, and the project states that the token grants no right to financial returns. The public face of the network on 14 August 2026 was a directory of money making group chats including paid trading and betting groups, and its headline earnings counter has not changed in months. Take the contract address from the official documentation, confirm it on a block explorer for the right chain, and read every token page rather than one.
Related market pages
Bitbase pages for the tokens named in this article:
- TOWNS: View price · Perpetual market
Related reading
Other Bitbase articles on this topic:
- Meme Coin Lifecycle and Hype
- Solana Meme Tokens: BOME, MEW, and Why MYRO Now Has Two Live Contracts
Disclaimer: This article is educational content from Bitbase Academy, provided for information only. It explains what a project does and what role its token plays in that system; it does not constitute investment, trading, tax, or financial advice, and it is neither a recommendation nor an endorsement of any project or token. Bitbase has not carried out due diligence on the project described here, and mentioning it does not mean Bitbase lists or supports the asset. Crypto assets carry significant risk, including price volatility, thin liquidity, smart-contract failure, regulatory uncertainty, and the possible loss of their entire value. Its contracts have not been publicly audited, or the published audit covers only part of the code. Written as of August 2026; a project's status, tokenomics, team, and contracts can change at any time. Verify everything yourself through official channels, the contract address, and a block explorer, and beware of imitation sites and phishing links.
References
[1] Towns Protocol, official homepage (money making group chats headline, TOTAL EARNINGS counter, featured and top-staking Spaces, read 14 August 2026) towns.com
[2] Towns, official documentation: Introduction (protocol components, Spaces and memberships, River Eridanus Association, clients) docs.towns.com
[3] Towns, official documentation: Utility (delegation, 30-day cooling-off period after unstake) docs.towns.com
[4] Towns, official documentation: Towns Token (contract addresses, 10 billion initial supply, 8 to 2 percent inflation, distribution, 60-day countdown after undelegation) docs.towns.com
[5] Towns, official documentation: Economics (annual inflation schedule, bi-weekly epoch distribution, operator commission) docs.towns.com
[6] Towns, official documentation: Staking (30-day cooldown on unstaking, RewardsDistribution facet on the BaseRegistry diamond) docs.towns.com
[7] Towns Technical Overview, official white paper (genesis allocation table, vesting, no rights to financial returns, legal classification) docs.towns.com
[8] Towns, official documentation: Contracts for node operators (chain ids and the Base and Ethereum token addresses) docs.towns.com
[9] BaseScan, TOWNS token page on Base (holders, transfers, proxy implementation, no security audit submitted, read 14 August 2026) basescan.org
[10] Blockscout, TOWNS token page on Ethereum mainnet (symbol, 18 decimals, holder count, read 14 August 2026) eth.blockscout.com
[11] audits github.com
