'/%3e%3cpath%20d='M31.5%2015.5c-.4-2.6.2-4.6%201.8-6'%20stroke='%236b4a1f'%20stroke-width='2.2'%20stroke-linecap='round'%20fill='none'/%3e%3cpath%20d='M33.5%2012.5c4.5-7.5%2013-10.5%2021-8.5-3.2%207.8-12%2011.4-21%208.5z'%20fill='url(%23leaf)'/%3e%3cpath%20d='M34.5%2012c6-2.8%2011.5-5%2017.5-6.8'%20stroke='%23e6f7da'%20stroke-opacity='0.55'%20stroke-width='1.1'%20stroke-linecap='round'%20fill='none'/%3e%3cellipse%20cx='31.8'%20cy='15.2'%20rx='3.4'%20ry='1.4'%20fill='%23b44e07'%20opacity='0.45'/%3e%3cellipse%20cx='22'%20cy='27'%20rx='9.5'%20ry='6'%20fill='url(%23shine)'%20transform='rotate(-32%2022%2027)'/%3e%3ccircle%20cx='19.5'%20cy='25'%20r='1.4'%20fill='%23ffffff'%20opacity='0.65'/%3e%3c/svg%3e){kind=small}
User Identification
Every user receives a unique numeric ID when their account is created. This ID is used as the public user identifier across the protocol.
- IDs are positive integers, starting from 5-digit numbers (10000+)
- ID ranges grow automatically as ranges fill up (5→6→...→10 digits)
- Maximum 10 digits (for OSCAR compatibility)
- IDs are generated using Format-Preserving Encryption (FPE) to appear random while guaranteeing uniqueness
All protocol fields referencing users use numeric IDs (JSON number type).