ALTCHA PHP Library

July 20, 2026 · View on GitHub

A lightweight PHP library for creating and verifying ALTCHA challenges using key derivation functions (PBKDF2, Argon2id, Scrypt).

Compatibility

  • PHP 8.1+

Migrating from V1 to V2

Example

Installation

composer require altcha-org/altcha

Usage

<?php

require 'vendor/autoload.php';

use AltchaOrg\Altcha\Altcha;
use AltchaOrg\Altcha\CreateChallengeOptions;
use AltchaOrg\Altcha\SolveChallengeOptions;
use AltchaOrg\Altcha\VerifySolutionOptions;
use AltchaOrg\Altcha\Payload;
use AltchaOrg\Altcha\Algorithm\Pbkdf2;

$pbkdf2 = new Pbkdf2();
$altcha = new Altcha(
    hmacSignatureSecret: 'secret',
    hmacKeySignatureSecret: 'key-secret', // optional, enables fast verification path
);

// Create a new challenge
// Modify the cost and counter depending on the algorithm
$challenge = $altcha->createChallenge(new CreateChallengeOptions(
    algorithm: $pbkdf2,
    cost: 5000,
    counter: random_int(5000, 10000),
    expiresAt: time() + 600,
));

// Solve the challenge (client-side in production)
$solution = $altcha->solveChallenge(new SolveChallengeOptions(
    algorithm: $pbkdf2,
    challenge: $challenge,
));

// Verify the solution (server-side)
if ($solution !== null) {
    $payload = new Payload($challenge, $solution);
    $result = $altcha->verifySolution(new VerifySolutionOptions(
        algorithm: $pbkdf2,
        payload: $payload,
    ));

    if ($result->verified) {
        echo "Solution verified!\n";
    }
}

VerifySolutionOptions::$payload also accepts the raw base64-encoded string posted by the widget, or a decoded associative array — no manual parsing required:

// $_POST['altcha'] is the base64-encoded payload string from the widget
$result = $altcha->verifySolution(new VerifySolutionOptions(
    payload: $_POST['altcha'],
    algorithm: $pbkdf2,
));

API

Altcha

$altcha = new Altcha(
    hmacSignatureSecret: 'secret',
    hmacKeySignatureSecret: 'key-secret', // enables fast verification path
    hmacAlgorithm: HmacAlgorithm::SHA256, // default
);

Altcha::createChallenge(CreateChallengeOptions $options): Challenge

Creates a new challenge.

CreateChallengeOptions

ParameterTypeDefaultDescription
algorithmDeriveKeyInterfacerequiredKey derivation algorithm
costintrequiredIterations/time cost
counter?intnullCounter for deterministic mode
data?arraynullCustom metadata
expiresAt?intnullUnix timestamp for expiration
keyLengthint32Derived key length in bytes
keyPrefixLengthintkeyLength / 2Key prefix length in bytes
memoryCost?intnullMemory cost (Argon2id/Scrypt)
nonce?stringnullCustom nonce (hex)
parallelism?intnullParallelism factor (Scrypt)
salt?stringnullCustom salt (hex)

When counter is provided and hmacKeySignatureSecret is set, the challenge includes a keySignature for fast verification (skips re-derivation).

Returns: Challenge with parameters (ChallengeParameters) and signature.

Altcha::solveChallenge(SolveChallengeOptions $options): ?Solution

Iterates counter values to find a derived key matching the challenge prefix.

SolveChallengeOptions

ParameterTypeDefaultDescription
algorithmDeriveKeyInterfacerequiredKey derivation algorithm
challengeChallengerequiredThe challenge to solve
startint0Initial counter value
stepint1Counter increment per iteration
timeoutfloat30.0Timeout in seconds

Returns: Solution with counter, derivedKey (hex), and time (seconds). Returns null if no match is found.

Altcha::verifySolution(VerifySolutionOptions $options): VerifySolutionResult

Verifies a solution against its challenge.

VerifySolutionOptions

ParameterTypeDefaultDescription
algorithmDeriveKeyInterfacerequiredKey derivation algorithm
payloadPayload|string|arrayrequiredChallenge + solution pair — a Payload object, a raw base64-encoded payload string (as posted by the widget), or a decoded associative array. Throws InvalidArgumentException if a string/array can't be parsed into a valid payload.

VerifySolutionResult

PropertyTypeDescription
verifiedboolWhether the solution is valid
expiredboolWhether the challenge has expired
invalidSignature?boolWhether the challenge signature is invalid
invalidSolution?boolWhether the derived key doesn't match
timefloatVerification time in seconds

Key Derivation Algorithms

All algorithms implement DeriveKeyInterface.

PBKDF2

use AltchaOrg\Altcha\Algorithm\Pbkdf2;
use AltchaOrg\Altcha\HmacAlgorithm;

new Pbkdf2();                        // PBKDF2/SHA-256
new Pbkdf2(HmacAlgorithm::SHA384);  // PBKDF2/SHA-384
new Pbkdf2(HmacAlgorithm::SHA512);  // PBKDF2/SHA-512

Argon2id

Requires ext-sodium (typically bundled with PHP).

use AltchaOrg\Altcha\Algorithm\Argon2id;

new Argon2id();

