Be interesting to see what those first five sell orders on c-cex to to the buck price. Would seriously hate to see the value low enough long enough where people buy coins and start bands for like $50 worth of BTC.

If that ever happened I don't see this coin lasting long as the market would at some point be flooded with minted band coins.

Also, how often are blocks found and what are the rewards for each block... here's what I tracked in 25 mins.

11:35pm 2,621 Buck Blocks - 12am 2,642 Buck Blocks

Ok, so I figured out what needs to be passed at launch, but how do I do it ?

walletpassphrase <pass> 99999 true

Also, not sure if you've pushed the update yet but I've restarted one client and am at 0 connections, was restarted ~2mins ago.

Also, for multiple clients... doesnt a unique port have to be set for each one in the conf file ?

Ex.

port=1234
port=5678

etc. etc. etc.

Or can they all use 36480 if port is not defined in a conf file ? I thought once a single instance used the port that it was locked in some respect.

Here's the thing though, I'm asking what I do (proper format, where does it get placed for proper execution etc.) lol

I've never messed with flags other than examples given, all I am guessing is it's something that will go in the conf file and beyond that I'm utterly clueless, the connection issue I can wait on but this is the last piece to my present time puzzle.

Ty for that but can you also address my query about the pass on launch and if it will be a stake pass or full unlock pass as a full unlock will endanger the wallet... Ty.

Can you assist me by explaining in detail what you mean ?

Ty.

I don't want to auto launch with the pasphrase if it wont be a "unlock for staking only" situation and not a auto launch which results in a fully unlocked / unsecure band.

Point of clarification lol, you mean the intial 1,000,000 premined supply that was used for the swap, right lol ?

Edit: Also, still only seeing 1-2 connection on all three clients ;-/

I know Vegas is a fudder but that image makes me itch... 67 connections ?

Also, in the next wallet version, is / would it be possible to code something for the band list where bands found that match the IP of the host location, in my case my house, are shown at the top so we don't have to filter the list by scrolling to see if were listed / running.

Hope that makes sense.

Ty.

Ya because I have the local machine on a weekly reboot.

But it makes sense it would need to be that way since earned BUCKS are staked until some confs come in.

But can you assist me with a demo of what you mean please ?

Ty.

Edit: I don't want to auto launch with the pasphrase if it wont be a "unlock for staking only" situation and not a auto launch which results in a fully unlocked / unsecure band.

THATS IT FUCKING EUREKA !!!

Wallets must be unlocked for "staking only" to allow bands to run / show... so basically each week after my system reboot I need to remember to do this less a workaround can be found. That aside, I can easily live with the connection issue this band not starting thing was what kept me awake last night !!!

So yes IGS, wallets need to be "unlocked" for staking only for bands to run after a wallet restart, unless your "anyone" is dumb enough to run an unencrypted band.

Edit: Soon as I unlocked for staking only was mere seconds before it popped up in the band list: 24.154.55.93:11838

I dont use the BAT file for ne of my bands. The Bands I use a short cut to the client with the target trick to name the folder which works file so I would have to just edit each conf file respectively but the conf files for my bands currently exist in a simple format...

rpcport=11839
port=11838

That being said... still running in to the issue where bands don't seem to start / show in the band list where all the bands are showed. Never did get an answer on that last night where I asked if bands will work with a fully locked wallet or have to be unlocked with "staking only" or fully unlocked to work which if fully unlocked doesnt make for a safe environment.

Right now I have band 24.154.55.93:11838 running locally and has been for ~20 minutes and is not showing up in the main band list... It does have 1 active connection so should be running fine like it was last night when I did a start from scratch deal.

Stopped all clients, one for staking and two bands. Started up just the staking one and am getting 0 connections.

Edit: With the VARY client I ALWAYS had 7-8 connections if not more.

Edit2: One active connection now on the staking client but that's it, took 15mins just to get that one.

I think I figured out the issue and this is just a hunch til I test it tomorrow / later today as I really do need ot get some sleep and have a carp appt in the am here in about 5hrs but...

Does the wallet need to be unlocked for the band to run because when I came home, I think I did reset the wallets and add in passwords and thats when I think I first recalled them not being listed.

I mean it makes sense if the band needs access to the funds for one reason or another and can't use em if the wallets locked.

That being said, if the wallet needs to be unlocked for the band to run doesnt that leave a big giant security hole ?

Anyway, both bands are up now but here's what I did not knowing at this point what if anything made a diff.

1> Re-enabled UPNP in the router.
2> Made sure all ports are forwarded correctly in the port forward / trigger area of the router.
3> Deleted existing <at the time> bands and made new ones per the instructions by clicking create local which named both band a and b's wallets as GorillaBand Node
4> Unlocked wallets and left unlocked, had to unlock to use the create local button.
5> Deleted both conf files for bands a n b and re did them to use nothing but port & rpcport calls.

But ya, as of right now, everyone should see my two bands as 24.154.55.93:11838/11840

But ya, @IGS... do wallets need to be unlocked for bands to run / work ? In any event, I will see if they're both still running by noon which is ~8hrs away and if so will proceed with a system (pc) where all wallets be it bucks, doge etc run at startup and see if the two bucks nodes come back online since the wallet will be locked and if not, proceed to unlock to see what happens if anything.

Previous reply where I answered some of your questions IGS can be found I think two replies above this as others have since replied since my last reply.

Edit: @IGS - Assuming wallets can be encrypted on bands, even though as you say they don't stake... to clarify an earlier comment... do they need to be unlocked for "staking only" to run / work right ? If so, I will need to either...

