I agree that quick answer acceptance is bad. Particularly with Bitcoin vs. say programming, many people have fundamental misunderstandings about it, and it is diffeacult to tell the difference without already knowing the answer.
With programming questions, usually you confirm the correctness of the answer in your own code before marking the answer correct. It's very difficult to do that with Bitcoin answers. I would recommend that one NEVER mark an answer correct unless they have independently confirmed it correct. Or have a priori knowledge when asking.
Even then it does not guarantee that the answer is complete. For example there is a question about Bitcoin address typos that has an approved answer that does not mention the fact that addresses have checksums. People get the correct information that their bitcoins would be destroyed if they sent them to a bad address, but miss the information that such typeos are difficult to make. This leaves a bad and incorrect impression of usability.