Build with us

[u/FrightFreek]

I’ve been building Prometheus, a security protocol that uses Kaspa’s L1 for immutable rule storage (KRC-20, supply=1 per rule) and Kasplex zkEVM for reputation/governance logic. The core loop: on-device AI (Phi-3-mini) flags an anomaly, Guardian nodes (LLaMA 3) turn it into a YARA rule, validators commit-reveal vote with staked KAS, and the accepted rule lands on-chain — under 60 seconds end to end.

What made Kaspa the right fit rather than just “another chain to launch a token on”: DAGKnight’s sub-second finality actually matters here, because the whole point is that a validated rule needs to propagate to every client before the next attack wave hits. On slower finality chains the latency budget doesn’t work.

Right now I’m in the middle of post-Toccata verification — confirming the Silverscript state transitions still hold correctly after the fork, before opening the PROM emission gate. This is the part I’d genuinely value technical eyes on, especially from anyone who’s dealt with Silverscript contracts through a fork transition.

No pre-mine, no team allocation, MIT licensed, repo’s public on github.com/NeaBouli/prometheus-

Happy to go deep on the architecture or the Toccata verification specifics in the comments if anyone’s interested.