A reusable open-source trust layer for verified-human, age, passkey, pseudonymity, anti-spam, and policy assertions.
Join
Help build safer public technology.
VoxonLabs needs people and institutions who can contribute concrete work, review, credibility, capacity, and care. The foundation track is Voxon Shield; the first application proof is EverCommons Social.
What we need
Useful help is specific, finite, and aligned with the rules.
We are not looking for vague hype. We need reviewable contributions that move the first public proof toward a safe 100-user adult pilot.
Developers
Shield API sketches, assertion verification, passkey prototypes, frontend, media upload, feeds, export, accessibility, and tests.
Designers
Onboarding, feed, upload, explicit-content controls, report/appeal, creator dashboard, and capacity UI.
Privacy and security reviewers
Minimal assertions, pairwise pseudonyms, provider boundaries, threat models, data inventory, upload abuse, and launch boundaries.
Creators
Cross-post rights-clean original content later and help test whether creator economics are understandable.
Organizations
Offer measured resources, research help, legal review, moderation expertise, credits, or pilot partnerships.
Universities and professors
Contribute research review, student projects, privacy-preserving identity methods, safety methods, sustainability measurement, or public-interest labs.
Future platform
What the platform should offer over time.
EverCommons starts with social because photo/video social networks shape culture and attention. Voxon Shield should become the shared trust layer for future applications that need human, age, eligibility, messaging, or abuse assertions.
Profiles, media, comments, feeds, creator pages, transparent discovery, and export.
Shadow ledgers first, then published formulas for creators, maintainers, infrastructure, safety, reserves, and public benefit.
Explicit-content controls, reporting, blocking, appeals, anti-spam systems, and age-aware design before broad launch.
Future news or civic flows should show claims, sources, corrections, conflicts, funding, and why something is trusted.
Measure cost, energy, storage, egress, provider concentration, and environmental intensity per useful activity.
Universities, nonprofits, cooperatives, and responsible companies can help without buying user data or governance control.