Labyrinth
WhitepaperResearchGet Private Access
  • 🔭Labyrinth Overview
    • Introduction
    • Why Labyrinth?
    • Who can use Labyrinth?
    • Reward and Fee in Labyrinth
    • Compliance
  • ⭐Use Labyrinth web App
    • How to use the Labyrinth app?
  • 📦Labyrinth SDK
    • ❓What is Labyrinth SDK?
    • ⚒️Quickstart
      • Setup Environment
      • Initialization
      • Private Transactions
      • Balance And Transaction History
      • Protocol Integration
    • 1️⃣Getting Started
    • 🔐Shielded Account
    • 📈Transaction
    • ▶️Initializing SDK
    • 💰Balances And History
    • 📤Sending Transaction
    • 🔌Integrating with DeFi Protocols
    • Labyrinth fee structure
  • Compliance Solution
    • Overview of Compliance
    • How Compliance Works
  • 💻CLI
    • ▶️Running SeDe CLI
  • Technical Implementation
    • Cryptographic Primitives
    • Shielded Account
    • Shielded Address
    • Account Abstraction
    • 🔵Core Architecture
      • 💵Note
      • 🌲Merkle Tree
      • 🔀JoinSplits
      • 🛡️Shielded Transaction
    • 🔄Protocol Interoperability
  • Resource and support
    • Roadmap
    • FAQs
    • Whitepaper
    • Selective De-Anonymization Compliance Paper
  • Contact and socials
    • Labyrinth Website
    • Twitter
    • Discord
    • Contact Us
Powered by GitBook
On this page
  1. Technical Implementation

Account Abstraction

Shielded Account as Smart Contract Account

PreviousShielded AddressNextCore Architecture

Last updated 10 months ago

Your shielded account is agnostic to any EOA from which the transaction originated. This is because transactions are not verified by a signature by EOA. Rather, it is verified by a ZK proof. As long as proof is valid, the transaction is let through by the contract. The transactions sent via your Shielded Account can be relayed on-chain using a bundler and are (Account Abstraction) compatible. This allows it to reap UX benefits like user not having to sign every transaction, sponsoring gas for user, etc, but more importantly enhancing privacy.

Privacy is enhanced as transactions via Labyrinth default to AA avoiding paying gas fees with their EOA which results in appearance of their address on-chain, hampering privacy.

This setup also enables shielded account to pay the transaction fee in any of the supported ERC-20 tokens and integrating protocols into Labyrinth, may sponsor gas fees for their users who use Shielded Account to anonymously interact with their protocol.

EIP-4337