Probably because of the broad agreement among crypto people that reinventing core crypto wheels is almost always a bad idea. On top of that, the intersection between the set of people who are qualified to write that crypto code and the set of people who know Haskell well enough to do a good job of it is probably the empty set.
cryptol (https://en.wikipedia.org/wiki/Cryptol)
seL4 (https://en.wikipedia.org/wiki/L4_microkernel_family#High_ass...)
Secondly, if you know where someone has claimed that Haskell lets you "formally prove the code implements the spec" then please point it out to me so I can challenge them for being misleading at best.
SeL4. It comes up regularly that C, or java or python or some other well used language doesn't work well with isabelle, coq because of pointers, destructive assignment or whatever but haskell is pure and this is one of the many advantage of pure. I don't have this opinion myself nor have I formed the opinion that it's false.
"This library provides native Haskell TLS and SSL protocol implementation for server and client."
0: http://hackage.haskell.org/package/tls
EDIT: This Github issue provides some great discussion about the security of this library and links to some good discussion as well:
The claims about being able to formally prove the code implements the spec would be pretty damn compelling in that space too.
Once upon a time I asked on HN if there are any useful and usable haskell programs you can just install and run for a purpose that isn't writing haskell code. Shellcheck & pandoc seemed to be the suggested examples. Is that still the case or are there now a few more?