mirror of
https://github.com/status-im/specs.git
synced 2025-01-30 16:15:31 +00:00
Merge pull request #88 from status-im/spec-stable/whisper-mailserver
Move Whisper Mailserver Usage to stable
This commit is contained in:
commit
e46d19be26
@ -19,6 +19,10 @@ The following SIPs are stable and running in production.
|
|||||||
|
|
||||||
- [Status Secure Transport Specification](status-secure-transport-spec.md). How Status provide a secure transport with conversational security properties.
|
- [Status Secure Transport Specification](status-secure-transport-spec.md). How Status provide a secure transport with conversational security properties.
|
||||||
|
|
||||||
|
- [Status Whisper Mailserver Specification](status-whisper-mailserver-spec.md). How we use Whisper mailservers to provide offline inboxing.
|
||||||
|
|
||||||
|
- [Status EIPs Standards](status-EIPs.md). Ethereum Improvement Proposals used in Status.
|
||||||
|
|
||||||
### Draft
|
### Draft
|
||||||
|
|
||||||
The following SIPs are under consideration for standardization.
|
The following SIPs are under consideration for standardization.
|
||||||
@ -27,7 +31,6 @@ The following SIPs are under consideration for standardization.
|
|||||||
- [Status Payload Specification](status-payloads-spec.md). What the message payloads look like.
|
- [Status Payload Specification](status-payloads-spec.md). What the message payloads look like.
|
||||||
- [Status Account Specification](status-account-spec.md). What a Status account is and how trust is established.
|
- [Status Account Specification](status-account-spec.md). What a Status account is and how trust is established.
|
||||||
- [Status Whisper Usage Specification](status-whisper-usage-spec.md). How we use Whisper to do routing, metadata protection and provide 1:1/group/public chat.
|
- [Status Whisper Usage Specification](status-whisper-usage-spec.md). How we use Whisper to do routing, metadata protection and provide 1:1/group/public chat.
|
||||||
- [Status Whisper Mailserver Specification](status-whisper-mailserver-spec.md). How we use Whisper mailservers to provide offline inboxing.
|
|
||||||
|
|
||||||
### Raw
|
### Raw
|
||||||
|
|
||||||
|
@ -1,5 +1,7 @@
|
|||||||
# Status Whisper Mailserver Specification
|
# Status Whisper Mailserver Specification
|
||||||
> Version: 0.1 (Draft)
|
> Version: 0.2
|
||||||
|
>
|
||||||
|
> Status: Stable
|
||||||
>
|
>
|
||||||
> Authors: Adam Babik <adam@status.im>, Oskar Thorén <oskar@status.im> (alphabetical order)
|
> Authors: Adam Babik <adam@status.im>, Oskar Thorén <oskar@status.im> (alphabetical order)
|
||||||
|
|
||||||
@ -85,7 +87,7 @@ In order to be useful, a mailserver SHOULD be online most of time. That means
|
|||||||
you either have to be a bit tech-savvy to run your own node, or rely on someone
|
you either have to be a bit tech-savvy to run your own node, or rely on someone
|
||||||
else to run it for you.
|
else to run it for you.
|
||||||
|
|
||||||
Currently Status Gmbh provides mailservers in an altruistic manner, but this is
|
Currently one of Status's legal entities provides mailservers in an altruistic manner, but this is
|
||||||
suboptimal from a decentralization, continuance and risk point of view. Coming
|
suboptimal from a decentralization, continuance and risk point of view. Coming
|
||||||
up with a better system for this is ongoing research.
|
up with a better system for this is ongoing research.
|
||||||
|
|
||||||
@ -96,8 +98,9 @@ A Status client SHOULD allow the mailserver selection to be customizable.
|
|||||||
In order to use a Mailserver, a given node needs to connect to it directly,
|
In order to use a Mailserver, a given node needs to connect to it directly,
|
||||||
i.e. add the Mailserver as its peer and mark it as trusted. This means that the
|
i.e. add the Mailserver as its peer and mark it as trusted. This means that the
|
||||||
Mailserver is able to send direct p2p messages to the node instead of
|
Mailserver is able to send direct p2p messages to the node instead of
|
||||||
broadcasting them. Effectively, it knows which topics the node is interested in,
|
broadcasting them. Effectively, it will have access to the bloom filter of
|
||||||
when it is online as well as many metadata like IP address.
|
topics that the user is interested in, when it is online as well as many
|
||||||
|
metadata like IP address.
|
||||||
|
|
||||||
### Denial-of-service
|
### Denial-of-service
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user