Cyberstorm Schemas

Building Verifiable Professional Reputation as an Asset Class

The Vision: Your Code Contributions as Verifiable Assets

In today's digital economy, developers build their careers through contributions to open source projects, but this professional reputation is trapped within platforms and impossible to verify across contexts. What if your GitHub contributions, code reviews, and technical expertise could become portable, verifiable assets that follow you throughout your career?

Cyberstorm Schemas provide the foundational data structures for building this future—where every meaningful contribution to software projects becomes a cryptographically-verified credential that developers truly own.

Monorepo Architecture

This repository contains two complementary Protocol Buffer modules that power the Cyberstorm ecosystem:

🏛️ Attestor Module

The Reputation Engine - Core schemas for building verifiable professional reputation:

• Identity System: Cryptographic linkage between GitHub accounts and Ethereum addresses
• Repository Registry: On-chain repository registration with ownership proofs
• Contribution Tracking: Structured data for PRs, issues, and code reviews
• Webhook Processing: Real-time event processing from GitHub to blockchain

📋 BSR: buf.build/cyberstorm/attestor

🔐 Crypto Module

IPLD Cryptographic Primitives - Content-addressed data structures:

• Content Identifiers (CID): Self-describing content addressing
• Encryption Keys: CEK/KEK management for secure content
• Context References: Building verifiable content graphs through IPLD links
• Modern Standards: ChaCha20-Poly1305 for EVM ecosystems

📋 BSR: buf.build/cyberstorm/crypto

How It Works: The Three-Step Reputation Network

1. Decentralized Identity (DID) Registration

Verifiably link your GitHub account to an Ethereum address, creating a cryptographic bridge between your development identity and blockchain-based credentials.

2. Repository Registration

Project maintainers register their repositories on-chain, establishing them as legitimate sources of verifiable contributions within the reputation network.

3. Contribution Attestation

High-value contributions—pull requests, issue resolutions, code reviews—against registered repositories, by registered identities, are automatically attested on-chain through the cyberstorm-attestor service.

Why This Matters for Developers

• Portable Reputation: Your verified contributions follow you across companies, platforms, and careers
• Proof of Expertise: Demonstrate technical skills with cryptographic proof, not just claims
• Network Effects: Join an ecosystem where verified reputation creates measurable professional value
• Future-Proof Career: Build assets that appreciate as the reputation network grows

Installation & Integration

Recommended: Buf Schema Registry

Attestor Module

buf generate buf.build/cyberstorm/attestor

Crypto Module

buf generate buf.build/cyberstorm/crypto

Add as Dependencies

# buf.yaml
deps:
  - buf.build/cyberstorm/attestor
  - buf.build/cyberstorm/crypto

Legacy Package Managers

TypeScript/JavaScript

npm install @cyberstorm-dev/schemas

Python

pip install cyberstorm-schemas

Go

go get github.com/cyberstorm-dev/schemas

Usage Examples

Identity Registration (Attestor Module)

TypeScript/JavaScript

import { Identity, Domain } from 'buf.build/cyberstorm/attestor';

// Register a GitHub identity with Ethereum address
const identity = new Identity({
  domain: new Domain({
    name: 'GitHub',
    domain: 'github.com'
  }),
  identifier: 'developer123',
  registrant: '0x742d35Cc6634C0532925a3b8D16f5a2C01234567',
  proofUrl: 'https://gist.github.com/developer123/abc123...',
  validator: '0x8ba1f109551bD432803012645Hac189451c24567'
});

Content Addressing (Crypto Module)

Python

from cyberstorm.crypto.v1 import CID, ContentEncryptionKey, EncryptionType

# Create self-describing content identifier
content_cid = CID(
    cid="bafkreig6mqa4p36x77qf5r3r7n4n4k3q3q3q3q3q3q3q3q3q3q3q3q3q"
)

# Set up content encryption
cek = ContentEncryptionKey(
    type=EncryptionType.ENCRYPTION_TYPE_CHACHA20_POLY1305,
    encrypted_key=b"encrypted_content_key_bytes..."
)

Repository Registration (Attestor Module)

Go

import attestorv1 "buf.build/cyberstorm/attestor/cyberstorm/attestor/v1"

