Thanks for bringing these points up. The Pyth DAO has the possibility to reserve certain names in advance if it wants to. However, this approach has some limitations as it’s impossible to have an exhaustive list, but it should be good enough to prevent impersonation and harmful squatting in most cases.
30 Likes
Yes, anything above 5 char should be under a renewal fee withtout which the name becomes up for the taking, much like .com or others.
1 Like
Love this proposal ! Pricing makes sense …
2 Likes
With @AllDomains proposing its service, i want to know what is best for the pythians.
Can both you and Alldomains provide subdomain/TLD and people can choose to get theirs on their preferred platform? Or do we need to decide on one ‘provider’ through these discussions processes?
5 Likes
No, having both is not be feasible. It would lead to a collision and create ambiguity in domain resolution. Therefore, the Pyth DAO needs to decide on a single provider.
17 Likes
Just got a different reply here: Enable .pyth TLD and domain name registrations - #12 by AllDomains
1 Like
Their reply was misleading and they have since then clarified it. Having 2 .pyth TLD will create collisions and ambiguous name resolution as I have mentioned in my initial reply. This can lead to loss of funds, impersonation etc
20 Likes
Very interesting!
1 Like
Yep thank you! The Pythians will have to choose then
1 Like
Ofcourse all the Pyf have a soft spot for Bonfida!, let all parties have a space & present their proposals
1 Like
oh i asked this in AllDomain, this was my concern, thank you
2 Likes
Thank you @bonfida for your idea and proposal.
We believe integrating Pyth subdomains is a useful tool that will allow Pyth community members to identify and differentiate themselves. The pricing structure creates little friction and will allow all members to own a domain name with few barriers to entry.
We also feel the proposed fee split is fair, allowing the PYTH DAO to have an additional revenue stream.
We look forward to seeing this progress – and eventually to getting our own .Pyth domain!
9 Likes
Great to see so many Pythians chiming in/asking questions about this!
Let me rebound on a few new points/Qs that appeared since last week — bear in mind this is Marc/my own views and not those of the Pyth Data Association
- .pyth.sol
@Duckling i do agree with you that ABC.pyth > ABC.pyth.sol and the opportunity to do it with AllDomains.
However one point @bonfida brings to the table is that going the .pyth.sol way means leveraging all the existing SNS integration — in practice if we have ABC.pyth.sol we can then just tell all applications like Phantom to incorporate the SNS SDK Pyth edition and your ABC.pyth would work on Phantom
Maybe @bonfida can share a list of all SNS integrations and we should maybe gauge the willingness from Phantom/Solflare/Backpack and the likes to start indexing the SNS SDK .pyth — there’s barely any tech work but needs to be accepted by them
- Squatting/Sybilling
Great points brought up by @KnightsofNi and @Derrp
While having a subscription could be a deterrent to squatters and extra value for the DAO, i’d rather not have this at least for now. Technically a squatter owning a valuable subdomain would still renew his and having a steep renewal cost might rather be a burden for regular community members that just want their own .pyth subdomains.
A reserved list of domains could work yes, but how intensive is the work? Should we reserve it for long time community members? Applications powered by Pyth? Chains where Pyth is available on? Mainstream companies etc? Seems like a bottomless pit of names. Were/Are the names reserved for Bonfida .sol domains publicly available? We can maybe start from the work already done by others?
- What else?
I very much like the angle of involving/taking into account PYTH stakers within this .pyth endeavor.
And maybe we should start with a staggered approach — @bonfida do let us know if this is technically feasible — where maybe the project has training wheels for the 1st 6 or 12 months
Pyth subdomains would only be mintable by a SPL wallet that is staking at least 1,000 PYTH (amount can be changed)
Then you can only mint the .pyth subdomains that match the original SNS/.sol domain you already own. In other words, if you have abc.sol, you’ll be the only wallet able to mint abc.pyth.sol and you won’t be able to mint another .pyth subdomain, unless you buy more .sol domains
The one pitfall: if you don’t already own the .sol you wish to get .pyth for (if your preferred .sol domain is squatted, your .pyth would also be)
8 Likes
Hi KemarTiti!
Thank you for your response and for giving me the opportunity to further clarify the distinction between .pyth and .pyth.sol. As mentioned in my previous message on the forum (Create pyth.sol subdomains - #37 by bonfida), the differentiation is merely a UI convention and should not be considered an issue. Regarding the integrations, you can find a list here List of Integrations | English | Community Help Center
To ensure that active users can secure their desired domains, we can easily compile a list of names and make them available for registration. In the event of a serious squatting issue, the PYTH DAO has the authority to revoke the domain and prevent it from being registered again.
Please note that the smart contract is designed to be generic and does not support special gating for PYTH stakers. The .sol and .pyth namespaces are fully independent and separate, and the smart contract does not reserve or gate specific domains for holders of the .sol equivalent.
29 Likes
Wen launch?
LFG
4 Likes
I got introduced to Pyth through Bonfida, so it’s a clear winner for me.
And if it’s only an UI convention on how it’s displayed, I’d definitely say go with SNS.
6 Likes
Voting is live: Poll: Selecting Domain Provider
7 Likes
Cant wait to vote！
2 Likes
It would be great to join SNS and be a staker of pyth
1 Like
I am not sure it will work. Subdomains make you either type in the full name. Btw, they’re usually free
5 Likes