You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion, to implement light, power-save mobile app, we need to think about cloud based twister wallet service.
The first way is the free to use, shared online wallet, like it implemented in the most crypt-coins projects. Main concept is using one cluster to run many twister daemons for each user/wallet on the same time. Using mobile app, through API, device connects to the server and initiate new daemon process. It's nice to pass PK through AES/PGP methods.
Alternatively, I think about twister hosting platform, where each user for a some cost can order his own virtual machine with pre-configured twister daemon, dedicated resources (for generating blocks ability) and remote web interface + mobile API. Every account will have dedicated IP. This way should be isolated from server administration to keep PK privacy. This way is more expensive and I doubt.
Also, it nice to write some python (or another server side language) command-line installation manager (e.g. openvpn-install), that helps to download, configure the remote node, and setup firewalls using any host by user choice.
In my opinion, to implement light, power-save mobile app, we need to think about cloud based twister wallet service.
The first way is the free to use, shared online wallet, like it implemented in the most crypt-coins projects. Main concept is using one cluster to run many twister daemons for each user/wallet on the same time. Using mobile app, through API, device connects to the server and initiate new daemon process. It's nice to pass PK through AES/PGP methods.
Alternatively, I think about twister hosting platform, where each user for a some cost can order his own virtual machine with pre-configured twister daemon, dedicated resources (for generating blocks ability) and remote web interface + mobile API. Every account will have dedicated IP. This way should be isolated from server administration to keep PK privacy. This way is more expensive and I doubt.
Also, it nice to write some python (or another server side language) command-line installation manager (e.g. openvpn-install), that helps to download, configure the remote node, and setup firewalls using any host by user choice.
Algorithm drafts: Remote Twister Node setup (Ubuntu Debian)
Related issue: Command-line installation manager
Pretty raw thoughts I will explain the subject later.
The text was updated successfully, but these errors were encountered: