Skip to content

feat(wallet): make crypto rail routing config-driven - #57

Merged
zaxovaiko merged 1 commit into
devfrom
worktree-crispy-herding-owl
Aug 5, 2026
Merged

feat(wallet): make crypto rail routing config-driven#57
zaxovaiko merged 1 commit into
devfrom
worktree-crispy-herding-owl

Conversation

@zaxovaiko

Copy link
Copy Markdown
Member

Summary

Make wallet crypto rail routing config-driven instead of a hardcoded currency set.

Why

railFor hardcoded a BTC/ETH/USDT set. Adding a custody vendor's full asset list required a core edit. Now the default adds USDC and platformConfig.wallet.cryptoCurrencies lets an operator override the set per-deployment, so onboarding a new asset is a config change.

Worth knowing

  • pnpm verify is green (typecheck + lint + boundaries + module-shape + tests)
  • pnpm check:drift is green (catalog / OpenAPI not stale) - run pnpm regen if not
  • New cross-module talk goes through events / command ports / contracts / the /schema subpath (no direct module imports)
  • New data tables carry tenantId and are RLS-covered (pnpm regen runs gen:rls) - N/A, no new tables
  • No secrets, real player data, or internal/customer names added

railFor was a hardcoded BTC/ETH/USDT set. Add USDC to the default and let
platformConfig.wallet.cryptoCurrencies override it per-operator, so adding a
custody vendor's full asset list is a config change, not a core edit.
@zaxovaiko
zaxovaiko merged commit e7f4395 into dev Aug 5, 2026
2 checks passed
@zaxovaiko
zaxovaiko deleted the worktree-crispy-herding-owl branch August 5, 2026 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant