npm run grant:proof before submissions.RWA compliance
Chainlink RWA alignment (in progress)
Property share transfers use permissioned on-chain compliance (REOC profile D). DTA-style subscribe/redeem, NAV feeds, and Proof of Reserve gates are rolling out per our public compliance matrix. Play raffle drops are separate from tokenized property securities.
- Not Chainlink ACE certified until partner sandbox + audit evidence is published.
- PoR attests declared backing — not government land registry title.
- Illustrative ROI on this page is not NAV or investment advice.
Thesis (for discussion)
Collectors and travelers already chase culture — but odds and fulfillment are too often opaque. We combine fair, inspectable drops with an app layer that makes participation legible: wallets, marketplace, missions, and XP tied to Building Culture Coin ($BCC) as the in-app economic story—without claiming guaranteed returns on any token.
Where product lives
Three entry points, one narrative: the Capital umbrella, the live app experience, and the BUILDCHAIN game loop.
app.buildingcultureid.space
Umbrella brand for on-chain culture and savings-club positioning—treasury narrative, compliance-conscious rollout, and room for ecosystem partnerships.
Visit site ↗App
Primary product surface: wallet, marketplace, missions, XP / points ledger, community profile, and experiments such as x402-protected APIs—where players actually stack BCC story and receipts.
app.buildingcultureid.space ↗Game
BUILDCHAIN loop: fair raffle tickets for real-world assets, drops, leaderboard, and campaigns—designed so odds and settlement stay inspectable on-chain.
game.buildingcultureid.space ↗Impact products (Austria)
BC-operated public-good betas — guidance and tooling only, not legal or medical advice.
Ankommen AI
Multi-agent companion for newcomers in Austria — housing, benefits, documents, jobs, and translation in 14 languages. Beta at the BC subdomain.
ankommen.buildingcultureid.space ↗KinderStimme (For Kids)
Open Child Protection Protocol — KI-Familienagent, encrypted evidence vault with Base anchors, and family collaboration for Austrian proceedings. Beta; not legal advice.
forkids.buildingcultureid.space ↗$BCC + BUILDCHAIN (accurate constraints)
$BCC is how we discuss value inside the product: balances, “Get $BCC” previews, and mission-driven storytelling. Where configured, the UI can read an ERC20 balance; where not, we label demo balances honestly.
Settlement today follows the deployed raffle path in the chain’s native gas token unless and until contracts accept $BCC for mints—we say that loudly so expectations stay aligned (FAQ).
Why this can compound
- On-chain receipts for tickets and campaigns reduce “trust me” moments.
- Marketplace + campaign surfaces create repeatable fee opportunities when volume follows.
- Social distribution is wired but early: Grove auto-post requires credentials; pulse ingestion shows real post counts in the traction table — often zero until streams run.
- Optional Strapi-backed community content lets partners ship stories without redeploying the core app.
What we can prove today
Every figure below is reproducible from production Postgres, public Base RPC reads, or documented APIs. We do not inflate social reach, mint counts, or GMV. Zeros mean zero — not “coming soon” marketing.
Loading…
Product & wallets
| Metric | Count | Notes |
|---|---|---|
| Member profiles (DB) | Wallet-first accounts in production Postgres | |
| Members with wallet on file | Not MAU — cumulative sign-ups | |
| Farcaster-linked members | FID stored on member row | |
| Telegram-linked accounts | SocialAccount platform=telegram | |
| Waitlist signups | waitlistEntry table | |
| Culture Points (ledger net) | Sum of PointLedger.delta | |
| Activity events (24h) | ActivityEvent rows in last 24h |
Social (real ingestion)
| Metric | Count | Notes |
|---|---|---|
| Ingested Farcaster posts | stream off (no NEYNAR_API_KEY) | |
| Ingested X posts | stream off | |
| Ingested Meta / TikTok / IG | Optional streams — mostly off in prod | |
| Native pulse comments | Curated in-app comments | |
| Verified social links (all platforms) | SocialAccount.verified=true | |
| Grove outbound: X | not configured — no auto-posts | |
| Grove outbound: Farcaster | not configured — no auto-posts | |
| Grove outbound: Telegram | not configured |
Mints & commerce
| Metric | Count | Notes |
|---|---|---|
| BCC total supply (on-chain) | ERC-20 totalSupply on Base — fair launch, no inflationary mint | |
| Raffle ticket NFTs minted | RaffleTicketCampaign.totalSupply() | |
| Agent share NFTs minted | AgentShareCampaign.totalSupply() | |
| Stripe pack purchases (app) | PackPurchase rows — revenue may be $0 | |
| Panic voucher NFTs minted (app) | — pending in DB | |
| BCC settlements credited | — pending treasury settlement | |
| Points → BCC redemptions | PointRedemption rows (gate usually off pre-TVL) | |
| Marketplace listings live | thirdweb Marketplace on Base |
Market (public pools)
| Metric | Count | Notes |
|---|---|---|
| BCC Uniswap liquidity | DexScreener via /api/market/bcc | |
| BCC DEX volume (24h) | Public pool data — not platform GMV | |
| BCC pack discount (configured) | VITE_BCC_DISCOUNT_BPS when packs enabled |
Machine-readable bundle: GET /api/investors/traction. On-chain bytecode audit: /grant-proof. Client refresh: — UTC.
Business model (directional)
Revenue can mirror how culture platforms already monetize—primary mint fees, marketplace fees, sponsored experiences, and eventually premium APIs — while keeping disclosures honest when drops settle in native tokens today.
| Line | Notes (fill with finance) |
|---|---|
| Marketplace / protocol fees | thirdweb marketplace live on Base (0x3af9…AEcf4); platform fee bps set per env when published |
| BCC commerce discount | 11.11% pack discount (1111 bps) when VITE_BCC_DISCOUNT_BPS is configured |
| Campaign & mint fees | On-chain raffle / art hub contracts on Base — see grant-proof bytecode audit |
| Sponsored drops & experiences | Partnership pipeline — not disclosed publicly |
| API / infra (e.g. x402-style) | Rentable trading agent + x402 routes — worker optional (/api/trading/health) |
Economics & fundraising (what we publish)
Angels typically underwrite category creation, distribution, and execution—not pre-filled spreadsheet sliders. This page shows audited live metrics above; it does not state an open round size, post-money valuation, or ownership slice.
| Topic | Public stance |
|---|---|
| Round size / valuation | Not disclosed here — NDA + term sheet |
| Cap table / ownership % | Not disclosed here — NDA + term sheet |
| Live ops & on-chain proof | /grant-proof + traction table on this page |
| Long-horizon scenario deck | /plan — labeled illustrative models only, not current traction |
| Live-call scenario sliders | /investors/workshop — password-gated, noindex; shared privately on advisor calls |
How we talk about outcomes (qualitative)
- Execution focus: ship inspectable drops, wallet UX, and marketplace rails before scaling marketing claims.
- Upside path: repeatable campaigns + partners if volume follows — not assumed in public numbers.
- Downside risks: regulatory scrutiny, fulfillment ops, chain/custody dependencies — see risks below.
Use of funds (directional outline)
Categories we discuss with investors in private materials — not a public ask size or instrument (SAFE vs priced equity vs token) on this site.
- Product engineering: marketplace reliability, wallet UX, campaign tooling.
- Growth: creator partnerships, drops programming, community.
- Compliance & ops: counsel retainer, fulfillment playbooks, accounting.
- Infrastructure: RPC, indexing, observability, security reviews.
Treasury & entity architecture (discussion outline)
High-level institutional framing for diligence conversations only. Jurisdictions, labels, and flows must be confirmed with qualified tax and securities counsel before any paid marketing, onboarding, or capital movement.
When funds route through a Delaware entity
Delaware works well when it is used for a narrow, well-documented purpose—not as a catch-all for every asset or operating role.
Strong fits
- Funding gateway
- Investor onboarding vehicle
- Treasury coordination entity
- Token subscription vehicle (with counsel-approved terms)
- Optional trading entity (if licensed / permitted)
Poor fits
- Direct real estate owner (use SPVs)
- Global operating company
- Unmanaged DAO treasury (no legal counterparty clarity)
Illustrative stack (not a commitment to current org chart)
Clean capital flow (example)
- 01
Investor intake
Investors may contribute USDC, USD, or EUR into a Delaware gateway entity—only under counsel-approved subscription documents and bank / stablecoin rails.
- 02
Gateway operations
The Delaware vehicle handles onboarding, subscription agreements, KYC / AML, and treasury intake—not discretionary marketing claims about trading performance.
- 03
Allocation downward
Capital can be allocated to Swiss holding layers, token SPVs, property SPVs, and treasury reserves according to board / manager authority and governing documents.
- 04
Yield flows upward
Rental income, exits, refinancing, and treasury profits can flow back through SPVs and holding companies with transparent waterfall logic—again, only as counsel approves.
Why Delaware is often chosen
- Flexible investor and LLC agreement design (including web3-style mechanics).
- Often easier U.S. investor onboarding vs. some European operating companies alone.
- Familiar to crypto-native funds and U.S. angels.
- Room to embed DAO signals, treasury rights, and governance mechanics in contracts—if lawfully structured.
Material risks to diligence
- FATCA / CRS: international investors through a U.S. gateway can trigger reporting—plan for accounting, AML / KYC, investor registry, and tax reporting early.
- SEC / securities: if tokens look like profit rights, investors expect returns, there is broad secondary trading, or DAO governance resembles a pooled investment vehicle, regulators may treat the program as a securities offering. Positioning must be counsel-led—not marketing-led.
Safer public framing (examples)
Avoid marketing lines like “send funds to Delaware and we trade them.” That pattern invites investment-company and securities scrutiny. Prefer counsel-approved narratives such as treasury management, reserve allocation, ecosystem treasury, and strategic liquidity—while real estate and operating businesses remain the documented core.
A Delaware LLC can be described as a private investment membership vehicle with defined rights—not a public crypto token issuer—when facts and documents support that distinction.
DAO integration (enforceability pattern)
A practical model: the DAO publishes governance signals; the Delaware operating agreement explicitly recognizes those signals; multisig or managers execute approved actions; a foundation or steward retains narrowly defined emergency powers. That stack aims for legal enforceability and operational clarity without pretending an on-chain vote replaces corporate law.
Delaware LLC
Investor intake, subscriptions, treasury coordination at the gateway.
Swiss holding
Treasury management, SPV coordination, IP, and operating alignment where appropriate.
DAO
Voting, proposals, transparency, reputation, and treasury signaling.
Foundation / steward
Legal protection, emergency governance, and protocol integrity within charter limits.
Building Culture treasury system (conceptual map)
- Delaware — investor gateway
- Switzerland — treasury + institutional layer
- Liechtenstein — governance / legal wrapper where used
- DAO — community coordination
- SPVs — property isolation and ring-fenced risk
Long-term story: real estate as the stable foundation, treasury as a disciplined growth engine, DAO as coordination, token as ecosystem access and governance where lawfully designed—not a promise of yield by slogan.
Risks & mitigations
- Regulatory: promotions and token mechanics vary by region — run campaigns only with appropriate licenses and disclosures.
- Execution: real-world fulfillment is operationally heavy — invest in partner SLAs and player support.
- Market: crypto UX friction and volatility — mitigate with clear settlement messaging and chain choices aligned with users.
Appendix — deeper dives
- Treasury & entity architecture — Delaware gateway, Swiss layer, DAO signals, SPV isolation (discussion only).
- Mission ($BCC) — treasury narrative, genesis claim context.
- About — product thesis and loop.
- FAQ — mechanics, disclaimers, “what is BUILDCHAIN”.
- Roadmap — what ships next.