[ENSv2, একটি নামে হাজার হাজার অ্যাকাউন্ট বহন করার পরিণতি] @ensdomains @ethereum 10 ই অক্টোবরে চালু হওয়া ENSv2-এ https://t.co/NvxB4rnXZr.eth এবং https://t.co/xwZsp1UT6i.eth-এর জন্য আলাদা আলাদা ব্যক্তি দায়িত্ব পালন করতে পারবেন। এটি হলো, কোম্পানি company.eth-এর মালিকানা ছেড়ে না দিয়েই, প্রতিটি দলকে প্রয়োজনীয় অনুমতি প্রদানের একটি পদ্ধতি। এই কাঠামোটির সঙ্গে একটি ঝুঁকিও আছে: একটি ছোট ডোমেইনই সম্পূর্ণ সেবার দুর্বলতা হয়ে দাঁড়াতে পারে। যদি উপরের (প্যারেন্ট) নামটির মেয়াদ শেষ হয়ে যায়, তবে তার নিচের সমস্ত সাবডোমেইনগুলিরও অনুসন্ধান বন্ধ হয়ে যাবে। ENS-কে সাধারণত দীর্ঘ ওয়ালেট ঠিকানার বদলে alice.eth-এর মতো পড়তে সহজ নামের সেবা হিসেবে চিহ্নিত করা হয়। অক্টোবরে ENS-এর প্রকাশিত পরিসরটি 905,000টি .eth নাম এবং 34,000,000টি সাবডোমেইন। মোট 36,000,000টিরওবেশি নামের সংখ্যায়, ব্যক্তিগতভাবে নিবন্ধিত নামগুলির পাশাপাশি, সংগঠনগুলির দ্বারা জারিকৃত সাবডোমেইনগুলিও 포함। একটি নামের মধ্যে অনেকগুলি ব্যক্তি এবং সেবা পরিচালনা করা—এই কাঠামোটি 이미 significant scale-এর use-এর । ENSv2-এ, these subnames-এর management-এর foundation-এ changes have been made. প্রতিটি name can now have its own subname registry, and the owner can assign permissions such as registration, profile editing, and subname management based on roles. উদাহরণস্বরূপ, a company can issue names to each employee, or grant editing rights separately to teams managing different services. পূর্বেও subnames-এর creation possible was, but ENSv2 has moved this management functionality into the core contract structure. অপরদিকে, responsible-এর concentration occurs. ENSv2-এ name lookup always starts from the parent registry and proceeds downward. যদি company.eth-এর expiration occurs or its subname registry connection is broken, even if you own https://t.co/xwZsp1UT6i.eth, you cannot resolve its payment address. This means the ability of the person who received the name, and the parent’s renewal and permission management, are now interlinked. Renewal rules also make this responsibility heavier. While ENSv1 maintained name resolution for up to 90 days after expiration, ENSv2 has a grace period of only 28 days, and resolution stops immediately upon expiration. If renewed during the grace period, it resumes functioning—but during the time missed, connected services may be affected. When migrating an existing name to v2, the expiration date is extended by 62 days to compensate for this difference. For example, if a v1 name had 100 days left until expiration, after migration to v2 it will have approximately 162 days left; the point at which another person can register it remains around day 190 for both versions. Although the re-registration window is the same, in v2 the name becomes unresolvable during the final 28 days. The risk of losing the name to someone else and the risk of temporarily disabling services now operate on different timelines. For an individual’s personal nickname, this may simply be an issue of renewal reminders. But if an organization has issued thousands of subnames to customers, employees, or agents, a single failure to renew the parent name can cause access problems across multiple services. This is precisely why—despite the fine-grained role-based design—the responsibility for renewing the parent name and having emergency recovery procedures becomes critically important. Registration price changes are also aligned with this design. The annual base price for .eth names longer than five characters has increased from $5 to $8—a 60% rise—while registering for six or more years reduces the annual cost to approximately $4.50. This pricing structure incentivizes long-term ownership over short-term use. However, as more accounts become linked to a single name, the cost of a missed renewal can far exceed the registration fee. Whether ENSv2 succeeds will not be explained solely by the number of new names issued. More convincing signals will be how many subnames organizations actually operate, how widely role-based permissions are delegated, and how many apps reliably resolve these names. ENS already supports name resolution for over 600 apps. Going forward, who takes responsibility for operating these names will determine the protocol’s trustworthiness. #ENS #Ethereum