chemaclass/unspent
Composer 安装命令:
composer require chemaclass/unspent
包简介
A PHP library for UTXO-like bookkeeping using unspent entries.
关键字:
README 文档
README
Track value like physical cash in your PHP apps. Every unit has an origin, can only be spent once, and leaves a complete audit trail.
$ledger = Ledger::inMemory(); $ledger->credit('alice', 100)->transfer('alice', 'bob', 25); echo $ledger->totalUnspentByOwner('bob'); // 25
Zero-dependency PHP 8.4+ library implementing the UTXO model, inspired by Bitcoin and decoupled as a standalone library.
Table of Contents
- Why?
- When to use it
- Install
- Quick Start
- Output types
- Examples
- Documentation
- Learning Path
- FAQ
- Contributing
Why?
Traditional balance tracking (balance: 500) is just a number you mutate. There's no history, no proof of where it came from, and race conditions can corrupt it.
Unspent tracks value like physical cash. You can't photocopy a $20 bill - you spend it and get change back. This gives you:
- Double-spend prevention — a unit can only be spent once, ever
- Complete audit trail — trace any value back to its origin
- Immutable history — state changes are additive, never mutated
- Advanced locks — timelocks, multisig, hash-locked outputs (HTLCs)
- Zero external dependencies — pure PHP 8.4+
When to use it
| Need | Traditional Balance | Unspent |
|---|---|---|
| Simple spending | Easy | Overkill |
| "Who authorized this?" | Requires extra logging | Built-in |
| "Trace this value's origin" | Requires event sourcing | Built-in |
| Concurrent spending safety | Race conditions | Atomic |
| Conditional spending rules | Custom logic needed | Lock system |
| Regulatory audit trail | Reconstruct from logs | Native |
Use Unspent when value moves between parties, you need to prove who authorized what, or audit trail is a requirement.
Skip it when you only need a simple counter, single-user balance, or no audit requirements.
Limitations
| Limitation | Details |
|---|---|
| Integer bounds | Amounts bounded by PHP_INT_MAX (~9.2e18). Wrap for arbitrary precision. |
| Single-node model | Single-node operation. For distributed consensus, add Raft/blockchain infrastructure. |
| No built-in rate limiting | Your application must implement rate limiting. |
| Memory for large datasets | In-memory ~1MB/1k outputs. Use store-backed mode for >100k outputs. |
| Not for sub-second precision | Timestamps not enforced; not a real-time trading engine. |
Install
composer require chemaclass/unspent
Quick Start
In-Memory (prototyping)
use Chemaclass\Unspent\Ledger; $ledger = Ledger::inMemory(); $ledger->credit('alice', 1000) ->credit('bob', 500) ->transfer('alice', 'bob', 200) ->transfer('alice', 'bob', 100, fee: 5) ->debit('bob', 50); $ledger->totalUnspentByOwner('alice'); // 695 $ledger->totalUnspentByOwner('bob'); // 750
| Method | Description |
|---|---|
credit($owner, $amount) |
Mint new value to owner |
transfer($from, $to, $amount, $fee) |
Move value between owners |
debit($owner, $amount, $fee) |
Burn value from owner |
SQLite persistence (production)
use Chemaclass\Unspent\Persistence\Sqlite\SqliteRepositoryFactory; use Chemaclass\Unspent\Output; $repo = SqliteRepositoryFactory::createFromFile('ledger.db'); $ledger = $repo->find('my-ledger') ?? Ledger::withGenesis(Output::ownedBy('alice', 1000)); $ledger->transfer('alice', 'bob', 200); $repo->save('my-ledger', $ledger);
Coin Control (full input/output control)
use Chemaclass\Unspent\Tx; $ledger = Ledger::withGenesis( Output::ownedBy('alice', 500, 'alice-savings'), Output::ownedBy('alice', 300, 'alice-checking'), ); $ledger->apply(Tx::create( spendIds: ['alice-checking'], outputs: [ Output::ownedBy('bob', 200), Output::ownedBy('alice', 100, 'alice-change'), ], signedBy: 'alice', ));
Use Coin Control for: specific output selection, custom IDs, multiple recipients, complex fees.
Batch operations
$ledger->consolidate('alice', fee: 10); $ledger->batchTransfer('alice', [ 'bob' => 100, 'charlie' => 200, 'dave' => 300, ], fee: 5);
Transaction Mempool
Stage transactions for validation before commit:
use Chemaclass\Unspent\Mempool; $mempool = new Mempool($ledger); $mempool->add($tx1); $mempool->add($tx2); // $mempool->add($conflictingTx); // Throws OutputAlreadySpentException $mempool->commit();
Output types
| Method | Use case |
|---|---|
Output::open(100) |
No lock - pure bookkeeping |
Output::ownedBy('alice', 100) |
Server-side auth (sessions, JWT) |
Output::signedBy($pubKey, 100) |
Ed25519 crypto (trustless) |
Output::timelocked('alice', 100, $time) |
Vesting, delayed payments |
Output::multisig(2, ['a','b','c'], 100) |
Joint accounts, escrow |
Output::hashlocked($hash, 100) |
Atomic swaps, HTLCs |
Output::lockedWith($lock, 100) |
Custom lock implementations |
Examples
Runnable demos under example/:
php example/run # List all php example/run game # Run a demo (also: loyalty, accounting, events, btc, wallet, locks, sqlite) php example/run game --reset # Reset state
| Alias | Demonstrates |
|---|---|
game |
In-game currency, ownership, double-spend, fees |
loyalty |
Customer rewards, minting, redemption, audit |
accounting |
Department budgets, multi-party auth, reconcile |
events |
Order lifecycle as state transitions |
btc |
Bitcoin simulation, mining, fees, consolidation |
wallet |
Ed25519 signatures, trustless verification |
locks |
Custom time-locked outputs, serialization |
sqlite |
SQLite persistence, querying, history |
See example/README.md for full output samples and the web API demo.
Documentation
Start at docs/README.md for the full index.
| Topic | What you'll learn |
|---|---|
| Core Concepts | How outputs, transactions, and the ledger work |
| Ownership | Locks (owner, timelock, multisig, hashlock), authorization |
| History | Tracing value through transactions |
| Fees & Minting | Implicit fees, coinbase transactions |
| Selection Strategies | FIFO, largest-first, exact-match, random, custom |
| Persistence | JSON, SQLite, custom storage |
| Scalability | In-memory vs store-backed mode |
| Events | PSR-14 event dispatching, integrations |
| Migration Guide | Moving from balance-based systems to UTXO |
| Troubleshooting | Common issues and solutions |
| API Reference | Ledger, Output, Tx, Mempool, UtxoAnalytics |
Learning Path
| Level | Topic | Docs | Example |
|---|---|---|---|
| 1. Basics | Outputs, transactions | Concepts | php example/run game |
| 2. Ownership | Locks, authorization | Ownership | php example/run wallet |
| 3. Persistence | SQLite storage | Persistence | php example/run sqlite |
| 4. Scale | Mode selection | Scalability | - |
| 5. Advanced | Timelocks, multisig, HTLC | Ownership | php example/run locks |
| 6. Operations | Batch, mempool, analytics | API Reference | - |
FAQ
Can two outputs have the same ID?
No. Output IDs must be unique across the ledger. If you omit the ID, a unique one is auto-generated (128-bit random entropy). Custom IDs that collide throw DuplicateOutputIdException. This mirrors Bitcoin's txid:vout model.
When should I use in-memory vs store-backed mode?
| Scenario | Recommendation |
|---|---|
| < 100k total outputs | Ledger::inMemory() or Ledger::withGenesis(...) |
| > 100k total outputs | Ledger::withRepository($repository) |
| Need full history in memory | Ledger::inMemory() |
| Memory-constrained environment | Ledger::withRepository($repository) |
See Scalability docs.
How are fees calculated?
Fees are implicit, like in Bitcoin. The difference between inputs and outputs is the fee:
$ledger->apply(Tx::create( spendIds: ['input-100'], // Spending 100 outputs: [Output::open(95)], // Creating 95 )); // Fee = 100 - 95 = 5 (implicit)
See Fees & Minting docs.
Contributing
See CONTRIBUTING.md for setup, TDD workflow, quality gates, and commit format.
composer install # Installs dependencies + pre-commit hook composer check:quick # Fast feedback: cs-fixer + phpunit composer test # Full: cs-fixer + rector + phpstan + phpunit
Docker workflow available via make help.
License
MIT — see LICENSE.
chemaclass/unspent 适用场景与选型建议
chemaclass/unspent 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 0 次下载、GitHub Stars 达 15, 最近一次更新时间为 2026 年 01 月 09 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「authorization」 「ledger」 「Accounting」 「transaction」 「bitcoin」 「wallet」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 chemaclass/unspent 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 chemaclass/unspent 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 chemaclass/unspent 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Ory-Hydra OAuth 2.0 Client Provider for The PHP League OAuth2-Client
A lightweight and powerful OAuth 2.0 authorization and resource server library with support for all the core specification grants. This library will allow you to secure your API with OAuth and allow your applications users to approve apps that want to access their data from your API.
General Ledger and Journal Accounting Package for Laravel with JSON API
PHP SDK for Ledga.io - Programmatic double-entry ledgers for finance, gaming and multi-tenant SaaS
Access auditing middleware intended for use with Slim Framework applications
Accounting module for atmosphere and laravel
统计信息
- 总下载量: 0
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 15
- 点击次数: 37
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2026-01-09