Since a new user will not know what a "Basilisk is", there are 2 options I may suggest:
Keep calling it basilisk, and have some way to explain what basilisk is: "A lite node which does not download anything". Perhaps a question mark which highlighted pops up an explanation.
Call it something else in GUI, like "Full node" and "Lite node", this would be more self explanatory and could still include an explanation for both for new users to cover all bases. Basilisk can still be called basilisk in the code, but in Gui it would just be a string change calling it "Lite".
I'm not sure which is the best option, since once people know what "Basilisk" is, they will know after reading the explanation and give iguana some 'cool flavour', for having unique names, but "Lite node" would be simpler and more intuitive initially.
It depends what the design / UX approach for iguana / supernet is I think.
Since a new user will not know what a "Basilisk is", there are 2 options I may suggest:
I'm not sure which is the best option, since once people know what "Basilisk" is, they will know after reading the explanation and give iguana some 'cool flavour', for having unique names, but "Lite node" would be simpler and more intuitive initially.
It depends what the design / UX approach for iguana / supernet is I think.