welcome to WAVS dashboard + wizard
operating a node today means stitching together triggers, components, and submissions while managing logs and CLI workflows
WAVS dashboard reduces this complexity
run nodes, configure services, monitor execution—all in one place
Digital human rights in a massive industry.
This can be extremely overwhelming, because you need to keep up with so many topics, people, and initiatives.
But also, it's an invitation, my gosh, to entanglement (trendy word), or just connection between so many different organisms. In @web3privacy, we expand our spores covering areas of
- investigative journalism as in @FreedomofPress
- data workers as in @timnitGebru
- politics of gen AI as in @Info_Activism
- mesh networks like BitChat
- localism
- internet censorship mapping @OpenObservatory
- resistance AI
- feminist orgs protecting marginalised groups
- open knowledge foundations from @internetarchive to @Wikimedia
- flagship rights orgs like @accessnow
- artists working on surveillance tech mapping
- anti-authoritarian practical stack like @TutaPrivacy
- new encrypted messengers https://t.co/inXU3b5zf5
- activists for various global causes x war conflicts, non-democratic regimes from Iran to Ukraine
- mercenary software mapping, advocacy like https://t.co/iVQcFAJmuT
- whistleblower tech like @SecureDrop
- tech workers unionising against Big Tech
- free software for young adults
- multi-generational hacktivism @DyneOrg
Donna Haraway & Anna Tsing would be proud!
keep3r network, gelato, and chainlink automation all share the same architectural weakness.
an external bot must be online, funded, and responsive at the exact moment your protocol needs execution
WAVS internal events are native, not another third party point of failure
Banks are saying it plainly: adapt, or be replaced as "lower-value human capital."
This is what it looks like when the social contract dissolves.
The response has to be bigger than policy. Regulation alone can’t fix a logic that sees people as diminishing returns.
We need to rebuild the system – so technology serves the public, and people remain the point.
💚
crypto is still stuck in 2013 paying oracle providers.
enterprise systems figured out years ago that connecting directly to data sources beats the middleman. that why 85% of enterprise systems run on event-driven architectures
WAVS is the event-driven framework for crypto🌊
WAVS turns three vendor categories: oracles, bridges, cron jobs into three event types in one framework.
that's not a feature slapped onto a blockchain. WAVS is a completely reimagined event-driven architecture for distributed applications
chainlink only supports ~600 data feeds but the internet has over 200 million active APIs.
this isn't a data problem, it's an integration problem.
WAVS offchain events connect to any of them. no coverage list. no middleman. no permission needed 🌊
nature 🤝 systems
what you water grows
sunlight, soil, attention, capital
they all determine what thrives
if we start funding regeneration
that’s what takes root
the future isn’t random
it’s cultivated
help fund what matters ↓
https://t.co/BpUYCv6lvR