Service definition
Messages
ParseRequest
The main request for parsing transactions.| Field | Type | Description |
|---|---|---|
unsigned_payload | string | Raw unsigned transaction bytes, base64 or hex encoded |
chain | Chain enum | The blockchain network (CHAIN_ETHEREUM, CHAIN_SOLANA, etc.) |
chain_metadata | ChainMetadata | Optional metadata like ABI or IDL |
Chain enum
Supported blockchain networks:ChainMetadata
Chain-specific metadata for enhanced parsing:ParseResponse
The parsed transaction response:Signature
Cryptographic signature for attestation:Response structure
Thesignable_payload field contains a JSON string with the following structure:
Usage examples
Basic transaction parsing
With contract ABI
Solana with Anchor IDL
Response format
Successful response
Error response
Errors follow the standard gRPC status codes:| Code | Name | Description |
|---|---|---|
3 | INVALID_ARGUMENT | Invalid transaction or chain |
5 | NOT_FOUND | Chain not supported |
13 | INTERNAL | Parser error |
14 | UNAVAILABLE | Service unavailable |
Health check API
The service also implements the standard gRPC health check:Client libraries
Go
Python
JavaScript/TypeScript
Rate limits
The parser service enforces the following limits:- Request size: Max 1MB per transaction
- Timeout: 30 seconds per request
- Concurrent requests: 100 per client