Back to the application

Real estate tokenization and claims history

Real estate assets now support property-specific compliance, valuation, and tenant tracking while the claims history drawer surfaces verification attempts and approval timestamps for complete audit trails.

Release overview

Real estate tokenization extends the asset framework with property-specific fields—location, valuation, tenant leases, and title documents—so operators can represent buildings, land parcels, and real estate funds on-chain with full regulatory context.

Claims tracking received a dedicated history drawer that shows verification attempts, rejections, and approval timestamps, giving compliance teams the audit trails they need without exporting to external systems.

User facing features

  • Real estate asset type — tokenize properties with address, valuation, tenant details, and title documents to support fractional ownership and REIT-style structures (#4200, #4291).
  • Claims history drawer — click any claims table row to see verification attempts, rejections, and approval timestamps for audit trails (#4292).
  • Enhanced real estate UI — improved property form validation, document upload, and tenant tracking to streamline onboarding (#4291).

Quality, reliability, and operations

  • Equity mint and transfer tests — restore Playwright coverage for equity asset flows after recent UI changes broke selectors (#4272).
  • Open docs in new tab — preserve app state when navigating to external documentation links (#4294).
  • Route data preloading — use ensureQueryData in loaders to hydrate critical queries on navigation, reducing spinners and layout shifts (#4234).

Developer experience

  • Dynamic token factory implementations — configure token factory addresses via environment variables instead of hard-coded constants, supporting multiple networks per deployment (#4311).
  • Compliance module environment variables — externalize compliance module addresses to simplify multi-chain deployments (#4309).

Upgrade checklist

  1. bun install to sync dependencies for real estate modules.
  2. Run bun run --cwd kit/contracts test to verify token factory and compliance module changes.
  3. bun run --cwd kit/dapp db:push to apply real estate schema migrations.
  4. Deploy updated contracts with bun run --cwd kit/contracts deploy and set TOKEN_FACTORY_ADDRESS and COMPLIANCE_MODULE_ADDRESS environment variables in your .env.local.
  5. bun run --cwd kit/e2e test:e2e:ui --grep "real estate" to verify property creation and transfer flows.

References

Kubernetes deployment
Global search