[ NEURALARC_REFERENCE_BUILD_—_EQUITYLEDGER ]
Blockchain Cap Table & Ownership Platform
What it is
Company and SPV ownership run as a programmable ledger — every issuance and transfer is a transaction, and the cap table can be reconstructed for any past date.
[ THE_PROBLEM ]
Why this existed
Ownership records rot as an organisation adds investors, SPVs, funding rounds, secondary transfers and employee allocations. The cap table lives in a spreadsheet, so there is no authoritative answer to what someone owned on a given date, no enforced transfer policy, and multi-party reconciliation happens by email.
[ WHAT_WE_BUILT ]
What we built
A cap-table and investor-management platform where the blockchain layer does more than record events. Entities — companies, SPVs, investment vehicles — each get their own ownership contract; ownership interests exist as digital units in classes (founder, investor, preference, property units, employee allocations, restricted), each with its own rules. The live dashboard shows the ownership breakdown and recomputes on every change; every investor has a profile carrying KYC status, wallet, units, ownership percentage, acquisition price and transaction history. Issuance runs through a governed flow — entity, investor, class, allocation, approval — and each issuance writes an immutable transaction reference. Transfers execute only after their gates pass: KYC verification, administrator or board approval, transfer agreement, payment confirmation, investor eligibility. The restriction logic lives in the contract itself — whitelisted investors only, maximum holder counts, restricted jurisdictions, locked periods, minimum holdings, per-asset rules — so the ledger enforces ownership policy rather than trusting the application to have checked it. Because every issuance, burn, transfer and corporate action (buyback, cancellation, split, consolidation, bonus allocation, dividend) is a timestamped transaction, the platform reconstructs the cap table as of any historical date. A distribution engine computes entitlements from an ownership snapshot date and issues per-shareholder statements with tax deductions and payouts; investors can generate blockchain-verifiable ownership certificates carrying a certificate ID, QR verification and transaction reference. Multi-SPV setups manage every property vehicle through one interface while keeping ledgers separate. Next.js front end, Node.js APIs, PostgreSQL, Solidity on Polygon/Base-class chains (ERC-20, ERC-1155 and custom permissioned contracts), embedded wallets plus WalletConnect, KYC/KYB provider integration, encrypted object storage for documents.
- Multi-entity support — companies, SPVs and investment vehicles each with their own ownership ledger
- Ownership classes (founder, investor, preference, property units, employee, restricted) with per-class rules
- Live cap-table dashboard that recomputes on every issuance and transfer
- Shareholder profiles with KYC status, wallet, units, ownership %, acquisition price and transaction history
- Governed issuance flow writing an immutable transaction reference for every allocation
- Transfers gated on KYC, administrator or board approval, transfer agreements and payment confirmation
- Restrictions enforced in the contract: whitelists, holder caps, jurisdiction locks, lock-ups, minimum holdings
- Historical cap-table reconstruction for any past date from the transaction record
- Corporate actions: buybacks, cancellations, splits, consolidations, bonus allocations, dividends
- Distribution engine computing entitlements from an ownership snapshot, with per-shareholder statements
- Blockchain-verifiable ownership certificates with certificate ID, QR verification and transaction reference
- Multi-SPV management through one administrative interface with strictly separate ledgers
[ HOW_IT_IS_USED ]
How a company uses it
A property-SPV platform, private company or fund administrator replaces spreadsheet cap tables with a ledger where "who owned what on which date" is a query rather than an archaeology project, transfers execute only when the rules allow, and investors hold certificates anyone can verify independently.
Built with
[ COMMON_QUESTIONS ]
Questions clients ask
Why does a cap table need a blockchain at all?
For enforcement and reconstruction, not currency. A database can hold the same data, but it cannot stop a non-compliant transfer from being recorded, and "who owned what in March" becomes an email thread. Here the contract enforces the transfer policy, and every issuance and transfer is a timestamped transaction — so the historical cap table is a query, and nobody has to trust anyone's copy of a spreadsheet.
What rules can the smart contract actually enforce?
Whitelisted-investor-only transfers, maximum holder counts, restricted jurisdictions, locked holding periods, minimum holdings and administrator transfer approval. The point is that a transfer which violates policy does not execute — rather than executing and being flagged afterwards, which is how spreadsheet cap tables fail.
Can this manage multiple property SPVs in one place?
Yes — that is the designed case. Each SPV gets its own ownership ledger and contract, so ledgers never mix, while a central administrator runs every entity, issuance and corporate action from one interface and investors see all their holdings in a single portal.
[ RELATED_WORK ]
Similar builds
NeuralArc reference build — YieldX
Tokenised Revenue-Sharing Platform
Fractional investment in revenue-generating assets, with a blockchain underneath doing the ownership, eligibility and distribution accounting.
Read case studyNeuralArc reference build — ChainVerify
Blockchain Document Verification Infrastructure
Documents anchored to a blockchain by their SHA-256 hash, so anyone can verify a file is the exact version that was registered — without the document ever being public.
Read case studySME retail & distribution
Billing Workspace with an Embedded Copilot
A billing app where the assistant can actually operate the app, not just describe it.
Read case studyIs this close to your problem?
Most engagements start with a version of something on this page. Tell us what is different about yours and we will tell you what it changes.
Start a conversation