This repository has been archived by the owner on Jul 31, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
cleanIssue.json
4565 lines (4565 loc) · 367 KB
/
cleanIssue.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
[
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/120",
"issue_number": 120,
"title": "Draft Project Idea: Impact Calculator 🌱",
"user": {
"name": "JSeiferth",
"avatar": "https://avatars.githubusercontent.com/u/43515441?v=4"
},
"tag": [
{
"name": "Draft Project Idea",
"desctiion": "Concept for a project or type of project to build within the Optimism Ecosystem"
}
],
"body": "**What is a Draft Project Idea?**\n\nA Draft Project Idea is a concept for a project within the Optimism ecosystem that is generally considered valuable but has not yet been fleshed out into a clearly defined product. Draft Project Ideas may be converted into Ecosystem Project Ideas as they are explored further and more thoroughly specified.\n\n---\n\n## Summary\nThe Impact Calculator is designed to streamline the evaluation of projects in the Optimism RetroPGF voting process by quantifying their impact through various metrics. This tool is expected to transition the grantmaking process from individual project evaluation to a more strategic overview, helping to maintain and improve the ROI of grant allocations.\nThe idea for this project is to built a simple prototype to test out the idea. \n\n\n\n\nYou can find a Figma mock up with some more detailed descriptions [here](https://www.figma.com/file/OS8DSbKyuiYPqcRTmmhTIM/Impact-Calculator-%F0%9F%8C%B1?type=design&node-id=0%3A1&mode=design&t=4qGwi0ZEsvOMlxkF-1) \n\nDive deeper into impact vectors by checking out Carl's post on [levels of the game](https://mirror.xyz/cerv1.eth/HikrWg-CneYoHruCON5gCi6BL7R71TEBpdJjgqon9M8) and [Ecosystem Impact Vectors](https://mirror.xyz/cerv1.eth/qL9YKLN9-dBzM89qKaZYgHK2ccpZy2XLPz2Z1PObwCg), or play around with [OpenSource Observer](https://www.opensource.observer/).\n\nIf you're interesting in tackling this project idea, come [join this Telegram group\n](https://t.me/+B5likgTv8sk3MWVi)\n## Possible Features\n1. Impact Vector Selection: Allows users to choose from various impact vectors with descriptions and creator names, search functionality, and options to view detailed pages or add vectors to a ballot.\n2. Ballot View: A ballot system where users can select or deselect impact vectors and edit their configurations. This includes a graphical representation of the distribution of funds among projects.\n3. Detailed View: Each impact vector has a detailed view, including a name, description, creator, and a link to GitHub. Users can visualize the impact vector and configure it.\n4. Configuration Option: Users can set a scale or weight to deterimine how flat or skewed the eventual distribution of tokens to projects should be.",
"created_at": "2024-01-16T12:56:58Z",
"updated_at": "2024-01-16T17:08:27Z",
"comment": 1,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/120/reactions",
"total_count": 3,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 3
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/119",
"issue_number": 119,
"title": "- Intentions of backend tools",
"user": {
"name": "philliprossii7",
"avatar": "https://avatars.githubusercontent.com/u/71346231?v=4"
},
"tag": [],
"body": "- Intentions of backend tools \n\n_Originally posted by @philliprossii7 in https://github.com/l2beat/l2beat/pull/2531#discussion_r1449948597_",
"created_at": "2024-01-12T07:34:11Z",
"updated_at": "2024-01-12T07:34:11Z",
"comment": 0,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/119/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/117",
"issue_number": 117,
"title": "RFP: Superchain Bridge",
"user": {
"name": "bdresser",
"avatar": "https://avatars.githubusercontent.com/u/1016190?v=4"
},
"tag": [
{
"name": "Foundation Mission (RFP)",
"desctiion": "A request for proposals for a specific work item."
}
],
"body": "## Foundation Mission (RFP) – Superchain Bridge RFP\r\n_To take on this project, submit a proposal to this thread by December 15. Read more about Missions [here](https://gov.optimism.io/t/token-house-missions/5881)._\r\n\r\n* **S5 Intent**: Technical Decentralization\r\n* **Foundation Mission (RFP):** Host an open source user interface (UI) that allows users to move assets to/from Ethereum (L1) to any OP Chain (L2) in the Superhain (OP Mainnet, Base, PGN, Zora, Mode, etc.) via the [standard bridge](https://community.optimism.io/docs/developers/bridge/standard-bridge/#) and OP Chain (L2) to OP Chain (L2) when interop is available.\r\n* **Proposal Tier:** [Fledgling](https://gov.optimism.io/t/collective-trust-tiers/5877) \r\n* **Baseline grant amount**: 200K OP\r\n* **Accepting one or multiple proposals:** Multiple \r\n* **OP Labs or Optimism Foundation Sponsor**: Zain (@zainbacchus)\r\n* **Submit by**: December 15th at 19:00 GMT\r\n* **Selection by**: December 29th at 19:00 GMT\r\n\r\n### **How will this Foundation Mission (RFP) will help accomplish the above Intent?**\r\n\r\nThis RFP introduces a Superchain Bridge interface which acts as the foundation for users to move tokens to / from any OP Chain in the Superchain using the canonical standard bridge in the OP Stack.\r\n\r\nOptimism is leaning on its ecosystem to bootstrap access to the protocol. Not running our own frontend increases censorship resistance and decentralization, but also helps us bootstrap a distributed ecosystem.\r\n\r\nAs such, this mission will contribute to a more resilient bridging ecosystem for the Superchain.\r\n\r\n\r\n### **What is required to execute this Foundation Mission (RFP)?**\r\n\r\nThe Superchain Bridge Interface allows users to bridge to / from any OP Chain in the Superchain from L1 Ethereum using the [standard bridge](https://community.optimism.io/docs/developers/bridge/standard-bridge/#). Once the [MVP of low latency L2 to L2 message passing](https://stack.optimism.io/docs/understand/explainer/#low-latency-l2-to-l2-message-passing) is live (est. mid 2024), the Superchain Bridge interface should also allow users to bridge between OP Chains.\r\n\r\nCompleting this RFP requires building an open source frontend that allows users to bridge to / from any OP Chain in the Superchain. The frontend should be fully open-source and should allow for future iterations of the functionality. This RFP requires both designs and implementation.\r\n \r\nFor this RFP, the Optimism Foundation will accept up to two submissions. Multiple frontends will maximize the likelihood of success and improve the resilience of the system.\r\n\r\nThe target grant reward for each submission will be 200k OP. Teams should discuss the solution criteria below with the Foundation, and may arrive at a different mutually agreeable grant amount dependent on the scope of their work.\r\n\r\n### **Solution Criteria:**\r\n\r\nCore functionality of the Superchain Bridge interface:\r\n\r\n**Wallet connection**\r\n- As a user I can use either an EOA or Smart Contract Wallet to deposit / withdraw from the bridge interface. The wallet connect should include but not limited to support browser injected wallets like Metamask, Coinbase Wallet, Rainbow Wallet, as well as WalletConnect v2 and smart contract wallets.\r\n\r\n**Token bridges**\r\n- As a user I can bridge from L1 to L2 Mainnets / Testnets for any OP Chain in the Superchain (e.g. OP, Base, PGN, Zora, Mode etc.)\r\n- As a user I can bridge from L2 to L2 Mainnets / Testnets for any OP Chain in the Superchain (e.g. OP, Base, PGN, Zora, Mode etc.)\r\n- As a user I can specify the destination address I want to transfer tokens to\r\n\r\n**Token lists**\r\n- As a user I can use my preferred token list to find which tokens I want to bridge. The token lists should include but should not be limited to the [Superchain Tokenlist](https://community.optimism.io/docs/developers/bridge/standard-bridge/#the-superchain-token-list). \r\n- As a user I can bridge any arbitrary [standard ERC-20](https://community.optimism.io/docs/developers/bridge/standard-bridge/#depositing-erc20s) using the bridge interface\r\n\r\n**3rd party bridges**\r\n- As a user I can find a list of supported 3rd party bridges when bridging to/from a non-Ethereum / OP Chain blockchain\r\n\r\n**Account history**\r\n- As a user I can view my deposits / withdrawals for any OP Chain in the Superchain (e.g. OP, Base, PGN, Zora, Mode etc.)\r\n- As a user I can initiate the two-step withdrawal process for any relevant withdraws\r\n\r\n**Query parameters** \r\n- As a user I can create a link that points to a specific network on the bridge (e.g. bridge.org/base)\r\n- As a user I can create a link that points to a specific token on a specific network on the bridge (e.g. bridge.org/base/USDC).\r\n\r\n**Block explorer**\r\n- As a User I can select my preferred block explorer for viewing transaction confirmation. This should include but not limited to support OnceUpon, Blockscout, and Etherscan (when available).\r\n\r\n**i18n**\r\n- As a user I can select my preferred language to interact with the bridge interface including but not limited to English (EN), Hindi (HI), Arabic (AR), German (DE), Spanish (ES), French (FS), Indonesian (ID), Japanese (JA), Vietnamese (VI), Chinese Simplified (ZH-CN), Chinese Traditional (ZH-TW), Korean (KO), Polish (PL), Portuguese (PT), and Thai (TH)\r\n\r\n\r\n**Compliance**\r\nThe Superchain Bridge Interface should include an appropriate user legal agreement and risk disclosures, which will be subject to evaluation and confirmation by the Foundation. The Superchain Bridge Interface should also implement appropriate compliance measures to prevent it from being used in violation of applicable laws. The compliance measures implemented by a grantee will be subject to evaluation and confirmation by the Foundation. Prior agreed compliance costs incurred by the grantee will be reimbursed by the Foundation for at least one year following launch. \r\n\r\n\r\n\r\n**Superchain Registry**\r\nThe Superchain Bridge Interface should only include OP Chains in the Superchain and update to include new OP Chains as they come online. \r\n\r\n\r\nThe user interface must use the [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry/tree/main/superchain/configs/mainnet) and relevant [CCTP bridges](https://developers.circle.com/stablecoin/docs/cctp-protocol-contract) to determine the canonical bridges that are supported. Furthermore, the UI should provide instructions for how the user can verify using their wallet that they are interacting with the canonical bridge for the respective OP Chain.\r\n\r\n\r\n\r\n**Service level agreement**\r\nThe bridge interface should continue to support adding new OP Chains as they come online. To ensure this happen, the RFP proposer must agree to a service level agreement that governs the ongoing maintenance, support, and enhancement of the Bridge UI, including but not limited to the addition of new operation chains, bug fixes, updates, and improvements as outlined in the RFP. Past the 1 year service agreement, through Optimism’s Retroactive Public Goods Funding, we expect interface maintainers will be rewarded based on the reliability of the interface.\r\n\r\n\r\n### **How should the Foundation measure progress towards this Foundation Mission (RFP)?** \r\n\r\nProgress can be measured based upon the completion of the following milestones:\r\n\r\n- Specification for implementation, design approach, and architecture for the functionality listed above.\r\n- Open-source code repository to observe progress over time\r\n- Launching Phase 1: L1 <> L2 bridging\r\n- Launching Phase 2: L2 <> L2 bridging\r\n- 1 year toll gate: Service level agreement for bridge has been hit \r\n\r\n\r\nThese milestones mark the completion of the proposal. \r\n\r\n## **How should RetroPGF badgeholders measure impact upon completion of this Foundation Mission (RFP)?**\r\n\r\n- Volume of bridging transactions (by distinct addresses / USD volume) that is triggered through this interface\r\n- Share of bridging transactions (by distinct addresses / USD volume) that is triggered through this interface compared to all other onramps\r\n\r\n\r\n\r\n## Application instructions\r\n\r\n_To apply for this RFP, please complete the form in the expandable section below and leave your response as a comment on this issue thread below. Submissions will be open until Dec 15, at which time the Foundation will review all submissions and select up to three individuals/teams to complete the work defined here._ \r\n\r\n<details>\r\n <summary>Submission form</summary>\r\n\r\n_Copy the entire application below and leave a comment on this issue with your answers completed. A representative from the Optimism Foundation may reach out using the contact info provided to request more information as necessary._\r\n\r\n## Foundation Mission (RFP) Application\r\n\r\n**Please verify that you meet the qualifications for submitting at the above [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877/2)**\r\n\r\n* **Alliance Lead:** Please specify the best point of contact for your team \r\n* **Contact info:** \r\n* **L2 recipient address:** \r\n* **Please list the members of your Alliance and link to any previous work:**\r\n\r\nRead more about Alliances [here](https://gov.optimism.io/t/season-4-alliance-guide/5873)\r\n\r\n--- \r\n\r\n**What makes your Alliance best-suited to execute this Mission?**\r\n- [...]\r\n- [...]\r\n\r\n**Please describe your proposed solution based on the above Solution Criteria (if applicable):**\r\n- [...]\r\n- [...]\r\n\r\n\r\n**Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each peice of work:**\r\n- [...]\r\n- [...]\r\n\r\n**Please define the [critical milestone(s)](https://gov.optimism.io/t/grant-policies/5833) that should be used to determine whether you’ve executed on this proposal:** \r\n- [...]\r\n- [...]\r\n\r\n**Please list any additional support your team would require to execute this mission (financial, technical, etc.):** \r\n- [...]\r\n- [...]\r\n\r\n**Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant:** _(Note: there is no guarantee that approved Missions will receive up-front cash grants.)_\r\n- [...]\r\n\r\nPlease check the following to make sure you understand the terms of the Optimism Foundation RFP program:\r\n\r\n- [ ] I understand my grant for completing this RFP will be locked for one year from the date of proposal acceptance.\r\n- [ ] I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant\r\n- [ ] I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md#valid-proposal-types)\r\n- [ ] I confirm that I have read and understand the [grant policies](https://gov.optimism.io/t/token-house-grant-policies/5833)\r\n- [ ] I understand that I will be expected to following the public grant reporting requirements outlined [here](https://gov.optimism.io/t/suggested-public-reporting-requirements-for-grantees/4176)\r\n\r\n-- end of application --\r\n\r\n---\r\n\r\n</details>",
"created_at": "2023-12-06T01:53:40Z",
"updated_at": "2024-01-14T22:43:19Z",
"comment": 16,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/117/reactions",
"total_count": 8,
"+1": 6,
"-1": 0,
"laugh": 0,
"hooray": 1,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 1
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/116",
"issue_number": 116,
"title": "RFP: Superchain Safe",
"user": {
"name": "bdresser",
"avatar": "https://avatars.githubusercontent.com/u/1016190?v=4"
},
"tag": [
{
"name": "Foundation Mission (RFP)",
"desctiion": "A request for proposals for a specific work item."
}
],
"body": "## Foundation Mission (RFP) – Superchain Safe (ex. Gnosis Safe) RFP\r\n\r\n_To take on this project, submit a proposal to this thread by December 4th. Read more about Missions [here](https://gov.optimism.io/t/token-house-missions/5881)._\r\n\r\n* **S5 Intent**: Grow the Superchain\r\n* **Foundation Mission (RFP):** Host an open source user interface (UI) that allows users to access Safe deployments on any OP Chain (L2) in the Superchain (OP Mainnet, Base, PGN, Zora, Mode, etc.)\r\n* **Baseline grant amount**: 150k OP\r\n* **Accepting one or multiple proposals:** Multiple \r\n* **OP Labs or Optimism Foundation Sponsor**: Zain (@zainbacchus)\r\n* **Submit by**: Dec 4th at 19:00 GMT\r\n* **Selection by**: Dec 8th at 19:00 GMT\r\n\r\n### **How will this Foundation Mission (RFP) will help accomplish the above Intent?**\r\nA common pain point for developers on OP Chains as well as Chain operators themselves is not having the Safe functionality. This RFP aims to remedy this by expanding access to the Safe functionality and interface to all OP Chains thereby reducing developer and operator friction. \r\n\r\nThe scope of this RFP will be to introduce a Superchain [Safe interface](https://github.com/safe-global/safe-wallet-web) which acts as the foundation for users to use the [Safe functionality](https://github.com/safe-global) across all testnets and mainnets in the Superchain\r\n\r\nAs such, this mission will contribute to a more resilient and secure developer ecosystem for the Superchain.\r\n\r\n### **What is required to execute this Foundation Mission (RFP)?**\r\n\r\nThe deployment (if required) of Safe Contracts (ex Gnosis Safe) and backend services for all mainnet and testnet OP Chains in the Superchain, and supporting Superchain Safe interface. \r\n\r\n### **Solution Criteria:**\r\n\r\nCore functionality of the Superchain Safe RFP include deployment (if required), backend services configuration (if required), Superchain Safe UI, and ongoing maintenance. \r\n\r\n**1. Deployment and configuration**: deploy Safe contracts (if required), and configure the latest Safe components on adequate infrastructure for 2 environments (Stage and Production)\r\n\r\n- Safe Contract deployments: As part of the RFP, we expect deterministic deployment of the collection of Safe contracts (https://github.com/safe-global/safe-contracts) on the following OP Chain mainnets and testnets: Zora, Public Goods Network, Mode, Lyra, Orderly, and Ancient8 as well as any future OP Stack Chain (total of 10 deployments). With the launch of the SafeL2 as a predeploy at 0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7 in the OP Stack estimated to launch Q1 2024, as new chains come online no deployment of Safe contracts will be needed. \r\n\r\n- Safe Backend Components: For all chains, we expect the deployment and configuration of Safe Backend Components (as outlined in https://github.com/safe-global/safe-contracts), as well as any respective frontend updates and maintenance as needed\r\n\r\n**2. Superchain Safe UI:** Design, configuration and implementation of an open-sourced Superchain specific Safe UI using the [default Safe web interface](https://github.com/safe-global/safe-wallet-web) that supports all OP Chain testnet and mainnets. DNS to be owned by Optimism. \r\n\r\n**3. Maintenance:** perform regular Safe updates, infrastructure monitoring & optimization, new features enablement (according to requests from OP Labs or Optimism Foundation). See service level agreement below. \r\n\r\n**4. Additional considerations:** \r\n\r\n- Initial setup maintenance: We will reimburse the infrastructure cost for 10 OP Stack Chains (incl. 2 staging environments each) for 1 year (capped at $30k)\r\n\r\n- Superchain Registry: the Superchain Safe Interface should only include OP Chains in the Superchain – referring to the [Superchain Registry](https://github.com/ethereum-optimism/superchain-registry/tree/main/superchain/configs/mainnet) to determine the canonical chains that are supported.\r\n\r\n- Service level agreement: the Superchain Safe interface should continue to support adding new OP Chains as they come online. To ensure this happen, the RFP proposer must agree to a service level agreement that governs the ongoing maintenance, support, and enhancement of the Superchain Safe UI, including but not limited to the addition of new operation chains, bug fixes, updates, and improvements as outlined in the RFP. Past the 1 year service agreement, through Optimism’s Retroactive Public Goods Funding, we expect interface maintainers will be rewarded based on the reliability of the interface. Expected Monthly Uptime 99% (i.e. ~7.31hrs of downtime / month)\r\n\r\n### **How should the Foundation measure progress towards this Foundation Mission (RFP)?** \r\n\r\nProgress can be measured based upon the completion of the following milestones:\r\n\r\n- Specification for implementation, design approach, and architecture for the functionality listed above.\r\n- Open-source code repository to observe progress over time\r\n- Successful deployment and configuration of Safe contracts and services for at least 10 OP Chains within the scope of this RFP\r\n- 1 year toll gate: Service level agreement for interface has been hit \r\n\r\n**How should RetroPGF badgeholders measure impact upon completion of this Foundation Mission (RFP)?**\r\n\r\n- Number of OP Chains successfully integrated with the Superchain Safe UI\r\n- Number of OP Stack Chains with Safe contracts deployed within the scope of this RFP\r\n\r\n</details>\r\n\r\n## Application instructions\r\n\r\n_To apply for this RFP, please complete the form in the expandable section below and leave your response as a comment on this issue thread below. Submissions will be open until December 4, at which time the Foundation will review all submissions and select one individual/team to complete the work defined in this RFP._ \r\n\r\n<details>\r\n <summary>Submission form</summary>\r\n\r\n_Copy the entire application below and leave a comment on this issue with your answers completed. A representative from the Optimism Foundation may reach out using the contact info provided to request more information as necessary._\r\n\r\n## Foundation Mission (RFP) Application\r\n\r\n* **Individual / Team Name:** Please specify the best point of contact for your team \r\n* **Contact info:** \r\n* **L2 recipient address:** \r\n* **Please list the members of your Alliance and link to any previous work:**\r\n\r\n--- \r\n\r\n**What makes you / your team best-suited to execute this Mission?**\r\n- [...]\r\n- [...]\r\n\r\n**Please describe your proposed solution based on the above Solution Criteria (if applicable):**\r\n- [...]\r\n- [...]\r\n\r\n**Please outline your step-by-step plan to execute this Mission, including expected deadlines (if relevant) to complete each component:**\r\n- [...]\r\n- [...]\r\n\r\n**Please define the critical milestone(s) that should be used to determine whether you’ve executed on this proposal:** \r\n- [...]\r\n- [...]\r\n\r\n**Please list any additional support your team would require to execute this mission (financial, technical, etc.):** \r\n- [...]\r\n- [...]\r\n\r\n**Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant:** _(Note: there is no guarantee that approved Missions will receive up-front cash grants.)_\r\n- [...]\r\n\r\nPlease check the following to make sure you understand the terms of the Optimism Foundation RFP program:\r\n\r\n- [ ] I understand my grant for completing this RFP will be locked for one year from the date of proposal acceptance.\r\n- [ ] I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant\r\n- [ ] I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md#valid-proposal-types)\r\n- [ ] I confirm that I have read and understand the [grant policies](https://gov.optimism.io/t/token-house-grant-policies/5833)\r\n- [ ] I understand that I will be expected to following the public grant reporting requirements outlined [here](https://gov.optimism.io/t/suggested-public-reporting-requirements-for-grantees/4176)\r\n\r\n-- end of application --\r\n\r\n",
"created_at": "2023-11-30T16:53:06Z",
"updated_at": "2023-12-07T22:05:08Z",
"comment": 5,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/116/reactions",
"total_count": 1,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 1,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/115",
"issue_number": 115,
"title": "RFP: Proof of Attendance Testnet Faucet",
"user": {
"name": "bdresser",
"avatar": "https://avatars.githubusercontent.com/u/1016190?v=4"
},
"tag": [
{
"name": "Foundation Mission (RFP)",
"desctiion": "A request for proposals for a specific work item."
}
],
"body": "## Foundation Mission (RFP) – Proof of attendance testnet faucet \r\n_To take on this project, submit a proposal to this thread by December 8. Read more about Missions [here](https://gov.optimism.io/t/token-house-missions/5881)._\r\n\r\n* **S5 Intent**: Grow the Superchain\r\n* **Foundation Mission (RFP):** Build a way for hackathon participants to claim larger testnet funds from in person hackathons via the [Superchain Faucet](https://app.optimism.io/faucet)\r\n* **Proposal Tier:** [Ember](https://gov.optimism.io/t/collective-trust-tiers/5877) \r\n* **Baseline grant amount**: 30K OP\r\n* **Accepting one or multiple proposals:** One \r\n* **OP Labs or Optimism Foundation Sponsor**: Zain (@zainbacchus)\r\n* **Submit by**: December 8th at 19:00 GMT\r\n* **Selection by**: December 15th at 19:00 GMT\r\n\r\n### **How will this Foundation Mission (RFP) will help accomplish the above Intent?**\r\n\r\n[Superchain Faucet](https://app.optimism.io/faucet) is a developer tool that allows developers to get free testnet ETH to test and build apps on testnet OP Chains like Base Sepolia, OP Sepolia, PGN Sepolia, Zora Sepolia, and other OP Chains in the Superchain. \r\n\r\nDevelopers who have an Optimist NFT, Gitcoin Passport attestation, or WorldID are able to get larger drips from the faucet. \r\n\r\nA common pain point for hackathon participants is not having credentials yet for larger drips. This RFP aims to expand access to larger testnet fund drips to participants at in person hackathons and reduce developer friction when building on OP Chains. \r\n\r\nAs such, this mission will contribute to a more resilient developer ecosystem for the Superchain.\r\n\r\n### **What is required to execute this Foundation Mission (RFP)?**\r\n\r\nCompleting this RFP requires building an open source frontend that allows users to claim a proof of attendance attestation, mint an Optimist NFT, and get larger testnet fund drips. The interface should be fully open-source and should allow for future iterations of the functionality. This RFP requires both designs and implementation.\r\n, \r\nFor this RFP, the Optimism Foundation will accept one submission.\r\n\r\nThe target grant reward for the submission will be 30K OP. Teams should discuss the solution criteria below with the Foundation, and may arrive at a different mutually agreeable grant amount dependent on the scope of their work.\r\n\r\n\r\n### **Solution Criteria:**\r\n\r\nCore functionality of the claim experience includes both a flow for event maintainers and an end user flow. \r\n\r\n**Proposed maintainer flow**\r\nTo set up the claim experience, the event maintainer should require minimal setup.\r\n- Maintainer sets up a new event using an admin portal\r\n- Maintainer is provided a URL to use for the specific in person events\r\n- Maintainer sets up the URL at the respective event\r\n\r\n**Proposed end user flow**\r\nTo claim the proof of attendance attestation the flow should be sybil-resistant, gasless, and allows the user to specify their preferred address. \r\n- Developers come to the OP booth \r\n- Developer scans the QR code or URL at the OP booth\r\n- Developer completes challenge that proves they’re at the booth (eg by entering a unique code)\r\n- Developer enters their wallet address or ENS name\r\n- Developer gets a proof of attendance attestation and Optimist NFT minted to their specified address \r\n- Developer is prompted use the faucet to get larger drips from the faucet or customize their Optimist NFT\r\n\r\n**Ethereum attestation service (EAS) and Optimist NFT**\r\n[EAS](https://docs.optimism.io/identity/contracts-eas) is an open-source public good that is included as a predeploy in the OP Stack. The proof of attendance attestations should use the EAS contracts on OP Mainnet and requires a new schema for the proof of attendance attestations to be created. \r\n\r\n[The Optimist NFT](https://app.optimism.io/optimist-nft) is a fully customizable digital avatar that allows you to showcase your personality and build your onchain identity. \r\n\r\n\r\nProposed implementation of proof of attestation / auto-minting the Optimist NFT:\r\n- Create an [EAS resolver](https://docs.attest.sh/docs/tutorials/resolver-contracts) that restricts ability to create this attestation to specific addresses\r\n- This resolver should maintain a mapping(address => bool) of everyone who currently has this attestation using the onAttest and onRevoke hooks\r\n- Update [OptimistAllowlist](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/periphery/op-nft/OptimistAllowlist.sol).sol to check the resolver contract to see if user is eligible\r\n- Auto-mint feature: Automatically mint the Optimist NFT to users who have the proof of attendance attestation\r\n - Option 1: The resolver should do the above, then directly mint the NFT\r\n - Option 2: Use multicall3 to 1. Create the attestation, 2. Use `function mint(address _recipient)` function on [OptimistNFT](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/periphery/op-nft/Optimist.sol) in a single transaction\r\n\r\n### **How should the Foundation measure progress towards this Foundation Mission (RFP)?** \r\n\r\nProgress can be measured based upon the completion of the following milestones:\r\n\r\n- Specification for implementation, design approach, and architecture for the functionality listed above.\r\n- Open-source code repository to observe progress over time\r\n- Launch of the interface\r\n\r\nThese milestones mark the completion of the proposal. \r\n\r\n## **How should RetroPGF badgeholders measure impact upon completion of this Foundation Mission (RFP)?**\r\n\r\n- Number of attestations (by distinct addresses) that is triggered through this interface\r\n- Number of contracts deployed on OP Chain testnets by addresses that have attestations from this interface\r\n\r\n\r\n## Application instructions\r\n\r\n_To apply for this RFP, please complete the form in the expandable section below and leave your response as a comment on this issue thread below. Submissions will be open until June 28, at which time the Foundation will review all submissions and select up to three individuals/teams to complete the work defined here._ \r\n\r\n<details>\r\n <summary>Submission form</summary>\r\n\r\n_Copy the entire application below and leave a comment on this issue with your answers completed. A representative from the Optimism Foundation may reach out using the contact info provided to request more information as necessary._\r\n\r\n## Foundation Mission (RFP) Application\r\n\r\n**Please verify that you meet the qualifications for submitting at the above [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877/2)**\r\n\r\n* **Alliance Lead:** Please specify the best point of contact for your team \r\n* **Contact info:** \r\n* **L2 recipient address:** \r\n* **Please list the members of your Alliance and link to any previous work:**\r\n\r\nRead more about Alliances [here](https://gov.optimism.io/t/season-4-alliance-guide/5873)\r\n\r\n--- \r\n\r\n**What makes your Alliance best-suited to execute this Mission?**\r\n- [...]\r\n- [...]\r\n\r\n**Please describe your proposed solution based on the above Solution Criteria (if applicable):**\r\n- [...]\r\n- [...]\r\n\r\n\r\n**Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each peice of work:**\r\n- [...]\r\n- [...]\r\n\r\n**Please define the [critical milestone(s)](https://gov.optimism.io/t/grant-policies/5833) that should be used to determine whether you’ve executed on this proposal:** \r\n- [...]\r\n- [...]\r\n\r\n**Please list any additional support your team would require to execute this mission (financial, technical, etc.):** \r\n- [...]\r\n- [...]\r\n\r\n**Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant:** _(Note: there is no guarantee that approved Missions will receive up-front cash grants.)_\r\n- [...]\r\n\r\nPlease check the following to make sure you understand the terms of the Optimism Foundation RFP program:\r\n\r\n- [ ] I understand my grant for completing this RFP will be locked for one year from the date of proposal acceptance.\r\n- [ ] I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant\r\n- [ ] I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md#valid-proposal-types)\r\n- [ ] I confirm that I have read and understand the [grant policies](https://gov.optimism.io/t/token-house-grant-policies/5833)\r\n- [ ] I understand that I will be expected to following the public grant reporting requirements outlined [here](https://gov.optimism.io/t/suggested-public-reporting-requirements-for-grantees/4176)\r\n\r\n-- end of application --\r\n\r\n---\r\n\r\n</details>",
"created_at": "2023-11-29T19:23:26Z",
"updated_at": "2023-12-21T22:27:08Z",
"comment": 9,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/115/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/114",
"issue_number": 114,
"title": "Foundation Mission Request: Season 5 govNERDs ",
"user": {
"name": "oplavande",
"avatar": "https://avatars.githubusercontent.com/u/111033022?v=4"
},
"tag": [
{
"name": "Intent: Governance Accessibility",
"desctiion": ""
},
{
"name": "Foundation Mission (RFP)",
"desctiion": "A request for proposals for a specific work item."
}
],
"body": "## Foundation Mission Request - Season 5 GovNERD(s)\r\n\r\n**Foundation Mission Summary:** govNERDs improve governance accessibility by shepherding proposals through the feedback, approval, and voting process. This will be especially important in Season 5 as we run new processes (Delegate Mission Requests) and bring Citizens’ House governance online. **We plan to transition the govNERDs to an open contribution path before Season 6 begins.** \r\n\r\n**S5 [Intent](https://gov.optimism.io/t/collective-intents/5874):** Governance accessibility\r\n\r\n**Proposal [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877):** Ember\r\n\r\n**Baseline grant amount:** 13,500 OP per GovNERD\r\n\r\n**Should this Foundation Mission be fulfilled by one or multiple applicants:** Up to 3; 1 govNERD will be dedicated to Citizens’ House. Additional govNERDs may be added throughout the Season as needed, these govNERDs would receive a pro-rata portion of the grant for the portion of the Season they are active. \r\n\r\n**OP Labs or Optimism Foundation Sponsor:** @op_lavande\r\n\r\n**Submit by:** December 1st at 23:59 GMT\r\n\r\n**Selection by:** December 6th at 23:59 GMT\r\n\r\n**Start date:** December 7th \r\n\r\n**Completion date:** May 8th (tentative end of Season 5) \r\n\r\n**Foundation Point of Contact:** @op_lavande and @Nicca42\r\n\r\n---\r\n\r\n## Mission Request\r\n\r\n### **How will this Foundation Mission Request help accomplish the above Intent?**\r\n\r\nThe iterative nature of Optimism governance means it is constantly changing. While this should ultimately lead to improvements in the health of the overall governance system, it makes the system harder to navigate and has lowered accessibility of Optimism governance. govNERDs help shepherd proposals through the feedback, approval, and voting process while ensuring the forum is a place for the highest quality engagement. This improves governance accessibility by making it easier for proposers to effectively navigate the proposal process and for voters to find the high quality proposals that require their attention in both Houses. \r\n\r\nThis Season, we will add an additional govNERD focused on supporting RetroPGF rounds. \r\n\r\n### **What is required to execute this Foundation Mission Request?**\r\n\r\ngovNERDs will serve as neutral shepherds that ensure high quality governance proposals move through the proposal process successfully, taking over some important administrative work the Optimism Foundation has thus far fulfilled.\r\n\r\n***General Governance Process:***\r\n\r\n- Ensure voters understand relevant processes during Season 5, clarifying any ambiguities in documentation\r\n- Attend governance community calls to identify and clarify areas of confusion about Season 5\r\n- Maintain the public governance calendar during Season 5, updating and circulating as needed\r\n- Maintain the Token House and Citizen’s House Onboarding Hubs\r\n\r\n***Proposal Feedback Process:***\r\n\r\n- Ensure all Season 5 proposals follow templates, gathering feedback on templates and suggesting improvements to the Optimism Foundation. This is especially important for Delegate Mission Requests.\r\n- Address any inconsistencies or non-compliance in proposals\r\n- Identify where there is overlap in proposals and help proposers reduce overlap or collaborate\r\n- Facilitate timely feedback from voters on high quality proposals\r\n\r\n***Proposal Approval Process:***\r\n\r\n- Facilitate the review of proposals that require approvals by voters in advance of the deadline required to move to a vote\r\n- Aid the Foundation in implementing any processes aimed at making the Mission Request approval process easier\r\n\r\n***Proposal Voting Process:***\r\n\r\n- Alert voters to the start and end of Special Voting Cycles and any other deadlines during the Reflection Period\r\n- Manage Voting Cycle Roundups, adding approved proposals to the roundup before the deadline\r\n- Draft copy for votes, to be reviewed and approved by the Foundation\r\n- Ensure voters understand what they need to be voting on throughout Season 5\r\n\r\n***Proposal Veto Process:***\r\n\r\n- Ensure voters are aware of any veto windows, and that they understand how to veto and what a veto means, throughout Season 5 (this pertains to Citizens’ House in Season 5)\r\n\r\n***Forum Management:***\r\n\r\n- Monitor, manage, and reduce low quality forum engagement during Season 5\r\n- Manage discourse tags to aid discoverability of relevant proposals during Season 5\r\n- Flag important posts and/or comments to the Optimism Foundation\r\n- Aid the Foundation in posting future Reflection Period posts to the forum\r\n- Assist with on-chain analytics reports (more details to be published soon)\r\n\r\nThis Season, we will add an additional govNERD focused on supporting RetroPGF rounds. This govNERD will: \r\n\r\n- Support RetroPGF applicants throughout the process of a round\r\n- Ensure applicants are aware that a round is taking place\r\n- Support applicants in tracking their impact\r\n- Answer questions relating to the application process\r\n- Support third party RetroPGF tooling such as [RetroPGFhub](https://retropgfhub.com/) and [RetroLists](https://retrolist.app/)\r\n\r\n#### The exact scope of govNERDs may evolve over the course of the Season\r\n\r\n### **How should the Foundation measure progress towards this Mission?**\r\n\r\n- If this Mission is successful, the Foundation should be able to remove its role in the following functions:\r\n - Maintenance of the public governance calendar during Season 5\r\n - Procedural questions raised in governance community calls\r\n - Announcements to voters pertaining to voting cycles or general governance schedules (without a corresponding decrease in turnout per proposal)\r\n - Alerts related to proposals receiving enough approvals to move to a vote, when required\r\n - Publication of Voting Cycle Roundups\r\n - Reduction in forum spam, as measured by the number of forum issues the Foundation is asked to address\r\n - Applicant support during retroPGF rounds \r\n\r\n### **How should badgeholders measure impact upon completion of this Mission?**\r\n\r\n- The Foundation may attest to the reduction in workload as a result of govNERDs taking on work for which the Foundation used to be responsible\r\n- The Foundation will document any positive or negative feedback from delegates and Citizens interacting with govNERDs throughout the Reflection Period and share a summary\r\n\r\n---\r\n\r\n## **Application Instructions:**\r\n\r\nTo apply for this Mission Request, please complete the form below and submit as a comment on this issue thread. Submissions will be open until December 1st 2023 23:59 GMT, at which time the Foundation will review all submissions and select *up to three applicants.*\r\n\r\nCopy the entire application below and leave a comment on this issue with your answers completed. A representative from the Optimism Foundation may reach out using the contact info provided to request more information as necessary.\r\n\r\n<details>\r\n <summary>Application template</summary>\r\n \r\n ## **Mission Application**\r\n\r\n- **Applicant Name:**\r\n- **Trust [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877):**\r\n- **Please verify that you meet the qualifications for submitting at the above [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877):**\r\n- **Contact info:** *Please specify the best point of contact (email preferred)*\r\n- **Twitter handle:** *For promotional purposes, when applicable*\r\n- **L2 recipient address:**\r\n- **Please link to any relevant previous work:**\r\n- **What makes you best-suited to execute this Mission? Please consider any experience relevant to the above requirements:**\r\n- **Please explain your familiarity with Optimism Governance and the proposal process:**\r\n- **Please describe the impact you aim to make in completing this Mission:**\r\n- **Please define the [critical milestone(s)](https://gov.optimism.io/t/grant-policies/5833) that should be used to determine whether you’ve executed on this proposal. Make sure you understand what a critical milestone is before answering this question:**\r\n- **Please verify that you are able to commit up to 10 hours per week to this role:**\r\n- **Please list any additional support your team would require to execute this mission (financial, technical, marketing, etc.):**\r\n\r\n---\r\n\r\nI confirm that my grant will be subject to clawback for failure to execute on the critical milestone(s) outlined in the Mission Request: [Yes/No]\r\n\r\nBuilders grants are awarded in OP, locked for one year. Growth experiments grants are subject to the no-sale rule. **This will be a builders grant.** I confirm that I have read and will abide by the [grant policies](https://gov.optimism.io/t/token-house-grant-policies/5833)): [Yes/No]\r\n\r\nI understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant: [Yes/No]:\r\n\r\nI understand that I will be expected to following the public grant reporting requirements outlined [here](https://gov.optimism.io/t/suggested-public-reporting-requirements-for-grantees/4176): [Yes/No]:\r\n\r\n---",
"created_at": "2023-11-22T15:16:14Z",
"updated_at": "2023-12-03T09:14:30Z",
"comment": 11,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/114/reactions",
"total_count": 7,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 7,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/pull/113",
"issue_number": 113,
"title": "Create devcontainer.json",
"user": {
"name": "Abuchtela",
"avatar": "https://avatars.githubusercontent.com/u/84213452?v=4"
},
"tag": [],
"body": "<!-- Contributions welcome! See https://github.com/ethereum-optimism/.github/blob/master/CONTRIBUTING.md -->\r\n\r\n**Description**\r\n\r\nA clear and concise description of the features you're adding in this pull request.\r\n\r\n**Tests**\r\n\r\nPlease describe any tests you've added. If you've added no tests, or left important behavior untested, please explain why not.\r\n\r\n**Additional context**\r\n\r\nAdd any other context about the problem you're solving.\r\n\r\n**Metadata**\r\n\r\n- Fixes #[Link to Issue]\r\n",
"created_at": "2023-11-16T22:29:17Z",
"updated_at": "2024-01-12T07:53:40Z",
"comment": 0,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/113/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/110",
"issue_number": 110,
"title": "RFP: Optimism Ecosystem Investment Network",
"user": {
"name": "oplavande",
"avatar": "https://avatars.githubusercontent.com/u/111033022?v=4"
},
"tag": [
{
"name": "Intent: Governance Accessibility",
"desctiion": ""
},
{
"name": "Foundation Mission (RFP)",
"desctiion": "A request for proposals for a specific work item."
}
],
"body": "## Foundation Mission Request (RFP) – Optimism Ecosystem Investment Network\r\n\r\n- **Foundation Mission Request:** Establish the Optimism Ecosystem Investment Network\r\n- **S4 Intent**: Intent 4 \r\n- **Proposal Tier**: [Ember](https://gov.optimism.io/t/collective-trust-tiers/5877)\r\n- **Baseline grant amount:** 25k OP for establishment of network (Potential for future engagement will be assessed upon completion of this mission) \r\n- **Should this Foundation Mission be fulfilled by one or multiple Alliances:** One\r\n- **Optimism Foundation point-of-contact:** @vwtao \r\n- **Submit by**: October 20th at 19:00 GMT\r\n- **Selection by**: November 10th at 19:00 GMT\r\n\r\n--- \r\n\r\n## **Mission Request**\r\n\r\n### **How will this Foundation Mission Request (RFP) help accomplish the above Intent?:**\r\n\r\nThis Mission Request will increase the accessibility of Optimism governance grant programs (including RetroPGF) by creating an ecosystem investment network that connects builders with additional access to upfront capital. \r\n\r\n### **What is required to execute this Foundation Mission Request (RFP)?**\r\n\r\nOptimism attracts builders from many different backgrounds and development stages – from indie hackers to seasoned entrepreneurs. While grants from Optimism Governance are effective in aligning builders with Optimism’s long-term success, builders sometimes need capital in order to cover up-front development and growth costs. \r\n\r\nTo complete this Mission, the Collective is looking for someone to establish an Optimism Ecosystem Investment Network that connects builders and investors. This project should:\r\n- Aggregate a cohort of investors interested in connecting with builders on OP Mainnet and understand their investment thesis\r\n- Establish a scalable process for aggregating and collating the flow: process to source leads from all relevant avenues, clear application instructions for projects, simple yet informative application template, and reliable pattern to share project details with investor groups\r\n- Facilitate introductions between builders and investors where and when appropriate \r\n- Gather feedback from investors and builders on the process and identify ways to improve the program\r\n\r\nThis Mission does not include the following: \r\n- Advice or participation in structuring deal terms between investors and builders.\r\n- Making investment recommendations or providing financial advice. \r\n \r\n**Additional Context**\r\n\r\nVenture investment plays an important role in the long-term vision for Optimism. Today, Optimism runs regular rounds of Retroactive Public Goods Funding to builders contributing to the public good of the Optimism Collective. Eventually, venture investment can be an important part of this funding mechanism: RetroPGF can create a market of investable projects by providing an \"exit\" in the form of funding from RPGF rounds. This allows venture investors to invest in exchange for equity or for future funding from RPGF, if received by the team. This helps make seed capital from venture investors more accessible to builders who need access to funding in order to start building. For more on this topic, read Vitalik’s [guest post](https://medium.com/ethereum-optimism/retroactive-public-goods-funding-33c9b7d00f0c) on the Optimism blog. \r\n\r\nThis is not required for this Mission Request or for the Ecosystem Investment Network. It is included here as context to help influence how this project could evolve over time. \r\n\r\n### **What milestones will help the Collective track progress towards completion of this Foundation Mission Request (RFP)?**\r\n\r\n- Clear project plan with milestones and projected dates for completion of each milestone.\r\n- Published process to source leads throughout the ecosystem \r\n- Published process for projects to participate in the network\r\n- Go-live date and launch for the first iteration of the program\r\n\r\n\r\n### **How should badgeholders measure impact upon completion of this Foundation Mission (RFP)?**\r\n\r\nA successful Mission may be measured on: \r\n- number of projects and investment groups participating in the network\r\n- number of introductions of projects and investors\r\n\r\nBadgeholders may also identify more rigorous or quantitative metrics of success at their discretion as part of the retroPGF evaluation process.\r\n\r\n---\r\n \r\n## Application instructions\r\nTo apply for this RFP, please complete the form in the expandable section below and leave your response as a comment on this issue thread. Submissions will be open until October 3rd, at which time the Foundation will review all submissions and select one individual/team to complete the work defined here.\r\n\r\n<details>\r\n <summary>Submission form</summary>\r\n\r\n_Copy the entire application below and leave a comment on this issue with your answers completed. A representative from the Optimism Foundation may reach out using the contact info provided to request more information as necessary._\r\n\r\n## Foundation Mission (RFP) Application\r\n\r\n**Please verify that you meet the qualifications for submitting at the above [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877/2)**\r\n\r\n* **Alliance Lead:** Please specify the best point of contact for your team \r\n* **Contact info:** \r\n* **L2 recipient address:** \r\n* **Please list the members of your Alliance and link to any previous work:**\r\n\r\n<details>\r\n <summary>_What's an Alliance?_</summary>\r\nAlliances are groups of contributors that *temporarily* work together to accomplish a Mission start-to-finish. This can be an established protocol or project or a group of contributors working together for the first time. Name your group, now you’re an Alliance :)\r\n</details>\r\n\r\n--- \r\n\r\n**What makes your Alliance best-suited to execute this Mission?**\r\n- [...]\r\n- [...]\r\n\r\n**Please describe your proposed solution based on the above Solution Criteria (if applicable):**\r\n- [...]\r\n- [...]\r\n\r\n\r\n**Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each peice of work:**\r\n- [...]\r\n- [...]\r\n\r\n**Please define the [critical milestone(s)](https://gov.optimism.io/t/grant-policies/5833) that should be used to determine whether you’ve executed on this proposal:** \r\n- [...]\r\n- [...]\r\n\r\n**Please list any additional support your team would require to execute this mission (financial, technical, etc.):** \r\n- [...]\r\n- [...]\r\n\r\n---\r\n\r\nPlease check the following to make sure you understand the terms of the Optimism Foundation RFP program:\r\n\r\n- [ ] I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md#valid-proposal-types)\r\n- [ ] I confirm that I have read and understand the [grant policies](https://gov.optimism.io/t/token-house-grant-policies/5833)\r\n- [ ] I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant\r\n- [ ] I understand that I will be expected to following the public grant reporting requirements outlined [here](https://gov.optimism.io/t/suggested-public-reporting-requirements-for-grantees/4176)\r\n\r\n-- end of application --\r\n\r\n</details>\r\n",
"created_at": "2023-09-12T14:14:07Z",
"updated_at": "2023-12-18T18:03:12Z",
"comment": 13,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/110/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/108",
"issue_number": 108,
"title": "🔴 Ecosystem Project Ideas--l2scan for OPstack",
"user": {
"name": "unifrarocks",
"avatar": "https://avatars.githubusercontent.com/u/96854957?v=4"
},
"tag": [],
"body": "### Summary\r\n\r\nOptimism's Superchain vision is to create a network of blockchains that provides the UX like a single blockchain, with OPstack being the essential tool for creating that vision. An important piece that is missing in the toolbox is an open-source, easy-to-use explorer that allows anyone to spin up an explorer easily while providing better than etherscan UX for their end users. \r\n\r\nL2scan is multi-chain by default. This allows users to monitor and analyze txs, assets, and other vital data without switching platforms. The open-source version of L2scan will provide developers who want to build on opstack an out-of-box, easy-to-use explorer with low maintenance cost. (blockscout alternative) \r\n\r\nAlso, we want to provide the hosted version of L2scan as the AI-powered blockchain explorer to the Optimism ecosystem. It will be a combination of an AI analytics platform + dev tools + user portal + Search Engine with the following feature: \r\n\r\n### Possible Features\r\n-Cross-chain search engine\r\n-Account System\r\n-Superchain ecosystem portal \r\n-Human-readable structured data presentation\r\n-AI-Powered\r\n - Automatically classifies and labels transactions\r\n - Aggregation and visualization of data\r\n - Smart Contract Analysis\r\n - Intelligent search and filtering (with natural language)\r\n -Code reader/Code Search/Similar Search\r\n\r\n \r\nFor example, L2scan for other chains already launched:\r\n - Home: https://linea.l2scan.co/\r\n - Txns List: https://linea.l2scan.co/txs\r\n - Blocks List: https://linea.l2scan.co/blocks\r\n - Batches List: https://linea.l2scan.co/batches\r\n - Bridge Info: https://linea.l2scan.co/bridge\r\n - Top Accounts: https://linea.l2scan.co/top-accounts\r\n - Token ERC-20: https://linea.l2scan.co/tokens\r\n - Token ERC-721: https://linea.l2scan.co/tokens-nft\r\n - Token ERC-1155: https://linea.l2scan.co/tokens-nft1155\r\n - Charts & Status: https://linea.l2scan.co/charts\r\n - Dev Tools: https://linea.l2scan.co/devtools\r\n - Dapps Ranking: https://linea.l2scan.co/dapps\r\n - Verify Contract: https://linea.l2scan.co/verifyContract\r\n - Account system with watch list(real-time notify), tag, etc. https://scroll.l2scan.co/account/watch-list\r\n\r\n**What we can offer:** \r\n--A unified multi-chain explorer for the superchain ecosystem providing seamless UX for the user. \r\n--An open-source version to support the opstack developers as a blockscout alternative ( with more popular programming choices which makes it easier to maintain) \r\n\r\n**What we need:** \r\n--A grant from OP Foundation to support the hosted version hosting cost & open source initiative \r\n--Featuring our open-source version in the superchain dev docs as the recommended option \r\n--Introducing opstack developers to us so we can monetize and find a sustainable business model\r\n",
"created_at": "2023-08-23T13:22:14Z",
"updated_at": "2023-08-23T14:00:09Z",
"comment": 0,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/108/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/107",
"issue_number": 107,
"title": "🔴 Ecosystem Project Idea: Voting Badge Attestation Visualizer",
"user": {
"name": "JSeiferth",
"avatar": "https://avatars.githubusercontent.com/u/43515441?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Estimated Effort: Small",
"desctiion": ""
},
{
"name": "Tag: RetroPGF",
"desctiion": ""
},
{
"name": "Tag: Governance",
"desctiion": ""
},
{
"name": "Estimated Impact: Small",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\n\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \n\n---\n\n## Summary\n\n**This project is for creating a frontend that allows users to explore how RetroPGF voting badges are distributed.**\n\nRecently, the voting badge distribution for RetroPGF round 3 has kicked off - you can find the full announcement [here](https://gov.optimism.io/t/retropgf-3-voting-badge-distribution/6557) 👈\nTo drive transparency and understanding it would be valueble to visualize how voting badges are distributed. Badgeholders are selected through a multiple selection methods. \n@smartcontracts prev built a frontend that allows you to visualize a specific attestation schema. You can find the repo [here](https://github.com/smartcontracts/coolgraph) https://github.com/smartcontracts/coolgraph 👈\n\n\n\nThis project can pick up on the existing visualizer and make minor changes to visualize the voting badge distribution or add new features that make this a useful tool for visualizing badgeholder attestations and attestations at large. \n\n### Resources\n- [Badgeholder EAS schema](https://optimism.easscan.org/schema/view/0xfdcfdad2dbe7489e0ce56b260348b7f14e8365a8a325aef9834818c00d46b31b), \n - I deployed a version of it on Goerli for experimentation [here](https://optimism-goerli-bedrock.easscan.org/schema/view/0x59631c889e2c1f9befae214d3aecf7e865d987cee5ff8c29ddbaa0b50010a34b)\n- [RetroPGF round 3 voting badge distribution](https://gov.optimism.io/t/retropgf-3-voting-badge-distribution/6557) \n- [RetroPGF round 2 voting badge distribution](https://community.optimism.io/docs/governance/retropgf-2/#)\n- [Get nerdsniped on attestations ](https://community.optimism.io/docs/identity/intro/)\n\n**OP Labs or Optimism Foundation Contact**: Jonas (gh: @JSeiferth, TG/Discord: @jonassft)\n\n## Possible Features\n- **Basic**: Make changes to [coolgraph](https://github.com/smartcontracts/coolgraph) to display [badgeholder attestations](https://optimism.easscan.org/schema/view/0xfdcfdad2dbe7489e0ce56b260348b7f14e8365a8a325aef9834818c00d46b31b) and host it to be available to users. \n - If the `refferedMethod` is \"badgeholderChoice\", the source should be the `referredBy` address and the target the attestation recipient\n - if the `refferedMethod` is not badgeholderChoice, the source should be the `refferedMethod`(e.g. Foundation Choice, Past Badgeholder, Token House Elected or RetroPGF Recipient)\n- **Extended**: Display how voting badges were distributed over multiple rounds (round 2 & round 3 + future rounds)\n- **Extended**: Allow to discover the path of a specific voting badge - e.g. I can see how a specific badgeholder attained a voting badge and the relevant social graph \n- **Extended**: Display the [Optimist NFT](https://opensea.io/collection/optimist-nft) associated with each address\n- **SuperFeature**: Allow for the visualization of any attestation by enabling users to input any EAS Schema\n- **SuperFeatureExtended**: Allow for the visualization of any attestation schema by enabling users to input any EAS schema and select arbitrary data fields to be visualized. \n\n## Impact\n- This can help drive understanding in the Citizens' House of how badgeholders are selected\n- This drives understanding of Optimism's identity layer \n- This could be the basis of a visual attestation explorer, a useful tool for users to interact with Optimism's identity layer\n\n",
"created_at": "2023-08-16T11:14:32Z",
"updated_at": "2023-10-07T16:59:54Z",
"comment": 9,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/107/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/106",
"issue_number": 106,
"title": "RFP: RetroPGF List Creation UI",
"user": {
"name": "bdresser",
"avatar": "https://avatars.githubusercontent.com/u/1016190?v=4"
},
"tag": [
{
"name": "Intent: Governance Accessibility",
"desctiion": ""
},
{
"name": "Foundation Mission (RFP)",
"desctiion": "A request for proposals for a specific work item."
}
],
"body": "## Foundation Mission (RFP) – RetroPGF List Creation UI\n* **Proposed Foundation Mission (RFP):** RetroPGF List Creation UI\n* **S4**[ **Intent**](https://gov.optimism.io/t/collective-intents/5874)**:** Governance Accessibility\n* **Proposal**[ **Tier**](https://gov.optimism.io/t/collective-trust-tiers/5877)**:** Ember\n* **Baseline grant amount:** 20k OP\n* **Should this Foundation Mission be fulfilled by one or multiple Alliances:** One\n* **OP Labs or Optimism Foundation Sponsor:** Jonas (gh: @JSeiferth, TG/Discord: **@jonassft**)\n* **Submit by:** September 4th, 2023\n* **Selection by:** September 11th, 2023\n\n* * *\n\n### **How will this Foundation Mission (RFP) help accomplish the above Intent?** \n\n\n[Retroactive Public Goods Funding (RetroPGF) Round 3](https://community.optimism.io/docs/governance/retropgf-3/) will take place this fall and will distribute 30M OP to reward contributions that have supported the development and adoption of Optimism. \n\nThis mission will create an application that **allows badgeholders (voters in RetroPGF) to create Lists, a new tool for vote sharing** and by doing so contribute to a more accurate evaluation of projects and the overall success of RetroPGF 3. \n\n**What are Lists?** \n- A List contains a set of projects chosen from the total set of RetroPGF applicants together with a suggested OP allocation for each project.\n- Each List should reference some methodology for allocating OP to each project based on the creators expertise and evaluation of relevant data.\n- Only badgeholders are allowed to create Lists. \n- Lists will facilitate context sharing among badgeholders, and enable badgeholders to easily leverage each other's proposed votes. \n\nIn the previous round of RetroPGF, badgeholders started sharing their [proposed votes](https://gov.optimism.io/t/retropgf-round-2-voting-rationale/5570) to learn from each other's expertise in different areas. In round 3, we’re introducing Lists as a more powerful tool to facilitate that sharing of context, and enable badgeholders to easily leverage each other's proposed votes. \n\nThe [RetroPGF Voting application](https://github.com/ethereum-optimism/ecosystem-contributions/issues/104) will allow badgeholders to discover, view and interact with Lists (see screenshot of designs below). This mission will enable badgeholders to create the Lists that are surfaced in the RetroPGF Voting application. \n\n<details><summary>How Lists are presented to users</summary>\n<p>\n\n\n\n\n</p>\n</details> \n\n### **What is required to execute this Foundation Mission (RFP)?**\nCompleting this Mission requires:\n* Outlining your proposed solution to allow badgeholders to create Lists\n* Building a frontend that enables badgeholders to create Lists by leveraging EAS for onchain attestations and posting metadata on IPFS. The frontend should be fully open-source and should allow for future iterations of the functionality.\n* Hosting and managing the application infrastructure while RetroPGF 3 is ongoing. \n\n**Core functionality of the application**\nEnable badgeholders to create Lists, the following steps are core to this user journey:\n- Input relevant metadata of a List (Name, description, impact evaluation description, impact evaluation link)\n- Filling in the contents of a List by choosing projects and inputting how much OP each project should receive\n- Posting the List onchain via EAS and associated metadata \n- View created Lists\n\nRelevant checks will need to applied to the creation of Lists, such as char limits and other limitations (e.g. the OP allocated among projects can't exceed the total round OP allocation.)\n\n**Technical Architecture and implementation**\n* **Query project data**: Ethereum Attestation Service (EAS) is used to query existing onchain information relating to entities and their RetroPGF 3 application (e.g. projects). This will be relevant to display project names and profile pictures, as well as referencing projects in List attestations. Relevant schema information and indexer will be provided once the proposal has been accepted. \n* **Posting Lists**: Ethereum Attestation Service (EAS) is used to post the contents of a List onchain and reference the relevant metadata. Relevant schema information and indexer will be provided once the proposal has been accepted.\n* The application should be live and usable by **Oct 14th 2023**, you will host the application yourself and maintain it until March 2024.\n* Everything that you build should be open-source under MIT license and should allow for future iterations of the functionality. \n\nYou can find the EAS & Metadata schema for Lists [here](https://gist.github.com/JSeiferth/fe8bf39c450be8772a9d93b7fc9a0702) \n\n### **What milestones will help the Collective track progress towards completion of this Foundation Mission (RFP)?**\n1. Specification for implementation, design approach, and architecture \n2. Open-source code repository to observe progress over time\n3. Launch of the application\n\n### **How should badgeholders measure impact upon completion of this Mission (RFP)?** \n* Number of Lists created via the application\n* Qualitative feedback on the List creation experience by badgeholders\n\n## Application instructions\n\n_To apply for this RFP, please complete the form in the expandable section below and leave your response as a comment on this issue thread. Submissions will be open until June 28, at which time the Foundation will review all submissions and select **one** individual/team to complete the work defined here._ \n\n<details>\n <summary>Submission form</summary>\n\n_Copy the entire application below and leave a comment on this issue with your answers completed. A representative from the Optimism Foundation may reach out using the contact info provided to request more information as necessary._\n\n## Foundation Mission (RFP) Application\n\n**Please verify that you meet the qualifications for submitting at the above [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877/2)**\n\n* **Alliance Lead:** Please specify the best point of contact for your team \n* **Contact info:** \n* **L2 recipient address:** \n* **Please list the members of your Alliance and link to any previous work:**\n\nRead more about Alliances [here](https://gov.optimism.io/t/season-4-alliance-guide/5873)\n\n--- \n\n**What makes your Alliance best-suited to execute this Mission?**\n- [...]\n- [...]\n\n**Please describe your proposed solution based on the above Solution Criteria (if applicable):**\n- [...]\n- [...]\n\n\n**Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each peice of work:**\n- [...]\n- [...]\n\n**Please define the [critical milestone(s)](https://gov.optimism.io/t/grant-policies/5833) that should be used to determine whether you’ve executed on this proposal:** \n- [...]\n- [...]\n\n**Please list any additional support your team would require to execute this mission (financial, technical, etc.):** \n- [...]\n- [...]\n\n**Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant:** _(Note: there is no guarantee that approved Missions will receive up-front cash grants.)_\n- [...]\n\n---\n\nPlease check the following to make sure you understand the terms of the Optimism Foundation RFP program:\n\n- [ ] I understand my grant for completing this RFP will be locked for one year from the date of proposal acceptance.\n- [ ] I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant\n- [ ] I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md#valid-proposal-types)\n- [ ] I confirm that I have read and understand the [grant policies](https://gov.optimism.io/t/token-house-grant-policies/5833)\n- [ ] I understand that I will be expected to following the public grant reporting requirements outlined [here](https://gov.optimism.io/t/suggested-public-reporting-requirements-for-grantees/4176)\n\n-- end of application --\n\n</details>\n",
"created_at": "2023-08-14T16:50:42Z",
"updated_at": "2023-11-07T13:30:58Z",
"comment": 17,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/106/reactions",
"total_count": 5,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 5,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/104",
"issue_number": 104,
"title": "RFP: RetroPGF 3 Discovery & Voting",
"user": {
"name": "bdresser",
"avatar": "https://avatars.githubusercontent.com/u/1016190?v=4"
},
"tag": [
{
"name": "Intent: Governance Accessibility",
"desctiion": ""
},
{
"name": "Foundation Mission (RFP)",
"desctiion": "A request for proposals for a specific work item."
}
],
"body": "## RetroPGF3: Discovery & Voting RFP\n\n* **Proposed Foundation Mission (RFP):** RetroPGF Discovery & Voting application\n* **S4**[ **Intent**](https://gov.optimism.io/t/collective-intents/5874)**:** Governance Accessibility\n* **Proposal**[ **Tier**](https://gov.optimism.io/t/collective-trust-tiers/5877)**:** Fledgling Tie\n* **Baseline grant amount:** 150k OP\n* **Should this Foundation Mission be fulfilled by one or multiple Alliances:** Multiple (two)\n* **OP Labs or Optimism Foundation Sponsor:** Jonas (gh: @JSeiferth, TG/Discord: **@jonassft**)\n* **Submit by:** August 4th, 2023\n* **Selection by:** August 11th, 2023\n\n* * *\n\n### **How will this Foundation Mission (RFP) help accomplish the above Intent?** \nRetroactive Public Goods Funding (RetroPGF) Round 3 will take place this fall and will distribute 30M OP to reward contributions that have supported the development and adoption of Optimism.\n\nBadgeholders (voters in RetroPGF) need to be able to discover and vote on nominated projects. A good voting experience is core to supporting the work of badgeholders and ensuring an accurate RetroPGF process. \n\nRound 2 of RetroPGF put a high burden on the voting experience of badgeholders, requiring them to do a lot of manual work spreadsheets and forms. This friction limited the overall accuracy of the RetroPGF round. \n\nRound 3 of RetroPGF is set to[ build on the learnings of round 2](https://optimism.mirror.xyz/7v1DehEY3dpRcYFhqWrVNc9Qj94H2L976LKlWH1FX-8) and provide a richer and more intuitive experience for browsing projects and submitting votes. \n\nBy doing so, this mission will contribute to a more accurate evaluation of projects and contribute to the overall success of RetroPGF 3. \n\n### **What is required to execute this Foundation Mission (RFP)?**\n\nCompleting this mission requires:\n1. Building a frontend that powers the discovery of projects and voting by badgeholders in RetroPGF round 3. The frontend will be based on existing designs and user stories and will utilize the Ethereum Attestation Service, and a combination of onchain and offchain (storage bucket, IPFS, etc.) sources to read data. The frontend should be fully open-source and should allow for future iterations of the functionality. The Foundation will provide product designs; this RFP primarily requires implementation. \n2. Hosting and managing the application infrastructure, including backend infrastructure needed to capture and store badgeholder votes.\n\n**Core functionality of the discovery & voting application**:\n\n* **Discover Projects**: The application will enable users to explore all nominated projects, including search, filtering and sorting functionality.\n* **Viewing a Project's Profile**: Users will be able to discover the profile of a specific project, populated with details provided by the project's team. The information will include general information about the project (name, creator, profile picture, social media links, etc.) and specific information relevant to RetroPGF’s goal of aligning impact and profit (description of contributions, links to contributions, impact description, funding history, etc.). \n* **Discovering and voting on Lists**: A standout new feature of round 3 will be 'Lists', a new tool for badgeholders to share their votes with others. Users will be able to discover, search, filter and sort Lists. By selecting a List, a user will find general information about the list (name, creator, description, impact evaluation description) and the votes on a number of projects included in a list. Badgeholders will be able to either directly import the votes of the list into their ballot, or edit the votes in a list based on their preferences, before adding them to their ballot. \n* **Allocating and submitting votes**: Badgeholders will be able to allocate and submit votes. Badgeholders are voting on individual project profiles or via a list (see above). All votes are aggregated in a badgeholders ballot, where badgeholders are able to see an overview of their votes, make changes to individual votes and submit their ballot. \n\n**Technical Architecture and implementation**:\n\n* **Query project data**: Ethereum Attestation Service (EAS) is used to query existing onchain information relating to entities, their RetroPGF 3 application, and social verifications. Relevant schema information and indexer will be provided once the proposal has been accepted. \n * An entity represents individuals or organizations\n * An application represents an entity’s application for RetroPGF and maps 1:1 to an entity. \n * A social verification represents an attestation made by OptimismFND that indiciates an entity is the owner of a specific Twitter or GitHub account\n* **Query project lists**: Ethereum Attestation Service (EAS) is leveraged to query existing onchain information relating to project lists. Relevant schema information and indexer will be provided once the proposal has been accepted.\n* **Create a voting backend**: Backend infrastructure is required to capture and store votes, badgeholder votes will be private and stored on a backend server hosted by yourself. Minor features in the application may require additional backend support. \n* You will host the application yourself and maintain it until March 2024. Optimism Foundation will help you host this application at an optimism.io subdomain\n* Everything that you build should be open-source under MIT license and should allow for future iterations of the functionality. \n\nFor this Mission, the Optimism Foundation will accept **up to two submissions**. Multiple frontends will maximize the likelihood of success and improve the resilience of the system. \n\nThe rollout of functionality of the application will be done in multiple phases:\n* Phase 1: Project discovery (early-October 2023) - users are able to discover eligible projects and view project profiles. \n* Phase 2: Voting (mid-October 2023)- badgeholders are able to discover lists and to allocate and submit votes. \n\nPlease find [user stories](https://docs.google.com/document/d/1msALT4H9-77WLfWlFW72eX4Mxd7urpcmrppWMBQyBvI/edit?usp=sharing), [designs](https://www.figma.com/file/DcoTZUiL9SqWgPjPjLCKHN/RetroPGF-3---Voting?type=design&node-id=172%3A24948&mode=design&t=EUuU8XdssEbeZkpD-1) and [EAS & Metadata Schemas](https://gist.github.com/jakim929/d8269973aa87862fa91037d3be3c4d7f) for the application linked. Note that these are not final. \n \n<details>\n<summary> 👈 Click here to see WIP wireframes </summary>\n\n\n\n\n</details>\n\n### **What milestones will help the Collective track progress towards completion of this Foundation Mission (RFP)?**\n\n1. Specification for implementation, design approach, and architecture for the functionality listed above.\n2. Open-source code repository to observe progress over time\n3. Launching Phase 1: Project discovery\n4. Launching Phase 2: Voting\n5. Successful completion of the voting period\n\n### **How should badgeholders measure impact upon completion of this Mission (RFP)?** \n\n* Qualitative feedback on the \"accuracy\" of RetroPGF Round 3\n* Number of badgeholders who successfully voted via the frontend\n* Qualitative feedback from badgeholders on the voting experience\n\n## Application instructions\n\n_To apply for this RFP, please complete the form in the expandable section below and leave your response as a comment on this issue thread below. Submissions will be open until August 4th, at which time the Foundation will review all submissions and select up to two individuals/teams to complete the work defined here._ \n\n<details>\n <summary>Submission form</summary>\n\n_Copy the entire application below and leave a comment on this issue with your answers completed. A representative from the Optimism Foundation may reach out using the contact info provided to request more information as necessary._\n\n## Foundation Mission (RFP) Application\n\n**Please verify that you meet the qualifications for submitting at the above [Tier](https://gov.optimism.io/t/collective-trust-tiers/5877/2)**\n\n* **Alliance Lead:** Please specify the best point of contact for your team \n* **Contact info:** \n* **L2 recipient address:** \n* **Please list the members of your Alliance and link to any previous work:**\n\nRead more about Alliances [here](https://gov.optimism.io/t/season-4-alliance-guide/5873)\n\n--- \n\n**What makes your Alliance best-suited to execute this Mission?**\n- [...]\n- [...]\n\n**Please describe your proposed solution based on the above Solution Criteria (if applicable):**\n- [...]\n- [...]\n\n\n**Please outline your step-by-step plan to execute this Mission, including expected deadlines to complete each peice of work:**\n- [...]\n- [...]\n\n**Please define the [critical milestone(s)](https://gov.optimism.io/t/grant-policies/5833) that should be used to determine whether you’ve executed on this proposal:** \n- [...]\n- [...]\n\n**Please list any additional support your team would require to execute this mission (financial, technical, etc.):** \n- [...]\n- [...]\n\n**Grants are awarded in OP, locked for one year. Please let us know if access to upfront capital is a barrier to completing your Mission and you would like to be considered for a small upfront cash grant:** _(Note: there is no guarantee that approved Missions will receive up-front cash grants.)_\n- [...]\n\nPlease check the following to make sure you understand the terms of the Optimism Foundation RFP program:\n\n- [ ] I understand my grant for completing this RFP will be locked for one year from the date of proposal acceptance.\n- [ ] I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant\n- [ ] I understand my locked grant may be clawed back for failure to execute on critical milestones, as outlined in the [Operating Manual](https://github.com/ethereum-optimism/OPerating-manual/blob/main/manual.md#valid-proposal-types)\n- [ ] I confirm that I have read and understand the [grant policies](https://gov.optimism.io/t/token-house-grant-policies/5833)\n- [ ] I understand that I will be expected to following the public grant reporting requirements outlined [here](https://gov.optimism.io/t/suggested-public-reporting-requirements-for-grantees/4176)\n\n-- end of application --\n\n---\n\n</details>",
"created_at": "2023-07-20T17:41:43Z",
"updated_at": "2023-10-31T00:17:23Z",
"comment": 31,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/104/reactions",
"total_count": 1,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 1,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/100",
"issue_number": 100,
"title": "🔴 Ecosystem Project Idea: Transaction Replay Tool",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Tag: Dev Tools",
"desctiion": ""
},
{
"name": "Estimated Effort: Medium",
"desctiion": ""
},
{
"name": "Estimated Impact: Large",
"desctiion": ""
},
{
"name": "Tag: Consumer Apps",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\r\n\r\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \r\n\r\n---\r\n\r\n## Summary\r\n\r\nAs it currently stands, users need to utilize the SDK or other low-level mechanisms to replay L1 => L2 or L2 => L1 transactions that ran out of gas. This can be complex for average users. A good tool would provide an interactive user interface for replaying transactions. This tool aims to simplify this process and make it more accessible.\r\n\r\n## Potential Features\r\n- **Query and Display Failed Transactions**: The tool would provide functionality to query both L1 and L2 chains using a user's public address to find transactions that have failed due to running out of gas. Should also be able to support searching by a specific transaction hash.\r\n- **Customize Gas Limit**: The user interface would allow users to specify a higher gas limit for replaying the failed transaction.\r\n- **Safe Replaying**: Before replaying, the tool should provide a cost estimation for the transaction and ask for user confirmation, this makes sure that the custom gas limit is going to be high enough.\r\n- **Tutorial and Help**: The tool would include a brief tutorial or walkthrough on how to use it, along with tooltips or help text to guide users.\r\n- **Real-time Updates**: The tool would offer real-time updates on the status of the transaction once replayed.\r\n- **Transaction History**: It should have the functionality to keep a history of all replayed transactions for a given address.\r\n\r\n## Impact\r\n- **Increased Usability**: This tool will drastically improve the experience for users who face gas issues during transactions between L1 and L2.\r\n- **Accessibility**: It will make L2 interactions more accessible for non-technical users by removing the need to use the SDK for these transactions.\r\n- **Reduced Transaction Failures**: The tool will help to reduce the number of failed transactions on the network, leading to improved overall network health.\r\n- **Better User Experience**: By giving users control over their gas limits, it provides a more personalized and user-friendly interaction with L2.\r\n- **Educational**: This tool can serve as an educational resource for users to better understand gas costs and transaction dynamics in L2.\r\n",
"created_at": "2023-06-27T04:55:14Z",
"updated_at": "2023-09-18T05:27:45Z",
"comment": 1,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/100/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/99",
"issue_number": 99,
"title": "🔴 Ecosystem Project Idea: Public OP Mainnet Network Health Dashboard",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Tag: Dev Tools",
"desctiion": ""
},
{
"name": "Estimated Effort: Medium",
"desctiion": ""
},
{
"name": "Estimated Impact: Large",
"desctiion": ""
},
{
"name": "Tag: Chain Infra",
"desctiion": ""
},
{
"name": "Tag: Consumer Apps",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\r\n\r\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \r\n\r\n---\r\n\r\n## Summary\r\n\r\nUsers need clear, constant insight into the functional behavior of OP Mainnet. In order to provide insights and better understanding of the state and performance of the L2 network, the L2 Network Health Dashboard will offer a range of crucial statistics in a visual, easy-to-understand format. As an important part of the ecosystem, the ability to monitor the health and performance of the L2 network will allow developers, users, and operators to make informed decisions and adjustments. \r\n\r\n## Features\r\n\r\n- The dashboard should be built using Grafana for real-time monitoring and interaction.\r\n- The dashboard should be fully open source.\r\n- The dashboard should have instructions on how to populate the dashboard.\r\n- The dashboard should track transaction latency and offer insights into the average, peak, and minimum transaction times.\r\n- The dashboard should keep track of the costs associated with specific actions on the network.\r\n- The dashboard should track the speed of block production and highlight any significant deviations.\r\n- The dashboard should be able to track reorganizations on the network.\r\n- The dashboard should be able to track the time taken for a block to be produced and sent to L1.\r\n- The dashboard should track block finalization times.\r\n- Flexibility for adding additional metrics or data points as they become relevant or necessary.\r\n\r\n## Impact\r\n\r\n- The dashboard will provide critical insights into the performance of the L2 network, allowing for informed decision making.\r\n- The data collected and displayed could help identify any bottlenecks or areas of inefficiency on the network.\r\n- By making this information easily accessible, the dashboard could encourage the growth and development of the network by providing developers with the information they need to optimize their applications and services.\r\n- Having this kind of transparency could increase trust and confidence in the network. Users and developers alike will have a clearer understanding of how the network operates and performs under various conditions.\r\n",
"created_at": "2023-06-27T04:43:47Z",
"updated_at": "2024-01-04T14:33:50Z",
"comment": 3,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/99/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/98",
"issue_number": 98,
"title": "🔴 Ecosystem Project Idea: OP Mainnet Resource Usage Tracker",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Tag: Dev Tools",
"desctiion": ""
},
{
"name": "Estimated Effort: Large",
"desctiion": ""
},
{
"name": "Estimated Impact: Medium",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\r\n\r\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \r\n\r\n---\r\n\r\n## Summary\r\n\r\nAs OP Mainnet and other L2 solutions gain traction, it becomes increasingly important to monitor and understand the resource consumption on these chains. Currently, it's challenging to get a clear picture of resource usage across gas, storage, and calldata. This project aims to create a comprehensive L2 resource usage monitoring tool that visualizes these aspects in real time and offers insights into usage patterns on OP Mainnet.\r\n\r\n## Potential Features\r\n\r\n- **Real-time visualization:** Display the use of resources such as gas, calldata, and storage in real-time.\r\n- **In-depth resource analysis:** Show detailed statistics of resource usage per transaction and the storage occupied by each contract.\r\n- **Filters:** Allow users to filter the displayed data based on various parameters, including time, type of transaction, contract, and more.\r\n\r\n## Impact\r\n\r\n- **Valuable insights for developers:** This tool will provide in-depth resource usage insights, helping developers optimize their dapps for L2.\r\n- **Contribute to network health and optimization:** Understanding resource usage patterns can help in taking steps to further optimize the OP Mainnet network.\r\n- **Promote efficient resource usage:** By highlighting resource usage, this tool will encourage better coding practices and more efficient usage of network resources, contributing to a more scalable and sustainable network.\r\n",
"created_at": "2023-06-27T04:37:04Z",
"updated_at": "2023-06-27T04:37:04Z",
"comment": 0,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/98/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/97",
"issue_number": 97,
"title": "🔴 Ecosystem Project Idea: Real Time OP Mainnet Bridge Dashboard",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Tag: Dev Tools",
"desctiion": ""
},
{
"name": "Estimated Effort: Large",
"desctiion": ""
},
{
"name": "Estimated Impact: Large",
"desctiion": ""
},
{
"name": "Tag: Chain Infra",
"desctiion": ""
},
{
"name": "Tag: Consumer Apps",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\r\n\r\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \r\n\r\n---\r\n\r\n## Summary\r\n\r\nIn the rapidly evolving landscape of Layer 2 solutions, an overarching understanding of cross-chain interactions and bridge activities is crucial. A real-time L2 Bridge Dashboard for OP Mainnet could provide a holistic view of all transaction activities across bridges connected to the OP Mainnet. This wouldn't just offer insights into the network's health, traffic, and usage trends, but also enhance the transparency and trust users have in the network. Users could better understand where liquidity is flowing, identify the most active bridges, and make informed decisions based on real-time data. For developers, such a dashboard could offer invaluable insights into user behavior and bridge performance, potentially guiding future development efforts and optimizations.\r\n\r\n## Features \r\n\r\n- **Real-Time Data**: A dashboard that displays constantly updated, real-time data on transaction activities across all bridges connected to OP Mainnet.\r\n- **Interactive UI**: A highly interactive user interface showcasing live flows of transactions.\r\n- **Source Identification**: Feature to identify the source of funds and the corresponding bridge utilized.\r\n- **Aggregated Statistics**: Display of aggregated statistics covering total volume, the number of transactions, average transaction size, bridge popularity, and more.\r\n\r\n## Impact \r\n\r\n- **Better Understanding**: A comprehensive tool that aids users, developers, and researchers in understanding bridge usage dynamics in real-time.\r\n- **Increased Transparency**: By providing a transparent view of transaction flows, the dashboard could significantly enhance users' trust in bridge operations.\r\n- **Actionable Insights**: The aggregated statistics and real-time data can deliver actionable insights for users and developers, potentially influencing strategic decision-making and future development direction.\r\n",
"created_at": "2023-06-27T04:24:03Z",
"updated_at": "2023-07-31T05:24:26Z",
"comment": 4,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/97/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/96",
"issue_number": 96,
"title": "🧪 Mad Science Project Idea: Ultra Sound Money as an OP Stack Chain",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Estimated Effort: Large",
"desctiion": ""
},
{
"name": "Estimated Impact: Large",
"desctiion": ""
},
{
"name": "Mad Science Project Idea",
"desctiion": "An experimental project concept"
},
{
"name": "Tag: Consumer Apps",
"desctiion": ""
},
{
"name": "Tag: Contracts",
"desctiion": ""
}
],
"body": "**What is a Mad Science Project Idea?**\r\n\r\nA Mad Science Project Idea is an idea for a project within the Optimism ecosystem that may not have clear value but is generally cool as heck. Mad Science Project Ideas make great hackathon projects and tend to be a great way to explore Optimism, OP Mainnet, and the OP Stack.\r\n\r\n---\r\n\r\n## Summary\r\n\r\nThis project aims to leverage the OP Stack chains, without a Sequencer, to index data. In particular, these chains, dubbed \"Indexing Chains,\" can capture various L1 data, such as gas burn information. By doing this, we can potentially replace the Ultra Sound Money website backend with an OP Stack chain Rollup. To do this, you would need to modify the OP Stack chain to constantly keep track of the L1 gas burn and store that information in an L2 smart contract.\r\n\r\n## Possible Features\r\n\r\n- Implement an Indexing Chain to track L1 gas burn.\r\n- Store the L1 gas burn in an L2 smart contract.\r\n- Replace the Ultra Sound Money website backend with the newly created Indexing Chain.\r\n- Query the L1 gas burn from the L2 smart contract via the USM website.\r\n\r\n## Impact\r\n\r\n- It offers a novel and efficient way to index L1 data.\r\n- Enhances the robustness and performance of the Ultra Sound Money website backend.\r\n- Showcases the versatility of the OP Stack chains for tasks beyond Sequencer-based operations.\r\n",
"created_at": "2023-06-27T04:19:02Z",
"updated_at": "2023-06-27T04:19:02Z",
"comment": 0,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/96/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/95",
"issue_number": 95,
"title": "🔴 Ecosystem Project Idea: Transaction Latency Testing Tool",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Tag: Dev Tools",
"desctiion": ""
},
{
"name": "Estimated Effort: Medium",
"desctiion": ""
},
{
"name": "Estimated Impact: Large",
"desctiion": ""
},
{
"name": "Tag: Consumer Apps",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\r\n\r\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \r\n\r\n---\r\n\r\n## Summary\r\n\r\nDevelop a latency testing tool for the OP Mainnet to track the dynamism of transaction latency. This tool would shed light on any issues impacting transaction inclusion times. If latency spikes, there might be network issues. Would be great to make as an open source tool that could also be provided as a public dashboard.\r\n\r\n## Possible Features\r\n\r\n- Facilitate configuration of routes (RPCs).\r\n- Enable the sending of various types of transactions at different intervals.\r\n- Record response times for each transaction.\r\n- Display a graph showcasing the correlation between transaction send times and response times.\r\n- Allow configuration of multiple RPCs and highlight differences in latency between them.\r\n\r\n## Impact\r\n\r\n- Provides invaluable data on the performance of OP Mainnet.\r\n- Assists in identifying and addressing latency issues.\r\n- Helps users and developers understand the implications of using different RPCs.\r\n",
"created_at": "2023-06-27T04:15:01Z",
"updated_at": "2024-01-06T09:49:37Z",
"comment": 2,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/95/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/94",
"issue_number": 94,
"title": "🔴 Ecosystem Project Idea: Awesome Optimism Repository",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Estimated Effort: Medium",
"desctiion": ""
},
{
"name": "Estimated Impact: Large",
"desctiion": ""
},
{
"name": "Tag: Documentation",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\r\n\r\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \r\n\r\n---\r\n\r\n## Summary\r\n\r\nCreate an 'Awesome Optimism' repository, akin to the widely popular 'awesome X' repositories found throughout GitHub. The goal is to showcase the vibrant open-source contributions happening within the Optimism ecosystem, including notable projects like Magi, op-erigon, and others.\r\n\r\n## Possible Features\r\n\r\n- Set up a GitHub repository named 'Awesome Optimism'.\r\n- Curate and include a comprehensive list of cool, open-source projects related to Optimism.\r\n- For each listed project, provide a brief description, related links, and any additional relevant information.\r\n- Structure the repository for easy navigation and exploration of listed projects.\r\n- Include a contributing guide to encourage community additions and updates to the list.\r\n\r\n## Impact\r\n\r\n- Provides a centralized resource for developers and enthusiasts to discover projects in the Optimism ecosystem.\r\n- Encourages open-source contributions and fosters a stronger community around Optimism.\r\n- Offers visibility and recognition for projects contributing to the Optimism ecosystem.\r\n",
"created_at": "2023-06-27T04:08:13Z",
"updated_at": "2024-01-12T14:08:56Z",
"comment": 11,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/94/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/93",
"issue_number": 93,
"title": "🧪 Mad Science Project Idea: I'm Feeling Lucky for OP Mainnet Dapps",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [],
"body": "**What is a Mad Science Project Idea?**\r\n\r\nA Mad Science Project Idea is an idea for a project within the Optimism ecosystem that may not have clear value but is generally cool as heck. Mad Science Project Ideas make great hackathon projects and tend to be a great way to explore Optimism, OP Mainnet, and the OP Stack.\r\n\r\n---\r\n\r\n\r\n## Summary\r\n\r\nIn the spirit of the 'I'm feeling lucky' feature made famous by Google, a similar functionality for OP Mainnet dapps would create a fun and interactive way to discover new projects. A website that allows users to either search or simply load a random dapp could increase exposure for a myriad of OP Mainnet applications.\r\n\r\n## Possible Features\r\n\r\n- Develop a website that optionally accepts a search term from users.\r\n- Upon button click, the site should load a random dapp relevant to the search term, if provided.\r\n- If no search term is provided, the site should be capable of loading a random dapp from the OP Mainnet ecosystem.\r\n\r\n## Impact\r\n\r\n- Adds an element of fun and discovery to the OP Mainnet ecosystem.\r\n- Helps to increase exposure and user interaction for a variety of OP Mainnet dapps.\r\n- Provides an easy and enjoyable way for users to explore new and existing OP Mainnet applications.\r\n",
"created_at": "2023-06-27T03:54:56Z",
"updated_at": "2023-10-18T18:04:22Z",
"comment": 2,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/93/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/92",
"issue_number": 92,
"title": "🔴 Ecosystem Project Idea: Smart Contract Code Verifier",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Tag: Dev Tools",
"desctiion": ""
},
{
"name": "Estimated Effort: Large",
"desctiion": ""
},
{
"name": "Estimated Impact: XLarge",
"desctiion": ""
},
{
"name": "Tag: Contracts",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\r\n\r\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \r\n\r\n---\r\n\r\n## Summary\r\n\r\nOP Mainnet and other OP Stack based chains encompass a multitude of smart contracts. It's crucial to have a tool or script that efficiently maps the code deployed on these blockchains to the code found within the corresponding GitHub repositories. This tool should be able to take a smart contract address (or list of addresses) and a commit hash and verify that the deployed code corresponds to the code from the specific commit hash.\r\n\r\n## Possible Features\r\n\r\n- Implement a tool or UI that accepts user inputs for L1 network name, contract address, and commit hash.\r\n- Allow the tool to download the corresponding GitHub repository at the specified commit hash and initialize it.\r\n- Compile contracts and compare the bytecode of the deployed contract with the actual bytecode.\r\n- Design the tool to handle proxies if necessary.\r\n- Throw alerts if unable to match the deployed code to what's in GitHub.\r\n\r\n## Impact\r\n\r\n- Enhances the safety of smart contract deployments by validating the origin of deployed code.\r\n- Improves auditability by providing an explicit link between the codebase in the repository and the deployed smart contracts.\r\n",
"created_at": "2023-06-27T03:49:49Z",
"updated_at": "2023-08-05T02:37:29Z",
"comment": 3,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/92/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/91",
"issue_number": 91,
"title": "🔴 Ecosystem Project Idea: Attestation-Based Challenger",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Estimated Effort: Medium",
"desctiion": ""
},
{
"name": "Estimated Impact: Medium",
"desctiion": ""
},
{
"name": "Tag: Protocol",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\r\n\r\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \r\n\r\n---\r\n\r\n\r\n## Summary\r\n\r\nOriginally, Optimism considered introducing an attestation-based challenger module as a pathway towards decentralization. Though focus has shifted towards fault proofs, the attestation-based module remains a fascinating and worthwhile concept. Instead of a multisig, this module would utilize a smart contract that verifies EIP-712 signatures. Any participant could call the smart contract with an array of signatures and a proposed output hash for a given L2 block number. If a threshold of signatures approves that output hash for that block number— and if the existing proposed output hash in the L2OutputOracle contract differs from the signed-off proposal—then the original proposed output hash is discarded.\r\n\r\n## Possible Features\r\n\r\n- Develop a slim server with a simple API route such as `/signature/block/N` that returns a signature over the correct proposal hash for block N.\r\n- Design the API to be callable by anyone.\r\n- If an incorrect proposal on L1 is detected, the API would be called on various known machines to obtain a threshold of signatures.\r\n- Incorporate a smart contract that accepts a proposed output hash for an L2 block number and a threshold of signatures.\r\n- If the threshold is met, and the proposed hash differs from the existing one in the L2OutputOracle, the existing proposal is removed.\r\n\r\n## Impact\r\n\r\n- Offer a novel approach towards securing the integrity of L2 block proposals.\r\n- Contribute to the broader ecosystem's understanding of decentralization mechanisms.\r\n- Help test the potential effectiveness of attestation-based challenger modules in a blockchain context.\r\n- Better than multisigs, easier than fault proofs.\r\n",
"created_at": "2023-06-27T03:33:31Z",
"updated_at": "2023-06-27T03:33:31Z",
"comment": 0,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/91/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/90",
"issue_number": 90,
"title": "🔴 Ecosystem Project Idea: Alternative Fault Detector",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Ecosystem Project Idea",
"desctiion": "Detailed project to build within the Optimism ecosystem."
},
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Estimated Effort: Medium",
"desctiion": ""
},
{
"name": "Estimated Impact: Large",
"desctiion": ""
},
{
"name": "Tag: Chain Infra",
"desctiion": ""
},
{
"name": "Tag: Protocol",
"desctiion": ""
}
],
"body": "**What is an Ecosystem Project Idea?**\r\n\r\nAn Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built. \r\n\r\n---\r\n\r\n## Summary\r\n\r\nL2 state proposals are published to the L2OutputOracle contract, and it's crucial that these proposals align with the accurate L2 state. OP Labs has built a service—the fault detector—that confirms this. However, to enhance the robustness of the system, it would be useful to have a secondary, independent implementation of the fault detector. This will provide an extra layer of assurance and help detect any potential bugs in the current fault detector.\r\n\r\n## Possible Features\r\n\r\n- Listen for new output proposal events for a given L2 block number.\r\n- Locally generate an output proposal for that specific L2 block number.\r\n- Perform a comparison between the locally generated proposal and the one received.\r\n- Flag any discrepancies between the two, raising an error when necessary.\r\n\r\n## Impact\r\n\r\n- Serve as a safeguard against potential bugs in the current fault detector.\r\n- Enhance the reliability and security of our L2 state verification process.\r\n- Provide peace of mind through this added layer of validation.\r\n",
"created_at": "2023-06-27T03:20:20Z",
"updated_at": "2023-12-19T21:00:13Z",
"comment": 2,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/90/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/89",
"issue_number": 89,
"title": "✨ Contribution Opportunity: Reproduce the Bedrock Migration",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Estimated Effort: Small",
"desctiion": ""
},
{
"name": "Estimated Impact: Large",
"desctiion": ""
},
{
"name": "Contribution Opportunity",
"desctiion": ""
},
{
"name": "Tag: Protocol",
"desctiion": ""
}
],
"body": "**What is a Contribution Opportunity?**\r\n\r\nA Contribution Opportunity is a concrete task that you can work on to contribute to the Optimism Collective.\r\n\r\n---\r\n\r\n## Summary\r\n\r\nThe transition to Bedrock called for the execution of an irregular state change, involving the execution of a script against the legacy database and modifying the database accordingly. This issue invites the community to independently carry out the migration and verify its outcome.\r\n\r\n## Possible Features\r\n\r\n- Use the guidance provided in [Mark's blog post](https://blog.oplabs.co/reproduce-bedrock-migration/).\r\n- Follow the steps meticulously and perform the migration.\r\n- Thoroughly validate that the migration has been executed correctly.\r\n- Share your findings by posting a comment in this thread once you have successfully reproduced the migration.\r\n\r\n## Impact\r\n\r\nBy ensuring that the migration is reproducible, we can confirm that no unexpected changes were introduced into the L2 state, thereby enhancing the security for all users.\r\n",
"created_at": "2023-06-27T03:12:39Z",
"updated_at": "2023-10-28T11:07:26Z",
"comment": 1,
"reaction": {
"url": "https://api.github.com/repos/ethereum-optimism/ecosystem-contributions/issues/89/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
},
"status": "open"
},
{
"url": "https://github.com/ethereum-optimism/ecosystem-contributions/issues/88",
"issue_number": 88,
"title": "🧪 Mad Science Project Idea: L2Geth Revamp",
"user": {
"name": "smartcontracts",
"avatar": "https://avatars.githubusercontent.com/u/14298799?v=4"
},
"tag": [
{
"name": "Tag: OP Stack",
"desctiion": ""
},
{
"name": "Estimated Effort: XLarge",