Add OWB (BASE)

[clash-deployer]

Adding info for ERC20 token 'OWB'.

[merge-fee-bot]

PR Summary

Files OK: 2
Token in PR: BASE 0xEF5997c2cf2f6c138196f8A6203afc335206b3c1
Failed to get info.json content: failed to unmarshal json: invalid character ']' looking for beginning of value (https://raw.githubusercontent.com/onewayblock/assets/master/blockchains/base/assets/0xEF5997c2cf2f6c138196f8A6203afc335206b3c1/info.json)

[merge-fee-bot]

Hi! In order to compensate for the efforts of processing PRs, we kindly ask for a contribution.
💀 As there is no refund, before paying the fee, make sure new tokens fulfill the minimum circulation and other acceptance criteria.
See also the PR Fee FAQ.

Please pay 500 TWT to the BEP20 (Binance Smartchain) address 0x912154fC3AeED776f767eBF0420Ec86b8d985d64.
Alternatively, 2.5 BNB is also accepted (same address).

QR code: Trust | other wallet

TWT Acquiring:

• Trust Wallet Tokens (TWT) can be obtained from DEXs/exchanges.
• TWT-BEP20 can be traded with TWT-BEP2 using the Trust Wallet Swap Option.

Notes:

• New tokens without significant usage are rejected, see criteria mentioned above.
• One PR should be for a single project; PR's with more than 10 logos will be rejected.
• Payment evaluation happens automatically, but with a few minutes delay. When payment is detected, an Accept Review is automatically placed on the PR, which is a condition for merge.
• Evaluating the PR is done manually, and it is merged only if all conditions are satisfied.
  There will be a fee to process this request. None of it goes to the developers.
  Before paying the fee, make sure new tokens fulfill the minimum circulation and other acceptance criteria.
  If you are paying TWT for the submission, this will be burned automatically. There will be no refunds.

[merge-fee-bot]

Fee is PAID, fantastic! Thanks! Review added.

The PR will be evaluated soon by a maintainer, and if merged, the new logos should be visible in Trust Wallet.
Please note that the app caches logos (up to several days; if you want to see changes immediately, use a new installation). See the assets FAQ.
@curiouschonk, @TWmLorejo, @twhino, @tw-jt: please take note.

(500.00 TWT)

[merge-fee-bot]

500.00 TWT have been successfully burned.

[twhino]

Hi @clash-deployer,

To facilitate a swift review of your submission, please respond to the following questions:

• What is the purpose of this token, and how will it benefit Trust Wallet users?
• How is the token being distributed? Have you conducted an airdrop, or, are you planning to do one?
• Is the token listed on any centralized exchanges?
• Is the token listed on any decentralized exchanges with locked liquidity?
• Is the token listed on CoinMarketCap (CMC)? If not, could you please explain the reason?
• Has a Smart Contract audit been completed, and where can we access this information?
• Are the team members behind this token publicly identified with their faces, names, and brief introductions available online? If so, please provide the link(s). If not, could you explain the reason for maintaining anonymity?

[clash-deployer]

Hi @clash-deployer,

To facilitate a swift review of your submission, please respond to the following questions:

• What is the purpose of this token, and how will it benefit Trust Wallet users?
• How is the token being distributed? Have you conducted an airdrop, or, are you planning to do one?
• Is the token listed on any centralized exchanges?
• Is the token listed on any decentralized exchanges with locked liquidity?
• Is the token listed on CoinMarketCap (CMC)? If not, could you please explain the reason?
• Has a Smart Contract audit been completed, and where can we access this information?
• Are the team members behind this token publicly identified with their faces, names, and brief introductions available online? If so, please provide the link(s). If not, could you explain the reason for maintaining anonymity?

Hi @twhino, thank you for the review and the questions. Happy to provide more context:

1. What is the purpose of this token, and how will it benefit Trust Wallet users?
   $OWB is the utility token of the OWB Studio ecosystem and our flagship game Clash of Coins.
   It fuels the in-game economy and is used for rewards, staking, community incentives, and to support upcoming games and ecosystem projects developed by OWB Studio.

We have over 500,000 registered users, and a substantial part of our community already uses Trust Wallet as their primary wallet. Adding verified metadata and the official logo helps users clearly identify the authentic $OWB token, avoid confusion with similarly named assets, and safely use Trust Wallet’s full DeFi functionality with $OWB.

2. How is the token being distributed? Have you conducted an airdrop, or are you planning to do one?
   The token has been distributed through community airdrops (two successful campaigns already completed) and a limited private sale among angel investors. Future distributions are tied to ecosystem growth and in-game participation.

3. Is the token listed on any centralized exchanges?
   No. This is a deliberate decision. We are currently not pursuing CEX listings in order to avoid liquidity fragmentation and to first build a strong foundation within the ecosystem before proceeding with centralized exchange listings.

4. Is the token listed on any decentralized exchanges with locked liquidity?
   Yes. $OWB is listed on decentralized exchanges on Base:

• Aerodrome
• Uniswap

Liquidity is managed transparently within the ecosystem.

5. Is the token listed on CoinMarketCap (CMC)?
   Yes:
   https://coinmarketcap.com/currencies/owb

6. Has a Smart Contract audit been completed, and where can we access this information?
   The token contract is based on an audited OpenZeppelin implementation.

The source code is public and available here:
https://github.com/onewayblock/coc-contracts/blob/main/contracts/Token.sol

It uses OpenZeppelin’s ERC20, ERC20Permit, ERC20Burnable, and Ownable contracts.

7. Are the team members behind this token publicly identified?
   Yes, the core team is public and identifiable.

Faces and brief introductions from pitch deck:
https://imgur.com/a/56Xpzsb

LinkedIn profiles with clear indication of their roles in OWB Studio
https://www.linkedin.com/in/nick-samarin/
https://www.linkedin.com/in/slav-pankratov-9b723117/

Please let us know if any additional details are required.

[twhino]

Hi @clash-deployer,

Has a Smart Contract audit been completed, and where can we access this information?
The token contract is based on an audited OpenZeppelin implementation

Although your token contract is based on an audited OpenZeppelin implementation, we still require a full audit of your token’s smart contract. Could you please explain why your token’s smart contract has not been audited?

Are the team members behind this token publicly identified?
Yes, the core team is public and identifiable.

You mentioned that your core team is public and identifiable. Could you provide a link on your website where this information is available?

Thank you for your cooperation.

[clash-deployer]

Hi @twhino, thank you for the follow-up questions.

Smart Contract Audit

Our smart contracts have been audited by Oxorio, and the audit reports are publicly available:

• Oxorio Smart Contracts Audit Report — 12.03.2025
• Oxorio Smart Contracts Audit Report — 25.12.2024

During discussions with our auditors, we jointly agreed that performing a separate audit specifically for the Token contract was not necessary. The reason is that the Token contract does not introduce any custom logic or modifications and directly inherits the standard OpenZeppelin ERC20 implementation without changes.

For reference:

• Our token contract:
  https://github.com/onewayblock/coc-contracts/blob/main/contracts/Token.sol

• OpenZeppelin ERC20 implementation:
  https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol

The contract simply extends OpenZeppelin’s audited components (ERC20, ERC20Permit, ERC20Burnable, Ownable) and does not override or customize their internal logic. Given OpenZeppelin’s position as an industry-leading smart contract security provider and the absence of custom code, both our team and the auditors considered an additional standalone audit for this specific contract to be redundant.

Public Identification of the Core Team

At the moment, we do not maintain a dedicated “team” page on our website. The website is intentionally focused on the product and what we are building rather than individual profiles. However, the core team is not anonymous and is publicly active.

Our team members regularly participate in public activities, including:

• Community AMAs
  Upcoming AMA this Thursday with our CEO and the Base Ecosystem Lead:
  AMA announcement

• Industry conferences and public speaking

  • ETHDenver talk
  • Abu Dhabi Finance Week

• Public ecosystem programs and demo days
  OWB Studio are finalists of Base Batches 002 and presented publicly at Devconnect last year:
  Devconnect presentation

We regularly publish community updates and openly reference key team members across our public channels with their names & photos.
Core team members are identifiable, active, and do not operate anonymously.

[twhino]

Hi @clash-deployer,

Please remove the comma after "gamefi" in the tags so we can proceed with merging your request.

Thank you for your cooperation.

[merge-fee-bot]

PR Summary

Files OK: 2
Token in PR: BASE 0xEF5997c2cf2f6c138196f8A6203afc335206b3c1
Symbol: OWB decimals: 18
Links: Logo Info Website Explorer
Tags: gamefi
Token check error:
❌ invalid value for links.name filed, allowed only: coingecko, discord, medium, github, telegram, telegram_news, reddit, facebook, coinmarketcap, forum, source_code, whitepaper, youtube, blog, docs, twitter
❌ number of holders not checked: please, check it manually

[clash-deployer]

@twhino It's done. Thank you.

[twhino]

Hi @clash-deployer,

We are seeing This branch is out-of-date with the base branch. To proceed with the merge, please pull the latest changes from the main branch into your branch to update it.

Thank you for your cooperation and understanding.

[merge-fee-bot]

PR Summary

Files OK: 2
Token in PR: BASE 0xEF5997c2cf2f6c138196f8A6203afc335206b3c1
Symbol: OWB decimals: 18
Links: Logo Info Website Explorer
Tags: gamefi
Token check error:
❌ invalid value for links.name filed, allowed only: discord, coingecko, github, medium, reddit, facebook, coinmarketcap, forum, source_code, whitepaper, telegram, telegram_news, docs, twitter, youtube, blog
❌ number of holders not checked: please, check it manually

[clash-deployer]

Hi @twhino , latest changes have been pulled to our branch.