My first reaction to a new protocol isn't to ask in the group "Is this reliable," but to check two things: GitHub and the audit report. Don't just look at the stars on GitHub; first see if anyone has been actively making changes recently, if issues are being responded to; also, don't be fooled by the logo on the audit report, focus on whether the identified issues have been fixed and if the re-audit is on schedule. Add one more point: who is responsible for the multi-signature upgrade, how many people are required, and whether the keys are distributed... Basically, it's about whether they can stop the problem when it happens, and whether the people who can stop it are trustworthy. Recently, before and after major public chain upgrades, everyone guesses about migration, but I care more whether these projects have redundancy measures, like my own computer file backup approach: not expecting it to never break, but if it does, don’t put everything in one basket. Anyway, that’s it for now; even beginners can filter out a lot of flashy stuff with just these few checks.