// Register a repository for contribution tracking
repoRegistration := &attestorv1.Repository{
    Repository: &attestorv1.Repository{
        Domain: &attestorv1.Domain{
            Name:   "GitHub",
            Domain: "github.com",
        },
        Path: "awesome-org/amazing-project",
    },
    Registrant: registeredIdentity,
    ProofUrl:   "https://github.com/awesome-org/amazing-project/issues/42",
}

Getting Started: Join the Reputation Network

Ready to build verifiable professional reputation? Here's how to integrate these schemas into your development workflow:

For Repository Maintainers

Use cyberstorm-attestor-client to:

1. Register your repository using the Repository schema
2. Configure webhooks to automatically attest contributor actions
3. Build value for your community by making contributions verifiable

For Developers

Use cyberstorm-attestor-client to:

1. Register your identity linking GitHub to your Ethereum address
2. Contribute to registered repositories and earn verified attestations
3. Build portable reputation that transcends individual platforms

For Platform Builders

1. Import these schemas to build reputation-aware applications
2. Query attestations to understand developer expertise and activity
3. Create network effects by recognizing verified contributions

Built for Scale

• 🌐 Multi-language client libraries for seamless integration
• 🛡️ EAS-compatible schemas built on Ethereum Attestation Service
• 🧰 buf.build toolchain for professional Protocol Buffer development
• 🤖 Comprehensive CI/CD with automated testing and publishing
• 📊 Production-ready data structures for enterprise adoption

Release Process

Unified Release and Publish Workflow

The project uses a single GitHub Actions workflow for all release activities:

To create a new release:

1. Update version in all files to match (e.g., 1.0.5):

   • pyproject.toml (project.version)
   • package.json (version)
   • package-lock.json (version)

2. Go to Actions → Release and Publish → Run workflow

3. Enter the version number without "v" prefix (e.g., 1.0.5)

4. Select publishing options:

   • ☐ Publish to TestPyPI (optional, for testing)
   • ☐ Publish to PyPI (optional, for production)
   • ☐ Publish to Buf Schema Registry (BSR) (optional, for proto schemas)
   • ☐ Publish to NPM Registry (optional, for TypeScript/JavaScript)
   • ☐ Mark as prerelease (optional)

The workflow will:

• ✅ Validate version format and consistency across all files
• 🏗️ Build and test all language bindings
• 🏷️ Create GitHub release with automatic "v" prefix (e.g., v1.0.5)
• 📦 Upload TypeScript, Go, Python, and OpenAPI packages as release assets
• 🐍 Optionally publish Python package to TestPyPI and/or PyPI
• 📡 Optionally publish Protocol Buffer schemas to Buf Schema Registry
• 📦 Optionally publish TypeScript/JavaScript package to NPM Registry

Version Format: Always use semantic versioning without "v" prefix (e.g., 1.0.5, 2.1.0-beta.1)

Required Secrets for Publishing

To enable optional publishing features, configure these repository secrets in Settings → Secrets and variables → Actions:

• TEST_PYPI_API_TOKEN - For TestPyPI publishing (get token)
• PYPI_API_TOKEN - For PyPI publishing (get token)
• BUF_TOKEN - For BSR publishing (generate with: buf registry token create --name "GitHub-Actions")
• NPM_TOKEN - For NPM publishing (get token)

Documentation

• Development Setup - Complete setup guide for all platforms and IDEs
• Contributing - Guidelines for contributing to the project
• Troubleshooting - Solutions for common issues
• FAQ - Frequently asked questions
• Quick Reference - Commands, imports, and schema overview

The Future of Professional Reputation

Traditional Model: Your contributions are trapped within platforms, easily lost, and impossible to verify across contexts.

Cyberstorm Model: Your contributions become cryptographically-verified credentials that create measurable professional value and follow you throughout your career.

Join the Network

The value of the reputation network grows with each participant:

• More registered repositories = More opportunities to earn verifiable credentials
• More registered developers = Stronger network effects and reputation signals
• More platform adoption = Greater utility for verified contributions

Ready to build the future? Start by integrating these schemas into your applications and contributing to the growing ecosystem of verifiable professional reputation.

Related Projects

• cyberstorm-attestor: The service that processes GitHub webhooks and creates attestations using these schemas
• Ethereum Attestation Service (EAS): The underlying attestation infrastructure
• Protocol Buffer Ecosystem: Learn more about buf.build for professional Protocol Buffer development

License

MIT

Contact

For questions or support, please open an issue on GitHub.