Open Standard for Verified Interfaces

The blockchain is trustless.
Your interface should be too.

CHUI is the first open standard that cryptographically binds what users see to what contracts do. 83 attack vectors eliminated. Not reduced. Eliminated.

83 Attack vectors
eliminated
1 Merkle root
to verify
<100ms Verification
time
AI Contract Builder
SimpleLoan.sol

Trustless Verification

Both parties verify the same contract independently

A
Alice
Loan Agreement
1,000 USDC
Verifying...
Ethereum
B
Bob
Loan Agreement
1,000 USDC
Verifying...
Contract Verified Both parties see identical terms • No intermediary needed
Normal View
Form Input
Contract Name:
Simple Loan Agreement
Contract Details
I Alice am extending a loan of 1,000 USDC to Bob with an interest rate of 5% for a term of 30 days. Total repayment will be 1,050 USDC due at the end of the term.
See Example ⇗
Principal Amount:
1,000 USDC
Loan Duration:
30 days
Total Repayment:
1,050 USDC
Lender: Alice
A
Borrower: Bob
B
✓ CHUI VERIFIED
📝
Human Readable
No code. Just plain language agreements with fill-in-the-blank values.
🔐
Cryptographically Bound
What you see IS what executes. Verified via Merkle proof.
Role-Based Views
Lenders and borrowers see their own relevant actions and terms.

Human Readable Smart Contracts.

Natural language agreements, cryptographically verified.

Deploy with Confidence

Every contract is verified, readable, and trustless

🔒
Cryptographically Secure What you read is what executes on-chain
Instant Verification Verify any contract in milliseconds
🌐
Distributed Blockchain Registry Direct lookup, no middleman—just you and Ethereum
Scroll to explore
The Solution

How CHUI Works

A four-point verification chain that mathematically guarantees interface integrity

1

Annotate

Developers add @custom:chui annotations. Users see TWO views: high-level agreements AND granular function interfaces.

Developer writes:
@custom:chui

contract Loan Agreement
  version 1.0.0
  category lending

agreement"I {lender} am extending a loan of {amount} to {borrower}
     with an interest rate of {rate} for a term of {duration}"

fn withdraw for depositor when active
  "Withdraw Payments"
  show
    @available = availableToWithdraw() "Available""Withdraw {@available} to wallet"
Users see TWO views:
Agreement View
Loan Agreement ✓ Verified
I Alice am extending a loan of 1,000 USDC to Bob with an interest rate of 5% for a term of 30 days
For: Signing agreements, reviewing terms
Function View
Payment Vault ✓ Verified
Withdraw Payments
Withdraw 2,450.00 USDC to wallet
Available: 2,450.00 USDC
For: Executing actions, managing funds
2

Hash Everything

Source code, bytecode, deployment transaction, and interface specification are all cryptographically hashed

Source Hash
Bytecode Hash
Deploy TX Hash
Interface Hash
3

Merkle Root

On-chain: Only the Merkle root (32 bytes). Off-chain: Full specs on IPFS. The elegance of off-chain lookups with on-chain trust.

0x7f3a...
4

Verify Anywhere

Verification is 100% local, <100ms, works offline. If any component is tampered with, the hash doesn't match. Binary result: valid or rejected.

Verified - Safe to use
Rejected - Tampering detected
The Problem

$690M+ Lost to Interface Attacks

Every major DeFi exploit shares one thing: the interface lied. The blockchain worked perfectly.

$570K
Curve Finance
August 2022
DNS Hijack
14:00 Attacker gains DNS access
14:05 DNS points to fake frontend
14:15 Users approve malicious contract
14:30 $570K stolen before detection
With CHUI:
14:10 Interface verification FAILS
14:11 Users see: "Signature invalid"
14:12 $0 lost. Attack detected immediately.
$120M
BadgerDAO
December 2021
Frontend Compromise
Malicious script injected into frontend
Users thought they were staking
Actually signed unlimited approvals
$120M drained over weeks
With CHUI:
Interface hash doesn't match Merkle root
Immediate rejection. Zero loss.
8M+
event-stream
November 2018
NPM Supply Chain
Malicious contributor added to npm package
Package downloaded 8 million times
Targeted Bitcoin wallet applications
Active for months before discovery
With CHUI:
Interface signed at build time
Malicious npm code cannot modify signature
Supply chain attacks are impossible.

83 Attack Vectors Eliminated

