Individuals</h3> <p>Personal financial data on a public chain is a security and privacy risk. Salary visibility, donation history, and spending patterns should not be permanently public.</p> </div> <div class="persona-card" data-persona="defi"> <div class="persona-icon">⚡</div> <h3>DeFi Traders</h3> <p>Front-running, sandwich attacks, and copy-trading are all enabled by transparent mempool. Private transactions break the information advantage of on-chain surveillance.</p> </div> <div class="persona-card" data-persona="enterprise"> <div class="persona-icon">🏢</div> <h3>Enterprises</h3> <p>Supply chain payments, vendor relationships, and treasury movements are competitively sensitive. Public blockchains expose this to competitors, suppliers, and regulators.</p> </div> <div class="persona-card" data-persona="dao"> <div class="persona-icon">🏛</div> <h3>DAOs & Protocols</h3> <p>Governance vote buying, bribe markets, and voter coercion are all downstream of transparent voting. Sealed voting removes the economic incentive to corrupt governance.</p> </div> </div> </div> </section> <!-- USE CASES --> <section class="sec bordered"> <div class="wrap"> <div class="sec-head"> <div class="eyebrow">use cases · deep dives</div> <h2>Fourteen problems privacy solves.</h2> </div> <div class="uc-list"> <div class="uc-item"> <div class="uc-num">01</div> <div class="uc-body"> <div class="uc-tag">Payroll</div> <h3>Private on-chain payroll</h3> <p>A company paying employees in SNCT today broadcasts every salary to the world — permanently indexed, queryable by anyone. With shielded transfers, the payroll contract sends funds with the sender hidden. Employees receive correct amounts; the company’s payroll data stays internal.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Every employee salary, bonus, and payment timing is permanently public</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Payroll contract shields transfers — amount and recipient confirmed on-chain, sender hidden</div> </div> </div> <div class="uc-item"> <div class="uc-num">02</div> <div class="uc-body"> <div class="uc-tag">DeFi</div> <h3>Front-running-resistant trading</h3> <p>MEV bots read pending transactions from the public mempool and execute ahead of them, extracting value at the expense of ordinary users. Shielded transactions cannot be read from the mempool — the order is visible but the content is not until finalized.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Large swaps are front-run; slippage is worse than expected</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Shielded swap intent is unreadable until included — front-running has no information to act on</div> </div> </div> <div class="uc-item"> <div class="uc-num">03</div> <div class="uc-body"> <div class="uc-tag">Governance</div> <h3>Sealed governance voting</h3> <p>On transparent chains, governance votes are visible as they accumulate. This creates incentives for last-minute vote-flipping and bribe markets where large holders sell their vote to the highest bidder. Sealed voting hides individual votes until the period closes.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Real-time vote visibility enables coordinated last-minute flips and bribe markets</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Votes are committed as shielded notes, revealed atomically at period close — no mid-flight manipulation</div> </div> </div> <div class="uc-item"> <div class="uc-num">04</div> <div class="uc-body"> <div class="uc-tag">Auctions</div> <h3>Sealed-bid auctions</h3> <p>NFT auctions, domain sales, and procurement contracts on public chains are not truly sealed — all bids are visible before close. Rational bidders wait to bid last, or shade bids based on observed competition. Shielded bids are cryptographically sealed until reveal.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Last-second sniping, bid shading from visible competition</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Bid amounts are shielded commitments — revealed simultaneously at auction close</div> </div> </div> <div class="uc-item"> <div class="uc-num">05</div> <div class="uc-body"> <div class="uc-tag">Enterprise</div> <h3>Confidential supply chain</h3> <p>A manufacturer using blockchain for supply chain payments exposes vendor relationships, payment terms, and procurement volumes to every competitor and supplier who can read the chain. Shielded transfers keep payment flows confidential while retaining the auditability of blockchain settlement.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Competitor visibility into vendor relationships and payment terms</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Payment graph is shielded; auditors with viewing key can verify; competitors see nothing</div> </div> </div> <div class="uc-item"> <div class="uc-num">06</div> <div class="uc-body"> <div class="uc-tag">Donations</div> <h3>Private charitable giving</h3> <p>Charitable donations on public chains are permanently associated with the donor’s address and wallet history. This is a privacy violation for donors and a security risk for charities operating in contested regions. Shielded donations are confirmed on-chain without linking donor identity.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Donor identity, amount, and history permanently visible</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Donation confirmed; donor address never linked on-chain</div> </div> </div> <div class="uc-item"> <div class="uc-num">07</div> <div class="uc-body"> <div class="uc-tag">Treasury</div> <h3>DAO treasury management</h3> <p>When a DAO’s treasury wallet is public, every payment to a contractor, service provider, or investment reveals that relationship to competitors and adversaries. Shielded treasury disbursements allow DAOs to operate with the efficiency of private corporate finance.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> All contractor payments, vendor relationships, and investment moves are public</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Treasury disbursements shielded; on-chain proof of spend without revealing to whom</div> </div> </div> <div class="uc-item"> <div class="uc-num">08</div> <div class="uc-body"> <div class="uc-tag">Personal</div> <h3>Everyday financial privacy</h3> <p>Sharing a wallet address to receive payment — for rent, a freelance invoice, or splitting a bill — exposes your entire financial history to the payer. Every wallet that has ever sent you funds, every token you hold, and every transaction you’ve ever made is permanently indexed. Shielded receiving breaks this graph.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> A single shared address reveals your entire financial life</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Receive shielded — payer confirms delivery; your history stays private</div> </div> </div> <div class="uc-item"> <div class="uc-num">09</div> <div class="uc-body"> <div class="uc-tag">Healthcare</div> <h3>Medical payment privacy</h3> <p>Healthcare payments on public chains create a permanent, queryable record linking patients to specific conditions, treatments, and providers. A single insurance claim or specialist payment reveals diagnoses that should remain between patient and doctor. Shielded medical payments preserve the settlement guarantee of blockchain while keeping health data confidential.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Medical payments reveal conditions, treatments, and provider relationships</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Shielded payments — insurance and provider confirm; condition stays private</div> </div> </div> <div class="uc-item"> <div class="uc-num">10</div> <div class="uc-body"> <div class="uc-tag">Freelance</div> <h3>Contractor invoice confidentiality</h3> <p>Freelancers and independent contractors who receive on-chain payments inadvertently expose their entire client list, rate card, and income history to anyone who looks up their address. A single payment from a known company links the contractor to that client permanently. Shielded receiving lets contractors get paid without broadcasting their business relationships.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Receiving payment exposes your entire client list, rate card, and income history</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Invoice via shielded receive — client confirms payment; your other clients and rates stay invisible</div> </div> </div> <div class="uc-item"> <div class="uc-num">11</div> <div class="uc-body"> <div class="uc-tag">Compliance</div> <h3>Selective disclosure for regulators</h3> <p>The false binary of full transparency versus full opacity forces users to choose between regulatory compliance and personal privacy. Viewing keys solve this by enabling granular, auditable disclosure — share a key with a regulator or auditor, and they can verify your complete transaction history without any of it being exposed to the public chain.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Full transparency or full opacity — regulators demand one, users need the other</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Share a viewing key with your auditor — they verify your history; the public sees nothing</div> </div> </div> <div class="uc-item"> <div class="uc-num">12</div> <div class="uc-body"> <div class="uc-tag">Whistleblowing</div> <h3>Anonymous tips and bounties</h3> <p>Bug bounty programs and whistleblower reward systems on transparent chains create a permanent on-chain link between the reporter and the organization they exposed. This link can be traced back to compromise the whistleblower’s identity, safety, and career. Shielded bounty payments confirm the reward was delivered without revealing who received it.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> On-chain bounty payments publicly link the whistleblower to the organization they reported</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Shielded bounty payment — recipient proves they received it; sender and amount stay private</div> </div> </div> <div class="uc-item"> <div class="uc-num">13</div> <div class="uc-body"> <div class="uc-tag">Real Estate</div> <h3>Property transaction privacy</h3> <p>Real estate transactions moving to blockchain expose exact purchase amounts, deposit timing, and buyer wealth to every chain observer. A single large deposit signals financial capacity to sellers, competitors, and adversaries. Shielded deposits let escrow contracts verify fund availability without broadcasting the transaction amount publicly.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Large property deposits broadcast exact wealth and timing to every chain observer</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Shielded deposits — escrow contract verifies funds; transaction amount is hidden from public view</div> </div> </div> <div class="uc-item"> <div class="uc-num">14</div> <div class="uc-body"> <div class="uc-tag">Cross-border</div> <h3>Private international remittances</h3> <p>Migrant workers sending money home through on-chain rails create a permanent, indexed record of amounts, frequency, and corridors. This data is a surveillance goldmine — revealing income levels, family locations, and financial patterns to anyone with a block explorer. Shielded remittances via the bridge let families receive funds without exposing the corridor or amount on-chain.</p> <div class="uc-problem"><span class="uc-problem-k">Without privacy:</span> Remittance amounts, frequency, and corridors are permanently indexed — a surveillance goldmine</div> <div class="uc-solution"><span class="uc-solution-k">With Sanect:</span> Shielded remittance via bridge — family receives funds; corridor and amount are invisible on-chain</div> </div> </div> </div> </div> </section> <!-- INDUSTRY ADOPTION --> <section class="sec bordered"> <div class="wrap"> <div class="sec-head"> <div class="eyebrow">industries · adoption potential</div> <h2>Privacy adoption by industry.</h2> </div> <div class="industry-grid"> <div class="industry-card"> <div class="industry-header"> <h3>Finance & Banking
Treasury management, inter-bank settlements, and wealth management all require transaction confidentiality that public chains cannot provide. Shielded transfers bring private banking infrastructure to decentralized rails.