Learn how to initiate the validator unstaking process
How voluntary exiting works
To initiate unstaking, validators are required to perform a SignedVoluntaryExit transaction, where the transaction is signed using Luganodes' validator keys.
Exiting validators must submit a signed challenge with relevant validator information. Thereafter, the createAndSignChallenge function generates the necessary signature for the exit API request, relying on validator indexes (found in the Get Delegation object response) and the withdrawal address.
We have created a script to perform the aforementioned operations with ease.
Script to create a Signed Challenge
Note:controllerAddress can be used alternatively to the withdrawalAddress in the script below
// Install ethers package using a package manager (eg. NPM, YARN)import { BaseWallet, SigningKey, hashMessage, hexlify, toUtf8Bytes,} from'ethers';constcreateAndSignChallenge=async ( validatorIndexes, privateKeyOfWithdrawalAdd, withdrawalAddress,) => {constwallet=newBaseWallet(newSigningKey(privateKeyOfWithdrawalAdd));// challenge that needs to be signedconstchallenge=JSON.stringify( { intentToExit:'I am signing this message and requesting that Luganodes exit the following validators from the network', validatorIndexes,// REQUIRED: list of validator indexes date:Date.now().toString(),// optional, timestamp this was signed address: withdrawalAddress,// REQUIRED: the signing address },null,2, );constsign=wallet.signMessageSync(hashMessage(challenge));console.log('signature: ', sign);// packedChallengeconstpackedChallenge=hexlify(toUtf8Bytes('\u0019Ethereum Signed Message:\n'+challenge.length.toString() + challenge, ), );console.log('packed_challenge', packedChallenge);};awaitcreateAndSignChallenge( validatorIndexes,//[0, 2] privateKeyOfWithdrawalAdd, withdrawalAddress, );
Request Luganodes to submit exits
POST/api/exit
Request Luganodes to exit a set of validators for a given withdrawal address. The list of validators comes from a challenge that must be signed with the withdrawal address. See the above code snippet for constructing the body for this method.
NOTE: If the challenge and signature check out, this submits the voluntary exits and will initiate the process for exiting validators. This method does not return the voluntary exits.
Headers
Query Parameters
Request Body
{"message":"exit request is under processing for these validators","validators": [ {"pubKey":"0xa8b4286511612eccb9f5834f278300fd389d5490d2c53c7674826959a1e2113e8dad87cdc357da16f9461473d82bff73","validatorIndex":1123,"provisionId":"a62c7c43-faf7-4fd8-908e-1791c6d8c257" } ]}
{"success":false,"status":400,"message":"validators are already in one of the exit states"}
// Example request body{ "signature":"0xba56185cea6b6f1bd9fc7bda51656a2136e19958d79718ff13c99cec82d36a9f5280784717a0579c5a7294a3778e7d0a00039b5a51d4e85cae25ebc14130dd691c",
"challenge":"0x19457468657265756d205369676e6564204d6573736167653a0a3234347b0a202022696e74656e74546f45786974223a20224920616d207369676e696e672074686973206d65737361676520616e642072657175657374696e672074686174205374616b656420657869742074686520666f6c6c6f77696e672076616c696461746f72732066726f6d20746865206e6574776f726b222c0a20202276616c696461746f72496e6465786573223a205b0a20202020300a20205d2c0a20202264617465223a202231363838373137333039383136222c0a20202261646472657373223a2022307861303863364339653364304532384530453945663137634536373839396538453036353031644432220a7d"
}
Generate Exit Message
POST/api/exit/message
Request Luganodes to generate an exit message for a set of validators for a given withdrawal address. This message can be broadcasted over the network through an RPC call. The list of validators comes from a challenge that must be signed with the withdrawal address.
NOTE: This method requires the exit message to be broadcasted through an RPC call. If RPC response is "null", then the exit message has been successfully broadcasted.