Trustlessly verifying the claim that XEN has "no admin keys"

genesis_1_1_1

Having "no admin keys" is an essential attribute of the Xen contract. How can this be verified by reading the contract? (https://etherscan.io/address/0x06450dEe7FD2Fb8E39061434BAbCFC05599a6Fb8#code) I can understand code somewhat, but what am I looking for exactly? Especially when the goal is to identify the absence of something?

According to this answer, "even if a contract is immutable (no admin key), a lot of time they have other issues that act essentially as an admin key". Does anyone have any insight on this?
https://ethereum.stackexchange.com/a/133227

Here is report from Certik, which seems to have a good reputation:
https://skynet.certik.com/projects/xen-crypto
On this page, under "Centralization Overview", it is suggested that the contract is not modifiable. But is the trust of others all that we have to go off of regarding this claim of "no admin keys"? It's not realistic for everyone to be an expert in smart contract security, so what can a common person do to verify this claim themselves?

TreeCityWes

genesis_1_1_1 The key is to look at the functions that can be called and by who. To say there are admin keys means there are functions that only an admin or contract owner can call. Check the write functions and you'll see there are no special permissions or contract owner defined. There are no functions that only an admin can run and no owner to call those functions if they existed.

IkennaGIfenna

TreeCityWes The people that spread this fud have done no research. Unfortunately, they will miss a good opportunity to make money from Xen if they continue this way. The worst is Cleo. The guy is too toxic too

madmike

Most will fail to see how important all the first principles are and come running to the XEN ecosystem and family in the future...it's only a matter of time and log(2) math