Hi everyone,
I’ve been building FiberLatch, a small backend-only experiment around Fiber payment verification and signed access receipts.
The idea is simple:
A service should only unlock a resource after it verifies that a Fiber payment is actually paid. Once verified, FiberLatch issues a signed receipt that can be verified and redeemed once.
Current milestone
FiberLatch has now reached its first live paid Fiber testnet proof.
A real paid Fiber payment_hash was verified through Fiber v0.8.1 RPC, converted into a signed access receipt, verified, redeemed once, and rejected on second redemption.
What this proves
- Live Fiber testnet payment verification
- Signed access receipt issuance
- Receipt verification
- Atomic one-time redemption
- Duplicate redemption rejection
What this does not prove
- Production readiness
- Mainnet readiness
- Merchant checkout readiness
- Generalized payment gateway behavior
Why I built this
I wanted to test a clear backend boundary:
paid Fiber payment -> signed access receipt -> one-time redemption
The important part is that invoice creation alone is not treated as proof. FiberLatch waits for the payment state before issuing access.
Links
Repo: GitHub - Ticoworld/fiber-latch · GitHub
Release: Release FiberLatch: live paid testnet proof · Ticoworld/fiber-latch · GitHub
Feedback
I’d appreciate feedback on:
- Whether the receipt model makes sense for Fiber-based access control.
- What would be most useful to improve next for Fiber developer experiments.
- Whether this direction should stay backend-only or later include a small demo client.