Skip to content
This repository was archived by the owner on Mar 25, 2025. It is now read-only.

Commit ebc7756

Browse files
committed
fix leftover
1 parent 581f8f0 commit ebc7756

1 file changed

Lines changed: 0 additions & 4 deletions

File tree

docs/getting-started/customization.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,6 @@ sidebar_position: 3
66

77
Developers can modify and extend the boilerplate to create their own privacy-preserving applications by customizing these following components.
88

9-
- Add new data sources: e.g.
10-
11-
12-
139
## 1. Modify the TLSNotary prover and verifier for new data sources.
1410

1511
> This is a bit different from original TLSNotary, because in addition to being able to specify "redacted" parts of data where they are just not shown in the proof, users can also specify the "private" parts in the proof, which are not only not shown in the proof, but also having their sha3 commitment in the proof such that they can be seamlessly integrated with MP-SPDZ to make sure that the inputs of MP-SPDZ actually come from the private parts of these data from TLSNotary. This guide will mostly focus on customizing this additional "private" feature.

0 commit comments

Comments
 (0)