🛡️ RaylsShield

Zero-Knowledge Privacy Layer for Rayls Protocol

RaylsShield adds privacy-preserving capabilities to cross-chain messaging on Rayls using ZK-SNARKs (Groth16 proofs). Send encrypted transactions across blockchains while maintaining verifiability and compliance.

🌐 Deployed Contracts

Rayls Testnet (Chain ID: 123123)

Contract	Address	Explorer
Groth16Verifier	`0xaF7B67b88128820Fae205A07aDC055ed509Bdb12`	View
RaylsShield	`0x71E3a04c9Ecc624656334756f70dAAA1fc4F985D`	View

Network Details:

RPC: https://devnet-rpc.rayls.com
Explorer: https://devnet-explorer.rayls.com
Chain ID: 123123
Gas Token: USDgas

🎯 Problem Statement

The Privacy vs. Compliance Dilemma

Blockchain technology promises transparency, but this comes at the cost of financial privacy. Every transaction, balance, and interaction is publicly visible on-chain. This creates several critical problems:

For Individuals:

No Financial Privacy: Anyone can track your entire transaction history, balance, and spending patterns
Front-Running Risk: Public transactions enable MEV attacks and front-running
Identity Correlation: Public addresses can be linked to real-world identities

For Institutions:

Competitive Intelligence Leaks: Competitors can see trading strategies, positions, and settlements
Regulatory Uncertainty: Privacy solutions like Tornado Cash were sanctioned for lacking compliance
Adoption Barriers: Cannot meet regulatory requirements while maintaining privacy

For the Industry:

Mass Surveillance: Complete financial transparency is incompatible with individual rights
Limited Enterprise Adoption: Fortune 500 companies won't use blockchain where competitors see everything
Regulatory Crackdown: Privacy-focused projects face sanctions without compliance mechanisms

Current Solutions Fall Short

Existing privacy solutions have critical flaws:

Solution	Privacy	Compliance	Cross-Chain	Status
Tornado Cash	✅ Yes	❌ No	❌ No	⚠️ Sanctioned
Aztec	✅ Yes	⚠️ Partial	❌ No	🟡 Complex
Privacy Coins	✅ Yes	❌ No	❌ No	⚠️ Delisted
RaylsShield	✅ Yes	✅ Yes	✅ Yes	✅ Compliant

The market needs a solution that provides:

Provable Privacy: Cryptographically guaranteed confidentiality
Verifiable Compliance: Prove regulatory adherence without revealing data
Cross-Chain Support: Privacy shouldn't be limited to a single blockchain
Institutional Grade: Enterprise-ready with proper compliance tools

RaylsShield solves this by combining Zero-Knowledge Proofs with AML compliance checks, enabling true privacy while proving regulatory compliance mathematically.

🚀 Long-term Vision Statement

Our Mission: Privacy as a Fundamental Right on Blockchain

We envision a future where privacy and compliance coexist seamlessly on-chain.

3-Year Roadmap

Year 1: Foundation & Adoption

✅ Q1 2025: Launch RaylsShield v1 on Rayls Devnet (Complete)
🔄 Q2 2025: Security audit by Trail of Bits or similar
📈 Q3 2025: Mainnet deployment on Rayls L1
🤝 Q4 2025: First institutional partnerships (target: 5 enterprises)

Year 2: Expansion & Features

🌐 Q1 2026: Multi-chain deployment (Ethereum, BSC, Polygon via Rayls)
💼 Q2 2026: Enterprise tier with KYC/AML integration
📱 Q3 2026: Mobile SDK for wallet integration
🔐 Q4 2026: Programmable privacy (privacy-preserving smart contracts)

Year 3: Industry Standard

🏢 Q1 2027: Bank-grade compliance dashboard
🤖 Q2 2027: AI-powered transaction privacy optimization
🌍 Q3 2027: Multi-jurisdictional compliance (EU, US, APAC)
🎯 Q4 2027: 1M+ private transactions processed monthly

Strategic Pillars

1. Privacy Innovation

Advanced ZK circuits for complex financial instruments
Recursive proofs for enhanced scalability
Privacy-preserving DeFi protocols

2. Regulatory Leadership

