A systematic approach for evaluating the role of surface-exposed loops in trypsin-like serine proteases applied to the 170 loop in coagulation factor VIIa

Abstract Proteases play a major role in many vital physiological processes. Trypsin-like serine proteases (TLPs), in particular, are paramount in proteolytic cascade systems such as blood coagulation and complement activation. The structural topology of TLPs is highly conserved, with the trypsin fold comprising two β-barrels connected by a number of variable surface-exposed loops that provide a surprising capacity for functional diversity and substrate specificity. To expand our understanding of the roles these loops play in substrate and co-factor interactions, we employ a systematic methodology akin to the natural truncations and insertions observed through evolution of TLPs. The approach explores a larger deletion space than classical random or directed mutagenesis. Using FVIIa as a model system, deletions of 1–7 amino acids through the surface exposed 170 loop, a vital allosteric regulator, was introduced. All variants were extensively evaluated by established functional assays and computational loop modelling with Rosetta. The approach revealed detailed structural and functional insights recapitulation and expanding on the main findings in relation to 170 loop functions elucidated over several decades using more cumbersome crystallization and single deletion/mutation methodologies. The larger deletion space was key in capturing the most active variant, which unexpectedly had a six-amino acid truncation. This variant would have remained undiscovered if only 2–3 deletions were considered, supporting the usefulness of the methodology in general protease engineering approaches. Our findings shed further light on the complex role that surface-exposed loops play in TLP function and supports the important role of loop length in the regulation and fine-tunning of enzymatic function throughout evolution.

Abstract licence: CC BY-NC-ND

A person counts once a day per paper. We keep no cookie and no address: a reader is a hash that changes every day. Any month under five reads shows no number.