Reference Documentation

Proof of SQL Syntax

Proof of SQL requires cryptographic proofs for query results. This reference covers what SQL features are provable—not just what parses successfully.

Capability profile: Centralized EVM Proof Planner via commitments_v1_evmProofPlan. Upstream specification. Last verified 2026-07-13.

Quick Reference

At-a-glance view of what's provable in Proof of SQL

Feature	Status	Notes
SELECT & FROM
SELECT columns	Supported	Column selection, aliases, and +, -, * expressions
SELECT *	Supported	Wildcard selection
LIMIT / OFFSET	Supported	—
SELECT DISTINCT	Partial	Exactly one non-VARCHAR, non-BINARY, non-VARBINARY result expression; DISTINCT ON and ORDER BY are unsupported
WHERE Clause
=, !=, <, >, <=, >=	Supported	Basic comparisons
AND, OR, NOT	Supported	Logical operators
BETWEEN / NOT BETWEEN	Supported	Inclusive bounds; lowered to inequality expressions
IN / NOT IN value lists	Supported	Numeric, decimal, and string value lists; subqueries remain unsupported
LIKE / ILIKE	Not Supported	—
IS NULL	Not Supported	SXT table columns are non-nullable
Aggregation
GROUP BY	Partial	Exactly one non-VARCHAR, non-BINARY, non-VARBINARY grouping expression
SUM()	Supported	Supported with or without COUNT()
COUNT()	Supported	COUNT(*) and COUNT(column) are supported
COUNT(DISTINCT) / SUM(DISTINCT)	Partial	One distinct aggregate over one non-VARCHAR, non-BINARY, non-VARBINARY expression; may be combined with plain aggregates but not GROUP BY
AVG(), MIN(), MAX()	Not Supported	—
HAVING	Supported	Supported on planner-compatible aggregate queries
Joins & Unions
INNER JOIN	Partial	The planner accepts equality, non-equality, and compound predicates; the current EVM verifier only validates one equality join key
LEFT / RIGHT / FULL JOIN	Not Supported	—
UNION ALL	Supported	—
UNION (distinct)	Partial	Exactly one non-VARCHAR, non-BINARY, non-VARBINARY output expression
Advanced
Query parameters ($1, $2)	Supported	Full guide — Dynamic values supplied at runtime
ORDER BY	Not Supported	Sort in the application
Subqueries	Partial	Derived tables and uncorrelated plain-column scalar subqueries in WHERE comparisons are supported; expression, aggregate, projection, correlated, tableless, IN, and EXISTS forms are unsupported
CTEs (WITH clause)	Not Supported	—
Window functions	Not Supported	—
Division (/)	Not Supported	Unsupported by the prover and EVM verification
Scalar functions	Not Supported	Unknown functions are rejected conservatively

Detailed Reference

The SELECT clause supports column selection, aliases, wildcards, and arithmetic expressions.

Supported

• Column selection: SELECT col1, col2
• Wildcard: SELECT *
• Aliases: SELECT col AS alias
• Arithmetic: col1 + col2, col1 * col2
• Type casting: CAST(col AS BIGINT)
• Single-expression SELECT DISTINCT on non-string data

Not Supported

• Division (/)
• String functions (CONCAT, UPPER)
• CASE expressions
• COALESCE / NULLIF

sql

-- ✅ Basic column selection
SELECT NAME, AREA, LONGITUDE FROM NAMESPACE.LOCATIONS

-- ✅ Arithmetic expressions
SELECT PRICE, QUANTITY, PRICE * QUANTITY AS TOTAL FROM NAMESPACE.ORDERS

-- ✅ DISTINCT supports one non-VARCHAR/non-BINARY/non-VARBINARY expression
SELECT DISTINCT BLOCK_NUMBER + 1 FROM ETHEREUM.TRANSACTIONS LIMIT 10

-- ✅ Column aliases
SELECT ID AS USER_ID, NAME AS USER_NAME FROM NAMESPACE.USERS

Test Your Query

Always verify your query via the RPC endpoint before deploying. If you receive an error, the query is not provable.

bash

curl -X POST https://rpc.mainnet.sxt.network \
  -H "Content-Type: application/json" -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "commitments_v1_evmProofPlan",
    "params": { "query": "SELECT NAME FROM NAMESPACE.TABLE WHERE ID = 1" }
  }'

Response Interpretation

Success

Response contains "proofPlan": "0x..."

Failure

Response contains "error" with details

Proof of SQL Syntax

Quick Reference

Detailed Reference

SELECT Clause

Supported

Not Supported

WHERE Clause

GROUP BY & Aggregation

JOIN Operations

Set Operations (UNION)

Arithmetic Operators

LIMIT & OFFSET

Query Parameters ($1, $2, ...)

Features NOT Provable

Query Limits

Test Your Query

Response Interpretation