package common.v1

Get desktop application:
View/edit binary Protocol Buffers messages

OneToOneConvoId should contain the two convo partners' userjids that are sorted in a consistent way.

Used in: XiConvoId

• repeated XiBareUserJid users = 1

Follows the form <cryptographic hash>_a@talk.kik.com, ex., abcdefCDEF01234567890123456789-_-_-_ghijkGHIJKxyz_a@talk.kik.com You can use an alias jid when you want to hide real jids from users. Consider the case of people spamming members of public groups. The spammer joins the group and would normally get all the real jids of the group members. There's nothing in our system that can prevent the spammer from sending unwanted messaging at that point. By using an alias jid, the spammer won't get the real jids right away but instead would only get an alias jid. We can then use that to control whether or not we want to give over the real jid that is associated with that alias jid. The real jid/s is/are encrypted here as part of the local_part below and it should be difficult for hackers or spammer to reverse that. A reverse look-up table of alias jids to real jids will be maintained elsewhere. Also, and given real jids x, y, and z, they should always map to the same alias jid. Alis Jid Mapper Service: https://github.com/kikinteractive/xiphias-service-alias-jid-mapper

Used in: entity.v1.AliasBlockEntry, entity.v1.EntityKey, entity.v1.GroupMemberRoster, matching.v1.AnonMatchingSessionKey, XiAnyJid, XiBareUserJidOrAliasJid, mobile.entity.v1.RequestedJid, mobile.matching.v1.SessionDetails

• string local_part = 1

• oneof jid_type

  • XiBareUserJid bare_user_jid = 1

  • XiAliasJid alias_user_jid = 2

  • XiGroupJid group_jid = 3

Used in: messagepath.v1.Keyboard, messagepath.v1.MentionReplyAttachment, messagepath.v1.VisibilityRulesAttachment, mobile.kin.payment.v1.GetPayToUserJwtRequest, mobile.kin.payment.v1.GetUsersReceiveTransactionLimitsRequest, mobile.kin.payment.v1.ProcessPaymentToUserRequest, mobile.kin.payment.v1.UserTransactionLimits

• oneof jid_type

  • XiBareUserJid bare_user_jid = 1

  • XiAliasJid alias_user_jid = 2

************************************************************************************************* Convo Identifier *************************************************************************************************

Used in: entity.v1.EntityConvo, entity.v1.EntityKey, mobile.entity.v1.GetConvosRequest, mobile.entity.v1.GetConvosResponse, mobile.profile.v1.SetConvoProfileRequest

• oneof kind

  • OneToOneConvoId one_to_one = 1

  • XiGroupJid group = 2

Used in: kin.authentication.v1.OfferJwt, product.v1.PaymentConfirmation, mobile.kin.authentication.v1.GenerateUserJwtResponse, mobile.kin.payment.v1.ProcessPaymentToUserRequest

• string jwt = 1

For user-to-user in public groups, we rely on JWTs for executing and verifying transactions The user-to-user payment JWT include both the sender and recipient IDs. In order to preserve privacy controls in public groups, these IDs will be a hashed version of the user real JID. It'll be called the Kin User ID Much like alias jids, the sender cannot use the KIN user ID to directly message the recipient in a public group Also, the KIN user ID is used to map clients to their wallet addresses on the blockchain The KIN user ID is included on the user profile. It is 32-bit encoded string

Used in: entity.v1.KinUserIdElement

• string id = 1