Skip to content

feat(opaque-links): recognise 0x link ids (TEC-3037) - #34

Merged
nadeem-fileverse merged 1 commit into
mainfrom
nk/opaque-link-0x
Oct 9, 2026
Merged

nadeem-fileverse merged 1 commit into
mainfrom
nk/opaque-link-0x

Conversation

@nadeem-fileverse

Copy link
Copy Markdown
Contributor

Opaque link ids are now 0x plus 18 base58 characters, a product requirement. Rooms are matched by that exact shape, never by the 0x prefix alone, since addresses, hashes and on-chain ids also start with 0x.

  • acceptedDdocId stores the on-chain ddocId only for a room named by a link id, and refuses a link id as the ddocId.
  • The publish reconciler skips link rooms that have no ddocId.
  • Tests cover link ids, the old o- shape, address-named rooms and on-chain ids that start with 0x.

Deploy before any ddocs.new that mints 0x ids, or no ddocId is stored for new opaque rooms.

Opaque link ids are now 0x plus 18 base58 characters, a product
requirement. Rooms are matched by that exact shape, never by the 0x
prefix alone, since addresses, hashes and on-chain ids also start
with 0x.

- acceptedDdocId stores the on-chain ddocId only for a room named by a
  link id, and refuses a link id as the ddocId.
- The publish reconciler skips link rooms that have no ddocId.
- Tests cover link ids, the old o- shape, address-named rooms and
  on-chain ids that start with 0x.

Deploy before any ddocs.new that mints 0x ids, or no ddocId is stored
for new opaque rooms.
@nadeem-fileverse
nadeem-fileverse merged commit 8202a0c into main Oct 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant