Skip to main content

EIPS

Abstract​

This specification describes how Status relates with EIPs.

Introduction​

Status should follow all standards as possible. Whenever the Status app needs a feature, it should be first checked if there is a standard for that, if not, Status should propose a standard.

Support table​

Status v0Status v1OtherState
BIP32NYNstable
BIP39YYYstable
BIP43NYNstable
BIP44NYNstable
EIP20YYYstable
EIP55YYYstable
EIP67PPNstable
EIP137PPNstable
EIP155YYYstable
EIP165PNNstable
EIP181PNNstable
EIP191Y?NYstable
EIP627YYNstable
EIP681YNYstable
EIP712PPYstable
EIP721PPYstable
EIP831NYNstable
EIP945YYNstable
EIP1102YYYstable
EIP1193YYYstable
EIP1577YPNstable
EIP1581NYNstable
EIP1459NNraw

Components​

BIP32 - Hierarchical Deterministic Wallets​

Support: Dependency.
Reference Description: Enable wallets to derive multiple private keys from the same seed.
Used for: Dependency of BIP39 and BIP43.

BIP39 - Mnemonic code for generating deterministic keys​

Support: Dependency.
Reference Description: Enable wallet to create private key based on a safe seed phrase. Used for: Security and user experience.

BIP43 - Purpose Field for Deterministic Wallets​

Support: Dependency.
Reference Description: Enable wallet to create private keys branched for a specific purpose. Used for: Dependency of BIP44, uses "ethereum" coin.

BIP44 - Multi-Account Hierarchy for Deterministic Wallets​

Support: Dependency. Reference Description: Enable wallet to derive multiple accounts in top of BIP39.
Used for: Privacy.
Source code Observation: BIP44 don't solve privacy issues regarding the transparency of transactions, therefore directly connected addresses through a transactions can be identifiable by a "network reconnaissance attack" over transaction history, this attack together with leakage of information from centralized services, such as exchanges, would be fatal against the whole privacy of users, regardless of BIP44.

EIP20 - Fungible Token​

Support: Full.
Reference Description: Enable wallets to use tokens based on smart contracts compliant with this standard.
Used for: Wallet feature.
Sourcecode

EIP55 - Mixed-case checksum address encoding​

Support: Full.
Reference Description: Checksum standard that uses lowercase and uppercase inside address hex value.
Used for: Sanity check of forms using ethereum address.
Related Also Sourcecode

EIP67 - Standard URI scheme with metadata, value and byte code​

Support: Partial.
Reference Description: A standard way of creating Ethereum URIs for various use-cases.
Used for: Legacy support.
Issue

EIP137 - Ethereum Domain Name Service - Specification​

Support: Partial.
Reference Description: Enable wallets to lookup ENS names.
Used for: User experience, as a wallet and identity feature, usernames.
Sourcecode

EIP155 - Simple replay attack protection​

Support: Full.
Reference Description: Defined chainId parameter in the singed ethereum transaction payload.
Used for: Signing transactions, crucial to safety of users against replay attacks.
Sourcecode

EIP165 - Standard Interface Detection​

Support: Dependency/Partial.
Reference Description: Standard interface for contract to answer if it supports other interfaces.
Used for: Dependency of ENS and EIP721.
Sourcecode

EIP181 - ENS support for reverse resolution of Ethereum addresses​

Support: Partial.
Reference Description: Enable wallets to render reverse resolution of Ethereum addresses.
Used for: Wallet feature.
Sourcecode

EIP191 - Signed Message​

Support: Full.
Reference Description: Contract signature standard, adds an obligatory padding to signed message to differentiate from Ethereum Transaction messages.
Used for: Dapp support, security, dependency of ERC712.

EIP627 - Whisper Specification​

Support: Full.
Reference Description: format of Whisper messages within the ÐΞVp2p Wire Protocol.
Used for: Chat protocol.

EIP681 - URL Format for Transaction Requests​

Support: Partial.
Reference Description: A link that pop up a transaction in the wallet.
Used for: Useful as QR code data for transaction requests, chat transaction requests and for dapp links to transaction requests.
Sourcecode Related: Issue #9183: URL Format for Transaction Requests (EIP681) is poorly supported Issue #9240 Issue #9238 Issue #7214 Issue #7325 Issue #8150

EIP712 - Typed Signed Message​

Support: Partial.
Reference Description: Standardize types for contract signature, allowing users to easily inspect whats being signed.
Used for: User experience, security.
Related: Isse #5461 Commit

EIP721 - Non Fungible Token​

Support: Partial.
Reference Description: Enable wallets to use tokens based on smart contracts compliant with this standard.
Used for: Wallet feature.
Related: Issue #8909 Sourcecode Sourcecode

EIP945 - Web 3 QR Code Scanning API​

Support: Full.
Reference Used for: Sharing contactcode, reading transaction requests.
Related: Issue #5870

EIP1102 - Opt-in account exposure​

Support: Full.
Reference Description: Allow users to opt-in the exposure of their ethereum address to dapps they browse.
Used for: Privacy, DApp support.
Related: Issue #7985

EIP1193 - Ethereum Provider JavaScript API​

Support: Full.
Reference Description: Allows dapps to recognize event changes on wallet.
Used for: DApp support.
Related: Issue #7246

EIP1577 - contenthash field for ENS​

Support: Partial.
Reference
Description: Allows users browse ENS domains using contenthash standard.
Used for: Browser, DApp support.
Related: Isse #6688 Sourcecode Sourcecode

EIP1581 - Non-wallet usage of keys derived from BIP-32 trees​

Support: Partial.
Reference Description: Allow wallet to derive keys that are less sensible (non wallet).
Used for: Security (don't reuse wallet key) and user experience (don't request keycard every login).
Related: Issue #9096 Issue #9096
Sourcecode

EIP1459 - Node Discovery via DNS​

Support: - Reference Description: Allows the storing and retrieving of nodes through merkle trees stored in TXT records of a domain. Used for: Finding Waku nodes. Related: - Sourcecode: -

Copyright and related rights waived via CC0.

References​