mirror of https://github.com/status-im/specs.git
Addressed comments
This commit is contained in:
parent
a12d4338c4
commit
f5e71d2a91
|
@ -1,10 +1,18 @@
|
||||||
---
|
---
|
||||||
title: 3rd party APIs used for core functionality that impacts things like availability/censorship and privacy
|
permalink: /spec/9
|
||||||
version: 0.1.0
|
parent: Stable specs
|
||||||
status: Draft
|
title: 9/3RD-PARTY
|
||||||
authors:
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
# 9/3RD-PARTY
|
||||||
|
|
||||||
|
> Version: 0.1
|
||||||
|
>
|
||||||
|
> Status: Draft
|
||||||
|
>
|
||||||
|
> Authors: Volodymyr Kozieiev <volodymyr@status.im>
|
||||||
|
|
||||||
|
|
||||||
# 3rd party APIs used for core functionality that impacts things like availability/censorship and privacy
|
# 3rd party APIs used for core functionality that impacts things like availability/censorship and privacy
|
||||||
|
|
||||||
## Table of Contents
|
## Table of Contents
|
||||||
|
@ -12,7 +20,7 @@ authors:
|
||||||
1. [Abstract](Abstract)
|
1. [Abstract](Abstract)
|
||||||
2. [Definitions](#definitions)
|
2. [Definitions](#definitions)
|
||||||
3. [Why 3rd party API can be a problem?](#why-3rd-party-api-can-be-a-problem)
|
3. [Why 3rd party API can be a problem?](#why-3rd-party-api-can-be-a-problem)
|
||||||
4. [3rd party APIs used by Status](#3rd-party-apis-used-by-status)
|
4. [3rd party APIs used by Status](#3rd-party-apis-used-by-current-status-app)
|
||||||
* [Infura](#infura)
|
* [Infura](#infura)
|
||||||
* [Etherscan](#etherscan)
|
* [Etherscan](#etherscan)
|
||||||
* [CryptoCompare](#cryptocompare)
|
* [CryptoCompare](#cryptocompare)
|
||||||
|
@ -23,7 +31,12 @@ authors:
|
||||||
7. [Copyright](#copyright)
|
7. [Copyright](#copyright)
|
||||||
|
|
||||||
## Abstract
|
## Abstract
|
||||||
In this specification listed 3rd party APIs that Status functionality rely on.
|
In this specification listed 3rd party APIs that Status rely on. With the help of that APIs Status:
|
||||||
|
- communicates to Ethereum network
|
||||||
|
- allows user to see address and transaction details on external website
|
||||||
|
- gets fiat<->crypto exchange prices
|
||||||
|
- gets information about collectibles
|
||||||
|
- hosts privacy policy
|
||||||
|
|
||||||
## Definitions
|
## Definitions
|
||||||
|
|
||||||
|
@ -37,7 +50,7 @@ In this specification listed 3rd party APIs that Status functionality rely on.
|
||||||
## Why 3rd party API can be a problem?
|
## Why 3rd party API can be a problem?
|
||||||
Relying on 3rd party APIs interferes with `censorship resistance` Status principle. Since we aim to avoid suppression of information it is important to reduce amount of 3rd parties crucial for app functionality.
|
Relying on 3rd party APIs interferes with `censorship resistance` Status principle. Since we aim to avoid suppression of information it is important to reduce amount of 3rd parties crucial for app functionality.
|
||||||
|
|
||||||
## 3rd party APIs used by Status
|
## 3rd party APIs used by current Status app
|
||||||
|
|
||||||
### Infura
|
### Infura
|
||||||
|
|
Loading…
Reference in New Issue