Difference between revisions of "Road Map"
(→Java FX Client) |
(→Snowblossom Channels) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 24: | Line 24: | ||
===Snowblossom Channels=== | ===Snowblossom Channels=== | ||
| + | |||
| + | [[Channels]] | ||
| + | |||
| + | [https://docs.google.com/document/d/1ze52_MIn7xfhwlsTij-DbLUMnz4ufOdS2Quh43zavgc/edit?usp=sharing Snow Channels Basics] | ||
[https://docs.google.com/document/d/18H70nQZVXh5Mw96dj5sUswICj6VKqwtrMjHTatB6ESs/edit?usp=sharing Snowblossom Channels] | [https://docs.google.com/document/d/18H70nQZVXh5Mw96dj5sUswICj6VKqwtrMjHTatB6ESs/edit?usp=sharing Snowblossom Channels] | ||
Latest revision as of 04:35, 11 September 2019
Contents
Road Map
We don't have a road map. We have some ideas.
Light Client Servers
Just discussing some ways which we can decide which nodes a light client will use
https://docs.google.com/document/d/12ZEZAsEJDm0ILyfiScVPXIzmYq7dEJvpnd7jJRuv_DI/edit?usp=sharing
Java FX Client
This should allow us to:
- Use existing java client code
- Target a number of platforms
- Windows
- Android (in addition to current android client)
- Maybe others?
- Run node and maybe other services under a UI
This is pretty much done. Didn't end up using JavaFX because it is a runtime disaster. IceLeaf
Snowblossom Channels
A distributed way to share content
Snow Payment and Auth
A simple payments (and auth) framework designed for microtransaction for web sites premium or ad-free content
Distributed Privacy Mixer
A protocol that allows users to mix their coins for privacy. Two modes:
- Passive mode - set required fee and parameters and acts as a mixer for other users
- Active mode - allows a user to create a mixed transaction, reaching out to passive mixers to get desired amount of noise.
