Follow RFC1464 for NNS TXT records #91
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-contract#91
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://datatracker.ietf.org/doc/html/rfc1464#section-2
As per https://github.com/neo-project/proposals/pull/133/ the soon-to-be-accepted format will be
neo.xxx.xx TXT "address=NUVPACMnKFhpuHjsRjhUvXz1XhqfGZYVtY"
Blocked until upstream proposal is merged.
Same can be done for CID (nice-name) and public key (group public key for contract signatures). This one is not blocked, but we still need to ensure compatibility between versions of the frostfs-node/frostfs-adm
This task better be in the frostfs-node repo. What we may do here is to write a convenient wrappers.