MisterTicot Completely agree with you, Federation Protocol is awesome, and is widely supported in the ecosystem. However, the Directory contains a list of well-known addresses and advanced properties (like accepted memo type), regardless of the Federation support.
For example, even if most of the addresses from the list do support federation, you have to query them all in order to retrieve a friendly name for each of them. In some cases, it just won't work. For example, on the StellarExpert Assets page more than 20 asset issuers are displayed at a time. That's 20 requests to Horizon and 20 more to the corresponding stellar.toml files.
Again, the Directory contains extended metadata for each anchor. Papayabot supports not only PAYMENT
but also MERGE_ACCOUNT
and PATH_PAYMENT
operations; it also requires MEMO_TEXT
to be set.
That's why the record looks like
{
"address" : "GBR3RS2Z277FER476OFHFXQJRKYSQX4Z7XNWO65AN3QPRUANUASANG3L",
"name" : "PapayaBot",
"domain" : "papayabot.com",
"accepts" : {
"memo" : "MEMO_TEXT",
"merge" : true,
"pathPayment" : true
},
"tags" : [
"anchor",
"issuer"
]
}