Part:BBa_K3039020
PETase Reconstructed Ancestor 4
An important part of our project is engineering more stable enzymes that will last longer in our filter. In order to achieve this, we decided to make use of the method of ancestral reconstruction. This technique is used to recover ancestral traits that are useful but have been lost during the process of evolution; and relies on a large number of sequences, phylogenetic analysis, and modelling.
We started by searching current papers for phylogenetic trees of PETase that have already been built. We identified a paper that had already organised plastic-degrading enzymes into categories, and had identified a set of enzymes that were closely related to PETase. We used BLAST software to search for sequences homologous to PETase and the set of enzymes previously identified in the paper; and through this process identified 243 homologous sequences. These sequences were aligned and narrowed down to 76 sequences with the help of Professor Harmer from the University of Exeter Living Systems Institute. The final alignment of the sequences was then fed into the ANCESCON software that performed the ancestral reconstruction. The software produced a phylogenetic tree and identified 74 ancestors. In order to identify the most suitable ancestors to model and use, we used the method below to weight each one:
Following this method, we identified 4 potentially suitable ancestors to further analyse. The YASARA software was used to model the 3D structure of each of the four ancestors. The models produced were then aligned against the structure of PETase by Professor Harmer in order to identify significant changes in the sequences. We discovered that the catalytic triad was conserved in all four ancestors, suggesting that the PET degrading activity had not been lost. Interestingly, we have also discovered that a beneficial mutations reported in past papers was already present in all four of the ancestors, namely R280A. The only significant trait lost during the reconstruction was the second disulfide bond that was present in PETase but not the ancestors. However, we reverted this by changing the two alanine residues in the ancestors with two cysteine residues. Additionally, we deleted the first five amino acids from the N-terminus that we suspected were composing the signal peptide. Once these minor adjustments had been completed, we sent the final sequences to be synthesised.
Characterisation
In order to characterise our part and determine the rate of its activity and prove its functionality we have run a series of experiments. After transforming the Arctic Express, Rosetta Gami and BL21 DE3 strains of E. coli with our plasmid we induced the expression of the enzymes using IPTG. In order to confirm that the enzyme expression has been successful we ran a western blot which showed the presence of the enzyme in the soluble fractions of the sonicated cells. Afterwards the enzyme was purified and used in assays to show its functionality and determine the rate of its activity.
Expression in E.coli
Western blot of the soluble fraction of Arctic Express strain showing expression of all Ancestral reconstruction mutants. The PageRuler Plus prestained protein ladder was used and labelled with the corresponding sizes. The negative control is in lane 1. WT PETase is in lane 2. Ancestral Reconstruction Mutant 1 is in lane 3. Ancestral Reconstruction Mutant 2 is lane 4. Ancestral Reconstruction Mutant 3 is lane 5. Ancestral Reconstruction Mutant 4 is lane 6.
Purification graphs
Nickel Affinity Chromatography
Nickel affinity trace showing the elution of the protein from the column with an increase in Imidazole concentration
Conclusions
Although we were able to express soluble protein in E.coli and purify it using Nickel Affinity Chromatography we were unable to purify enough from the Size exclusion chromatography to characterise the enzyme using the activity assays.
Sequence and Features
- 10INCOMPATIBLE WITH RFC[10]Illegal PstI site found at 433
- 12INCOMPATIBLE WITH RFC[12]Illegal PstI site found at 433
- 21COMPATIBLE WITH RFC[21]
- 23INCOMPATIBLE WITH RFC[23]Illegal PstI site found at 433
- 25INCOMPATIBLE WITH RFC[25]Illegal PstI site found at 433
- 1000COMPATIBLE WITH RFC[1000]
| None |