Build calldata to open a cross-chain front lock
Returns the calldata to open a front lock, the source-chain leg of a cross-chain fronting flow. It must be sent by the owner (the on-chain call requires msg.sender == owner), either directly or as a UserOp from the owner's smart account under a scoped session key.
Authorization
ApiKeyAuth In: header
Path Parameters
Numeric ID of the chain to query or act on.
The vault's underlying asset, as a token contract address (0x-prefixed).
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X POST "https://example.com/api/vaults/string/string/prepare-request-front-lock" \ -H "Content-Type: application/json" \ -d '{ "strategyId": "string", "amount": "string", "owner": "string", "frontId": "string" }'{ "vault": "string", "calls": [ { "to": "string", "data": "string", "value": "string", "description": "string" } ], "sender": "string", "note": "string"}Build calldata to redeem a strategy's counter-asset leg
Returns the calldata to redeem the counter-asset portion of a cross-asset strategy position (here the asset is the counter-asset vault, not the one originally locked).
Submit a cross-chain front request (LP-signed demand)
Records an LP's EIP-712-signed FrontRequest bound to the frontId they will lock. The signature is the authorization, so this records demand only and moves no funds.