Not sure if subdomains are integrated. What is bothering me is that when I use subdomains for my web2 domains, the owner is still the domain. And they are free.
I haven’t seen this with any other name service provider
Not sure if subdomains are integrated. What is bothering me is that when I use subdomains for my web2 domains, the owner is still the domain. And they are free.
I haven’t seen this with any other name service provider
This is not actually true, on the integration level what you’re proposing here is doing subdomains
and they don’t need to decide on a single provider
ps: .pyth domains can only be done by AllDomains
so both .pyth.sol and .pyth can be made available to the public and the public can decide on what they want to own
I completely agree, but they are suggesting here is to do subdomains
.pyth can only be done by AllDomains
I will trust @bonfida answer here about this as my technical knowledge is limited: Create pyth.sol subdomains - #56 by bonfida
Saying that .pyth and .pyth.sol is the same and a UI convention is like saying
.sol is a UI convention, and I’m pretty sure you don’t want that
btw, I’m the founder of AllDomains
someone who had to go through it to get ourselves integrated, I can tell you it’s wild ride and it will never happen
trust whoever you want
Will do!
It was also pointed out as a potential issue here by @AllDomains: Enable .pyth TLD and domain name registrations - #14 by AllDomains
So i understand both can be done in parallel but could lead to impersonation and malicious actors. Thus, giving a choice for the community to choose one official provider.
All Domains who is offering the simplest solution in another proposal via .pyth (no extra characters) are renewable for this specific reason
Prevents squatters and creates an ongoing revenue stream for the DAO
You guys got caught lying on your data by @Fitzpatrick. Why would we trust you? You also avoided fully replying to him.
I think it’s sort of showing considering Alldomains has resorted to trying to threaten Bonfida.
I don’t see a threat here…
the main difference between the two is the fact that
x.pyth.sol is a subdomain
and x.pyth is a domain
imagine buying x.pyth.sol and thinking that you actually bought x.pyth
that was what the answer hinted to and the fact that doing subdomains is not a good path
it will confuse users and integrators that will not change the way they did it before now, it would add complexity and man hours to maintain
This statement is misleading. Subdomains and .sol
domains are the exact same thing from a technical perspective. The name service is recursive by design. In fact, .sol
domains are subdomains of the root
domain/TLD. Therefore, everything that is technically possible with a .sol
is possible with a subdomain. Regarding integrations, they are already supporting another TLD maintained by SNS which is the .twitter
TLD while using @
as the UI convention. Therefore, I don’t foresee the UI level convention being an issue based on this.
I thought it would only able to show .pyth.sol on the UI. It turns out much better now with just .pyth
In the past month, we’ve been working on formalizing what .sol subdomains are, and refining their design to protect both users and the community. This takes the form of a specification document (SNS-IP 4). The reference implementation of this specification (sub-registrar) will be used to administer pyth.sol
if the community ends up choosing to go with us. It is also worth noting that sub-registrar’s audit by Halborn is currently wrapping up. sns-ip/proposals/sns-ip-4.md at master · Bonfida/sns-ip · GitHub
This idea complicates the user experience.
TLD > Subdomains
I don’t fully get this as I am not that technical.
Why do we need a document - SNS-IP 4 to administer frog.pyth.sol?
Can’t I just go an claim my frog.pyth and be the owner of it?
your whole proposal here was about subdomains or I am wrong ??
Create pyth.sol subdomains
changing the goalpost is a a bad look from a supposedly big project
the fact that dAPPS integrated twitter a long time ago doesn’t mean they will actually work on this, it requires man hours
as I’ve said here: Poll: Selecting Domain Provider - #39 by vladtoni
this will create a lot of confusion on the users and dAPPS, nobody will work on this, I can guarantee it
imagine you showing X.pyth somewhere, but the user will have to send X.pyth.sol to a friend to receive some SOL (which they won’t, it defeats the whole purpose of domains) or use that in an explorer
Wow they are trying to charge for SUB domains?!
What a joke
i will vote the pyth.sol
yes. i believe they call this bullish