{"id":20246432,"url":"https://github.com/vitelabs/go-vite","last_synced_at":"2025-04-07T23:13:49.130Z","repository":{"id":33261116,"uuid":"133392857","full_name":"vitelabs/go-vite","owner":"vitelabs","description":"Official Go implementation of the Vite protocol","archived":false,"fork":false,"pushed_at":"2024-09-26T15:11:39.000Z","size":135510,"stargazers_count":322,"open_issues_count":36,"forks_count":94,"subscribers_count":32,"default_branch":"master","last_synced_at":"2025-03-31T22:18:15.018Z","etag":null,"topics":["blockchain","cryptocurrency","dag","golang","ledger","smart-contracts","vite"],"latest_commit_sha":null,"homepage":"https://vite.org/","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/vitelabs.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2018-05-14T16:43:43.000Z","updated_at":"2025-03-28T18:44:32.000Z","dependencies_parsed_at":"2024-04-21T06:25:17.165Z","dependency_job_id":"093abc64-3276-4637-bffb-c2ae7ac4632f","html_url":"https://github.com/vitelabs/go-vite","commit_stats":null,"previous_names":[],"tags_count":67,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/vitelabs%2Fgo-vite","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/vitelabs%2Fgo-vite/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/vitelabs%2Fgo-vite/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/vitelabs%2Fgo-vite/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/vitelabs","download_url":"https://codeload.github.com/vitelabs/go-vite/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247744335,"owners_count":20988783,"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":["blockchain","cryptocurrency","dag","golang","ledger","smart-contracts","vite"],"created_at":"2024-11-14T09:29:09.431Z","updated_at":"2025-04-07T23:13:49.102Z","avatar_url":"https://github.com/vitelabs.png","language":"Go","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"https://github.com/vitelabs/doc.vite.org/blob/master/docs/.vuepress/public/logo_black.svg\" alt=\"Logo\" width='300px' height='auto'/\u003e\n\u003c/div\u003e\n\n\u003cbr /\u003e\n\n[Vite](https://vite.org) is a next-generation Reactive Blockchain that adopts a _message-driven, asynchronous architecture and a DAG-based ledger_.\nThe goal for Vite’s design is to _provide a reliable public platform for industrial dApps_, with features of ultra-high throughput and scalability.\n\n## Go Vite\n\nOfficial golang implementation of Vite Protocol\n\n[![GitHub release](https://img.shields.io/github/release/vitelabs/go-vite.svg)](https://github.com/vitelabs/go-vite/releases)\n[![Go Report Card](https://goreportcard.com/badge/github.com/vitelabs/go-vite)](https://goreportcard.com/report/github.com/vitelabs/go-vite)\n[![GitHub closed pull requests](https://img.shields.io/github/issues-pr-closed/vitelabs/go-vite.svg)](https://github.com/vitelabs/go-vite/pulls)\n[![Downloads](https://img.shields.io/github/downloads/vitelabs/go-vite/total.svg)](https://github.com/vitelabs/go-vite/releases)\n\n\nThe go-vite binary files can be download from [releases](https://github.com/vitelabs/go-vite/releases).\n\n\n## Guides \u0026 Documentation\n   * [White Paper](https://github.com/vitelabs/whitepaper/blob/master/vite_en.pdf)\n   * [Documentation](https://docs.vite.org)\n   * [Techblog](https://docs.vite.org/vite-docs/articles/)\n   * [Runing a node](https://vite.wiki/tutorial/node/install.html) \n\n## Product\n   * [Products Navigation](https://vite.net)\n   * [Web Wallet](https://wallet.vite.net)\n   * [Desktop Wallet](https://github.com/vitelabs/vite-wallet)\n   * [Wallet App](https://app.vite.net) open through mobile browser\n   * [Block Explorer](https://vitescan.io/)\n\n## Links \u0026 Resources\n   * [Project Vite official Website](https://www.vite.org/)\n   * [Vite products](https://vite.net)\n   * [Twitter](https://twitter.com/vitelabs)\n   * [Telegram](https://t.me/vite_en)\n   * [Telegram Announcement](https://t.me/vite_ann)\n   * [Reddit](https://www.reddit.com/r/vitelabs)\n   * [Discord](https://discordapp.com/invite/CsVY76q)\n   * [Youtube](https://www.youtube.com/channel/UC8qft2rEzBnP9yJOGdsJBVg)\n   * [Forum](https://forum.vite.net/)\n\n## Installation\n\nYou can choose one of the following installation options:\n\n- [Install from binary](https://docs.vite.org/vite-docs/tutorial/node/install.html#install-from-binary)\n- [Install from source](https://docs.vite.org/vite-docs/tutorial/node/install.html#install-from-source)\n\n### Faster ledger sync\n\n[download](ledger_snapshot.md) gvite ledger file manually.\n\n## Versioning\n\nGiven a version number MAJOR.MINOR.BUILD, increment the:\n\n1. MAJOR version when you make a significant update of the protocol (like Ethereum, Ethereum 2.0 is rather a new blockchain from Ethereum 1.0),\n2. MINOR version when you introduce some breaking changes, and\n3. BUILD version when you make non-breaking changes such as bug fixes, RPC modifications, code refactoring, test updates, etc.\n\n## Branching\n\nThe `master` branch is the working branch for the next release. \n- Breaking changes should not be merged into `master` unless as described below.\n- Non-breaking changes should be merged into `master`.\n\n1) A new branch should be checked out from `master` before releasing a new version. \n    - Say the latest version running on mainnet is 2.12.2, we can checkout a branch named `release_v2.12.3` from `master` for building, deploying on testnet, releasing the binary and deploying on mainnet.\n\n2) A development branch for the next breaking changes, for example `v2.13`, will be checked out from `master`. \n    - Any commits from `master` are required to be merged into `v2.13` (or rebase `v2.13` onto `master`) as soon as possible. \n    - All unit tests and integration tests should pass before merging a pull request.\n\n3) Merge `v2.13` into `master` and checkout `release_v2.13.0` from `master` before the mainnet upgrade. \n    - This means that v2.13.0 is the next release and there are no more releases of version 2.12.x. \n    - The branch `v2.13` reached end-of-life and a new branch `v2.14` for the next breaking changes should be checked out from `master`.\n    - From this point onwards, any new commits which are merged into `master` are based on version 2.13.\n\nAny changes should be committed to your personal fork followed by opening a PR in the official repository.\n\n## Contribution\n\nThank you for considering to help out with the source code! We welcome any contributions no matter how small they are!\n\nIf you'd like to contribute to go-vite, please fork, fix, commit and send a pull request for the maintainers to review and merge into the main code base.\n\nPlease make sure your contributions adhere to our coding guidelines:\n\n- Code must adhere to the official Go [formatting](https://golang.org/doc/effective_go.html#formatting) guidelines.\n- Code must be documented adhering to the official Go [commentary](https://golang.org/doc/effective_go.html#commentary) guidelines.\n- Pull requests need to be based on and opened against the `master` branch.\n- Open an issue before submitting a PR for non-breaking changes.\n- Publish a VEP proposal before submitting a PR for breaking changes.\n\n## License\n\nThe go-vite source code is licensed under [GPLv3](https://www.gnu.org/licenses/gpl-3.0.html), also included in the `LICENSE` file.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fvitelabs%2Fgo-vite","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fvitelabs%2Fgo-vite","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fvitelabs%2Fgo-vite/lists"}