Composite

Part:BBa_K4417018

Designed by: Jiaying Zou   Group: iGEM22_UCL   (2022-10-12)


CuO-RBS-ureABC-ureEFG-rrnB T1 Native Operon Sequence

Description

This part was created by cloning the master plasmid (BBa_K4417017) with the coding sequence of ureEFG (BBa_K4417016). This plasmid retained the native urease operon sequence under a novel cumate inducible promoter (BBa_K4417007). The Type IIS backbone also contains a strong RBS (BBa_K4417008) and an rrnB T1 terminator (BBa_K4417011).

Figure 1:Urease native operon sequence from Sporosarcina pasteurii.

Usage and Biology

  • This part can be transformed in both B. subtilis and E. coli.
  • Inducer: p-isopropyl benzoate (cumate).
  • Cumate is non-toxic to the host. In our experiment, we induced the urease expression with 50 μM cumate.
  • E. coli ori is a pMB1 derivative
  • B. sub ori is unknown
  • The copy number of this plasmid in B. subtilis and E. coli is unknown.
  • NdeI and SacI restriction digest can be used to change the promoter.

Cloning Strategy

Golden Gate Assembly was used to assemble the master plasmid with TU2B.

Figure 2:CuO-RBS-ureABC-ureEFG-rrnB T1 Terminator native operon sequence.

Method

We used Golden Gate Assembly to clone the ureEFG part into the master plasmid, following NEB’s Golden Gate Assembly Protocol (https://international.neb.com/protocols/2015/03/04/golden-gate-assembly-protocol-for-using-neb-golden-gate-assembly-mix-e1600) using BsaI restriction site.

Golden Gate Assembly protocol:

  • The following reagents were assembled in a thin-walled PCR tube.
    • 0.5 μL T4 DNA Ligase
    • 2 μL of 10X T4 Ligase buffer
    • 0.5 μL BsaI enzyme
    • 100ng of receiver plasmid
    • Equimolar amounts of inserts
    • MilliQ for a total volume of 20 μL
  • Mixed gently.
  • Set up the thermocycler program.


Hbhbhbh.png


Figure 3:E. coli plates transformed with urease native operon plasmid. (a), (b) transformed with no bME. (c), (d) transformed with 24mM bME.

Figure 3 verified that bME could be used to improve the transformation efficiency to a certain extent. After successful transformation, colonies were picked, grown, and the plasmid isolated. The isolated plasmid was checked by SapI diagnostic digest. 5 μL uncut and 10 μL cut samples were loaded on a 1% agarose gel to check the band size. From Figure 4, expected bands can be observed around 6880bp and 4789bp.

Figure 4:Restriction digest of urease native operon plasmid. 1: DNA ladder, 2,4,6,8: nature operon plasmid cut with SapI, 3,5,7,9: nature operon plasmid uncut, 10: TU1 cut with SapI, 11: TU1 uncut.

Characterization

In order to observe whether the ureABCEFG genes were successfully expressed in DH5-α, we analysed our the soluble cell lysate by SDS PAGE. The cell pellet obtained from the 10 mL culture was resuspended in Tris Buffer Saline. Once resuspended, the sample was lysed using sonication. Following sonication, the samples were centrifuged to separate the soluble and insoluble fractions from the whole cell lysate. 60 μL from each sample were taken and boiled for 10 min with Laemmli buffer to denature the sample.

Figure 5:SDS PAGE of native urease operon in E. coli. All the strains were grown in LB medium, and only the soluble fraction was loaded; 1: PageRuler Protein Ladder, 2: WT E. coli cell lysate, 3: WT E. coli soluble fragment, 4: SDM1,3 TU1 cell lysate, 5: SDM1,3 TU1 soluble fragment, 6: pCT5c TU1 cell lysate, 7: pCT5c TU1 soluble fragment, 8: SDM1,3 TU2 cell lysate, 9: SDM1,3 TU2 soluble fragment, 10: pCT5c TU2 cell lysate, 11: pCT5c TU2 soluble fragment, 12: pCT5c full urease operon cell lysate, 13: pCT5c full urease operon soluble fragment, 14: pCT5c native urease operon cell lysate, 15: pCT5c native urease operon soluble fragment.

From Figure 5, it could be concluded that the urease was successfully produced since the correct bands are observed in both the soluble and insoluble fragment. ureC was identified at 61.5 kDa, and ureF was identified at 24.9 kDa.

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    INCOMPATIBLE WITH RFC[21]
    Illegal BglII site found at 3592
    Illegal BamHI site found at 1
    Illegal XhoI site found at 4346
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    COMPATIBLE WITH RFC[25]
  • 1000
    COMPATIBLE WITH RFC[1000]


[edit]
Categories
Parameters
None