Skip to content

Commit fce6464

Browse files
committed
docs: Remove blockchain question in FAQ
Signed-off-by: Facundo Tuesca <[email protected]>
1 parent c71b9da commit fce6464

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

content/en/about/faq.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -146,10 +146,6 @@ We would love that. The more people monitoring the logs and providing useful ser
146146

147147
There's no need for a distributed source of transparency as there can be multiple points of transparency which only adds more sources of security guarantee, not fewer. An entity can post to as many Rekor logs as they want and inform users of where they post. We do encourage folks to use common public instances, but we don't seek to enforce this. We do plan to look to produce a gossip protocol, for those that desire a more decentralised model (if there's demand).
148148

149-
### Why not use a blockchain?
150-
151-
Public blockchains often end up using a centralized entry point for canonicalization and authentication. Consensus algorithms can be susceptible to majority attacks, and transparency logs are more mature and capable for what we aim to build with sigstore.
152-
153149
### Why use a Merkle Tree/Transparency log?
154150

155151
- Rekor's back end is [Trillian](https://github.com/google/trillian)

0 commit comments

Comments
 (0)