The specification for Moneysocket is work-in-progress.
The existing library implementations have been an exercise in figuring out the problem space and gathering experience and opinions on what we're building.
The exercise of writing the first draft of the spec is more an exercise in revisiting all the choices made along the way of building the libraries and existing apps. Some choices have been great, others less so.
The exact shape and size of this deliverable is TBD, however inspiration is taken by some of the other documents and processes in the Bitcoin space for BIPs, BOLTs, LNURL-XXXs, etc.
This is also an effort to bootstrap and sustain an open and transparent process for all stakeholders for the long term. If you have any thoughts, opinions, questions, please drop in our Telegram Group or file issues or whatever you feel comfortable with.
Some conceptual foundation of Moneysocket when it comes to intent and language-independent software architecture.
- Consumers and Providers
- Accounts
- Composibility
- Stack/layer/nexus model
- beacon/relay behavior
- transport layers (outgoing websocket, incoming websocket)
- Code API description
This borrows structure from Basis of Lightning Technology (BOLT) specification.
These articles will capture individual aspects of the techonology in implementable detail.
- BOM #0 - Introduction
- BOM #1 - Encoding format primitives (kinda like bolt1 & bolt 4)
- BOM #2 - Beacon encoding format (kinda like bolt11)
- BOM #3 - Provider Info data & Wad data
- BOM #4 - Request/notification message encodings
- BOM #5 - Transport layer and nexus behavior
- BOM #6 - Rendezvous layer and nexus behavior
- BOM #7 - Ephemeral Encryption Layer
- BOM #8 - Cryptographic Identity Layer
- BOM #9 - Consumer/Provider/Automatic role handshake layer
- BOM #10 - API layer
- BOM #11 - Error Messages
This is a space for BIP-like feature and extension proposals to be proposed, discussed, refined and implemented in standardized ways without necessarily getting includsion in the Basis of Moneysocket documentation.
- MIP #0001 - Avatar Image for Public Key
- TBD
- TBD
- Shortcomings - Known shortcomings of the pre-specification library implementations.
- Embedded Relay - Suggestion on how to implement a listening Moneysocket servers