Skip to content

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 

Repository files navigation

VeilPay

Pay privately. Prove when necessary.

VeilPay is a privacy-first payment platform built on Starknet that enables crypto-native organizations to make private payroll and contractor payments using STRK20.

Traditional blockchain payments are transparent by default. That transparency is powerful for verification, but it can expose sensitive financial information such as salaries, payment amounts, payment timing, and relationships between organizations and individuals.

VeilPay brings privacy to organizational payments while preserving the ability to selectively verify transactions when required.


The Problem

Public blockchain transactions can reveal far more than the sender and recipient.

For a company paying employees or contractors, an observer may be able to determine:

  • How much an individual is paid
  • When payments are made
  • How frequently someone is paid
  • Which wallets belong to the same organization
  • How much an organization spends on payroll
  • Relationships between organizations and contributors

For crypto-native companies, DAOs, and globally distributed teams, this creates a serious privacy problem.

Salary information should not become public financial intelligence simply because the payment happens on-chain.


The Solution

VeilPay provides a private payment layer for organizations.

An employer can create a payment run, fund it with supported ERC-20 assets, and distribute payments to employees or contractors through STRK20 private transfers.

Recipients can access their own payment information while authorized parties can use selective disclosure mechanisms when verification is required.

The principle

Private by default. Verifiable when necessary.


How It Works

                    ┌──────────────────┐
                    │     Employer     │
                    │   Connect Wallet │
                    └────────┬─────────┘
                             │
                             ▼
                    ┌──────────────────┐
                    │   Payment Run    │
                    │                  │
                    │ Alice   $2,500   │
                    │ Bob     $1,800   │
                    │ Charlie $3,200   │
                    └────────┬─────────┘
                             │
                             ▼
                    ┌──────────────────┐
                    │      STRK20      │
                    │ Private Transfers│
                    └────────┬─────────┘
                             │
                 ┌───────────┼───────────┐
                 ▼           ▼           ▼
              Alice         Bob       Charlie
             $2,500       $1,800       $3,200

The goal is to prevent the public chain from exposing the sensitive payment relationships that VeilPay is designed to protect.


Core Features

🔐 Private Payments

Send supported ERC-20 assets through STRK20 privacy primitives without exposing sensitive payment information publicly.

💼 Payment Runs

Create a single payment run for multiple employees or contractors.

August Payment Run

12 recipients
$18,450 USDC

✓ Funded
✓ Ready

👤 Recipient Dashboard

Recipients can view their own payment information without requiring the entire organization's payment history to be public.

🧾 Payment Receipts

Generate receipts for completed payments containing relevant payment information and verification data.

🔎 Selective Disclosure

VeilPay is designed around controlled disclosure rather than absolute secrecy.

Authorized parties can verify relevant financial information without requiring an organization to expose its entire payment history.

🌐 Starknet Native

VeilPay is designed specifically for the Starknet ecosystem and uses STRK20 as its privacy layer.


Why STRK20?

STRK20 provides privacy primitives for ERC-20 assets on Starknet, including shielded balances and private transfers.

VeilPay builds the organizational payment experience on top of these primitives rather than attempting to create a separate privacy system.

This allows VeilPay to focus on the actual user problem:

How do organizations use private blockchain payments in the real world?


Example

Imagine a crypto-native company with four contractors:

Contractor Payment
Alice $2,500
Bob $1,800
Charlie $3,200
David $1,400

The company creates one VeilPay payment run.

TOTAL
$8,900 USDC

4 recipients

[ Execute Private Payments ]

The payment run is executed using STRK20 private transfers.

Each contractor can access their own payment information.

The company's financial activity does not need to become a publicly readable payroll spreadsheet.


Privacy Model

VeilPay follows a simple model:

                    PUBLIC
                      │
                      ▼
              ┌───────────────┐
              │ Minimal       │
              │ information   │
              └───────┬───────┘
                      │
                ┌─────▼─────┐
                │  VeilPay  │
                └─────┬─────┘
                      │
          ┌───────────┴───────────┐
          ▼                       ▼
      Recipient               Authorized
       Access                 Verification
          │                       │
          ▼                       ▼
     Own payment             Relevant data
      information             when needed

