Verify signature
Authorizations
ApiKeyAuthApiKeyAuthapi-key string
NOWNodes API key passed in the api-key header.
Verifies a user signature.
gRPC method: sui.rpc.v2.SignatureVerificationService.VerifySignature (unary).
This is a gRPC method (HTTP/2, Protocol Buffers), not a REST endpoint. The request and response bodies below are shown in the proto3 JSON form that tools such as grpcurl and Postman accept and print. Pass your NOWNodes API key as the api-key gRPC metadata header. Proto files: sui/rpc/v2/signature_verification_service.proto.
Example grpcurl request:
grpcurl \
-insecure \
-H 'api-key: YOUR_API_KEY' \
-emit-defaults \
-proto './sui-apis-grpc/proto/sui/rpc/v2/signature_verification_service.proto' \
-import-path './sui-apis-grpc/proto' \
-d '{"message": {}, "signature": {}, "address": "0xADDRESS"}' \
'sui-grpc.nownodes.io' \
sui.rpc.v2.SignatureVerificationService.VerifySignatureBody
messageBcsThe message to verify against.
Today the only supported message types are PersonalMessage and
TransactionData and the Bcs.name must be set to indicate which type of
message is being verified.
signatureUserSignatureThe signature to verify.
addressstringOptional. Address to validate against the provided signature.
If provided, this address will be compared against the the address derived from the provide signature and a successful response will only be returned if they match.
jwksArray<ActiveJwk>The set of JWKs to use when verifying Zklogin signatures. If this is empty the current set of valid JWKs stored onchain will be used
Response
Successful response.
gRPC error. The status code (e.g. UNAUTHENTICATED, INVALID_ARGUMENT, NOT_FOUND) is returned in the grpc-status trailer, details in grpc-message.