Forming a Ring of Ethereum Architects


#1

Short Version:
Ethereum Architect (EA) is a new role in Ethereum Community.

EA keeps in mind most core projects in ethereum ecosystem with focus on their interoperability, performance and specific features. EA’s role in a project is to integrate different modules into working product and compare similar modules to pick the most suitable one.
EA is financially self-sufficient: you are able to earn money even if you are not part of any other project.

In Ethereum Community EA takes care about core project’s UX, interoperability and integrations and creates RFEs in that projects in order to push necessary improvements. In Ethereum Governance (Signaling) his role is to identify influencers (projects and developers).

Ring of Ethereum Architects supports, summarizes and promotes community work done by its members.

Long Version:
Many of the ethereum projects are developer driven grassroot projects. Developers are acting independently and get revenue from community attention generated by their project. Moreover nobody in Ethereum likes hierarchies and external management, nothing can be enforced. We are like that cats, that don’t like to be herded.
All this is an ethereum-style development process, this is our “eth-ish” lifestyle .

It has huge drawbacks. Ethereum Ecosystem is a patchwork of many loosely connected independent projects. There is no direct incentives for developers to spend their time working on interoperability and integrations into other projects. In old-school world there is a management for that, but we don’t like it, we like to have it “eth-ish”. Therefore we don’t have any role in our community taking care about seamless integration of the parts into one smoothly working platform.

Ethereum Architect (EA) is exact the full-time role for that purpose: he/she …

  • knows almost all sub projects in ethereum space (and makes his knowledge public),
    • … this includes project’s features, performance, interoperability and future development.
  • proposes standard architectures and solutions, i.e. for external customer needs.
  • creates a EIP’s in particular projects to improve their interoperability and UX, based on own experience in customer’s projects.
  • represents customer needs in technical ethereum discussions.
  • compares similar projects creating the “best-of” lists.
  • provides quality reports and promotes best devs or projects or makes list of their flaws public.

EA role meant to be “eth-ish”. It means an EA should not pretend to manage other people, but because of his broad knowledge of ethereum ecosystem and community, this role is quite influential. “Eth-ish” means also working active and independently. It means also, the role is self-sufficient: as an Ethereum Architect you are able to earn money even if you are not part of any other project.

EA is like a Software Architect but it is more, because EA actively takes care about ethereum as a platform in general. Moreover, he/she brings projects, developers and stakeholder together because of knowledge of the community and ecosystem.

Because of wide knowledge of ethereum ecosystem and community, EA plays important role in Ethereum Governance (Signaling): EA identifies influential projects and people, which is essential to interpret signals. EA signals customer needs into ethereum community and project needs to each other.

Any thoughts?


#2

This is an interesting approach, and much-needed! I appreciate how you incorporate values into this ring.

As an aside, I see three types of rings emerging:

  • type of EIP or dapp e.g. wallet ring
  • technique or process e.g. UX ring
  • type of work e.g. architects, philosophers, attorneys

#3

As an aside, I see three types of rings emerging:

  • type of EIP or dapp e.g. wallet ring
  • technique or process e.g. UX ring

Why do you put EIP and dapp/walet together and UX in separate category?

As an aside, I would re-think EIP categorisation to separate Standard from DesignPattern.

  • A Standard MUST be stricktly followed by all implementors. Once released and implemented, it can’t be changed. Therefore it needs cautios design and broad discussion. (f.e.: ERC20).
  • A DesignPattern is only a recomendation. It needs roughly consensus and can be changed later. The process should be RFC like.

Personally, I try to read and understand every new Standard, proposed in Ethereum Space, because it has lasting and general impact. Not the same about DesignPattern: I read them if I need them.

Unfortunately, I am totally overhelmed by EIP proposals that pretend to be Standards but are DesignPatterns actually. They do not need so much timely attention, but they claim it.

It is a pain and we need to target it, IMHO.
Possibly by better categorisation for EIPs, applied by EIP editors.


#4

I am still thinking about realtionship between “Ethereum Architect (EA)” role and “XYZ Manager”.
Even EA should solve some typical problems, that the classical manager would solve, I would avoid to give the EA role the “Manager” name.

Nomen est omen. Using term “manager” to describe EA role, we will import old problems from hierarchically managed world. I would avoid it.


#5

I think I like how you put it best somewhere else, it’s more of a community management role. The EAs ensure that those in the community understand what else is out there in terms of colloboration and partnerships so Ethereum can be a more effective platform overall. We can all be so far down our silos it’s difficult to listen for these, but our EAs are superstars and can bridge those connections.

I think this honestly already happens quite well on crypto-twitter, but it’s great to discuss the importance of this role especially as we scale.


#6

@Ethernian, are you volunteering?


#7

=====
Yes, for sure.


#8

… Excellent :slight_smile:


#9

… I am just waiting few days more for feedback and then will continue with formal steps organizing the ring


#10

Interested in helping with this :slight_smile:

I have a keen focus on helping out with scalability - particularly state channels and plasma. Naturally, I can assist on the various user onboarding nuances - transaction fueling services, identity management, etherless accounts, etc…

I’m really just in favor of helping to promote any open standards :slight_smile:


#11

Great!
A lot of thanks for your help!

I will finalize forming a Ring of Ethereum Architects next days and then will start a separate topic to bring more structure into the Ring.


#12

@Ethernian working on the specification of the Ring Application Process. As someone who is interested in forming a ring I would love to hear some feedback.

An aside

As part of EthSignals this would be great :slight_smile:

We want to integrate with projects as much as possible and are working on finding appropriate projects for each signal. Being new to the space it has been pretty difficult to even know what exists out there.


#13

unsure I am understand you correctly. Do you see Ring of Ethereum Architects as a part of EthSignals?

hmm… I would disagree… I see them on different levels: EthSignals creates an infrastructure and methodology to understand whats going on in community related to any possible topic. In particular in domain of Ethereum Architects or Ethereum Wallet Developers or any other ring.

Any Ring will use EthSignals but not be part of it.


#14

That is how I see it as well. Sorry for the confusion.

One thing that would be helpful for us is as Ethereum Architects identifies projects, some of those could be analysed for integration. One example is Slockit.io gas voting. They are actively working on a voting mechanism never before seen. Luckily, we found them because Phil found them. Without this connection we may have never found this amazing project. We are always interested in integrating more and varied signals and hope to keep on top of upcoming technology in this area.


#15

Great idea. Goes very much with the market demand for this type of the service. With wise realisation should help in identification of real skills and knowledge among tonns of self elected gurus.
I support the idea to build the structured approach as it will simplify the usage of the technology and clarify the gaps for the community.