Skip to main content
POST
/
95e61622bf6a8af293978377718e3b77
/
wallet
/
createshieldedtransactionwithoutspendauthsig
wallet/createshieldedtransactionwithoutspendauthsig
curl --request POST \
  --url https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/createshieldedtransactionwithoutspendauthsig \
  --header 'Content-Type: application/json' \
  --data '
{
  "to_address": "ztron1a2b3c4d5e6f7g8h9j0k1l2m3n4p5q6r7s8t9u0v1w2x3y4z5a6b7c8d9e0f1g2h3j4k5l6m7n8p9",
  "to_amount": 1000000,
  "transparent_from_address": "TQn9Y2khEsLJW1ChVWFMSMeRDow5KcbLSE",
  "from_amount": 1000000,
  "shielded_spends": [
    {}
  ],
  "shielded_receives": [
    {}
  ]
}
'
{
  "raw_data_hex": "<string>",
  "raw_data": {},
  "txID": "1a2b3c4d5e6f7890abcdef1234567890abcdef1234567890abcdef1234567890"
}

Documentation Index

Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt

Use this file to discover all available pages before exploring further.

Create unsigned shielded TRX transactions. This endpoint is not exposed via RPC for security reasons—shielded transaction construction requires local key material and zero-knowledge proof generation. Build shielded transactions client-side using TRON shielded transaction libraries.
Get your 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.

​
Parameters

  • transparent_from_address — the transparent TRX address sending funds (optional)
  • from_amount — the amount to send from transparent address (in sun)
  • shielded_spends — array of shielded input specifications
  • shielded_receives — array of shielded output specifications
  • to_address — recipient shielded address
  • to_amount — amount to send to shielded address (in sun)

​
Response

  • raw_data_hex — the raw unsigned transaction data in hexadecimal format
  • raw_data — the structured raw unsigned transaction data
  • txID — the transaction ID hash (will change after signing)

​
Use case

The wallet/createshieldedtransactionwithoutspendauthsig method is used for:
  • Creating unsigned shielded transactions for offline signing workflows
  • Separating transaction creation from signing for enhanced security
  • Supporting hardware wallet integration with shielded transactions
  • Enabling multi-step transaction creation processes

​
Client-side implementation

This endpoint is not available via RPC. Build shielded transactions client-side using TRON privacy libraries (e.g., tronweb with shielded support) or Sapling-compatible implementations. Generate the raw transaction locally with your key material, then sign and broadcast separately.
Use TRON’s shielded transaction libraries to:
  1. Construct the shielded inputs (spends) and outputs (receives) using your local key material
  2. Generate the zero-knowledge proof parameters offline
  3. Build the raw transaction structure without spending authority signatures
  4. Sign the transaction in a separate step (e.g., with hardware wallet)
  5. Broadcast the signed transaction via wallet/broadcasttransaction

Body

application/json
​
to_address
string
required

Recipient shielded address

Example:

"ztron1a2b3c4d5e6f7g8h9j0k1l2m3n4p5q6r7s8t9u0v1w2x3y4z5a6b7c8d9e0f1g2h3j4k5l6m7n8p9"

​
to_amount
integer
required

Amount to send to shielded address in sun

Example:

1000000

​
transparent_from_address
string

Transparent TRX address sending funds

Example:

"TQn9Y2khEsLJW1ChVWFMSMeRDow5KcbLSE"

​
from_amount
integer

Amount to send from transparent address in sun

Example:

1000000

​
shielded_spends
object[]

Array of shielded input specifications

​
shielded_receives
object[]

Array of shielded output specifications

Response

200 - application/json

Successfully created unsigned shielded transaction

​
raw_data_hex
string

Raw unsigned transaction data in hexadecimal

​
raw_data
object

Structured raw unsigned transaction data

​
txID
string

Preliminary transaction ID (will change after signing, 64 hex characters, no 0x prefix)

Example:

"1a2b3c4d5e6f7890abcdef1234567890abcdef1234567890abcdef1234567890"

Last modified on April 29, 2026