Sha256
$sha256(data) is now a compatibility function in builtins, not a registered C built-in. It returns $xform(+sha256 data): a SHA-256 digest represented as 64 uppercase hexadecimal digits. The wrapper requires its defining script to be loaded; default startup normally loads it.
The direct xform equivalent is:
$xform(+sha256 booya booya booya boo)
For that input the digest is:
62EA80CA6A21D4AB1FEC0C5C3227B593ED04309474BE04CA03EA74D91FA09C34
This hashes the received input bytes, not a named file's contents, and sends no IRC request. Ordinary argument expansion happens before hashing. Script arguments are C strings; use a single xform chain when an earlier transform produces binary data containing NUL bytes, so intermediate lengths are preserved.
The current implementation uses OpenSSL's EVP SHA-256 interface. The digest is a one-way hash, not encryption; using the decoding direction does not recover the original input. It is no longer documentation for the retired AES+SHA or SED+SHA encryption interfaces. See xform for the currently registered transformations and failure behavior.
Source references
script/builtins:sha256wrapper.source/ircaux.c:sha256_digest, hexadecimal formatting, and transform registration.source/functions.c: xform entry point and current function registry.configure.ac: cryptographic-library build checks.