{"id":80507,"date":"2025-03-20T12:45:55","date_gmt":"2025-03-20T17:45:55","guid":{"rendered":"https:\/\/blog.familytreedna.com\/?p=80507"},"modified":"2026-03-13T15:41:52","modified_gmt":"2026-03-13T20:41:52","slug":"update-earliest-known-ancestor-mtdna-haplotree","status":"publish","type":"post","link":"https:\/\/blog.familytreedna.com\/es\/update-earliest-known-ancestor-mtdna-haplotree\/","title":{"rendered":"Update Your Earliest Known Ancestor to Strengthen the mtDNA Haplotree"},"content":{"rendered":"

[vc_row][vc_column width=”1\/1″][vc_column_text uncode_shortcode_id=”167838″]By: Roberta Estes<\/p>\n

Updating your Earliest Known Ancestor (EKA) information at FamilyTreeDNA helps improve mtDNA Discover\u2122, enhances genealogy research, and makes match connections more meaningful\u2014here\u2019s how you can contribute.<\/h2>\n

I\u2019ve been testing the newly released Updated mtDNA Haplotree<\/a> and mtDNA Discover haplogroup reports<\/a> and have some things to share with you.<\/p>\n

For anyone who has ever been involved with a major release that includes brand-new tools, you know that means that our research team has been neck deep in testing, refining and preparing.<\/p>\n

The new mtDNA Discover tool functions similarly to Y-DNA Discover<\/a>, but it\u2019s designed specifically for mitochondrial DNA (mtDNA) results<\/a>, helping testers explore their maternal line and understand their place on the haplotree.<\/p>\n

However, I\u2019ve noticed something you can help us with.<\/p>\n

What Are mtDNA Discover Time Tree Clusters?<\/h2>\n

I\u2019m using my husband Jim\u2019s kit for testing. On the existing tree, his mtDNA haplogroup was V, but with the Updated mtDNA Haplotree, it has been refined to V71b\u2014one of the thousands of new haplogroups added to the tree. His new mtDNA Discover V71b Time Tree now looks like this:[\/vc_column_text][vc_single_image media=”80513″ caption=”yes” media_lightbox=”yes” media_width_percent=”100″ lbox_caption=”yes” lbox_social=”yes” uncode_shortcode_id=”335745″][vc_column_text uncode_shortcode_id=”198429″]The problem? All those Earth globes with black arrows.<\/strong><\/p>\n

These globes indicate testers who did not provide location details for their EKA<\/strong> on their matrilineal line.<\/p>\n

You don\u2019t need an exact birthplace\u2014just selecting a country<\/strong> is better than leaving it blank. If all you know is the United States, Canada, or another broad region<\/strong>, that\u2019s still useful.<\/p>\n

The circles with flags<\/strong> indicate testers who have completed their EKA information<\/strong>, helping others identify potential geographic connections within their haplogroup or haplogroup subgroup.<\/p>\n

If you\u2019re a tester, it can be frustrating to have mtDNA matches but lack genealogy details to explore shared ancestry.<\/p>\n

How Updating Your EKA Helps Everyone<\/h3>\n

We need your help\u2014not just by updating your own EKA information, but by encouraging your matches to do the same<\/strong>.<\/p>\n

When testers leave this section blank, it creates challenges in understanding maternal ancestry and can lead to the misconception that mtDNA isn\u2019t useful. That then becomes a self-fulfilling prophecy\u2014if testers don\u2019t see value, they don\u2019t test, and valuable connections are lost.<\/p>\n

But here\u2019s the truth: Matching, mtDNA tools, and mtDNA Discover can be far more powerful when testers complete their EKA information<\/strong>\u2014and encourage their matches to do the same.<\/p>\n

It\u2019s a win-win.<\/strong> Feel free to share this blog with your matches<\/strong> in a polite email<\/strong>, asking them to update their EKA information<\/strong>.<\/p>\n

How the mtDNA Discover Match Time Tree Uses Your Self-Reported Information<\/h2>\n

One of the most exciting new features introduced alongside the Updated mtDNA Haplotree is the Match Time Tree<\/strong>. This tool helps mtFull Sequence testers<\/a> visualize their matches in clusters based on their maternal ancestry and how closely they relate to one another.[\/vc_column_text][vc_single_image media=”80514″ caption=”yes” media_lightbox=”yes” media_width_percent=”100″ lbox_caption=”yes” lbox_social=”yes” uncode_shortcode_id=”868554″][vc_column_text uncode_shortcode_id=”184634″]Above, you can see Jim\u2019s Match Time Tree\u2014and how much more insightful it would be if every tester had completed their EKA information.<\/p>\n

In this example, Jim\u2019s matches are grouped by haplogroup:<\/p>\n