GrowBlocks
Home
Solutions
Cases
Knowledge
Design
Media
Cross-chain · Bridge

Lower the assumption of trust

Cross-chain bridge

PeriodAbout 1.5 months
Business LineCross-chain bridges / multi-chain assets
Core StackMulti-chain contracts / validators / listeners
RegionChina

Project Background and Challenges

Customers already have multi-chain deployments and need reliable cross-chain asset bridges to enable users to transfer assets across chains. The challenge lies in cross-chain bridges, which have always been a hotspot for attacks; any centralized trust is a potential attack surface.

Selection of safety models— Multisig / threshold signature / optimistic verification / ZK each requires trade-offs. Our goal is to minimize trust assumptions within acceptable performance limits.

The scope we undertake

Cross-chain contracts (source chain / target chain), validators / relay nodes, on-chain event listeners, user frontends, emergency circuit breaker mechanisms.

Scope 1
Cross-chain contracts (source chain / target chain)
Scope 2
Validators / Relay nodes
Scope 3
On-chain event listeners
Scope 4
User front-end
Scope 5
Emergency circuit breaker mechanism

Technology stack

合约
Contract
Multi-chain smart contracts (source/target)
验证
Verification
Threshold Signature / Validator Scheme
中继
Relay
On-chain event monitoring and cross-chain message relay
安全
Safety
Circuit breaker mechanism + upper limit control

Key technical decisions

Decision 01
Assume the trust is minimized
Choose threshold signature + decentralized validator solution to avoid single custody and reduce the concentration of targeted funds.
Decision 02
Circuit breakers and upper limits
Set upper limits for single transactions and daily cumulative transactions; abnormal situations trigger immediate circuit breaks, limiting potential losses within a controllable range.
Decision 03
Auditing and stress testing
Multiple rounds of audits and offense-defense drills before launch, leaving no room for trial and error in cross-chain bridges.

Delivery Success (Desensitization)

10+ items
Supported chain count
1 min
Cross-chain confirmation time
Multiple rounds
Third-party audit

Teams and cycles

The total cycle is about 1.5 months, involving 10 people, progressing in four phases:

01
Safety model design
02
Contracts and validators
03
Relay and monitoring
04
Audit and online service

Related Content

Case library
Multi-chain MPC wallet
View Details
Custom development
Public Chain· Layer 2 development
View Details
Knowledge base
Why are cross-chain bridges always being criticized?
View Details
contact us

Want to see the complete Figma file?

Schedule a 30-minute technical consultation where we walk you through the most relevant Figma / Lanhu files for your project via remote demo, including all pages, component libraries, and interactive prototypes.