Service Closed, please use https://masternode.me as alternative
Last edited:
Pick testnet faucet here https://dashtalk.org/threads/testnet-tools-resources.1768/...
PS: Could S.O. send me some TDash i badly need them for testing purpose: y5BvozxAjmdwR3DPLJfVAFjWYH2PsjQ7Vt
Just to wrote you the stuff again (what we talked about in IRC):scratchy - Now if you can make it do "start-many" it will be dandy...
And thanks for taking me up on the Testnet idea!![]()
15:28:41

masternode start-many
15:28:41

{
"overall" : "Successfully started 0 masternodes, failed to start 0, total 0",
"detail" : {
}
}
Wonderful !Got "start-many" to work and 7 MNs up on testnet so far... More coming..![]()
Can't do anything right now because Testnet blockchain seems to be having issue atm... All my wallets are stuck .. :sad:Wonderful !
Your 'own' wallets or the one running on the cloud env?Can't do anything right now because Testnet blockchain seems to be having issue atm... All my wallets are stuck .. :sad:
Hey,scratchy - So far "start-many" masternodes keep going down after being started and running for a while. I have to keep restarting them. You might want to check from your end. Also, how many IPs on the system? because I've got a few IPs that were already issued to other masternodes. Each masternode can be on only one IP.
EDIT:Sorry, I meant each IP can have only one masternode as I understand it.
I'd sure like to know how you did this :what:Got "start-many" to work and 7 MNs up on testnet so far... More coming..![]()
Hi scratchy,Hey,
There are currently about 30 IPs on our system.
If theres a need for it ill add further more.
If a Masternode is not used any more it expires, and the IPs are recycled and used again later.
You can read more about expiring and hows it handled here: http://masternodecloud.com/#faq/destroyed
Ill check out about start-many ASAP and keep you updated~
I followed Reuben's guide from here: https://dashtalk.org/threads/reuben...rnodes-from-one-wallet-guide-start-many.4034/I'd sure like to know how you did this :what:
Yes, I followed that, it's very good. Thing is, he puts IP and privkey in masternode.conf (like normal), but blonkel says to paste those items in dash.conf; and then where to put tx_hash & index?I followed Reuben's guide from here: https://dashtalk.org/threads/reuben...rnodes-from-one-wallet-guide-start-many.4034/
It's not a perfect guide but it helped. I'll let you read it and figure it out first, and i'm sure you will..![]()
The instruction on masternodecloud is for one wallet. If you read Reuben's guide you'll see for start-many, you have to set it up a bit different. You need dash.conf and masternode.conf. Follow Reuben's guide, it's simple. Your masternode.conf looks something like this: (disregard the error screen):Yes, I followed that, it's very good. Thing is, he puts IP and privkey in masternode.conf (like normal), but blonkel says to paste those items in dash.conf; and then where to put tx_hash & index?
Sure would help if you could post your dash.conf and (if used) masternode.conf
Sorry moli, I missed that screenshot of yours in Reuben's thread. Yep, that's what my masternode.conf looked like.The instruction on masternodecloud is for one wallet. If you read Reuben's guide you'll see for start-many, you have to set it up a bit different. You need dash.conf and masternode.conf. Follow Reuben's guide, it's simple. Your masternode.conf looks something like this: (disregard the error screen):
https://dashtalk.org/threads/reuben...allet-guide-start-many.4034/page-3#post-59209
WOOHOOOO!!! THANKS, scratchyUpdate:
Leave Feedback
- Fixed a huge amount of backend bugs
- Autoupdate system for testnet/mainnet (Based on Github commits)
- Start-many should be solved now
- Prepared for txindex=1 (checkout latest git commits)
- Fast deploy based on chain-snapshots
![]()
Currently i will cap it on 30 IPs, give me some more time to stablize it / add other features i have in mind ~WOOHOOOO!!! THANKS, scratchy
We will report. Also, can we have more IPs pls? We want to test out about 100 MNs, maybe?![]()
The start-many nodes still keep dropping. I just restarted my 15 MNs.Updates !
- Stats on Main-Page
- Fixed some bugs in autoupdater
- Restarting VMs/Daemons in case of crash / failure
- Improved backend monitoring
- Collecting crash logs depending on git commits to help out the devs
Sadly i already noticed this.The start-many nodes still keep dropping. I just restarted my 15 MNs.
Ok i am. i hope you can get help from someone.Sadly i already noticed this.
Anyways it looks like the issue is not on my system. Its the daemon itself which is crashing.
Hopefully i get response asap from the devs to solve it. (Thats why i added "Collecting crash logs depending on git commits to help out the devs")
Please be patient it has the highest priority for me to solve it.
Great work man, glad you are here.I investigated, i guess the reason is that you using expired nodes on my cloud system. (Which doesnt exist anymore)
Start-many has currently a bug which leads to a successfull response even if theres no node running on the give IP.
Check this out: https://github.com/dashpay/dash/issues/436
thank you doing my bestGreat work man, glad you are here.