A: After the automated weekly PC reboot, remember to unlock for "staking only" both bands.

or

B: Leave wallets un-encrypted which may bite me in the ass in the grand scheme of things.

Dont need bat file for band a, dont use for band two as I use this in the target link of a shortcut which works: "C:\Users\Me\Desktop\GorillaBucks-qt.exe" -datadir="C:\Users\Me\AppData\Roaming\GorillaBucks2"

Also, do I even need the conf file with the whole one click setup thing ?

Also @ IGS...

Start results in this...


Start all results in this...


Stop all (as well as one other button) results in this...


Must be nice lol... so if conf file doesn't matter maybe it could be a router thing. I have ports forwarded to the right system, not sure on the upnp thing someone mentioned. On my router it's currently turned on, but I manually did the port forwarding from the port forward / trigger area of the router.

Edit: I've since turned off UPNP in the router and changed both config file to just the following since IGS suggests we / he dont need config files...

rpcport=11839
port=11838

rpcport=11841
port=11840

First and foremost, do I need the conf file as seen in my last reply at all with the whole one click set up ?

Screw it, I can't sleep because this is bugging the piss outa me since I seem to be sitting on 10k between two bands doing nothing.

I assume the one click config mentioned on the site is what otherwise eliminates the need for the conf file. That being said, if I removed the listed band from the band tab and opt for a conf file alone, will I (if I'm lucky) still have a running band ?

That being said, here's what one bands conf file looks like, it's all otherwise visible info from the band tab with the exception to the <removed> priv key which I assume is that of the 5k band address.


Edit: At this point I feel like selling out n dumping all 10k on c-cex but I told myself and promised IGS I was in it for the long haul and still am if this can be figured out.

Calling it a night but I refer you (IGS) to my last reply as it's been heavily modified since you may have last read it... Ty.

https://bitcointalk.org/index.php?topic=1059159.msg11751211#msg11751211

Edit: If anyone else with a band running that restarts after a system "computer" / wallet reset can help I'd very much appreciate it, Ty.

I feel the how ti set up a band / keep it running info was a little lacking right now... grant it this is new and there's bound to be bugs but theres apparently people with bands running just fine, especially the one guy whos got ~10 or so.

As much as it would be nice to have one, I'm actually getting tired of seeing you constantly pop up here. Do you really think you doing this over, n over, n over is going to get anything accomplished ?

If they give it they give it if they don't they don't. I'm out money too so it's not like I'm bein all stop whining even though I kinda am, I'm just saying you may as well be beating a dead horse with a stick.

At this point all any of us can do is wait for a refund or compensation that may or may never show up.

I assume the similar is the "low" connection count. But my biggie is my MN's not showing up in the list and not knowing if they're running. Last "payout" on both was around ~4 hrs ago and because of the queue, I don't know if I haven't hit my next turn yet or something wrong with them.

Also, when the main system "the computer" is reset and clients launched at startup, are MN's auto started or do I need to hit "start" on each one which kinda defeats the purpose of full automation which is what my end game is.

Edit: FWIW, when I do try to hit Start again I get the "dreaded" Error: could not allocate vin for collateralAddress

So ya, while I've been a firm supporter of past and current coin(s), if I have to keep trouble shooting two bands that may or may never stay running even after main system / wallet resets. I don't know if I'll really be able to continue with bucks in one form or another.

Also, there seems to be no form of "order" to the band list, should it run from rank 1 on down or something ? Seems to bounce all over the place.

Edit 2: When you click Get Config a window pops up with a tooltip reading: This pane shows an example GorillaBucks.conf template with the necessary masternode settings.

With this in the pane:


So could that be my issue right there with my two bands and if so, what do I do with the rpc stuff or can that (the three RPC calls) be commented out while filling out the rest ?

Edit: My referred to issue being I never had a conf file configured with any of the info above.

Edit: Also, when you hit various buttons, some pop up some darksend, coinbase message or something... at this point I'm calling a night and pray you find the time to help figure this out.

TTYL.

I know lol.

My swap was done but my email was asking if when you have a moment, if you could please check out: https://bitcointalk.org/index.php?topic=1059159.msg11750536#msg11750536

Thx.

Sorry if that was because of me lol

I know before you said you don't check PM's like you should hence the one email I sent that may as well be minor support related but it just linked to my last reply here since I have no clue wth is going on.

Ok, so I'm home, had time to look things over and don't know what's going on.

Here's my setup before I get to the "issue". I have three nodes running, two masters and a regular I use for staking and a lotto system I'm trying to get going. All on unique ports so no crossover issues.

The two masters should be showing up as follows: 24.154.55.93:11838/11840

Connections as of this post...

Master 1: 3
Master 2: 3
Regular: 1

So last night when I set them up they showed in the "master list" but now they're not showing "I check from my regular / lotto wallet" and haven't been since I don't know when. So ya, how do I know if my two MN's are even running ?

Last "payout" on each was around an ~hr ago so at that point I assume they were ok but I don't even know if they're running now.

Thoughts ?

Edit: Also, shouldnt I be seeing more connections, especially on the regular wallet ?

Or is that just due to the fact the coin was official as of last night ?

Edit 2: The two band wallets are locked not that I think that matters since the only option is to unlock for staking.

Edit 3: I did reset the two MN's when I got home though and they as of this edit still haven't shown in the MN list. Someone else said when he reset his client "closed n re-opened" that his MN(s) restarted, so do they or don't they when the clients are reset ?

I ask because I have a batch file that resets the system running all my various cryptos weekly and given the current BTC cost of a single MN, I'd hate to think that at any given time I have "dead" nodes with coin just sitting there doing nothing.