openzeppelin_relayer::api::controllers::signer

Function create_signer

Source 
pub async fn create_signer<J, RR, TR, NR, NFR, SR, TCR, PR>(
    request: SignerCreateRequest,
    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

Creates a new signer.

§Arguments

  • request - The signer creation request.
  • state - The application state containing the signer repository.

§Returns

The created signer or an error if creation fails.

§Note

This endpoint only creates the signer metadata. The actual signer configuration (keys, credentials, etc.) should be provided through configuration files or other secure channels. This is a security measure to prevent sensitive data from being transmitted through API requests.