Vyges · Security & Licensing

VySeal™

Cryptographic signing, encryption, and licensing for silicon IP — protect, prove, and deliver designs across vendor tools, without locking them inside one EDA walled garden.

Early access · closed-source binaries (request access below)

What it does

For: IP publishers, silicon vendors, and platform teams that distribute designs to customers or across EDA toolchains.

vyseal is the security and licensing layer of the Vyges ecosystem — a CLI (and library) that signs, verifies, encrypts, and licenses silicon IP. It gives a design a tamper-evident identity (Ed25519 signature over a SHA-256 Merkle tree) and standards-based encryption (IEEE P1735) that the major EDA tools read directly — so IP stays portable and provable instead of trapped behind a single vendor's proprietary delivery format. VySeal complements — not replaces — EDA tool encryption, license servers, and foundry NDAs, by making IP packages independently verifiable and portable. It operates at the artifact and package layer; it does not inspect, modify, or interpret the functional behavior of the IP itself.

IP + keys  ──►  vyseal  ──►  signed (+ optionally P1735-encrypted) package + vyseal-manifest.json

Four cryptographic operations on one sealed manifest

Signing & integrity

Ed25519 signatures over a SHA-256 Merkle tree produce a vyseal-manifest.json with per-file hashes — any later tampering is detectable down to the single file.

vyseal sign · vyseal verify

IEEE P1735 encryption

Standards-compliant RTL/gate-level encryption with per-recipient key wrapping compatible with the major EDA toolchains — without re-authoring the IP per vendor — plus a native AES-256-GCM mode for Vyges-to-Vyges delivery.

vyseal encrypt --to synopsys,cadence,siemens

Keys, trust & license binding

An Ed25519 keystore you control — generate, list, back up, and restore — with trust-on-first-use or a pinned public key to authenticate a publisher. The IP's license and metadata are sealed into the manifest, so they travel cryptographically bound to the package. VySeal adds no runtime call-home checks or tool-dependent enforcement.

vyseal keygen · vyseal keys

The workflow

A publisher seals an IP once; any consumer can verify it, and encrypted deliveries open only in the tools they were wrapped for. Consumers verify sealed IP independently — no shared trust anchor with Vyges or an EDA vendor is required. Early-access partners get the vyseal binary.

$ vyseal keygen   # one-time: Ed25519 key pair in ~/.vyseal/keys/
$ vyseal sign ./my-ip/   # hash + Merkle tree + sign → vyseal-manifest.json
$ vyseal encrypt ./my-ip/ --to synopsys,cadence,siemens   # P1735 per recipient
$ vyseal verify ./my-ip/   # signature + Merkle + per-file hashes
$ vyseal keys list   # manage the ~/.vyseal keystore (list / backup / restore)

Early Access

VySeal ships as a closed-source binary to early-access partners. Tell us about your IP and delivery needs — requests are private and tracked individually, not posted to a public forum.

Ideal for teams distributing RTL, netlists, or IP bundles across multiple customers, vendors, or toolchains.

Prefer to talk first? Contact us →