# 2.0.7644

## 2.0.7644

#### [docs](https://liquidapps.gitbook.io/liquidapps-documentation)

#### [@liquidapps/zeus-cmd](https://www.npmjs.com/package/@liquidapps/zeus-cmd)

* add errors noting that eosio-cpp and nodeos must be installed to run zeus
* add waxtest and wax default networks
* add `regmapping` action to eosio evm bridge so author can enable bridge transfer of NFT collection, schma name, template id, immutable data.  NFT cannot be sent to bridge if not whitelisted
  * also add for eosio <> eosio bridge
* enable multi erc721 eosio -> evm support, collection, schema name, template, immutable data and erc721 token address can be used to run the regmapping action from above
* add default evm networks to `zeus-config.js`

#### [@liquidapps/dsp](https://www.npmjs.com/package/@liquidapps/dsp)

#### [@liquidapps/dapp-client](https://www.npmjs.com/package/@liquidapps/dapp-client)

#### [@liquidapps/box-utils](https://www.npmjs.com/package/@liquidapps/box-utils)

#### dappservices contract

### DSP Services:

#### [LiquidAccount Service](https://docs.liquidapps.io/en/v2.0/services/vaccounts-service.html)

#### [LiquidVRAM Service](https://docs.liquidapps.io/en/stable/services/ipfs-service.html)

#### [LiquidStorage Service](https://docs.liquidapps.io/en/stable/services/storage-service.html)

#### [LiquidHarmony Service](https://docs.liquidapps.io/en/stable/developers/harmony-getting-started.html)

#### [LiquidScheduler Service](https://docs.liquidapps.io/en/stable/developers/cron-getting-started.html)

#### [LiquidLink Service](/liquidapps-documentation/dapp-network-services/dapp-network-services/liquidlink.md)

#### Link Library


---

# Agent Instructions: 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:

```
GET https://docs.liquidapps.io/liquidapps-documentation/release-notes/history/latest-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.