Work with regulators to define privacy standards
Open-source compliance frameworks
Industry-wide adoption of privacy + compliance

3. Enterprise Adoption

Fortune 500 onboarding program
Institutional-grade SLAs and support
Private settlement networks for banks

4. Developer Ecosystem

Privacy SDK for any blockchain
No-code privacy integration tools
Educational programs and grants

Ultimate Goal: Privacy by Default

By 2027, we aim to make RaylsShield the de facto standard for:

✅ Private institutional settlements
✅ Compliant DeFi transactions
✅ Cross-chain confidential messaging
✅ Privacy-preserving enterprise blockchain

Success Metrics:

🎯 1M+ monthly active users
🎯 100+ enterprise integrations
🎯 $10B+ in private transaction volume
🎯 Compliance certified in 20+ jurisdictions

💼 Business Model

Revenue Streams

1. Transaction Fees (Primary Revenue)

Privacy Fee Structure:

0.1% per private transaction
Minimum fee: $0.50
Maximum fee: $100 (capped for large transactions)

Revenue Distribution:

50% → Protocol treasury
30% → Liquidity providers / Validators
20% → Development fund

Example:

Transaction: $10,000 → Fee: $10
Monthly volume: $100M → Revenue: $100,000/month
Yearly projection (Year 1): $1.2M ARR

2. Enterprise Tier (Premium Services)

Enterprise Features:

White-label privacy integration
Custom compliance rules
Dedicated support & SLAs
Private deployment options
Advanced analytics dashboard

Pricing:

Startup: $5,000/month (up to 1,000 txs)
Growth: $15,000/month (up to 10,000 txs)
Enterprise: Custom pricing (unlimited txs)

Target: 50 enterprise clients by Year 2 → $6M ARR

3. API & SDK Licensing

Developer Tools:

Privacy SDK for dApp integration
API access for automated compliance
White-label UI components

Pricing:

Free Tier: 100 proofs/month
Pro: $500/month (10,000 proofs)
Business: $2,500/month (100,000 proofs)

Target: 500 API customers → $1M ARR

4. Compliance-as-a-Service

Regulatory Solutions:

Automated AML reporting
Multi-jurisdiction compliance packs
Real-time risk scoring
Audit trail generation

Pricing:

Basic: $1,000/month
Advanced: $5,000/month
Custom: $20,000+/month

Target: 100 compliance customers → $3M ARR

Total Revenue Projection

Year	Transaction Fees	Enterprise	API/SDK	Compliance	Total ARR
Year 1	$1.2M	$1M	$300K	$500K	$3M
Year 2	$10M	$6M	$1M	$3M	$20M
Year 3	$50M	$15M	$5M	$10M	$80M

Market Opportunity

Total Addressable Market (TAM):

Global blockchain transaction volume: $10 Trillion/year
Privacy-sensitive transactions: ~5% → $500 Billion
At 0.1% fee → $500M market

Serviceable Addressable Market (SAM):

Cross-chain + compliance focus → $50B/year
Institutional + DeFi segments → $5B/year

Serviceable Obtainable Market (SOM):

Year 3 target: 5% market share → $250M/year

Go-to-Market Strategy

Phase 1: Early Adopters (Months 1-6)

DeFi protocols needing privacy
Crypto-native institutions
Privacy-focused communities

Phase 2: Institutional Penetration (Months 6-18)

Traditional finance (TradFi) partnerships
Enterprise blockchain consortiums
Regulatory pilot programs

Phase 3: Mass Market (18+ months)

Wallet integrations (MetaMask, Trust Wallet)
Exchange partnerships (Coinbase, Binance)
Enterprise SaaS expansion

Competitive Advantages

Moat 1: Technical Excellence

First mover in ZK + Compliance + Cross-chain
Patent-pending privacy architecture
Open-source trust + proprietary optimization

Moat 2: Regulatory Relationships

Early compliance certification
Regulator advisory board
Jurisdictional expansion ahead of competitors

Moat 3: Network Effects

More users → better privacy set
More chains → more use cases
More integrations → higher switching costs

Moat 4: Brand & Trust

Security audits by top firms
Transparent operations
Community governance

