PNS
  • PNS: Your Identity in Polkadot
  • Summary
  • Advanced Topics
  • Contributing
  • Core Concepts
  • FAQ & Troubleshooting
  • PNS Troubleshooting Guide
  • PNS User Guide
  • advanced-topics
    • Contract Deployments
    • Custom Resolvers
    • Custom Top-Level Domain (TLD) Registration
    • Subdomain Management
  • contributing
    • GitHub Workflow
    • Contribution Guidelines
    • Issue Reporting
  • faq
    • Common Issues
    • Technical FAQ
Powered by GitBook
On this page
  • Why PNS Matters
  • Real-world Impact
  • Why Choose PNS?
  • For Users
  • For Developers
  • For Projects

PNS: Your Identity in Polkadot

Why PNS Matters

Imagine sending tokens to 0x6C6b33B45573DE6C04E7b644246129DDb3d8610D when you could just use alice.dot. PNS transforms complex Polkadot addresses into human-readable names, making web3 more accessible and safer.

Real-world Impact

  • ✅ Send assets to company.dot instead of 0x6C6...10D

  • 🔒 Reduce transaction errors

  • 🌐 One name works across all Polkadot parachains

  • 🎯 Build your web3 identity and brand

Why Choose PNS?

For Users

  • Universal Identity: One name for all Polkadot services

  • Asset Protection: Never send to wrong addresses again

For Developers

  • Simple Integration: Easy to add PNS to your projects

  • Extensible: Add custom records and features

For Projects

  • Brand Protection: Secure your project's identity

  • Enhanced UX: Make your dApp more user-friendly

  • Ecosystem Ready: Integration with major Polkadot tools

This project is licensed under the MIT License - see the LICENSE file for details.

NextSummary

Last updated 3 days ago