Routing Options

Different Routes. Different Capabilities.

Choose the transaction workflow that fits your needs.

Understand the route. Review the details. Make an informed decision.

Understanding Transaction Routing

What Is Digital Asset Routing?

Transaction routing is the process of determining how supported digital assets move between an origin and a destination.

Digital asset transactions can involve different networks, protocols, and execution stages. The route you choose affects how a transaction is processed, which technologies are involved, and the costs and risks associated with execution.

WalletShielder provides access to supported routing configurations, from standard asset transfers and swaps to workflows incorporating Zero-Knowledge (ZK) privacy technology.

Each option is designed for a different transaction experience.

Not every transaction requires every stage. The available route depends on factors such as network compatibility, liquidity, supported assets, and current infrastructure conditions.

Routing determines how a transaction is executed. ZK privacy determines how selected information can be cryptographically protected within supported operations.

Depending on the selected assets, networks, and available infrastructure, a route may involve:

Direct blockchain transfers.

Digital asset swaps.

Cross-chain transfers.

Interactions with third-party liquidity and routing providers.

Multiple transaction execution stages.

Supported ZK privacy operations.

Explore Your Routing Options

Three configurations. One interface.

Standard01

Standard Routing

Straightforward digital asset execution.

Public routingOriginRoutingDestination

Standard Routing provides access to supported asset swaps, transfers, and cross-chain transaction workflows without incorporating a dedicated ZK privacy stage.

It is designed for users who want to move supported digital assets through available transaction infrastructure.

Key characteristics

Supported digital asset swaps and transfers.
Cross-chain routing where available.
Execution through applicable blockchain and third-party infrastructure.
Standard public blockchain visibility.
No dedicated ZK privacy operation.

Important: Standard Routing does not provide the cryptographic confidentiality associated with ZK privacy protocols.

Best suited for: Users who prioritize straightforward transaction execution without requiring an additional ZK-enabled workflow.

Launch with Standard

Enhanced02

Enhanced Routing

Transaction routing with integrated ZK privacy functionality.

ZK-enabled routeOriginZK stageDestination

Enhanced Routing combines supported digital asset routing with a ZK-enabled operation.

Depending on the selected transaction, the workflow may include public routing stages before and after the privacy-enabled operation.

Within the supported ZK system, cryptographic proofs can validate defined conditions while limiting disclosure of selected underlying information.

Key characteristics

Supported swaps and cross-chain routing.
Integration with ZK privacy functionality.
Cryptographic verification of supported operations.
Multiple execution stages, where required.
Different visibility characteristics across public and ZK-enabled stages.

Important: Enhanced Routing does not guarantee end-to-end confidentiality. Public transaction stages and associated metadata may remain visible.

Best suited for: Users seeking access to ZK privacy technology as part of a supported transaction workflow.

Launch with Enhanced

Maximum03

Maximum Routing

An extended multi-stage routing configuration.

Extended route · subject to availabilityOriginRoutingZK stageRoutingDestination

Maximum Routing is intended to provide an additional routing configuration for supported transactions.

Where implemented, it may introduce extra asset-conversion or routing stages around a ZK-enabled operation.

These additional stages may create different transaction paths, but they also introduce further execution dependencies, costs, and potential failure points.

Key characteristics

Extended multi-stage transaction routing.
Additional routing or asset-conversion operations, where supported.
Integration with supported ZK privacy functionality.
Potentially higher transaction costs.
Additional execution complexity and dependencies.

Important: Additional routing stages do not automatically provide stronger privacy or anonymity. Any privacy benefit depends on the actual transaction design and should not be assumed.

Best suited for: Users who understand multi-stage transaction execution and wish to use an available advanced routing configuration.

Availability: Confirm whether this option is implemented and available

Launch with Maximum

Compare Routing Options

Side by side.

Capability	Standard	Enhanced	Maximum
Supported asset swaps	Yes, where available	Yes, where available	Yes, where available
Cross-chain routing	Where supported	Where supported	Where supported
Dedicated ZK privacy operation	— No	Yes	Yes, if implemented
Additional routing stages	As required	As required	Extended configuration
Public blockchain visibility	Applies	Applies to public stages	Applies to public stages
Transaction complexity	Route-dependent	Typically higher	Potentially highest
Fees	Route-dependent	Additional costs may apply	Additional costs may apply
Availability	Subject to support	Subject to support	Pending confirmation

Scroll → to compare all three

Note: This comparison describes intended routing configurations. Actual features, availability, and execution characteristics depend on the supported implementation.

How a Transaction Route Is Built

From Origin to Destination

A routing workflow is determined by the selected origin asset, destination asset, blockchain networks, and available execution infrastructure.

Depending on the configuration, WalletShielder may coordinate a sequence of supported operations.

01Origin

Select Your Origin

Choose the digital asset and network from which the transaction will begin.

02Destination

Define Your Destination

Select the intended destination asset, network, and recipient address.

03Option

Choose a Routing Option

