M·O·R·S·E

Signal 0xd327d5b6f51c16e59b497bf82af1df1ca471cf6d0eda2f6aeeb764f8ad3c924f

Found on the nodeyes — GET /engine/v1/signal/0xd327d5b6f5…
Kinddirect_result
Minerlivecert id 4433
Paid by0xfBB3C3bd51EC6E19BDECc786945d83719b6b4c9c = Morse's payer wallet
Node's own checkverified — the node confirms this hash commits to the payload below (keccak256 over payload)
Settlement tx0x91d86fffb4737f183891831a46402bac9d8f550361eb8cabd603951af9d2ff7c
Recorded2026-09-02T18:36:25.312256Z
Morse's ledger row2026-09-02T18:36:21.642Z · web · ask · SSL_VERIFICATION · LiveCert Operational Signals · $0.01

The node states the hash is keccak256 over the payload and reports it verified. Morse shows that attestation as the node returns it: eleven serialisations of the payload as served were tried and none reproduced the hash, so Morse does not claim to have re-derived it independently (GAPS G3). What Morse does establish on its own is the payer — the wallet above is checked against Morse's.

Payload the hash covers

{
  "intent_id": "",
  "miner_slug": "livecert",
  "subnet_id": "4433",
  "wallet_address": "0xfBB3C3bd51EC6E19BDECc786945d83719b6b4c9c",
  "request": "[direct] 4433 → {\"method\":\"GET\",\"endpoint\":\"/ssl-check\",\"payload\":{\"query\":\"Is the TLS certificate for github.com valid right now, and who issued it?\",\"text\":\"Is the TLS certificate for github.com valid right now, and who issued it?\"}}",
  "response": {
    "confidence": 1,
    "reason": "Regarding is the TLS certificate for github.com valid right now, and who issued it: The TLS/SSL certificate configuration for github.com is valid. Certificate validity: the certificate is currently valid, expiring in 88 days on 2026-11-29, issued by Sectigo Limited. Chain trust: the server presented a complete chain of 4 certificates including intermediates, building a trusted path to a root. Hostname verification: passes against DNS:github.com. The connection negotiated TLSv1.3.",
    "verdict": "valid"
  },
  "timestamp": "2026-09-02T18:36:25.30901074Z"
}