Skip to content

assmore22/sourcepulse

Repository files navigation

SourcePulse

Live Links

The project is a source-backed GenLayer workflow, with frontend views designed around evidence status rather than generic contract buttons.

SourcePulse Brief

  • Project folder: projects/project-09-sourcepulse
  • Frontend: Next/Vite-style app folder
  • Contract package: contracts/ plus deployment.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...

SourcePulse On Studionet

Evidence Mechanics

  • 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.

Operator Preview

cd <this-repository-folder>
npm install
npm run dev

Open the dev server URL printed by npm.

Smoke Transactions

Public Repo Safety

  • 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.

About

Source-watch intelligence console for snapshots, alerts, challenges, and GenLayer-backed source review.

Topics

Resources

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors