By Tobi Loba
Wietse Wind, a lead developer at XRP Ledger, has taken his time to answer a necessary question directed to him by a supposed XRP community member, regarding the linking of multiple XRP public addresses to a PayID.
Back in mid-June 2020, Ripple, the US-based cross-border payment company, announced its coalition with over 40 other related firms across the world, to launch PayID, the universal payment identifier created to provide a replacement for complex account numbers, routine number, and SWIFT code.
Linking Multiple XRP Public Addresses to a PayID
A user identified on Twitter as “Just another chap” took to the microblogging platform to ask Wietse Wind, the founder of XRP Labs, about the possibility of linking multiple XRP addresses to a PayID.
The Supposed XRP holder asked:
“Hey Wietse Wind congrats on your tremendous efforts on PayID. Quick Q: can you link more than one XRP public address to a PayID. If so, how is it determined which address would receive? Would the sender have to select which address to send to?”
In response to the user’s inquiry, Wietse Wind wrote:
“Yes, the PayID standard specifies a preferred address and alternate addresses.”
Yes, the PayID standard specifies a preferred address, and alternate addresses.
— WietseWind – 🛠 XUMM @ XRPL Labs (@WietseWind) June 19, 2020
Galgitron Has a Contrary Opinion
Galgitron, a channel based on Ripple and XRP, weighed in with a contrary opinion, stating that there is nowhere in the whitepaper that made such a specification:
“You know I love you man, but I don’t see anything in the whitepaper specs that specifies preferred. Just an array of addresses. If there were two XRP addresses, I can’t see how PayId facilitates which one is used by the client.”
You know I love you man, but I don't see anything in the whitepaper specs that specifies preferred. Just an array of addresses. If there were two XRP addresses, I can't see how PayId facilitates which one is used by the client.
— galgitron (don't ask for predictions) (@galgitron) July 8, 2020
Responding to galgitron’s assertion, Wietse Wind noted:
“I can’t find it in the specs but it’s in the source code generating the response: (preferredAddresses response property) – It now returns a filtered list based on request headers, but it can easily return a list based on user defined preference.
“I can’t find any reference to the `preferredAddresses` property in eg. the Xpring SDK (client). I’ll ask around what the idea is, and if it’s legacy in the PayID server or missing in the RFCs.”