BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

[tiras]

check out this provider for VPS  :  https://www.hyperexpert.com

1GB 1CPU $3
2GB 2CPU $5

I've been  using it on testnet with no problems so far .

[Rob Andrews]

check out this provider for VPS  :  https://www.hyperexpert.com

1GB 1CPU $3
2GB 2CPU $5

I've been  using it on testnet with no problems so far .

Thanks! Looks like they lost all their customers data once, but for clones of cryptonodes, might be pretty good, as long as static IPs never change.

[togoshigekata]

I updated the backup explorer: http://explorer.biblepay.org:3001/
I plan to move it from AWS to a cheaper Vultr server in the near future, which I guess means I would need a DNS record update to point to new address, Ill let you know Rob!

====

In addition to Robs Original Sanctuary Guide:
http://wiki.biblepay.org/Create_Sanctuary

I also am working on a more detailed/step by step Sanctuary 2 Guide (wasnt sure what to name it):
http://wiki.biblepay.org/Create_Sanctuary_2

[jaapgvk]

I tried setting up a masternode in prod, but in my sanctuary wallet I get the following message when I type 'masternode status':

Code Select Expand

Not capable masternode: Masternode not in masternode list

Mnsync is 999 and everything else went without errors as far as I know. My controller wallet is showing the masternode as 'pre-enabled', but I can't find it on my sanctuary wallet masternodelise.

It's masternode '12161bf30e75b1bebe9d7b0ebf0d73902e0bea07021c400d166debab4a655552' on '84.29.208.33'.

Does anyone know what this might mean? Otherwise I just have to try and setup the masternode again from the start, I guess...

[togoshigekata]

Interesting, I believe I got a similar error when my masternode was still in MISSING status,
once I ran start-alias from controller wallet it went from MISSING to PRE_ENABLED state
and running "./biblepay masternode status" on the sanctuary wallet gave me: "status": "Masternode successfully started"

[jaapgvk]

Thank you togoshigekata and Alex I just installed everything again from the start and now it's working, so I probably did something wrong...

And also thank you both for your excellent work and guides!

[Rob Andrews]

Hey Rob, I was just wondering. Is the client version 1.0.6.5 the mandatory or is anything with the protocol 70709 good?

I'm just asking because I totally forgot the dnsseeder is actually only looking at the protocol version to determine if a node is good or not. I could modify it to look at the client version instead but I would like to get a confirmation from you before I go ahead with that.

I didnt increment the version, since masternodes have never been live yet in prod, but in this case, 1065 is required after block 21350.  We can enforce that with a checkpoint around 21550.  As a matter of fact, its no big deal if the owner of the 1040 botnet wants to play games, as that is more BBP for us on 1065.

Yeah I think your code would have to look at both, as some mandatories go by chain height + version, others go by forced protocol upgrades.

Id just say Good = 70709 + 1065, bad is anything less.

[jaapgvk]

I guess f8000 is looking good sofar.

Also I just noticed that two of the mainnet masternodes have the label 'EXPIRED'. Just a heads-up

[klondike]

that f8000 this was step back ... pool vs miner machines= big problems: more ppl calling me where is problem,that their machines is offline from pool when mining: classic 2core home HTPC and similar machines max 4 core ....  very frustrated... i hope that all will be stable cos this stable isnt ...

before we had our machines stable with stable hashes power ... now?

im testing 2 VULTR machine (for 2 MN) for mining and still crashed after few minutes
cpuproclimit=8  before was this 2 machines stable with mining on pool . ah yay

so where is problem?


Alex, Rob thanks for your time

[jaapgvk]

that f8000 this was step back ... pool vs miner machines= big problems: more ppl calling me where is problem,that their machines is offline from pool when mining: classic 2core home HTPC and similar machines max 4 core ....  very frustrated... i hope that all will be stable cos this stable isnt ...

before we had our machines stable with stable hashes power ... now?

im testing 2 VULTR machine (for 2 MN) for mining and still crashed after few minutes
cpuproclimit=8  before was this 2 machines stable with mining on pool . ah yay

so where is problem?


Alex, Rob thanks for your time

What do you mean with 'offline'? Because my slow mining laptop also sometimes doesn't show in the list, but that's because is has zero shares at that moment. It's only in the list after it has it's first share. And it resets after every found block.

[klondike]

thanks ALEX for your helping BBP ... excellent job with ROB!!!

[jaapgvk]

I just updated my masternode-wallet (not the controller, because it isn't out yet), and the status says the following:

Code Select Expand

{
  "vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
  "service": "208.115.99.108:40000",
  "status": "Not capable masternode: Invalid protocol version"
}

And in the masternodelist it says:

Code Select Expand

  "12161bf30e75b1bebe9d7b0ebf0d73902e0bea07021c400d166debab4a655552-1": "UPDATE_REQUIRED"

Is this concerning? I did a 'masternode start-alias' from the controller wallet.

[togoshigekata]

My mastenode went into state EXPIRED and running "masternode status" in the masternode wallet gave me the same message: "Not capable masternode: Invalid protocol version"

[Rob Andrews]

My mastenode went into state EXPIRED and running "masternode status" in the masternode wallet gave me the same message: "Not capable masternode: Invalid protocol version"

I had to increment the protocol version today in prod- is this in prod?

[togoshigekata]

Yes, this is in production/mainnet, I noticed protocolversion went from 70709 to 70710

looks like its slowly hitting the current masternodes and operators are starting them again,
I assume it wont be an issue once the mandatory block is hit?

Im not sure if another start-alis is actually needed or not, How long can a masternode stay in the EXPIRED state?

Yesterday my biblepay daemon crashed in my masternode and it was in the EXPIRED state and when I turned on the daemon again, it went right back to ENABLED, so that was cool.

I know starting a masternode again can take like an hour or so to go from PRE_ENALBED to ENABLED.

===

Just noticed your post:

"everyone will have to start-many on the sanctuaries, we just had a protocol upgrade."