mirror of
https://github.com/logos-messaging/specs.git
synced 2026-01-02 14:13:06 +00:00
separate recommendations for contract vs app devs
This commit is contained in:
parent
50d7272910
commit
2c65185669
@ -54,6 +54,9 @@ Contract parameters and their RECOMMENDED values for the initial mainnet deploym
|
||||
| Membership price for `1` message per epoch | `p_u` | `0.01` | `USD` |
|
||||
| Membership expiration term | `T` | `180` | days |
|
||||
| Membership grace period | `G` | `30` | days |
|
||||
| Accepted tokens | | `DAI` | |
|
||||
|
||||
The pricing function SHOULD be linear in the rate limit per epoch.
|
||||
|
||||
## Membership lifecycle
|
||||
|
||||
@ -174,14 +177,6 @@ User-facing application SHOULD suggest one or a few rate limits (tiers) to simpl
|
||||
- `200` messages per epoch as mid-tier;
|
||||
- `600` messages per epoch as high-tier.
|
||||
|
||||
The RECOMMENDED pricing parameters are:
|
||||
|
||||
| Parameter | Value |
|
||||
| ------------------ | ------ |
|
||||
| Accepted tokens | `DAI` |
|
||||
| Reference currency | `USD` |
|
||||
| Pricing function | linear |
|
||||
|
||||
User-facing applications SHOULD save membership expiration dates in a local keystore during registration,
|
||||
and notify the user when their membership is about to expire.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user