Skip to main content
POST
/
95e61622bf6a8af293978377718e3b77
/
wallet
/
createshieldedcontractparameterswithoutask
wallet/createshieldedcontractparameterswithoutask
curl --request POST \
  --url https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/createshieldedcontractparameterswithoutask \
  --header 'Content-Type: application/json' \
  --data '{
  "ovk": "0x09b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2",
  "from_address": "ztron1sender123456789abcdef...",
  "to_address": "ztron1recipient123456789abcdef...",
  "amount": "1000000",
  "transparent_from_address": "<string>",
  "transparent_to_address": "<string>"
}'
{
  "receive_description": {},
  "spend_description": {},
  "binding_signature": "<string>"
}
TRON API method that creates parameters for a shielded TRC20 contract transaction without requiring the authentication secret key (ask). This simplified version is used when the ask is not available or needed for the specific transaction type.
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.

Parameters

  • ovk — the outgoing viewing key for transaction monitoring
  • from_address — the sender’s shielded address
  • to_address — the recipient’s shielded address
  • amount — the amount to transfer
  • transparent_from_address — optional transparent sender address
  • transparent_to_address — optional transparent recipient address

Response

  • receive_description — the receive description for the shielded transaction
  • spend_description — the spend description for the shielded transaction
  • binding_signature — the binding signature that ties the transaction together

Use case

The wallet/createshieldedcontractparameterswithoutask method is used for:
  • Creating shielded transaction parameters without access to authentication secret keys
  • Generating transaction data for view-only or monitoring applications
  • Supporting simplified wallet implementations that don’t store sensitive key material
  • Enabling third-party services to prepare shielded transactions with limited key access

Body

application/json
ovk
string
required

Outgoing viewing key

Example:

"0x09b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2"

from_address
string
required

Sender's shielded address

Example:

"ztron1sender123456789abcdef..."

to_address
string
required

Recipient's shielded address

Example:

"ztron1recipient123456789abcdef..."

amount
string
required

Amount to transfer

Example:

"1000000"

transparent_from_address
string

Optional transparent sender address

transparent_to_address
string

Optional transparent recipient address

Response

200 - application/json

Successfully created shielded contract parameters

receive_description
object

Receive description for shielded transaction

spend_description
object

Spend description for shielded transaction

binding_signature
string

Binding signature for transaction

I