Open Evanfeenstra opened 1 year ago
@tomastiminskas @Evanfeenstra
I am thinking of adding a connection_string
to the invite body.
And connection_string
is what we give users to use in signing up.
I guess the logic will go this way when the invite status is ready
, we check if we have connection_string
, and if we have that allow user to copy the connection_string
, else if there is no connection string we allow users to copy invite_string
.
It makes sense to me. We can add the new connection_string
on the apps whenever we have some test environment ready and relay changes deployed to my nodes. It should be pretty simple.
Not sure if the initial process of sending a key send to swarm admin would be done from the app and if that will have a specific flow that we will need to implement or if that will be done outside of sphinx for now.
We will use the flow that already exists in the app, so no need for a new workflow...
Immediately an invite is sent, the status of the invite becomes pending_payment
@Evanfeenstra
Here are the two basic configs that need to be added to swarm
"allow_swarm_invite": true,
"host_name": "localhost:3004"
proxy users should be able to "buy" a new user (invite)
You need to send keysend to swarm admin... those sats are the initial sats that the new user gets. Also the admin could set a percentage "cut" (like they could take one percent).
And it would be great to hook this up to the same "invite" UX in the apps
This is an R+D issue for now