Redbrick
Redbrick (BRIC) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).
Redbrick describes an “AI‑powered gaming engine” for accelerating game creation (including text‑to‑game) and a Web2↔Web3 platform with an onchain economy and the $BRIC token.
Disclaimer
Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.
TL;DR (for readers who are not into AI)
- What it is: a game engine/platform that promises to simplify the creation and monetization of games (UGC) and supports Web3 integrations.
- Who it’s for: game/content creators, game studios and Web3 projects that want to quickly release “casual” games and plug in an onchain economy.
- Why onchain/token: onchain is used for transactions/assets/monetization and the token economy; the BRIC token is described as a utility token for fees, rewards and staking (per the litepaper).
How it works (very briefly)
- The user does: creates/publishes a game via Redbrick’s tools.
- The system does: uses the engine’s AI tools to speed up creation and provides a monetization layer (ads, marketplace, in‑game purchases).
- The user gets: a published game and monetization/rewards.
- Where the blockchain is: onchain assets/transactions and the BRIC token (BEP‑20 on BNB Smart Chain); multi‑chain integrations are claimed in the documentation.
- Token role (if any): BRIC is used for fees, rewards, transactions and staking benefits (per the docs).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Redbrick |
| Also known as (aliases) | $BRIC; Redbrick Engine |
| Logo (logo) | ../assets/303_redbrick_logo.svg |
| Token symbol (ticker) | BRIC |
| Category | AI/Agents | Gaming | Infra |
| Primary chain (chain) | BNB Smart Chain |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoSA (BNB Smart Chain; 21 validators) |
| Launch date (launch_date) | — |
| Project status (status) | active (litepaper + token) |
| Token (standard) | BEP-20 |
| Token contract | 0xb40f2e5291c3Db45AbB0Ca8DF76F1C21E9f112a9 |
| Token model (token_type) | utility (staking) |
| Max supply | 1,000,000,000 BRIC (BscScan Max Total Supply; docs: capped at 1B) |
| Issuance | capped supply (per the docs) |
| Tokenomics (tokenomics, brief) | the docs publish the allocation and release schedule; utility: fees, rewards, staking |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | investors allocation 6.3% (per the docs) |
| AI component (ai_component) | AI Engine (text-to-game + visual no-code) |
| Use‑case (use_case) | fast creation + monetization of UGC games |
| DecAI Fit — AI thesis fit | 4/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 2 / 2 / 1 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://redbrick.land |
| Docs | https://docs.redbrick.land/ |
| GitHub | — |
| Releases / Changelog | https://medium.com/redbrick-official |
| Whitepaper | https://docs.redbrick.land/ |
| Roadmap | https://docs.redbrick.land/~gitbook/image?url=https%3A%2F%2F2651639109-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FnQa8Ie648QZD5YtjzM0d%252Fuploads%252FpnZuKTh9k2H7v2lsVwGC%252FCommunity%2520Roadmap.jpg%3Falt%3Dmedia%26token%3Da870b5fc-c2e8-4cd2-a571-02cb3a38419b |
| Security advisories | — |
| Explorer | https://bscscan.com/token/0xb40f2e5291c3Db45AbB0Ca8DF76F1C21E9f112a9 |
| X | https://twitter.com/RedbrickLand |
| Discord | https://discord.gg/redbrickio |
| Telegram | https://t.me/redbrick_games |
| Medium | https://medium.com/@redbrick.land |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/redbrick |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/redbrick/ |
General project overview
In its documentation, Redbrick describes an “AI‑powered gaming engine” that lowers the barriers to game creation, including text‑to‑game, a 2D/3D engine and visual programming. The platform claims a Web2↔Web3 bridge and an economy where users and creators receive rewards and use the BRIC token for fees, purchases and other operations. The litepaper provides product KPIs and theses on onchain transactions (as platform metrics, not AI model quality).
Features/modules
- AI Engine (text‑to‑game) and a set of tools for content creation.
- Multi‑chain and account abstraction (claimed in the docs).
- Monetization: ads, marketplace, in‑game purchases, platform fees.
- BRIC token: utilities + staking benefits (per the docs).
Typical scenarios
- Scenario 1: a creator generates/assembles a game via the engine’s tools → publishes it → receives income/BRIC based on engagement.
- Scenario 2: a player plays and accumulates offchain points → converts them into BRIC → spends them on assets/fees (per the docs).
Getting started (wallet/network)
- What you need: a wallet for BNB Smart Chain (if the user interacts with BRIC/onchain assets).
- Network/chain: BNB Smart Chain (the BRIC contract).
- Fees: gas on BNB Smart Chain + platform fees (if applicable).
Architecture/tech (non‑AI)
- Onchain: the BRIC token and transactions/assets related to the platform economy (per the docs — high‑level).
- Offchain: the game engines/creation tools and part of the monetization.
Token/economics (expanded, no forecasts)
- Token utility: platform fees, rewards, transactions and staking benefits (described in the docs).
- Allocation & schedule: the allocation and release schedule are published.
AI component of the project
- What is real AI here? The documentation describes an “AI Engine” (text‑to‑game, generation of assets/logic and visual no‑code). This confirms the presence of an AI layer as part of the product, but the sources of this card contain no model quality metrics.
- What is truly onchain? The BRIC token and onchain transactions/assets as part of the platform economy; multi‑chain integrations are claimed.
- Why is a token needed? BRIC is described as the platform’s central currency (fees, rewards, staking), but protocol‑level irreplaceability is not proven in the sources of this card.
- Red flags (based on the information found): the absence of a public audit report on the contracts in the links of this card.
DecAI Fit component summary
- DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 2 |
| Onchain necessity | medium | 2 |
| Token necessity | low | 1 |
| Evidence | Tier‑1 present | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI Engine is described as a current part of the product, not just a plan.
- Evidence: Tier‑1 — https://docs.redbrick.land/
- Why sufficient / why not (one line): the litepaper describes the AI Engine components.
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): AI Engine allows creating a game/assets from a prompt (text‑to‑game) and simplifies content creation.
- Evidence: Tier‑1 — https://docs.redbrick.land/
- Why sufficient / why not (one line): the AI Engine functions are described.
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Evidence: —
- Why sufficient / why not (one line): there is no verifiable demo of AI generation in the links of this card.
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Evidence: —
- Why sufficient / why not (one line): the KPIs in the docs relate to the product/community, but are not AI model quality metrics.
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): the docs describe the technology stack and the composition of AI Engine (2D/3D, visual coding, text‑to‑game).
- Evidence: Tier‑1 — https://docs.redbrick.land/
- Why sufficient / why not (one line): a high‑level breakdown of the modules is given.
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: BNB Smart Chain
- Addresses/identifiers: BRIC token (BSC): 0xb40f2e5291c3Db45AbB0Ca8DF76F1C21E9f112a9
- Evidence: Tier‑1 — https://bscscan.com/token/0xb40f2e5291c3Db45AbB0Ca8DF76F1C21E9f112a9
- Why sufficient / why not (one line): we confirm the token’s onchain contract in the explorer.
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- Claim (one line): the docs describe onchain transactions/assets, minting and marketplace/fees as part of the ecosystem.
- Evidence: Tier‑1 — https://docs.redbrick.land/
- Why sufficient / why not (one line): the onchain economy is described beyond “just a token”.
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- Claim (one line): the Tier‑1 sources of this card contain no strict argument that the product “breaks” without a blockchain (rather “integrations”).
- Evidence: —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Evidence: Tier‑1 — https://bscscan.com/token/0xb40f2e5291c3Db45AbB0Ca8DF76F1C21E9f112a9
TK_1 — payment for the service (1/0)
- TK_1 (decision): 1
- Claim (one line): the docs describe “Pay platform fees with $BRIC” and the use of BRIC in platform transactions.
- Evidence: Tier‑1 — https://docs.redbrick.land/introduction/what-is-redbrick/redbrick-creator-and-token-economy
- Why sufficient / why not (one line): the fee payment utility is described directly.
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): the docs describe rewards and staking benefits, as well as the points → BRIC conversion.
- Evidence: Tier‑1 — https://docs.redbrick.land/introduction/what-is-redbrick/redbrick-creator-and-token-economy
- Why sufficient / why not (one line): incentives and staking benefits are described.
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Evidence: —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): in the Tier‑1 sources, the utilities are described as economic (fees/rewards), without proof that they cannot be replaced by another payment asset.
- Evidence: Tier‑1 — https://docs.redbrick.land/introduction/what-is-redbrick/redbrick-creator-and-token-economy
- Why sufficient / why not (one line): protocol‑level irreplaceability is not substantiated.
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.redbrick.land/ | Litepaper: AI Engine, stack, onchain economy and platform KPIs. |
| Tier‑1 | https://docs.redbrick.land/introduction/what-is-redbrick/redbrick-creator-and-token-economy | $BRIC utilities (fees/rewards/staking) and the creator economy. |
| Tier‑1 | https://docs.redbrick.land/introduction/what-is-redbrick/usdbric-token-allocation | Allocation + release schedule and capped supply 1B. |
| Tier‑1 | https://bscscan.com/token/0xb40f2e5291c3Db45AbB0Ca8DF76F1C21E9f112a9 | The BRIC contract and max total supply (1B). |
No comments to display
No comments to display