Nil UUID (All Zeros)

The Nil UUID is a special UUID where all 128 bits are set to zero: 00000000-0000-0000-0000-000000000000. It is explicitly defined in both RFC 4122 and RFC 9562 as a valid UUID that serves as a sentinel or placeholder value.

Binary representation:

00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000

Version and variant: The Nil UUID does not conform to any version or variant encoding. Its version bits (bits 48-51) are 0000 and its variant bits do not match the standard 10 pattern. UUID validation libraries should recognize it as a special case rather than rejecting it as invalid.

Nil UUID vs NULL: In database design, the Nil UUID and SQL NULL serve different purposes. NULL means "no value" or "unknown" and has special three-valued logic behavior in SQL (NULL != NULL, NULL comparisons return NULL). The Nil UUID is an actual value that can be compared with equality, used in foreign key constraints, and indexed normally. Use NULL when the absence of a value is semantically meaningful. Use the Nil UUID when you need a concrete "empty" or "default" identifier that still satisfies NOT NULL constraints.

Common use cases:

• Default value for UUID columns that require NOT NULL
• Sentinel value indicating "not yet assigned" or "system-generated"
• Root node identifier in tree structures
• Placeholder in configuration when no real UUID exists yet

Detection in code:

function isNilUuid(uuid) {
  return uuid === '00000000-0000-0000-0000-000000000000';
}

import uuid
nil = uuid.UUID(int=0)  # or uuid.UUID('00000000-0000-0000-0000-000000000000')
assert nil == uuid.UUID(int=0)

Important design consideration: If you use the Nil UUID as a default, document this convention clearly. Developers may accidentally treat it as a valid entity reference, leading to bugs where operations are performed against a non-existent resource. Always validate that a UUID is not Nil before using it as a lookup key.