Create pyth.sol subdomains

[yondu]

This makes sense to me. I think .sol is eponymous to solana, the general ecosystem

[Dave]

exactly my thoughts

[johnSmith]

absolutely. .sol!!

[defijedi]

great idea fully support

[Till]

Aren’t subdomains free?

[futu]

Subdomains can be free or not free, I believe. It would be up for the Pyth community to pick and choose.

[jasming]

I think 10pyth for a domain is a great deal and will actually help more people buy $pyth!

[RaulRoyal]

Wait what? Wasn’t this the point AllDomains was trying to make?

That domain names should be free?

But what does Bofida get out of it then tho?

[Exitliq]

all domains wants to keep 40%, and bonfida will keep 10% or something. I bet Bonfida will just hodl the tokens for voting in pyth anyways.

[boble]

Going with bonfida makes the most sense since they are multichain which makes sense for pythians

[Antoniosolana]

All Domain better!

[mowife]

they should be

[vincini45]

interesting idea

[KemarTiti]

Hi everyone,

A formal announcement regarding this proposed idea has been published in the temperature check topic. The poll has concluded and the results have been announced.

Please see this announcement post: https://forum.pyth.network/t/poll-selecting-domain-provider/229/183

[easy.sol]

GM again Pythians!

Selene here from the Solana Name Service BD team. The team is delighted with your choice to use SNS as your name service provider. We’d like to raise a few points that the Pyth DAO still needs to decide on before you can set up the subdomain registrar.

1. Pricing schedule for the domains (based on character length)

2. Authority address (address used to change the parameters of the subdomains)

3. Vault address (address to receive registration proceeds)

4. How often will the DAO review the pricing and based on what criteria

Feedback on the points above thus far;

1. There seems to have been some agreement on the initial pricing schedule detailed by @bonfida. The shorter the name the more premium and therefore the more expensive. For clarity the price schedule is quoted below - this is still to be decided on by you all.

@bonfida

Proposed Plan and Feasibility

The Pyth DAO needs to decide on the pricing of the subdomains. Pricing is based on the length of the subdomains, for example, the price schedule could be as follows:

# of characters	Cost in $PYTH
1	1000 PYTH
2	750 PYTH
3	500 PYTH
4	100 PYTH
5+	10 PYTH

2. For the authority address, @KemarTiti raised a valuable point - perhaps it’ll be better for the Pyth Council (multisig) to own this. This will likely be more efficient - considering that if the DAO owned it, each pricing schedule change would have to go through an operational vote. What do you all think about this?

@KemarTiti

Last, about the subdomain authority — I would suggest granting this authority to the Pythian Council (Multisig) as it would be solution with the least overheard/work required to maintain this endeavour

If the Pyth DAO were to be the owner of such, any changes would have to go through an operational vote (requiring a 50% quorum and a majority of YES) which slow things down as well as require the creation of custom proposals

3. The vault address seems clear-cut to be the DAO

4. Lastly, the frequency of the pricing review and the associated criteria were thoughtfully suggested by @Derrp. For conciseness, the proposed plan is to review it once every two years or when $PYTH hits these specific markers. The Pyth DAO needs to reach a consensus on this still.

@Derrp

Pricing structure seems fine. In regards to review timing structure…

Review at the following intervals (whichever is longest)
1: every 2years, OR

2: When the follong PYTH/USD Price targets are hit:
2.1. $0.01
2.2. $0.10
2.3. $1.00
2.4. $10.00
2.5. $100.00
2.6. $1000.00

I want to attach one final thought from @KemarTiti regarding point 4 - when the price schedule is changed, it may be wise for it to remain for at least 1 week before another round of repricing. This will give the Council time to evaluate the current condition of $PYTH accordingly and ensure users won’t be caught off guard. Does this align with the Pyth community?

Hope this quick summary helps. Once the DAO has finalized the points above you can get to setting up the registrar.

On a final note, the subdomain smart contract has now been open-sourced and the audit has been published. You can find it here: GitHub - Bonfida/sub-registrar: Allow the registration of subdomains through a community owned smart contract

[gnarleyquinn]

I dont actually get it myself.
I have a sol one, and I dont even use that to be honest.
Not sure what difference a pyth one will accomplish

[TheDetective]

I gotta admit both of these proposals are really good I wonder if both could be implemented so that the ecosystem would be able to benefit from both of these

[Derrp]

Unfortunately, as I understand it, both cannot be implemented.

[CLOSED] Poll: Selecting Domain Provider

Back to the poll results: Which service provider should be selected for launching Pyth-branded domains? The majority of the Pythians (59.5%) have voted to indicate a preference for Bonfida as the service provider. The @Bonfida team is invited to share their next steps as well as any next steps for the Pyth DAO in the initial topic: Create pyth.sol subdomains - #95 by bonfida

Bonfida have been invited to continue their proposal as they won a higher number of votes.

Also a lot of learnings from this initial process which are good to reflect upon

[RealPythGod]

I think this could be really interesting. I’ll be looking to cop an address, don’t really understand why less characters is more $$ but I guess thats how its designed

[ed_pyth]

Very well said. A lot of lessons learn on keeping a clean, organized forum…

Thank you again Selene @easy.sol for this opportunity!