A non-custodial, Bitcoin-native protocol addressing demand-shock deflation in the age of AI automation through time-locked staking, velocity incentives, and decentralized governance.
🚀 Quick Start • 📖 Documentation • 🔬 Research • 💬 Community
- 🌟 What is the DLD Protocol?
- 🎯 The Problem We Solve
- 💡 The Solution
- 🧮 The Formula
- ⚙️ Core Components
- 🚀 Quick Start
- 📊 Key Features
- 🏗️ Architecture
- 💻 Usage Examples
- 📖 Documentation
- 🗺️ Roadmap
- 🔒 Security
- 🤝 Contributing
- 🔬 Research & Citation
- 💬 Community
- 🤝 Acknowledgements
- 📄 License
The Bitcoin Digital Labor Derivative (DLD) Protocol is a groundbreaking economic framework built entirely on Bitcoin's proven security primitives. It transforms passive Bitcoin holdings into an active economic engine without requiring custody, sidechains, or wrapped tokens.
- 🔐 Non-Custodial: Users maintain full control of their private keys
- ⛓️ Bitcoin-Native: Uses only Bitcoin primitives (OP_CHECKLOCKTIMEVERIFY, UTXO tracking)
- 🌐 Decentralized: Miner-governed through hash power voting
- 📐 Mathematically Sound: Provably fair distribution mechanics
- 🔓 Open Source: Fully auditable and transparent
As automation and AI increasingly replace human labor, traditional economic models face a critical challenge:
📉 Automation → Job Displacement → Reduced Purchasing Power → Economic Deflation → Recession
The Challenge: How do we maintain economic velocity and purchasing power when machines produce value but humans still need to participate in the economy?
Traditional Solutions (and their flaws):
- ❌ Universal Basic Income (UBI): Requires centralized control and taxation
- ❌ Central Bank Digital Currencies (CBDCs): Sacrifices privacy and sovereignty
- ❌ Token-based Systems: Introduces new trust assumptions and counterparty risk
The DLD Protocol creates a sustainable, decentralized dividend system by leveraging:
Participants lock Bitcoin for defined periods using Bitcoin's native OP_CHECKLOCKTIMEVERIFY, proving long-term commitment without giving up custody.
Bitcoin miners voluntarily contribute a percentage of block rewards to create a sustainable dividend pool—no central authority required.
Rewards active economic participation over hoarding, encouraging circulation while respecting Bitcoin's deflationary nature.
Protocol parameters adjusted through miner voting weighted by contribution and reputation.
Real-time economic health monitoring to detect and respond to deflationary pressure.
The Result: A self-sustaining economic engine that maintains Bitcoin's sovereignty while addressing automation-driven economic challenges.
At the heart of the DLD Protocol is a mathematically precise distribution formula:
D̂ᵢ = P̂ · (pᵢ · Tᵢ / Σⱼ₌₁ᴺ(pⱼ · Tⱼ)) · Vᵢ
| Symbol | Name | Description | Range |
|---|---|---|---|
| D̂ᵢ | Individual Dividend | Satoshis earned by participant i |
≥ 0 |
| P̂ | Systemic Pool | Total dividend pool (miner-funded) | ≥ 0 sats |
| pᵢ | Stake Amount | Individual's locked Bitcoin | ≥ 0 sats |
| Tᵢ | Trust Coefficient | Time-weighted commitment factor | 0.5 - 2.0 |
| Vᵢ | Velocity Multiplier | Circulation activity bonus | 1.0 - 1.5 |
| Σ | Normalizer | Sum of all weighted stakes | > 0 |
- 🔢 Proportional Distribution: Your share is proportional to your weighted stake
- ⏳ Time Rewards: Longer commitments earn higher trust multipliers
- 🔄 Activity Bonus: Active circulation earns velocity multipliers
- ⚖️ Fair Allocation: Automatically normalized across all participants
The Innovation: Where does the dividend pool come from without central control?
The Answer: Bitcoin miners voluntarily contribute a percentage of block rewards and transaction fees.
| Benefit | Description |
|---|---|
| ♻️ Sustainability | Self-funding tied to Bitcoin's security budget |
| 🌐 Decentralization | No central authority controls distribution |
| 🤝 Alignment | Miners benefit from network effect and Bitcoin value growth |
| 👑 Sovereignty | Pure Bitcoin-native, no external dependencies |
pub enum FundingMechanism {
BlockRewardPercentage { percentage: Decimal }, // e.g., 1% of 6.25 BTC
TransactionFeeShare { percentage: Decimal }, // e.g., 5% of tx fees
Hybrid { /* combination */ }, // Best of both
Voluntary, // Direct contributions
}Example: 1% of block rewards contribution:
| Timeframe | Calculation | Total Contribution |
|---|---|---|
| Per Block | 6.25 BTC × 1% | 0.0625 BTC (6.25M sats) |
| Daily | 0.0625 BTC × 144 blocks | 9 BTC (900M sats) |
| Annual | 9 BTC × 365 days | 3,285 BTC |
Concept: Longer time commitments earn higher trust multipliers, rewarding long-term economic participation.
| Lock Duration | Trust Coefficient | Rationale |
|---|---|---|
| < 30 days | 0.5× | Minimal commitment, reduced weight |
| 30-90 days | 1.0× | Baseline participation |
| 90-180 days | 1.3× | Medium-term commitment |
| 180-365 days | 1.6× | Strong long-term signal |
| 365+ days | 2.0× | Maximum trust, maximum weight |
Alice: Locks 1 BTC for 365+ days → Trust = 2.0 → Weighted Stake = 2.0 BTC
Bob: Locks 2 BTC for 30 days → Trust = 1.0 → Weighted Stake = 2.0 BTC
Result: Equal distribution despite different amounts (rewarding commitment)
Concept: Encourage active economic participation rather than passive hoarding.
Vᵢ = 1.0 + velocity_bonus (based on circulation activity)
Factors Considered:
- 📦 Average UTXO age (dormancy indicator)
- 💸 Transaction frequency (30-day window)
- ⚡ Lightning Network activity (future integration)
| Activity Level | Velocity Multiplier | Description |
|---|---|---|
| Dormant | 1.0× | Minimal on-chain activity |
| Low Activity | 1.1× | Occasional transactions |
| Moderate | 1.25× | Regular circulation |
| High Activity | 1.5× | Active economic participant |
Note: Velocity rewards are bounded to prevent gaming while encouraging genuine circulation.
Purpose: Real-time monitoring of economic health to detect deflationary pressure.
R.B.I. = (V_DLD × T_c) / (D_s / E^A)
| Component | Description |
|---|---|
| V_DLD | DLD velocity (circulation speed) |
| T_c | Aggregate trust coefficient |
| D_s | Demand shock factor |
| E^A | Productivity exponential (AI/automation) |
RBI ≥ 1.0 ✅ Healthy: Economy stable or growing
RBI < 1.0 ⚠️ Warning: Deflationary pressure detected
RBI < 0.5 🚨 Critical: Immediate intervention needed
Automatic Alerts: The system can trigger notifications when RBI falls below thresholds, enabling proactive governance responses.
|
|
┌─────────────────────────────────────────────────────────────────┐
│ Bitcoin Mainnet │
│ ┌──────────────────┐ ┌────────────────────┐ │
│ │ Timelock UTXOs │◄────────┤ OP_CLTV Scripts │ │
│ └────────┬─────────┘ └────────────────────┘ │
└────────────┼───────────────────────────────────────────────────┘
│ Read-Only Chain Data
▼
┌─────────────────────────────────────────────────────────────────┐
│ Bitcoin DLD Protocol Layer │
│ ┌────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │
│ │ UTXO Analyzer │ │ Stake Registry │ │ RBI Engine │ │
│ │ │ │ │ │ │ │
│ │ • Age tracking │ │ • Participants │ │ • V_DLD calc │ │
│ │ • Velocity │ │ • Trust calc │ │ • D_s monitor │ │
│ │ • Tx counting │ │ • Status mgmt │ │ • Alerts │ │
│ └───────┬────────┘ └────────┬────────┘ └────────┬────────┘ │
│ │ │ │ │
│ └────────────────────┼─────────────────────┘ │
│ ▼ │
│ ┌───────────────────────┐ │
│ │ Derivative Engine │ │
│ │ │ │
│ │ D̂ᵢ = P̂·(pᵢ·Tᵢ/Σ)·Vᵢ │ │
│ └───────────┬───────────┘ │
│ │ │
│ ┌───────────▼───────────┐ │
│ │ Distribution Pool │ │
│ │ • Normalizer │ │
│ │ • Dividend compute │ │
│ └───────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ Miner Coordination Layer │
│ ┌──────────────────┐ ┌──────────────────┐ │
│ │ P̂ Pool Manager │ │ Governance │ │
│ │ │ │ │ │
│ │ • Contributions │ │ • Voting │ │
│ │ • Balance track │ │ • Consensus │ │
│ │ • Distribution │ │ • Parameters │ │
│ └──────────────────┘ └──────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ REST API Layer │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ GET /api/v1/rbi - RBI status │ │
│ │ GET /api/v1/pool/balance - Pool balance │ │
│ │ GET /api/v1/participants/:id - Participant info │ │
│ └──────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘
bitcoin-digital-labor-derivative/
├── src/
│ ├── lib.rs # Core library exports
│ ├── rbi_engine.rs # RBI calculation engine
│ ├── velocity_analyzer.rs # Velocity scoring logic
│ ├── utxo_scoring.rs # UTXO age analysis
│ ├── bitcoin_core_chain.rs # Bitcoin Core RPC integration
│ ├── sqlite_participant_registry.rs # SQLite participant storage
│ ├── economic_oracle.rs # Economic data providers
│ ├── alerts.rs # Alert system
│ ├── simulation/ # Deterministic simulations
│ │ ├── state.rs # Simulation state
│ │ ├── scenarios.rs # Economic scenarios
│ │ └── report.rs # Reporting tools
│ ├── api/ # REST API (feature-gated)
│ │ ├── node.rs # Global state management
│ │ ├── handlers.rs # HTTP handlers
│ │ ├── server.rs # Server configuration
│ │ └── types.rs # API types
│ └── bin/
│ ├── sim.rs # Simulation runner
│ └── api_server.rs # API server binary
├── tests/
│ ├── simulation_determinism.rs # Deterministic tests
│ └── registry_sybil.rs # Registry security tests
├── examples/
│ ├── global_node_usage.rs # API usage examples
│ └── api_demo.sh # Shell script demos
├── docs/
│ ├── ARCHITECTURE.md # System design
│ ├── PAPER.md # Research paper
│ ├── SECURITY.md # Security model
│ ├── API.md # API reference
│ └── ANALYSIS.md # Economic analysis
└── Cargo.toml # Package manifest
|
Want to integrate DLD into your app? # Start the REST API
cargo run --bin api-server \
--features api
# API available at
# http://localhost:3000 |
Build and extend the protocol? # Clone & build
git clone https://github.com/dfeen87/bitcoin-digital-labor-derivative
cd bitcoin-digital-labor-derivative
cargo build --release
# Run tests
cargo test --all |
Study the economic model? # Run simulations
cargo run --bin sim
# Generate reports
# See examples/ for
# various scenarios |
- Rust 1.70 or higher (Install)
- Bitcoin Core (for mainnet integration) - Download
- SQLite (included via bundled feature)
# Install Rust (if needed)
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
# Clone repository
git clone https://github.com/dfeen87/bitcoin-digital-labor-derivative
cd bitcoin-digital-labor-derivative
# Build all components
cargo build --release
# Build with API server
cargo build --release --features api
# Run test suite
cargo test --all
# Run benchmarks
cargo benchuse bitcoin_digital_labor_derivative::*;
fn main() -> Result<(), Box<dyn std::error::Error>> {
// Create a 90-day Bitcoin stake
let stake = TimelockedStake {
address: "bc1qyour_address_here".to_string(),
amount: 100_000_000, // 1 BTC in satoshis
lock_duration_days: 90,
block_height: 800_000,
};
// Calculate trust coefficient based on duration
// After 60 days at block 800_000 + (60 * 144)
let current_block = 800_000 + (60 * 144);
let trust = stake.calculate_trust_coefficient(current_block)?;
println!("Trust coefficient after 60 days: {}", trust);
// Output: Trust coefficient after 60 days: 1.0
Ok(())
}use bitcoin_digital_labor_derivative::*;
use rust_decimal::Decimal;
fn main() -> Result<(), Box<dyn std::error::Error>> {
// Create participant with stake info
let participant = ParticipantData {
id: "alice".to_string(),
stake_amount: 100_000_000, // 1 BTC
trust_coefficient: Decimal::new(15, 1), // 1.5
velocity_multiplier: Decimal::new(12, 1), // 1.2
};
// Initialize distribution pool with 10 BTC
let mut pool = DistributionPool::new(
1_000_000_000, // 10 BTC pool
800_000 // Current block height
);
// Add participant to pool
pool.add_participant(participant)?;
// Calculate dividend
let dividend = pool.calculate_dividend_rate("alice")?;
println!("Alice's dividend: {} satoshis ({} BTC)",
dividend,
dividend as f64 / 100_000_000.0
);
Ok(())
}use bitcoin_digital_labor_derivative::miner::*;
use rust_decimal_macros::dec;
fn main() -> Result<(), Box<dyn std::error::Error>> {
// Set up 1% block reward funding mechanism
let mechanism = FundingMechanism::BlockRewardPercentage {
percentage: dec!(0.01), // 1%
};
let mut pool = MinerCoordinationPool::new(mechanism);
// Register a mining pool
let miner = MinerNode {
name: "FoundryUSA".to_string(),
payout_address: "bc1qminer_address".to_string(),
hashrate_ph: 100_000, // 100 PH/s
reputation: dec!(1.0),
};
pool.register_miner(miner)?;
// Process a block contribution
let contribution = pool.process_block_contribution(
"FoundryUSA",
625_000_000, // 6.25 BTC block reward
50_000_000, // 0.5 BTC in fees
800_000, // Block height
)?;
println!("Contribution to pool: {} sats", contribution);
println!("Total pool balance: {} sats", pool.get_pool_balance());
// Contribution to pool: 6_250_000 sats (1% of 6.25 BTC)
// Total pool balance: 6_250_000 sats
Ok(())
}# Terminal 1: Start server
cargo run --bin api-server --features api
# Server starts on http://localhost:3000# Terminal 2: Make API calls
# 1. Health check
curl http://localhost:3000/health
# {"status":"healthy","version":"1.0.0"}
# 2. Get current RBI status
curl http://localhost:3000/api/v1/rbi | jq
# {
# "rbi_value": 1.45,
# "status": "healthy",
# "components": {
# "v_dld": 2.5,
# "t_c": 1.2,
# "d_s": 0.8,
# "productivity_a": 1.5
# }
# }
# 3. Check pool balance
curl http://localhost:3000/api/v1/pool/balance | jq
# {
# "balance_sats": 1000000000,
# "balance_btc": 10.0,
# "timestamp": "2026-02-14T19:57:22Z"
# }
# 4. Calculate participant dividend
curl "http://localhost:3000/api/v1/participants/alice/dividend?\
stake_amount_sats=100000000&\
trust_coefficient=1.5&\
velocity_multiplier=1.2" | jq
# {
# "participant_id": "alice",
# "dividend_sats": 18000000,
# "dividend_btc": 0.18,
# "parameters": {
# "stake_amount": 100000000,
# "trust_coefficient": 1.5,
# "velocity_multiplier": 1.2
# }
# }
# 5. Get velocity data
curl http://localhost:3000/api/v1/participants/alice/velocity | jq
# {
# "participant_id": "alice",
# "velocity_multiplier": 1.2,
# "utxo_stats": {
# "avg_age_blocks": 1440,
# "tx_count_30d": 12,
# "circulation_score": "moderate"
# }
# }use bitcoin_digital_labor_derivative::simulation::*;
fn main() -> Result<(), Box<dyn std::error::Error>> {
// Create simulation state
let mut sim = SimulationState::new(
vec![
Participant::new("alice", 100_000_000, 1.5, 1.2),
Participant::new("bob", 200_000_000, 1.0, 1.1),
Participant::new("carol", 50_000_000, 2.0, 1.4),
],
1_000_000_000, // 10 BTC pool
);
// Run simulation for 365 days
for day in 1..=365 {
sim.step(day)?;
if day % 30 == 0 {
let report = sim.generate_report();
println!("Day {}: RBI = {:.2}", day, report.rbi);
}
}
// Generate final report
let final_report = sim.generate_report();
println!("\nSimulation Results:");
println!(" Final RBI: {:.2}", final_report.rbi);
println!(" Total distributed: {} sats", final_report.total_distributed);
println!(" Avg velocity: {:.2}", final_report.avg_velocity);
Ok(())
}use bitcoin_digital_labor_derivative::api::GlobalNode;
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
// Create global node instance
let node = GlobalNode::new();
// Set pool balance
node.set_pool_balance(1_000_000_000)?; // 10 BTC
// Get current pool balance
let balance = node.get_pool_balance()?;
println!("Current pool: {} sats", balance);
// Get RBI status
let rbi_status = node.get_rbi_status().await?;
println!("RBI: {:.2} ({})",
rbi_status.value,
rbi_status.status
);
// Calculate dividend for participant
let dividend = node.calculate_participant_dividend(
"alice",
100_000_000, // 1 BTC stake
1.5, // trust
1.2, // velocity
).await?;
println!("Dividend: {} sats", dividend);
Ok(())
}This roadmap reflects the current state following the v1.0.0 stable release.
Future work is additive and will not modify protocol economics or public APIs without a major version bump.
Click to expand completed features
- Protocol-complete economic model
- Velocity-based scoring with bounded multipliers
- Time-weighted trust coefficients (5 duration brackets)
- Recession Bypass Index (RBI) computation and alerts
- Bitcoin Core–backed chain data integration (read-only)
- SQLite-backed participant registry with anti-sybil features
- Production-safe RPC handling (bounded queries, reorg awareness)
- Security model and threat boundaries documented
- Complete architecture and formal protocol specification
- REST API with global node access
- Deterministic simulation framework
- Comprehensive test suite (unit + integration + simulation)
Target: Q2 2026
- Chain Data Adapters
- Esplora HTTP API adapter
- Electrum protocol adapter
- Custom indexer support
- Testnet Support
- Testnet deployment guides
- Configuration profiles
- Faucet integration
- Operator Tooling
- CLI management tools
- Diagnostics and monitoring
- Prometheus metrics export
- Grafana dashboards
- Storage Improvements
- PostgreSQL adapter
- Redis caching layer
- Backup/restore utilities
- Testing Enhancements
- Extended failure mode coverage
- Chaos engineering tests
- Performance benchmarks
Target: Q3 2026
- Economic Data Providers
- HTTP-based oracle integration
- Multiple data source aggregation
- Weighted oracle consensus
- Fallback mechanisms
- RBI Enhancements
- Historical trend analysis
- Predictive modeling
- Advanced alert conditions
- Multi-timeframe analysis
- Monitoring & Alerting
- Email/SMS notifications
- Webhook integrations
- Slack/Discord bots
- Custom alert rules
- Analytics Tools
- Historical data replay
- Economic impact reports
- Visualization dashboards
- Export to CSV/JSON
Target: Q4 2026
- Miner Coordination
- Miner dashboard UI
- Contribution tracking
- Voting interface
- Reputation system
- Governance Workflows
- Proposal submission
- Discussion forum integration
- Vote tallying automation
- Parameter update execution
- Public Interfaces
- Public analytics portal
- Real-time RBI dashboard
- Participant leaderboards
- Network statistics
- Third-Party Integration
- SDKs (Python, JavaScript, Go)
- Plugin architecture
- Webhook system
- GraphQL API
- Research & Analysis
- Long-term economic studies
- Academic partnerships
- Peer review process
- Conference presentations
Major version (v2.0.0+) required for:
- Core economic formula changes
- Trust or velocity invariant modifications
- Public trait interface breaking changes
- Security assumption revisions
- Bitcoin consensus requirement changes
Potential Explorations:
- Lightning Network integration for velocity tracking
- Multi-sig coordination contracts
- Cross-chain oracle bridges (research only)
- Zero-knowledge proof integrations
- Hardware wallet support
| Phase | Progress | Status |
|---|---|---|
| Phase 1 (v1.0.0) | ████████████ 100% | ✅ Complete |
| Phase 2 (v1.1.x) | ███░░░░░░░░░ 25% | 🚧 In Progress |
| Phase 3 (v1.2.x) | ░░░░░░░░░░░░ 0% | 📋 Planned |
| Phase 4 (v1.3.x) | ░░░░░░░░░░░░ 0% | 📋 Planned |
The Bitcoin DLD Protocol is built with security as a foundational principle:
|
|
| Audit Type | Status | Date | Findings |
|---|---|---|---|
| CodeQL Static Analysis | ✅ Passed | 2026-02 | 0 vulnerabilities |
| Dependency Audit | ✅ Passed | 2026-02 | 0 high-risk deps |
| Manual Code Review | ✅ Complete | 2026-02 | Security-focused |
In-Scope Threats (actively mitigated):
- ✅ Malformed RPC responses
- ✅ Chain reorganizations
- ✅ Pruned nodes
- ✅ Network failures
- ✅ Cache invalidation
- ✅ Economic data anomalies
- ✅ DoS via unbounded scans
Out-of-Scope (external to this software):
- Bitcoin Core compromise
- User key compromise
- Miner collusion
- Consensus changes
// ✅ Good: Bounded chain queries
let utxos = chain.get_utxos_in_range(
start_height,
end_height.min(start_height + MAX_SCAN_WINDOW)
)?;
// ✅ Good: Defensive error handling
let trust = calculate_trust(duration)
.unwrap_or(DEFAULT_TRUST_COEFFICIENT);
// ✅ Good: Input validation
if velocity < MIN_VELOCITY || velocity > MAX_VELOCITY {
return Err("Invalid velocity multiplier");
}If you discover a security issue:
- DO NOT open a public issue
- Email: security contact - see SECURITY.md
- Include: description, steps to reproduce, potential impact
- We'll respond within 48 hours
- Coordinated disclosure after fix
Full security policy and vulnerability reporting guidelines:
👉 SECURITY.md
We welcome contributions from the community! Here's how you can help:
| Area | How to Help | Skill Level |
|---|---|---|
| 🐛 Bug Reports | Found an issue? Open a ticket | Beginner |
| 📝 Documentation | Improve docs, fix typos | Beginner |
| ✅ Testing | Add test cases, run simulations | Intermediate |
| 💻 Code | Fix bugs, add features | Intermediate |
| 🔬 Research | Economic analysis, papers | Advanced |
| 🏗️ Architecture | Design proposals, RFCs | Advanced |
- Fork the repository
- Clone your fork locally
- Create a feature branch
git checkout -b feature/amazing-feature
- Make your changes
- Test thoroughly
cargo test --all cargo clippy --all-targets cargo fmt --all - Commit with clear messages
git commit -m "Add amazing feature" - Push to your fork
git push origin feature/amazing-feature
- Open a Pull Request
Code Style:
# Format code
cargo fmt --all
# Check lints
cargo clippy --all-targets --all-features
# Run tests
cargo test --all
# Check for security issues
cargo auditCommit Messages:
- Use present tense: "Add feature" not "Added feature"
- Be descriptive: "Add velocity caching" not "Update code"
- Reference issues: "Fix #123: Resolve RBI calculation error"
Pull Requests:
- Describe what and why, not just how
- Include tests for new features
- Update documentation as needed
- Keep PRs focused and atomic
- Respond to review feedback promptly
All contributions must include tests:
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn test_trust_coefficient_calculation() {
let stake = TimelockedStake { /* ... */ };
let trust = stake.calculate_trust_coefficient(800_000);
assert_eq!(trust, Decimal::new(10, 1)); // 1.0
}
}- Update README.md for user-facing changes
- Add inline comments for complex logic
- Update docs/ for architectural changes
- Include examples for new features
- Open a Discussion
- Join our community (see below)
- Read existing docs and issues first
| Document | Description | Audience |
|---|---|---|
| 🏛️ ARCHITECTURE.md | System design, components, and data flow | Developers |
| 🔒 SECURITY.md | Security model, threat analysis, and boundaries | Security researchers |
| 🌐 API.md | Complete REST API reference and examples | API users |
| 📄 PAPER.md | Full research paper and mathematical proofs | Academics |
| 📊 ANALYSIS.md | Economic modeling and impact analysis | Economists |
- 📝 CHANGELOG.md - Version history and release notes
- 📋 CITATION.cff - Academic citation information
- ⚙️ Cargo.toml - Package configuration and dependencies
- 🐳 Dockerfile - Container deployment configuration
- ☁️ RENDER_DEPLOYMENT.md - Cloud deployment guide
1. Start here (README.md) ← You are here!
↓
2. Read ARCHITECTURE.md ← Understand the system
↓
3. Try Quick Start examples ← Build and run
↓
4. Explore API.md ← Integrate with your app
↓
5. Study PAPER.md ← Deep dive into economics
↓
6. Review SECURITY.md ← Security considerations
↓
7. Run simulations ← Test scenarios
If you use this software or protocol in academic or technical work, please cite:
@software{feeney2026dld,
author = {Feeney, Don Michael Jr.},
title = {Bitcoin Digital Labor Derivative Protocol},
year = {2026},
version = {1.0.0},
url = {https://github.com/dfeen87/bitcoin-digital-labor-derivative},
note = {A non-custodial, Bitcoin-native economic framework addressing
demand-shock deflation through time-locked staking and
velocity-aware distribution}
}APA Format:
Feeney, D. M., Jr. (2026). Bitcoin Digital Labor Derivative Protocol (Version 1.0.0)
[Computer software]. https://github.com/dfeen87/bitcoin-digital-labor-derivative
Full citation details: CITATION.cff
| Title | Type | Link |
|---|---|---|
| DLD Protocol: Technical Specification | Technical Paper | PAPER.md |
| Economic Analysis of Velocity Incentives | Analysis | ANALYSIS.md |
| Security Model & Threat Analysis | Security | SECURITY.md |
-
Economic Theory
- Demand-shock deflation in automated economies
- Velocity-aware distribution mechanisms
- Time-preference economic modeling
-
Protocol Design
- Non-custodial staking on Bitcoin
- Miner-coordinated governance
- Bounded incentive mechanisms
-
Computer Science
- Deterministic economic simulations
- Blockchain data analysis
- Distributed consensus systems
- Bitcoin's deflationary economics
- Universal Basic Income alternatives
- Decentralized governance mechanisms
- AI impact on labor markets
- Cryptocurrency velocity studies
| Platform | Purpose | Link |
|---|---|---|
| GitHub | Code, Issues, PRs | Repository |
| Discussions | Questions, Ideas | GitHub Discussions |
| Issues | Bug Reports | Issue Tracker |
- ⭐ Star this repository to follow updates
- 👀 Watch for release notifications
- 🔔 Subscribe to discussions for announcements
- Don Michael Feeney Jr. - Protocol Designer & Lead Developer
- Research: Economic framework and mathematical modeling
- Development: Core implementation and architecture
This protocol builds on the shoulders of giants:
- Bitcoin Core Team - For the foundation of digital scarcity and programmable money
- Satoshi Nakamoto - For inventing Bitcoin and solving the double-spend problem
- The Bitcoin Mining Community - For securing the network and making this protocol possible
- Open Source Community - For the tools, libraries, and inspiration
Special Thanks:
- Rust programming language community
- Bitcoin development ecosystem
- Economic researchers studying automation impacts
- Early testers and contributors
Is this a fork of Bitcoin?
No. The DLD Protocol is built on top of Bitcoin, using only standard Bitcoin features like OP_CHECKLOCKTIMEVERIFY for timelocks. It doesn't modify Bitcoin's consensus rules or require any changes to Bitcoin Core.
Do I need to give up custody of my Bitcoin?
No. The protocol is completely non-custodial. You maintain full control of your private keys. Time-locked stakes use Bitcoin's native timelocks - you're locking your own coins in your own address, not sending them to anyone.
How does this differ from staking on other blockchains?
Traditional PoS staking requires delegating tokens to validators. DLD uses Bitcoin's time-locked UTXOs - you're proving commitment by making your coins temporarily unspendable in your own address, not transferring them anywhere.
Where does the dividend pool come from?
Bitcoin miners voluntarily contribute a percentage of their block rewards and/or transaction fees. This creates a sustainable, decentralized funding mechanism without any central authority or external dependencies.
Is this like a DAO or DeFi protocol?
No. This is Bitcoin-native only. No smart contracts, no wrapped tokens, no sidechains. Governance happens through miner voting weighted by contribution and reputation. All economic calculations happen off-chain with on-chain verification.
What happens if miners stop contributing?
Contribution is voluntary and incentivized by network effects. If contributions decrease, the pool shrinks proportionally, but the protocol continues functioning. Miners benefit from increased Bitcoin adoption and value.
Can this scale to millions of participants?
The v1.0.0 implementation is an analytical and monitoring tool. Future versions will explore scaling solutions including:
- Batched distribution transactions
- Lightning Network integration
- Hierarchical registry structures
- Off-chain coordination with on-chain settlement
How is velocity calculated without invading privacy?
Velocity analysis uses public blockchain data only - UTXO age and transaction patterns visible on the Bitcoin blockchain. No personal information or off-chain data required. Users who value privacy can choose not to participate.
Is this production-ready?
The v1.0.0 release provides a production-ready analytical core for:
- Economic simulations
- RBI monitoring
- Velocity analysis
- Read-only chain integration
Transaction construction and fund custody features are planned for future releases.
How can I contribute?
See the Contributing section above! We welcome:
- Bug reports and feature requests
- Documentation improvements
- Code contributions
- Economic research and analysis
- Testing and feedback
I would like to acknowledge Microsoft Copilot, Anthropic Claude, and OpenAI ChatGPT for their meaningful assistance in refining concepts, improving clarity, and strengthening the overall quality of this work.
MIT
Bitcoin Digital Labor Derivative Protocol
Transforming cold storage into economic participation
Documentation • Research • Security • API
Made with ❤️ by the DLD Protocol team and contributors