Referendum #105

Proposal: OpenZeppelin x Polkadot Ecosystem Growth

Medium Spender
7 Comments
Executed
  • Content
  • AI Summary
Reply
Up 3
Share
Request
43.88KDOT
Status
Decision28d
Confirmation1d
Attempts
1
Tally
96.5%Aye
57.5%Threshold
3.5%Nay
Aye
13.43MDOT
Nay
490.2KDOT
  • 0.0%
  • 0.0%
  • 0.0%

Threshold

Support(0.69%)
8.03MDOT
Issuance
1.17BDOT
Votes
Nested
Flattened
Calls
  • Call
  • Metadata
  • Timeline6
  • Votes Bubble
  • Statistics
Comments
Sort by
Oldest
[Deleted Account]

Within the first 30 days begin sourcing a 3 dedicated member open-source development team that will work with Parity and the Polkadot community to define a roadmap

What will be the process for working with the Polkadot community to determine this roadmap? Super keen to see more teams coming into the ecosystem and tackling challenges that the ecosystem faces - however, to date we are missing consensus on "what" it is that needs to be built.

Thinking in particular regarding the generic pallets you'll be developing - how do we ensure that you won't be duplicating work that e.g. Tanssi are doing as part of their generic runtime packages? I would hate to see multiple good teams working on the same thing when they could be tackling ecosystem pain points.

Reply
Up 3
[Deleted Account]

5G67C7ZVqWysL79ExVA6AtSo3M1mrxC7DPiPmxE5qQye4mxp

Reply
Up