diff --git a/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_14_14f46277adb38d5cb802cd23eb2cde04._comment b/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_14_14f46277adb38d5cb802cd23eb2cde04._comment
new file mode 100644
index 0000000000..d290f80a88
--- /dev/null
+++ b/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_14_14f46277adb38d5cb802cd23eb2cde04._comment
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 14"""
+ date="2021-08-12T18:42:03Z"
+ content="""
+I've implemented a tailVerify; all that remains to be done is hook
+all special remotes that retrieve to a file up to use it.
+
+That's mostly ones using fileRetriever, which will come down to making
+retrieveChunks use it, probably. Although it may be that a few of them,
+like Remote.Directory, could avoid using it and feed the verifier
+themselves, more efficiently.
+
+There are also a couple of special remotes that don't use fileRetriever or
+retrieveChunks but could also use tailVerify. Looks like only Remote.BitTorrent
+and Remote.Web. But bittorrent is just the kind of thing that tailVerify
+will not support well due to random access. And Remote.Web could feed the
+verifier itself.
+"""]]