Uses memoryCost from challenge options.

Scrypt

Requires ext-scrypt (php-scrypt).

use AltchaOrg\Altcha\Algorithm\Scrypt;

new Scrypt();

Uses memoryCost (r, default: 8) and parallelism (p, default: 1) from challenge options.

HmacAlgorithm

Enum used for HMAC signing and PBKDF2 hash selection:

  • HmacAlgorithm::SHA256 - SHA-256
  • HmacAlgorithm::SHA384 - SHA-384
  • HmacAlgorithm::SHA512 - SHA-512

ServerSignature::verifyServerSignature(string|array $data, string $hmacKey, HmacAlgorithm $hmacAlgorithm = HmacAlgorithm::SHA256): ServerSignatureVerification

Verifies a server signature payload.

ServerSignatureVerification

PropertyTypeDescription
verifiedboolWhether the signature is valid, not expired, and solution verified
expiredboolWhether the verification data has expired
invalidSignatureboolWhether the HMAC signature is invalid
invalidSolutionboolWhether the solution was not verified
timefloatVerification time in seconds
verificationData?ServerSignatureVerificationDataParsed verification data

Verification data is parsed generically from URL-encoded params with auto-detected types (bool, int, float, string, array for fields/reasons). Access values via property or array syntax:

use AltchaOrg\Altcha\ServerSignature;

$result = ServerSignature::verifyServerSignature($payload, 'server-secret');

if ($result->verified) {
    $result->verificationData->expire;          // int
    $result->verificationData->score;           // float
    $result->verificationData->verified;        // bool
    $result->verificationData->fields;          // array
    $result->verificationData->classification;  // string
    $result->verificationData['email'];         // array access also works
}

ServerSignature::verifyFieldsHash(array $formData, array $fields, string $fieldsHash, HmacAlgorithm $hmacAlgorithm = HmacAlgorithm::SHA256): bool

Verifies the hash of specific form fields.

$isValid = ServerSignature::verifyFieldsHash(
    formData: ['name' => 'John', 'email' => 'john@example.com'],
    fields: ['name', 'email'],
    fieldsHash: hash('sha256', "John\njohn@example.com"),
);

Sentinel::verify(VerifyServerOptions $options): VerifyServerResult

Verifies a payload remotely by calling ALTCHA Sentinel's POST /v1/verify/signature API, instead of verifying the HMAC signature locally. Useful when Sentinel issues and signs challenges directly, so your server doesn't need to hold the HMAC secret at all.

use AltchaOrg\Altcha\Sentinel;
use AltchaOrg\Altcha\VerifyServerOptions;

$result = Sentinel::verify(new VerifyServerOptions(
    payload: $_POST['altcha'], // raw base64 string, or a decoded array
    url: 'https://sentinel.example.com/v1/verify/signature',
    secret: $sentinelApiKeySecret, // optional, checked against the payload's API key
    timeout: 10.0,
    retries: 2,
));

if ($result->verified) {
    // ...
}

VerifyServerOptions

ParameterTypeDefaultDescription
payloadstring|arrayrequiredThe payload to verify, as received from the client (raw base64 string or decoded array)
urlstringrequiredFull URL of the Sentinel /v1/verify/signature endpoint
secret?stringnullAPI key secret checked against the payload's API key
httpClient?HttpClientInterfacenullCustom HTTP client. Defaults to a built-in stream-based client requiring no extra extension
headersarray<string, string>[]Additional headers to send with the request
timeoutfloat10.0Per-attempt request timeout in seconds
retriesint0Number of retry attempts after the first try
retryDelayint300Base delay in milliseconds between retries
retryBackoffRetryBackoffRetryBackoff::ExponentialBackoff strategy (Fixed or Exponential) applied to retryDelay

A 4xx/non-2xx HTTP response and network errors are retried up to retries times (with backoff), except HTTP 400, which is treated as a definitive verification failure and returned immediately.

VerifyServerResult

PropertyTypeDescription
verifiedboolWhether the payload was successfully verified
apiKey?stringAPI key associated with the verification
reason?stringReason or error message if verification failed
verificationData?ServerSignatureVerificationDataVerification data returned by Sentinel

To use your own HTTP client (e.g. Guzzle, Symfony HttpClient) instead of the built-in stream-based one, implement AltchaOrg\Altcha\Http\HttpClientInterface and pass it via httpClient:

use AltchaOrg\Altcha\Http\HttpClientInterface;
use AltchaOrg\Altcha\Http\HttpResponse;

class MyHttpClient implements HttpClientInterface
{
    public function send(string $url, string $method, array $headers, string $body, float $timeout): HttpResponse
    {
        // ... perform the request with your client of choice ...
        return new HttpResponse($statusCode, $responseBody);
    }
}

Payload

Wraps a Challenge and Solution pair for verification and serialization.

$payload = new Payload($challenge, $solution);

$payload->toArray();   // array
$payload->toJson();    // JSON string
$payload->toBase64();  // base64-encoded JSON

V1 API

The V1 API is available under the AltchaOrg\Altcha\V1 namespace. It uses simple hash-based challenges (SHA-1, SHA-256, SHA-512) instead of key derivation functions.

Tests

vendor/bin/phpunit tests

License

MIT