Sysnode is a public dashboard for the Syscoin Sentry Node ecosystem. It gives operators, builders, and community members a clear view of network health, Sentry Node distribution, governance activity, reward context, and SYS market data in one place.
Live site: sysnode.info
Syscoin Sentry Nodes provide an incentivized full-node layer that strengthens network availability, supports decentralized governance, and contributes to finality and resilience across the Syscoin network.
Sysnode is designed to make that information easier to read, easier to verify, and easier to act on. The interface focuses on practical operator context rather than raw data dumps.
- Current Sentry Node count, enabled nodes, locked supply, and ROI range.
- Sentry Node trend data over selectable time ranges.
- Current governance proposals, budgets, support, vote counts, voting deadline, and next superblock.
- Country-level Sentry Node distribution.
- SYS market context including price, volume, market cap, supply, and exchange links.
- Educational pages covering what Sentry Nodes are and how to approach setup.
- React 18
- React Router
- Chart.js via
react-chartjs-2 - Axios
- Create React App build tooling
The frontend currently reads live dashboard data from the Sysnode backend API:
https://syscoin.dev
The backend aggregates data from a Syscoin Core node, Sentry Node RPC responses, market APIs, and supporting network datasets. If you fork this project for another deployment, update the API base URL in:
src/lib/api.js
Install dependencies:
npm installRun the site locally:
npm run devOpen:
http://localhost:3000
Build for production:
npm run buildRun tests:
npm test -- --watchAll=falsesrc/
components/ Shared UI components
data/ Navigation, exchange, learn, and setup content
hooks/ Data loading hooks
lib/ API client and formatting helpers
pages/ Main dashboard pages
parts/ Header, footer, and layout parts
Community issues and pull requests are welcome. The best contributions keep the dashboard accurate, readable, and useful for real Sentry Node operators.
When contributing:
- Keep UI changes clear and accessible on desktop and mobile.
- Avoid committing generated files such as
build/ornode_modules/. - Keep API response shape changes coordinated with the backend.
- Include tests for formatting, calculations, or data transformation logic where practical.
- Treat governance and operator workflows carefully. Anything related to voting keys, signatures, private keys, or node control should be designed with security review in mind.
This frontend should not contain private keys, RPC credentials, server secrets, or privileged voting credentials. Sensitive operations should be handled by secure backend services or wallet flows designed specifically for that purpose.
If you discover a security issue, please avoid opening a public issue with exploit details. Contact the maintainers privately first so it can be reviewed responsibly.