Transaction Visibility And Knowledge

This page explains what LibertySwap knows and does not know about user transactions when using LibertySwap Railgun Routes.

1. System Overview

LibertySwap Railgun Routes allow users to route swaps through Railgun shielded pools and cross chain paths, including Ethereum, PulseChain, and other supported networks.

LibertySwap acts as:

• A routing interface

• A transaction coordinator

• A notification and status relay

LibertySwap is not a custodian, wallet provider, or identity broker.

2. What LibertySwap CAN See

LibertySwap has limited visibility required to operate the routing service reliably.

2.1 Transaction Status Metadata

LibertySwap can observe:

• Swap initiation events

• Swap completion or failure states

• Input and output transaction hashes that show LibertySwap contract interacted with Railgun Relayer

• Network paths used, for example Ethereum to Railgun to PulseChain

• Fees charged by the protocol

This data is used only to:

• Display transaction progress

• Confirm delivery

• Provide support for failed or delayed swaps

2.2 Non Identifying Routing Information

LibertySwap may temporarily process:

• Asset type involved, for example ETH, WETH, USDC

• Approximate amounts for routing calculation

• Network selection and bridge path

This information is not linked to a known identity.

3. What LibertySwap CANNOT See

3.1 User Identity

LibertySwap does not know:

• Who the user is

• The real world identity of the sender

• Any KYC, name, email, or account ownership

Transactions routed through Railgun appear as unknown senders by design.

3.2 Wallet Ownership

LibertySwap does not know:

• Which wallet owns the funds

• Which wallet controls the shielded balance

• Whether multiple transactions belong to the same user

Railgun cryptography prevents wallet level attribution.

3.3 Shielded Transaction Internals

LibertySwap cannot access:

• Railgun shielded balance history

• Private notes or commitments

• Internal transfers within Railgun

• Sender recipient relationships inside the shielded pool

These are cryptographically hidden and never exposed to LibertySwap.

4. What LibertySwap NEVER Stores

LibertySwap does not store:

• User addresses mapped to identities

• Transaction histories tied to users

• Behavioral profiles

• IP to wallet correlations

• Any long term personal data

Any temporary operational data is ephemeral and used only for swap execution and monitoring.

5. On Chain Transparency vs Shielded Privacy

5.1 Public Chains

On public chains, observers can see:

• Contract interactions

• Aggregate volume

• Network level activity

This is inherent to public blockchains.

5.2 Railgun Shielded Layer

Within Railgun:

• Sender and recipient are cryptographically hidden

• Transaction amounts are shielded

• Historical linkability is removed

LibertySwap cannot override or bypass this privacy layer.

6. Compliance and Responsibility Boundary

LibertySwap:

• Does not custody funds

• Does not initiate transactions on behalf of users

• Does not control Railgun cryptography

• Does not deanonymize users

Users are fully responsible for:

• Their wallet security

• Their jurisdictional compliance

• Their transaction intent

LibertySwap provides software and routing infrastructure only.

7. Summary Table

Category	LibertySwap Knows	LibertySwap Does Not Know
Transaction Status	Yes	—
Network Path	Yes	—
Asset Type	Yes	—
User Identity	—	Yes
Wallet Ownership	—	Yes
Shielded History	—	Yes
Sender Recipient Links	—	Yes

8. Final Statement

LibertySwap is designed to minimize data exposure by default. When users utilize Railgun Routes, LibertySwap only processes the minimum technical information required to complete swaps, while Railgun ensures cryptographic privacy at the transaction level.

LibertySwap cannot identify users, trace shielded funds, or reconstruct transaction histories beyond public chain confirmations.

Privacy is not a promise. It is an architectural constraint.