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 ↗$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 hooks (e.g. Farcaster / Warpcast flows where configured) can shorten acquisition loops for culture-native audiences.
- Optional Strapi-backed community content lets partners ship stories without redeploying the core app.
Traction (placeholders)
Replace with counsel-approved metrics. Example labels only.
| Signal | Example / TBD |
|---|---|
| Monthly active wallets | — |
| Secondary GMV (proxy) | — |
| Campaign mint volume | — |
| Brand / venue partners | — |
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 | TBD — attach take rate when stable |
| Campaign & mint fees | TBD — per deployment |
| Sponsored drops & experiences | TBD — partnership pipeline |
| API / infra (e.g. x402-style) | TBD — optional premium tier |
ROI framing & illustrative economics
Angels typically underwrite category creation, distribution, and execution speed—not a spreadsheet cell. Below is a qualitative band, placeholder cap table lines, then a toy scenario you can tune in conversation with advisors.
Illustrative outcome bands (not predictions)
- Base case story: niche liquidity + steady drops → fees fund core team and infra; token narrative stays subservient to product.
- Upside story: cultural moments spill into mainstream acquisition; marketplace + campaigns scale GMV; partnerships repeat.
- Downside risks: regulatory scrutiny on promos, execution on fulfillment, chain / custody dependencies — see risks below.
| Cap table line | Placeholder |
|---|---|
| Founders / early team | — % |
| Seed / angel | — % |
| Option pool | — % |
| Strategic / advisors | — % |
Illustrative scenario (toy model)
Drag sliders to stress-test stories, not precision. Outputs are rounded bands for conversation with advisors—not projections.
$0.25M – $20M
Used only for a coarse “slice of the cap table” story if this round were primary.
Indicative ownership sold (toy)
11.1%
raise ÷ post-money — simplified; excludes option pools and prior rounds.
Illustrative annual fee revenue
~$2.16M
(Monthly GMV proxy × 12 × take rate). Not profit; excludes infra, grants, and volatility.
Round & use of funds (outline)
- 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.
Instrumentation (SAFE vs priced round, jurisdiction, token vs equity) belongs in your term sheet — not on this page.
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.