Create a node lock for confidential compute
This endpoint attempts to find a suitable node and retrieve its public key for encryption through a two-step process:
- First, it tries to select an existing node with a public key directly.
- If no node is immediately available, it falls back to finding the cheapest compatible node and acquiring a new stack entry for it.
This endpoint is specifically designed for confidential compute scenarios where requests need to be encrypted before being processed by nodes.
Errors
INTERNAL_SERVER_ERROR- Communication errors or missing node public keysSERVICE_UNAVAILABLE- No nodes available for confidential compute
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
The model to lock a node for
Request body for creating a node lock
The model to lock a node for
The number of tokens to be processed for confidential compute (including input and output tokens)
x >= 0An optional timeout period for the locked compute units, in seconds
x >= 0Response
Node DH public key requested successfully
The response body for selecting a node's public key for encryption from a client. The client will use the provided public key to encrypt the request and send it back to the proxy. The proxy will then route this request to the selected node.
The node small id for the selected node
x >= 0The public key for the selected node, base64 encoded
The stack small id to which an available stack entry was acquired, for the selected node
x >= 0Transaction digest for the transaction that acquires the stack entry, if any