// the find
FinAegis/core-banking-prototype-laravel
Open-source core banking platform — 61 DDD domains with event sourcing, CQRS, and a schema-first GraphQL API. Multi-asset accounts, exchange, lending, compliance, x402/MPP machine payments, and a non-custodial wallet backend. Laravel 12 / PHP 8.4. Reference implementation: the GCU basket currency.
A Laravel 12 / PHP 8.4 core banking reference implementation with 61 DDD domain modules, event sourcing via Spatie, CQRS, and a Lighthouse PHP GraphQL API. The GCU basket currency serves as the primary working example. Aimed at developers who want to study modern fintech architecture patterns in PHP rather than build production banking software.
The event sourcing implementation goes deeper than most tutorials — Event Store v2 includes domain-specific event tables, upcasting for schema migrations, replay tooling, and projector lag monitoring, which is the part most examples skip. PHPStan Level 8 and 4,900+ Pest tests with parallel execution is genuine discipline, not checkbox coverage. The modular plugin system with `domain:install`, dependency resolution, and enable/disable without data loss is well thought out for a monorepo of this complexity. The GCU basket currency example — weighted assets, democratic governance votes, automatic rebalancing, transparent NAV — is a concrete, end-to-end working demonstration of financial primitives rather than a TODO stub.
The version number is a red flag: v7.16.0 with 176 stars means they're shipping major versions faster than they're gaining users. The feature table — post-quantum cryptography, RAILGUN privacy, ZK-KYC, Solana, Apple IAP, Bridge.xyz, x402 micropayments, AI agent escrow — reads like AI-assisted feature stuffing rather than organic development, and it shows in the depth; many of these are thin adapter wrappers, not real implementations. The project simultaneously claims SOC 2 Type II and PCI DSS readiness in its feature table and then disclaims 'a security audit and compliance review are required before any production deployment' — these two statements cannot coexist, and the contradiction should make anyone pause before building on it. MySQL is listed as the primary database ahead of PostgreSQL for an event-sourced system, which is an odd choice given that event sourcing benefits substantially from PostgreSQL's JSONB handling and richer indexing.