Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

Commit

Permalink
Chore/depr notice (#1119)
Browse files Browse the repository at this point in the history
* add README changes

* format readme

* add link

* add bootstrap notice

* fix wording
  • Loading branch information
opaolini authored Aug 11, 2021
1 parent d76af70 commit a40744b
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 0 deletions.
9 changes: 9 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,15 @@
[![Chat with us on Discord](https://img.shields.io/badge/chat-Discord-blueViolet.svg)](https://discord.gg/HF7fHwk)
[![Circle CI](https://img.shields.io/circleci/project/0xProject/0x-mesh/master.svg)](https://circleci.com/gh/0xProject/0x-mesh/tree/master)

⚠️ **DEPRECATION NOTICE** ⚠️

This repository is no longer being maintained. 0x Labs isn’t keeping it aligned with future 0x protocol versions, nor is updating its dependencies with other blockchain protocols. We welcome other team’s contributions to do that if they find value in it.
If you’re looking to integrate orderbook-like capabilities in your application, we encourage you to try [0x API /orderbook service instead](http://0x.org/docs/api)

We intend to keep 0x-mesh bootstrap nodes up for the foreseeable future, however you can always set up your own [mesh-bootstrap nodes](cmd/mesh-boostrap) and configure the 0x-mesh nodes via the `BOOTSTRAP_LIST` environment variable.

---

# 0x Mesh

0x Mesh is a peer-to-peer network for sharing orders that adhere to the
Expand Down
6 changes: 6 additions & 0 deletions docs/deployment_with_telemetry.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
[![Version](https://img.shields.io/badge/version-11.2.0-orange.svg)](https://github.com/0xProject/0x-mesh/releases)

# Deprecation Notice
Since 0x-Mesh will no longer be maintained we also deprecate our telemetry log ingest, that means our telemetry endpoint will return `200` for all requests and not store new logs. We return `200` to make sure your local fluentbit will not continously retry sending logs our way.

You can disable telemetry by removing the logging configuration from your `docker-compose.yml` and spinning down the `fluentbit` and `esproxy` services.


## Deploying a Telemetry-Enabled Mesh Node

0x Mesh is completely permissionless and the beta is open to anyone who wants to
Expand Down

0 comments on commit a40744b

Please sign in to comment.