Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

App Ids for Forks

Anxo Rodriguez edited this page Aug 28, 2020 · 20 revisions

The APP ID is a required config parameter.

Every transaction sends an additional payload with the app. This ID allows to track the app where a transaction comes from.

APP ID APP
01 Gnosis Protocol Web (default for local development)
02 Mesa
03 Razor Network
04 StarCurve
05 Gnosis Safe App: CMM

Anyone can get it's own App Id. Keep reading if you need one :)

โ“ How to get your App Id

Write in our Discord Community Chat to get the App Id.

Message example:


Hello, I'm forking Gnosis Protocol Frontend, I would love to get an APP ID assiged in the wiki https://github.com/gnosis/dex-react/wiki/App-Ids-for-Forks 

My project details are:
* Name: <your-name>
* Project: <project_name>
* Url for the project: <website>
* Any additional information: <add any relevant information, like why you want to fork the front end, and what are your plans>


๐Ÿ“Š How is the appId used

Every transaction sent to the blockchain will include, the appId and some analytics flags as an additional payload.

This will allow to identify which Dapp or client is submitting the transaction, and some basic analytic data, like browser, wallet or screen size.

The transactions will have in their data: <normal-payload><sentinel><appId><analytics-data>

Where:

  • normal-payload is the ABI encoded parameters of the call
  • sentinel is always dec0de
  • appId identifies the app
  • analytics-data are 6 digits: 2 for provider name, 1 for mobile or desktop flag, 2 for browser name, 1 for screen size.

For example given

i.e.
<normal-payload>dec0de01010130

๐ŸดLearn more about forks

The web can be forked. This way any project can use its own token list, rebrand it, add new pages or modify the existing ones.

Read more here.

Clone this wiki locally