openzeppelin_relayer::api::controllers::relayer

Function sign_data

Source 
pub async fn sign_data<J, RR, TR, NR, NFR, SR, TCR, PR>(
    relayer_id: String,
    request: SignDataRequest,
    state: ThinDataAppState<J, RR, TR, NR, NFR, SR, TCR, PR>,
) -> Result<HttpResponse, ApiError>
where
    J: JobProducerTrait + Send + Sync + 'static,
    RR: RelayerRepository + Repository<RelayerRepoModel, String> + Send + Sync + 'static,
    TR: TransactionRepository + Repository<TransactionRepoModel, String> + Send + Sync + 'static,
    NR: NetworkRepository + Repository<NetworkRepoModel, String> + Send + Sync + 'static,
    NFR: Repository<NotificationRepoModel, String> + Send + Sync + 'static,
    SR: Repository<SignerRepoModel, String> + Send + Sync + 'static,
    TCR: TransactionCounterTrait + Send + Sync + 'static,
    PR: PluginRepositoryTrait + Send + Sync + 'static,
Expand description

Signs data using a specific relayer.

§Arguments

  • relayer_id - The ID of the relayer.
  • request - The sign data request.
  • state - The application state containing the relayer repository.

§Returns

The signed data response.