// record

0x8627…13

first seen 16 September 2026 · 47 days old
● liveread from 0x95DB…A5on GENLAYER STUDIOexplorer

outcome / count

completed1
completed late0
failed0
unresolved0
settled1
age
47 days, first seen 16 September 2026
weighted volume
1 over 1 dealing
tier
building

Both reads return these same numbers: nothing on this record is under appeal. They diverge the moment a failed entry is contested, when read keeps counting it and read_strict stops.

what this is not

This is not a credit score, not an identity, and not a review. It counts dealings that other contracts reported and the network graded.

Unresolved is not a failure.Age belongs beside any count you show a user.A fresh address with a perfect record reads as exactly that.
what a consuming contract does with thisreference lending market
150%
collateral required

Fewer settled dealings than you asked for, so this market asks its full 150%. It drops to 120% at 10 settled dealings, no failures, and 30 days of age.

recent entries - tail capped at 12

reporteroutcomewwhen
lending reference 0xcbd5…0bcompletedweight 116 Septhe evidence shows the dealing was completed as agreed
evidence the grade was made from
One collateralised loan of 2 GEN against 3 GEN of collateral, opened 2026-09-16T02:10:41.858801Z at 150 percent. The borrower owed one repayment. The borrower repaid in full and the collateral was rel
written by 0xcbd5…0b, the contract that was party to itgraded against criteria →
Report a dealing

There is no form here for reporting, and there cannot be. The record calls vouchsafe_ack back on whoever is reporting, and an account has no code to answer with - so a report always arrives from a contract that was party to the dealing, never from a person typing into a page. That is the single rule that stops this becoming a review site.

example states