Draft: add DIP for transparent Platform contact payments via DashPay relationship xpubs

[QuantumExplorer]

Summary

• add an alias-named draft DIP for transparent Platform contact payments via DashPay relationship xpubs
• specify reuse of the existing DIP-15 contact xpub instead of adding a second encrypted xpub to contact requests
• reserve the terminal child-index subspace 2^30 + i for transparent Platform contact payments

Notes

• follows the repository guidance to avoid self-assigning a DIP number
• leaves shielded / zk contact payments out of scope for a future proposal

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 47ccadf1-e6e3-48b5-8741-876092ef6b8c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/dip-contact-xpub-platform-addresses

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[hilawe]

@QuantumExplorer quick scope question on this draft.

Does it cover paying a username you have no existing contact relationship with or is it limited to payments between established contacts? Reusing the DIP-15 contact xpub reads to me as the latter, but I'd rather ask than assume.

Asking because I'm scoping a community project on private payments to any username with @TheDesertLynx and I'd rather not design over something already specified here.