XIP-43: Consent Proofs

rygine · February 22, 2024, 9:19pm

xmtp/XIPs/blob/main/XIPs/xip-43-permission-pref-proofs.md

---
xip: 43
title: Consent proofs
description: Enables recipients to sign to specify inbox consent preferences
author: Ry Racherbaumer (@rygine), Nick Molnar (@neekolas), Saul Carlin (@saulmc)
status: Final
type: Standards
category: Interface
created: 2024-02-22
---

## Abstract

This XIP proposes to add an _optional_ signed payload to conversations that client apps can consider as proof that a recipient has granted a sender consent to reach their main inbox.

## Motivation

Today, a recipient must use a full XMTP client to set a universal permission preference such as allowing a sender. This presents challenges to senders due to the XMTP client's bundle size and integration requirements. For integrations such as simple subscribe buttons, these hurdles can be blockers.

To solve these issues, senders can simply ask users to produce a signature attesting to the consent update. Inbox apps can consider this signature as proof that the recipient has explicitly opted in to receive the sender's messages. This eliminates the bundle size problem, as very little code is required to initiate signing a message with a user's wallet. It also greatly simplifies integration by providing a single function to obtain the user's signature and return an encoded payload to be used by SDKs to verify the granted consent.

This file has been truncated. show original

saul · March 21, 2024, 2:25am

@rygine Do nodes have visibility into the validity of a permission proof? Or is only the recipient client able to validate it?

rygine · March 21, 2024, 8:39pm

@saul they do not. a private key is required to validate the signature.