Exit Strategy

Potential Paths:

Acquisition by major L1/L2 protocol ($500M-$2B valuation)
Acquisition by enterprise blockchain company (IBM, Oracle)
Strategic partnership with TradFi institution
Token launch + DAO governance transition
IPO (long-term, if SaaS revenue dominates)

Comparable Exits:

Aztec Network: $100M valuation (Series B)
Zcash: $2B peak market cap
Tornado Cash: $1B+ TVL before sanctions

🌟 Key Features

Privacy

Hidden Transaction Amounts: Cryptographic commitments hide actual values
Private Recipients: Recipient addresses are hashed for privacy
Secret Nullifiers: Prevent double-spending and replay attacks
Cross-Chain Privacy: Maintain confidentiality across different blockchains

Compliance

AML Threshold Proofs: Prove amount < $10,000 without revealing exact amount
Regulatory-Friendly: Built for institutional use cases
Verifiable On-Chain: All proofs verified via Groth16 verifier contract
Audit Trail: Nullifier tracking provides compliance-friendly history

Performance

Sub-Second Finality: Leverages Rayls L1's high-performance consensus
Gas-Efficient: Optimized Solidity contracts (~272k gas per transaction)
Fast Proof Generation: 1-2 seconds per proof
Scalable: Cross-chain messaging via Rayls Protocol

🚀 Quick Start

Installation

# Clone the repository
git clone https://github.com/Abenavidese/rayls-shield-BA.git
cd rayls-shield-BA

# Install backend dependencies
cd backend
npm install

Run the Demo

# Start local Hardhat node (Terminal 1)
npm run node

# Run the demo flow (Terminal 2)
npm run demo

Demo Output:

🛡️  RaylsShield - Zero-Knowledge Privacy Demo

✅ Contracts Deployed
✅ ZK Proof Generated
✅ Private Message Sent Cross-Chain
✅ Privacy Preserved!

💡 Alice sent $7,500 to Bob - amount hidden from everyone!

📋 Available Commands

# Development
npm run compile          # Compile Solidity contracts
npm run circom           # Compile Circom ZK circuits
npm run clean            # Clean build artifacts

# Testing
npm test                 # Run all tests
npm run test:integration # Run integration tests (13 tests)

# ZK Proofs
npm run generate:proof   # Generate a ZK proof
npm run generate:inputs  # Generate valid circuit inputs

# Deployment
npm run node             # Start local Hardhat node
npm run deploy:local     # Deploy to local network
npm run deploy:devnet    # Deploy to Rayls Devnet

# Demo
npm run demo             # Run complete E2E demo

🏗️ Project Structure

rayls-shield-BA/
├── backend/                         # Smart contracts and ZK circuits
│   ├── contracts/
│   │   ├── RaylsShield.sol         # Main privacy contract
│   │   ├── PrivacyVerifier.sol     # Groth16 verifier (auto-generated)
│   │   └── MockRaylsEndpoint.sol   # Local testing mock
│   │
│   ├── circuits/
│   │   ├── privacy.circom          # Core privacy circuit
│   │   ├── compliance.circom       # AML compliance circuit
│   │   ├── privacy.wasm            # Compiled witness calculator
│   │   ├── privacy.zkey            # Proving key
│   │   └── verification_key.json   # Verification key
│   │
│   ├── scripts/
│   │   ├── generate-inputs.js      # Generate valid circuit inputs
│   │   ├── generate-proof.js       # ZK proof generation
│   │   ├── deploy.js               # Contract deployment
│   │   └── demo-flow.js            # Complete demo workflow
│   │
│   ├── test/
│   │   ├── RaylsShield.test.js     # Basic unit tests
│   │   └── RaylsShield.integration.test.js  # E2E tests (✅ 13 passing)
│   │
│   ├── hardhat.config.js           # Hardhat + Circom configuration
│   ├── package.json                # Dependencies and scripts
│   └── .env.example                # Environment variables template
│
├── README.md                        # Project documentation
├── FRONTEND.md                      # Frontend integration guide
├── CONTRIBUTING.md                  # Contribution guidelines
└── LICENSE                          # MIT License

🔐 How It Works

