Railgun Shield logo

Catalog action EVM Onchain wallet Gas send

Shield ERC20 tokens from public wallet to Railgun private balance. Requires turnkey (for signing) and railgun (for mnemonic) connectors.

This action can require a wallet connector, gas, token movement, or an external side effect. Test with simulation or a controlled amount before using it in a live workflow.

At a Glance

FieldValue
Action IDrailgun-shield
CategoryEVM Onchain
Connectorwallet
Requires gasYes
Funds movementsend
Tagsblockchain, privacy, railgun, shield, zk

Payload Schema

FieldTypeRequiredDescription
chainIdnumberYesChain ID. Supported: Ethereum (1), BNB Chain (56), Polygon (137), Arbitrum (42161)
tokenAddressstringYesERC20 token contract address to shield
amountstringYesAmount to shield in smallest unit (wei) as string
railgunAddressstringYesRailgun address to receive shielded tokens (0zk...)

Result Schema

FieldTypeRequiredDescription
statusstringYes-
transactionHashstringNoTransaction hash of the shield operation
blockNumbernumberNoBlock number where the transaction was confirmed
gasUsedstringNoGas used for the shield transaction

Examples

json
{ "type": "railgun-shield", "payload": { "chainId": 1, "tokenAddress": "0x0000000000000000000000000000000000000000", "amount": "1000000", "railgunAddress": "0zk1q8p9example..." }, "children": [], "connector": { "type": "wallet", "id": "conn_wallet" }}

Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.

Ask a question... ⌘I