Download — LimenGate

LimenGate for Linux

x86_64-unknown-linux-gnu

Coming Soon — Pre-release

SHA3-512

Hash will be published here upon first release

macOS

aarch64 / x86_64

Planned

Windows

x86_64-pc-windows-msvc

Planned

Build from Source

        # Prerequisites

        sudo apt-get install build-essential cmake libssl-dev \

          libasound2-dev libespeak-ng-dev libfontconfig1-dev \

          libfreetype6-dev libglib2.0-dev libx11-dev libxcb-render0-dev \

          libxcb-shape0-dev libxcb-xfixes0-dev

        # Rust toolchain (1.92.0 stable)

        rustup default 1.92.0

        # Clone & build

        git clone https://limengate.quest/repo/limen-gate.git

        cd limen-gate

        cargo build --release --bin limengate

        # Run (Servo needs 32MB stack for CSS-heavy pages)

        RUST_MIN_STACK=33554432 cargo run --release --bin limengate

Verify Your Build

LimenGate includes SHA3-512 self-hashing. After building, you can verify the binary matches the published hash.

        # Option 1: Use LimenGate's built-in verification

        # Go to Help > About in the browser to see the self-hash

        # Option 2: External verification with sha3sum

        pip install pysha3  # or use any SHA3-512 tool

        sha3sum -a 512 target/release/limengate

        # Option 3: OpenSSL (3.0+)

        openssl dgst -sha3-512 target/release/limengate

        # Compare with the hash published on /provenance

Why SHA3-512?

SHA-2 is still considered secure, but LimenGate uses SHA3-512 (Keccak) because it's a completely independent design from SHA-2. If a weakness is ever found in SHA-2's Merkle-Damgård construction, SHA-3's sponge construction remains unaffected. Defense in depth extends to our hash functions.

Reproducible Builds

A shell.nix environment is included for Nix users. This pins all build dependencies to exact versions, ensuring you can reproduce the exact same binary from the same source commit.

          nix-shell

          cargo build --release --bin limengate