[temp check] Proposal for new Service Provider Streams

[cap]

I agree with all of your thoughts here. I also want to highlight the following:

@lightwalker.eth

This vote isn’t about spending money. It’s about investing into the continued growth and success of ENS. We have so much potential with ENS and there is so much remaining work to be done. These investments can produce a strong return in the growth of ENS.

I look at this proposal as ‘addressing the opportunity’ rather than thinking of how much it would ‘cost’ the DAO. And the opportunity is big, especially since the criteria for eligible projects is well defined by AvsA in his proposal above.

[accessor.eth]

I agree. It is rather important for ENS DAO, ENS Labs, contributors to implement using ENS Domains in all aspects of ENS matters. Given the the recent reflection regarding the DAO and Working Groups previous and ongoing expenditures; we should consider using ENS Names in every payment officially affiliated.

This would include using subdomains as labeling identifiers for outbound payments.

Requiring all official wallets to be properly labeled. I’m not sure who is in control, where they are located or what names the DAO controls. I think it’s important to create a master list of all name and addresses.

All assets shouldto be identified and indexed.

• what the asset is (mainly wallets)

• those who have been granted authority, i,e, authorizers, approvers, reviewers et al.

• a schedule of when granted authority will (or may) change due to election or assigned position changes.

classification and labeling

          {endpoint}.{q#yy}.scholarship.{wg}.ensdao.eth
            {endpoint}.{q#yy}.bounty.metagov.ensdao.eth
 {endpoint}.{q#yy}.{project}.{subgroup}.{wg}.ensdao.eth
                name.q3-23.personnel.metagov.ensdao.eth
                       servicer.q3-23.stream.ensdao.eth
                member.servicer.q3-23.stream.ensdao.eth
        .......etc.

If ENS isn’t setting the standard for name use, then who will?

[meta8.eth]

I think I was the only proposal in the last Grant round that actually utilised subdomains and even a sub sub domain in which I nominated for any potential pay funding.

And also the key term amongst all of this debate needs to be highlighted that:

Investing > Spending

For example, Nick himself asked Vitalik for funding for ENS…i for one at pretty certain that Vitalik new that he was investing in the future of Ethereum. So perhaps this needs to be the mindset of more delegates moving forward.

Guarding the keys/vaults to this virtual castle for too long isn’t going to get us very far…in a world whereby we vouch for pure trust-less decentralisation, we cannot forget the moments “trust” and belief in people doing the right thing.

Like a farmer who has no access to water for his crop until the owner of the dam upstream releases the supply, much the same is for the builders and creative innovators in the barren sand Pitt of Web3.

Don’t be the guy who thinks the dam was built all by itself…

[AvsA]

I’ve created a new thread to announce the EP number and snapshot vote:

[EP4.7] Create Provider Streams is now live on snapshot

The service provider ENS Proposal has now a EP number of 4.7 and is now live on snapshot! Previous Temp Check Snapshot

I also replied on the matter of 1M ENS support

[EP4.7] Create Provider Streams is now live on snapshot

A comment on the 1M ENS requirement: While it’s true that this is purposefully a high limit, It’s not at all unattainable. In fact, every single winning snapshot proposal has achieved that (including every steward that ever got elected), and it’s also the minimum quorum on tally. It’s also much higher than any one delegate can achieve. So I think a 1M ENS support is a good indicative of a broad ecosystem support.