1. Privacy Circuit

The core privacy circuit (circuits/privacy.circom) uses:

Poseidon Hash: ZK-friendly hash function
Commitment Scheme: commitment = Poseidon(secret, nullifier, amount)
Nullifier Hash: nullifierHash = Poseidon(nullifier)
Recipient Hash: recipientHash = Poseidon(recipient)

2. Groth16 Proofs

Industry-standard ZK-SNARK system
Proof generation: ~1-2 seconds
On-chain verification: ~272k gas
Proves knowledge of private inputs without revealing them

3. Smart Contract Integration

function sendPrivateMessage(
    uint256 _dstChainId,
    address _destination,
    bytes calldata _encryptedPayload,
    uint256[2] calldata _pA,      // Proof point A
    uint256[2][2] calldata _pB,   // Proof point B
    uint256[2] calldata _pC,      // Proof point C
    uint256[3] calldata _publicSignals  // [nullifierHash, commitment, recipientHash]
) external payable;

4. Cross-Chain Privacy

RaylsShield extends RaylsApp to leverage:

_raylsSend() for cross-chain messaging
_raylsSendToResourceId() for resourceId-based routing
Rayls Endpoint integration for multi-chain support

🧪 Testing

Run All Tests

npm test

Test Results:

  RaylsShield Integration Tests with ZK Proofs
    ✓ Deployment tests (3 passing)
    ✓ ZK proof generation and verification (2 passing)
    ✓ Send private messages (2 passing)
    ✓ ResourceId messaging (1 passing)
    ✓ Nullifier tracking (1 passing)
    ✓ Verifier management (3 passing)
    ✓ Complete E2E privacy flow (1 passing)

  13 passing (11s)

Integration Tests

npm run test:integration

Tests include:

Real ZK proof generation
On-chain proof verification
Cross-chain messaging simulation
Nullifier replay prevention
End-to-end privacy workflow

🌐 Deployment

Local Network

# Terminal 1: Start local node
npm run node

# Terminal 2: Deploy contracts
npm run deploy:local

Rayls Devnet

Create .env file:

PRIVATE_KEY=your_wallet_private_key_here
RAYLS_ENDPOINT_ADDRESS=0x...  # Get from Rayls team

Deploy:

npm run deploy:devnet

Rayls Devnet Details:

Chain ID: 123123
RPC: https://devnet-rpc.rayls.com
Explorer: https://devnet-explorer.rayls.com
Gas Token: USDgas

💡 Use Cases

1. Institutional Trading

Hide trading amounts from competitors
Prove compliance with AML regulations
Maintain privacy while meeting regulatory requirements

2. Private Cross-Chain Transfers

Send encrypted messages across blockchains
Verify recipient without revealing identity
Prevent double-spending with nullifiers

3. Confidential Settlements

Private institutional settlements
Compliance-friendly privacy
Rayls' sub-second finality for instant settlement

4. Private DeFi

Hidden liquidity provisions
Anonymous yield farming
Private DAO voting

🔧 Technical Details

Circuit Complexity

Privacy Circuit: 3 Poseidon hashes + 1 range check
Compliance Circuit: Adds 2 comparison constraints for AML
Witness Calculation: < 1 second
Proof Generation: 1-2 seconds
Proof Size: ~128 bytes

Gas Costs

Deploy RaylsShield: ~1,037,239 gas
Deploy Verifier: ~390,033 gas
Send Private Message: ~272,268 gas (avg)
Update Verifier: ~30,588 gas

Security

✅ Groth16 ZK-SNARKs (industry standard)
✅ Poseidon hash (ZK-optimized)
✅ Nullifier system (replay protection)
✅ OpenZeppelin contracts (battle-tested)
✅ Reentrancy guards
✅ Access control (Ownable)

📚 Documentation

FRONTEND.md - Complete frontend integration guide with React examples
NEXT_STEPS.md - Deployment guide and next steps
CLAUDE.md - Development instructions

Generate a ZK Proof

npm run generate:proof

Output:

✅ Proof generated successfully!
Proof valid: ✅ YES

Solidity call data:
a: [...]
b: [...]
c: [...]
publicSignals: [nullifierHash, commitment, recipientHash]