The objective is not to make financial activity unverifiable.

The objective is to make sensitive information private by default while preserving controlled verification.


Use Cases

VeilPay starts with payroll, but the underlying infrastructure can support many forms of organizational payments.

Payroll

Pay employees without publishing their salaries on-chain.

Contractor Payments

Pay freelancers and contributors privately.

DAO Contributor Payments

Distribute contributor compensation without exposing individual compensation packages.

Grants

Privately distribute grants while maintaining verifiable payment records.

Vendor Payments

Pay suppliers without exposing sensitive commercial relationships.

Bonuses & Incentives

Distribute bonuses privately without revealing compensation details to the entire market.


Architecture

At a high level:

┌─────────────────────────────────────┐
│              VeilPay UI             │
│                                     │
│  Employer Dashboard                 │
│  Recipient Dashboard                │
│  Payment Runs                       │
│  Receipts                           │
└──────────────────┬──────────────────┘
                   │
                   ▼
┌─────────────────────────────────────┐
│          Starknet Wallet             │
└──────────────────┬──────────────────┘
                   │
                   ▼
┌─────────────────────────────────────┐
│              STRK20                 │
│                                     │
│  Shielded Assets                    │
│  Private Transfers                  │
│  Viewing / Disclosure Mechanisms    │
└──────────────────┬──────────────────┘
                   │
          ┌────────┴────────┐
          ▼                 ▼
     Recipients        Authorized
                       Verification

Tech Stack

The initial VeilPay implementation is intended to use:

  • Starknet — settlement layer
  • STRK20 — privacy and shielded ERC-20 functionality
  • Cairo — Starknet smart contracts
  • React / Next.js — frontend
  • Starknet wallet integration — user authentication and transaction signing

Additional infrastructure may be introduced as the product evolves.


Project Status

🚧 VeilPay is currently under development.

The initial MVP focuses on demonstrating the complete private payment lifecycle:

Connect Wallet
      ↓
Create Payment Run
      ↓
Fund Payment Run
      ↓
Execute Private Transfers
      ↓
Recipient Receives Payment
      ↓
View Payment
      ↓
Generate / Verify Payment Proof

Roadmap

Phase 1 — MVP

  • Starknet wallet connection
  • STRK20 asset integration
  • Create payment run
  • Add recipients
  • Fund payment run
  • Execute private payments
  • Recipient payment dashboard
  • Payment receipts
  • Basic selective verification flow
  • Starknet mainnet deployment

Phase 2 — Organizational Payments

  • Recurring payment runs
  • Contractor management
  • Payment history
  • Organization accounts
  • Multiple supported assets
  • Improved verification workflows

Phase 3 — Private Financial Operations

  • Private invoices
  • DAO contributor distributions
  • Grants
  • Vendor payments
  • Role-based access
  • Advanced compliance workflows

Why VeilPay?

Blockchain gave organizations transparent financial infrastructure.

But transparency should not mean that everyone gets to see everything.

VeilPay explores a different model:

Organizations should be able to use blockchain for settlement without turning sensitive financial information into public data.

Privacy and verifiability don't have to be opposites.


Built for Starknet

VeilPay is being built for the STRK20 Private Sprint with a focus on meaningful STRK20 integration and a functional Starknet application.

The goal is not to add privacy as a cosmetic feature.

Privacy is the core product.


Contributing

Contributions, feedback, and ideas are welcome.

If you find a bug or have an idea for improving VeilPay, please open an issue or submit a pull request.


Security

VeilPay is experimental software under active development.

Do not use VeilPay with funds you cannot afford to lose.

The system has not necessarily undergone a formal security audit, and implementation details may change during development.


License

License information will be added as the project is finalized.


VeilPay

Private payments for a transparent world.

Pay privately. Prove when necessary.

About

The first privacy layer for crypto-native organizations.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors