---

Earning rules

Last updated: 29.04.2024

Rule 1 (Device State): Devices can have different states during their lifetime (enabled, idle, alert, or error). The most important is the idle state, which means the device is working properly and sending the Keep-Alive signal periodically. A functioning network is the core state of the project, so points are awarded for devices in the Idle state.

Rule 2 (Referral Points): Points are also awarded by the referral system. Any user can send his referral code to his friends and family. Before adding the first device, the user can add the referral code he received. After the first device is added, the referral code can no longer be used. A referral code can be used by many users, but a user can only use one referral code. If the referral code is valid, a referral reward of 1000 points will be added to both the referrer’s and referee’s accounts during the daily points distribution.

Rule 3 (Reward Time): Points are awarded by an automatic process that calculates the amount each user receives on a daily basis, at midnight, between 00:00 – 01:00 GMT+0. The calculation includes both points earned from maintaining devices and from the referral system.

---

Level Reward System

Last updated: 01.03.2024

Level 1 (Novice Keeper): 10 Points / Idle Device / Day (24h)

Level 2+ (Sensor Squire): Coming Soon!

---

Lithium Guidelines

Last updated: 29.04.2024

For a community safety network to work, all participants must agree on some basic guidelines for understanding how devices work, how they can be used, and how to translate different events that occur in the network.

1. The compatible sensors used in the security network are intended for no other purpose than to protect your assets and loved ones, even though the devices may have other applications. For example, motion detection may be used for automatic light triggering or room occupancy, but in the Lithium use case it is used solely to detect unauthorized movement in a defined space.
2. Depending on the type of device, the placement/setup must be chosen to reduce false positives and avoid unintentionally triggering devices by detecting other non-emergency situations. For example:
   • The flood sensor should ideally be placed in a dry area under the sink, not in the bathtub or directly exposed to potential water splashes;
   • The fire sensor should be placed in a non-smoking room, no cooking room or outdoors;
   • The motion sensor should be placed indoors, facing a target space with no constant or random movement;
   • The door/window open/close sensor should typically be placed at the front door or patio door of the building to allow the user to receive alerts while away;
   • The panic sensor can be carried in a pocket or on a keychain, allowing the user to quickly press the SOS button.
3. Depending on the category of device, some additional actions may be necessary to ensure proper operation, workflow, and reduction of false alarms. For example, for devices in the Security category to send alerts, it is necessary to “arm” the system using the in-app button. To stop sending alerts and reduce false alarms, always remember to “disarm” the security system when it is not needed, such as when you return home.
4. The safety network is designed to detect and alert nearby users in the event of an emergency. Since emergencies such as fire, flood, and robbery do not occur very often, a limit is placed on the number of public alerts shared to reduce the number of false positives and prevent panic from spreading. If the sensor sends alerts erratically, or too many in a short period of time, it may be improperly placed or defective.
5. Therefore, the current daily limit is set to 2 public shared emergencies per day (either published automatically or manually). A device can be triggered multiple times during the day and the alert notification will automatically be sent to the owner of the sensor, but only the first 2 alerts will notify nearby users.
6. In addition, if a sensor sends too many public shared alerts in two consecutive days (48 hours), more specifically, if it sends more than 4 alerts, the cooldown period for that device will begin.
7. Cooldown Mechanism: The cooldown mechanism is designed to ensure that nearby users are neither panicked nor bothered by false alarm notifications. When a sensor exceeds the cooldown limit, Silent Mode is automatically enabled without the ability to manually disable it before the cooldown period ends.

IMPORTANT: The Lithium App is currently in the beta phase. To minimize false alarms, only a select few devices can automatically send alerts to nearby users. Both current compatible devices and potential new models are under careful supervision and testing. New models capable of automatic alerts will be announced in due course. In the meantime, alerts are always sent to the device owner, who can choose to share them publicly with nearby users. Lithium is dedicated to reducing false alarms and collaborates with the community to test compatible devices and develop mechanisms for better emergency identification in the future.