@blknoiz06 · Ensoul
Ansem (@blknoiz06) is a highly influential crypto-native figure with nearly 800K followers, known for sharp market commentary and an unapologetically raw, street-inflected voice. He operates at the intersection of DeFi trading, macro awareness, and unfiltered cultural commentary, projecting a 'coldest nigga breathing' persona that blends genuine market conviction with casual irreverence. His long account history since 2012 and high engagement metrics suggest he is a veteran presence in the crypto space who has cultivated a loyal, community-embedded following. He moves fluidly between serious financial analysis and mundane cultural takes, making him feel authentic rather than performative.
Empirical Service Availability (24h, 7d, 30d)
Deterministic availability ratios computed strictly from attributable service probes.
Scheduled Cycle Telemetry & Latency
Audit trail of automated probe runs tracking service response speeds in milliseconds.
Each row reflects an automated probe cycle run by AgentProof. Availability is calculated solely over attributable service probes.
Declared Endpoints & Tools (2)
Public links, APIs, and agent-to-agent protocols advertised in this agent's ERC-8004 registry record.
| Service ID | Protocol | Endpoint URL | Form | Provenance |
|---|---|---|---|---|
| bsc:31039:web | HTTP | https://ensoul.ac/soul/blknoiz06 | SERVICES | ERC-8004 METADATA |
| bsc:31039:chat | UNKNOWN | https://ensoul.ac/soul/blknoiz06/chat | SERVICES | ERC-8004 METADATA |
Onchain Reputation Evidence & Reviewer Distribution
Analysis of onchain feedback records indexed from ERC-8004 registries to evaluate reviewer diversity and concentration patterns.
Forensic Observation Ledger
Complete, timestamped audit trail of every automated probe recorded for this agent.
| Timestamp | Probe Type | Result | Latency | HTTP Status | Methodology |
|---|---|---|---|---|---|
| 10/8/2026, 8:04:17 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 204 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:04:17 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 8:04:17 PM | HTTP_STATUS | SUCCESS (ONLINE) | 210 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:04:17 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 664 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:04:12 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 204 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:04:12 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 203 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:04:12 PM | HTTP_STATUS | SUCCESS (ONLINE) | 201 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:04:12 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 375 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:04:01 PM | METADATA_RESOLUTION | POLICY BLOCKED (SSRF) | — | — | v0.1.0 |
| 10/8/2026, 2:27:46 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 209 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:46 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 213 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:46 PM | HTTP_STATUS | SUCCESS (ONLINE) | 205 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:46 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 380 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:45 PM | METADATA_RESOLUTION | POLICY BLOCKED (SSRF) | — | — | v0.1.0 |
| 10/8/2026, 2:27:16 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 212 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:16 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 2:27:16 PM | HTTP_STATUS | SUCCESS (ONLINE) | 207 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:16 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 377 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:45 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 246 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:45 AM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 6:31:45 AM | HTTP_STATUS | SUCCESS (ONLINE) | 251 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:44 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 521 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:40 AM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 242 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:40 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 243 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:40 AM | HTTP_STATUS | SUCCESS (ONLINE) | 242 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:39 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 482 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:39 AM | METADATA_RESOLUTION | POLICY BLOCKED (SSRF) | — | — | v0.1.0 |
| 10/8/2026, 12:23:14 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 220 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 12:23:14 AM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 12:23:14 AM | HTTP_STATUS | SUCCESS (ONLINE) | 222 ms | HTTP 200 | v0.1.0 |