Add TSS endpoint to get TDX quote #1173
Conversation
| Ok(nonce) | ||
| attestee: &sr25519::Pair, | ||
| ) -> Result<[u8; 32], ClientError> { | ||
| Ok(user::request_attestation(api, rpc, attestee).await?) |
There was a problem hiding this comment.
This function needed to move out of this module because it is behind a feature flag which entropy-tss does not enable. I have left this wrapper so that there is a version of it with the same error type as the other full-client functions.
| let nonce = request_attestation(&api, &rpc, signer.signer()).await?; | ||
|
|
||
| // We also need the current block number as input | ||
| let block_number = |
There was a problem hiding this comment.
This is the problem - we cannot know at what block number the node operator is going to submit this quote
| /// body. | ||
| /// This is used by node operators to get a quote for use in the `validate`, `change_endpoint` | ||
| /// and `change_tss_accounts` extrinsics. | ||
| pub async fn get_attest( |
There was a problem hiding this comment.
| pub async fn get_attest( | |
| pub async fn request_attestation( |
To match the extrinsic?
| let api = get_api(&app_state.configuration.endpoint).await?; | ||
| let rpc = get_rpc(&app_state.configuration.endpoint).await?; | ||
|
|
||
| // Request attestation to get nonce |
There was a problem hiding this comment.
| // Request attestation to get nonce |
| let rpc = get_rpc(&app_state.configuration.endpoint).await?; | ||
|
|
||
| // Request attestation to get nonce | ||
| let nonce = request_attestation(&api, &rpc, signer.signer()).await?; |
There was a problem hiding this comment.
As part of the AttestationIssued event we return not only the nonce but also the block_number at which that request was processed.
I thought it would be useful for that second step, but thinking about it a bit more it might not be.
Part of #982 - see #982 (comment)
This adds an endpoint to the TSS server which allows the operator to get a quote for use in the
validate,change_endpoint, andchange_tss_accountsextrinsics.In doing this i noticed a possible problem with our design. I have made an issue: #1174