📪FOUNDATION STACK

WEU foundation believes that wealth distribution & decentralization doesn’t come just by building the decentralised technology and it takes more inorder to make the world more Decentralized |sharable.

Every layer runs on different consensus as to solve the problem of human control over decentralized technology. These five consensuses together make out the most efficient consensus which is being implemented for the middleware market like ORCHESTRA.

Here is our Decentralized stack which we believe bring sharable economy to the people of the planet Earth.

LAYER 1

ORGANISATION LAYER

This layer is referred as organising layer. Where team and community participate to organise the foundation in a structure and a defined way. This layer is managed by the core team as they take decision for adding up more members in the core or not.

Organisational layer management takes care of other roles salaries as it cannot be measured through proof of code. And the data will ledger publicly on GitHub as well INPUT received on dashboard.

PROOF OF CONCEPT

PROOF OF COMMUNITY

Proof of community is a open consensus and verifying software. Where after attaining few badges a developer or a researcher can apply for the core team. existing core team vote in order to take care it on recruiting software which consist of their id rating , no. of PRs done , quality ratio , and definately more than 66 % of consensus in agreement of the profile.

And for other non tech profiles it just agree on 75% consensus.

---

This layer basically a interim functionality added in core / alpha contributors dashboard where they can check who has applied for core contributor from the variable contributor . There can just check the id who applied for the role , and can either mark yes / no .

A dashboard simply carries the contributor data, their badges , PR done by them , PR incentive claim/or not , repositories link , tags mentioning the specific topics so whenever a issue will be created with the same tag there profile get a notification . A token balance dashboard for how much they have mint, burn or staked . A proposal dashboard where they can see current open proposal and in which one, they had participated or not.

👍A core contributor dashboard carries an additional feature of selecting the person in core or not.

👍 A evaluator dashboard carry a additional feature of their TIMECHAIN activation for evaluation , issues they have to audit/evaluate and slashed amount due to inactivity or lack of finding the bug in the code .

LAYER 2

INCENTIVE LAYER

Incentive layer take care of the incentive distribution based on how much PRs, issues resolved or repos build by the community. Incentives are directed to the dashboard of the member and these incentives are generated in INPUT(INT).

Incentive layer through the core developers consensus take care of the balancing of the developer minting token (INT).

A community can participate for solving issue and building repos with mentioning participants to build the community, so that the incentives can be evenly distribute between the builders of the particular same like we see on GitHub.

PROOF OF CONCEPT

PROOF OF CODE

Proof of code is a zero knowledge ids infrastructure managed on peer to peer network for code collaboration such as radicle, build on did infrastructure such as Ethereum Attestation Service and other DID infrastructure. Where incentive will be decided by core team posting the reward for the particular PRs , issues or building repos.

Generation Development Incentives (GDI) are basically incentive for PRs pushed by the community to the github/software. GDI for particular PRs in the initial days are decided by the core team consensus . Once the community starts growing it will be majorly algorithmic + minting value remaining in the vault + core team consensus.

*Check out docs. to know more about INPUT

---

Proof of code is basically have a simple pipeline -

step 1- Choose a issue to resolve .

step 2 - Push the issue in progress , so other developers or researchers can get notified . So they can choose to work on other issue ( this condition is only for variable contributors)

step 3 - Once the PR is done , push the PR in submission to review

step 4 - Once PR will be verified by an evaluator, they can push the PR into final submission for review by all the evaluators within that timechain and generate a incentive based on their evaluation or if not they can send it to unapproved tasks or core contributor programmae based on the conditions mentioned .

step 5 - At the end of every timechain , paid out will be done to the contributor by council members approval .

LAYER 3

TECHNOLOGY LAYER

Technology layer is where self-sovereign tech stacks are build and used to build self-operating applications. In WEU Foundation technology layer anyone can participate who wants to take part in building , researching of existing tech stack or wants to propose or build their own self sovereign applications.

Technology layer basically derives what protocols are currently building and on what stage they are developing right now. IN which protocol what is the need and what kind of development is required in it.

PROOF OF CONCEPT

PROOF OF BUILDING

Proof of building let anyone build solutions related to self sovereign applications. Anyone can take participation in the technology layer either by contributing through code , research and applications.

Proof of building let the community to be the part of the foundation and let them take part in the operations and governance of the foundation. Once the dashboard be there they can go any protocol and see on what stage currently it is running so and can solve , build solutions within the protocol while opting/reading/connecting with the rest of the community in the forum .

---

In proof of building

A community or individual can propose the idea in the discussion forum , discuss the implementation or ask for review from the community

If there is a idea which you believe will work out and you are firm about it, you can apply for first brick grant program and become a sub-protocol/entropy within the foundation .

LAYER 4

ECONOMICAL LAYER

Economical layer build on weightage method, where the token owners can take participation in the governance from different protocols . Economical stack let investors take participation in the ico , public or private investment of different protocols which all the transaction been done on chain in order to keep it transparent.

As different protocols have their different type of governance, they are free to add any economical theme within the foundation as well as they can follow the economic structure of weu foundation.

As for the developer stack they can mint tokens through their ZK ID based on proof of building but at the same time they can include an interim system to build their protocol but have to publish their monthly expense report on chain.

PROOF OF CONCEPT

PROOF OF STAKE/DELEGATED POS

Proof of stake or DPOS basically let the users to delegate the stake to the pool guardians for DPOS which basically works on REVERSE INCENTIVE MECHANISM will be implemented in v2 governance .

Users can participate through buying the certain protocol token or minting the devp. token through proof of building and take participation in the governance of the protocols . bINT and INT is used to take participation in the elections .

Community can earn certain apy% in by staking directly in the pools or by delegating to the pool guardians where guardians might take their cuts in order to execute various functions within the protocol and taking decisions in the governance in the users behalf.

Developers can stake INT till the stablecoin minting address goes live or even after it While staking their tokens after minting goes live they can boost by staking these tokens through governance equilibrium and multiply there voting power .

*check docs for DPOS mechanisms(v2) , reverse incentive mechanism(v2) , governance eq.

LAYER 5

CONSENSUS LAYER

Consensus layer basically takes care of all the development, grants , foundation pools, voting on major issues in the protocols , meetups and hackathons through voting by the community organising the foundation at the top layer.

PROOF OF CONCEPT

PROOF OF AGGREGATE CONSENSUS

Proof of aggregate consensus is headed by governing bodies heading the foundation by delegating their votes for foundation pool . The pool to make a decision will need 2/3 of the council members and technical commitee to agree with their decision in order