Cipherblock

Portable cryptographic reputation management system

What is Cipherblock?

Cipherblock enables anyone to operate a reputation platform where users build verifiable identity and trust metrics that follow them across services. Service providers (like Uber drivers), forecasters, freelancers, and professionals can carry their ratings and reputation across any platform using the same cryptographic keys.

Key Features

• 🔑 Portable Identity: Same keys work across all operators
• 📊 Portable Reputation: Trust history follows you everywhere
• 🔒 Tamper-Proof: Cryptographically signed transactions and blocks
• ⚡ Fast: Thousands of transactions per second
• 🌐 Decentralized Ecosystem: Multiple competing operators
• 🔍 Transparent: All transactions publicly verifiable
• 🚀 Serverless: Built on Firebase (zero server management)

Project Status

Phase 1: Core Cryptography ✅ COMPLETE

The foundational cryptographic layer is fully implemented and tested:

• ✅ Keypair generation (secp256k1)
• ✅ Transaction signing and verification
• ✅ Block signing and verification
• ✅ Hashing functions (SHA-256)
• ✅ Comprehensive test suite (27 tests passing)
• ✅ Browser & Node.js support

Phase 2: Transaction Validation ✅ COMPLETE

Complete validation for all 8 transaction types:

• ✅ Common validation (signature, nonce, format)
• ✅ TOKEN_TRANSFER validation
• ✅ RATE transaction validation
• ✅ NFT transactions (MINT, TRANSFER, orders)
• ✅ ASSET_BURN validation
• ✅ FEE_UPDATE validation
• ✅ State-aware checks (balances, ownership, nonces)
• ✅ Comprehensive test suite (26 validation tests)

Phase 3: State Management ✅ COMPLETE

Complete state execution for all transaction types:

• ✅ Transaction execution (all 8 types)
• ✅ Balance tracking (regular and locked)
• ✅ NFT ownership and locking
• ✅ Order book management
• ✅ Order matching with self-cancellation
• ✅ Order expiration
• ✅ Fee collection and updates
• ✅ Nonce tracking
• ✅ Rating storage
• ✅ Comprehensive test suite (17 state tests)

Phase 4: Block Processing Engine ✅ COMPLETE

Complete block processing with integrated validation and state:

• ✅ Transaction validation and execution
• ✅ Block creation and signing
• ✅ Genesis block creation
• ✅ Block verification
• ✅ Block hashing for chain linking
• ✅ Order matching during finalization
• ✅ Comprehensive test suite (10 block tests)

What's Next

Phase 5: Firebase Backend

• Cloud Functions (submitTransaction, processBlock)
• Firestore schema and collections
• Distributed locking for block processing
• Mempool management
• Genesis block deployment

Phase 6: Browser Client

• Wallet UI (key generation and management)
• Blockchain explorer
• Transaction submission
• Real-time blockchain updates

Quick Start

Prerequisites

• Node.js 18+
• npm

Install Dependencies

npm install

Run Tests

npm test

Usage Example

import { generateKeypair, signTransaction } from './src/crypto/index.js';
import { validateTransaction } from './src/transactions/index.js';

// Generate a wallet
const wallet = generateKeypair();
console.log('Address:', wallet.address);

// Create a transaction
const tx = {
  transaction_type: 'TOKEN_TRANSFER',
  sender_address: wallet.address,
  recipient_address: '02...',
  amount: 100,
  nonce: 1,
  timestamp: new Date().toISOString()
};

// Sign it
const signature = await signTransaction(tx, wallet.privateKey);
const signedTx = { ...tx, sender_signature: signature };

// Validate against blockchain state
const state = {
  balances: { [wallet.address]: 1000 },
  nonces: { [wallet.address]: 0 },
  fee_schedule: { token_transfer_fee: 0.01 },
  // ... other state
};

const result = validateTransaction(signedTx, state);
if (result.valid) {
  console.log('Transaction is valid!');
} else {
  console.error('Invalid:', result.error);
}

