Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat!: reserve the last 256 namespaces for protocol use (backport #2257) #2261

Merged
merged 7 commits into from
Aug 15, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Aug 14, 2023

Back-port the following commits from main to v1.x:

  1. 6f8ece4
  2. 5845ea4
  3. 2b9a883
  4. 8bd17d3

Instead of just cherry-picking the last one because then we'd have to maintain a slight divergence between main and v1.x.
Since the pre-ceeding commits were easy to cherry-pick too, this PR brings v1.x closer to main.

Closes #2253

(cherry picked from commit cb8247e)

# Conflicts:
#	pkg/namespace/consts.go
#	pkg/namespace/namespace.go
#	pkg/namespace/namespace_test.go
#	pkg/shares/padding.go
#	specs/src/specs/namespace.md
@github-actions
Copy link

github-actions bot commented Aug 14, 2023

PR Preview Action v1.4.4
🚀 Deployed preview to https://celestiaorg.github.io/celestia-app/pr-preview/pr-2261/
on branch gh-pages at 2023-08-14 19:12 UTC

@MSevey MSevey requested a review from a team August 14, 2023 14:32
@rootulp rootulp marked this pull request as draft August 14, 2023 16:58
@rootulp rootulp self-assigned this Aug 14, 2023
rootulp and others added 5 commits August 14, 2023 15:04
Closes #2143

De-duplicate `ValidateBlobNamespace` and export it from `x/blob/types`
package. The namespace package needs to define its own `isBlobNamespace`
because it can't import `ValidateBlobNamespace` from `x/blob/types` as
that would introduce a circular dependency.
…to IsReserved function (#2194)

Closes ##2138
This PR also addresses the concerns raised in the
[comment](#2138 (comment))
by introducing a distinction between two types of reserved namespaces.
Namespaces within the range [0-255] are now identified as "Primary
Reserved Namespaces," while any other reserved namespaces beyond this
range are categorized as "Non-Primary Reserved Namespaces." Hopefully,
this differentiation provides better clarity and organization regarding
namespace allocation and usage within the code.

- [x] New and updated code has appropriate documentation
- [x] New and updated code has new and/or updated testing
- [x] Required CI checks are passing
- [x] Visual proof for any user facing features like CLI or
documentation updates
- [x] Linked issues closed with keywords
@rootulp rootulp added this to the Mainnet milestone Aug 14, 2023
@rootulp
Copy link
Collaborator

rootulp commented Aug 14, 2023

Note: I think we should not squash when we merge this PR b/c each commit (with the exception of the first two) is a separate logical change that occurred on main and was cherry-picked to v1.x.

@rootulp rootulp marked this pull request as ready for review August 14, 2023 19:26
@rootulp rootulp enabled auto-merge (squash) August 14, 2023 19:43
@rootulp rootulp disabled auto-merge August 14, 2023 19:57
@rootulp rootulp enabled auto-merge August 14, 2023 19:58
@rootulp rootulp merged commit 53b5dbf into v1.x Aug 15, 2023
22 checks passed
@rootulp rootulp deleted the mergify/bp/v1.x/pr-2257 branch August 15, 2023 10:47
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.

4 participants