Use in Your Code

const { generateProof, formatProofForSolidity } = require("./scripts/generate-proof");

// Generate proof
const { proof, publicSignals } = await generateProof({
  secret: BigInt(123456789),
  nullifier: BigInt(987654321),
  recipient: BigInt("0x..."),
  amount: BigInt(7500),
});

// Format for Solidity
const solidityProof = formatProofForSolidity(proof, publicSignals);

// Send private message
await raylsShield.sendPrivateMessage(
  dstChainId,
  destination,
  encryptedPayload,
  solidityProof.a,
  solidityProof.b,
  solidityProof.c,
  solidityProof.publicSignals
);

🎯 Hackathon Achievements

✅ Complete ZK Implementation

Privacy circuit compiled and tested
Compliance circuit with AML checks
Real proof generation working

✅ Full Rayls Integration

Extends RaylsApp correctly
Cross-chain messaging implemented
ResourceId support added

✅ Production-Ready Testing

13 comprehensive tests passing
Real ZK proofs in tests
End-to-end flow validated

✅ Developer Experience

Easy proof generation scripts
Comprehensive documentation
One-command demo

📖 Additional Resources

🤝 Contributing

This is a hackathon project. Contributions, issues, and feature requests are welcome!

📝 License

MIT License - See LICENSE file for details

🎉 Acknowledgments

Rayls Team for the amazing L1 protocol
Circom/iden3 for ZK circuit tooling
OpenZeppelin for secure smart contract libraries
Hardhat for development framework

📬 Contact

For questions about RaylsShield:

Check IMPLEMENTATION_COMPLETE.md for detailed implementation notes
Review CLAUDE.md for architectural decisions
Run npm run demo to see it in action

Built with ❤️ using Zero-Knowledge proofs, Rayls Protocol, and Solidity.

Perfect for: Institutional DeFi • Private Cross-Chain Messaging • Regulatory-Compliant Privacy • Confidential Settlements

Name		Name	Last commit message	Last commit date
Latest commit History 8 Commits
backend		backend
frontend/rayls-shield-landing-page		frontend/rayls-shield-landing-page
.gitignore		.gitignore
CLAUDE.md		CLAUDE.md
CONTRIBUTING.md		CONTRIBUTING.md
FRONTEND.md		FRONTEND.md
IMPLEMENTATION_COMPLETE.md		IMPLEMENTATION_COMPLETE.md
LICENSE		LICENSE
README.md		README.md
SETUP_COMPLETE.md		SETUP_COMPLETE.md

Folders and files

Latest commit

History

Repository files navigation

🛡️ RaylsShield

🌐 Deployed Contracts

🎯 Problem Statement

The Privacy vs. Compliance Dilemma

Current Solutions Fall Short

🚀 Long-term Vision Statement

Our Mission: Privacy as a Fundamental Right on Blockchain

3-Year Roadmap

Strategic Pillars

Ultimate Goal: Privacy by Default

💼 Business Model

Revenue Streams

1. Transaction Fees (Primary Revenue)

2. Enterprise Tier (Premium Services)

3. API & SDK Licensing

4. Compliance-as-a-Service

Total Revenue Projection

Market Opportunity

Go-to-Market Strategy

Competitive Advantages

Exit Strategy

🌟 Key Features

Privacy

Compliance

Performance

🚀 Quick Start

Installation

Run the Demo

📋 Available Commands

🏗️ Project Structure

🔐 How It Works

1. Privacy Circuit

2. Groth16 Proofs

3. Smart Contract Integration

4. Cross-Chain Privacy

🧪 Testing

Run All Tests

Integration Tests

🌐 Deployment

Local Network

Rayls Devnet

💡 Use Cases

1. Institutional Trading

2. Private Cross-Chain Transfers

3. Confidential Settlements

4. Private DeFi

🔧 Technical Details

Circuit Complexity

Gas Costs

Security

📚 Documentation

Generate a ZK Proof

Use in Your Code

🎯 Hackathon Achievements

📖 Additional Resources

🤝 Contributing

📝 License

🎉 Acknowledgments

📬 Contact

About

Resources

License

Contributing

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

Packages