Back to Agents Directory
BNB CHAIN (56)TOKEN #31039ACTIVELY MONITOREDMETADATA RESOLVEDINDEXER (8004scan)

@blknoiz06 · Ensoul

bsc:31039
Reliability Passport
AUTONOMOUS MONITORING
100 retained observations

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.

Agent-provided metadata (not independently verified by AgentProof)
BNB Registry: 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
Metadata Link: data-uri (application/json)
First Tracked: Oct 8, 2026

Empirical Service Availability (24h, 7d, 30d)

Deterministic availability ratios computed strictly from attributable service probes.

Methodology & Formulas →
24H WindowSTRONG EVIDENCE
87.5%
Attributable Probes:28 / 32 passed
Attributable Failures:4
Median Latency:223ms
P95 Peak Latency:732ms
Methodology v0.1.0Formula
87.6%
Attributable Probes:78 / 89 passed
Attributable Failures:11
Median Latency:269ms
P95 Peak Latency:569ms
Methodology v0.1.0Formula
87.6%
Attributable Probes:78 / 89 passed
Attributable Failures:11
Median Latency:269ms
P95 Peak Latency:569ms
Methodology v0.1.0Formula
About Evidence Coverage: Sufficiency tiers (LIMITED, MODERATE, STRONG) describe the statistical depth of recorded empirical observations. It is not a safety or trust rating.

Scheduled Cycle Telemetry & Latency

Audit trail of automated probe runs tracking service response speeds in milliseconds.

Scheduled Cycle Uptime History12 cycles recorded
Total checks: 100Methodology

Each row reflects an automated probe cycle run by AgentProof. Availability is calculated solely over attributable service probes.

Cycle #12•Oct 8 08:04 PM
204ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #11•Oct 8 02:27 PM
212ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #10•Oct 8 06:31 AM
246ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #9•Oct 8 12:22 AM
222ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #8•Oct 7 08:29 PM
268ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #7•Oct 7 07:03 AM
251ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #6•Oct 7 12:57 AM
285ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #5•Oct 6 09:09 PM
294ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #4•Oct 6 04:10 PM
319ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #3•Oct 6 09:18 AM
249ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #2•Oct 6 02:26 AM
269ms87.5%
7 passed1 failed(8 attributable probes)
9 total pings
Cycle #1•Oct 5 10:23 PM
224ms100.0%
1 passed(1 attributable probes)
1 total pings
Observed Response Latency & Status89 attributable / 100 total pings
Measured Availability: 87.6%(78/89)
Median: 269ms
P95: 569ms
How calculated?
Hover over any probe bar above to view timestamp, latency, and response status. Green = Success, Red/Amber = Attributable Failure, Gray = Policy Excluded.

Declared Endpoints & Tools (2)

Public links, APIs, and agent-to-agent protocols advertised in this agent's ERC-8004 registry record.

Service IDProtocolEndpoint URLFormProvenance
bsc:31039:webHTTPhttps://ensoul.ac/soul/blknoiz06SERVICESERC-8004 METADATA
bsc:31039:chatUNKNOWNhttps://ensoul.ac/soul/blknoiz06/chatSERVICESERC-8004 METADATA

Onchain Reputation Evidence & Reviewer Distribution

Analysis of onchain feedback records indexed from ERC-8004 registries to evaluate reviewer diversity and concentration patterns.

Reputation Methodology →
No onchain feedback records indexed for this agent yet.

Forensic Observation Ledger

Complete, timestamped audit trail of every automated probe recorded for this agent.

TimestampProbe TypeResultLatencyHTTP StatusMethodology
10/8/2026, 8:04:17 PMRESPONSE_LATENCYSUCCESS (ONLINE)204 msHTTP 200v0.1.0
10/8/2026, 8:04:17 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 8:04:17 PMHTTP_STATUSSUCCESS (ONLINE)210 msHTTP 200v0.1.0
10/8/2026, 8:04:17 PMSERVICE_REACHABILITYSUCCESS (ONLINE)664 msHTTP 200v0.1.0
10/8/2026, 8:04:12 PMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)204 msHTTP 200v0.1.0
10/8/2026, 8:04:12 PMRESPONSE_LATENCYSUCCESS (ONLINE)203 msHTTP 200v0.1.0
10/8/2026, 8:04:12 PMHTTP_STATUSSUCCESS (ONLINE)201 msHTTP 200v0.1.0
10/8/2026, 8:04:12 PMSERVICE_REACHABILITYSUCCESS (ONLINE)375 msHTTP 200v0.1.0
10/8/2026, 8:04:01 PMMETADATA_RESOLUTIONPOLICY BLOCKED (SSRF)——v0.1.0
10/8/2026, 2:27:46 PMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)209 msHTTP 200v0.1.0
10/8/2026, 2:27:46 PMRESPONSE_LATENCYSUCCESS (ONLINE)213 msHTTP 200v0.1.0
10/8/2026, 2:27:46 PMHTTP_STATUSSUCCESS (ONLINE)205 msHTTP 200v0.1.0
10/8/2026, 2:27:46 PMSERVICE_REACHABILITYSUCCESS (ONLINE)380 msHTTP 200v0.1.0
10/8/2026, 2:27:45 PMMETADATA_RESOLUTIONPOLICY BLOCKED (SSRF)——v0.1.0
10/8/2026, 2:27:16 PMRESPONSE_LATENCYSUCCESS (ONLINE)212 msHTTP 200v0.1.0
10/8/2026, 2:27:16 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 2:27:16 PMHTTP_STATUSSUCCESS (ONLINE)207 msHTTP 200v0.1.0
10/8/2026, 2:27:16 PMSERVICE_REACHABILITYSUCCESS (ONLINE)377 msHTTP 200v0.1.0
10/8/2026, 6:31:45 AMRESPONSE_LATENCYSUCCESS (ONLINE)246 msHTTP 200v0.1.0
10/8/2026, 6:31:45 AMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 6:31:45 AMHTTP_STATUSSUCCESS (ONLINE)251 msHTTP 200v0.1.0
10/8/2026, 6:31:44 AMSERVICE_REACHABILITYSUCCESS (ONLINE)521 msHTTP 200v0.1.0
10/8/2026, 6:31:40 AMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)242 msHTTP 200v0.1.0
10/8/2026, 6:31:40 AMRESPONSE_LATENCYSUCCESS (ONLINE)243 msHTTP 200v0.1.0
10/8/2026, 6:31:40 AMHTTP_STATUSSUCCESS (ONLINE)242 msHTTP 200v0.1.0
10/8/2026, 6:31:39 AMSERVICE_REACHABILITYSUCCESS (ONLINE)482 msHTTP 200v0.1.0
10/8/2026, 6:31:39 AMMETADATA_RESOLUTIONPOLICY BLOCKED (SSRF)——v0.1.0
10/8/2026, 12:23:14 AMRESPONSE_LATENCYSUCCESS (ONLINE)220 msHTTP 200v0.1.0
10/8/2026, 12:23:14 AMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 12:23:14 AMHTTP_STATUSSUCCESS (ONLINE)222 msHTTP 200v0.1.0