I LOVE NEM but - I am very upset that a beautiful thing has been essentially ruined by not having an intuituive set-up in the nano-wallet due to one little tiny thing. So … lets get into harvesting.
- I got 11,000 vested NEM, I Change node to LOCALHOST while running a standalone NIS just for fun.
Now at this point it would be INTUITIVE to just “start local harvesting” BUT the nano wallet has no “start local harvesting” button.
INSTEAD you have to go to “services” and get into the whole delegated harvesting mess.
Why is that a mess? Because for starters the “remote account” address suggested in the importance transfer is some
WEIRD default account that nobody knows what it goes to or where or who - some default super node I guess?
But dam, it should not be like that without EXPLAINING. So, what can you do? I decided maybe it would be intuitive to put my OWN Wallet’s account address into that “remote account” by selecting my own public key (which you can do by checking custom key) - and then using the wallet’s public key. That would be INTUITIVE for local harvesting. But NO! I know that is not right - becasue there is NO literature suggesting to do that! Just that it would be intuitive to do that if you wanted LOCAL harvesting!
And guess what? You cant select localhost there either. All you CAN do is accept the default address the wallet gives you as “remote account” and click ‘send my 6xem’ having NO clue what remote account the NEM team has selected for me. Doesn’t seem too decentralized … Seems more like my “up link” in my network marketing campaign or star architecture to one of 700 super nodes. So then what? Well you wait the 6 hours, you get activated, and then I GUESS you can actually worry about HOW to CHANGE your delegation to localhost - but guess what? It aint in the “remote account”: section. You know where it is? You’ll find it in a NEW field that just appears under the start/stop harvesting" section. OR maybe you can make the “remote delegated public key” to lcoahost. Hmmm? Where is it?!? or SOME other field that will miraculously appear to be cahnged to “localhost” at that time.
But wait a minute! Who the heck did I transfer my importance to in the first place? I mean dam, I have had to activate and deactivate to some unknown node like 4 times just to test the thing. SOOO non-intuitive. You should not have some random remote account in the remote account field. It should be BLANK and it should appear and CHANGE depending on what you put in - in other words (if you want to be intuitive that is) ONLY a forced input of some custom public key - not some weird random remote account that does not change when you change your “node” to some other supernode either. Which you would think it would change becasue intuitively that random remote account corresponds to the supernode you are connected to - I mean that might make sense - otherwise whose is it? Still, if I connect to localhost or alice 7 or whatever that dam default remote account stays the same - so WHOSE is it? And why is it arbitrary - I know ti isw arbitrary becasue switching to localhost AFTER activation (i.e. via start/stop harvesting) does NOT change the “:remote account” So what is that dam remote account then - jsut some fictitious default to send 6 xem to??? wow!
FURTHER: It is NOT intuitive as to why a localhosting of a NIS does not get MORE incentive to harvest then just letting some supernode do the work for me via delegation - (again I assume the dreaded default “remote account” is just some random supernode that is pegged to my wallet. What else prey tell can it be?) I assume any new running NIS helps NEM as a whole no? Wher eis my incentive to do that if I jsut farm out my harvesting to the “default” remote account in the nano-wallet? Wherever that is …