Unconfigured Name

Description

This error occurs when a contract attempts to access data that is missing or undefined in the destination contract. Typically, this happens when the destination contract is either not deployed on the target chain or does not implement the expected entry function.

In the LiquidsFi Explorer, the error may appear as follows:

unconfigured name (value="CCXBMT64IVE2ZV7E2NOSZ7MKK5YJAWRPQZKNBR6EAEUZZ5I3XOXTWAWJ", code=UNCONFIGURED_NAME, version=6.15.0)

Example

In this particular transaction:

• msg_id: 0x7ef78433118fa9421f15f8b481d64e473282c448d17d84eb6f5c1abf2b9c2f6a

• Origin Chain: 12000000 (Soroban)

• Destination Chain: 35000000 (Ethereum Sepolia)

• Destination Contract: CCXBMT64IVE2ZV7E2NOSZ7MKK5YJAWRPQZKNBR6EAEUZZ5I3XOXTWAWJ

This error occurs because the destination contract either:

1. Is not deployed on the Ethereum Sepolia, or

2. Does not implement the LiquidsFi Oracle entry function expected by the Oracle contract.

How to Fix

1. Verify Contract Deployment: Ensure the destination contract is deployed on the correct destination chain.

2. Implement the Oracle Entry Function: Confirm that the contract includes the required onOracleData function:

function onOracleData(bytes calldata data) external onlyOracle {
    // decode data
    // custom code to handle the oracle data
}

Notes

The onOracleData function serves as the entry point for LiquidsFi oracle data. Missing or incorrectly implemented functions will cause transactions to fail with the “missing revert data” error.