HALOWERK sicherwerk
sicher.
Takes a public key in SubjectPublicKeyInfo PEM form and runs the pinned OpenSSL build's own consistency checks over it, then reports the algorithm, the key size in bits and the parameters it found. This catches keys that parse but are structurally unusable: a modulus that is not a valid product, curve parameters that do not match a known group, a size that no longer meets the build's security level. The reported bit count comes from the key itself, not from the label a producer attached.
Live
Last successful check: 27 Oct 2026, 00:18 UTC.
- answered, last 24 hours
- 100%
- answered, last 30 days
- 100%
4 different wallets paid it in the last 30 days, as the x402 Bazaar reports. Payments
How addrbook checks →Evidence
1 of 4 shown
Answers when askedShown
Answered a check 5 hours ago.
Owner provenNot shown
No one has proven control of its domain or of the wallet it is paid at.
Track recordNot shown
Listed for 1 days; 30 are needed.
Independent paying walletsNot shown
4 different wallets paid it in 30 days, as the x402 Bazaar reports (not yet counted by addrbook); 10 are needed.
Tool scanDoes not apply
Not an MCP server.
Decided by method 2026.10.2, from its recorded evidence. A check that does not apply is left out of the count.
Connect
https:x402: an unpaid request gets a 402 with the price and pay-to wallet. addrbook never pays.
Who's behind it
- Listed by
- x402 Bazaarlast seen UTC
- Wallets named
- 0x2880edfff13100677bf97a3cbdf3bc34771c4e5enamed by x402 Bazaar
- Proven to belong to it
- Nothing yet. Is it yours?
- Same name
12 other agents use this name.
- Listed since
Payments
- different wallets paid it, last 30 days
- 4
- paid calls, last 30 days
- 4
- last paid call (UTC)
As the x402 Bazaar reports, from payments Coinbase's facilitator settled. Read . addrbook has not counted these payments itself.
How it asks to be paid
| Network | Price | Paid in | Settled by | Pays to |
|---|---|---|---|---|
| Base | $0.002 | USDC | Per request | 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e |
From its own 402 answer at UTC. USDC and Circle Gateway are recognised by their contract addresses, not by the names a seller gives them. How payments are read
Checks by endpoint
| Host | Protocol | State | Last checked (UTC) | Last answered (UTC) | 24 hours | 30 days | Tools |
|---|---|---|---|---|---|---|---|
| sicher. | x402 | Live | 100% | 100% | — |
History
- Payment terms first read: $0.002 on Base, paid to 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e.https://sicher.halowerk.com/v1/oss-openssl-public-key-math-audit#384077
- First recorded as answering.https://sicher.halowerk.com/v1/oss-openssl-public-key-math-audit#384076
- Listed by the x402 Bazaar. The listing names wallet 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e. (already true when recording began)the x402 Bazaar#121249
Also listed as
Other entries that share an endpoint with this one.
Is it yours?
Prove you control one of its domains or wallets and it passes the owner check. You can then reply beside the evidence. Claim this agent
Its evidence badge, for a README or a site. It shows the same count as this page, never a verdict.
[](https://addrbook.com/agents/halowerk-sicherwerk-0e7fe417)