1 Introduction and Background
2 Limitations of BTC and BTC-pegged Assets
- 2.1 Limited Empowerment of BTC Native Assets
- 2.2 Weaknesses of BTC-pegged Assets
3 Overview of SATPORT
4 SATPORT Technical Architecture
- 4.1 Hyper-Scalability Solution: zk-HSS
- 4.2 SATPORT's Dual Security Mechanism
5 satBTC
6 Ecosystem Development Plan
7 Exploring the Integration of ZKP with BTC Use Cases
- 7.1 Research Direction and Planning
- 7.2 Applications of Chain State Proofs
8 RaaS Strategy
9 Conclusion

Powered by GitBook

On this page

4 SATPORT Technical Architecture

4.1 Hyper-Scalability Solution: zk-HSS

4.1.2 Asset "peg-in" Solution

Trust-Minimized Asset "peg-in" Solution Using Zero-Knowledge Proofs

Previous4.1.1 Private Key Sharding Next4.1.3 "Peg-In" Process

Last updated 1 year ago