I'm sure theres guides on there on it already
I've found a few pertaining to DASH but reading em and comprehending em are two totally diff things, plus most of what I have found is based on linux installations. I mean there's talk of conf file remote and conf file local but not much beyond that like ok, once conf files are done, here's how to get your windows mn to talk to your windows wallet. Not to mention I havent as of yet found info on other than conf files, telling the mn which wallet address it needs to manipulate on the local machine. |
|
|
|
Sure, use Create instead of Create Local, but that's a process I won't be doing a walkthrough for now or be helping with
What if I was willing to pay for the time ? Provided we could agree on an acceptable fee ? Edit: Both bands and the "main" wallet would be on one machine with unique ports like they are now. |
|
|
|
|
To keep coins in one wallet, could "unlocked" bands be set up where no funds are help which RPC in to the locked wallet for fund manipulation ?
I've been trying to read up a lil on masternodes and it seems dash can do something like this as it mentions local and remote conf files or I'm just completely mis reading shit.
Ideally to easy track transactions accross multiple bands it would be nice to view it all from one wallet.
|
|
|
|
|
@IGS, the last seem time is a personal pet peeve, anyway to make the Last Seen time local to the machine the clients on ?
|
|
|
|
Screw it, why not... really want to be able to do this and it has to be possible in some respect since IGS brought it up but can't seem to clarify in the way he originally meant. Snippet: You can auto-launch with walletpassphrase BOUNTY TIME !!! 50 bucks to the FIRST correct solution to the linked post in this thread ! https://bitcointalk.org/index.php?topic=1059159.msg11765543#msg11765543You have to put the RPC config in your conf file: rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=3333
Then you make your call using curl like this: curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": [" <yourwalletpassword>", 99999, true] }' -H 'content-type: text/plain;' http:// <rpcuser>: <rpcpassword>@127.0.0.1:3333  Please send them to this stealth address: cYBjoey3EfezH2qJDekP4QHiB6zhEykt2BifBVcGgET3GPDbRFsSsxjNg9XXaR2ywzfnnQwvbqkJoRZ pjiHCLYe7UCTot36TMTB1jb Gracias Edit: And double Gracias because I learned something new today Edit2: ["<yourwalletpassword>", 99999, true] 99999 : timeout true : for staking only Probably shoulda mentioned this is on a windows machine but I can't get this to work even using a batch file. Might just have to give up on this little endeavor. |
|
|
|
|
Did that, waiting to see what happens but will suck if I have to keep monitoring it all the time like this lol
|
|
|
|
So I have two bands that have been connected for ~7hrs... 24.154.55.93:11839/11840 but only one seems to be getting paid. Anyone else have ne thin similar ? Edit: Just got another payment to band 2...    |
|
|
|
Screw it, why not... really want to be able to do this and it has to be possible in some respect since IGS brought it up but can't seem to clarify in the way he originally meant. Snippet: You can auto-launch with walletpassphrase BOUNTY TIME !!! 50 bucks to the FIRST correct solution to the linked post in this thread ! https://bitcointalk.org/index.php?topic=1059159.msg11765543#msg11765543You have to put the RPC config in your conf file: rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=3333
Then you make your call using curl like this: curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": [" <yourwalletpassword>", 99999, true] }' -H 'content-type: text/plain;' http:// <rpcuser>: <rpcpassword>@127.0.0.1:3333 Please send them to this stealth address: cYBjoey3EfezH2qJDekP4QHiB6zhEykt2BifBVcGgET3GPDbRFsSsxjNg9XXaR2ywzfnnQwvbqkJoRZ pjiHCLYe7UCTot36TMTB1jb Gracias Edit: And double Gracias because I learned something new today Edit2: ["<yourwalletpassword>", 99999, true] 99999 : timeout true : for staking only I'll give this a shot and get back to you by tomorrow at the latest. Also, does anyone else find they need to "unlock for staking only to keep the bands running ? Had one band unlocked the other locked and the locked one strangely enough seemed to be the bread winner. So not sure what all still does or doesn't need to be done to get the most out of my bands. IGS said he doesnt use confs but I don't believe has started his type of setup like r his wallet excrypted, has he tried a system reboot or two with wallet launch on startup etc. Ty. |
|
|
|
Screw it, why not... really want to be able to do this and it has to be possible in some respect since IGS brought it up but can't seem to clarify in the way he originally meant. Snippet: You can auto-launch with walletpassphrase BOUNTY TIME !!! 50 bucks to the FIRST correct solution to the linked post in this thread ! https://bitcointalk.org/index.php?topic=1059159.msg11765543#msg11765543 |
|
|
|
I don't use flags like that so I don't know the format, but it's walletpassphrase
Ehh, I was tlaking about the connections thing that youd love, 18 now but again I'm only running the wallet right now, not ne of my bands. But the pass thing, you did say I can auto-launch with walletpassphrase so you have to know how to do it in one form or another so thats what I was trying to ask about, Ty. |
|
|
|
Wallets been up a few mins and only seeing 4 cons which is what I've been averaging all though it's never the same between the main client and two bands.
Edit: Just hit 8, only got the main non band wallet running right now.
Edit 2: Ehh, bouncing 6-8 but seems better, for the one client running ne way.
If you get capped at 8, the issue is local See same reply for edits since quote LMAO,,, ull love it. |
|
|
|
Wallets been up a few mins and only seeing 4 cons which is what I've been averaging all though it's never the same between the main client and two bands. Edit: Just hit 8, only got the main non band wallet running right now. Edit 2: Ehh, bouncing 6-8 but seems better, for the one client running ne way. Edit 3: LOL, fuckin 13 cons now, curious to see if the new numbers hold before I go launching bands a n b. Now that the con issue seems solved.. can we PLEASE address my elephant in the room lol... https://bitcointalk.org/index.php?topic=1059159.msg11765543#msg11765543 |
|
|
|
Hey IGS, I know your still busy with the whole connection thing but I just wana try and revisit this really quick if you don't mind, Ty. Ok, thanks
You can auto-launch with walletpassphrase if your end-game is trying to automate it, which is what it seems like to me
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. I figured out that walletpassphrase <secret> 99999 true is what needs to be used but not sure where it goes / how it needs to be set up to be passed on wallet load. Still running in to issue with bands and did some reading on the vin message me n others have gotten and want to try a few tricks but this "the above" plays heavily in to my testing. |
|
|
|
@Spots
You have one less guy to worry about.
Some of your changes must have worked because my wallets now have 11 and 5 nodes each respectively, without restart. One running on port 36482 and the other one in 36480. I'm synced and staking in both.
I have been working on this nonstop. About 231138172 fixes have been going in and out. It's almost 4 AM again now and I'm about to punch my fucking screen soon I know exactly what the problem is, but I'm trying to fix it without requiring a hard fork this early because I promised no more updates Grant it I can't help for shit but if you know exactly what the issue is might it help if it's discussed publicly for the extra "eyes" ? Edit: Even if it came to a hard fork, given the issue I think it'd be one everyone would accept if it guaranteed resolution to some respect. |
|
|
|
I'm not concerned about bands right now, sorry, getting connection bullshit sorted and it's pissing me off
**Walks away quietly as he's very clearly hit a big ass nerve** |
|
|
|
I'm connected with 1 node. It there a list of know nodes for conf-file?
addnode is hit or miss with a lot of people, at one point I added like 10 and still only hovered around 2 connections. @IGS: I know I said above if you answered the one question it'd be my last but given issues people are having with bands, I did want to try something else. If I wanted to sway away from the one click band setup and go for something I can control a bit more, I could otherwise set up a band using the suggested config info shown with the one click bands right ? Ex. staking=0 server=1 listen=1 port=11838 masternode=1 masternodeaddr=24.154.55.93:11838 masternodeprivkey=<address> |
|
|
|
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 just got reward from masternode with locked wallet, so... Ehh, who knows have you stopped your client for a period of 10 mins or more, restarted it and done NOTHING ELSE to see if your band starts up and shows in the band list ? I just closed it, restarted it. Did't unlocked it, my band was there in band network and after few minuted I got reward with locked wallet Hows it started and what's in your conf file, if you have one. All I know is when I restart a client, it needs to be unlocked for staking only. Edit: Your reward that showed up could have also been delayed in the chain which meant it was coming anyway... Edit 2: See, like I deleted a band 5 minutes ago, closed client restarted it and just had 2 bucks show up. |
|
|
|
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 just got reward from masternode with locked wallet, so... Ehh, who knows have you stopped your client for a period of 10 mins or more, restarted it and done NOTHING ELSE to see if your band starts up and shows in the band list ? |
|
|
|
There's a guide on GorillaStake.com/gorillabands.htmlSetting up multiple GorillaBands on one machine is easy and takes only a few extra minutes. Please follow the guide below to complete setup in moments
First, navigate to Roaming and find the GorillaBucks folder. This is the folder and path you will want to remember for the second step. Copy this entire folder (except wallet.dat) and rename to Roaming/GorillaBucksMasternode1
Next, edit the batch file that was included in your wallet download and replace 'masternodedirectory' with the file location copied from above, (example: ../Roaming/GorillaBucksMasternode1). If this is the only additional GorillaBand you plan on setting up, then you can close the .bat edit window now and launch the client using this file. If you plan on setting up a third, fourth.. GorillaBand on the same machine, continue on with the simple step by step instructions below
By now you have your first GorillaBand set up, so this will be easy! Simply copy the batch file (GorillaBand.bat) and change the datadir and ports to unique and unused folders and ports. Each instance of the wallet will need a new folder and port assigned to it. Simply copy the batch file and change a few flags to set up multiple GorillaBands on one machine, saving on rentals and maintenance I brain farted and figured it out. But if you could PLEASE answer one final thing for me I've sorta been harping on, I can promise you wont hear another peep from me in the support area. Seeing as how the only thing after this question is the connection thing your actively working on. But ya, if you could please do me this one SOLID I would reallllllllly appreciate it m8. Ok, thanks
You can auto-launch with walletpassphrase if your end-game is trying to automate it, which is what it seems like to me
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. I figured out that walletpassphrase <secret> 99999 true is what needs to be used but not sure where it goes / how it needs to be set up to be passed on wallet load. Still running in to issue with bands and did some reading on the vin message me n others have gotten and want to try a few tricks but this "the above" plays heavily in to my testing. |
|
|
|
|
Show Posts
