> For the complete documentation index, see [llms.txt](https://docs.element.market/welcome-to-element/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.element.market/welcome-to-element/spotlight/whats-new-in-element/product-updates-for-2022-09-27.md).

# Product Updates For 2022/09/27

### New Features:

* Support display domain name in BNB chain market, display rule priority: Element nickname > domain name > address

### Function Optimizations:

* Optimize ETH chain multi-market listing: shorten the caching time of Web terminal listing parameters, and increase the listing queue in the background
* Added logic so that when the NFT does not have an image URL, the default display is the collection item graph
* Optimize server performance: intercept invalid requests, shorten service timeout, and optimize front-end API routing strategy
* Optimize UX in Google search

### Bug Fixes:

* Fix the abnormal order of search results caused by using collection slug as the contract address


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.element.market/welcome-to-element/spotlight/whats-new-in-element/product-updates-for-2022-09-27.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.