How razwantanvir/forktree-repo-platform works
BlockchainForkTree is a multi-chain fork registry and healthcare-data platform with a web dashboard. Users inspect chains and records, search the fork tree with BFS or DFS, manage governance and consent, and create new forks. The server routes dashboard requests to the fork-tree service, which uses a JSON-RPC contract client against the simulated multi-chain engine. Deployment and seeding establish the repository and data-chain contracts and initial topology. Governance, patient records, and consent are documented capabilities; some implementation details are unsampled, so their internal links are not expanded.
Main entry points: forkTreeService.js Fork tree service · contractClient.js Contract client · chainEngine.js JSON-RPC engine · server.js API server
Components 21
Dashboard and API
- Web dashboard
public/app.js - API server
server.js
Fork Tree Services
- Fork tree service
services/forkTreeService.js - BFS / DFS search
services/forkTreeService.js - Governance and consent
services/forkTreeService.js - Patient records
services/forkTreeService.js - Contract deployment
scripts/deployContracts.js - Topology and data seeding
scripts/seedForkTree.js - Search CLI
scripts/searchData.js
Multi-Chain Runtime
- Contract client
services/contractClient.js - JSON-RPC engine
engine/chainEngine.js
Contracts and State
- Contract artifacts
contracts/compiledArtifacts.js - Fork registry contract
contracts/StoreForkEvent.sol - Chain data contract
contracts/BlockData.sol - Consortium governance
contracts/ConsortiumGovernance.sol - Network configuration
config/networkTopology.json - Stakeholder configuration
config/consortiumStakeholders.json - Deployment addresses
config/deployments.json - Persisted chain state
engine/chainEngine.js
Other components
- Dashboard user
- JSON-RPC endpoints
Connections 28
- Dashboard user → Web dashboard: uses
README.md - Web dashboard → API server: requests API
public/app.js - API server → Fork tree service: routes requests
server.js - API server → JSON-RPC engine: starts nodes
server.js - API server → Contract deployment: invokes deployment
server.js - API server → Topology and data seeding: invokes seeding
server.js - Fork tree service → Contract client: calls contracts
services/forkTreeService.js - Fork tree service → BFS / DFS search: performs traversal
README.md - Fork tree service → Governance and consent: manages proposals
server.js - Fork tree service → Patient records: reads and writes
server.js - Search CLI → Fork tree service: runs search
scripts/searchData.js - Contract deployment → Contract client: deploys through
scripts/deployContracts.js - Topology and data seeding → Contract client: writes through
scripts/seedForkTree.js - Contract deployment → Contract artifacts: uses ABI
scripts/deployContracts.js - Topology and data seeding → Contract artifacts: uses ABI
scripts/seedForkTree.js - Topology and data seeding → Network configuration: loads network
scripts/seedForkTree.js - Contract deployment → Network configuration: loads network
scripts/deployContracts.js - Contract client → JSON-RPC endpoints: sends JSON-RPC
services/contractClient.js - JSON-RPC engine → JSON-RPC endpoints: serves endpoints
README.md - JSON-RPC engine → Contract artifacts: uses interfaces
engine/chainEngine.js - JSON-RPC engine → Network configuration: loads topology
engine/chainEngine.js - JSON-RPC engine → Stakeholder configuration: loads roles
engine/chainEngine.js - JSON-RPC engine → Persisted chain state: persists state
README.md - Contract client → Fork registry contract: accesses registry
- Contract client → Chain data contract: accesses chain data
- Contract client → Consortium governance: accesses governance
- Topology and data seeding → Deployment addresses: reads addresses
scripts/seedForkTree.js - Fork tree service → Deployment addresses: reads addresses
services/forkTreeService.js