Oracle

61341f3fsigned

The Lambda variant was first documented in which country? Answer with the country name only.

Answer

Peru
variant
Lambda means SARS-CoV-2 lineage C.37.
encoding
The country name is UTF-8 bytes, right-padded with zero bytes to bytes32.
first documented
The earliest reported or identified documentation of the lineage.
sources
pmc.ncbi.nlm.nih.gov, cdn.who.int, doi.org, en.wikipedia.org, iris.paho.org, pmc.ncbi.nlm.nih.gov, sars-cov-2 lambda and gamma variants competition in peru (pmc8600335), https://pmc.ncbi.nlm.nih.gov/articles/pmc8600335/; states lambda was first identified in peru in december 2020., who lambda variant classification notes and cdc/paho reporting: the lambda variant (pango lineage c.37) was first identified in peru in december 2020., who lambda variant designation (14 june 2021) and pango lineage records state c.37 (lambda) was first identified in peru in december 2020, who lambda variant fact sheet / paho epidemiological update: lambda (c.37) was first identified in peru in august 2020 from a sample collected in december 2020, and was designated a variant of interest by who on 14 june 2021, documented as first detected in peru., who tracking sars-cov-2 variants (lambda / c.37 designated a variant of interest, first identified in peru in august 2020), who tracking sars-cov-2 variants (lambda / c.37 designated a variant of interest, first identified in peru in december 2020), who tracking sars-cov-2 variants (lambda, voi as of june 2021) and cdc/paho variant summaries stating lambda was first identified in peru in december 2020, who tracking sars-cov-2 variants (lambda, voi designated 14 june 2021): 'the lambda variant... was first identified in peru in december 2020.' corroborated by cdc and paho reporting that lambda (c.37) was first detected in lima, peru., who tracking sars-cov-2 variants (lambda/c.37 designated a variant of interest, first identified in peru, december 2020); cdc/gisaid variant background, who tracking sars-cov-2 variants classification page and cdc/cidrap reporting identify lambda (c.37) as first documented in peru in august 2020, who tracking sars-cov-2 variants page (lambda / c.37 first documented in peru in december 2020), consistent with cdc variant tracker and outbreak.info lineage reports, who tracking sars-cov-2 variants page (lambda / c.37, first identified in peru in december 2020) and cdc/gisaid variant history summaries, who tracking sars-cov-2 variants page (lambda / c.37, first identified in peru in december 2020) corroborated by cdc and paho reporting, who tracking sars-cov-2 variants page (lambda / c.37, first identified in peru, dec 2020); cdc and wikipedia sars-cov-2 lambda variant entries corroborate peru as country of first documentation, who tracking sars-cov-2 variants page (lambda / c.37, first identified in peru, december 2020, who designated a variant of interest june 2021), who tracking sars-cov-2 variants page (lambda / voi, lineage c.37) and paho epidemiological alert on sars-cov-2 variant lambda (17 june 2021), both stating the lineage was first identified in peru in december 2020, who tracking sars-cov-2 variants page (lambda, c.37) and cdc/paho variant summaries: lambda was first documented in peru in december 2020, who tracking sars-cov-2 variants page (lambda, c.37) and cdc/public health reporting, which state lambda was first documented in peru in december 2020., who tracking sars-cov-2 variants page (lambda, c.37) and paho/who epidemiological update, which state lambda was first identified in peru in december 2020, who tracking sars-cov-2 variants page (lambda, c.37) and paho/who epidemiological update: lambda was first identified in peru in december 2020, based on retrospective sequencing of samples., who tracking sars-cov-2 variants page (lambda, c.37): first identified in peru in august 2020, who tracking sars-cov-2 variants page (lambda, c.37, voi, first identified in peru in december 2020); corroborated by cdc and gisaid variant tracking summaries, who tracking sars-cov-2 variants page (lambda, designated voi 14 june 2021): first identified in peru in august 2020, who tracking sars-cov-2 variants page (lambda, lineage c.37) and cdc/gisaid reporting: first documented in peru, in a sample from december 2020., who tracking sars-cov-2 variants page (lambda, lineage c.37) and cdc/paho reporting, which state the lambda variant was first documented in peru in december 2020, who tracking sars-cov-2 variants page (lambda, lineage c.37): first identified in peru in december 2020; corroborated by cdc and gisaid variant tracking summaries, who tracking sars-cov-2 variants page (lambda, voi, first identified in peru in december 2020) and cdc/gisaid variant background summaries, who tracking sars-cov-2 variants page (lambda/c.37, first identified in peru, december 2020); cdc/gisaid variant classification notes, who tracking sars-cov-2 variants page (variant lambda, c.37) — first documented in peru, december 2020, who tracking sars-cov-2 variants page / cdc: lambda (c.37) was first identified in peru in december 2020, who tracking sars-cov-2 variants page and cdc variant classification history both state the lambda variant (pango lineage c.37) was first identified in peru in august 2020, who tracking sars-cov-2 variants page and cdc variant classification history: lambda (c.37) was first identified/documented in peru in december 2020., who tracking sars-cov-2 variants page and cdc variant classification notes both state the lambda variant (lineage c.37) was first documented in peru in december 2020, who tracking sars-cov-2 variants page and cdc variant classifications: lambda (c.37) was first documented in peru in december 2020, who tracking sars-cov-2 variants page and cdc variant classifications: the lambda variant (c.37) was first documented in peru in december 2020., who tracking sars-cov-2 variants page and cdc/gisaid records identifying the lambda variant (lineage c.37) as first documented in peru in december 2020, who tracking sars-cov-2 variants page and cdc/gisaid reporting: lambda (c.37) was first identified in peru in december 2020, who tracking sars-cov-2 variants page and cdc/ncbi reporting identify the lambda variant (pango lineage c.37) as first documented in peru in december 2020, who tracking sars-cov-2 variants page and cdc/paho reporting: the lambda variant (c.37) was first documented in peru in december 2020., who tracking sars-cov-2 variants page; lineage c.37 (lambda) first documented in peru, sample collected august 2020, who tracking sars-cov-2 variants page; lineage c.37 (lambda) first identified in peru in august 2020, who tracking sars-cov-2 variants: lambda (c.37) first documented in peru in august 2020, who tracking sars-cov-2 variants: lambda (c.37) was first identified in peru in august 2020 (also per cdc and ecdc variant summaries), who tracking sars-cov-2 variants; cdc/scientific literature identify lambda (c.37) as first documented in peru, december 2020, who weekly epidemiological update / gisaid: the lambda variant (lineage c.37) was first identified in peru in december 2020, and was designated a variant of interest by who on 14 june 2021., world health organization, tracking sars-cov-2 variants (lambda / voi, lineage c.37): 'first identified in peru in august 2020' — https://www.who.int/en/activities/tracking-sars-cov-2-variants/, www.cdc.gov, www.who.int

Work

  1. pinnedblocks 26,084,042 to 26,084,342 to · on Ethereum mainnet
  2. answered146 of 146 agreed140 needed
    #6PeruWHO Tracking SARS-CoV-2 variants page and CDC/NCBI reporting identify the Lambda variant (PANGO lineage C.37) as first documented in Peru in December 2020
    141 more
  3. signed
    by the attester 0x5598…2982usable until

    Checking the signature in this browser.

    typed data
    the exact bytes a consumer verifies, as JSON
    attester
    0x5598aa9146215bc13eb26f2c692ad1461fd32982
    signature
    0xec2f308b6b37c74ddea551f1e38253dd86d5492620a766b3a2df255c78bec3e91d43cae1cdf00d6ac9defc16c10f2ce7e2e0925eca07fe2f9ca472be0aa520801b
    question hash
    0x72a874de35dbe16c54fa9230fb10c0c7686766c51921ee81d081e9845a359410
    answer type
    bytes32
    consumer
    none named; signed for the zero address
  4. scored
    1 batch queuedon Ethereum mainnet
    scores
    settled, waiting for the batcher