> For the complete documentation index, see [llms.txt](https://docs.nucleusearn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nucleusearn.io/nucleus-architecture/smart-contracts/contracts/base/roles/cross-chain/multichainlayerzerotellerwithmultiassetsupport.md).

# MultiChainLayerZeroTellerWithMultiAssetSupport

[Git Source](https://github.com/Ion-Protocol/nucleus-boring-vault/blob/cc0b494b83e17b9b169a73b96050d2810b690477/src/base/Roles/CrossChain/MultiChainLayerZeroTellerWithMultiAssetSupport.sol)

**Inherits:** MultiChainTellerBase, OAppAuth

LayerZero implementation of MultiChainTeller

## Functions

### constructor

```solidity
constructor(
    address _owner,
    address _vault,
    address _accountant,
    address _endpoint
)
    MultiChainTellerBase(_owner, _vault, _accountant)
    OAppAuth(_endpoint, _owner);
```

### \_quote

function override to return the fee quote

```solidity
function _quote(uint256 shareAmount, BridgeData calldata data) internal view override returns (uint256);
```

**Parameters**

| Name          | Type         | Description             |
| ------------- | ------------ | ----------------------- |
| `shareAmount` | `uint256`    | to be sent as a message |
| `data`        | `BridgeData` | Bridge data             |

### \_lzReceive

Called when data is received from the protocol. It overrides the equivalent function in the parent contract. Protocol messages are defined as packets, comprised of the following parameters.

```solidity
function _lzReceive(
    Origin calldata _origin,
    bytes32 _guid,
    bytes calldata payload,
    address,
    bytes calldata
)
    internal
    override;
```

**Parameters**

| Name      | Type      | Description                                                       |
| --------- | --------- | ----------------------------------------------------------------- |
| `_origin` | `Origin`  | A struct containing information about where the packet came from. |
| `_guid`   | `bytes32` | A global unique identifier for tracking the packet.               |
| `payload` | `bytes`   | Encoded message.                                                  |
| `<none>`  | `address` |                                                                   |
| `<none>`  | `bytes`   |                                                                   |

### \_bridge

bridge override to allow bridge logic to be done for bridge() and depositAndBridge()

```solidity
function _bridge(uint256 shareAmount, BridgeData calldata data) internal override returns (bytes32);
```

**Parameters**

| Name          | Type         | Description              |
| ------------- | ------------ | ------------------------ |
| `shareAmount` | `uint256`    | to be moved across chain |
| `data`        | `BridgeData` | BridgeData               |

## Errors

### MultiChainLayerZeroTellerWithMultiAssetSupport\_InvalidToken

```solidity
error MultiChainLayerZeroTellerWithMultiAssetSupport_InvalidToken();
```


---

# 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.nucleusearn.io/nucleus-architecture/smart-contracts/contracts/base/roles/cross-chain/multichainlayerzerotellerwithmultiassetsupport.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.