{"id":15928720,"url":"https://github.com/0xfuturistic/vrgda-rollup","last_synced_at":"2025-03-24T15:32:21.739Z","repository":{"id":184942116,"uuid":"672621833","full_name":"0xfuturistic/vrgda-rollup","owner":"0xfuturistic","description":"Minting the proposer for the OP Stack with Variable Rate Gradual Dutch Auctions (VRGDAs)","archived":false,"fork":false,"pushed_at":"2023-10-27T09:13:22.000Z","size":167374,"stargazers_count":5,"open_issues_count":61,"forks_count":0,"subscribers_count":1,"default_branch":"develop","last_synced_at":"2025-03-19T03:57:42.435Z","etag":null,"topics":["ethereum","rollups","solidity","vrgdas"],"latest_commit_sha":null,"homepage":"","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/0xfuturistic.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":"CITATION.cff","codeowners":".github/CODEOWNERS","security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-07-30T17:46:38.000Z","updated_at":"2023-10-30T17:35:39.000Z","dependencies_parsed_at":"2024-10-06T23:51:45.638Z","dependency_job_id":null,"html_url":"https://github.com/0xfuturistic/vrgda-rollup","commit_stats":null,"previous_names":["0xfuturistic/verbose-fortnight","0xfuturistic/vrgda-rollup"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/0xfuturistic%2Fvrgda-rollup","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/0xfuturistic%2Fvrgda-rollup/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/0xfuturistic%2Fvrgda-rollup/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/0xfuturistic%2Fvrgda-rollup/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/0xfuturistic","download_url":"https://codeload.github.com/0xfuturistic/vrgda-rollup/tar.gz/refs/heads/develop","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":245298345,"owners_count":20592591,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ethereum","rollups","solidity","vrgdas"],"created_at":"2024-10-06T23:41:46.618Z","updated_at":"2025-03-24T15:32:16.730Z","avatar_url":"https://github.com/0xfuturistic.png","language":"Go","funding_links":[],"categories":[],"sub_categories":[],"readme":"\n\u003cdiv align=\"center\"\u003e\n  \u003cbr /\u003e\n  \u003cbr /\u003e\n  \u003ca href=\"https://optimism.io\"\u003e\u003cimg alt=\"Optimism\" src=\"https://raw.githubusercontent.com/ethereum-optimism/brand-kit/main/assets/svg/OPTIMISM-R.svg\" width=600\u003e\u003c/a\u003e\n  \u003cbr /\u003e\n  \u003ch3\u003e\u003ca href=\"https://optimism.io\"\u003eOptimism\u003c/a\u003e is Ethereum, scaled.\u003c/h3\u003e\n  \u003cbr /\u003e\n\u003c/div\u003e\n\n## What is Optimism?\n\n[Optimism](https://www.optimism.io/) is a project dedicated to scaling Ethereum's technology and expanding its ability to coordinate people from across the world to build effective decentralized economies and governance systems. The [Optimism Collective](https://app.optimism.io/announcement) builds open-source software for running L2 blockchains and aims to address key governance and economic challenges in the wider cryptocurrency ecosystem. Optimism operates on the principle of **impact=profit**, the idea that individuals who positively impact the Collective should be proportionally rewarded with profit. **Change the incentives and you change the world.**\n\nIn this repository, you'll find numerous core components of the OP Stack, the decentralized software stack maintained by the Optimism Collective that powers Optimism and forms the backbone of blockchains like [OP Mainnet](https://explorer.optimism.io/) and [Base](https://base.org). Designed to be \"aggressively open source,\" the OP Stack encourages you to explore, modify, extend, and test the code as needed. Although not all elements of the OP Stack are contained here, many of its essential components can be found within this repository. By collaborating on free, open software and shared standards, the Optimism Collective aims to prevent siloed software development and rapidly accelerate the development of the Ethereum ecosystem. Come contribute, build the future, and redefine power, together.\n\n## Documentation\n\n- If you want to build on top of OP Mainnet, refer to the [Optimism Community Hub](https://community.optimism.io)\n- If you want to build your own OP Stack based blockchain, refer to the [OP Stack docs](https://stack.optimism.io)\n- If you want to contribute to the OP Stack, check out the [Protocol Specs](./specs)\n\n## Community\n\nGeneral discussion happens most frequently on the [Optimism discord](https://discord.gg/optimism).\nGovernance discussion can also be found on the [Optimism Governance Forum](https://gov.optimism.io/).\n\n## Contributing\n\nRead through [CONTRIBUTING.md](./CONTRIBUTING.md) for a general overview of the contributing process for this repository.\nUse the [Developer Quick Start](./CONTRIBUTING.md#development-quick-start) to get your development environment set up to start working on the Optimism Monorepo.\nThen check out the list of [Good First Issues](https://github.com/ethereum-optimism/optimism/contribute) to find something fun to work on!\n\n## Security Policy and Vulnerability Reporting\n\nPlease refer to the canonical [Security Policy](https://github.com/ethereum-optimism/.github/blob/master/SECURITY.md) document for detailed information about how to report vulnerabilities in this codebase.\nBounty hunters are encouraged to check out [the Optimism Immunefi bug bounty program](https://immunefi.com/bounty/optimism/).\nThe Optimism Immunefi program offers up to $2,000,042 for in-scope critical vulnerabilities.\n\n## The Bedrock Upgrade\n\nOP Mainnet is currently preparing for [its next major upgrade, Bedrock](https://dev.optimism.io/introducing-optimism-bedrock/).\nYou can find detailed specifications for the Bedrock upgrade within the [specs folder](./specs) in this repository.\n\nPlease note that a significant number of packages and folders within this repository are part of the Bedrock upgrade and are NOT currently running in production.\nRefer to the Directory Structure section below to understand which packages are currently running in production and which are intended for use as part of the Bedrock upgrade.\n\n## Directory Structure\n\n\u003cpre\u003e\n~~ Production ~~\n├── \u003ca href=\"./packages\"\u003epackages\u003c/a\u003e\n│   ├── \u003ca href=\"./packages/common-ts\"\u003ecommon-ts\u003c/a\u003e: Common tools for building apps in TypeScript\n│   ├── \u003ca href=\"./packages/contracts-bedrock\"\u003econtracts-bedrock\u003c/a\u003e: Bedrock smart contracts.\n│   ├── \u003ca href=\"./packages/core-utils\"\u003ecore-utils\u003c/a\u003e: Low-level utilities that make building Optimism easier\n│   ├── \u003ca href=\"./packages/chain-mon\"\u003echain-mon\u003c/a\u003e: Chain monitoring services\n│   └── \u003ca href=\"./packages/sdk\"\u003esdk\u003c/a\u003e: provides a set of tools for interacting with Optimism\n├── \u003ca href=\"./op-bindings\"\u003eop-bindings\u003c/a\u003e: Go bindings for Bedrock smart contracts.\n├── \u003ca href=\"./op-batcher\"\u003eop-batcher\u003c/a\u003e: L2-Batch Submitter, submits bundles of batches to L1\n├── \u003ca href=\"./op-bootnode\"\u003eop-bootnode\u003c/a\u003e: Standalone op-node discovery bootnode\n├── \u003ca href=\"./op-chain-ops\"\u003eop-chain-ops\u003c/a\u003e: State surgery utilities\n├── \u003ca href=\"./op-challenger\"\u003eop-challenger\u003c/a\u003e: Dispute game challenge agent\n├── \u003ca href=\"./op-e2e\"\u003eop-e2e\u003c/a\u003e: End-to-End testing of all bedrock components in Go\n├── \u003ca href=\"./op-exporter\"\u003eop-exporter\u003c/a\u003e: Prometheus exporter client\n├── \u003ca href=\"./op-heartbeat\"\u003eop-heartbeat\u003c/a\u003e: Heartbeat monitor service\n├── \u003ca href=\"./op-node\"\u003eop-node\u003c/a\u003e: rollup consensus-layer client\n├── \u003ca href=\"./op-program\"\u003eop-program\u003c/a\u003e: Fault proof program\n├── \u003ca href=\"./op-proposer\"\u003eop-proposer\u003c/a\u003e: L2-Output Submitter, submits proposals to L1\n├── \u003ca href=\"./op-service\"\u003eop-service\u003c/a\u003e: Common codebase utilities\n├── \u003ca href=\"./op-signer\"\u003eop-signer\u003c/a\u003e: Client signer\n├── \u003ca href=\"./op-wheel\"\u003eop-wheel\u003c/a\u003e: Database utilities\n├── \u003ca href=\"./ops-bedrock\"\u003eops-bedrock\u003c/a\u003e: Bedrock devnet work\n├── \u003ca href=\"./proxyd\"\u003eproxyd\u003c/a\u003e: Configurable RPC request router and proxy\n└── \u003ca href=\"./specs\"\u003especs\u003c/a\u003e: Specs of the rollup starting at the Bedrock upgrade\n\n~~ Pre-BEDROCK ~~\n├── \u003ca href=\"./packages\"\u003epackages\u003c/a\u003e\n│   ├── \u003ca href=\"./packages/common-ts\"\u003ecommon-ts\u003c/a\u003e: Common tools for building apps in TypeScript\n│   ├── \u003ca href=\"./packages/core-utils\"\u003ecore-utils\u003c/a\u003e: Low-level utilities that make building Optimism easier\n│   ├── \u003ca href=\"./packages/chain-mon\"\u003echain-mon\u003c/a\u003e: Chain monitoring services\n│   └── \u003ca href=\"./packages/sdk\"\u003esdk\u003c/a\u003e: provides a set of tools for interacting with Optimism\n├── \u003ca href=\"./indexer\"\u003eindexer\u003c/a\u003e: indexes and syncs transactions\n├── \u003ca href=\"./op-exporter\"\u003eop-exporter\u003c/a\u003e: A prometheus exporter to collect/serve metrics from an Optimism node\n├── \u003ca href=\"./proxyd\"\u003eproxyd\u003c/a\u003e: Configurable RPC request router and proxy\n└── \u003ca href=\"./technical-documents\"\u003etechnical-documents\u003c/a\u003e: audits and post-mortem documents\n\u003c/pre\u003e\n\n## Branching Model\n\n### Active Branches\n\n| Branch          | Status                                                                           |\n| --------------- | -------------------------------------------------------------------------------- |\n| [master](https://github.com/ethereum-optimism/optimism/tree/master/)                   | Accepts PRs from `develop` when intending to deploy to production.                  |\n| [develop](https://github.com/ethereum-optimism/optimism/tree/develop/)                 | Accepts PRs that are compatible with `master` OR from `release/X.X.X` branches.                    |\n| release/X.X.X                                                                          | Accepts PRs for all changes, particularly those not backwards compatible with `develop` and `master`. |\n\n### Overview\n\nThis repository generally follows [this Git branching model](https://nvie.com/posts/a-successful-git-branching-model/).\nPlease read the linked post if you're planning to make frequent PRs into this repository.\n\n### Production branch\n\nThe production branch is `master`.\nThe `master` branch contains the code for latest \"stable\" releases.\nUpdates from `master` **always** come from the `develop` branch.\n\n### Development branch\n\nThe primary development branch is [`develop`](https://github.com/ethereum-optimism/optimism/tree/develop/).\n`develop` contains the most up-to-date software that remains backwards compatible with the latest experimental [network deployments](https://community.optimism.io/docs/useful-tools/networks/).\nIf you're making a backwards compatible change, please direct your pull request towards `develop`.\n\n**Changes to contracts within `packages/contracts-bedrock/contracts` are usually NOT considered backwards compatible and SHOULD be made against a release candidate branch**.\nSome exceptions to this rule exist for cases in which we absolutely must deploy some new contract after a release candidate branch has already been fully deployed.\nIf you're changing or adding a contract and you're unsure about which branch to make a PR into, default to using the latest release candidate branch.\nSee below for info about release candidate branches.\n\n### Release candidate branches\n\nBranches marked `release/X.X.X` are **release candidate branches**.\nChanges that are not backwards compatible and all changes to contracts within `packages/contracts-bedrock/contracts` MUST be directed towards a release candidate branch.\nRelease candidates are merged into `develop` and then into `master` once they've been fully deployed.\nWe may sometimes have more than one active `release/X.X.X` branch if we're in the middle of a deployment.\nSee table in the **Active Branches** section above to find the right branch to target.\n\n## Releases\n\n### Changesets\n\nWe use [changesets](https://github.com/changesets/changesets) to mark packages for new releases.\nWhen merging commits to the `develop` branch you MUST include a changeset file if your change would require that a new version of a package be released.\n\nTo add a changeset, run the command `pnpm changeset` in the root of this monorepo.\nYou will be presented with a small prompt to select the packages to be released, the scope of the release (major, minor, or patch), and the reason for the release.\nComments within changeset files will be automatically included in the changelog of the package.\n\n### Triggering Releases\n\nReleases can be triggered using the following process:\n\n1. Create a PR that merges the `develop` branch into the `master` branch.\n2. Wait for the auto-generated `Version Packages` PR to be opened (may take several minutes).\n3. Change the base branch of the auto-generated `Version Packages` PR from `master` to `develop` and merge into `develop`.\n4. Create a second PR to merge the `develop` branch into the `master` branch.\n\nAfter merging the second PR into the `master` branch, packages will be automatically released to their respective locations according to the set of changeset files in the `develop` branch at the start of the process.\nPlease carry this process out exactly as listed to avoid `develop` and `master` falling out of sync.\n\n**NOTE**: PRs containing changeset files merged into `develop` during the release process can cause issues with changesets that can require manual intervention to fix.\nIt's strongly recommended to avoid merging PRs into develop during an active release.\n\n## License\n\nAll other files within this repository are licensed under the [MIT License](https://github.com/ethereum-optimism/optimism/blob/master/LICENSE) unless stated otherwise.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2F0xfuturistic%2Fvrgda-rollup","html_url":"https://awesome.ecosyste.ms/projects/github.com%2F0xfuturistic%2Fvrgda-rollup","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2F0xfuturistic%2Fvrgda-rollup/lists"}