The road to V1 specs and more

[corpetty]

Alright, this issue is a to track and describe what needs to be done to get to the start of V1 specs. For V1, I'm ok with the first non-draft version having overlap with specs that live in vacp2p specs. As things finalize there, we can remove them here and appropriately reference them here with our design decisions around that reference.

I'd also like to store various higher-level views of the Status App here which give insight to how our implementation of Status uses the specs within here. I'm open to how we document and store that, but initial attempts to do so can be found here:

• Message Encapsulation Structure
• Front-end / Back-end Comms flow
• Message lifecycle

Checklist of getting the bare minimums for V1:

• [x] Draft Status Client Spec -> SIP 1
  • WIP PR here https://github.com/status-im/specs/pull/76
• [x] Draft Secure Transport Spec -> SIP x
• [ ] Draft Payload Spec -> SIP x
  • [x] resolve https://github.com/status-im/specs/issues/62
  • [ ] resolve https://github.com/status-im/specs/issues/57 PR open
• [ ] Draft Account spec -> SIP x
• [x] Draft Whisper Usage Spec -> SIP x
  • [x] resolve https://github.com/status-im/specs/issues/59
  • [x] resolve https://github.com/status-im/specs/issues/58
• [ ] Draft Whipser Mailserver spec -> SIP x
  • [x] resolve https://github.com/status-im/specs/issues/55

Note that this does not HAVE to be done before V1 launch, but with the extra time between finishing required issues and launch date, it should give some time on documenting how V1 works.

Hit me with updates, changes, and thoughts.

[oskarth]

@corpetty can we update the state of this?

[oskarth]

Taking this over. See open PRs here https://github.com/status-im/specs/pulls

[oskarth]

Bare minimum done!