Sorry guy's we been busy We Should have a date for you Tomoz as to when the swap will actuallly Occur, Who will be involved etc.I'm about to build for the Rpi2. Anything I need to know? (By no means am I an expert) Do I need to use that qmake use_upnp=1 command to help with the master node, or will that not make a difference?
Also, in some of the other wallets that were built, once I launch them the wallet is bigger than the screen. Anyone know how to fix that prior to build?
Thanks!
I Cannot see you building without the UPNP option causing issue's (However saying that i have never personally tried to see what happens when you use UPNP or Not other than it helping with Routers which most tend to have UPNP turned on automatically. But saying that everytime i build a Qt wallet UPNP is always used.
If you would just like shall we say the peace of mind then include it. Does that help.
We can certainly look into how big it's displayed when you first open But once you wish to use the tabs you will have to make it bigger unless we make everything smaller (which may cause issue's with others).
there isnt any issue compiling and running it without upnp active ( or compiled in the build ) with the old build - or any of the builds i have running on most other coins and the older code of drz ...
the reason is that upnp only really helps to automatically gain an ip address ( dynamically ) ... especially since masternodes require a permanent ip address to run - the best way to get this sorted is open a port on the router - or use a vps with a permanent ip ...
even though i have not successfully compiled the latest code - the upnp option is still exactly the same ... you can compile and run without it - as long as you have the tcp / udp ports open ion the router ( in home systems using a solid internet link ) ...
i compile ALL my wallets / daemon without upnp support - and as long as you have access to the ports - you should run into no issues ... i have all my vps system daemons that i support ( grn - drz - mtr - bst - bnt - and soon egc ) without upnp support and statically compiled daemons on centos 7 x64 vps system ...
the new drz3 code is still giving me issues - though this time its about static boost libraries - which fedora 23 x64 supports but refuses to compile ...
this weekend i will try and compile a static daemon on the vps to see if it works - and if so - will incorporate them as the new nodes ...
the droidz.conf file is the important part here to get right though ... especially as masternodes ...
back in a couple of days
...
#crysx