Review the available routing configurations and their relevant technical characteristics.

04Review

Review the Route

Examine the proposed transaction stages, estimated amounts, fees, and material risks.

05Authorize

Authorize the Operation

Complete the required wallet approvals or other supported authorization steps.

06Progress

Follow Transaction Progress

Monitor the available transaction status information as the operation progresses through its required stages.

A multi-stage transaction may involve separate confirmations and settlement events.

Understanding Public and ZK-Enabled Stages

Different Stages. Different Visibility.

A transaction route may combine public blockchain operations with ZK-enabled functionality.

These stages have different technical characteristics.

The presence of a ZK-enabled stage does not make every other stage confidential.

PUB

Public Routing Stages

Swaps, transfers, and other public blockchain operations may expose wallet addresses, transaction amounts, assets, timestamps, and smart contract interactions.

ZK-Enabled Stages

Supported ZK privacy operations use cryptographic proofs to verify defined conditions without publicly disclosing all underlying information.

PUB

Return to Public Blockchain Execution

Where a workflow moves assets from a ZK-enabled environment to a public destination, the resulting public transaction may expose relevant transaction details.

01WalletShielder service fees.

02Blockchain network fees.

03Swap and liquidity provider fees.

04Cross-chain routing or bridge costs.

05Protocol-related execution costs.

06Price slippage.

Fees and Execution Considerations

Understand the Cost of Your Route

Transaction costs depend on the selected routing configuration and the infrastructure involved. Potential costs may include the items shown.

Routes involving more stages may incur additional costs. Estimated amounts and fees may change due to market conditions, liquidity, and network activity.

Users should review the available quote and transaction details before authorizing execution.

Multi-Stage Execution and Transaction Risks

More Stages Mean More Dependencies.

Some routes involve several independent blockchain or protocol operations.

Each stage may have its own confirmation requirements, execution conditions, and potential failure scenarios.

Not all incomplete transactions are eligible for automatic recovery. Where available, refund and recovery procedures depend on the relevant provider and transaction circumstances.

For more information, please review our Risk Disclosure.

Users should understand that:

Successful completion of one stage does not guarantee completion of the entire route.

Blockchain transactions may be irreversible.

Third-party infrastructure may experience delays or failures.

Refund procedures differ between providers and transaction stages.

Additional routing steps can increase execution complexity.

Network conditions may affect the final amount and completion time.

Routing and Regulatory Considerations

Technology With Clear Boundaries.

WalletShielder is designed to provide access to supported digital asset transaction infrastructure, including ZK privacy functionality where available.

Routing configurations are technical transaction options. They do not constitute guarantees of anonymity, regulatory approval, or compliance with any particular legal requirement.

ZK cryptography may reduce public disclosure of selected information, but it does not remove applicable sanctions, AML, tax, reporting, or other legal obligations. Certain routes or features may be restricted based on applicable laws, supported networks, service-provider requirements, or compliance controls.

Choosing a routing option does not change your legal obligations.

Frequently asked questions

Questions, Answered.

01What is the difference between Standard and Enhanced Routing?

Standard Routing facilitates supported digital asset transactions without a dedicated ZK privacy operation.

Enhanced Routing incorporates supported ZK privacy functionality into the transaction workflow.

02Does Standard Routing provide ZK privacy?

No. Standard Routing does not include a dedicated ZK privacy stage.

03Does Enhanced Routing make my entire transaction confidential?

No. Public routing stages may remain visible, and ZK privacy does not guarantee anonymity or prevent all forms of transaction analysis.

04Is Maximum Routing more private than Enhanced Routing?

Not necessarily. Additional routing stages do not automatically improve privacy. Any claimed privacy advantage must be supported by the actual implementation and relevant technical analysis.

05Why do some routes require more transaction stages?

Different assets, networks, and protocols may require separate swaps, transfers, or other operations to complete the requested transaction.

06Will more stages increase transaction fees?

They may. Additional stages can involve extra network fees, swap costs, and other execution expenses.

07Are transactions guaranteed to complete?

No. Transactions remain subject to blockchain, smart contract, liquidity, and third-party infrastructure risks.

08What happens if a transaction fails?

The outcome depends on the stage at which the failure occurs and the applicable provider's recovery mechanisms. Some transactions may support refunds, while others may not.

09Can routing options change?

Yes. Available routes may change depending on network conditions, liquidity, technical support, provider availability, or applicable restrictions.

Choose your route

Choose Your Route With Confidence.

Different transaction goals require different technical workflows.

WalletShielder helps you explore supported routing configurations, understand the relevant technologies, and review important execution considerations before proceeding.

Your assets. Your transaction choices. Clearer technology.

Launch WalletShielder Learn About ZK Privacy

Routing options are subject to technical availability, supported assets and networks, and applicable restrictions. ZK-enabled functionality does not guarantee anonymity, complete confidentiality, or successful transaction execution. Review all transaction details, applicable fees, Terms of Use, and Risk Disclosure before proceeding.