9
DNS & Domain
Hijacking, poisoning, typosquatting, BGP attacks
8
TLS & Certificates
CA compromise, MITM, SSL stripping, key theft
8
CDN & Hosting
Edge compromise, cache poisoning, CI/CD attacks
19
JavaScript & Browser
XSS, prototype pollution, npm supply chain
11
API & Backend
Response tampering, SSRF, JWT confusion
13
Wallet & Transaction
Phishing tx, blind signing, address replacement
15
Social & Crypto
Impersonation, fake apps, weak signatures
Not reduced. Eliminated. These attacks become mathematically impossible when the interface is cryptographically verified.
Strategy

CHUI is an Open Standard

Not just open source. An open standard that creates an unbeatable ecosystem.

Open Source

  • Competitors can clone entire platform
  • Forks dilute adoption
  • Code can be copied
  • Value in having code
vs

Open Standard

  • Competitors must implement YOUR spec
  • All implementations drive YOUR ecosystem
  • Spec is un-copyable - you define it
  • Value in OWNING the language

Spec is Your Moat

Even if someone forks the code, they're implementing YOUR standard. You remain the canonical reference.

Community as Defense

When everyone uses CHUI, no competitor can launch something different. Network effects compound.

Innovation Inflows

Developers build tools for YOUR standard. Every CHUI parser, every integration strengthens your position.

Protected Brand

CHUI is trademarked. The brand is protected while the standard is open for all to implement.

Proven by Industry Leaders

GraphQL Open spec, but Facebook leads
OAuth 2.0 Open standard, providers profit
Docker Dockerfile open, Hub dominates
USB Open spec, consortium leads
For Developers

One Line. Verified Interfaces.

Add CHUI annotations to your Solidity. Verification happens automatically.

VestingSchedule.sol
/** @custom:chui
 *
 * contract Vesting Schedule
 *   version 1.0.0
 *   category defi
 *
 * parties
 *   beneficiary: address
 *
 * view beneficiary "Your Vesting"
 *   hero vestedAmount() token
 *     "Vested Balance"
 *   actions
 *     withdraw
 *       preset "Max" = claimable() primary
 */

Indentation-Based DSL

Role-based views, preset actions, and cryptographic verification—all defined in Solidity comments.

Terminal
$ npm install @contractregistry/chui-tools

$ npx hardhat deploy --network mainnet

Deploying VestingSchedule...
Contract deployed: 0x7f3a2b...
CHUI verified automatically
Merkle root: 0x9c4e...
Time to verification: 47ms

Zero Extra Work

Deploy normally. CHUI verification happens in the background. No manual steps. No configuration.

chui.config.ts
export default {
  chains: ["ethereum", "polygon", "arbitrum"],
  verification: "automatic",
  registry: "mainnet",
  // That's it. Cross-chain by default.
}

Cross-Chain by Default

One set of annotations works across all supported chains. Same verification, everywhere.

Verifiable on iOS
Verifiable on Android
Verifiable on Web
Works Offline
CNC Package Manager

apt install for Smart Contracts

Discover, install, and verify contracts with familiar package management

Terminal
$ chui search "vesting milestone"
Found 42 contracts matching "vesting milestone" VestingSchedule v2.1.0 Gold Milestone-based vesting TokenVesting v1.4.2 Silver Linear token vesting SimpleVest v0.9.0 Bronze Basic vesting contract
$ chui install VestingSchedule
Downloaded from IPFS (ipfs://Qm7f3a...) Verified Merkle root against registry Gold badge confirmed (3 auditor signatures) Installed to local cache Ready to use. Run chui deploy VestingSchedule to deploy.

Git-Style Operations

chui fork VestingSchedule my-vest chui commit --version 1.1.0 chui pull-request

Built-in Verification

chui verify VestingSchedule chui cache --sync

Fair Economics

90% of install fees go to publishers. Fork royalties vest over 365 days to original creators.

The Difference

Traditional web dApps vs. Contract Registry

Metric Web dApps Contract Registry
Attack Vectors 83 exposed 0 exposed
Trust Assumptions 8+ (DNS, CDN, npm, CA...) 1 (Merkle root)
Offline Verification Impossible Full support
Tamper Detection None Cryptographic
DNS Attacks Vulnerable Mathematically impossible
XSS Attacks Vulnerable Mathematically impossible
Supply Chain Vulnerable Mathematically impossible
Verification Result Trust-based Binary: valid or rejected

"The blockchain is trustless.
The interface you use to access it is not.
We fixed that."

Ready to Verify?

Join the protocols that trust cryptography, not infrastructure.

Open standard. Open source tooling. Enterprise-ready platform.

Get Early Access

Join the waitlist and be among the first to experience cryptographically verified smart contract interfaces.