Research module C

Security Events

Administrative changes decoded from each asset's contracts — roles, ownership, upgrades, proxy admins, pauses — and daily mints and burns. Every event is administrative unless researchers have reviewed it against a published bar; an event's name is never evidence of an incident.

Last event scan attempted 23 Oct 2026, 11:37 UTC · 2026-10-23T113712Z-research

Events published
0
Decoded from contract logs
Contracts scanned
0 / 22
With at least one completed scan
Reviewed classifications
0
Above administrative
Confirmed incidents
0
Two reviewers, independent sources
Mint and burn days
0
Daily totals per token
Last block scanned
—
No scan has completed

Classification

Three tiers, each with a published bar

Administrative events, suspicious observations and confirmed incidents are kept apart throughout. An event moves up a tier only when the bar for that tier is met; until then it stays where it is.

  1. 1

    Administrative

    A decoded administrative event. The default for every event; it says what happened onchain and nothing about intent.

    Bar: Every decoded event, by default. Code never assigns anything else.

  2. 2

    Suspicious observation

    Flagged by a named researcher after review, with at least one cited source. An open question, not a finding of wrongdoing.

    Bar: An approved review by a named researcher, citing at least one source.

  3. 3

    Confirmed incident

    Confirmed by two researchers on independent sources, at least one of them not a block explorer.

    Bar: Approval by two different researchers, with sources on at least two independent hosts — at least one of them not a block explorer.

F · Historical Security IncidentsCase studies of past incidents, researched from public forensic reporting and issuer statements, are kept in their own dataset. They are not decoded events, are not counted in this module's figures, and say nothing about which contracts these scans have covered.

Latest verified changes

Most recent onchain changes

The ten most recent decoded events, each verified at its block, transaction and log index.

No event has been collected. The last scan attempt could not reach the chain for any contract; see scan coverage below. Nothing is shown in place of data that was not read.

Data table

All events

Search and filter every published event. Each links to its transaction on a public explorer.

Showing 0 of 0 events

No events have been collected

No event scan has reached the chain yet. The coverage table below shows each contract's last scan attempt and why it did not complete.

Scan coverage

What was scanned, and what was not

An empty event list means nothing unless the scan behind it completed. Each contract's last attempt is shown with the block range its completed scans cover.

Each contract scanned for events: last attempt, outcome, and the block range completed scans cover.
AssetContractLast attemptBlocks covered
JTRSYToken contract0x8c213ee79581Ff4984583C6a801e5263418C4b86 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
TBILLController0x377de6729507Bb0E56E0AAC666bd8522E4A3fe41 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
TBILLKycManager0x51Be497AcEd1a2C19f6151064301e356B020D947 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
TBILLTimelockController0x8Bb125BA9A0429583dfc3FCF295636A6cC8e9dc0 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
TBILLFeeManager0x99C913B3cBDdCFC7eD49Ff19B00704286a4B3b6B (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
TBILLPartnership0xc0952c8ba068c887B675B4182F3A65420D045F46 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
TBILLTBillPriceFeed0xCe9a6626Eb99eaeA829D7fA613d5D0A2eaE45F40 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
TBILLToken contract0xdd50C053C096CB04A3e3362E2b622529EC5f2e8a (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USTBAllowListProxy0x42d75C8FdBBF046DF0Fe1Ff388DA16fF99dE8149 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USTBToken contract0x43415eB6ff9DB7E26A15b704e7A3eDCe97d31C4e (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USTBProxyAdmin0xCb8d325C0Af19697B8454481602097f93aa9040F (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USTBLoracle-USTBL0x021289588cd81dC1AC87ea91e91607eEF68303F5 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USTBLmanager0x344278aff344d6fb960705dc18a4912221608472 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USTBLforwarder0x42DB5A5AF4D82E8eD42405dfA37278c360d923C3 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USTBLredemption0xDA5599f04e9b437C8394b0c2BC68B502A66ebFe8 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USTBLToken contract0xe4880249745eAc5F1eD9d8F7DF844792D560e750 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
OUSGToken contract0x1B19C19393e2d034D8Ff31ff34c81252FcBbee92 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USDYToken contract0x96F6eF951840721AdBF46Ac996b59E0235CB985C (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
WTGXXToken contract0x1feCF3d9d4Fee7f2c02917A66028a48C6706c179 (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
BENJIToken contract0x408A634B8a8f0dE729B48574a3a7Ec3fE820B00A (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
BUIDLToken contract0x7712c34205737192402172409a8F7ccef8aA2AEc (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed
USYCToken contract0x136471a34f6ef19fE571EFFC1CA711fdb8E49f2b (opens explorer in a new tab)Provider unavailable23 Oct 2026, 11:37 UTC · No HTTP response: fetch failed (Request was cancelled.)None completed

Mint and burn activity

Daily mints and burns

Transfers from and to the zero address on each token, totalled by UTC day in raw token units. Supply movement onchain says nothing about the offchain assets behind it.

No mint or burn has been collected.

Methodology

Method and limitations

Events decoded

Role granted
RoleGranted(bytes32,address,address)
Role revoked
RoleRevoked(bytes32,address,address)
Role admin changed
RoleAdminChanged(bytes32,bytes32,bytes32)
Ownership transferred
OwnershipTransferred(address,address)
Ownership transfer started
OwnershipTransferStarted(address,address)
Implementation upgraded
Upgraded(address)
Proxy admin changed
AdminChanged(address,address)
Beacon upgraded
BeaconUpgraded(address)
Paused
Paused(address)
Unpaused
Unpaused(address)

Limitations

  • Only these standard event signatures are decoded. A contract that emits authority changes under other signatures will show fewer events than it has.
  • Contracts are scanned when the index or an issuer manifest names them. Authority held through an undocumented contract is not scanned.
  • Scans stop a confirmation depth short of the chain head: 64 blocks on Ethereum, 256 on Polygon.
  • A classification describes a researcher's reviewed judgement at a date, with its sources. Mechanical flags that prompt a review are never published.
  • The tiers are never merged or ranked against each other: an administrative event is not a lesser incident, and a suspicious observation is not a finding of wrongdoing.

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.