From f801aee1378f536a41f0eb5a299787a28d983137 Mon Sep 17 00:00:00 2001
From: Rasmus Dahlberg <rasmus@mullvad.net>
Date: Wed, 30 Mar 2022 20:13:59 +0200
Subject: move issues into a common pad

---
 issues/add-verify-tooling.md | 14 --------------
 1 file changed, 14 deletions(-)
 delete mode 100644 issues/add-verify-tooling.md

(limited to 'issues/add-verify-tooling.md')

diff --git a/issues/add-verify-tooling.md b/issues/add-verify-tooling.md
deleted file mode 100644
index a6eb305..0000000
--- a/issues/add-verify-tooling.md
+++ /dev/null
@@ -1,14 +0,0 @@
-**Title:** Add verify tooling </br>
-**Date:** 2021-12-09 </br>
-
-# Summary
-Add a command-line utility that makes log verification easy.
-
-# Description
-This issue requires design considerations before getting started.  The goal is
-to have a verify tool that checks if some data is signed and transparency logged
-without any outbound network connections.  It should be possible to configure
-which policy to use for known logs and required witnesses.
-
-(Remark: there is no strict requirement that this has to be in Go.  If anyone
-wants to work on tooling in, say, rust or python, that would be welcomed too.)
-- 
cgit v1.2.3