LogoLogo
  • Venn Network
    • Introduction to Venn
    • Getting Started
      • Protocols & Developers
        • Installation
        • Testnet Guide
        • Venn CLI
        • Venn DApp SDK
        • How It Works
        • Roles
      • Node Operators
        • Installation
        • Configuration
        • Testnet Guide
      • Security Teams
        • Build Custom Detector
        • API Reference
        • Security Sandbox
      • Venn Safe Guard
        • Bypass Mechanism
      • Venn Wallet RPC
        • Custom RPC in MetaMask
    • Explorer
    • Playground
    • Use Cases
    • Roadmap
    • Consensus Model
    • Litepaper
    • FAQ
    • Community
    • Audit Reports
Powered by GitBook
On this page
  • Introduction
  • Why Choose Venn Safe Guard?
  • What Venn Safe Guard Protects Against?
  • How it Works
  • Step 1: Build Your Transaction
  • Step 2: Decentralized Security Validation
  • Step 3: Submission to Safe Queue
  • Step 4: On-Chain Guard Validation
  • Transaction Validation API
  • Code Example
  • Venn Guard Smart Contract

Was this helpful?

  1. Venn Network
  2. Getting Started

Venn Safe Guard

Introduction

Venn Safe Guard is a decentralized security-validation layer for Safe (Gnosis Safe) multisig accounts. By integrating seamlessly into your Safe transaction workflow, Venn ensures that every transaction undergoes rigorous decentralized security validation, thereby reducing the risk associated with malicious or unauthorized multisig operations.


Why Choose Venn Safe Guard?

  • Zero UI Trust: Independent validation - immune to compromised front-ends.

  • Decentralized and vendor-neutral: no single points of failure or risky dependencies on third parties.

  • End-to-End Validation: Continuous validation before, during, and after execution.


What Venn Safe Guard Protects Against?

  • Compromised Signers

  • Compromised Interfaces (UI Hijack)

  • Privilege Escalation

  • Silent Backdoor Installation

  • Malicious Admin Batching

  • Fallback handlers Hijacking


How it Works

Step 1: Build Your Transaction

  • Safe owners or admins build transactions using two options:

    • Venn API (for local/programmatic builds)

    • Venn Transaction Builder UI.

Transaction format matches Safe's native structure and supports multicalls/batches, which mirrors Safe’s native transaction-building and transaction Service flow.

Step 2: Decentralized Security Validation

  • Independent Tier-1 security operators evaluate transactions against your security policy.

You can consume Venn Security Validation either using the Venn Safe Guard API (for programmatic or local use), or through the dedicated Venn UI, which handles the validation process automatically behind the scenes.

Step 3: Submission to Safe Queue

  • Approved transactions (including Venn's validation signature) are submitted to the Safe multisig transaction queue.

  • Safe signers proceed to approve transactions normally, just like regular Safe transactions.

Step 4: On-Chain Guard Validation

  • When signers trigger on-chain execution, the Venn Safe Guard contract performs:

    • Pre-Execution Check: The Guard extracts and stores the transaction’s original bytecode for comparison.

    • Execution-Time Validation: On-chain verification of Venn’s aggregated signature and operator consensus, validating transaction authenticity and integrity.

    • Post-Execution Check: Confirms executed transaction bytecode matches pre-approved bytecode.


Transaction Validation API

The Venn Guard Transaction Validation API enables automatic transaction validation through Venn’s decentralized security network. It accepts standard user transactions and returns a JSON file that is ready to upload to any Safe UI.

Full integration with Safe's transaction service API - coming soon

Code Example

import axios from "axios";

// Your Safe Address
const SAFE_ADDRESS = "0x..." 

// 1st transaction in the batch
const userTransaction1 = {
    to: "0x...",
    value: "0",
    data: "0x...",
    safeAddress: SAFE_ADDRESS,
};

// 2nd transaction in the batch
const userTransaction2 = {
    to: "0x...",
    value: "0",
    data: "0x...",
    safeAddress: SAFE_ADDRESS,
};

// Validating and signing the transactions with Venn
const response = await axios.post(
    "https://validation.venn.build/api/v1/batch/sign",
    {
       transactions [userTransaction1, userTransaction2],
       safeAddress: "0x..."
    }
);

console.log(response.data):
// Transaction Batch JSON
// {
//    ...
//    transactions: [
//       <Venn's Approving Signature Tx>,
//       <User Tx 1>,
//       <User Tx 2>,
//    ]
// }


Venn Guard Smart Contract

PreviousBuild Custom DetectorNextBypass Mechanism

Last updated 28 days ago

Was this helpful?

Venn Safe Guard is designed as a modular Safe Guard, seamlessly integrated into your existing Safe multisig account. Safe Guards are specialized smart contracts officially supported by Safe, created to add customized validation logic for the lifecycle of Safe transactions (see ).

The built transaction is automatically sent to the .

Venn’s aggregates operators' votes to decide if the transaction is secure and allowed to proceed or malicious and blocked from execution.

The Venn Guard smart contract is the core on-chain component of Venn’s Safe integration. Implemented as a Safe Guard contract, it acts as a firewall enforcing transaction validations directly at the smart contract execution layer. The Guard interacts with Venn's decentralized network, ensuring only transactions explicitly approved by can be successfully executed.

Safe Guard documentation
operator consensus
Venn Decentralized Validation Network
consensus
Venn Safe Guard