If I read the posts from the dev team right then this form is really only the start to get it functioning correctly and being inflicted on wave 1 people who for the most part are more technically minded or willing to learn. Yes there will be some who are not so minded in wave 1. And if I read the devs posts correctly then soon enough we will be getting more GUI style of interface well before launch
You kill them off and start over I guess.
But I would like the discord name displayed by the launcher to confirm the name was accepted and can be checked to see if its correct by the user.
But when restarting the launcher the nodes persist - so part of the settings stay - I’d have assumed the discord name too…?
Prob, I hope they have a way to reset completely. Considering this will end up being the GUI for node-manager I’d guess the reset functionality will be included @joshuef
Not wanting to criticise anything - I do understand why rust for nodes - but I could imagine a small python based dash app or nodejs app might be simpler and faster to develop (probably a couple of days for the right person) that just fires commands to the command line node manager than optimising this TUI and reworking it later …?
Thx @JPL forgot how to run the TUI would be nice if this was in the op.
Would be handy if you can copy the peerID from the terminal/launchpad
After getting one node to start with discord: eddde, I can’t [Ctrl+g] or [0]
Didn’t try [Ctrl+x] because I want to keep my node running
It’s more for advanced users comfortable with the CLI / Node manager.
The Launchpad first iterations are really being built with new entrants in mind who want to contribute to the beta and participate in the rewards comp.
Not catering to uploads, or file management for them at this stage.
Remember, the beta rewards is about building capacity and network resilience at this stage.
Okay… Then one needs the node manager in addition to it and it needs to be installed/updated correctly and stuff… I see other solutions have their challenges too… This just feels so limited and at the same time I feel so lost (at least with the current version)
Ps:
Oh well - just ignore me - you have a plan to launch an I’m perfectly okay with it! Just thought there might be faster or easier ways but your plan starts with rewards beta next month and full launch later this year - so perfectly fine and super fast
This hasn’t been clear. Can you make a post to clarify what and when for various CLIs and UIs. We now have quite a few and I hadn’t seen launchpad described and in my mind had lumped it in with the TUI.
This makes it hard to know what we’re trying to evaluate without the context and juxtaposition of the different ways to run nodes or use network services so I think a clarifying post would help. Something like UI name, aims/functionality, audience and what stage of the roadmap they relate to. So far we seem to have TUI, Launchpad, safenode-manager, safeup and safe CLI and I’m confused. Did I miss anything?!
Imagine how I feel
BUG?: I did export SAFE_PEERS=
before trying the faucet but it still said connecting with 1 peer and timed out. Is that a bug?
100% this is the way. Tokens for reward calcs are sent back to the foundation w/ encrypted id
in the metadata. You could in theory keep some $$ back if you wanted to upload, but right now default is to send it all on if you set an owner.
And accordingly I can see timbobjones
has earnt some $$ That’s the whole thing working right there.
You don’t have to put in an id if you just want to run nodes. If you want to have rewards tracked (and in the end be part of the program), then you’ll be needing a discord_id
.
You’ll be able to ask the foundation for your exact amount via DM or similar on discord. But yeh, you may well want to track what is sent out matches. (We’ll be aiming to do this too).
Could be. Also won’t be today though I imagine
metrics
endpoint could tell us (I think we might already track times paid eg…) Let’s see how things shake out.
Right now nothing. That hinges on there being a faucet though …
Don’t worry, we’ll be getting on such things soon enough. Looks like the underpinnings are working as expected which is a great place to be. If we get the home-network
success rate up, we’ll be able to iterate over such pains superfast.
@bzee has been working on an auto-nat detection bin, which will essentially advise the launchpad on the mode to start nodes in (and could be run standalone eg). It’s not there yet, but not far off either.
Aye it’ll be back. We’ll be iterating over a bunch of bits soon enough.
It’s all simpler and fast until it’s not Right now we can all get stuck into the TUI. As/when there’s a need for a GUI we’ll likely go
tauri
or similar, I’d wager. I really don’t want to get heaps of javascript involved though…
For me:
Non Technical users should care about:
- launchpad = general ui for starting nodes
Technical Users may care about
- tui = current iteration of ui, which is essentially the launchpad (but maybe later the launchpad grows beyond this; tui could get merged into node-manager as a “zero argument” mode eg.)
- node-manager = cli/lib for managing nodes, used both for local testnets, and starting/joining existing WAN testnets
- safeup = CLI for installing various safe/autonomi tooling (for advanced users…
- safe cli = cli for interacting with the network
- safenode = binary that starts and runs a node, joins the network and contributes resources
There are more layers, but that’s how the shake out atm.
edit: also updated the OP there for the ripgrep search to get things a bit more useful:
cc @neo @Southside as you’ve already been at it
rg -c 'Dcutr with remote peer: PeerId\(".*"\) is: Ok' ./ --search-zip | awk -F: '{sum += $2} END {print sum}'
rg -c 'Dcutr with remote peer: PeerId\(".*"\) is: (Ok|Err)' ./ --search-zip | awk -F: '{sum += $2} END {print sum}'
The Launchpad is the application… it has a Text/Terminal User Interface (TUI).
Edit: Josh me
Discord ID: happybeing (two nodes started).
BUG: Here’s what I see after starting and then setting my Discord username. It hasn’t cleared the screen before writing so what was on the screen before I started is showing through the gaps. I had this issue with vdash at one point:
I began by setting resources - I think that’s a necessary step but the UI doesn’t make this obvious so people may get stuck there, particularly as “Start nodes” is the first command on the line. I think the ordering should reflect what you expect us to do, and that the screen should tell you what that is or force you to set resources before presenting the TUI.
Setting resources: there was no guidance about what to allocate related to numbers of nodes. It told me I had 12GB available so I allocated 5GB and it started one node (on Ctrl-g). So I upped it to 10GB and Ctrl-g started a second node. I think it would help if the UI told me how many nodes it can run as I increase or decrease the number of GB.
Resources per node: I regularly run ten nodes on this machine so limiting me to two is odd.
Here’s the UI after starting two nodes:
And here they are in vdash using:
vdash -g "/home/<USER>/.local/share/safe/node/safenode*/logs/safenode.log"
All earnings regardless of setting a owner go the foundation it seems.
Can’t have a faucet, it will be gamed. I don’t think any of us regs will do that it would be just daft but there are folk who entered that couldn’t give a damn, they are just a stranger with a discord id.
Oh aye, that’s what I mean. There won’t be one (as @JimCollinson noted above)
I still want to test the port forwarding before launching the Node Launchpad, can you tell me what to forward?
Privacy. Security. Freedom
Made payment of NanoTokens(5598305) for 33970 chunksreward-test / 2a695ca / 2024-05-24
Made payment of NanoTokens(970879) for royalties fees
And, according to @joshuef’s list there is a separate thing being being called “tui”. So I’m still confused although now we have a list to clarify . I know what a TUI is though.