Architecture

Technology Stack

• Cryptography: @noble/secp256k1, @noble/hashes
• Backend: Firebase Cloud Functions (2nd gen), Firestore
• Client: Vanilla JavaScript (Web Crypto API)
• Testing: Jest

Design Principles

1. Centralized Processing, Decentralized Ecosystem

   • Each operator processes transactions serially for speed
   • Multiple competing operators create decentralization

2. Portable Identity

   • Same cryptographic keys work everywhere
   • Users own their private keys

3. Tamper-Proof History

   • Users save signed blocks
   • Can prove if operator modifies history

4. Market Competition

   • Bad operators lose users
   • Good operators attract adoption

5. Simplicity

   • Non-Turing-complete (fixed transaction types)
   • Easy to audit and verify

Documentation

• Functional Specification - Complete system requirements
• Technical Specification - Implementation details
• Crypto Module README - Cryptography API reference
• Transaction Validation README - Validation API reference
• State Management README - State management API reference
• Block Processing README - Block processing API reference

Use Cases

Service Provider Reputation

Uber drivers, Etsy sellers, and freelancers carry ratings across platforms.

Driver on Lyft → Earns 4.9★ rating → Applies to Uber →
Full rating history visible → Fast-tracked approval

Prediction Markets

Track forecasting accuracy across markets and platforms.

User predicts 10 events → 8 correct →
Verifiable 80% accuracy → Consulting opportunities

Professional Credentials

Verifiable work history and peer endorsements.

Developer earns reputation on Platform A →
Switches to Platform B → Reputation follows

Project Structure

cipherblock/
├── src/
│   ├── crypto/                      ✅ Complete
│   │   ├── index.js                 # Main exports
│   │   ├── keys.js                  # Key management
│   │   ├── signing.js               # Signing/verification
│   │   ├── keys.test.js             # Tests
│   │   ├── signing.test.js          # Tests
│   │   └── README.md                # Crypto documentation
│   ├── transactions/                ✅ Complete
│   │   ├── index.js                 # Main exports
│   │   ├── types.js                 # Transaction types & schemas
│   │   ├── validator.js             # Validation logic
│   │   ├── validator.test.js        # Tests
│   │   └── README.md                # Validation documentation
│   ├── state/                       ✅ Complete
│   │   ├── index.js                 # Main exports
│   │   ├── manager.js               # State management logic
│   │   ├── manager.test.js          # Tests
│   │   └── README.md                # State documentation
│   └── blocks/                      ✅ Complete
│       ├── index.js                 # Main exports
│       ├── processor.js             # Block processing logic
│       ├── processor.test.js        # Tests
│       └── README.md                # Block documentation
├── cipherblock-functional-spec.md   # System requirements
├── cipherblock-tech-spec.md         # Implementation spec
├── package.json
├── jest.config.js
└── README.md                        # This file

Testing

# Run all tests
npm test

# Watch mode
npm run test:watch

Current Test Results:

Test Suites: 5 passed, 5 total
Tests:       80 passed, 80 total
Time:        ~1s

Security

Private Keys

• Generated client-side
• Never transmitted to operator
• User responsible for storage
• Production: encrypt before storing

Signatures

• All transactions signed by sender
• All blocks signed by operator
• Tamper detection via saved blocks
• Replay prevention via nonces

Verification

• Anyone can verify signatures
• Anyone can reconstruct state from genesis
• Operator cannot forge signatures

Contributing

This is currently a personal project. Contributions, suggestions, and feedback are welcome!

License

MIT

Roadmap

• Phase 1: Core Cryptography
• Phase 2: Transaction Validation
• Phase 3: State Management
• Phase 4: Block Processing Engine
• Phase 5: Firebase Backend
• Phase 6: Browser Client
• Phase 7: Production Deployment

---

Built with ❤️ for portable reputation