Retention and storage
Nothing on an app lane is kept forever. How long an event lives depends on its kind and on whether your lane is a known tenant.
How long events live
| Kind | Known tenant | Public lane |
|---|---|---|
| Ephemeral (20000–29999) | Relayed live, never stored | Relayed live, never stored |
| Regular | Up to 7 days | 2 hours |
| Replaceable / addressable (0, 3, 10000–19999, 30000–39999) | 30 days | 2 hours |
Replaceable and addressable events are refreshed every time you publish a newer version, so data you keep updating stays. A shorter NIP-40 expiration tag is honoured; a longer one is capped.
On a public lane, an event that is published once and never updated disappears after 2 hours. The current value is always in the relay information document (cinder_addressable_ttl_sec, retention).
Quotas
| Quota | Known tenant | Public lane |
|---|---|---|
| Addresses per author and kind | 64 | 16 |
| Size of one addressable event | 32 KB | 32 KB |
| Addressable data per author (all kinds) | 8 MB | 2 MB |
Stored events per #p recipient | 500 (oldest dropped) | 500 (oldest dropped) |
Each lane storage also has a total ceiling of 128 MB for addressable events and 128 MB for other stored events. When a ceiling is reached, the events closest to expiry are removed first.
Avoid kind 30078
Kind 30078 is used by Cinderous for encrypted backups and is handled specially on the messenger side. Pick another addressable kind for your app.