Api Endpoints

Encode a predeposit transaction for the PredepositGuarantee contract

post
https://api.northstake.dk/v1/lidov3/staking-vaults//predeposit

Generates the encoded transaction to submit validator pre-deposits via the
Lido PredepositGuarantee contract. BLS12-381 Y-coordinates for pubkeys and
signatures are computed server-side from the provided deposit data.

Deposit data is optional: if the contract's node operator supports generating
deposit data for a 1 ETH deposit (currently northstake and myrmidon), the
deposit data for a single 1 ETH predeposit is generated automatically when
deposits is omitted. Otherwise deposits must be provided, and each entry
must contain pubkey, signature and depositDataRoot.

Path Params
string
required

The unique identifier of the Lido staking contracts

Body Params

Request to encode a predeposit transaction for the PredepositGuarantee contract.
Provide either the full deposits array, or omit it entirely to have the 1 ETH
deposit data generated server-side (only supported for node operators that support
generating it for a 1 ETH deposit — currently northstake and myrmidon).

deposits
array of objects
length ≥ 1

Array of validator deposit data. Optional — when omitted, deposit data for a
single 1 ETH predeposit is generated server-side for supported node operators.

deposits
string
required
^0x[a-fA-F0-9]{96}$

Validator BLS public key (48 bytes hex).

string
required
^0x[a-fA-F0-9]{192}$

BLS signature (96 bytes hex).

string
required
^0x[a-fA-F0-9]{64}$

Deposit data Merkle root (32 bytes hex).

string
^0x[a-fA-F0-9]{40}$

Optional Ethereum address to simulate the transaction from. If provided, the transaction will be simulated and any revert errors will be returned.

Responses

Updated 3 months ago

Did this page help you?
Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 3 months ago

Did this page help you?