Skip to content

Conversation

@satoshi-testaccount
Copy link
Contributor

  • Revised intermediate guide: Running Your Own IPFS Node and IPNS Publishing

  • Add advanced section with 6 comprehensive guides:

    • Advanced dWebsite Topics overview
    • ENS Subdomains and CCIP (wildcard resolvers)
    • Registry vs Resolver (ENS architecture)
    • Record Types (contenthash, TXT, multiformats)
    • Alternatives to IPFS (Arweave, Swarm, Sia, Skynet, Filecoin)
    • Arweave and ArNS (permanent storage)
  • Update SUMMARY.md with proper navigation structure

  • Include code examples, best practices, and troubleshooting guides

  • Add current ENS Public Resolver addresses for mainnet, goerli, and sepolia

  • Add version compatibility warnings for IPFS commands

  • Add verification notes for multicodec values and API compatibility

  • Add comprehensive disclaimers about technical review requirements

  • Update code examples with current best practices

  • Add links to official documentation for verification

All technical implementation details now include proper disclaimers
and references to official documentation for verification.

satoshi-testaccount and others added 2 commits August 16, 2025 19:09
- Add intermediate guide: Running Your Own IPFS Node and IPNS Publishing
- Add advanced section with 6 comprehensive guides:
  * Advanced dWebsite Topics overview
  * ENS Subdomains and CCIP (wildcard resolvers)
  * Registry vs Resolver (ENS architecture)
  * Record Types (contenthash, TXT, multiformats)
  * Alternatives to IPFS (Arweave, Swarm, Sia, Skynet, Filecoin)
  * Arweave and ArNS (permanent storage)
- Update SUMMARY.md with proper navigation structure
- Include code examples, best practices, and troubleshooting guides
- Add current ENS Public Resolver addresses for mainnet, goerli, and sepolia
- Add version compatibility warnings for IPFS commands
- Add verification notes for multicodec values and API compatibility
- Add comprehensive disclaimers about technical review requirements
- Update code examples with current best practices
- Add links to official documentation for verification

All technical implementation details now include proper disclaimers
and references to official documentation for verification.
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