LEI 70DNWEAINTGFO4DMV441 · Toronto, CA-ON, CA · one of 3,428,529 GLEIF LEI records on the directory
70DNWEAINTGFO4DMV441Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
8888RA999999Verbatim from the GLEIF LEI Golden Copy record for this LEI (fetched 2026-07-13). Fields the golden copy does not publish are omitted — never guessed. The registration authority name is GLEIF's own list entry for the record's code.
NO_KNOWN_PERSONNO_KNOWN_PERSON254900013HLB0XKF1J63 · ACTIVE · from 2021-10-072549005M2S1OO7W6U250 · ACTIVE · from 2015-03-30254900DKN2GOSG0ICG28 · ACTIVE · from 2013-02-06254900INE09PWZJG7524 · ACTIVE · from 2013-03-13254900KKZI8Q0NBQID69 · ACTIVE · from 2023-04-19254900LHTL2F56F36E06 · ACTIVE · from 2014-05-22254900OVLJUIEVETLQ91 · ACTIVE · from 2023-08-30254900V02NNTYS9A7H67 · ACTIVE · from 2024-07-315493002SWYWP0UV2HE91 · ACTIVE · from 2016-09-305493005KEXDG6TMT0972 · ACTIVE · from 2019-01-232549001ZK3PD0MV72633 · ACTIVE · from 2013-03-1325490040NLNTT8SY0R21 · ACTIVE · from 2022-09-122549004H3YJ0739MKW32 · ACTIVE · from 2013-03-13254900515NL66CC2OB24 · ACTIVE · from 2013-03-132549005NSON5O3W0DX74 · ACTIVE · from 2023-04-192549006YQDEOXC5X0C32 · ACTIVE · from 2013-03-13254900757MORPFNK3Z05 · ACTIVE · from 2013-03-132549007D03C84HY32061 · ACTIVE · from 2022-06-172549007K16E79XAHHW86 · ACTIVE · from 2013-03-132549007XLDP1NMX4A781 · ACTIVE · from 2022-09-13Verbatim from GLEIF's Level 2 relationship and reporting-exception files (CC0). Each link is an LEI pair GLEIF publishes; names come from this directory and never create a link. No ownership share or value is stated. Complete refresh: 2026-10-20.
CPPBCATTXXX · CACross-registry identity (LiNx) for this LEI and BIC
Verbatim rows from GLEIF's certified BIC-to-LEI mapping file (bic-registry dataset) — a certified correspondence between this LEI and SWIFT BIC codes, not an inference.
None loaded for this LEI yet. CNXT has no proven complete refresh of GLEIF's ISIN-to-LEI file yet, so this is not a negative.
Indicative correspondences from the CNXT registry-linkage layer (SEC EDGAR / BIC / FedNow families) — asserted only where the registries' own published identifiers agree; certified BIC↔LEI rows appear in their own panel above.
#://CNXTTHePeoPLe/ORG/GLEIF/70DNWEAINTGFO4DMV441web+usd://org-gleif-70dnweaintgfo4dmv441 — 1-of-1 edition · universal linkweb+usd://org-gleif-70dnweaintgfo4dmv441 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/70DNWEAINTGFO4DMV441 — JSONThis record is addressable on the CNXT network. Its web+usd:// edition address doubles as the record's settlement rail — reserved, with no holder and no balance, until the 1-of-1 edition is minted. The JSON endpoint returns the same org-level fields rendered here; person-level registry contacts are never exposed on this public tier.
Stage is derived live from real rows — directory row (Addressable), source-published domain or cross-registry links (Enriched), tokenized_entities registration (Reserved) and holder (Minted), CNXTCLOUD binding (Connected), settled transfers on the rail (Transacting). Nothing here is simulated.
Organization records are represented in CNXT — not operated by the listed entities. Registry identity is verbatim from the source registry's public data; CNXT issues only the disclosed token attributes and never implies affiliation or endorsement.