Liminal Network · 无介
中文

2026-08-15 · ring signature / stealth address / RingCT / Dandelion++ / zero-knowledge

Ring signatures, stealth addresses, RingCT, Dandelion++ — Liminal’s four hides

A plain-language map of Liminal Network’s public cryptography stack: who sent, who received, how much, and from which IP.

Liminal Network (无介) treats full-path privacy as the default, not a filter you remember to enable. The stack in its public docs answers four questions: who sent, who received, how much, and which machine spoke first.

No formulas below—only the jobs.

Who sent: ring signatures

A ring signature mixes the real spender’s key with decoy keys. Verifiers learn that someone in the ring authorized a valid transaction. They do not learn which member.

On an explorer, the sender stops being “this address” and becomes “one of these.” Larger rings and better decoys raise the cost of a guess. That is why pool size keeps showing up in the narrative: mix depth is the anonymity set.

Who received: stealth addresses

Paying the same public address over and over draws a hub, even if senders are hidden.

A stealth address issues a one-time destination per payment. It should not invert to the recipient’s long-term key. The sender still knows the money arrived; outsiders see a scatter of fresh addresses.

How much: RingCT and zero-knowledge proofs

Cleartext amounts leak life: round salaries, repeating invoices, change patterns.

Ring confidential transactions hide the value. Zero-knowledge proofs let the network check that no coins were invented and no output was spent twice, without learning the number. The chain accepts the transfer; bystanders do not read the size.

Which machine: Dandelion++

Hide every ledger field and you can still leak an IP if the first broadcast hop is obvious.

Dandelion++ uses a stem-then-fluff pattern: a quieter path first, then wider diffusion. It is not a substitute for a VPN or basic device hygiene. It does close the “we only thought about the chain” hole.

Why all four

Hide only the sender, and the receiver still paints a target.

Hide only the receiver, and amounts still build a timeline.

Mix on-chain and ignore the network, and the gateway talks.

Liminal’s closed loop is sender, receiver, amount, IP. That is the inverse of a public chain, where everything is public unless the user improvises.

Where this shows up in the product

You rarely click “build a ring.” The same machinery sits under Portal swaps, claim codes, Catbox, and pool mixing. Users should assume the loop is on once they enter the gateway. Liquidity providers enlarge the set those constructions draw from.

Start with the Portal guide. Same cryptography family, different product: Liminal vs Monero. Site: liminalnetwork.xyz.

This article summarizes public Liminal Network (无介) materials. It is not investment advice and does not guarantee returns. Closed modules such as node subscriptions are not current entry points. Live product rules always win over this explainer.