Storage limits
Makechain V2 keeps per-account storage bookkeeping keyed by owner_address.
Base model
Accounts start with default-zero rented units plus the protocol's built-in base allocation.
Additional capacity enters the protocol only through STORAGE_CLAIM.
Ingress path
STORAGE_CLAIM is the only Tempo-backed storage ingress path in V2.
Legacy STORAGE_RENT relay messages are removed and invalid.
Merge request quota
Merge requests consume the target project owner's storage quota:
| Resource | Effective limit |
|---|---|
| Merge requests per target project | 20 + storage_units × 20 |
The target project owner funds capacity because merge requests occupy the target project's namespace.
Both active entries and tombstones count toward the limit. When the limit is exceeded, the oldest entries are pruned first. Pruning an active entry deletes the forward row, deletes the matching reverse row, and decrements merge_request_count. Pruning a tombstone deletes only that tombstone row and leaves the prune marker behind.
As with other storage-sensitive message types, expired storage grants are swept before quota enforcement.
Current implementation note
Appendix A now assigns both DEVNET and TESTNET to the Tempo Moderato StorageRelay proxy 0x930dc180AaD00fc9302278d502Ff8b52bB0a0F79.
MAINNET still uses the zero-address fail-closed sentinel until its canonical StorageRelay deployment is published.