- App: https://sourcepulse.vercel.app
- Repository: https://github.com/assmore22/sourcepulse A GenLayer-powered source-monitoring and change-verification protocol.
The project is a source-backed GenLayer workflow, with frontend views designed around evidence status rather than generic contract buttons.
- Project folder:
projects/project-09-sourcepulse - Frontend: Next/Vite-style app folder
- Contract package:
contracts/plusdeployment.json - Logo asset: FontAwesome satellite-dish (faSatelliteDish) + plain text wordmark 'SourcePulse'
- Build status: next build OK (9 routes, 0 type/lint errors); contract schema-valid; all 11 write methods executed on-chain; 17 read methods power the UI; RainbowKit+wagmi+viem+genlayer-js; D3 source-change timeline + GSAP command-log...
- QA notes: Browser QA 1440px + 390px: source monitor workbench (terminal command-log + D3 source-change timeline + alert drawer + sticky bottom action bar; terminal status rail top, command nav - no sidebar/tabs/cards) / watchlist detail (timeline, snapshots, alerts...
- Network: studionet (61999)
- Contract: 0x17E593B469A82BDA42f1b377ea14851C5D410856
- Deploy tx: 0xb329699f...1cadae
- Deployed at: 2026-06-22T17:16:41.026Z
- Smoke writes recorded: 11
- Primary source:
contracts/SourcePulse.py(36,072 bytes) - Public write/action methods: 11
- Read methods: 17
- GenLayer features: live web rendering, LLM adjudication, validator-comparative consensus, indexed storage, append-only collections
Typical flow: create_watchlist -> submit_snapshot -> resolve_challenge -> challenge_snapshot -> file_appeal -> archive_watchlist -> activate_watchlist
Useful reads: get_watchlist, get_snapshot, get_alert, get_challenge, get_appeal, get_profile, get_recent_watchlists, get_active_watchlists
The contract is deliberately larger than a one-method demo. It keeps lifecycle state, evidence records and read endpoints so the UI can show real project state instead of static copy.
cd <this-repository-folder>
npm install
npm run devOpen the dev server URL printed by npm.
- create_watchlist: 0x75279544...06ef45
- activate_watchlist: 0xd07f170d...9d1000
- submit_snapshot: 0x6b787037...353bd7
- assess_snapshot: 0xbda8bfe9...f167d0
- challenge_snapshot: 0x5df6af2f...bc5424
- file_appeal: 0xa935cbd2...83da90
- resolve_challenge: 0xe825efe8...b44de4
- resolve_appeal: 0x82d4233f...35dc0f
- Private keys and local vault files are not part of this repository.
- Public addresses, contract source, deployment metadata and frontend code are safe to publish.
- Vercel should receive only this project folder, never the workspace dashboard or vault data.