How vedhu01/blockchain works
The repository tree exposes only a web page and PowerShell server; the README describes a much broader platform, but its nested web, mobile, contract, and data sources are not present in the supplied tree. The principal documented journey is an investor entering a role-specific portal, accessing art and trading capabilities, and using permissioned tokenization and compliance controls. Documented-only subsystems are included with null paths; their implementation and runtime connections cannot be verified from the available files.
Main entry points: index.html Stakeholder Portal · server.ps1 REST API and WAF
Components 15
Web Experience
- Stakeholder Portal
index.html - Art Gallery
- Fractional Trading
- Portfolio and Claims
Platform Services
- REST API and WAF
server.ps1 - DID and KYC
- IBFT Validators
- Bank Escrow
Art and Custody
- Artwork Records
- Vault Provenance
- IPFS Storage
Tokenization and Governance
- ERC-3643 Tokens
- ZK Verification
- Market and Governance
Other components
- Investor
Connections 16
- Investor → Stakeholder Portal: enters
README.md - Stakeholder Portal → Art Gallery: offers
README.md - Stakeholder Portal → Fractional Trading: offers
README.md - Stakeholder Portal → Portfolio and Claims: offers
README.md - Stakeholder Portal → REST API and WAF: uses API
- REST API and WAF → DID and KYC: supports KYC
- REST API and WAF → IBFT Validators: serves network
- Art Gallery → Artwork Records: presents works
README.md - Artwork Records → IPFS Storage: references media
README.md - Vault Provenance → Artwork Records: anchors artworks
README.md - Fractional Trading → Market and Governance: supports orders
README.md - Market and Governance → ERC-3643 Tokens: fractionalizes
README.md - ERC-3643 Tokens → DID and KYC: checks eligibility
README.md - ZK Verification → DID and KYC: proves accreditation
README.md - Portfolio and Claims → Bank Escrow: shows reserves
- Portfolio and Claims → Market and Governance: claims dividends
README.md