This is first public release of NuBox binaries. So far it covers only nu binaries, packaged for Debian. Packages are deployed with systemd services and are ready to be integrated with future NuBox.
What I need now from testers is to verify that binaries are stable and play well with legacy wallet.dat files. Binaries are built against libdb4.8, which means wallet.dat from official binaries should work out of the box.
Packages for both armhf (raspberry pi) and x86_64 are provided.
To install repository, copy/paste following commands in the terminal:
-h, --help show this help message and exit
-version print NuBox version.
-unit [UNIT] switch between NuShareas and NuBits
-info equal to “nud getinfo” with some extras
-balance print balance
-public show info with omitted private data
-stdout dump data to stdout, use to pipe to some other program
-rates current average NuShares exchange rates in USD and BTC
-start start NuBox
-stop stop NuBox
make NuBox autostart at boot time
-tor start NuBox with Tor
-onion show .onion address if this node has one
-restart restart NuBox
-mint unlock wallet for minting.
-addr shows all associated addresses.
-send [SEND [SEND …]]
send NuShares/NuBits; -send ADDRESS AMMOUNT
-gauth [GAUTH] enable or disable google-authenticator, use with 'set’
-nbt switch to NuBits
-motions show active motions
-parkrates show parking rates
-liquidity show current liquidity
-vote [VOTE] set vote for motion or grant proposal
-feed set data feed
I really want to, but just too busy with the ALPv2 project, NuDroid, Pybot and datafeeds.
Instead I will offer 5 NBT each to the first 3 people posting in this thread, providing a NBT address and showing that they actually installed NuBox (screenshot) and provide some kind of feedback about its usage.
I tried the “nubox -public” since it looked nice from you, but it gave me a traceback, because no nu.conf available.
"touch"ed that .conf-file and now above command gave me a better msg: NuBox isn’t running
Then I started NuBox via “nubox -start”, but there is not much feedback. It just stays like that.
I tried other commands (e.g. nubox -addr) in another terminal, but they tell me NuBox is not running, though I started it.
Is there some kind of log file (besides the debug.log) I can look at?
Could it be b/c I haven’t yet downloaded the whole NU blockchain? if so, would be great to display such an info to the user also when I type: "nubox -start"
I’ll be downloading the blockchain now via the UI: nu, since I see there progress.
Then close the UI and try the “nubox -start” again
during NuBox install, for one of my choices I got:
“Poor misguided one. Why are you installing this, then ?”
did you read the choice for which you got this? it is for the name of the box on the network, if you want to call it nubox type yes, you typed no, maybe there should be some smiley faces added, and some “ha ha ha” to make it more clear, or change the words so it reads more yoda like?