reorg some
This commit is contained in:
60
QA_en.md
60
QA_en.md
@@ -1,60 +0,0 @@
|
||||
# Sentinel Protocol FAQ (Frequently Asked Questions)
|
||||
|
||||
---
|
||||
|
||||
### Q1: If the company behind Sentinel Protocol shuts down, can I still retrieve my data and heritage?
|
||||
**A: Yes.** Sentinel Protocol is designed with "non-dependency" as a core principle:
|
||||
* **Data Persistence**: Your core data is stored on decentralized networks like Arweave/Filecoin. Its physical existence does not depend on our central servers.
|
||||
* **Self-Rescue Kit**: The decryption tool code is entirely open-source. Even if the company ceases to exist, as long as you hold your full mnemonics or shards (S0/S1/S2), you can independently retrieve and decrypt your data using open-source tools.
|
||||
* **DAO Takeover**: Smart contracts automatically monitor company activity. If a "failure state" is triggered, control of the protocol is automatically transferred to a Decentralized Autonomous Organization (DAO).
|
||||
|
||||
---
|
||||
|
||||
### Q2: How do you prevent an heir (holding S2) from colluding with the platform (holding S1) to steal my assets?
|
||||
**A: Technical isolation makes collusion impossible.**
|
||||
Before your status is determined as "Released," the distributed nodes storing S1 shards are in a **logically locked state**. No node will provide its shard unless it detects a "Proof of Status" on the blockchain (a legitimate release signal signed by the smart contract). Even if an heir has the S2 credential, they cannot reverse-engineer the ciphertext without the system-generated release command.
|
||||
|
||||
---
|
||||
|
||||
### Q3: What if I am just in a temporary coma or working in an area with no signal (e.g., on the high seas)? Will the system misjudge me as deceased?
|
||||
**A: No.** We have designed the **Double-Lock Mechanism**.
|
||||
* **Freezing Period**: You can preset a freezing period of 180-365 days. When a heartbeat signal is interrupted, the system first enters a "Pending" state.
|
||||
* **One-Click Abortion**: During this long freezing period, the release process can be immediately terminated and reset as soon as you come back online or your emergency contact intervenes.
|
||||
* **Sleep Mode**: If you plan an extended offline expedition, you can manually activate "Sleep Mode" to pause monitoring.
|
||||
|
||||
---
|
||||
|
||||
### Q4: My financial situation is unstable recently; can I temporarily stop my subscription?
|
||||
**A: Yes.** You can activate **"Sleep Mode"** at any time.
|
||||
* **Physical Retention**: During the pause, active services like AI monitoring will stop, but your data will remain physically sealed in the storage network and will not be deleted.
|
||||
* **Instant Wake-up**: You only need to pay a small storage maintenance fee in the future to reactivate the "Sentinel" to its full active state.
|
||||
* **Extreme Extraction**: Even during a pause, if an extreme event occurs, heirs can still settle outstanding fees and trigger the extraction process according to the protocol.
|
||||
|
||||
---
|
||||
|
||||
### Q5: Does the AI see my privacy (e.g., passwords, will content) when sorting data?
|
||||
**A: Absolutely not.**
|
||||
* **Local Encryption**: Data is heavily encrypted before it even leaves your device.
|
||||
* **Shadow Proxy Technology**: The AI only processes metadata within a **TEE (Trusted Execution Environment)**. The AI is responsible for indexing and suggesting archives but does not have the key authority to decrypt the ciphertext, meaning it cannot read the actual content of your files.
|
||||
|
||||
---
|
||||
|
||||
### Q6: is the Sentinel Protocol legally valid? Can heirs use the exported keys for legal title confirmation?
|
||||
**A: Yes.** * **Legal Pre-declaration**: When you set up an S2 recipient, the system generates a "Notice of Authorization" based on a digital signature, clarifying that this act is a legal "Gift/Inheritance" authorization.
|
||||
* **Notary Integration**: For L2 users, we provide full-process legal notarization support.
|
||||
* **Multidimensional Evidence**: The extraction process is recorded on the blockchain, ensuring the authenticity of the inheritance and avoiding potential legal disputes.
|
||||
|
||||
---
|
||||
|
||||
### Q7: Why is the duration for L0 users only 10 years?
|
||||
**A: This is to ensure the robustness of the financial model.**
|
||||
10 years is a financial equilibrium point designed to cover the initial storage costs of decentralized networks and the hedging fees of the Protocol Reserve Pool. After expiration, data enters an "Extended Retention State," where heirs only need to pay a very small storage gap to complete the extraction. This design ensures the protocol remains resilient over decades.
|
||||
|
||||
---
|
||||
|
||||
### Q8: If I lose all my mnemonics, can you help me recover them?
|
||||
**A: Sorry, we cannot.**
|
||||
Sentinel Protocol adheres to a **non-custodial** principle. If you lose all your shards and have no backup of your original mnemonics, the platform does not hold your master key, and no one can force open your vault. This is the ultimate guarantee of your sovereignty and the final boundary of security.
|
||||
|
||||
---
|
||||
**Sentinel Protocol: Guarding your digital assets until sovereignty is awakened once more.**
|
||||
@@ -4,7 +4,9 @@ Welcome to the Sentinel Protocol official documentation repository.
|
||||
|
||||
## 🇨🇳 中文文档 (Chinese)
|
||||
- [产品白皮书](./zh-CN/product/README.md)
|
||||
- [技术白皮书](./zh-CN/technical/V2.0.md)
|
||||
- [技术白皮书](./zh-CN/technical/architecture.md)
|
||||
- [技术术语表](./zh-CN/technical/glossary.md)
|
||||
- [系统架构图](./zh-CN/technical/arch.md)
|
||||
|
||||
## 🇺🇸 English Documents
|
||||
- [Product Whitepaper](./en/product/V2.0.md)
|
||||
|
||||
102
tech.md
102
tech.md
@@ -1,102 +0,0 @@
|
||||
# Sentinel Protocol (哨兵协议) 技术白皮书 (V2.0)
|
||||
|
||||
## **1. 摘要 (Abstract)**
|
||||
Sentinel Protocol 提出了一种基于“主权原点 + 递归碎片”的数字资产保护框架。通过 **AI 隐私代理** 降低普惠门槛，利用 **TEE 硬件** 锁定主权执行根，并结合 **多级 SSS 算法** 实现资产的永续传承。核心创新在于：通过 **智能合约死手开关 (Dead Man Switch)** 与 **法定信托存储机制** 的双轨保障，确保在商业公司停止服务后，开源社区能接管访问权限，且数据密文在长历史时段内依然得以物理保留与解密。
|
||||
|
||||
---
|
||||
|
||||
## **2. 核心架构：四层防御体系**
|
||||
|
||||
### **2.1 AI 普惠层 (AI Accessibility Layer)**
|
||||
* **功能小助手**：将高端 Prompt 封装为预设插件，提供自然语言交互入口。
|
||||
* **隐私代理 (Privacy Proxy)**：
|
||||
* **本地拦截**：在应用端执行敏感词过滤，确保私钥片段或实名隐私 **绝不** 离开本地环境。
|
||||
* **去标识化转发**：中转代理剔除 IP、设备 ID 等元数据，使第三方 AI 厂商仅接收脱敏后的纯粹指令。
|
||||
* **本地语义总结**：端侧 AI 本地总结资产，仅在发现价值目标时提示用户进入加固流程。
|
||||
|
||||
### **2.2 硬件主权层 (Hardware Sovereignty Layer)**
|
||||
* **Master Key (K)**：由助记词派生，锁死在手机 **TEE (可信执行环境)** 内。我们不信任软件系统，只信任锁在芯片里的数学。
|
||||
* **内层加固**：数据在离机前，由 $K$ 完成第一层硬件级内层加密。
|
||||
|
||||
|
||||
|
||||
### **2.3 哨兵存储层 (Sentinel Vault Layer)**
|
||||
* **外层加固**：服务器集群对密文进行二次公钥加密，防御传输风险。
|
||||
* **永续存储**：双重加密后的密文托管于 Arweave 等去中心化永久网络。
|
||||
|
||||
### **2.4 第三方 API 接入层 (Third-Party Integration)**
|
||||
* **模式 A：独立主权模式 (Standalone)**：第三方应用使用 **独立助记词** 工作。哨兵协议仅作为存储载体和算法套件，逻辑完全隔离。
|
||||
* **模式 B：协同共享模式 (Collaborative SDK)**：第三方应用集成 **哨兵加密 SDK**。在用户生物识别授权后，协同共享主授权数据，打破数据孤岛。
|
||||
|
||||
---
|
||||
|
||||
## **3. 角色定义与密钥派生体系**
|
||||
|
||||
系统遵循从“数学元种子”到“物理分片”的严密派生逻辑：
|
||||
* **助记词 (Mnemonic)**：系统的 **元种子 (Root Seed)**，一切密钥的唯一数学起源。
|
||||
* **Master Key (K)**：锁死于 TEE 芯片，作为日常主权执行根。
|
||||
* **S0 (Redundancy)**：冗余备份片。用户离线（物理打印/U盘）保存，作为最后救济。
|
||||
* **S1 (Cloud)**：分布式递归分片，由云端节点托管。
|
||||
* **S2 (Heir)**：继承分片。由用户分发给指定的遗产处理人。
|
||||
|
||||
---
|
||||
|
||||
## **4. S1 的分布式递归裂解 (Multi-Server Fragmentation)**
|
||||
|
||||
为了彻底消除中心化节点的拖库与合谋风险，$S_1$ 采取“化整为零”的策略：
|
||||
|
||||
### **4.1 二次裂解逻辑**
|
||||
手机端在生成 $S_1$ 后，不直接上传，而是再次通过 SSS 算法将其裂解为 $n$ 个子分片 ($n \ge 2$)：$\{S_{1a}, S_{1b} \dots S_{1n}\}$。
|
||||
|
||||
### **4.2 节点加密与存储**
|
||||
* **独立加密**：每个子分片使用对应存储节点的独立公钥进行加密。
|
||||
* **分布式存储**：子分片分别分发至地理隔离、逻辑独立的多个哨兵服务器节点。
|
||||
* **安全特性**：没有任何单一服务器拥有完整 $S_1$。黑客攻破单点数据库，拿到的仅是“碎片的碎片”。
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
## **5. 业务逻辑流程 (Workflow)**
|
||||
|
||||
### **5.1 数据入库流**
|
||||
1. **识别确权**：本地 AI 发现信息，征得用户生物识别授权。
|
||||
2. **双重加密**：TEE 调用 $K$ 完成内层加固 $\rightarrow$ 服务器执行外层加固。
|
||||
3. **递归分发**：$S_1$ 裂解为多子分片，加密后飞向不同地理节点。
|
||||
|
||||
### **5.2 传承与恢复流**
|
||||
1. **状态判定**：智能合约监测到失能信号。
|
||||
2. **分片归集**：多节点验证合约指令，解密并释放各自的子分片。
|
||||
3. **多级重构**：
|
||||
* **一级重构**：子分片重构出原始云分片 $S_1$。
|
||||
* **二级重构**：$S_1$ 与继承人持有的 $S_2$（或冗余片 $S_0$）合成 Master Key (K)。
|
||||
4. **解密资产**：利用 $K$ 剥离内层加密，获取原始资产。
|
||||
|
||||
---
|
||||
|
||||
## **6. 生存保障与安全总结**
|
||||
|
||||
### **6.1 生存保障 (The Great Survival Protocol)**
|
||||
* **法定信托与续费**：专项信托基金独立于商业实体，确保存储费用在长历史时段内的物理有效性。
|
||||
* **死手开关 (Dead Man Switch)**：一旦商业公司失能，智能合约自动释放密文索引与节点私钥，开源社区接管访问。
|
||||
* **开源自救**：用户通过开源工具，配合 $S_2/S_0$ 本地还原 $K$，即便官方消失也能找回数据。
|
||||
|
||||
### **6.2 安全性总结 (Security Highlights)**
|
||||
* **抗拖库 (Anti-DB Leak)**：云端 $S_1$ 碎裂化存在，单点沦陷无意义。
|
||||
* **隐私主权化**：Privacy Proxy 物理隔离 AI 侧写风险。
|
||||
* **唯一性与鲁棒性**：$K$ 锁死 TEE，且系统在部分节点掉线时依然能重构数据。
|
||||
|
||||
---
|
||||
|
||||
## **附录：技术术语表 (Appendix: Glossary)**
|
||||
|
||||
| 术语 | 通俗定义 | 在本协议中的角色 |
|
||||
| :--- | :--- | :--- |
|
||||
| **TEE (可信执行环境)** | 手机芯片里的“独立保险箱”。 | 存储主密钥 $K$，防止即便手机中毒也被盗取密钥。 |
|
||||
| **SSS (秘密共享算法)** | 就像古代的“虎符”，拆开是碎片，合拢是权力。 | 将主密钥拆分为 $S_0, S_1, S_2$，实现容灾备份。 |
|
||||
| **Mnemonic (助记词)** | 系统的“元种子”，生命中最重要的单词。 | 恢复一切资产的最高权限根源。 |
|
||||
| **Privacy Proxy (隐私代理)** | 你的“数字替身”，替你和 AI 说话。 | 拦截本地敏感信息，抹除 IP/设备 ID，防止身份泄露。 |
|
||||
| **Arweave** | 一种“永不磨灭”的数字石碑。 | 永久托管加密密文，解决传统云盘倒闭后的数据丢失问题。 |
|
||||
| **Recursive Sharding (递归裂解)** | 就像把碎纸机出来的纸片再撕碎一次。 | 确保存储节点即便被盗，也拿不到完整的云分片 $S_1$。 |
|
||||
| **Dead Man Switch (死手开关)** | 如果我不打卡了，协议自动执行。 | 判定商业公司状态，若倒闭则将解密权限移交社区。 |
|
||||
| **Legal Trust (法定信托)** | 一份受法律保护的数据“维护基金”。 | 确保存储费用持续缴纳，不因公司破产而断缴续费。 |
|
||||
103
whitepaper_cn.md
103
whitepaper_cn.md
@@ -1,103 +0,0 @@
|
||||
# Sentinel Protocol (哨兵协议) 白皮书
|
||||
> **——基于 AI 与区块链的数字生命永续存储与智能传承协议**
|
||||
|
||||
## 目录
|
||||
- [1. 项目背景与深度痛点](#1-项目背景与深度痛点)
|
||||
- [2. 核心技术：持久化存储与分片主权](#2-核心技术持久化存储与分片主权)
|
||||
- [3. 被动验证与状态机：多维服务边界](#3-被动验证与状态机多维服务边界)
|
||||
- [4. 永续性治理：社区共治与故障转移](#4-永续性治理社区共治与故障转移)
|
||||
- [5. AI 应用层：智能管家](#5-ai-应用层智能管家)
|
||||
- [6. 开发者生态：开放 API](#6-开发者生态开放-api)
|
||||
- [7. 经济模型：差异化分级与储备池](#7-经济模型差异化分级与储备池)
|
||||
- [8. 结论](#8-结论)
|
||||
|
||||
---
|
||||
|
||||
## 1. 项目背景与深度痛点
|
||||
* **1.1 数字遗产“永久锁死”**：由于私钥随持有者离世而丢失，导致去中心化资产不可逆损失。
|
||||
* **1.2 互联网数据“十年消失律”**：商业公司倒闭导致 38% 的链接在 10 年内失效，用户数字记忆面临蒸发。
|
||||
* **1.3 意义淹没与筛选困境**：海量冗余数据导致用户无法从碎片信息中提取真正具有传承价值的关键资产。
|
||||
* **1.4 高危行业“猝发断裂”**：矿工、海员等群体在零预警、零网络状态下的资产提取鸿沟。
|
||||
|
||||
---
|
||||
|
||||
## 2. 核心技术：持久化存储与分片主权
|
||||
### 2.1 碎裂化密钥管理与用户绝对主权 (SSS 3/2)
|
||||
* **用户主权态 (组合 A)**：用户初始化即拥有完整助记词熵值，拥有 S0、S1、S2 全集控制权。在生前任何时刻，用户均具备 **100% 主权自决**。
|
||||
> **主权定义**：这意味着你无需任何人的许可，即可完成日常调用。无论是资产划转还是文件读取，系统均通过生物识别在后台完成验证，用户拥有绝对的掌控力与顺畅的使用体验。
|
||||
* **S1 与 S2 防串通机制 (Anti-Collusion Logic)**：
|
||||
* **逻辑隔离**：在判定逻辑触发前，S1 分布式节点处于锁定状态，拒绝任何碰撞请求。
|
||||
* **合约见证释放**：S1 的解冻必须由智能合约检测到系统进入“Released”状态后，方可签署释放指令，彻底杜绝托管方与继承人私下合谋。
|
||||
* **传承提取态 (组合 B)**：状态判定成立后，S1 自动解冻，继承人凭 S2 碰撞提取资产。
|
||||
|
||||
### 2.2 S1 去中心化分发与多重存储保障
|
||||
* **异构冗余备份**：同步对接 Arweave (永久存储)、Filecoin (激励存储) 及多司法管辖区的异构加密节点。
|
||||
* **VSS 分布式托管**：S1 分片利用 **可验证秘密分享 (VSS)** 再次切割，分布式存储于去中心化网络，消除单一服务器崩溃风险。
|
||||
|
||||
### 2.3 AI 驱动的“数据漏斗”与自动归档
|
||||
* **智能分拣**：AI 在日常交互中识别高价值信息，自动建议用户将关键要素（账号、保单、遗嘱意愿）结构化归档，实现“一键灌装”。
|
||||
|
||||
---
|
||||
|
||||
## 3. 被动验证与状态机：多维服务边界
|
||||
### 3.1 判定中 (Pending) 的二次锁定机制 (Double-Lock)
|
||||
* **防误判宽限**：若系统触发 Pending（失联信号），用户可预设进入 **180-365 天的冷冻期**。期间系统禁止释放任何数据，确保处于长期昏迷或特殊环境下的用户主权不被洗劫。
|
||||
* **复合验证**：结合低敏感隐私监测（步数、心跳、交互频率）与紧急联系人人工核实。
|
||||
|
||||
### 3.2 已释放 (Released) 与自动化交付
|
||||
* **影子代理 (AI Proxy)**：在 **TEE (可信执行环境)** 中运行，AI 生成结构化的《数字遗产继承指南》并主动推送给指定的继承人。
|
||||
### 3.3 暂停订阅与恢复机制 (Suspension & Recovery)
|
||||
* **睡眠态 (Sleep Mode)** ：用户可主动触发“暂停订阅”。
|
||||
|
||||
* **服务静默**：进入此状态后，系统停止主动心跳监测与 AI 资产分拣。
|
||||
|
||||
* **物理存续**：得益于多重存储体系（Arweave/Filecoin），核心密文数据依然在底层网络物理封存，不受订阅状态影响。
|
||||
|
||||
* **唤醒逻辑**：用户随时可通过身份验证（S0/助记词）补缴欠缴的维护成本，一键恢复至“活跃态”。
|
||||
|
||||
* **睡眠态下的极端提取**：若用户在睡眠态离世，持有 S2 的继承人仍可发起提取请求。系统将引导继承人结算欠费后，进入释放流程。
|
||||
---
|
||||
|
||||
## 4. 永续性治理：社区共治与故障转移
|
||||
* **4.1 数字信托基金会**：独立法人实体，管理存储基金与分片安全。
|
||||
* **4.2 智能故障转移 (Smart Failover)**：区块链智能合约实时监测商业实体活跃度。若异常超过阈值（如心跳丢失），系统控制权自动移交给 **社区自治组织 (DAO)** 接管，确保服务永不宕机。
|
||||
|
||||
---
|
||||
|
||||
## 5. AI 应用层：智能管家
|
||||
* **5.1 影子网关**：AI 辅助处理日常任务，但不触碰核心密文，保障隐私边界。
|
||||
|
||||
---
|
||||
|
||||
## 6. 开发者生态：开放 API
|
||||
* **开放保险柜 API**：支持第三方应用（钱包、密码管理等）接入，共用协议与资源，共享产生的收益分润。
|
||||
|
||||
---
|
||||
|
||||
## 7. 经济模型：差异化分级与储备池
|
||||
### 7.1 服务等级体系
|
||||
| 等级 | 持久期 | 提取费 | 法律服务能力 | 增值特性 |
|
||||
| :--- | :--- | :--- | :--- | :--- |
|
||||
| **Standard (L0)** | 10 年 | 补足欠费+服务费 | 基础存证+定制咨询 | 提取费支持预付，离线密钥可选 |
|
||||
| **Premium (L1)** | 20 年 | 免提取服务费 | 电子签名+定制咨询 | 大数据配额，无感继承体验 |
|
||||
| **Eternal (L2)** | 100 年+ | 免提取服务费 | 全流程公证+定制咨询 | 银行级密钥托管，定期冷备份 |
|
||||
|
||||
### 7.2 财务稳健性：协议储备池 (Reserve Pool)
|
||||
* **交叉补贴逻辑**：从 L1/L2 等级的高溢价收入中提取 10% 注入储备池。
|
||||
* **风险对冲**：储备池用于对冲未来存储成本波动，并作为 L0 级用户的存储违约兜底基金，确保全量用户的数据物理安全。
|
||||
|
||||
### 7.3 线下服务与定制化咨询
|
||||
* **线下冷钱包密钥服务**：针对全量用户开放。L2 用户额外享受受银行级安保监控的离线存储环境。
|
||||
* **全量法律服务**：所有等级用户均可预约战略合作律所进行重要文件的法律效力认证及定制咨询。
|
||||
|
||||
### 7.4 存储超额费用
|
||||
* **用户配额外收费**：每个等级都有一定的配额，超过后额外收费
|
||||
|
||||
|
||||
---
|
||||
|
||||
## 8. 结论
|
||||
Sentinel Protocol 建立了以“用户主权”为核心的数字资产传承新范式。通过 **S1 分布式托管** 与 **防串通协议** 杜绝风险，利用 **二次锁定机制** 保护失能主权，结合 **协议储备池** 实现经济长效，为人类文明的数字资产提供了一个可信、永续、合法的避风港。
|
||||
|
||||
---
|
||||
**哨兵协议：守护你的数字资产，直到主权再次被唤醒。**
|
||||
@@ -1,94 +0,0 @@
|
||||
# Sentinel Protocol Whitepaper
|
||||
> **—— An AI & Blockchain-based Protocol for Digital Life Perpetual Storage and Intelligent Inheritance**
|
||||
|
||||
## Table of Contents
|
||||
- [1. Project Background & Pain Points](#1-project-background--pain-points)
|
||||
- [2. Core Technology: Perpetual Storage & Shared Sovereignty](#2-core-technology-perpetual-storage--shared-sovereignty)
|
||||
- [3. Passive Verification & State Machine: Service Boundaries](#3-passive-verification--state-machine-service-boundaries)
|
||||
- [4. Perpetual Governance: Community Co-governance & Failover](#4-perpetual-governance-community-co-governance--failover)
|
||||
- [5. AI Application Layer: Intelligent Proxy](#5-ai-application-layer-intelligent-proxy)
|
||||
- [6. Developer Ecosystem: Open API](#6-developer-ecosystem-open-api)
|
||||
- [7. Economic Model: Tiered Services & Reserve Pool](#7-economic-model-tiered-services--reserve-pool)
|
||||
- [8. Conclusion](#8-conclusion)
|
||||
|
||||
---
|
||||
|
||||
## 1. Project Background & Pain Points
|
||||
* **1.1 "Permanent Lock" of Digital Heritage**: Irreversible loss of decentralized assets due to private keys being lost upon the owner's passing.
|
||||
* **1.2 The "Ten-Year Disappearance Law" of Internet Data**: 38% of web links fail within 10 years due to company bankruptcies, leading to the evaporation of digital memories.
|
||||
* **1.3 Meaning Drowning & Filtering Dilemma**: Massive data redundancy makes it impossible for users to extract key assets of true inheritance value from the flood of information.
|
||||
* **1.4 High-Risk Industry "Sudden Disconnection"**: A gap in asset retrieval for groups like miners and sailors in zero-warning or zero-network environments.
|
||||
|
||||
---
|
||||
|
||||
## 2. Core Technology: Perpetual Storage & Shared Sovereignty
|
||||
### 2.1 Fragmented Key Management & Absolute User Sovereignty (SSS 3/2)
|
||||
* **Sovereign State (Combination A)**: Upon initialization, the user possesses the full mnemonic entropy and holds total control over S0, S1, and S2. At any moment during their lifetime, the user maintains **100% sovereign self-determination**.
|
||||
> **Sovereignty Definition**: This means you can complete daily calls and transactions without anyone’s permission. Whether it is transferring assets or reading files, the system completes verification in the background via biometrics, providing the user with absolute control and a seamless experience.
|
||||
* **S1 & S2 Anti-Collusion Mechanism**:
|
||||
* **Logical Isolation**: Before the inheritance logic is triggered, S1 distributed nodes remain locked, rejecting any collision requests.
|
||||
* **Contract Witness Release**: The unlocking of S1 must be triggered by a smart contract detecting the "Released" status. This prevents collusion between the hosting party and the heirs.
|
||||
* **Inheritance Extraction State (Combination B)**: Once the state is determined, S1 is automatically unfrozen, allowing heirs to extract assets using S2.
|
||||
|
||||
|
||||
|
||||
### 2.2 Decentralized S1 Distribution & Multi-Storage Redundancy
|
||||
* **Heterogeneous Redundant Backup**: Synchronized interfacing with Arweave (permanent storage), Filecoin (incentivized storage), and heterogeneous encryption nodes across multiple jurisdictions.
|
||||
* **VSS Distributed Hosting**: S1 shards are further sliced using **Verifiable Secret Sharing (VSS)** and stored across a decentralized network to eliminate the risk of a single server crash.
|
||||
|
||||
### 2.3 AI-Driven "Data Funnel" & Auto-Archiving
|
||||
* **Intelligent Sorting**: AI identifies high-value information during daily interactions and suggests structured archiving for key elements (accounts, insurance policies, wills), achieving "one-click filling."
|
||||
|
||||
---
|
||||
|
||||
## 3. Passive Verification & State Machine: Service Boundaries
|
||||
### 3.1 "Double-Lock" Mechanism in Pending State
|
||||
* **Anti-Misjudgment Grace Period**: If the system triggers a "Pending" status (loss of signal), the user can preset a **180-365 day freezing period**. During this time, the system is prohibited from releasing any data, ensuring that the sovereignty of users in long-term comas or special environments is not compromised.
|
||||
* **Composite Verification**: Combines low-sensitivity privacy monitoring (steps, heart rate, interaction frequency) with manual verification from emergency contacts.
|
||||
|
||||
### 3.2 Released State & Automated Delivery
|
||||
* **Shadow Proxy (AI Proxy)**: Running in a **TEE (Trusted Execution Environment)**, the AI generates a structured "Digital Heritage Inheritance Guide" and actively pushes it to designated heirs.
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
## 4. Perpetual Governance: Community Co-governance & Failover
|
||||
* **4.1 Digital Trust Foundation**: An independent legal entity managing the storage fund and shard security.
|
||||
* **4.2 Smart Failover**: Smart contracts monitor the activity of the commercial entity in real-time. If anomalies exceed a threshold (e.g., loss of heartbeat), control of the system is automatically transferred to a **Decentralized Autonomous Organization (DAO)** to ensure the service never goes offline.
|
||||
|
||||
---
|
||||
|
||||
## 5. AI Application Layer: Intelligent Proxy
|
||||
* **5.1 Shadow Gateway**: AI assists in handling daily tasks without touching core ciphertexts, maintaining a strict privacy boundary.
|
||||
|
||||
---
|
||||
|
||||
## 6. Developer Ecosystem: Open API
|
||||
* **Open Vault API**: Supports third-party applications (wallets, password managers, etc.) to access the protocol, share resources, and participate in revenue sharing.
|
||||
|
||||
---
|
||||
|
||||
## 7. Economic Model: Tiered Services & Reserve Pool
|
||||
### 7.1 Service Tier System
|
||||
| Tier | Retention Period | Retrieval Fee | Legal Support | Value-Added Features |
|
||||
| :--- | :--- | :--- | :--- | :--- |
|
||||
| **Standard (L0)** | 10 Years | Dues + Service Fee | Basic Evidence | Pre-paid retrieval fees supported |
|
||||
| **Premium (L1)** | 20 Years | **Waived** | E-Signature + Consulting | Large quota, seamless inheritance |
|
||||
| **Eternal (L2)** | 100+ Years | **Waived** | **Full Notarization** | **Bank-grade Key Vault**, Cold Backup |
|
||||
|
||||
### 7.2 Financial Stability: Protocol Reserve Pool
|
||||
* **Cross-Subsidization**: 10% of revenue from L1/L2 premiums is injected into the Reserve Pool.
|
||||
* **Risk Hedging**: The pool hedges against future storage cost fluctuations and acts as a guarantee fund for L0 users, ensuring the physical security of all data.
|
||||
|
||||
### 7.3 Offline Services & Customized Consulting
|
||||
* **Offline Cold Wallet Key Service**: Available to all users. L2 users enjoy an offline environment monitored by bank-grade security.
|
||||
* **Universal Legal Service**: Users of all levels can book consultations with partner law firms for legal certification of important documents.
|
||||
|
||||
---
|
||||
|
||||
## 8. Conclusion
|
||||
Sentinel Protocol establishes a new paradigm for digital asset inheritance centered on "User Sovereignty." By utilizing **S1 Distributed Hosting** and **Anti-Collusion Protocols** to eliminate risks, employing **Double-Lock Mechanisms** to protect incapacitated sovereignty, and integrating a **Protocol Reserve Pool** for economic longevity, it provides a trusted, perpetual, and legal haven for human digital civilization.
|
||||
|
||||
---
|
||||
**Sentinel Protocol: Guarding your digital assets until sovereignty is awakened once more.**
|
||||
@@ -66,6 +66,9 @@
|
||||
|
||||
## 5. AI 应用层：智能管家
|
||||
* **5.1 影子网关**：AI 辅助处理日常任务，但不触碰核心密文，保障隐私边界。
|
||||
* **5.2 高级提示词封装与场景化助手**：
|
||||
* **技能胶囊化 (Skill Capsules)**：将复杂的提示词工程（Prompt Engineering）封装为开箱即用的功能模块。用户无需学习 AI 指令，只需选择“资产盘点”、“家书撰写”或“法律咨询”等场景，系统即自动加载后台经过深度优化的思维链（CoT），引导用户高效完成信息整理。
|
||||
* **AI 助手矩阵**：内置“资产侦探”（帮助回忆隐形资产）与“情感陪跑”（降低身后事规划焦虑）等专用助手，通过启发式对话降低用户的使用门槛与心理负担。
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user