### Project
Liquidity Staking on Optimism (Lido & Rocket Pool)
### Description
Deep dives to explore the how OP rewards are distributed to incentivise liquidity staking on Optimism, how rewards are allocated across dapps/liquidity pools and their performances, OP and LDO spend, how liquidity retention is looking like in the absence of incentives, and any other recommendations you have

### Find out more
Lido: https://www.notion.so/oplabs/Lido-51c8f1e4a6f24bcd88ca84bba9fc8dfc?pvs=4
Rocketpool: https://www.notion.so/oplabs/Rocket-Pool-260afe3571434634a680d21e006839a7?pvs=4

Optimism

[Request for Contributions] OP Rewards: Liquidity Staking on Optimism (Lido & Rocket Pool)

As outlined below, it might be nice to just have one page outlining all JS tools and how they fit into each other. This draft is how I imagine them relating to each other.

- The sdk, [[op-viem](https://www.opviem.sh/)](https://www.opviem.sh/), [[fee-estimation](https://github.com/ethereum-optimism/optimism/tree/develop/packages/fee-estimation)](https://github.com/ethereum-optimism/optimism/tree/develop/packages/fee-estimation) are all a class of “JS libraries that bridge the gap between Ethereum and the OP Stack.” 

Here’s what’s potentially the right abstraction:

- In JS tools, explain that OP Mainnet and OP Stack chains are automatically compatible with many Ethereum JS tools, and we provide subsidiary libraries for the different functions: bridging & gas
    - Ethers v5
        - the SDK provides the different functions
    - Ethers v6
        - (the plugin is incoming, a draft of it at https://github.com/ethers-io/ext-utils-optimism
    - Viem
        - op-viem handles bridging; fee-estimation handles fees, but both will be merged into op-viem
    - web3.js
        - fees handled by the [[web3.js-plugin](https://github.com/ethereum-optimism/optimism/tree/develop/packages/web3js-plugin)](https://github.com/ethereum-optimism/optimism/tree/develop/packages/web3js-plugin)

[AUDIT] Add JS tools overview page

[AUDIT] new tutorial: op-viem

In this section https://stack.optimism.io/docs/build/getting-started/#deploy-the-l1-contracts, after you broadcast the L1 contracts the folder that gets updated is deployments/goerli and the folder you make deployments/getting-started remains empty. The follow command to generate the genesis and rollup files assumed deployments/getting-started is populated but it's empty and errors. I have been copying the goerli folder to getting-started to be consistent with the command
Step 4 in https://stack.optimism.io/docs/build/getting-started/#configure-your-network asks you to put your PRIVATE_KEY in the .envrc but doesn't specify using the raw privkey and not the hex prepended 0x... key
I don't think there's a section on which address/steps on how to bridge back out (understand this takes a while to actually execute, but unless I missed it I don't think the info is there)
Small note when you're configuring your files to change the batcher inbox address to something arbitrary would be helpful to users
Proposed ETH amounts for Admin — 2 ETH Proposer — 5 ETH Batcher — 10 ETH is probably a bit high, Goerli is super cheap 🙂
Pin the optimism and geth tags/versions here https://stack.optimism.io/docs/build/getting-started/#build-the-optimism-monorepo - trying this guide from a latest tag has many config values missing or missing steps, I am using v1.1.4 and it seems fine
The RPC port by default is 8545, a note on which piece of the software has the flag to change this and a note about ssl setup with it would help

[FEEDBACK] Update op-stack getting started

for this page: https://docs.optimism.io/builders/dapp-developers/bridging/custom-bridge

we can link to some custom bridges to help explain this more (eg the NFT bridge) 

[AUDIT] Add custom bridge examples

2 steps to update this page https://docs.optimism.io/builders/tools/monitoring/analytics-tools:
1. Update the list of OP Dashboards
    - [[OP Stack Chains - L1 Mainnet Activity & Fees Paid, L2 OP Chain Activity](https://dune.com/oplabspbc/op-stack-chains-l1-activity)](https://dune.com/oplabspbc/op-stack-chains-l1-activity)
    - [[OP Mainnet Protocol Metrics](https://dune.com/optimismfnd/Optimism)](https://dune.com/optimismfnd/Optimism)
    - [[Popular Apps on OP Mainnet and Project Usage Trends](https://dune.com/optimismfnd/Optimism-Project-Usage-Trends)](https://dune.com/optimismfnd/Optimism-Project-Usage-Trends)
    - [[OP Token House Delegates](https://dune.com/optimismfnd/optimism-op-token-house)](https://dune.com/optimismfnd/optimism-op-token-house)
    - [[Superchain NFTs](https://dune.com/oplabspbc/superchain-nfts)](https://dune.com/oplabspbc/superchain-nfts)
2. Add additional tools/resources (i.e. our github, defillama, growthepie)
    - DeFi Stats: https://defillama.com/
    - L2 Usage and comparison: https://www.growthepie.xyz/
    - OP Analytics (incentive tracking, helper functions, public analysis): https://github.com/ethereum-optimism/op-analytics
    - Contribute to NumbaNERDs: https://app.dework.xyz/optimism-community/main-space-35638/overview or requests: https://github.com/ethereum-optimism/op-analytics/issues

[AUDIT] update analytics-tools

The [op_token_distributions_optimism.transfer_mapping](https://dune.com/queries/2370566) abstraction table in Dune is generated by first identifying distribution recipient project wallets, then pulling all OP transfer transactions from those wallets.

If you notice a wallet that is not being picked up, you can add it in the [Dune spellbook here](https://github.com/duneanalytics/spellbook/blob/main/models/op/token_distributions/optimism/op_token_distributions_optimism_project_wallets.sql).
- Add the wallet to the `intermediate_wallets` if the wallet represents an internal team wallet (i.e. team multisig).
- Add the wallet to the `distributor_wallets` if the wallet represents a token distribution wallet (i.e. airdrop distributior, liquidity mining gauge).

[Request for Contributions] OP Rewards: Project Wallet Mapping

suggested changes for https://docs.optimism.io/builders/cex-wallet-developers/wallet-support
- update for gotchas when running a smart contract wallet 
- link to some guide on how to use the RPC
- link to [this page](https://docs.optimism.io/stack/transaction-fees/overview) for the fee section since wallet providers ask about this often

[AUDIT] Wallet support page revisions

**Is your feature request related to a problem? Please describe.**
Currently, the alternative implementations of OP Stack components, apart from `op-erigon` and `asterisc`, cannot take advantage of the superchain registry. This creates a sharded collection of chain configurations, where components like `op-reth`, `magi`, `hildr`, `op-besu`, `op-nethermind`, `cannon-rs`, the Rust FPP, and whatever comes in the future that isn't written in Golang, cannot take advantage of this package.

**Describe the solution you'd like**
Modularize the superchain registry such that it can be used by all OP Stack components, preparing for a future where our critical infrastructure is implemented in many more languages than just `Go`.

Ideally, this means defining a core implementation, preferably in a language such as `C`, `C++`, or `Rust` that is more friendly for interop, and then creating FFI bindings that enable several front-end APIs to be built for the library.

We currently need support for:
* `Java`
* `Rust`
* `C#`

**Describe alternatives you've considered**
1. Implement separate versions of the `superchain-registry` repository for each language that the OP Stack's core components are built upon. This would require a decent bit of duplicated code, increasing the possibility of divergent configuration between the implementations.
2. Create FFI bindings from the Go implementation. Go does not lend itself well towards being called via FFI, and `Cgo` is a bit horrendous to work with when the direction is `<language>` -> `Go` rather than `Go` -> `<language>`. It requires `cbindgen` to embed Go types and semantics into the C header, etc. Rather than doing this, we should choose a more FFI friendly language that is closer to `C` (or, even `C`/`C++` itself) for the base implementation.

**Additional context**
Modularizing the superchain registry will pay dividends in the future, offering a central, interoperable library for every OP Stack component to share the same configuration utilities.


feat: Support all OP Stack components

## Brief Description of the Docs Request
There are a few outstanding items on [rpc methods](https://docs.optimism.io/node-operators/json-rpc) that require updating from a developer running an op stack chain. 

## Description of the Documentation You'd Like

- [ ] [admin section](https://docs.optimism.io/node-operators/json-rpc#admin), needs description
- [ ] [this item](https://docs.optimism.io/node-operators/json-rpc#admin_resetderivationpipeline), needs sample success output
- [ ] [this item](https://docs.optimism.io/node-operators/json-rpc#admin_startsequencer), missing sample success output
- [ ] [this item](https://docs.optimism.io/node-operators/json-rpc#admin_stopsequencer), needs sample success output
- [ ] [this last item](https://docs.optimism.io/node-operators/json-rpc#admin_sequenceractive), missing sample success output

## Links to Related Pages
n/a

## Additional Context
We want to provide the community with complete documentation. :)

[DOCS] Update RPC methods with op stack chain info

revisions for this page: https://docs.optimism.io/builders/chain-operators/tutorials/sdk
- This tool is relevant for OP Mainnet developers too, there should probably be a reference to it there, maybe just as a link to this page
- There are lots of smaller tutorials around the SDK all over the docs, might be nice to put them all in one place by linking them here!

[AUDIT] Add more links to diff sdk tutorials

when running a private L1 network,  the CREATE2 factory contract is not already deployed.

The steps that they would need to take:
• spin up private L1 network
• fund the create2 deployer account and deploy the create2 deployer
    ◦ These two commands can be found on the <https://github.com/ethereum-optimism/optimism/blob/536b44b0c6b5317c6a5dba9bad85ebdd069cbac8/bedrock-devnet/devnet/__init__.py#L123-L133|devnet init script>
• deploy the  L1 contracts (they will use the create2 deployer)
• deploy the OP Stack


[TUTORIAL] run op stack on a private L1 network

## Brief Description of the Docs Request
Feedback from devconnect about dev-node tutorial

## Description of the Documentation You'd Like
I'll point out some minor issues in the docs that we noticed during setup:

- The [optimism docs](https://community.optimism.io/docs/developers/build/dev-node/#) do not mention that you need to build the bedrock contracts prior to the deployment (only the [github wiki](https://github.com/ethereum-optimism/optimism/blob/65ec61dde94ffa93342728d324fecf474d228e1f/specs/meta/devnet.md) has this info).
- The contracts are located in the packages/bedrock-contracts, while the github wiki instructs to build from packages/contracts (does not exist).
- When building the contracts using yarn (as per the guidelines in the docs), we were prompted to use pnpm instead. Using pnpm the installation and build process worked fine.

## Links to Related Pages
n/a

## Additional Context
dev-node tutorial and github wiki need to be updated to match

[FEEDBACK] Update dev-node tutorial + github wiki

### Project
Yearn
### Description
Deep-dive on Yearn's Optimism yVaults boosted yields which distribute 25K OP for 40 weeks. Boost currently is live on USDC, DAI, USDT, and WETH vaults. How is Yearn's program performing as compared to other similar incentive programs? How long will those TVL be kept on Optimism? Anything else you want to suggest or recommend for liquidity incentives?
There's also Yearn Coinbase Quest live at the same time, can you help differentiate that? 
### Find out more
https://www.notion.so/oplabs/Yearn-3274e9ac94654fa7a84174c4cd810e2a?pvs=4

[Request for Contributions] OP Rewards: Yearn Deep-dives

**Is your doc request related to a problem or existing docs? Please describe.**

One of our users lost their ERC20s by directly sending them to a bridge implementation contract.

**Describe the documentation you'd like**

Create new user documentation around bridging tokens and ether with multisig (Safe) wallets.

**Additional context**
Add any other context or screenshots about the feature request here.


[DOCS] add instructions on how to bridge ERC20s/ETH with multisig wallets

Opening up discussion for requirements / ideas for creating an open-source registry for any and all OP Chains & OP Stack Forks.

**Problem:**
Crypto data teams have a super hard time keeping track of deployed OP Chains & OP Stack Forks. Some chain deployers attempt to get in touch with OP Labs / OP Foundation, but otherwise this requires sleuthing through Twitter, blog posts, news aggregators, etc. Many people maintain their own lists with varying degrees of comprehensiveness (nobody knows how many production mainnet chains actually exist)

To solve for this, want to create a shared open-source resource for analysts, developers, educators, etc to identify OP Chains & OP Stack Forks with the relevant information about them.

See [Key Definitions for Chain Segments](https://community.optimism.io/docs/contribute/important-terms/#the-superchain)

**Goals:**
- Be the best "source of truth" for identifying metadata for OP Chains & OP Stack Forks
- Store relevant information for analysts (i.e. Name, RPC, Block Explorer, L1 Contracts, Chain Configuration)
- Make it SUPER easy to contribute to (i.e. easy to add new chains, easy to modify data, easy to add bespoke attributes)
- Make it SUPER easy to read from (i.e. if we input in yml, outputs are available in csv, json, sql, etc)
- Provide the necessary metadata for analysts to create chain segments (i.e. RAAS provider, DA Layer, other Config Changes, potential superchain compatibility)
- Be scalable, we don't want to have to re-do this if/when there are thousands of chains

**Existing Version(s):**
- op-analytics Repo [`chain_metadata`](https://github.com/ethereum-optimism/op-analytics/blob/main/op_chains_tracking/inputs/chain_metadata.csv)
- Dune Upload from OP Labs CRM [`dataset_op_stack_chain_metadata`](https://dune.com/queries/3109219)
- [superchain-registry](https://github.com/ethereum-optimism/superchain-registry) repo
- [superchain.eco](https://www.superchain.eco/ecosystem/chains)

**Other Inspiration / Attempts:**
- [L2Beat](https://l2beat.com/scaling/summary)
- [growthepie](https://www.growthepie.xyz/)
- [Kofi's Rollup Economics](https://dune.com/niftytable/rollup-economics)
- [OP Stack Data Dashboard](https://dune.com/oplabspbc/op-stack-chains-l1-activity)
- [ethereum-lists/chains](https://github.com/ethereum-lists/chains)

**Open Questions:**
- What are the top use cases for this? (_Non-Labs teams, please share!_)
- What fields do we need to track? What "requirements" should this have?
--
- What's the best input format (i.e. csv, yml), output formats to be available (i.e. csv, json, sql cte)?
- What is the right organizational structure? (i.e. one ecosystem/chain deployer can have multiple chains, there may be a gazillion chains)
--
- How can we "automate" parts of this? (i.e. identify new L2s via L1 contracts - somehow tie that back to metadata)
- What could/should be onchain?
--
- What's the process for accepting/rejecting/verifying changes?
- How do we incentivize chain deployers to "register"?

[Idea Discussion] Open-Source OP Chain & OP Stack Forks Metadata Source

## Description

We don't want to write docs for the cli we want to generate it in a script. It appears pretty easy to do looking at this https://github.com/urfave/cli/pull/830. We also want to make s

## Tasks

- [ ] Add a new `scripts/` package
- [ ] Add a script to generate markdown doc for cli app into docs/cli.md
- [ ] (optional) Add check to circleci config that make sure generated docs are up to date

[Nice to have] Generate markdown docs about the cli from urfavecli

### Project
Rabbithole
### Description
Protocol deep-dive for Rabbithole to measure the impact of its Optimism Weekly Quests, areas to explore include but not limited to how quests are onboarding users/wallets to Optimism, does amount of OP reward correlate with retention, do some quests perform better than others, what else can we learn to help Rabbithole team to design future quests on Optimism
### Find out more
https://www.notion.so/oplabs/Rabbit-Hole-d1074aa502fd415290a6cacf81fe9820?pvs=4

[Request for Contributions] OP Rewards: Rabbithole Deep-dives

## Description

In https://github.com/ethereum-optimism/mocktimism/pull/46 we added a way of publishing mocktimism to npm. To make it cross platform we need to add postinstall scripts.  Example of this is here https://github.com/ethereum-optimism/mocktimism/pull/46

## Tasks

- [ ] Add necessary scripts

Optimism

About

Team

Bounties

Jobs