[OP Stack Deployment] Which documentation should I use as existing one is not recommended by OP Stack itself #675
Unanswered
OpenArmand
asked this question in
Deploying the OP Stack
Replies: 2 comments 3 replies
-
Hello. |
Beta Was this translation helpful? Give feedback.
2 replies
-
ok, I have done the dirtywork of figuring this out and can clean up your
documentation. Could there be a small reward for helping? As we've made our
own L2 and have observed gaps and we can patch for you documentation wise.
…On Mon, Dec 16, 2024 at 4:50 AM hashigo ***@***.***> wrote:
I don't know which parts of the documentation are outdated.
—
Reply to this email directly, view it on GitHub
<#675 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALJ6ZA6OO722F3REHAXQBUT2FYFFRAVCNFSM6AAAAABTOF4FTGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJXGUYTCMI>
.
You are receiving this because you authored the thread.Message ID:
<ethereum-optimism/developers/repo-discussions/675/comments/11575111@
github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
i was going to use this to build a chain on testnet:https://docs.optimism.io/builders/chain-operators/tutorials/create-l2-rollup
but it says "Please do not rely on the content of this page as it is currently undergoing maintenance. Code samples and solutions may not function as expected. Please check back for an update or signup to help us revise this page. We welcome your contribution! ❤️"
so what should i do instead? should i wait for the update if it's in like the next few days? or how should i get this tutorial otherwise?
Logs
No response
Additional Information
I’m building OpenWork (https://openwork.technology/), a decentralized work protocol that we plan to build directly on the OP Stack.
OpenWork enables two strangers to safely enter work contracts, pay in crypto, use escrow services, resolve disputes, build reputations, and maintain self-custody of their profiles, all without the need for a centralized authority of any kind.
Our vision includes a “1 job = 1 block” model, where every completed job is recorded as its own block. By doing this, we aim to make posting, completion, skill verification, and even dispute resolution fully transparent and trustless on-chain. We see the OP Stack as the perfect foundation for creating more openness, fairness, and efficiency in work arrangements.
Optimistic about to working with OP Stack with your support!
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions