QuotaCell progress: Owner revocation and treasury recovery now tested on CKB
In my previous update, I shared how QuotaCell enforces shared spending limits through CKB scripts.
This week, I focused on another important question: Can a treasury owner revoke delegated access and recover the protected funds without relying on the delegates?
I’ve now tested the owner-control lifecycle using real signed transactions on a fresh isolated CKB node, without modifying the existing policy.
The results:
-
Revocation: An owner-signed transaction revoked a delegate’s authority and committed successfully.
-
Enforcement: A newly signed payment using the updated policy state reached the node and was rejected at Q17 because the delegate was disabled. This was not a stale-Cell rejection.
-
Treasury recovery: The owner closed the policy and recovered all 200 protected synthetic tokens, along with the fund Cell’s 154 CKB capacity, into an owner-controlled token Cell. No delegate signature was required.
-
Recovery after closure: I deposited 50 of those same tokens back into the protected treasury after closure. The policy remained CLOSED, and a separate owner-signed sweep successfully recovered the deposit.
The final owner balance remained 200 tokens, since the late deposit reused previously recovered funds.
An important limitation also became clear in the executed lifecycle.
The current policy retains all 600 CKB of its policy Cell after closure, with an occupied minimum of approximately 572 CKB. That capacity isn’t a transaction fee, but it remains unavailable for reuse under this experimental design.
The recovered fund capacity is also held in owner-controlled typed token Cells, not automatically converted into freely spendable CKB.
This is still an experimental implementation using synthetic xUDT on a local CKB node. It isn’t a public-testnet release, independent reproduction or a security audit.
The broader goal is to make shared spending authority practical for CKB teams and applications, with enforceable delegation, owner control, recovery and reusable integration components.
The new signed transaction evidence, capacity accounting, validation tools and reproduction instructions are now public:
Reproduction instructions:
The next challenges are making owner recovery independently usable, improving the policy’s capital efficiency and supporting practical native CKB payments.