StellarExpert - New features and public Directory API

Fresh StellarExpert release is deployed, and I'd like to share some info about new features implemented since previous major release.

• XLM supply chart shows the circulating amount and its changes over time.
  
• Open Directory API for developers. Use a curated list of well-known account addresses in your application.
• New Directory explorer interface.
  
• All dates displayed in UTC format, no more problems with local browser timezone conversions.
• Multiple minor bugs fixed, performance improved. The explorer and ingestion engine are now stable.

Special thanks to @irisli, who maintained the original Stellar directory. Sorry to see that StellarTerm is shutting down.

dzham I can add the fields query parameter to the API to force endpoints return only specific fields, the same way Google and other data providers do this.

For example,

/directory?fields=accepts,name

will return something like

{
  "_links": {...},
  "_embedded": {
    "records": [
      { 
        "address" : "GA6HCMBLTZS5VYYBCATRBRZ3BZJMAFUDKYYF6AH6MVCMGWMRDNSWJPIH",
        "paging_token": "GA6HCMBLTZS5VYYBCATRBRZ3BZJMAFUDKYYF6AH6MVCMGWMRDNSWJPIH", 
        "name" : "Changelly", 
        "accepts" : {
          "memo" : "MEMO_ID"
        }
      },
      { 
        "address" : "GBR3RS2Z277FER476OFHFXQJRKYSQX4Z7XNWO65AN3QPRUANUASANG3L", 
        "paging_token" : "GBR3RS2Z277FER476OFHFXQJRKYSQX4Z7XNWO65AN3QPRUANUASANG3L", 
        "name" : "PapayaBot", 
        "accepts" : {
          "memo" : "MEMO_TEXT", 
          "merge" : true, 
          "pathPayment" : true
        }
      }
    ]
  }
}

What do you think?

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"
    ]
}