Skip to content

ENSIP-31: Payment Preferences - #87

Open
nxt3d wants to merge 15 commits into
ensdomains:masterfrom
nxt3d:ensip/payment-preferences-snapshots
Open

nxt3d wants to merge 15 commits into
ensdomains:masterfrom
nxt3d:ensip/payment-preferences-snapshots

Conversation

@nxt3d

@nxt3d nxt3d commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Proposes Payment Preferences so senders who know an ENS name can discover the recipient's preferred chains for an asset. Preferences are stored through ENSIP-24 as ordered ERC-7930 Chain Identifiers, keyed by a fingerprint from an immutable Multichain Token Registry. The draft defines the registry interface, supports native assets and tokens, and explains that snapshots identify submitted data without establishing authenticity. It includes a verified Sepolia reference deployment; clients remain responsible for assessing preferences alongside other payment information.

@github-actions

Copy link
Copy Markdown

Thanks for submitting an ENSIP. An editor will be along to review your proposal and assign it a permanent number using /assign-ensip.

In the meantime, please make sure your proposal follows the submission checklist. We're glad you're here.

@wentelteefje

Copy link
Copy Markdown
Member

/assign-ensip

@github-actions

Copy link
Copy Markdown

All set — this proposal is now ENSIP-31. The number is reserved.

Could you make these changes to your PR so it's ready to merge?

  • Rename ensips/x.mdensips/31.md
  • Update the H1 heading in that file to start with # ENSIP-31:
  • Update the PR title to start with ENSIP-31:

Thanks!

@nxt3d nxt3d changed the title ENSIP: Payment Preferences ENSIP-31: Payment Preferences Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants