Research module E

Systemic Dependencies

The parties and systems each asset depends on: administrators, upgrade authorities, custodians, oracle providers, bridges, settlement and shared infrastructure. Every relationship is verified, documented only, or unresolved, and shows the exact statement it rests on. A dependency is a fact about structure, not a finding about security.

Last collection run 23 Oct 2026, 11:37 UTC · 2026-10-23T113712Z-research

Relationships
19
Across 5 assets
Verified
0
Confirmed onchain
Documentation only
13
Issuer source, not confirmed
Unresolved
6
Link to the asset not established
Shared counterparties
0
Behind two or more assets
Links between assets
1
Counterparty is itself indexed

Statuses

Three statuses, never merged

A relationship is published only while the statement behind it is found in the issuer's file at a pinned commit. Documentation is never presented as confirmation, and an unresolved link is never presented as a documented one.

Verified
Documented, and confirmed onchain: the counterparty's address holds the authority at the block read.
Documentation only
Stated for this asset in an issuer-published source, found verbatim at a pinned commit. Not independently confirmed.
Unresolved
Documented for a related system, but its link to this asset is not established — or the statement behind it is no longer in the source.

By asset

Documented relationships by dependency group

Each cell counts the relationships in that group by status. A dash means none was documented in the sources read — not that the asset has no such dependency.

For each asset, in published order, the number of documented relationships in each dependency group, by status.
AssetIssuers and administratorsUpgrade authoritiesCustodiansOracle providersBridges and settlementShared infrastructure
JTRSYCentrifugeJTRSY, Issuers and administrators: 2 unresolvedJTRSY, Upgrade authorities: none documented in the sources readJTRSY, Custodians: none documented in the sources readJTRSY, Oracle providers: none documented in the sources readJTRSY, Bridges and settlement: 4 unresolvedJTRSY, Shared infrastructure: none documented in the sources read
TBILLOpenEdenTBILL, Issuers and administrators: none documented in the sources readTBILL, Upgrade authorities: 1 documentation onlyTBILL, Custodians: none documented in the sources readTBILL, Oracle providers: 1 documentation onlyTBILL, Bridges and settlement: 1 documentation onlyTBILL, Shared infrastructure: none documented in the sources read
USTBSuperstateUSTB, Issuers and administrators: 1 documentation onlyUSTB, Upgrade authorities: 1 documentation onlyUSTB, Custodians: none documented in the sources readUSTB, Oracle providers: none documented in the sources readUSTB, Bridges and settlement: none documented in the sources readUSTB, Shared infrastructure: none documented in the sources read
USTBLSpikoUSTBL, Issuers and administrators: 2 documentation onlyUSTBL, Upgrade authorities: none documented in the sources readUSTBL, Custodians: none documented in the sources readUSTBL, Oracle providers: 1 documentation onlyUSTBL, Bridges and settlement: none documented in the sources readUSTBL, Shared infrastructure: 1 documentation only
OUSGOndo FinanceOUSG, Issuers and administrators: none documented in the sources readOUSG, Upgrade authorities: none documented in the sources readOUSG, Custodians: none documented in the sources readOUSG, Oracle providers: none documented in the sources readOUSG, Bridges and settlement: none documented in the sources readOUSG, Shared infrastructure: none documented in the sources read
USDYOndo FinanceUSDY, Issuers and administrators: none documented in the sources readUSDY, Upgrade authorities: none documented in the sources readUSDY, Custodians: 1 documentation onlyUSDY, Oracle providers: 1 documentation onlyUSDY, Bridges and settlement: 1 documentation onlyUSDY, Shared infrastructure: 1 documentation only
WTGXXWisdomTreeWTGXX, Issuers and administrators: none documented in the sources readWTGXX, Upgrade authorities: none documented in the sources readWTGXX, Custodians: none documented in the sources readWTGXX, Oracle providers: none documented in the sources readWTGXX, Bridges and settlement: none documented in the sources readWTGXX, Shared infrastructure: none documented in the sources read
BENJIFranklin TempletonBENJI, Issuers and administrators: none documented in the sources readBENJI, Upgrade authorities: none documented in the sources readBENJI, Custodians: none documented in the sources readBENJI, Oracle providers: none documented in the sources readBENJI, Bridges and settlement: none documented in the sources readBENJI, Shared infrastructure: none documented in the sources read
BUIDLSecuritizeBUIDL, Issuers and administrators: none documented in the sources readBUIDL, Upgrade authorities: none documented in the sources readBUIDL, Custodians: none documented in the sources readBUIDL, Oracle providers: none documented in the sources readBUIDL, Bridges and settlement: none documented in the sources readBUIDL, Shared infrastructure: none documented in the sources read
USYCCircleUSYC, Issuers and administrators: none documented in the sources readUSYC, Upgrade authorities: none documented in the sources readUSYC, Custodians: none documented in the sources readUSYC, Oracle providers: none documented in the sources readUSYC, Bridges and settlement: none documented in the sources readUSYC, Shared infrastructure: none documented in the sources read

Concentration

Relationships whose counterparty is itself an asset in the index, derived from the published relationships.

Concentration

Shared dependencies

Counterparties documented behind two or more assets in the index.

No shared counterparty is documented in the sources read

No single counterparty is documented behind two or more indexed assets in the files checked. That describes the sources read; it is not evidence that no shared dependency exists.

Evidence

Every relationship, with the statements behind it

Each quote is matched in the file at the commit linked, with only whitespace normalised. JSON values are matched at the path shown.

Showing 19 of 19 relationships

Each documented dependency: the asset, the counterparty and its role, the relationship status, and the exact statements it rests on.
AssetCounterpartyStatusEvidence
JTRSYAdministratorCentrifuge protocolAdmin0x9711730060C73Ee7Fcfe1890e8A0993858a7D225 (opens explorer in a new tab)UnresolvedThe protocol administrator documented for Centrifuge V3 on Ethereum. Whether JTRSY is governed by V3 contracts is an open question from the 14 Oct 2026 revalidation, so its link to JTRSY is unresolved.
JTRSYAdministratorCentrifuge opsAdmin0xd21413291444C5c104F1b5918cA0D2f6EC91Ad16 (opens explorer in a new tab)UnresolvedThe operations administrator documented for Centrifuge V3 on Ethereum. Whether JTRSY is governed by V3 contracts is an open question from the 14 Oct 2026 revalidation, so its link to JTRSY is unresolved.
JTRSYBridge or messagingLayerZero0x1a44076050125825900e736c501f859c50fE728c (opens explorer in a new tab)UnresolvedA cross-chain messaging adapter documented for Centrifuge protocol V3 on Ethereum. Whether JTRSY is governed by V3 contracts is an open question from the 14 Oct 2026 revalidation, so the relationship to JTRSY is unresolved.
JTRSYBridge or messagingAxelar0x4F4495243837681061C4743b74B3eEdf548D56A5 (opens explorer in a new tab)UnresolvedA cross-chain messaging adapter documented for Centrifuge protocol V3 on Ethereum. Whether JTRSY is governed by V3 contracts is an open question from the 14 Oct 2026 revalidation, so its link to JTRSY is unresolved.
JTRSYBridge or messagingChainlink CCIP0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D (opens explorer in a new tab)UnresolvedA cross-chain messaging adapter documented for Centrifuge protocol V3 on Ethereum. Whether JTRSY is governed by V3 contracts is an open question from the 14 Oct 2026 revalidation, so its link to JTRSY is unresolved.
JTRSYBridge or messagingHyperlane0xc005dc82818d67AF737725bD4bf75435d065D239 (opens explorer in a new tab)UnresolvedA cross-chain messaging adapter documented for Centrifuge protocol V3 on Ethereum. Whether JTRSY is governed by V3 contracts is an open question from the 14 Oct 2026 revalidation, so its link to JTRSY is unresolved.
TBILLUpgrade authorityOpenEden TimelockController0x8Bb125BA9A0429583dfc3FCF295636A6cC8e9dc0 (opens explorer in a new tab)Documentation onlyThe README states the timelock governs upgrades and privileged actions; the deployed-addresses file gives its Ethereum address. Its delay and proposers are read onchain in Privileged Access.
TBILLOracle or price sourceOpenEden T-Bill NAV price feed (issuer-operated)0xCe9a6626Eb99eaeA829D7fA613d5D0A2eaE45F40 (opens explorer in a new tab)Documentation onlyThe README calls it TBillPriceOracle and the deployed-addresses file TBillPriceFeed; the address is from the latter. Who updates the price is not stated in the sources read.
TBILLSettlementUSYC instant redemptionDocumentation onlyUSYC is itself an asset in this index, so this documents a link between two indexed assets: TBILL's instant-redemption path relies on USYC. The helper's address and how much redemption flows through it are not stated in the sources read.
USTBUpgrade authoritySuperstate ProxyAdmin0xCb8d325C0Af19697B8454481602097f93aa9040F (opens explorer in a new tab)Documentation onlyThe manifest names this ProxyAdmin and the deployment guide upgrades through a proxy admin. That it is the EIP-1967 admin of the USTB proxy, and who owns it, are read onchain in Privileged Access.
USTBKey managementFireblocksDocumentation onlyThe deployment guide executes upgrades from Fireblocks. Fireblocks is an institutional wallet provider; the signing policy behind the admin account is not public.
USTBLAdministratorSpiko Permission ManagerDocumentation onlyThe deployment cache names a `manager` contract; that it is this Permission Manager is not stated in the sources read, so no address is recorded here.
USTBLAdministratorSpiko admin SafeDocumentation onlyThe README's worked example is the Arbitrum One deployment and does not give the Ethereum admin Safe's address. Its owners and threshold need to be read onchain.
USTBLOracle or price sourceSpiko oracle contract (implements Chainlink's AggregatorV3Interface)0x021289588cd81dC1AC87ea91e91607eEF68303F5 (opens explorer in a new tab)Documentation onlyImplementing Chainlink's interface does not make Chainlink the price source; the sources read do not say who sets the price.
USTBLSoftware libraryOpenZeppelin ContractsDocumentation onlyA shared software library: a defect in it would reach every contract built on it.
USDYCustodianThird-party custodians (not named in the source)Documentation onlyThe source documents that deposits go to third-party custodians but does not name them.
USDYOracle or price sourceTrusted account setting subscription and redemption pricesDocumentation onlyThe exchange rate for each subscription is set by an externally owned account the README calls trusted; it is not named in the source.
USDYSettlementUSDCDocumentation onlySubscriptions and redemptions settle in USDC.
USDYCompliance screeningChainalysis sanctions oracle0x40C57923924B5c5c5455c48D93317139ADDaC8fb (opens explorer in a new tab)Documentation onlyEvery USDY transfer checks this list, per the README. The README is in a repository that does not list the deployed USDY address, so that the deployed token reads this oracle is documented, not verified onchain.

Methodology

Method and limitations

Important context

Scores measure publicly observable technical controls and documentation at the stated snapshot date. They are not smart-contract audits, credit ratings, investment recommendations, or assessments of an organization's complete security posture.