Publish a DNSLink record of the immutable archives IPNS name in the Mithril networks DNS zones
Maintainers usually reply within 2 days
Assessment
This issue has not been assessed yet.
Description
Why
Third parties replicating the immutable archives of a Mithril network must copy its opaque IPNS name (/ipns/k51...) from the documentation, while a DNSLink TXT record (_dnslink.<domain>, see https://deepwiki.com/ipfs/specs/5.1-ipns-records-and-protocol and https://dnslink.dev/) would give it a stable and human readable name under the Mithril domain.
What
Each Mithril network with IPNS publication enabled has a DNSLink TXT record pointing to the IPNS name of its immutable archives directory, documented for third parties, while the artifacts keep their direct ipfs:// locations.
How
- Add a
_dnslink.immutablesTXT record with the valuednslink=/ipns/<IPNS name>in the DNS zone of the network (<network>.api.mithril.network) inmithril-infra, only when IPNS publication is enabled - Deploy the record on the networks with IPNS publication enabled
- Update the documentation with the DNSLink name of the immutable archives
- Network configurations page
- IPFS replica guide (
ipfs name resolveof the DNSLink name) - Prepare for publication of IPNS DNSLink names with next distributions
- Dominant language
- Rust
- Stars
- 155
- Forks
- 52
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 37
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IntersectMBO/mithril
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
IntersectMBO/mithril#1605 · 2 comments ·
Maintainers usually reply within 2 days
-
spike :satellite:
Difficulty 5/5 Over a week Newbie friendliness 10/100
IntersectMBO/mithril#3701 ·
Maintainers usually reply within 2 days
-
feature :rocket:
Difficulty 4/5 3-5 days Newbie friendliness 25/100
IntersectMBO/mithril#3699 ·
Maintainers usually reply within 2 days
-
feature :rocket:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
IntersectMBO/mithril#3698 ·
Maintainers usually reply within 2 days
-
Prototype the Cardano database snapshot and restoration with the Leios databasePossibly taken @jpraynaud claimed this 5 days ago. Openprototype :hammer_and_wrench:
IntersectMBO/mithril#3691 · 1 assignee ·
Maintainers usually reply within 2 days
All issues in IntersectMBO/mithril
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/photocraft#14822 ·
Maintainers usually reply within 1 day
-
bug css
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
dginev/latexml-oxide#853 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
[Bug] export_build_environment admits its output directory only after the export ran in the build computerPossibly taken @viniciusdsandrade claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day