Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
All cryptographic parameters (
ask, alpha, tx_hash) must be exactly 32 bytes (64 hexadecimal characters) provided as raw hex strings without the 0x prefix. Values that are shorter, longer, or include the 0x prefix will result in a “param length must be 32” error.Parameters
ask— the authentication secret key used for signing (32 bytes, hex without 0x prefix)alpha— the alpha parameter for randomization (32 bytes, hex without 0x prefix)tx_hash— the transaction hash being authorized (32 bytes, hex without 0x prefix)
Response
value— the generated spending authorization signature (hex string without 0x prefix)
Use case
Thewallet/createspendauthsig method is used for:
- Authorizing the spending of shielded notes in privacy transactions
 - Creating cryptographic signatures that prove spending authority without revealing identity
 - Supporting the zero-knowledge proof system in shielded transactions
 - Enabling secure authorization of shielded TRC20 transfers
 
Body
application/json
Authentication secret key for signing (32 bytes, hex without 0x prefix)
Example:
"0f63eabdfe2bbfe08012f6bb2db024e6809c16e8ed055aa41a6095424f192005"
Alpha parameter for randomization (32 bytes, hex without 0x prefix)
Example:
"d0f0768664f5c807f9e70d05993f029c71da529afaa5c037b44c63d6e13bc907"
Transaction hash being authorized (32 bytes, hex without 0x prefix)
Example:
"7fb99e66df052f430d50e80a3f197c319a4e35184ed48a433d6219e025741337"
Response
200 - application/json
Successfully created spending authorization signature
Generated spending authorization signature (hex string without 0x prefix)
Example:
"66c806bc592a7599e65833bf25c3c7005c8b21b7895dd835a84c97d7bec49d0f1493d2c73a68eeb9b9699b92cae42406f9e44ebe19acaea3d5febfe28de57109"