Bible Pay

TestNet => TestNet Discussion Archive => Topic started by: Rob Andrews on October 03, 2017, 01:07:26 pm

Title: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 03, 2017, 01:07:26 pm
Good Afternoon All,

It is time to Test sanctuaries in Testnet.

- Testing requires linux - because windows will not run watchman on the wall (thats the decentralized sanctuary database)
- Testing requires 500,000 TestNet BBP to be sent to the new testnet masternode (actually send more, so you have extra first) - this is not the final amount to run a sanctuary, its the testnet amount
- Testing requires an external open IP, IE you need to be able to run with the firewall port 40001 open
- Testing needs to have the latest version of BBP compiled from source

If anyone needs test BBP, let me know.

Here is a guide to explain how to start a masternode:

http://wiki.biblepay.org/Create_Masternode
(*** NOTE!!!  The above guide says 1 million BBP is required.  Its actually 500,000 BBP in testnet!  Please dont try 1 million as it will not work ***)





** Note that this procedure documented above actually failed.  It failed when I took a look at the log in the actual masternode wallet, an error was generated saying something to the effect of invalid escrow sent to the masternode. 

To get around this, send the test biblepay to the masternode wallet, create the  private key on the masternode, set the masternodeprivatekey and masternode=1 in the config, and then we can resume testing.  If anyone can get this working in 'cold' mode (that means the mastnode has 0 funds in the wallet with remote activation working) that would be extremely valuable.  I will obviously help with this, as we cant go live until cold mode works, but I also need to move past and start testing the governance commands next.

My first test procedure is lets ensure we have 5+ masternodes running and see if we can all see each other and stay in sync.  We now have 1 minute blocks on testnet.

PS: To install watchman-on-the-wall, please see the "BuildBiblePay.txt" document in the root.  It has a section called Watchman. 

Note, I will modify the wiki entry to explain how to add watchman to the cron.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 03, 2017, 01:14:43 pm
Here is a blockhash to see if you are synced:

showblock 2700:
  "hash": "4d5d13c36da85b81ab23e1f2747cc080f053409c711a680b2cbb9e278efc49b3"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 03, 2017, 01:22:37 pm
telnet node.biblepay.org:40001

Code: [Select]
telnet: could not resolve node.biblepay.org:40001 Name or service not known
Same with ping.
Hmm, cant be, I flushed my dns cache, and when I ping 'node.biblepay.org' i receive 97.99.69.33.  I also checked cloudflare and the entry is live.  Do you have DNS enabled at your provider by chance?
Anyway you can go by IP now :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 03, 2017, 01:51:40 pm
I will try and set up a sanctuary sometime this week :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 03, 2017, 03:04:26 pm
I have a lot of these errors, so I can't get 500k tBBP :)

Code: [Select]
2017-10-03 19:42:05 ^M
ProcessBlockFound::Generated 16800.25
2017-10-03 19:42:05 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 2780.000000 pindexPrev e463d4d9e236b8ff1ed18b5bcb03fcc914db7d4a59a0127dd785949c7ce81bf7
2017-10-03 19:42:05 ERROR: CheckBlockHeader(): proof of work failed
2017-10-03 19:42:05 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-10-03 19:42:05 ERROR: ProcessBlockFound -- ProcessNewBlock() failed, block not accepted
2017-10-03 19:42:05 keypool keep 12
2017-10-03 19:42:05 12121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212CMasternodePayments::SyncLowDataPaymentBlocks -- asking peer 3 for 2781 payment blocks
2017-10-03 19:42:38 1212SYNCSTATUSCOUNT -- got inventory count: nItemID=3  nCount=0  peer=3
2017-10-03 19:42:38 1212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212CBlock(hash=e38012aaad6067cdb7d93bf175da5b0632683e7c6ca0ccffefbe92b9b4f2f426, ver=536870912, hashPrevBlock=e463d4d9e236b8ff1ed18b5bcb03fcc914db7d4a59a0127dd785949c7ce81bf7, hashMerkleRoot=1757c05d10cf959f669b18b2b96cfe795f4283d13a98e9462c37d40d2bdef4d7, nTime=1507059804, nBits=1c6128d6, nNonce=22193, vtx=1)
  CTransaction(hash=1757c05d10, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02dd0a02dc00)
    CTxOut(nValue=16800.25000000, scriptPubKey=2103b9ef046bca7ec39a61e246eb10)

Code: [Select]
2017-10-03 19:34:15 ^M
ProcessBlockFound::Generated 16882.70
2017-10-03 19:34:15 ERROR: ProcessBlockFound -- generated block is stale
2017-10-03 19:34:15 keypool keep 43
2017-10-03 19:34:15 12121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212121212CBlock(hash=ec2ea9af71570945dd38a4dfb689ea77cad6d9d28360bf4caca8b4dd6fe96ab3, ver=536870912, hashPrevBlock=4649305bba3d4e886d2d258379ff7e6c5bdb37280b523de6e36abdb011bc9aa8, hashMerkleRoot=c06abfafd37dedb14eea6defafde0f91e6cedf1f3e815b6c2d8e248c2d660128, nTime=1507059262, nBits=1d0128a9, nNonce=7175, vtx=1)
  CTransaction(hash=c06abfafd3, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02d60a029100)
    CTxOut(nValue=16963.45000000, scriptPubKey=21034728686b433bb0c08cec8fa1ee)

Also, somewhere in debug.log I see lines without any errors and the "AddToWallet" line, but my wallet balance is 0.

Code: [Select]
2017-10-03 19:34:14 ^M
ProcessBlockFound::Generated 16954.10
2017-10-03 19:34:14 12UpdateTip: new best=4649305bba3d4e886d2d258379ff7e6c5bdb37280b523de6e36abdb011bc9aa8  height=2773  log2_work=42.213349  tx=2783  date=2017-10-03 19:34:14 progress=0.003227  cache=0.0MiB(17tx)
2017-10-03 19:34:14 AddToWallet 831af4ce0947df326eb8a2a6e8729ac5b20bf9e37620bfe9b3b7020c28568927  new
2017-10-03 19:34:14 ProcessNewBlock : ACCEPTED
2017-10-03 19:34:14 1212121212CBlock(hash=e7544330af5181938b9315dd59c97faee9ef0ad7b50dfac6bfdaaa526a864869, ver=536870912, hashPrevBlock=7003ca18a69cfdf83982163b9ae56807befc22163ec094b0be303e6d5d2cdada, hashMerkleRoot=9e9e04108b340d77dc126966d096433c941475d450b34d7162afff8933ad4a8a, nTime=1507059254, nBits=1d010d1e, nNonce=7291, vtx=1)
  CTransaction(hash=9e9e04108b, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02d40a029000)
    CTxOut(nValue=16882.70000000, scriptPubKey=2103c2f360732f95a884a88bbf27d6)

Hmm, I just grepped my first node running the newest version and dont have that particular checkblock error.  Before I delve further into this,  did you possibly have an old testnet blockchain before?  Can you please try deleting blocks -R and chainstate -R and mncache.dat and peers.dat and restarting?  Its possibly you have some headers from the prior chain or from another node running the old version.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 03, 2017, 06:27:44 pm
Removed all files and started again, now I have this:

getchaintips
Code: [Select]
[
  {
    "height": 2800,
    "hash": "eb067b1c548908ab169f1d97b1421213e38970357649116b3818154a0b9eb18c",
    "difficulty": 4.276836403033586,
    "chainwork": "000000000000000000000000000000000000000000000000000004ef01f970b6",
    "branchlen": 2724,
    "status": "headers-only"
  },
  {
    "height": 80,
    "hash": "3a1f92a302a6d72eb32581aad9fbd61cf7ee4f71e52497b3b8dd9fc137b2b845",
    "difficulty": 0.1591938163763032,
    "chainwork": "0000000000000000000000000000000000000000000000000000000e14654f62",
    "branchlen": 0,
    "status": "active"
  },
  {
    "height": 28,
    "hash": "f3c2791f04be079d0b7d3a28bf61ae28ee24b06a762ab6ad19af7667b4e8d88c",
    "difficulty": 0.0001111867252099767,
    "chainwork": "00000000000000000000000000000000000000000000000000000000001d0e27",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28,
    "hash": "e4c3ec0608dd9e051bbdd2dec3772dc3d048e56f19fdd31c67c6f11627412a7c",
    "difficulty": 0.0001111867252099767,
    "chainwork": "00000000000000000000000000000000000000000000000000000000001d0e27",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 19,
    "hash": "7065555a9dd366041ecc5a3d0af2567291058292c5fbe3ca449595f1b8fee7f2",
    "difficulty": 8.31726475264857e-06,
    "chainwork": "0000000000000000000000000000000000000000000000000000000000022637",
    "branchlen": 1,
    "status": "valid-fork"
  }
]

I have to give up for now, will be back tomorrow :)

Yeah, we might have to increment the protocol version in testnet.  Lets see what happens tomorrow after I fire up 3 vultrs and one personal machine and we try at the same time.  Have a good night.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: svirus on October 04, 2017, 06:17:42 am
hi,
I'am on good chain in testnet ? :
Code: [Select]
new best=5e008f7ab671fcbefafbf410db50b46c893f1824ce7b0f9bd7a05a5dac7e05cd  height=3428

BTW... I must mine 1mln BBP , or someone can send me BBP for start masternode ? ;)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 04, 2017, 08:27:16 am
hi,
I'am on good chain in testnet ? :
Code: [Select]
new best=5e008f7ab671fcbefafbf410db50b46c893f1824ce7b0f9bd7a05a5dac7e05cd  height=3428

BTW... I must mine 1mln BBP , or someone can send me BBP for start masternode ? ;)

Yeah, your on my chain, but I know we still have a fork, because whoever has the 142.44 IP has the last 100 blocks different, and on my 2nd vultr, I had to ban you to get it to sync, who has 142? Can you please restart your chain?

Anyway svirus, please post your testnet address and Ill send the tBBP. 

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 04, 2017, 08:28:52 am
Here are a few addnodes if anyone wants to try to sync:

addnode=node.biblepay.org
addnode=vultr4.biblepay.org
addnode=vultr5.biblepay.org

I also fired up a windows PC on testnet but its behind the firewall.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 04, 2017, 09:36:12 am
Ive got to run some errands for a few hours but while Im gone if you guys could just see if you can keep the chain synced with inblue and Westwarnsworth, just verify the thing is agreeing on 1047 for everyone with 1 minute blocks.  Then we can move to the next baby step which is enabling a few hot masternodes, and verifying the masternode payments are actually paying each other the 50% compensation level.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: svirus on October 04, 2017, 12:45:54 pm
yiADn9XHSj58Vab9zqMooQCTsYmADNZRXJ - one 1mln please ;)
I mining half day, and have only 500k ;)

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 04, 2017, 02:50:01 pm
yiADn9XHSj58Vab9zqMooQCTsYmADNZRXJ - one 1mln please ;)
I mining half day, and have only 500k ;)
Sent.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: svirus on October 04, 2017, 03:25:56 pm
Sent.

Thanks...
I will make one masternode today.
Just waitng for compile new biblepay-qt on my laptop.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: svirus on October 04, 2017, 05:55:58 pm
some anothers nodes with external IP ?
I think I'am banned on *.biblepay.org
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 04, 2017, 06:51:53 pm
some anothers nodes with external IP ?
I think I'am banned on *.biblepay.org
I only banned one IP this morning, what is your ip prefix? 

EDIT:

Btw, one thing you can do is: go into the \testnet3 dir, delete the peers.dat, banlist.dat, and the mncache.dat, and restart.  (With the 3 addnodes in).
One other thing, from a command line:
telnet node.biblepay.org 40001

Ensure you get a connection?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: svirus on October 05, 2017, 12:36:53 am
I only banned one IP this morning, what is your ip prefix? 

EDIT:

Btw, one thing you can do is: go into the \testnet3 dir, delete the peers.dat, banlist.dat, and the mncache.dat, and restart.  (With the 3 addnodes in).
One other thing, from a command line:
telnet node.biblepay.org 40001

Ensure you get a connection?

I started it from other server.
But I stuck on other thing.

On my sanctuary I have messeges like:
Code: [Select]
2017-10-05 05:19:08 CActiveMasternode::ManageStateInitial -- Checking inbound connection to '137.74.0.113:40001'
2017-10-05 05:19:08 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2017-10-05 05:19:08 CActiveMasternode::ManageStateInitial -- INITIAL: Wallet balance is < 500000 biblepay
2017-10-05 05:19:08 CActiveMasternode::ManageStateRemote -- NOT_CAPABLE: Masternode not in masternode list
....
2017-10-05 05:30:53 CActiveMasternode::ManageStateRemote -- NOT_CAPABLE: Masternode not in masternode list
2017-10-05 05:31:30 12UpdateTip: new best=06ea4473c0e4cc9c63432a676e20730bf97ec27be9a91d61db977ef570af901a  height=4151  log2_work=42.877044  tx=4165  date=2017-10-05 05:31:33 progress=0.004809  cache=0.0MiB(10tx)
mnsync status:
Code: [Select]
{
  "AssetID": 2,
  "AssetName": "MASTERNODE_SYNC_LIST",
  "Attempt": 1,
  "IsBlockchainSynced": true,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true
}
masternode list is empty.

on my laptop:
mnsycn status
Code: [Select]
{
  "AssetID": 999,
  "AssetName": "MASTERNODE_SYNC_FINISHED",
  "Attempt": 0,
  "IsBlockchainSynced": true,
  "IsMasternodeListSynced": true,
  "IsWinnersListSynced": true,
  "IsSynced": true,
  "IsFailed": false,
  "MasternodesEnabled": true
}

masternode list
Code: [Select]
{
  "0b9b0bc476ba9fd11060d3aaced702bd90608a947259420d8f2dff97d189804d-1": "PRE_ENABLED"
}

my server and my laptop is connected to the same node (vultr5.biblepay.org).


EDIT
ok, in my office I forwarded 40001 port to my laptop.
now everything is connected, on my laptop I have locked tx for masternode, and is in masternode list,
but when I try to broadcast masternode node then on my sanctuary I see this in debug log:
Code: [Select]
2017-10-05 06:38:24 CMasternodeMan::CheckOutpoint -- Got mismatched pubKeyCollateralAddress and vin
2017-10-05 06:38:24 CMasternodeMan::CheckMnbAndUpdateMasternodeList -- Rejected Masternode entry: 0b9b0bc476ba9fd11060d3aaced702bd90608a947259420d8f2dff97d189804d-1  addr=137.74.0.113:40001

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: svirus on October 05, 2017, 09:07:21 am
ok... I found on first post, there now external cold wallet not working ;)
but... I found this: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/27197442/Guide+using+OS+X+local+Linux+remote
here is one more option ... masternodeaddr - that we need to put in our cold wallet
maybe this is a problem ?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 05, 2017, 09:42:11 am
I modified the install wiki a bit. 

One issue I hit was it exhausted the virtual memory while building BBP Core.  I'm rebuilding it from
./autogen.sh
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/"
sudo make

on the linux install docs.  Is 1 GB RAM enough to build?


Just a general note on this particular issue regarding the Create_Masternode wiki.
If you have not installed a Masternode successfuly and are not yet running a successful masternode yet, I would suggest not trying to modify the wiki page that you dont fully grasp yet.

I know the page is no where near perfect, but what is happening is you are making modifications to something that is not complete and potentially misleading us.

I think what we need to do is get our cold and hot masternodes working first, and then tweak the prod instructions with Successful known changes.

If you want, you can go ahead and clone the masternode create page to another testnet page name and tweak that one for testnet until its final.

Changing to 500,000 bbp is fine for testnet, but its not the final amount for prod.
The 'sanctuary server' is not the right nomenclature.  All the hosts are servers.  (IE this is not a client-server solution).  There are going to be one to many sanctuaries per single controller wallet. (So we have controller wallet, and sanctuary wallets).

I just wanted to mention this because I noticed you took out all the lines that said 'still from the main PC' to try to simplify it.  Thus leaving ambuiguity between the commands from the sanctuary wallet and the main controller wallet.  So lets clone the page to a create_masternode_testnet version and do whatever you want to it until its clear then we can overwrite the prod version.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 05, 2017, 09:54:33 am
ok... I found on first post, there now external cold wallet not working ;)
but... I found this: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/27197442/Guide+using+OS+X+local+Linux+remote
here is one more option ... masternodeaddr - that we need to put in our cold wallet
maybe this is a problem ?
Hi Svirus,

Great find.  Yeah, I had gone through that myself, and in the end the only way I could create the masternode was in hot mode, and then I did successfully boot two masternodes up, and they are running in cold mode.  In cold mode, I see the masternodes are now being paid through the masternode payment system (not through block subsidy) and the amounts seem to be correct.  I have not successfully activated one in hot mode.

You did find the key to the problem, whenever the hot wallet is 'activated' from the controller wallet, then I see this in the log on the *sanctuary*:
Got mismatched pubKeyCollateralAddress and vin

Just like you do.  Now it is possible, that my first 7 tests didnt actually honor the 'masternodeaddr'.  I do remember this, it is quite different to fully qualify the addr and the port.  If you want you can try this:  masternodeaddr=YourIP:40001. Note the fully qualifyied port number for testnet. 
Could you see if that works?  Btw, our port is 40000 for prod and 40001 for testnet, so anytime you see a 9999 for dash its 40001 for our testnet.

Im thinking we try to get hot mode going a little while longer, and eventually over the next day or so, we put someone else here on a mission to keep working on hot mode and we bring up 5 or so in cold mode to keep us moving as a team, so that I can add the code for the sanctuaries on the web site for testnet.

Does anyone here have a dash masternode?  I was kind of wondering how long it takes to see the other masternodes in the all sanctuaries list.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 05, 2017, 09:55:38 am
Sorry to tinker with the wiki, just was trying to make it cleaner and easier to read as I went along and didn't consider the nomenclature being as significant but understand.

Also, have you installed the wallet on a 1GB Vultr?  If so, do you have any thoughts about the memory issue.?

No, sorry, I really never ran into that memory problem, I dont even have any input here.  You would be better off googling that one.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 05, 2017, 03:04:08 pm
Hang on guys, I see a fundamental error in the instructions.

The masternode genkey command should actually be done on the SANCTUARY!  LOL. 

Let me do another çold wallet test, and if it works Ill edit the wiki, hang on.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 05, 2017, 03:20:10 pm
OK. Btw, is there anything else to do after following the wiki instructions? Or that's it, then just keep the node online?
Were going to have to see if it stays in sync, shows a global list of masternodes that agree, if the payments are correct for Inbound payments, how to install watchman-on-the-wall, if watchman helps the masternode show ÄCTIVE (instead of just synced), and how to create a proposal.

So far, we have achieved absolutely Zilch.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 05, 2017, 04:11:51 pm
I have to step out but if anyone wants to continue creating a cold sanctuary tonight you can refer more to this video:

https://www.youtube.com/watch?v=Lybtz7iucVs

Note that he definitely creates the masternode genkey on the sanctuary side.

 :P
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 06, 2017, 05:42:45 am
Can someone send me 600k (or whatever is enough for a sanctuary) testnet biblepay?

yiVg3gjd2UiyeCmFrbvL8phqUnLTYdVroK
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 06, 2017, 09:23:55 am
Can someone send me 600k (or whatever is enough for a sanctuary) testnet biblepay?

yiVg3gjd2UiyeCmFrbvL8phqUnLTYdVroK

Sent.


So Im a little frustrated with the 'cold wallet' creation process (on my end), and at this point Im going to move on and spin up 3 hot wallet masternodes.  As I need to move further.

At least with hot masternodes, theoretically, we can still test to see if the masternode list is being broadcast and that we stay in sync, and that the payments and votes work.

The biggest disadvantage of the hot wallet masternode is your hosting provider can steal your biblepay.  Yes thats a problem we will have to solve separately, but I dont want it to stop our progress.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 06, 2017, 11:40:30 am
Here is a link to create a swap file on the vultr server if you hang up during compile:

https://digitizor.com/create-swap-file-ubuntu-linux/

Worked for me.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 06, 2017, 12:35:34 pm
I am elated to inform everyone that a bug existed in 1047, preventing sanctuaries from being verified and broadcast to other nodes.  I believe this even caused a small d-dos issue!  The problem is fixed now in 1048.  Code has been sent in to github.  Windows is compiling now.

Sorry about the inconvenience.  It took 3 full days out of my life.

So, now if anyone feels like testing a hot wallet, please do it over.  For now, Ive already created 3 cold wallets this morning and Im going to go ahead and test those out first.

Also, I updated the 'CompilingBiblePayOnLinux.txt' doc in the root of github.  There is a section in there for watchman-on-the-wall.  Feel free to install it on your linux node and test it.  I have it running, and it appears to be working.  Now we are making some progress again!  Thank God!

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 07, 2017, 06:25:49 am

So, now if anyone feels like testing a hot wallet, please do it over.  For now, Ive already created 3 cold wallets this morning and Im going to go ahead and test those out first.


I finally got a linux version compiled on my laptop. I tried it on a Raspberry 3 first (with ubuntu 16.04), but it doesn't seem up to the task. It freezes when compiling.

I there also a walkthrough to create a hot-wallet sanctuary?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 07, 2017, 06:50:24 am
Make sure you have enough memory. Follow admin's post above or for me I have found these commands to be working well for a 1 GB RAM machine:

Code: [Select]
free (check if swap is 0)
dd if=/dev/zero of=/var/swap.img bs=1024k count=1000
mkswap /var/swap.img
swapon /var/swap.img
free (check if swap is 1024)

Then compile again.

Thanks! I saw the earlier post but didn't link it to my specific situation, but it's indeed what I was looking for. Will try again :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 07, 2017, 09:31:10 am
OK, I compiled 1.0.4.8 and also followed the steps to install watchman, but I encounter this:

~/.biblepaycore/watchman$ venv/bin/python bin/watchman.py

Code: [Select]
[Errno 111] Connection refused
Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.

biblepayd is running, but I don't know how to do the second part.

Yea, and I know we need to modify the master wiki with better instructions, sorry, I plan on doing that once we get a stable set of instructions, but anyway on this issue:

Ensure the 'watchman.conf' file (in the watchman dir) is pointed to testnet and not mainnet (by putting a # in front of the main and unpounding the testnet)
- Ensure rpcallowip=127.0.0.1 is set along with rpcuser and rpcpassword in the main 'biblepay.conf' for the node (the one in the root) and then restart. 

When you rerun watchman, if the nodes 'mnsync status' is 999, watchman should return empty meaning everything is working (in contrast to an error).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 07, 2017, 02:30:21 pm
I already did all of that. I did it again now carefully to confirm the steps, but I still get the same error.  :-\ Currently I have no idea where else to look.


LOL, I've never seen that before. I wonder how Wikipedia deals with this.


Great, more things to deal with huh.

Looks like we need to put a captcha on the edit page.

If that doesnt stop it later on we can go to requiring an approved account.

Ill look into deleting all this garbage next.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 07, 2017, 03:58:44 pm
Been out of pocket for a few days, sorry.

I'm getting success with the swap file, I'll try and get time in the next few days to write up some more notes and submit them.  Again, apologies for editing the wiki when I wasn't having success.

Speaking of the wiki, it looks like it is getting spammed pretty hard.


Ok, I deleted the 7500 spammed fake articles, and 3250 fake accounts.

I added a math captcha on article edit, and on user create.  I enabled the option to require email verification and the requirement to have an account and be logged in before editing any pages.

Thanks for pointing out the mass defacation.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on October 08, 2017, 02:30:00 am
500k tBBP please :) yPn4ibkbAHo9jB1SthLEFqzRVpsDmfWTN3

EDIT: Mined a bunch of coins, now waiting for them to mature

=====

Questions:
- How to start Biblepay Daemon in TestNet mode on linux command line?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 08, 2017, 04:41:06 am
500k tBBP please :) yPn4ibkbAHo9jB1SthLEFqzRVpsDmfWTN3

EDIT: Mined a bunch of coins, now waiting for them to mature

=====

Questions:
- How to start Biblepay Daemon in TestNet mode on linux command line?

I was trying to send to tBP but when I fired up the testnet wallet I couldn't get synched...

But anyway, to start in testnet with the GUI-wallet, go to your Biblepay qt folder $BP_ROOT/biblepay/src/qt

And then run the following command:
./biblepay-qt -testnet

I don't know how to start the headless wallet, but I guess in general it will be the same procedure.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 08, 2017, 07:56:59 am
I there also a walkthrough to create a hot-wallet sanctuary?

Can anyone help me with this? I'm not successful in creating a cold masternode. But maybe that's because both my computers are in the same network and have the same external ip? I'm not at all an expert in linux, so I just try to follow the guide as best as possible.

Also: should the biblepay.conf also be in the testnet3 folder? Or does the testnet use the same one as the main wallet? I put it in the testnet3 folder btw.

I'm also compiling biblepay on my raspberry as we speak. seems to work now I have the swapfile enabled. I wonder how much hps2 I'm gonna get with this :p
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 08, 2017, 09:21:34 am
Can anyone help me with this? I'm not successful in creating a cold masternode. But maybe that's because both my computers are in the same network and have the same external ip? I'm not at all an expert in linux, so I just try to follow the guide as best as possible.

Also: should the biblepay.conf also be in the testnet3 folder? Or does the testnet use the same one as the main wallet? I put it in the testnet3 folder btw.

I'm also compiling biblepay on my raspberry as we speak. seems to work now I have the swapfile enabled. I wonder how much hps2 I'm gonna get with this :p
So what I have found so far about public IPs, is they really will be required in prod because your masternode payment will fall back to the end of the queue if the pings to the external IP fail.  Also in testnet, it will be hard to test watchman out properly if we dont simulate the prod environment with real permanent IPs.  You can use a dynamic IP though, it just has to be Public and Distinct (another words, a house IP is fine with port forwarding, but you can only have One masternode running in your house per public IP).
Anyway, if you will port forward port 40001 from your router to the PC that is going to be the masternode, and it has to run linux since watchman needs to run, do a test from another pc to telnet to the address (IE:      telnet my_public_ip 40001) and ensure it answers.  Then you know you have that public IP associated with the new masternode.

As far as binding it to the new hot wallet, you would need to put this line in the actual masternode (not the controller) in the biblepay.conf file:
externalip=my_public_ip

On the controller wallet, you dont need the line with externalip.

Then, as far as directories, here is what I learned that is sort of frustrating:  For testnet, you need to go into the \testnet3 directory and create the masternode.conf file there, IE:  \testnet3\masternode.conf.  But for the standard settings in testnet, they go in : ~.biblepaycore\biblepay.conf (IE the root).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on October 08, 2017, 05:50:14 pm
TOGO NOTES

We are testing Masternodes (Sanctuaries) functionality on the Testnet chain, using Test Biblepay (tBiblePay) coins

Requirements
2 machines with 2 separate IP addresses

you are setting up a Masternode on a remote Linux server (Sanctuary Wallet)
and storing tBiblePay coins on a local Windows PC (Controller Wallet)

PART 1 - Controller Wallet (Windows) TestNet

On local/home Windows PC:

1. Download & Install latest version of BiblePay:
http://biblepay.org/

2. Enable and Run Wallet in Testnet Mode

Find and Edit biblepay.conf file in %appdata%/BiblePayCore folder,
Add line below and Save:
testnet=1
(Note: Can also edit biblepay.conf from Wallet Menu >> Tools >> Open Configuration File)

3. Run BiblePay

4. See Green Background on loading screen and on Icon, also See tBiblePay name for coins
On command line, use ./biblepay-cli getinfo command and check for: "testnet": true

5. After Loading, Close Wallet

6. Edit biblepay.conf file, add lines below and save:
addnode=node.biblepay.org
addnode=vultr4.biblepay.org
addnode=vultr5.biblepay.org

7. Run BiblePay

8. Ask in this Forum for someone to send you 500,000 tBiblePay (Test Biblepay coins)
Post your Receiving Address:
Wallet Menu >> File >>> Receiving Addresses >> Right Click >> Copy Address
(or start mining coins: setgenerate true X)

==========

PART 2 - Rent Linux Cloud Machine

1. Research and Choose Cloud Provider (AWS, Google, Azure, [Vultur], etc)  and Create Account
2. Choose Machine to Rent (Recommend: Ubuntu 16.04, 2GB RAM)
3. Payment Method
4. Connect to it / SSH (Putty http://www.putty.org/ SSH Client for Windows)

==========

PART 3 - Install Sanctuary Linux Wallet
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

==========

PART 4 - Run Sanctuary Linux Wallet Testnet

On remote Linux machine:

1. Enable & Run Wallet in Testnet mode:

Edit ~/.biblepaycore/biblepay.conf file and add
testnet=1
addnode=node.biblepay.org
addnode=vultr4.biblepay.org
addnode=vultr5.biblepay.org

2. Close wallet:
./biblepay-cli stop
-or if stuck-
ps -ef #view processes
kill PID

3. Run BiblePay:
./biblepayd -daemon

4. Check that blocks number matches home Windows wallet and that testnet=true:
./biblepay-cli getinfo

===========

PART 5 - Financing your Sanctuary Masternode

http://wiki.biblepay.org/Create_Masternode

1. Generate private key on Sanctuary Masternode Linux machine

./biblepay-cli masternode genkey

(Store this as your MASTERNODE_PRIVATE_KEY)

2. Controller Wallet - Show Proof of Coins
getaccountaddress MASTERNODE_NAME #creates MASTERNODE_ADDRESS
sendtoaddress MASTERNODE_ADDRESS 500000 "" ""

3. Wait for 15 confirmations
(Note: Testnet chain mines blocks every 1 minute,
turn on miner if no one else is mining so confirmations can go through: setgenerate true 1)

4. Controller Windows Wallet - Edit masternode.conf:
%appdata%/biblepaycore/testnet3/masternode.conf
Add line below and Save:

ALIAS IP:40001 MASTERNODEPRIVKEY TRANSACTIONHASH INDEX

ALIAS: Any name/label that you want to call your masternode
IP: Your masternode IP (Your masternode VPS's IP)
MASTERNODEPRIVKEY: This is the private key that you placed in your remote configuration
TRANSACTIONHASH: This is the transaction hash for the transaction in which you got your 500000 BBP deposited.
INDEX: This is the Index of your transaction for that address I'll show you how to get it in a bit.

4.a Get TRANSACTIONHASH and INDEX from running this command:
./biblepay-cli masternode outputs

You will get a string that looks like this:
{
"06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb" : "0",
}
The long string is your TRANSACTIONHASH, and the last number is the INDEX.


5. Controller Windows Wallet - Edit biblepay.conf:
Find and Open: %appdata%/BiblePayCore/testnet3/biblepay.conf
Decide on RandomUsername and RandomPassword to use for RPC credentials
Add Lines below and Save:

rpcuser=RandomUsername
rpcpassword=RandomPassword
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

6. Restart Controller Wallet

7. Sanctuary Wallet Remote Linux Machine, Run Firewall/Port commands:
sudo apt-get update
sudo apt-get install ufw
sudo ufw allow ssh/tcp
sudo ufw limit ssh/tcp
sudo ufw allow 40001/tcp
sudo ufw logging on
sudo ufw enable
sudo ufw status

8. Sanctuary Masternode Linux Wallet - Edit ~/.biblepaycore/biblepay.conf:
rpcuser=RandomUsername
rpcpassword=RandomPassword
rpcallowip=127.0.0.1
rpcport=9998
listen=1
server=1
daemon=1
logtimestamps=1
externalip=MASTERNODE_PUBLIC_IP
maxconnections=256
masternode=1
masternodeprivkey=MASTERNODE_PRIVATE_KEY

(MASTERNODE_PUBLIC_IP, Public IP Address of Remote Linux Sanctuary Wallet_

9. Sanctuary Masternode Linux Wallet - Restart BiblePay:
./biblepay-cli stop
./biblepayd -daemon

10. Controller Windows Wallet - Start Masternode?
masternode list
masternode list-conf
masternode start-alias MASTERNODE_NAME
(Note: MASTERNODE_NAME is from Step 3. b when you added Masernode information to /testnet3/masternode.conf file)

mnsync status
(Masternodes take a few minutes to sync(

masternode start-alias MASTERNODE_NAME

masternode help
masternode debug

11. Sanctuary Masternode Linux Wallet, Check Status:
masternode status

==========

PART 6 - Watchman
How to install Watchman on the Wall
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://github.com/biblepay/watchman

1, Clone & Install Watchman
sudo apt update
sudo apt install git python-virtualenv virtualenv
cd ~/.biblepaycore
git clone https://github.com/biblepay/watchman.git
cd watchman
virtualenv venv
venv/bin/pip install -r requirements.txt

2. Set Watchman Config
nano watchman.conf
- Ensure the 'watchman.conf' file (in the watchman dir) is pointed to testnet and not mainnet (by putting a # in front of the main and unpounding the testnet)
[For nano editor, ctrl+O to save file, ctrl+X quit]

3. Run Watchman
venv/bin/python bin/watchman.py

4. Setup Watchman in Cron:
crontab -e
Add this line:
* * * * * cd /home/YOURUSERNAME/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

===========

Wallet GUI PROTIP
Settings >> Options >> Wallet >> Show Masternodes Tab >> OK

References:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://github.com/biblepay/watchman
http://wiki.biblepay.org/Create_Masternode
https://www.youtube.com/watch?v=Lybtz7iucVs

Dash Masternode Guides:
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867820/TAO+S+SETUP+GUIDE+FOR+DUMMIES+12.1
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867877/Start+multiple+masternodes+from+one+wallet+start-many
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/24019061/Newcomer+Section+-+What+is+...+and+how+do+I+set+one+up

More References:
https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)#JSON-RPC
https://bitcoin.org/en/developer-reference#remote-procedure-calls-rpcs
https://github.com/dashpay/dash/blob/master/contrib/debian/examples/dash.conf
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on October 09, 2017, 09:21:02 pm
Im stuck installing watchman:
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://github.com/biblepay/watchman

This command I get an error:
venv/bin/python bin/watchman.py

[Errno 111] Connection refused
Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on October 09, 2017, 10:37:22 pm
https://www.youtube.com/watch?v=Lybtz7iucVs&t=75s

he did run "masternode genkey" command in the remote Linux wallet, interesting, Im still confused on that

he also sets in vivo.conf
rpcport=10000
masternode=1
bind=PublicIP:Port
masternodeprivkey=asdf

Wallet GUI PROTIP
Settings >> Options >> Wallet >> Show Masternodes Tab >> OK

These Dash Guides look like their masternode genkey is run on local home wallet
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867820/TAO+S+SETUP+GUIDE+FOR+DUMMIES+12.1
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867877/Start+multiple+masternodes+from+one+wallet+start-many

https://dashpay.atlassian.net/wiki/spaces/DOC/pages/31326216/Simple+MN+on+a+Windows+machine
" a more simple method of running a mastermode directly on a Windows platform, if you have enough confidence that your digital cash is safe. With this method, you will be using your wallet directly as a masternode, keeping it open 24/7."
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 10, 2017, 09:24:12 am
Togo,

Thanks for the guide buddy, you are the man!  I think what we can do is, once we get this process down, Ill edit the create_masternode to be the 'highly technical' version, just to refer to as a sanctuary owner.  We can take your version, which includes more details and make a linked page for newbies who need more help (or something to that effect).

Anyway let me just try to answer the questions from your post first, instead of reposting the entire big post, Ill be back.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 10, 2017, 09:45:08 am
I just wanted to mention that I have been a little busy lately (other than being interrupted to upload the pool, which is a huge necessity), with a brand new cryptocurrency feature for biblepay.  I think it might be "the killer" feature for us.

I'm thinking about adding colored coins into biblepay with an integrated 401k or retirement account fund inside the wallet.  And in-wallet trading.

I'm thinking maybe we can be the first coin with the ability to trade BiblePay for our second asset inside the wallet (other than Ripple, but technically, Ripple is a network of market makers making existing markets).  This is a little different.

I'm thinking we emit a new deflationary colored currency (called either retirement coins or 401k coins) inside the wallet on a schedule decreasing by 1% per day.  Then, the wallet will keep track of both normal balance and "colored coin" balances.  So you would have your BBP balance and your rBBP balance. 

   Starting on the day we have retirement coins, the retirement system would emit 1 million retirement coins per day equally divided over 202 daily blocks to the miners who mine the blocks.  However each day, the emission rate would decrease by 1% .  So on day 2 we would emit 10,000 coins less (or 990,000 retirement coins over 202 blocks).  Each block solver would receive normal BBP, plus a separate share of colored retirement coins.  If you mined 4,000 retirement coins on day #1, your balance would now be:  1,000,000 BBP and 4,000 rBBP (retirement bbp). 

You cannot send colored coins to an exchange to sell them and cannot buy colored coins on an exchange.
All colored coins must be sent in a transaction that includes a reference to the root of the colored coins (another words, the colored indicator on the tx, the previous output is colored, and the new vout for the receiver is colored).

Available coins for spending will never select colored coins for spending (IE They cannot be spent). But they can be Traded for BBP with other holders through Trade transactions.

A new RPC command will allow you to send colored coins back and forth among others, if you want to give them to others.

Now here is where it gets interesting.  If we view the colored coins as a deflationary retirement account (assuming that IF they are becoming scarcer, storing FIAT in rBBP would theoretically result in a gain in value).

We implement in-wallet trading to allow trading from BBP to rBBP.  So we would have RPC commands to "execute order SELL 9000 rBBP for 1100 BBP" for example.  Other in-wallet users would "execute order BUY rBBP 5000 for 700 BBP".  When the matching engine matches an order over the nodes, one masternode  who is the chosen winner of the round (chosen winner meaning which masternode has the closest hash to the center of the blockhash for the current BBP block, can be active market maker for this tx).

At this point, the masternode jumps in, Locks the trade, grabs the collateral from the seller and the buyer, crosses the trade, then unlocks it and it is completed.  We will have a Trading log in biblepay, so you can go into your separate debug file and monitor STEPS that occur during trading.  (In case something goes wrong partially through).

Lastly, partially executed orders would be changed via a MODIFY - so if only 1000 got filled your order would readvertise with the partial amount left.

In this way, we would have in-wallet trading, colored coins, and a second deflationary asset inside biblepay.

My projection shows that the retirement coins would deflate for 4000 days before reaching a floor where they would be emitted at approximately 1 per day (if we start with a million per day).  I think at that point, I would like the system to reverse split the coins and start over, so that we perpetually have a deflationary retirement asset inside BBP.

One benefit of having this particular feature is we would attract outside investors that would need to buy BBP in order to have the ability to buy rBBP and they also potentially download the wallet and be users and might have a tendency to be long term holders.




Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 10, 2017, 10:39:41 am

QUESTION: Are we sending coins to ourself?
It is OK to send the balance to yourself or from another node (I tested both).  The important thing is to make the amount exactly 500000 and dont click instant send or any other options.

If you are creating a Hot wallet (IE funds live on the masternode) you would send the 500k to the masternode wallet.  Now that we know cold wallets work, the recommended way is to send the funds To the cold wallet (IE the home controller wallet).


QUESTION: Which node is the Masternode?
  -> The masternode is the sanctuary running at the hosting company with the static IP.

QUESTION: Does the Masternode actually hold coins?
-> In a Hot masternode scenario, the masternode holds the coins, otherwise the masternode wallet is empty.
Biblepay puts a lock on the escrow when the masternode starts.

QUESTION: Is there a certain label that should be used for getaccountaddress?
One pitfall I noticed is if you use the same label more than once sometimes I get a new address.  I would recommend something short such as "MN1".  To ensure its only in the book once, click Receiving addresses and if it is already there as MN1, copy it to clipboard.

QUESTION: How to deal with fees when sending? Does amount have to be 500,000 exactly?
Fees are OK as long as you dont click the checkbox to Subtract fees.  Fees are stored in a different vector, so the vout is still 500,000.


QUESTION: Why port 51472? And does it need to be changed in any firewalls?
-> Oh no, this is a mistake, I will modify the guide.  This should be 40001.  Also in the UFW command list, it should be 40001.
Port 40001 is BBP testnets P2P port, 40000 is Prod BBP p2p port.



QUESTION: What IP address goes in this part of the config? "externalip=your_public_ip"
-> So when you rent your VM, and click into its hosted properties, you should see a public IP.  You should copy that and make it like this:
externalip=your_masternode_public_ip
NOTE: This is only required on the sanctuary side, not on the controller wallet side.


QUESTION: What are these config settings doing? Can the Home Wallet now control the Linux Wallet? or reverse of that?
-> These config settings only allow the home controller wallet to start and stop the masternode.  This is not only to safeguard your eventual 1 million BBP escrow if it goes up in value (to prevent vultr host from stealing it), but also because of Proof-Of-Service.  Dash has created POSE, which monitors how much uptime your masternode has stayed up and eventually becomes important if we have more than about 800 masternodes, these nodes start falling to the back of the payment queue and do not get paid if they need restarts.  When they fail and need restarted, it is easy for home computer controller wallet to start the masternode again.


QUESTION: Im stuck, help! :)
I opened /testnet3 debug.log with baretail and I see action happening, is their a syncing Period?
-> Yes, unfortunately this is a very frustrating, thats one reason I had to go to 1 minute blocks in testnet.  The wallet requires blocks to be moving for the 'mnsync status' command to iterate to the next step.  Do a setgenerate true 5, to keep blocks moving.  After 'mnsync status' shows 999, then you can start and stop the masternode and see the masternode list 'masternodelist'.


QUESTION: Where does Watchman fit in the process? What is Watchman? what is it doing?
-> Yes, I know.  Why we have to have yet another piece of software called Watchman-on-the-wall?  Watchman implements proof of service and one major superblock budget feature.  Let us say without it, Dashs POSE system would be in tatters.  Basically, if BBP ever reaches say $50 million market cap and then we have 1000 masternodes, situation A is without watchman, all the nodes who do a start on windows and then start playing video games a few hours later and kill the node by accident those nodes would not be doing anything for us, and would still get paid fully.  With watchman, every node has to send a watchdog alert every couple hundred blocks and prove their static IP and how long they been online.  This means as competition heats up you really have to have provided good service to stay in the payment queue. The other thing watchman does is collects a database of gobjects.  Governance objects are stored in tables.  Votes are kept.  It allows deleting governance objects by masternode.  The most important thing it does is when we create a very complicated budget that got approved from a proposal, it creates a text file of budget items for the superblock.  Without it the superblocks dont work very well.  Dash probably could have added code to masternode governance for all of it, but they chose this modular design in case they want to have masternodes upgrade the superblock code side and NOT the entire network to upgrade the wallet.  We inherited it so we have to embrace it now - what I am hoping is the version we ported is already stable and I can code a lot more on the web side and sort of freeze what we have for a year and grow as we are until we have our extra few IT devs helping me out to ensure we have the bitcoin commits committed constantly.

Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.

STUCK: What am I doing wrong here?
-> In this case I would go to the masternode and edit the biblepay.conf, and ensure rpcallowip=127.0.0.1 is set.
Also check to make sure watchman.conf has testnet uncommented and prod commented.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on October 10, 2017, 01:01:28 pm
Thank you so much for answering my questions!!!  :D
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 10, 2017, 01:08:19 pm
Thank you so much for answering my questions!!!  :D

No problem.  I am going to edit the create_masternode wiki page now (with that port number) etc.  I tested a cold masternode yesterday and it worked.

What I would like to do is get a few of us together here in a synced quorum, so we have at least 4 running masternodes on our synced list.
Then I can go ahead and create a governance object and see if everyone sees it.

Please, post here if you have your running static IP masternode in the masternode list.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 11, 2017, 08:25:12 am
My node is a cold node.  The only thing I've yet to get working is the watchman. 

Mine is 104.207.140.159 (cold node, no watchman, Vultr).

Could you please tell us something about a non-watchman node?  I am under the impression from interpreting the watchdog code that after a certain number of blocks passes, your non-watchman node status should go from "ENABLED" to NEW_START_REQUIRED.   

It will be interesting to know if you get paid your masternode fees with watchman off.  Are you receiving subsidies of 8300~ or so?  Note in your receiving list, the subsidy to the masternode comes in BY NAME, not by address.  For example I named my masternode DEBIAN in the cold sanctuary, so the payments come in the receiving list to DEBIAN.

Either way you will probably get tripped up when we get to the voting but it is interesting to know if you are getting paid, and when you get tripped up without watchman.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 11, 2017, 10:02:02 am
Good morning all-

I modified http://wiki.biblepay.org/Create_Masternode enough to at least allow you to create a cold sanctuary.   Ill put Togos FAQs in at the end in a half hour.

Next, now is the time to get our wheels rolling.  I added our first proposal in testnet.  (Ill explain more later on how to create a decentralized proposal, but for now, behind the scenes, I have to collect the 8 input fields- things like discussion URL, start date time, end date time, the times fit between the superblock trigger time, the payment address and the funding amount- convert this to hex- which I did create a tool for inside the wallet - I will enable the tool that does all this automatically for you).  For now, I created an proposal for 5777 biblepay, sending the reward to my testnet address for payment on one of my sanctuaries, with a start time 1 second in the future and ending tomorrow at 10 pm (for voting).  What I am hoping is today we can vote yes on this for funding, and then we can check to see if everyone sees the votes and if it goes into the superblock for payment and then obviously if I receive the money.

So first, do a 'gobject list' and see if you see the proposal for 5777bbp.

Next to vote on it for funding, grab your masternode alias name - this is done on the controller wallet wherever the escrow is and type this:
gobject vote-alias 86e1a81115085f055d585db97a42e5189e613baddc1c244dd4bce0b756e5db08 funding yes your_node_alias

Next do a gobject list. and see if the YesCount as incremented above 1 (I voted Yes 20 minutes ago).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 11, 2017, 12:03:48 pm
So far I've received several hundred transactions the last one was about 10 minutes ago, and the node shows enabled in the sanctuary list as well.

Running 'gobject list' from Debug shows two proposals, one with a hash of 86e1a81115085f055d585db97a42e5189e613baddc1c244dd4bce0b756e5db08 for 444 BBP, and the second with a hash of e4470e53f65843b8f5c82172b41c10a5e31a74bdbe4aaba32a83ca1fd1e2f656 for 5777 BBP.  I voted for the later and the vote count increased by one.
Good on the vote, so far.

Could you please double click one of the transactions from the tx list row, and grab the txid and paste here?  Id like to verify it is a masternode payment and not a mining payment.

Btw, if anyone wants to learn how to audit a payment you can do this:

getrawtransaction txid 1
When you use a 1, you will see everything about it.  In the vout list, the coinbase payment to the miner is in location 0.  A masternode payment is in location 1.  A superblock payment is in location 2->count of superblockpayment list for approved budget.  The destination address is also shown in the vout so you can see if its your masternode alias address also, by comparing it to your receiving address book list (Receiving Addresses -> List).  Your mn alias should be labeled on that list since you did the getaccountaddress alias command when you set up the cold wallet (this is all done inside the controller wallet btw).

Its also a very helpful command when someone asks you where the missing coins are.  Getrawtransaction txid 1 means the tx reached the entire network.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 11, 2017, 06:08:34 pm
910ac78557d3fbefe063e0a070333de4043010db95016002f0661aaa31344de9-001 is one of the MN payments. It was for block 8980.  I also mined block 8980 with TXID 910ac78557d3fbefe063e0a070333de4043010db95016002f0661aaa31344de9-000.
I see it, looks like a masternode payment.

I did see your watchdog expire while I was casually looking.  I wonder if your payments stopped after that?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 11, 2017, 06:14:24 pm
So now I am doing a little Biblepay hacking to try to find out if our approved proposal made it into the budget, and therefore becomes a lone superblock.

On a side note, we have superblocks every 25 blocks in testnet. 

If you want to see what is inside watchman, you can do the following:

apt-get install sqlite3

cd into the watchman directory

sqlite3 watchman

sqlite> .tables (ENTER)

select * from proposals;

To dump the schema:

.fullschema

So now, on the bright side, I see our proposal has become a proposal in SQLite.  And I see our watchdog is communicating back and forth for POSE into biblepayd.  I see the votes going into the gobject in SQL. 
     However what Im trying to find next is if the superblock height has to be between the start and end unix time of the approved proposal.  I believe all we had to do was have more than 2 absolute votes for validity and funding for this proposal to become part of the superblock, but cant say for certain yet.  Checking...

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 12, 2017, 02:47:51 pm
Just got in from work, in my wallet it still says status:enabled in both the My Sanctuaries and All Sanctuaries views.

Got txID f864a54729cff1c481ba3e1a275b5d4c9402560022739bffb9d7cc2bfbf35ad8-000 for block 9461 at 10/12/17 04:43:22 (a few minutes ago local time)

Ok cool, well Im learning more about the details of watchdog now.  It looks like after 7200 seconds, if watchman runs while your node is dead, it fails to create a signable gobject for POSE.  So, somewhere in the picture, it looks like your node would eventually fall behind in the payment queue if you werent the miner.  I think right now we can all get paid because our actual biblepayd instances are miners themselves, so they can always find the receiving address to append to the block plus we have more than enough blocks to go around.


Anyway, this is a very deep rabbit hole, the budgets and superblocks.  It looks like we actually need more code to be executed between proposal, budget and superblock creation (called a trigger).  Im merging in the trigger code now and Ill let everyone know what happens after I figure this out. 

Since we are on testnet, we only need 2 signing masternodes to approve the budget.  Since I have 2 I might be able to approve the budget, will update asap.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 12, 2017, 04:09:40 pm
(http://pool.biblepay.org/san/2.png)


*** YIPPI ****

We had our first testnet superblock!  I feel like Evan Duffield.    The Hex encoding finally broke through, oh but the convoluted feeling.

Alright now I need to regroup and figure out how we can add this to the testnet side of the pool.

Will be back tomorrow for more testing.

PS: If anyone wants to see the very first testnet superblock, do a showblock 10125.
I see that the miner gets the block subsidy (no sanctuary is paid the 50% on the superblock, lucky miner gets entire subsidy), and the 15% budget we allocate to IT/PR and Charity is paid in vout 2+ to the recipients of the passing voted budget.  So if we had a superblock every 100 blocks in prod for example (this is only an example), 15% would be held back from all 99 blocks (10% for charity, 5% for IT-PR) and on block 1000, that superblock would have the sum of the 15% allocated over the last 99 blocks included in the voted and approved budget, paying recipients 2+ (IE for the distinct count of approved campaigns) for those 100 blocks.....  Sweet....   

The website will allow us to create proposals in an easier manner, and enter receiving addresses.

Right now it will be a little convoluted to vote on things from the masternodes.  I forgot to mention an added benefit of the cold wallet.  If you plan on hosting say 5 masternodes, you can create one controller wallet and vote on an issue with all masternode keys at once with the command 'gobject vote-many objectid action vote'.  That will alleviate a lot of the pain once we work this template out.



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 13, 2017, 09:43:36 am
Maybe this is the problem? Was this exactly 500000 BBP or not? I'm confused with the fee. I used the command from the wiki instructions:

Code: [Select]
sendtoaddress <ESCROW_ADDRESS> 500000
But maybe I need to send it through the GUI and uncheck any fees?

Also, this is how the transaction appears in the wallet:

(https://i.imgur.com/oahSoFs.png)

And balance:

(https://i.imgur.com/HK1usCc.png)


Yeah, you sent it right.  There are a couple ways to double check it.  But first of all when you do it from the command line like that, you cant screw it up.

First, if you do a getrawtransaction b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2 1, and look at the vout1 you will see its exactly 500 grand.

Next if you type masternode outputs from the node that received the BBP, you will get the proper txid and vout to use for the masternode.conf.

Regarding the 'not a masternode' issue,from masternode status, you have to run that command from the masternode (not the controller wallet).  The masternode has to have the masternode=1 in the config file, along with its masternodeprivkey=XXX in the config.  Was all that set up?

Hopefully you got it all worked out.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 13, 2017, 09:48:34 am
So a little update for everyone- I spent last night adding the ability to the pool to add a governance object, added a proposal object, and the ability to list proposals.  Since the proposals have to go through phases (IE created, submitted, voted, budgeted, approved, queued for superblock, paid) I have to still add more code to the pool on the testnet side in order to get everyone on board and vote from testnet for the first proposal!  Then we can watch it go through the phases, and add some more code to be able to see the masternodes voting on it!  Kind of like dash-central does, when they see the progress of their proposals, and the entry into the budget superblock cycle.
I also have to ensure we move these proposals to history so we dont clutter up the screen.  We will probably have an active proposals list (those that you can vote on) respecting testnet and prod of course, and then the Historical proposals (those are the ones that have been Paid in a superblock already).

Just as a side note, I am going to create a wiki page for a Fundraiser for testnet, to pay our orphan recurring expenses as a Proposal - IE to simulate a real world use case for January 2018!  Then we can all vote on it here in testnet and see if it pays the keypair properly!

Exciting stuff!  You will be able to click on the row in the proposal to bring up the wiki page to see what you are voting as a masternode....


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 13, 2017, 04:54:23 pm
This is it. This was somehow missing from the wiki instructions, I added it now: http://wiki.biblepay.org/Create_Masternode
(I have no idea how all of you set it up and knew about that :) )

Now when I type masternode status, I get this:

Code: [Select]
{
  "vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
  "service": "35.196.88.202:40001",
  "status": "Not capable masternode: Masternode not in masternode list"
}

Which I reckon is normal and you just need to add this IP to some list, right? So there it is above. Thanks
Thanks, glad you added that.  I think we had that line in the config at one time and deleted it by accident.

I believe this error is coming from the wallets broadcast identifier, it stores the masternodes public ip, port, and vin (which is the txid and vout of the escrow) in order to validate the masternode when you come on line.

So, check to see if you have ''externalip=your_public_ip" in your base biblepay.conf file on the masternode itself (ie under masternode=1).  Try leaving off the colon and port # as I monkeyed with that and mine is working without the port number crrently at least for that setting.

Then restart the masternode, and wait until 'mnsync status' shows 999, then check the 'masternode status'  again and lets see if it works?


EDIT:  Also ensure your masternode.conf file in the /testnet3 directory of your controller wallet has the public IP And the colon and 40001 in it, and it matches, the public ip, and that you can reach the public ip from the controller wallet with:
telnet public_IP 40001


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on October 14, 2017, 02:22:33 am
Good news, I think I got a master node working!
(One gotchya was that with AWS (Amazon Web Services) I needed to add inbound rule for port 40001 in the security group of the EC2)

Love your updates to the Masternode guide Rob!
http://wiki.biblepay.org/Create_Masternode

===

Bad news, Im having trouble with Watchman:
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://github.com/biblepay/watchman

Im using Ubuntu 16.04

My watchman.conf:
Quote
# specify path to biblepay.conf or leave blank
# default is the same as BiblepayCore
#biblepay_conf=/home/ubuntu/.biblepaycore/biblepay.conf

# valid options are mainnet, testnet (default=mainnet)
#network=mainnet
network=testnet

# database connection details
db_name=database/watchman.db
db_driver=sqlite

~/.biblepaycore/watchman$ venv/bin/python bin/watchman.py
Code: [Select]
[error]: unable to open database file
Cannot connect to database. Please ensure database service is running and user access is properly configured in 'watchman.conf'.

Source Code:
https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/init.py#L46

https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/config.py#L82

https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/config.py#L37

===

~/.biblepaycore/watchman$ venv/bin/pip list

inflection (0.3.1)
peewee (2.8.3)
pip (9.0.1)
pkg-resources (0.0.0)
py (1.4.31)
pycodestyle (2.3.1)
pytest (3.0.1)
python-bitcoinrpc (1.0)
setuptools (36.6.0)
simplejson (3.8.2)
wheel (0.30.0)

===

So it seems like database file isnt getting created? Im not sure
Looks like peewee library handles the database stuff?

if driver == peewee.SqliteDatabase:
        db_conn = {}

db = driver(db_name, **db_conn)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 14, 2017, 09:35:44 am
Good news, I think I got a master node working!
(One gotchya was that with AWS (Amazon Web Services) I needed to add inbound rule for port 40001 in the security group of the EC2)

Love your updates to the Masternode guide Rob!
http://wiki.biblepay.org/Create_Masternode

===

Bad news, Im having trouble with Watchman:
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://github.com/biblepay/watchman

Im using Ubuntu 16.04

My watchman.conf:
~/.biblepaycore/watchman$ venv/bin/python bin/watchman.py
Code: [Select]
[error]: unable to open database file
Cannot connect to database. Please ensure database service is running and user access is properly configured in 'watchman.conf'.

Source Code:
https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/init.py#L46

https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/config.py#L82

https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/config.py#L37

===

~/.biblepaycore/watchman$ venv/bin/pip list

inflection (0.3.1)
peewee (2.8.3)
pip (9.0.1)
pkg-resources (0.0.0)
py (1.4.31)
wheel (0.30.0)

===

So it seems like database file isnt getting created? Im not sure
Looks like peewee library handles the database stuff?

if driver == peewee.SqliteDatabase:
        db_conn = {}

db = driver(db_name, **db_conn)

Oh man thats great!  You almost have it working.  Yeah, on the watchman, I will add those instructions to the create_masternode guide in a few minutes for everyone else.

So lets start with a couple basic things to see if the problem reveals itself.

Im no python guy, but during the time that I was debugging the first superblock I had to figure out how to turn peewee logging on and I was successfully able to see the watchman debug output and figure out where the system was breaking.  So step 1 that might help a little is turning on the logging, and then try to run the venv/bin/python watchman.py again, here is how I turned on logging:

First cd into the watchman directory
Then execute the python interpreter like this:

venv/bin/python

Then you will see the python interpreter command line:
Python interpreter>>

Type:

import os;
os.env["WATCHMAN_DEBUG"]="1";
quit()


Then rerun venv/bin/python watchman.py first to see if it reveals anything.
Btw, I think you already modified your config file properly as it looks good.
The database file itself should have been downloaded to the watchman directory - its called "Watchman".  If you ls -l, and cat the file it should have some tables in it.  Note the case is "Watchman" in this case.

To check to see what is in the database, if you have not gotten further try this:

sudo apt-get install sqlite3
sqlite3 Watchman
sqlite>
select * from votes;
.table <enter>

See if the .table command lists out all the governance object tables?  Or if possibly the "Watchman" file does not even exist in the directory?

Im not sure if you have access to any other machines, but it would also be good to know if the behavior is different on another machine (IE Watchman gets created on ubuntu, but not at AWS).

We will have to see which step it fails to create the database file in.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 14, 2017, 12:48:56 pm
Alright everyone, I believe we are now at the point where we need to perform end-to-end sanctuary testing!

Lets try to go through this process from start-finish to see what needs improvements  :'(

So first, log in to pool.biblepay.org and click Network: Testnet.  If you are not in testnet mode, the proposals lists will be empty.

Next click Governance | Proposal List.  You will see the list of Active proposals at the top (those not funded yet that need voted on) and then in the Funded List you will see those proposals that are already inside superblocks and paid.
NOTE: I will be adding a chart soon so we can see a graphical view of the proximity to funding per row one proposal is generating in popularity.

We need to simulate: Keeping compassion as a charity, Paying a single invoice, Paying multiple invoices in a superblock, Shooting down a proposal, and watching a proposal get paid (included in a superblock), verifying the budget, test inability to exceed the budget, and review a historical expense.

First lets test a dry run of the theoretical monthly recurring expense for compassion.  I added a new proposal and it is ready to be voted on, for Octobers recurring orphan sponsorships (39,900 BBP).  Click on Proposal List.  Note the gobjectID in the second row of each item row (that is the Detail row).  Copy the gobjectID to the clipboard (note - Clicking on the first line of each row allows you to View the proposal), so you need to double click the gobject id (62a9c8afaf2af86f3820d6d30a93b4f84b29927b66c88badf8ad9699a48e20a6) from the second row, (the row that says the Proposal Name hyphen the gobjectid).  To vote on this for funding from your sanctuary issue this command:

Code: [Select]
gobject vote-many 62a9c8afaf2af86f3820d6d30a93b4f84b29927b66c88badf8ad9699a48e20a6 funding yes


The pool will actually update the row eventually with voting information also.

After the supermajority votes on it, the pool will create a budget item automatically that "fits" as many proposals as possible into a superblock (IE it will try to create a superblock for us), the pool has no power to vote, all it can do is suggest to the sanctuary network that "4 approved proposals can fit in superblock Y" and Y must be an upcoming superblock with at least enough lead time to be voted on (this is called the budget maturity period).  We need to test that also.

So please go ahead and vote on this proposal, and we will watch to see if it moves through the phases.

Also, I wanted to mention, for the very first Discussion URL, I used the wiki page just to get started.  But, technically, we need to use a Forum topic for this purpose so that other Biblepayers and Sanctuaries can discuss the validity in an open forum of the actual item.  For example, if someone submits a proposal to place a BiblePay ATM with a "medicianal weed" dispenser in it, the community should stand up and say: Wait I thought we were a Christian community isnt this going to tarnish our image, and coax the sanctuaries to vote it down.

Initiative II:

Id also like to ask someone here, who has a running sanctuary, to go ahead and create a Mock up proposal with a real testnet discussion URL, one that we can vote on, so we can test the "multiple proposals in one budget and in one superblock" issue.  Who is up for it?  Click on Proposals| Add.
Create a discussion URL on Forum.biblepay.org in the Testnet Forum, as a new Topic.  Ensure you can post to it (test it).  Use that as the discussion URL.
Enter an amount below 10000 BBP as the "amount" because the superblock budget is only 72000 on testnet and the orphan budget is already at 39,900.
Add the Proposal and verify it exists and notify us so that we can discuss and vote on it. 

And finally, please, someone who wants to make a really negative and tacky proposal, go ahead and make one, and let us know, one that we deliberately want to shoot down so that it misses the budget.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 14, 2017, 06:03:23 pm
Is there a way to see more detail on what the proposal is?  Because (and yes, I understand we're testing), right now, I see a proposal entitled "Oct 2017 recurring orphan expense due" and a id, but there is no way to really tell what we're voting on.  Or is that coming and I'm jumping the gun?

Well on a side note, I am working on an advanced feature now that will let you pull up commands to let you vote on a budget or a proposal, but Im kind of getting ahead of myself here, the current version in Pool-testnet right now please check this out:

If you single left click on the First row of each Proposal, you can view the Forum detail.  To vote on it, copy the Second rows gobject ID to clipboard and vote.  Let me know if you vote, because Ive done something very convoluted to the first proposal.  I voted on it, voted on the budget, became the supermajority (because I had 3 cool sanctuaries running) got it in the superblock and paid and then pulled it back out and re-instantiated it - I am trying to see what happens if us guys vote on something again that was already paid.

Anyway, since you are mod, if you want to create that other one we need, you should then be able to left click it and see your forum URL discussion also.

You should see an entire web page for the recurring orphan expense with the invoice in it.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 14, 2017, 06:19:42 pm
No problem, family first.  I gotta do some other things. But I did vote and the proposal did show when I left clicked it.
Wait, I think its fixed.  Gotta step out, but go ahead and left click from the weblist from the one that is not funded and you should see a Wiki page pop up.

When you create your forum link and a new proposal, once you navigate to the list, it should also pop up- we will probably need to make that open in a new window, otherwise forum javascript will probably be broken (IE it may need a whole dedicated discussion page).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 15, 2017, 03:44:31 am
I've had a busy week, but I think I've finally got a masternode working  :D

I didn't set it up on a vultr server, but run it within my own network. So now I have two computers running from my home, one having the controller wallet and the other having the sanctuary wallet.

I do still have a few questions/remarks.
In the guide it says:

Quote
Type 'masternode outputs' (Record the output of this command in notepad as ESCROW TXID and ESCROW VOUT).

 What I got was:

Code: [Select]
{
  "d7701a68ef4a7af4f066499477b935bfccf5efaacf28149cdf8b5316c1daa626": "1",
  "fd5cb3ef632fb25a40665d1b4da0c1cd992c4f3d99ef38ce1ddf725ecfe53836": "0"
}

Then later on the guide says:

Quote
Find masternode.conf and add the following line to it: (*** NOTE: For TestNet, you must modify testnet3\masternode.conf ***): [SANCTUARY_ALIAS] SPACE [SANCTUARY_PUBLIC_IP:40001] SPACE [SANCTUARY_PRIVATE_KEY] SPACE [SANCTUARY_TXID] SPACE [SANCTUARY_VOUT]

But I didn't know where to find the 'SANCTUARY_TXID' and 'SANCTUARY_VOUT'. Am I right in saying that these two are the last two I got when typing 'masternode outputs' on my controller wallet (thus in my case 'SANCTUARY_TXID'='fd5cb3ef632fb25a40665d1b4da0c1cd992c4f3d99ef38ce1ddf725ecfe53836' and 'SANCTUARY_VOUT'='0'?
That's the way I configured it a least, and it seems to be working.

When I type 'masternode status' on my sanctuary wallet, I get:

Code: [Select]
{
  "vin": "CTxIn(COutPoint(fd5cb3ef632fb25a40665d1b4da0c1cd992c4f3d99ef38ce1ddf725ecfe53836, 0), scriptSig=)",
  "service": "84.29.208.33:40001",
  "payee": "yahMsXVAioaFT9EXfna78sqoYZh5y4NMfP",
  "status": "Masternode successfully started"
}

While typing this, I got my first masternode-payment, so I guess it's working  8)
Next step is getting wachtman up and running.

One last question: do I also need to keep the controller wallet online? I don't think so, based on the information I've read, but I'm wondering how it works...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 15, 2017, 04:10:25 am
@togoshigekata: I'm having the same problem with watchman. Dit you solve this issue?

Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.

STUCK: What am I doing wrong here?
-> In this case I would go to the masternode and edit the biblepay.conf, and ensure rpcallowip=127.0.0.1 is set.
Also check to make sure watchman.conf has testnet uncommented and prod commented.

rpcallowip=127.0.0.1 is set in the biblepay.conf file, and this is my watchman.conf:

Code: [Select]
# specify path to biblepay.conf or leave blank
# default is the same as BiblepayCore
#biblepay_conf=/home/rob/.biblepaycore/biblepay.conf

# valid options are mainnet, testnet (default=mainnet)
#network=mainnet
network=testnet

# database connection details
db_name=database/watchman.db
db_driver=sqlite

venv/bin/python bin/watchman.py

I do work from the GUI. Might this be the problem?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 08:40:59 am
On a side note, on my guinea pig test last night where I took a funded-paid gobject, and tried to revote it into a new superblock, it was rejected.  So thats great to know, because that means one cannot pull a fast one on the community and try to slip their proposal into two budgets and have the sanctuaries accidentally pay it twice (especially thinking they didnt vote it in properly in the last budget-superblock).

However there is one circumstance I can think of that will happen in prod that we have to make a distinction on.  If a proposal is submitted, and everyone likes it and approves it, but everyone goes away after proposal is approved, and forgets to vote on the budget, then it fails to to be created in the next superblock, then it is not funded, then we will auto-create a new budget, and that allows us to continue to vote for it in the *next* superblock.  In prod that would be rare, as we only have one per month, so dont worry too much about this.  It should happen in testnet however quite a bit with these hourly superblocks.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 08:44:51 am
I've had a busy week, but I think I've finally got a masternode working  :D

I didn't set it up on a vultr server, but run it within my own network. So now I have two computers running from my home, one having the controller wallet and the other having the sanctuary wallet.

I do still have a few questions/remarks.
In the guide it says:

 What I got was:

Code: [Select]
{
  "d7701a68ef4a7af4f066499477b935bfccf5efaacf28149cdf8b5316c1daa626": "1",
  "fd5cb3ef632fb25a40665d1b4da0c1cd992c4f3d99ef38ce1ddf725ecfe53836": "0"
}

Then later on the guide says:

But I didn't know where to find the 'SANCTUARY_TXID' and 'SANCTUARY_VOUT'. Am I right in saying that these two are the last two I got when typing 'masternode outputs' on my controller wallet (thus in my case 'SANCTUARY_TXID'='fd5cb3ef632fb25a40665d1b4da0c1cd992c4f3d99ef38ce1ddf725ecfe53836' and 'SANCTUARY_VOUT'='0'?
That's the way I configured it a least, and it seems to be working.

When I type 'masternode status' on my sanctuary wallet, I get:

Code: [Select]
{
  "vin": "CTxIn(COutPoint(fd5cb3ef632fb25a40665d1b4da0c1cd992c4f3d99ef38ce1ddf725ecfe53836, 0), scriptSig=)",
  "service": "84.29.208.33:40001",
  "payee": "yahMsXVAioaFT9EXfna78sqoYZh5y4NMfP",
  "status": "Masternode successfully started"
}

While typing this, I got my first masternode-payment, so I guess it's working  8)
Next step is getting wachtman up and running.

One last question: do I also need to keep the controller wallet online? I don't think so, based on the information I've read, but I'm wondering how it works...

That is great dude, glad to hear it.

Yeah, in masternode outputs, it prints the TXID of the collateral, colon then the vout (locationid) of the collateral.  So Ill modify the FAQ to make it clearer that what value is which one.

Once your masternode is started you dont have to keep the controller wallet online.  When in prod, we will have to ocasionally look at the masternode list and if it says "Restart Required"thats when you have to bring the controller back up and do a restart on the cold sanctuary.  Ill take a look at the code to ensure this is not going to be a nuisance where its down if it misses one ping.  Maybe we relax it a little so its easier to manage these for the first year (IE requires a hard down for one hour instead of 5 minutes) as I noticed out of my 3 sanctuaries I left them running and one of them already requires restart.

Ill add this to the faq also.

Btw guys I added the watchman to the create_masternode wiki.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 08:50:42 am
@togoshigekata: I'm having the same problem with watchman. Dit you solve this issue?

rpcallowip=127.0.0.1 is set in the biblepay.conf file, and this is my watchman.conf:

Code: [Select]
# specify path to biblepay.conf or leave blank
# default is the same as BiblepayCore
#biblepay_conf=/home/rob/.biblepaycore/biblepay.conf

# valid options are mainnet, testnet (default=mainnet)
#network=mainnet
network=testnet

# database connection details
db_name=database/watchman.db
db_driver=sqlite

venv/bin/python bin/watchman.py

I do work from the GUI. Might this be the problem?

Sorry, I dont understand what is broken, but, if you ran the
venv/bin/python bin/watchman.py and did not receive an error I believe you are actually OK with watchman.   
What you can do is vote on our new proposal that is coming out in one hour and then go into this

sqlite3 Watchman
select * from vote;

And just see if your vote went in from your masternode then you will know for sure your watchman is working.

Also if you receive WatchdogExpired from the GUI list of Sanctuaries in a few hours, watchman is down.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 09:31:58 am
Alright so I just deployed a couple new governance features to the pool.

Now you can go to proposals, and when you click View Proposal, it opens the Discussion in a new Tab on the browser.  The idea is we create proposals with Forum URLs, let everyone discuss it, and the URL for the discussion stays on the proposal forever.

I updated the Orphan proposal that still needs voted on today with the new Forum URL, so lets pretend its real and vote on it now.

I added some more features to make voting more intuitive.  The proposal has to go through the initial voting stage (that is it either gets voted for funding or gets voted away and dies).  During this phase internally it has a gobject id.  To make this easier, when you right click on a proposal that is not fully voted to a budget, you can now either copy the proposal ID to the clipboard or copy the Vote command to the clipboard.  It appears only IE lets me write to your clipboard, so if you are on Chrome, you will have to copy the command from the dialog into your clipboard.  I think this will work on firefox, let me know.

So another words to vote on the orphan proposal, right click on it and copy the proposal vote command to the clipboard then vote on it from your masternode. Let me know that it works.

Then once the system finds a supermajority voted on it, it will create a budget item for it. You will also have to vote on the budget once per month.
When you right click the proposal and click Vote on Budget, it will copy the Budget Tx ID and voting command to the clipboard.  Later today we can use that to vote on the budget.

We still need someone to create another real proposal (a good one) and some one to create a tacky one.

Got to head to church have fun.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 15, 2017, 12:32:09 pm
gobject vote-many e33c9a0e6a010a9515bf20868ac6ede5efc1747f7e771a4e82e12536d356a9a4 funding yes

Code: [Select]
{
  "overall": "Voted successfully 0 time(s) and failed 0 time(s).",
  "detail": {
  }
}

What am I doing wrong here?

I get the same...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 15, 2017, 12:42:58 pm
Sorry, I dont understand what is broken, but, if you ran the
venv/bin/python bin/watchman.py and did not receive an error I believe you are actually OK with watchman.   
What you can do is vote on our new proposal that is coming out in one hour and then go into this

sqlite3 Watchman
select * from vote;

And just see if your vote went in from your masternode then you will know for sure your watchman is working.

Also if you receive WatchdogExpired from the GUI list of Sanctuaries in a few hours, watchman is down.

Thanks! Sadly I get the 'Cannot connect to biblepayd' error at the point where I type the command 'venv/bin/python bin/watchman.py'.
So it seems to think the wallet is not running while it actually is. I got no errors typing the other commands.

This might also explain why I'm not able to vote... (see my previous post).
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on October 15, 2017, 02:46:29 pm
I think I found a solution to watchman

On Sanctuary Wallet (remote linux machine), I added a line to ~/.biblepaycore/biblepay.conf
rpcport=9998

I got this port number from here:
https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/biblepay_config.py#L37

And I re-ran the Wallet
~/.biblepaycore/watchman$ venv/bin/python bin/watchman.py
biblepayd not synced with network! Awaiting full sync before running watchman.

Never received this message before!, Waited for sync, ran again and got no error, I was always getting errors!, but I also got no output, SUCCESS!?

QUESTION: How do I check to make sure watchman is working?

Another slight change I made, not sure if it was important, I manually created the /database folder inside the /watchman folder

===

I got 1 error when running the watchman tests though

~/.biblepaycore/watchman$ ./venv/bin/py.test ./test
====================================== test session starts ======================================
platform linux2 -- Python 2.7.12, pytest-3.0.1, py-1.4.31, pluggy-0.3.1
rootdir: /home/ubuntu/.biblepaycore/watchman, inifile:
collected 20 items

test/integration/test_jsonrpc.py F
test/unit/test_biblepay_config.py .
test/unit/test_biblepay_things.py .....
test/unit/test_biblepayd_data_shims.py ..
test/unit/test_models.py ..
test/unit/test_submit_command.py .
test/unit/models/test_proposals.py ...
test/unit/models/test_superblocks.py .....

=========================================== FAILURES ============================================
________________________________________ test_biblepayd _________________________________________

    def test_biblepayd():
        config_text = BiblepayConfig.slurp_config_file(config.biblepay_conf)
        network = 'mainnet'
        is_testnet = False
        genesis_hash = u'00000ffd590b1485b3caadc19b22e6379c733355108f107a430458cdf3407ab6'
        for line in config_text.split("\n"):
            if line.startswith('testnet=1'):
                network = 'testnet'
                is_testnet = True
                genesis_hash = u'00000bafbc94add76cb75e2ec92894837288a481e5c005f6563d91623bf8bc2c                        '

        creds = BiblepayConfig.get_rpc_creds(config_text, network)
        biblepayd = BiblepayDaemon(**creds)
        assert biblepayd.rpc_command is not None

        assert hasattr(biblepayd, 'rpc_connection')

        # Biblepay testnet block 0 hash == 00000bafbc94add76cb75e2ec92894837288a481e5c005f6563d91                        623bf8bc2c
        # test commands without arguments
        info = biblepayd.rpc_command('getinfo')
        info_keys = [
            'blocks',
            'connections',
            'difficulty',
            'errors',
            'protocolversion',
            'proxy',
            'testnet',
            'timeoffset',
            'version',
        ]
        for key in info_keys:
            assert key in info
        assert info['testnet'] is is_testnet

        # test commands with args
>       assert biblepayd.rpc_command('getblockhash', 0) == genesis_hash
E       assert '122f423f0912...ae2b957d1ac10' == '00000bafbc94a...d91623bf8bc2c'
E         - 122f423f0912850a871c58f1533dd80be62154bb0c56dfb8cb9ae2b957d1ac10
E         + 00000bafbc94add76cb75e2ec92894837288a481e5c005f6563d91623bf8bc2c

test/integration/test_jsonrpc.py:51: AssertionError
============================== 1 failed, 19 passed in 0.50 seconds ==============================

Only 1 test failed out of 20
and it looks like its just a difference in hash numbers for block 0?
for my testnet machines getblockhash 0 returns:
122f423f0912850a871c58f1533dd80be62154bb0c56dfb8cb9ae2b957d1ac10

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 15, 2017, 03:18:58 pm
can i run masternode on windows? any help with this? no all using linux VPS
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 03:58:01 pm
can i run masternode on windows? any help with this? no all using linux VPS
No. PoSE does not run on windows.

You can hack Watchman to run on windows, but you would need to know python and you would be spearheading the project with absolutely no support.  At the very least, you should get your masternode running on linux first, then you could become  a windows hacker (otherwise I doubt you would have a chance at succeeding).

However,  if you did succeed I would be interested in running a windows sanctuary on one of my extra servers.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 04:06:22 pm
I think I found a solution to watchman

On Sanctuary Wallet (remote linux machine), I added a line to ~/.biblepaycore/biblepay.conf
rpcport=9998

I got this port number from here:
https://github.com/biblepay/watchman/blob/c6f4cdc831b45019b1f7b3b6ce99100b5fa7086f/lib/biblepay_config.py#L37

And I re-ran the Wallet
~/.biblepaycore/watchman$ venv/bin/python bin/watchman.py
biblepayd not synced with network! Awaiting full sync before running watchman.

Never received this message before!, Waited for sync, ran again and got no error, I was always getting errors!, but I also got no output, SUCCESS!?

QUESTION: How do I check to make sure watchman is working?

Another slight change I made, not sure if it was important, I manually created the /database folder inside the /watchman folder

===

I got 1 error when running the watchman tests though

~/.biblepaycore/watchman$ ./venv/bin/py.test ./test
====================================== test session starts ======================================
platform linux2 -- Python 2.7.12, pytest-3.0.1, py-1.4.31, pluggy-0.3.1
rootdir: /home/ubuntu/.biblepaycore/watchman, inifile:
collected 20 items

test/integration/test_jsonrpc.py F
test/unit/test_biblepay_config.py .
test/unit/test_biblepay_things.py .....
test/unit/test_biblepayd_data_shims.py ..
test/unit/test_models.py ..
test/unit/test_submit_command.py .
test/unit/models/test_proposals.py ...
test/unit/models/test_superblocks.py .....

=========================================== FAILURES ============================================
________________________________________ test_biblepayd _________________________________________

    def test_biblepayd():
        config_text = BiblepayConfig.slurp_config_file(config.biblepay_conf)
        network = 'mainnet'
        is_testnet = False
        genesis_hash = u'00000ffd590b1485b3caadc19b22e6379c733355108f107a430458cdf3407ab6'
        for line in config_text.split("\n"):
            if line.startswith('testnet=1'):
                network = 'testnet'
                is_testnet = True
                genesis_hash = u'00000bafbc94add76cb75e2ec92894837288a481e5c005f6563d91623bf8bc2c                        '

        creds = BiblepayConfig.get_rpc_creds(config_text, network)
        biblepayd = BiblepayDaemon(**creds)
        assert biblepayd.rpc_command is not None

        assert hasattr(biblepayd, 'rpc_connection')

        # Biblepay testnet block 0 hash == 00000bafbc94add76cb75e2ec92894837288a481e5c005f6563d91                        623bf8bc2c
        # test commands without arguments
        info = biblepayd.rpc_command('getinfo')
        info_keys = [
            'blocks',
            'connections',
            'difficulty',
            'errors',
            'protocolversion',
            'proxy',
            'testnet',
            'timeoffset',
            'version',
        ]
        for key in info_keys:
            assert key in info
        assert info['testnet'] is is_testnet

        # test commands with args
>       assert biblepayd.rpc_command('getblockhash', 0) == genesis_hash
E       assert '122f423f0912...ae2b957d1ac10' == '00000bafbc94a...d91623bf8bc2c'
E         - 122f423f0912850a871c58f1533dd80be62154bb0c56dfb8cb9ae2b957d1ac10
E         + 00000bafbc94add76cb75e2ec92894837288a481e5c005f6563d91623bf8bc2c

test/integration/test_jsonrpc.py:51: AssertionError
============================== 1 failed, 19 passed in 0.50 seconds ==============================

Only 1 test failed out of 20
and it looks like its just a difference in hash numbers for block 0?
for my testnet machines getblockhash 0 returns:
122f423f0912850a871c58f1533dd80be62154bb0c56dfb8cb9ae2b957d1ac10


Good hacking man, so I think all it was in your case was the rpcport was not set.  RPCPort is not really hardcoded to be 9998, it is picked by you and just cant be the p2p port.  For example, rpcport cannot be 40001 or 40000.  What this is for, is to let your sanctuary be an RPC server.  Thats so Watchman can connect to it.  I see the guide does not include the Port!   I see mine is set in the high 4000s on testnet and my watchman.conf has no port number in it and watchman finds it.  Oh well you got it working.

But moving on to the genesis, Yeah, I think I have the gensis hash in the test, good find.  I need to update that to our genesis hash and all tests should succeed :).

So anyway after you vote on the first governance vote, you can go in and select * from votes, and you should see table data.  Actually, if you see anything in select * from proposals then you know its working.

Out of curiousity if you get a chance why dont you leave rpcuser and rpcpassword in your cold sanctuary set, and see if it works with the "rpcport=" commented out?  You can put a # in front of it.  This way we know if the guide needs modified.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 04:20:59 pm
I get the same...

For JaapGVK & InBlue:

Checking the gobject:
gobject vote-many e33c9a0e6a010a9515bf20868ac6ede5efc1747f7e771a4e82e12536d356a9a4 funding yes
The gobject is valid and I am able to vote from my masternodes on this item.

To troubleshoot check the following:

- masternode status (ensure it says Started) from the sanctuary wallet
- Vote from the Controller wallet if you run cold sanctuaries, vote from a hot wallet if you run a hot sanctuary
- mnsync status from the sanctuary wallet (ensure it is 999)

Next you can type 'gobject get gobjectid' if you did vote successfully to see the vote take effect.


The web site should now automatically pick up vote changes in the proposal list.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 15, 2017, 05:03:21 pm
No. PoSE does not run on windows.

You can hack Watchman to run on windows, but you would need to know python and you would be spearheading the project with absolutely no support.  At the very least, you should get your masternode running on linux first, then you could become  a windows hacker (otherwise I doubt you would have a chance at succeeding).

However,  if you did succeed I would be interested in running a windows sanctuary on one of my extra servers.
you want to run masternode without windows support?  :o it wont be good idea ... price for MNode will be how much?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 15, 2017, 05:07:25 pm

- Vote from the Controller wallet if you run cold sanctuaries, vote from a hot wallet if you run a hot sanctuary

Okay. I found my problem ;D I was voting from the sanctuary walled instead of the controller wallet. Good to know.

All seems well now:
Code: [Select]
{
  "overall": "Voted successfully 1 time(s) and failed 0 time(s).",
  "detail": {
    "MN1": {
      "result": "success"
    }
  }
}

Quote
Next you can type 'gobject get gobjectid' if you did vote successfully to see the vote take effect.

The web site should now automatically pick up vote changes in the proposal list.

I did a gobject get and my vote shows up:

Code: [Select]
"FundingResult": {
    "AbsoluteYesCount": 3,
    "YesCount": 3,
    "NoCount": 0,
    "AbstainCount": 0

The pool hasn't updated my vote as of yet, but I'm guessing that won't take long.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 06:00:18 pm
Lol, I did the same mistake as jaapgvk. :) All good, now my vote is in too:

Yeah, I see the 5 votes in my cold sanctuary now.
Why is the pool not showing 5... Hmm, let me debug the pool.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 06:07:23 pm
Yeah, I see the 5 votes in my cold sanctuary now.
Why is the pool not showing 5... Hmm, let me debug the pool.

Ok, not sure if I had a bug in there or not, because its working now, anyway, it looks like the system automtically created a budget for us now that a superblock is around the corner and the proposals are approved and fit within the superblock.

So now we all need to vote on the budget.

Please Right click on the unfunded proposal and click Copy Vote on Budget command to clipboard, then use it to vote from the masternode.

If it works, it will be funded at the height proposed in the proposal.

Im going to add a Budget object to the pool soon also, so we can see all 3 phases:  Proposal, Current Budget, and Funded Proposals.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 06:16:37 pm
you want to run masternode without windows support?  :o it wont be good idea ... price for MNode will be how much?

No masternodes exist anywhere for windows... they are always linux... (IE, POSE (Proof Of Service) is a linux thing in python).

However in the vein of this idea, West and I have been discussing the *potential* of a higher priced sanctuary (like 10 million BBP) that would do More than a regular sanctuary and *may* end up running on windows.  The idea here is this supersanctuary might do something like run biblepaycentral in a decentralized manner.  Those nodes would get 10* the financial reward (which is the same as the smaller nodes) but would be required to run IIS and windows server, and would run a web site for us.  (I think I want to be one).  So when we work on that, I will port watchman on the wall to c# so it all works, but this is a long term project, not something going to go live by Christmas.

EDIT:
The proposed price is "approx" 1 million BBP (Im shooting for roughly a $1000 USD cost for a node around Christmas).  If we have a super sanctuary it would be 10 million BBP and financial reward 10* the amount.  I am currently checking out the ability for voting rights with that setup.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 06:31:10 pm
Looks like we didnt vote in time on the budget for it to make the superblock.

In Prod this wont be a problem since it is once a month.  In testnet its every 25 blocks.  What Ill do is modify the pool to add 25 blocks to the future superblock height to give us more time.

Now we have to wait for N+4 (4 blocks past the next superblock) for the pool to create a new budget to be voted on.  Lets wait until the height dissappears (from the unfunded row).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 15, 2017, 07:26:57 pm
Ok pool has create a budget, go ahead and vote on the budget by right clicking the proposal and left click Copy vote for budget command to clipboard;execute in sanctuary.

In the future we will have a separate list for budgets.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on October 16, 2017, 01:00:02 am
I think all the masternodes went down?
My controller and sanctuary wallets are on different blocks now >.>
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 16, 2017, 02:10:38 am
I think all the masternodes went down?
My controller and sanctuary wallets are on different blocks now >.>

I guess so. Mine seems to be down also...

Also, when I click 'Copy vote for budget' a 'copied to clipboard' window pops up, but it just says 'Unable to locate Budget.'
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 16, 2017, 07:32:39 am
I guess so. Mine seems to be down also...

Also, when I click 'Copy vote for budget' a 'copied to clipboard' window pops up, but it just says 'Unable to locate Budget.'

1) What gobjectid are you right clicking on so I can reproduce? (Just first 5 characters is fine).  Dont use the fake ones #1-5, I created those just for the chart im writing.  Still need two people to create the good one and fake one.

2) Regarding going down, I dont think we actually went down, I think either some masternodes banned each other or maybe watchdog isnt working on those nodes.  First, please each individual sanctuary, test your watchdog to see if its working by doing the select * from votes, just to ensure watchman is actually working. 

Next, delete your banlist.dat file.

I am looking at my masternodes and Im still synced and dont have anyone banned.  So Im really wondering whats wrong, I dont see a problem where we are banning each other.  Im leaning towards the masternodes exceeded the threshhold when told "restart required" and never restarted.

Right now I see 3 enabled - lets see if we are all on the same fork?

getblockhash 13680:
c3ce1181965b9652866a35a585dccdfdb047a8b20dc694fc2958ff51d55ec189
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 16, 2017, 09:58:01 am
1) What gobjectid are you right clicking on so I can reproduce? (Just first 5 characters is fine).  Dont use the fake ones #1-5, I created those just for the chart im writing.  Still need two people to create the good one and fake one.

2) Regarding going down, I dont think we actually went down, I think either some masternodes banned each other or maybe watchdog isnt working on those nodes.  First, please each individual sanctuary, test your watchdog to see if its working by doing the select * from votes, just to ensure watchman is actually working. 

Next, delete your banlist.dat file.

I am looking at my masternodes and Im still synced and dont have anyone banned.  So Im really wondering whats wrong, I dont see a problem where we are banning each other.  Im leaning towards the masternodes exceeded the threshhold when told "restart required" and never restarted.

Right now I see 3 enabled - lets see if we are all on the same fork?

getblockhash 13680:
c3ce1181965b9652866a35a585dccdfdb047a8b20dc694fc2958ff51d55ec189

About 1: I clicked the fake ones, because they were the only ones that showed options when right-clicking them. The one with the proposal just shows a thin blank box. I'm using chrome btw, and didn't test with another browser.
I would try to create the good and bad proposal, but I'm still struggling with the basics as of now.

About 2: It just seems a coïncedence. My wallet crashed last night, maybe because I was testing to mine and simultaneously be a masternode. All seems fine now. Sadly I can't getblockhash right now, since I don't have access to that computer right now.

Could you maybe explain in more detail what you mean with "select * from votes"? You also told me something similar some time ago, but I don't exactly understand what I should do. I do still get sanctuary payments, so I'm guessing watchman is running, but I don't know how to test it...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 16, 2017, 12:06:56 pm
About 1: I clicked the fake ones, because they were the only ones that showed options when right-clicking them. The one with the proposal just shows a thin blank box. I'm using chrome btw, and didn't test with another browser.
I would try to create the good and bad proposal, but I'm still struggling with the basics as of now.

About 2: It just seems a coïncedence. My wallet crashed last night, maybe because I was testing to mine and simultaneously be a masternode. All seems fine now. Sadly I can't getblockhash right now, since I don't have access to that computer right now.

Could you maybe explain in more detail what you mean with "select * from votes"? You also told me something similar some time ago, but I don't exactly understand what I should do. I do still get sanctuary payments, so I'm guessing watchman is running, but I don't know how to test it...
Yeah, the proposals in testnet are not in a state that I expected, I had to recreate the data a couple times today to get the chart working, but starting now, I just recreated the Orphan proposal (the only non-voted non-fake proposal in the list).  Its waiting for the pool to submit it to the network.  Once you see Submitted DateTime set, go ahead vote on it everyone.

On the checking on the watchman, just type:
sqlite3 Watchman
.table
select * from votes;

See if anything is in there, if there is, its definitely working as you cannot receive 1 record if it is not working.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 16, 2017, 12:09:02 pm
I just added Budgets to the pool; now we have Proposals, Budgets and Funded Proposals.

Ill explain budgets once we get a few things in the budget, right now, just vote on the Orphan proposal once it has a "SubmittedDateTime" populated.

Also, still need someone to create a tacky proposal and a good proposal for us to vote on - I want these to be done on machines other than mine so I can simulate the autonomous sanctuary network.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 16, 2017, 04:27:10 pm
I just added Budgets to the pool; now we have Proposals, Budgets and Funded Proposals.

Ill explain budgets once we get a few things in the budget, right now, just vote on the Orphan proposal once it has a "SubmittedDateTime" populated.

Also, still need someone to create a tacky proposal and a good proposal for us to vote on - I want these to be done on machines other than mine so I can simulate the autonomous sanctuary network.

I voted on the Orphan proposal, and as far as I can tell it went fine:

Code: [Select]
{
  "overall": "Voted successfully 1 time(s) and failed 0 time(s).",
  "detail": {
    "MN1": {
      "result": "success"
    }
  }
}

I tried to create a 'tacky proposal'. I set it up on the pool side, but I don't know what step to take next. Do I have to do anything with my masternode?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 16, 2017, 04:28:40 pm
I voted on the Orphan proposal, and as far as I can tell it went fine:

Code: [Select]
{
  "overall": "Voted successfully 1 time(s) and failed 0 time(s).",
  "detail": {
    "MN1": {
      "result": "success"
    }
  }
}

I tried to create a 'tacky proposal'. I set it up on the pool side, but I don't know what step to take next. Do I have to do anything with my masternode?

Hi bud,

Great, on the vote!  So on tacky, I dont know if you can create topics on this forum, can you just try and we can learn together? Try to create a forum topic and put a blurb in there about how you are spending the money and make it tacky.  Then use that as the URL for the new proposal.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 16, 2017, 04:47:34 pm
Hi bud,

Great, on the vote!  So on tacky, I dont know if you can create topics on this forum, can you just try and we can learn together? Try to create a forum topic and put a blurb in there about how you are spending the money and make it tacky.  Then use that as the URL for the new proposal.

I already did that, haha! I can create topics :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 16, 2017, 05:29:32 pm
I already did that, haha! I can create topics :)

Ok, cool, I added a post to the topic and I see the "buy heroin" proposal in the list - LOL.  Yeah, the reason you cant vote No on it yet is the pool has not created a gobject for it yet.  The underlying cause, I think, is each masternode can only create one proposal per superblock cycle. 

I have some company coming over so I dont think I can look now, but in the night, if you see a Submitted=1 and submitteddatetime, then you can vote no on it.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 16, 2017, 06:56:19 pm
Ok, cool, I added a post to the topic and I see the "buy heroin" proposal in the list - LOL.  Yeah, the reason you cant vote No on it yet is the pool has not created a gobject for it yet.  The underlying cause, I think, is each masternode can only create one proposal per superblock cycle. 

I have some company coming over so I dont think I can look now, but in the night, if you see a Submitted=1 and submitteddatetime, then you can vote no on it.

You're right, the pool created a gobject and I tried to vote 'no'. Sadly, I got this:

Code: [Select]
{
  "overall": "Voted successfully 0 time(s) and failed 1 time(s).",
  "detail": {
    "MN1": {
      "result": "failed",
      "errorMessage": "GOVERNANCE_EXCEPTION_WARNING:CGovernanceManager::ProcessVote -- Unknown parent object , MN outpoint = fd5cb3ef632fb25a40665d1b4da0c1cd992c4f3d99ef38ce1ddf725ecfe53836-0, governance object hash = d418d2c8860147caa5ce3d62576a804384e830d67b8adf465d8f0b7ae87609f0\n"
    }
  }
}

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 16, 2017, 10:25:31 pm
You're right, the pool created a gobject and I tried to vote 'no'. Sadly, I got this:

Code: [Select]
{
  "overall": "Voted successfully 0 time(s) and failed 1 time(s).",
  "detail": {
    "MN1": {
      "result": "failed",
      "errorMessage": "GOVERNANCE_EXCEPTION_WARNING:CGovernanceManager::ProcessVote -- Unknown parent object , MN outpoint = fd5cb3ef632fb25a40665d1b4da0c1cd992c4f3d99ef38ce1ddf725ecfe53836-0, governance object hash = d418d2c8860147caa5ce3d62576a804384e830d67b8adf465d8f0b7ae87609f0\n"
    }
  }
}


Thanks, this is a complicated issue- something to do with governance hash collateral missing.  I added code to the pool to recover from this.  It can now move the proposal back to the beginning phase and resubmit the collateral, and then submit the gobject automatically. 

I just deployed it and hit it and it looks like it created a new proposal for us.  I just voted No on it, please try now :)

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 17, 2017, 02:06:14 am

Thanks, this is a complicated issue- something to do with governance hash collateral missing.  I added code to the pool to recover from this.  It can now move the proposal back to the beginning phase and resubmit the collateral, and then submit the gobject automatically. 

I just deployed it and hit it and it looks like it created a new proposal for us.  I just voted No on it, please try now :)

It worked this time :) Well. at first I got the same error, but mnsync status didn't say '999' yet. I tried it a second time and it worked.

In the previous round, when I tried it, I first checked mnsync status, and it did say '999' and I still got the error, but maybe I should have waited a bit longer (for voting, I first fire up the testnet controller wallet, because normally that pc is on the mainnet, so maybe it's just a syncing thing on my end).
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 17, 2017, 08:42:22 am
It worked this time :) Well. at first I got the same error, but mnsync status didn't say '999' yet. I tried it a second time and it worked.

In the previous round, when I tried it, I first checked mnsync status, and it did say '999' and I still got the error, but maybe I should have waited a bit longer (for voting, I first fire up the testnet controller wallet, because normally that pc is on the mainnet, so maybe it's just a syncing thing on my end).

Good, well I think they are different errors, when someone creates a new proposal, 5 BBP has to be burned.  Somehow on that first one you created, I saw the txid but the burnt was not in the chain.  On the new one I see the burned BBP. 

Maybe a different error text is emitted when your node isnt synced yet.  I guess we will find out soon enough.


Its looking pretty good now overall, but I see a little bug in the pool where it is not showing 4 negative votes on the substance vote yet.  Its a strange bug, when I debug the code, it works, when it runs in the pool it doesnt.  Havent had that problem on the pool yet.


Anyway, I wonder how we are all syncing?   I havent had an issue staying in sync on my 3 cold sanctuaries- can we do a little tests? 


08:41:19

getblockhash 14700


08:41:19

8c4d078c31c7cdf700af58b5db36a854b93339c70c488e39c8b8386a664578b2


Is general opinion that sanctuaries seem to be solid now?  Other than "watchdog expired" (Im working on relaxing that btw by 400%, already modified a lot of the code for the watchdog for prod and for the Restart Required).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 17, 2017, 10:19:00 am
Good, well I think they are different errors, when someone creates a new proposal, 5 BBP has to be burned.  Somehow on that first one you created, I saw the txid but the burnt was not in the chain.  On the new one I see the burned BBP. 

Maybe a different error text is emitted when your node isnt synced yet.  I guess we will find out soon enough.


Its looking pretty good now overall, but I see a little bug in the pool where it is not showing 4 negative votes on the substance vote yet.  Its a strange bug, when I debug the code, it works, when it runs in the pool it doesnt.  Havent had that problem on the pool yet.


Anyway, I wonder how we are all syncing?   I havent had an issue staying in sync on my 3 cold sanctuaries- can we do a little tests? 


08:41:19

getblockhash 14700


08:41:19

8c4d078c31c7cdf700af58b5db36a854b93339c70c488e39c8b8386a664578b2


Is general opinion that sanctuaries seem to be solid now?  Other than "watchdog expired" (Im working on relaxing that btw by 400%, already modified a lot of the code for the watchdog for prod and for the Restart Required).

Looking good :)

Code: [Select]
17:16:16

getblockhash 14700


17:16:16

8c4d078c31c7cdf700af58b5db36a854b93339c70c488e39c8b8386a664578b2

Where does the 5 BBP come from? The balance of the person creating the proposal?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 18, 2017, 10:29:56 am
Looking good :)
Where does the 5 BBP come from? The balance of the person creating the proposal?


Right now, it comes out of the pool wallet and does not even charge you, but that needs fixed.  So as to prevent spam.
Another problem is the pool is only allowed to submit one proposal per superblock, so thats got to be changed somehow.

Im still hunting down why our No votes arent showing.  Ill check that next.

We also need to raise the cost of a proposal to more like 5000 BBP so as to weed out frivilous proposals.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 22, 2017, 01:27:28 pm
You should raise the cost of proposals to 5000 but have it so that if it passes, that fee is refunded.
Yeah, I like that.  You know they can ask for 5000 more in the proposal, then get it back automatically.

Its tricky to code in a refund, since the money has to come from somewhere.

I am still working on looking at that issue where the No votes arent showing up; been tied up adding something new to the pool.

In the mean time people can still do more testing on the news feature; ensure its at least solid as far as what was originally written.

We can then re-brand it from news to use it as a built in help guide for creating masternodes at least.

Or maybe call it an 'article'.  Just an ability to list articles, add an article, and read articles. 
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 24, 2017, 10:03:37 am
hello, after restarted win testnet wallet i get this error

(https://i.imgur.com/IXooaPT.png)

im stuck on this error and dont know where is problem


thanks for your help
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 24, 2017, 12:22:44 pm
hello, after restarted win testnet wallet i get this error

(https://i.imgur.com/IXooaPT.png)

im stuck on this error and dont know where is problem


thanks for your help

I tried to help him, but this seems a strange error. Can't really find anything online. Thing is: he also does something with storj, and that's also on port 40001. But changing the port doesn't seem to help...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 24, 2017, 06:04:02 pm
I guess the question is where does that 5000 go initially?  Is it going to the Orphan Fund or just being burned?  You could send it to a  special address like the Orphan Fund, and using the conditional transaction fund logic you're building for wallet-to-wallet trading, make it a conditional transaction to either return to the sender or go on to the Orphan Fund/Burned.
The 5000 goes to the orphan address now, but Im sure we will have to change that to a burn address after sancs go live, because orphans will be paid out of the budget.
I dont follow you on the conditional payment; even if retirement account trading was live, there would be no way to send a payment back to a person from someones wallet, that would be like stealing from a random trader.  All money minted from the money supply must come from the coinbase tx.  So the only way to do this is either vote on the refund, or have him add it to the proposal.  Of course the latter is easier :)

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 24, 2017, 06:05:15 pm
I tried to help him, but this seems a strange error. Can't really find anything online. Thing is: he also does something with storj, and that's also on port 40001. But changing the port doesn't seem to help...

Lets check to see if his port is blocked and if he is modifying the correct masternode file?
Klondike, for testnet the correct file is : %appdata%\testnet3\masternode.conf.
Next, ensure the port is 40001 for testnet (I see you did that).
Ensure you are not listening on 40001 for anything else?
telnet yourip 40001 from another machine on your lan?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 25, 2017, 12:41:54 am
ADMIN:

im idiot :D i must go telnet3 folder in main folder ... no setup main masternode but masternode in telnet3 folder   ;D

PROBLEM NEXT:

when tried run masternode by masternode start-alias IVANKA from DEBUG CONSOLE on WINWALLET(controller wallet )failed: but when i run it by MIXING BUTTON, i see my masternode in peerlist.... its OK?

(https://i.imgur.com/FVohIR7.png)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 27, 2017, 12:59:18 pm
ADMIN:

im idiot :D i must go telnet3 folder in main folder ... no setup main masternode but masternode in telnet3 folder   ;D

PROBLEM NEXT:

when tried run masternode by masternode start-alias IVANKA from DEBUG CONSOLE on WINWALLET(controller wallet )failed: but when i run it by MIXING BUTTON, i see my masternode in peerlist.... its OK?

(https://i.imgur.com/FVohIR7.png)

Great!  Yeah, the txid just needed to confirm.  Since the tx is in your winwallet, just wait for 6 blocks to pass then do a 'getrawtransaction txid 1' and then you should see it, and your masternode start command should then work.  (As long IP is recognized on the network as public).

So I see your IP in my sanctuary list right now, so it looks like you are good :)

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 27, 2017, 01:13:28 pm
Alright all, I know a while has passed since we did heavy duty testing.  Ive been adding code in to the core for "Temples" and for F8000.

The code is now running on my LAN, but I need to do a little more testing before I release it here to testnet.

It looks like this is going to be Critical to test, as we have to ensure the Temple will not bring down the sanctuaries and its payments are approved by everyone and works smoothly. 

I would also like to see f8000 get a good round of testing so we know it will solve our "node mutex" issue in prod, on the very first try.  Its critical that once we deem it to be releaseable, that when its released during Christmas and sent as a mandatory that we dont hose up CCEX.  So please be watching for f8000 and jump on with an extra server and lets try to verify the hash speed cannot be manipulated by linux vs windows, or multiple linux vs linux. 

The retirement accounts are almost ready also, but Im going to deprirotize them right now so I can test my Temple, and Ill explain those later.  What to be expected: In the next release, you will start accruing retirement coins.  We will at least be able to own some and see the balance.  Then in a couple weeks we can test trading them.  The trading engine "works" but it needs some business logic to keep it "safe".  Its currently getting a harness put in it that allows the escrow trade of colored coins for non-colored asset, with the ability to roll back the trade.  This is done by using a complex transaction.  The complex transaction piggybacks the output of the first two legs into a new tx and then piggybacks the colored coins on that, along with non colored coins relying on that, so no one can get burned.

Finally this is what I envision a Temple to be:

In TestNet, a temple requires 15MM BBP collateral.  It has to run on windows.  For now, the only requirement is that it runs on a public IP with IIS, and this user syncs the github pool code in.  Im going to be setting one up in an hour so we can test the ecosystem. This will require everyone to upgrade.

Im thinking by the time Christmas hits, we might have ebay integration.  The ebay integration requires the Temple owner to apply for an Ebay developer license.  Im thinking this Ebay ID might be the "key" that unlocks the payment for the temple.  Anyway- the idea here is when a normal wallet user tries to buy a KJV bible, the order will be routed to a temple with a valid Ebay ID and auto-dropped ship to the users house directly from the wallet.  This means the temple will BUY the bible and Receive the Escrow.  Im going to make it so the temple can charge an extra padding fee to sell the coins if they start losing money on the deal.  This is what I think the Temple will provide for the network:  A gateway for purchasing valuable products with BBP.  (If you are asking why Amazon and Walmart didnt work, they have the API blocked off so that users cant use it for purchases or checkouts.  This is deliberate to protect their large billion $ revenue web presence).  It makes it impossible to check out an item with AWS or Walmart without clicking the Checkout button on the ecommerce branded site.  This however, will hopefully work in-wallet if we can integrate with ebay.  Im in talks right now with Zinc, but they seem to be very greedy and high priced, so Ebay is our best bet.



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 27, 2017, 04:13:31 pm
1.0.4.9 - Mandatory Upgrade for TESTNET

- Retirement accounts 1.0 (TESTNET)
- Trading Engine orderbook (TESTNET)
- Temples with 15MM BBP Requirement
- F8000 (TESTNET)
- Colored coins, complex transactions with escrow


All, please upgrade in testnet as Temples are a breaking change requiring a mandatory upgrade.

If anyone wants to test temples, follow the same hot wallet instructions except use 15,000,000 for escrow (as the e-commerce features are not integrated yet).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 28, 2017, 02:07:23 am
1.0.4.9 - Mandatory Upgrade for TESTNET

- Retirement accounts 1.0 (TESTNET)
- Trading Engine orderbook (TESTNET)
- Temples with 15MM BBP Requirement
- F8000 (TESTNET)
- Colored coins, complex transactions with escrow


All, please upgrade in testnet as Temples are a breaking change requiring a mandatory upgrade.

If anyone wants to test temples, follow the same hot wallet instructions except use 15,000,000 for escrow (as the e-commerce features are not integrated yet).

I'll update today and try to start a temple if I have enough coins now :)

Offtopic: I want to write a full guide for the pool. But what's your opinion on what the content should be? Should I just write a first introduction on how to pool-mine (create account, name miners) and then create a glossary of all the menu options? And should I make it a wiki-page?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 28, 2017, 02:46:26 am
1.0.4.9 - Mandatory Upgrade for TESTNET

- Retirement accounts 1.0 (TESTNET)
- Trading Engine orderbook (TESTNET)
- Temples with 15MM BBP Requirement
- F8000 (TESTNET)
- Colored coins, complex transactions with escrow


All, please upgrade in testnet as Temples are a breaking change requiring a mandatory upgrade.

If anyone wants to test temples, follow the same hot wallet instructions except use 15,000,000 for escrow (as the e-commerce features are not integrated yet).

How can I 'update' from sanctuary to temple? Should I just generate another masternode key and use a new alias?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 28, 2017, 04:34:22 am
admin do guide for us please: where i can see newest wallet testnet? or how can i update to newest? please do it still otherwise it does not matter
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 28, 2017, 04:42:18 am
admin do guide for us please: where i can see newest wallet testnet? or how can i update to newest? please do it still otherwise it does not matter

It's in the reddit guide:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

Under the header 'UPDATE:'

(Also, you have to use the command './biblepay-cli -testnet stop' instead of './biblepay-cli stop', because you're on testnet).
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 28, 2017, 05:21:29 am
thanks jaaapgk

ADMIN: where can be bug when masternode wallet filling with new coins but winwallet didnt?

again new bug: i tried do again masterode like testing with new reinstalled vps .... can be any problem with win controller wallet?
(https://i.imgur.com/UeOJF5u.png)

i resigned do anything with masternode
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 28, 2017, 10:33:53 am
How can I 'update' from sanctuary to temple? Should I just generate another masternode key and use a new alias?
Yeah, you can, but be aware there is a pitfall that affects all masternodes when rebroadcasting same public IP with new VIN.
I recommend spending the old vin first in coin control.  Enable coin control, from settings, go to send money, and spend the 500k.
Then, create your new vin except the only change being with 15MM BBP instead.  Also, make a new masternode privkey.  Restart the Temple.
Restart the controller.  Reactivate the temple (by sending the start command from the controller).  Then look at the logs in the temple and see if the new VIN was accepted.

So far, I just brought one temple online.  We have 4 people on 1049 and 2 on 1048.  Meaning that the supermajority has upgraded.
Now we have to see if these nodes vote that the temple is paid, so far I have not received a payment, but its only been an hour.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 28, 2017, 10:37:57 am
I'll update today and try to start a temple if I have enough coins now :)

Offtopic: I want to write a full guide for the pool. But what's your opinion on what the content should be? Should I just write a first introduction on how to pool-mine (create account, name miners) and then create a glossary of all the menu options? And should I make it a wiki-page?
That would be really, really sweet.  I think if you just cover the basics, over a few pages, and maybe the FAQs if you can think of any, -- then later we can fill in what people are really confused about.  But anyway I think a wiki would be great, as then we could link to other wiki pages from the wiki when the docs get really big.

But anyway, I can link to the wiki page from Help | Help just like the BX link works now.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 28, 2017, 10:39:28 am
How can I 'update' from sanctuary to temple? Should I just generate another masternode key and use a new alias?

For mine, I used same public IP, new masternode key, Same alias, Same original alias receiving address, updated the masternode.conf file on the controller with the new vin and vout, changed private key on the cold temple, restarted both, waited for mnsync status to = 999, then did a rebroadcast, and Temple updated.  It says PRE ENBABLED right now, so we are not Out of the woods yet :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 28, 2017, 10:43:37 am
Lets also collect info about f8000.  So far Ive only done a couple baby tests, but it appear to be a light year ahead of f7000 in the consistency sense.

My debian box is running at the same HPS as my win box, ~2000 HPS and these are the older type machines, and processor is being utilized fully.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 28, 2017, 12:27:17 pm
Hi All,

I found a few bugs in 1.0.4.9.

Please upgrade to 1.0.5.0.  Temples do not work in 1049.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 28, 2017, 02:15:18 pm
Also one more clarification for testnet:

When your sanctuary is paid, the retirement coins currently show on the tx line below the sanctuary payment (IE 7900 for sanctuary, 29 bbp for retirement). in the transaction list on the UI.

This is just temporary, in prod, the retirement rows are hidden, and instead we use a command: exec getretirementbalance.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 29, 2017, 04:55:21 am
Yeah, you can, but be aware there is a pitfall that affects all masternodes when rebroadcasting same public IP with new VIN.
I recommend spending the old vin first in coin control.  Enable coin control, from settings, go to send money, and spend the 500k.
Then, create your new vin except the only change being with 15MM BBP instead.  Also, make a new masternode privkey.  Restart the Temple.
Restart the controller.  Reactivate the temple (by sending the start command from the controller).  Then look at the logs in the temple and see if the new VIN was accepted.

So far, I just brought one temple online.  We have 4 people on 1049 and 2 on 1048.  Meaning that the supermajority has upgraded.
Now we have to see if these nodes vote that the temple is paid, so far I have not received a payment, but its only been an hour.

Thanks for the tip. I didn't know this. I've spend some other 500k masternode deposits (made 3 in total, while testing).

I'm first gonna try and start my sanctuary again, before moving on to the temple. It shows enabled right now, but my controller-wallet can't seem to sync to testnet (no block source available). Also, I saw there was an update to 1.0.5.1. so I'm gonna update first, before anything else.

Any clue on to why the controller wallet doesn't sync? It's on 1.0.4.8. btw.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 29, 2017, 09:00:34 am
same problem with no syncing

(https://i.imgur.com/VWlzZLJ.png)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 29, 2017, 09:02:40 am
Thanks for the tip. I didn't know this. I've spend some other 500k masternode deposits (made 3 in total, while testing).

I'm first gonna try and start my sanctuary again, before moving on to the temple. It shows enabled right now, but my controller-wallet can't seem to sync to testnet (no block source available). Also, I saw there was an update to 1.0.5.1. so I'm gonna update first, before anything else.

Any clue on to why the controller wallet doesn't sync? It's on 1.0.4.8. btw.

Yeah, to find out why it doesnt sync, you have to set debug=true and debugmaster=true first then look for the last line before repeating entries.

Unfortuantely 1051 has a breaking bug (growing pains of Temples I guess).  I cant guarantee the next version will solve everything.

But it appears the last version was capable of Paying temples, syncing When already synced, sharing info about the temples to the other sanctuaries, but where it hosed up, is during fresh syncs from zero and when its masternodes were not synced.

I have to go in baby steps because sometimes after we fix somethng it cascades to a new issue.


So All, please upgrade to 1052 now and lets try this again.  We will all need to reindex afterwards after upgrading  to ensure the blocks from 24 hours ago are pulled in the chain with headers.


The 1052 version is out now on github.






Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 29, 2017, 09:09:57 am
and how can syncing on win controller with old 148? problem isnt in wallet but in blockchain....cos before with win wallet on testnet i synced w/problem

(https://i.imgur.com/DWVs6Ls.png)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on October 29, 2017, 09:55:32 am
Does the Home/Controller wallet need to be upgraded? 

Windows 32 bit download from biblepay.org still has version 1.0.4.8

I also get stuck on syncing Home/Controller wallet,  stuck at 22 hours behind on block 25684
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 29, 2017, 09:57:37 am
Yeah, to find out why it doesnt sync, you have to set debug=true and debugmaster=true first then look for the last line before repeating entries.

Unfortuantely 1051 has a breaking bug (growing pains of Temples I guess).  I cant guarantee the next version will solve everything.

But it appears the last version was capable of Paying temples, syncing When already synced, sharing info about the temples to the other sanctuaries, but where it hosed up, is during fresh syncs from zero and when its masternodes were not synced.

I have to go in baby steps because sometimes after we fix somethng it cascades to a new issue.

So All, please upgrade to 1052 now and lets try this again.  We will all need to reindex afterwards after upgrading  to ensure the blocks from 24 hours ago are pulled in the chain with headers.

The 1052 version is out now on github.

Updating right now :)

I added  debug=true and debugmaster=true to the biblepay.conf, but I'm not exactly sure what to look for in the log, or if I'm even in looking in the right place. But here is a log of a complete startup and shutdown:

Code: [Select]
2017-10-29 15:48:21 Biblepay Core version 1.0.4.8 (2017-10-06 11:29:31 -0500)
2017-10-29 15:48:21 InitParameterInteraction: parameter interaction: -listen=0 -> setting -upnp=0
2017-10-29 15:48:21 InitParameterInteraction: parameter interaction: -listen=0 -> setting -discover=0
2017-10-29 15:48:21 InitParameterInteraction: parameter interaction: -listen=0 -> setting -listenonion=0
2017-10-29 15:48:21 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-10-29 15:48:21 GUI: libpng warning: bKGD: invalid
2017-10-29 15:48:21 GUI: setGeometryDp: Unable to set geometry 5x13+320+252 on QWidgetWindow/'QLabelClassWindow'. Resulting geometry:  116x13+320+252 (frame: 8, 30, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 0x0, maximum size: 16777215x16777215).
2017-10-29 15:48:21 ProdMode: Prod 0.000000GUI: "registerShutdownBlockReason: Successfully registered: Biblepay Core didn't yet exit safely..."
2017-10-29 15:48:22   thread  category true
2017-10-29 15:48:22 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-10-29 15:48:22 Default data directory C:\Users\JAAP\AppData\Roaming\BiblepayCore
2017-10-29 15:48:22 Using data directory C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3
2017-10-29 15:48:22 Using config file C:\Users\JAAP\AppData\Roaming\BiblepayCore\biblepay.conf
2017-10-29 15:48:22 Using at most 256 connections (2048 file descriptors available)
2017-10-29 15:48:22 Using 4 threads for script verification
2017-10-29 15:48:22 scheduler thread start
2017-10-29 15:48:25 libevent: getaddrinfo: no address associated with nodename
2017-10-29 15:48:25 Binding RPC on address :: port 39001 failed.
2017-10-29 15:48:25 HTTP: creating work queue of depth 16
2017-10-29 15:48:25 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2017-10-29 15:48:25 HTTP: starting 4 worker threads
2017-10-29 15:48:25   thread  category true
2017-10-29 15:48:25 Creating backup of C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\wallet.dat -> C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\backups\wallet.dat.2017-10-29-15-48
2017-10-29 15:48:25 Using wallet wallet.dat
2017-10-29 15:48:25 init message: Verifying wallet...
2017-10-29 15:48:25 CDBEnv::Open: LogDir=C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\database ErrorFile=C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\db.log
2017-10-29 15:48:25 init message: Init KJV Bible...
2017-10-29 15:48:25 init message: Loading KJV Bible...
2017-10-29 15:48:25 s1 e5aff8cff54256fe8ee133467eed3af0, s2 e409eb2ba6eb6801f52763ae370c350e
2017-10-29 15:48:25 Cache configuration:
2017-10-29 15:48:25 * Using 12.5MiB for block index database
2017-10-29 15:48:25 * Using 29.9MiB for chain state database
2017-10-29 15:48:25 * Using 57.6MiB for in-memory UTXO set
2017-10-29 15:48:25 init message: Loading block index...
2017-10-29 15:48:25 Opening LevelDB in C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\blocks\index
2017-10-29 15:48:25 Opened LevelDB successfully
2017-10-29 15:48:25 Using obfuscation key for C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\blocks\index: 0000000000000000
2017-10-29 15:48:25 Opening LevelDB in C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\chainstate
2017-10-29 15:48:25 Opened LevelDB successfully
2017-10-29 15:48:25 Using obfuscation key for C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\chainstate: 5cd10f0687210f92
2017-10-29 15:48:27 LoadBlockIndexDB: last block file = 0
2017-10-29 15:48:27 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=25733, size=6380886, heights=0...25721, time=2017-06-01...2017-10-29)
2017-10-29 15:48:27 Checking all blk files are present...
2017-10-29 15:48:27 LoadBlockIndexDB: transaction index enabled
2017-10-29 15:48:27 LoadBlockIndexDB: address index disabled
2017-10-29 15:48:27 LoadBlockIndexDB: timestamp index disabled
2017-10-29 15:48:27 LoadBlockIndexDB: spent index disabled
2017-10-29 15:48:27 LoadBlockIndexDB: hashBestChain=40ba5c7e1abd08349294010793155e0aa371e7595267703c37b842041a12c085 height=25684 date=2017-10-28 16:16:51 progress=0.027892
2017-10-29 15:48:27 init message: Verifying blocks...
2017-10-29 15:48:27 Verifying last 288 blocks at level 3
2017-10-29 15:48:28 No coin database inconsistencies in last 289 blocks (294 transactions)
2017-10-29 15:48:28  block index            3550ms
2017-10-29 15:48:28 init message: Loading wallet...
2017-10-29 15:48:28 nKeysLeftSinceAutoBackup: 1001
2017-10-29 15:48:28 nFileVersion = 1000408
2017-10-29 15:48:28 Keys: 1072 plaintext, 0 encrypted, 1072 w/ metadata, 1072 total
2017-10-29 15:48:29  wallet                  234ms
2017-10-29 15:48:29 init message: Activating best chain...
2017-10-29 15:48:29 Using masternode config file C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\masternode.conf
2017-10-29 15:48:29 Locking Masternodes:
2017-10-29 15:48:29   a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4 1 - locked successfully
2017-10-29 15:48:29 fLiteMode 0
2017-10-29 15:48:29 nInstantSendDepth 5
2017-10-29 15:48:29 PrivateSend rounds 2
2017-10-29 15:48:29 PrivateSend amount 1000
2017-10-29 15:48:29 init message: Loading masternode cache...
2017-10-29 15:48:29 Reading info from mncache.dat...
2017-10-29 15:48:29 Loaded info from mncache.dat  0ms
2017-10-29 15:48:29      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-10-29 15:48:29 Read: Cleaning....
2017-10-29 15:48:29      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-10-29 15:48:29 init message: Masternode cache is empty, skipping payments and governance cache...
2017-10-29 15:48:29 init message: Loading fulfilled requests cache...
2017-10-29 15:48:29 Reading info from netfulfilled.dat...
2017-10-29 15:48:29 Loaded info from netfulfilled.dat  0ms
2017-10-29 15:48:29      Nodes with fulfilled requests: 3
2017-10-29 15:48:29 Read: Cleaning....
2017-10-29 15:48:29      Nodes with fulfilled requests: 1
2017-10-29 15:48:29 init message: Memorizing Prayers...
2017-10-29 15:48:30 CMasternodeSync::ProcessTick1 -- nTick 1 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2017-10-29 15:48:30 CMasternodeSync::SwitchToNextAsset -- Starting MASTERNODE_SYNC_SPORKS
2017-10-29 15:48:36 CMasternodeSync::ProcessTick1 -- nTick 7 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:48:42 CMasternodeSync::ProcessTick1 -- nTick 13 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:48:44 mapBlockIndex.size() = 26284
2017-10-29 15:48:44 chainActive.Height() = 25684
2017-10-29 15:48:44 setKeyPool.size() = 1001
2017-10-29 15:48:44 mapWallet.size() = 2515
2017-10-29 15:48:44 mapAddressBook.size() = 7
2017-10-29 15:48:44 init message: Loading addresses...
2017-10-29 15:48:44 ERROR: Read: Failed to open file C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\banlist.dat
2017-10-29 15:48:44 Invalid or missing banlist.dat; recreating
2017-10-29 15:48:44 Loaded 221 addresses from peers.dat  0ms
2017-10-29 15:48:44 dnsseed thread start
2017-10-29 15:48:44 net thread start
2017-10-29 15:48:44 addcon thread start
2017-10-29 15:48:44 init message: Done loading
2017-10-29 15:48:44 msghand thread start
2017-10-29 15:48:44 opencon thread start
2017-10-29 15:48:44 mnbcon thread start
2017-10-29 15:48:44   thread  category true
2017-10-29 15:48:44 AddToWallet 2b9c7e1ce2cd5303e8e4094ffc0e3fbc727404544e6b4376dbb59f82f4231334 
2017-10-29 15:48:44   thread  category true
2017-10-29 15:48:44 GUI: Platform customization: "windows"
2017-10-29 15:48:44 GUI: PaymentServer::LoadRootCAs: Loaded  49  root certificates
2017-10-29 15:48:45   thread  category true
2017-10-29 15:48:45   thread  category true
2017-10-29 15:48:45 receive version message: /Biblepay Core:1.0.4.8/: version 70708, blocks=25684, us=84.29.208.33:54553, peer=1
2017-10-29 15:48:48 CMasternodeSync::ProcessTick1 -- nTick 19 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:48:55 CMasternodeSync::ProcessTick1 -- nTick 25 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:48:55 Loading addresses from DNS seeds (could take a while)
2017-10-29 15:48:56 receive version message: /Biblepay Core:1.0.5.1/: version 70708, blocks=25752, us=84.29.208.33:54557, peer=2
2017-10-29 15:48:57 ERROR: AcceptBlockHeader: block is marked invalid
2017-10-29 15:48:57 ERROR: invalid header received 08fd212a444c97384e70f6ea93f96d6269e897dab68dd184769fa3b0ea7df3a8
2017-10-29 15:48:57 ProcessMessages(headers, 45039 bytes) FAILED peer=2
2017-10-29 15:48:57 receive version message: /Biblepay Core:1.0.5.1/: version 70708, blocks=26233, us=84.29.208.33:54558, peer=3
2017-10-29 15:48:58   thread  category true
2017-10-29 15:48:58 15 addresses found from DNS seeds
2017-10-29 15:48:58 dnsseed thread exit
2017-10-29 15:49:01 CMasternodeSync::ProcessTick1 -- nTick 31 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:01   thread ‰ˆˆˆ category true
2017-10-29 15:49:01 CMasternodeSync::ProcessTick4 -- nTick 31 nRequestedMasternodeAssets 1 -- requesting sporks from peer 2
2017-10-29 15:49:01 CMasternodeSync::ProcessTick4 -- nTick 31 nRequestedMasternodeAssets 1 -- requesting sporks from peer 3
2017-10-29 15:49:07 CMasternodeSync::ProcessTick1 -- nTick 37 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:14 CMasternodeSync::ProcessTick1 -- nTick 43 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:20 CMasternodeSync::ProcessTick1 -- nTick 49 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:26 CMasternodeSync::ProcessTick1 -- nTick 55 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:33 CMasternodeSync::ProcessTick1 -- nTick 61 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:33 CMasternodeSync::ProcessTick4 -- nTick 61 nRequestedMasternodeAssets 1 -- requesting sporks from peer 1
2017-10-29 15:49:39 CMasternodeSync::ProcessTick1 -- nTick 67 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:45 CMasternodeSync::ProcessTick1 -- nTick 73 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:51 CMasternodeSync::ProcessTick1 -- nTick 79 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:58 CMasternodeSync::ProcessTick1 -- nTick 85 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:04 CMasternodeSync::ProcessTick1 -- nTick 91 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:10 CMasternodeSync::ProcessTick1 -- nTick 97 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:17 CMasternodeSync::ProcessTick1 -- nTick 103 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:23 CMasternodeSync::ProcessTick1 -- nTick 109 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:29 CMasternodeSync::ProcessTick1 -- nTick 115 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:36 CMasternodeSync::ProcessTick1 -- nTick 121 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:42 CMasternodeSync::ProcessTick1 -- nTick 127 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:48 CMasternodeSync::ProcessTick1 -- nTick 133 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:54 CMasternodeSync::ProcessTick1 -- nTick 139 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:01 CMasternodeSync::ProcessTick1 -- nTick 145 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:07 CMasternodeSync::ProcessTick1 -- nTick 151 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:13 CMasternodeSync::ProcessTick1 -- nTick 157 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:20 CMasternodeSync::ProcessTick1 -- nTick 163 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:26 CMasternodeSync::ProcessTick1 -- nTick 169 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:32 CMasternodeSync::ProcessTick1 -- nTick 175 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:38 receive version message: /Biblepay Core:1.0.5.2/: version 70708, blocks=25752, us=84.29.208.33:54599, peer=4
2017-10-29 15:51:39 CMasternodeSync::ProcessTick1 -- nTick 181 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:39 CMasternodeSync::ProcessTick4 -- nTick 181 nRequestedMasternodeAssets 1 -- requesting sporks from peer 4
2017-10-29 15:51:45 CMasternodeSync::ProcessTick1 -- nTick 187 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:51 CMasternodeSync::ProcessTick1 -- nTick 193 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:57 CMasternodeSync::ProcessTick1 -- nTick 199 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:04 CMasternodeSync::ProcessTick1 -- nTick 205 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:10 CMasternodeSync::ProcessTick1 -- nTick 211 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:16 CMasternodeSync::ProcessTick1 -- nTick 217 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:23 CMasternodeSync::ProcessTick1 -- nTick 223 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:29 CMasternodeSync::ProcessTick1 -- nTick 229 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:35 CMasternodeSync::ProcessTick1 -- nTick 235 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:42 CMasternodeSync::ProcessTick1 -- nTick 241 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:48 CMasternodeSync::ProcessTick1 -- nTick 247 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:54 CMasternodeSync::ProcessTick1 -- nTick 253 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:00 CMasternodeSync::ProcessTick1 -- nTick 259 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:07 CMasternodeSync::ProcessTick1 -- nTick 265 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:13 CMasternodeSync::ProcessTick1 -- nTick 271 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:19 CMasternodeSync::ProcessTick1 -- nTick 277 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:26 CMasternodeSync::ProcessTick1 -- nTick 283 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:32 CMasternodeSync::ProcessTick1 -- nTick 289 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:34 mnbcon thread interrupt
2017-10-29 15:53:34 addcon thread interrupt
2017-10-29 15:53:34 scheduler thread interrupt
2017-10-29 15:53:34 msghand thread interrupt
2017-10-29 15:53:34 net thread interrupt
2017-10-29 15:53:36 opencon thread interrupt
2017-10-29 15:53:36 PrepareShutdown: In progress...
2017-10-29 15:53:37 StopNode()
2017-10-29 15:53:37 Verifying mncache.dat format...
2017-10-29 15:53:37 Loaded info from mncache.dat  0ms
2017-10-29 15:53:37      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-10-29 15:53:37 Writting info to mncache.dat...
2017-10-29 15:53:37 Written info to mncache.dat  0ms
2017-10-29 15:53:37      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-10-29 15:53:37 mncache.dat dump finished  0ms
2017-10-29 15:53:37 Verifying mnpayments.dat format...
2017-10-29 15:53:37 Loaded info from mnpayments.dat  0ms
2017-10-29 15:53:37      Votes: 0, Blocks: 0
2017-10-29 15:53:37 Writting info to mnpayments.dat...
2017-10-29 15:53:37 Written info to mnpayments.dat  0ms
2017-10-29 15:53:37      Votes: 0, Blocks: 0
2017-10-29 15:53:37 mnpayments.dat dump finished  0ms
2017-10-29 15:53:37 Verifying governance.dat format...
2017-10-29 15:53:37 Loaded info from governance.dat  0ms
2017-10-29 15:53:37      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-10-29 15:53:37 Writting info to governance.dat...
2017-10-29 15:53:37 Written info to governance.dat  15ms
2017-10-29 15:53:37      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-10-29 15:53:37 governance.dat dump finished  15ms
2017-10-29 15:53:37 Verifying netfulfilled.dat format...
2017-10-29 15:53:37 Loaded info from netfulfilled.dat  0ms
2017-10-29 15:53:37      Nodes with fulfilled requests: 3
2017-10-29 15:53:37 Writting info to netfulfilled.dat...
2017-10-29 15:53:37 Written info to netfulfilled.dat  5ms
2017-10-29 15:53:37      Nodes with fulfilled requests: 4
2017-10-29 15:53:37 netfulfilled.dat dump finished  5ms
2017-10-29 15:53:38 Shutdown: done
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 29, 2017, 10:25:53 am
i tried mining on testnet wallet 152 on linux VPS but without chance ... chain is broken

all my win wallets testnet no syncing
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 29, 2017, 11:16:27 am
i tried mining on testnet wallet 152 on linux VPS but without chance ... chain is broken

all my win wallets testnet no syncing

I actually think the linux wallet is fine. I've been mining for a few minutes:

Code: [Select]
[email protected]:~/biblepay/src$ ./biblepay-cli -testnet getwalletinfo
{
  "walletversion": 61000,
  "balance": 0.00000000,
  "retirement_account_balance": 242.23500000,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 88013.36721135,
  "txcount": 9,
  "keypoololdest": 1508425662,
  "keypoolsize": 1001,
  "keys_left": 1000,
  "paytxfee": 0.00000000
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 29, 2017, 12:30:18 pm
what is correct biblepay.config for mining?

testnet=1
genproclimit=8

enough? cos before working,not now

ADMIN: can you explain where is problem with stuck syncing win-controller wallets?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on October 29, 2017, 02:56:03 pm
what is correct biblepay.config for mining?

testnet=1
genproclimit=8

enough? cos before working,not now

ADMIN: can you explain where is problem with stuck syncing win-controller wallets?

Do you also have 'gen=1' in your config?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 29, 2017, 03:53:42 pm
no........after add gen=1 synced:

so problem was in gen=1 or admin fixed it? :D

edit:// all blockchain is dead ... with my friend tried sync independent syncing:

my VPS is on others blocks like 2 other PCs
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 29, 2017, 07:44:09 pm
Oh yeah, I see the problem, the controller wallets, duh. Sorry.

Yeah, I was trying to avoid releasing the code to prod, because it has untested things in it, but double checking, everything is pushed off until block 400,000 so I think we are OK to push this out to the download site.  Lets cross our fingers and pray.   Please all let me know if this breaks anyone.  The miner is stll f7000, sanctuaries are disabled, and all the features are delayed in prod.

So go ahead and upgrade the controller wallets next.  From the download site.

Yes, it makes sense the chain is hosed in testnet, because we have a high % of controller wallets causing forks.  There are so many different rules in that 1047-1048 its not worth trying to run a fractured net.





Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 30, 2017, 01:58:36 am
how can we upgrade our controller win wallets when exists only 148 and its broken? we cant syncing ... give us any solution .. im downloaded any new wallet from main web=but it still 148 and still no syncing
im only 1 guy who will trying run it?  :o
(https://i.imgur.com/sqwGRgP.png)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 30, 2017, 07:53:02 am
Looks like we are getting closer now.  The primary issue is we need a rule that prevents a temple from staking during the same block as a superblock.

2017-10-30 13:38:39 coinbase pays too much at height 25700 (actual=9601632816378 vs limit=8660296265738), exceeded superblock max valueHeight 25700.000000, Amount 96016.328164
ERROR: ConnectBlock(biblepay): coinbase pays too much at height 25700 (actual=9601632816378 vs limit=8660296265738), exceeded superblock max value
2017-10-30 13:38:39 InvalidChainFound: invalid block=9cb8783758718a7ebc74bf456f59aeec825444b0954781e612432ea2ef7116cb  height=25700  log2_work=45.197793  date=2017-10-29 02:52:01


Looks like one of the two temples staked at block 25700 which is the same block as our superblock, which has a max payment of 72,000. 

In the mean time to get around this, everyone should reindex your block file.  See if you can get past block 25700 after a reindex.  If you are already above height  25700, delete your whole blocks file and chainstate and restart.  We need to get past the bad block at 25700.

Ill work on adding a rule in the mean time, but if we all sync and drop that bad block then we can at least continue testing on 1052.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 30, 2017, 08:21:07 am
All-

Please upgrade to 1.0.5.3 on linux, then delete your chainstate and blocks file and restart.

Windows is compiling now.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 30, 2017, 10:12:05 am
(https://i.imgur.com/4GL976O.png)   what blocks is last?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 30, 2017, 11:36:22 am
All,

I have discovered one issue with Temples related to security that I dont really like, and although we could probably work through it, I think at this point it would be stronger for us to roll back the temples out of the code and cancel them, and consider other options such as paying for the specific service through a budget in the future.

Sorry for the inconvenience guys, but I think this will be more straightforward.  Please hold off on testing until the new version is available.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 30, 2017, 12:19:13 pm
Alright 1.0.5.4 is out there, please upgrade.  Windows is still compiling.

Note that after we all get together with 1054, we have a little work to do on the masternodes.  Part o the reason we couldnt sync is some have banned each other and whats really exact with MNs, is they have an iterative payment schedule depending on who was paid last.  Meaning that if one node knows of A&B, and another B&C, those schedules will not agree.  So please delete your peers.dat, banlist.dat, mncache.dat, and blocks and chainstate and database and resync, we will need to re-seed the mncache data after we all upgrade.

PS Temples have been removed.  You can still have a 10 MM sanctuary right now, but it will not pay you any more than the 500k sanctuary so it is of no benefit. 

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 31, 2017, 11:30:28 am
Ok Windows is out for download (1.0.5.4) please delete all your .dat files including mnpayments.dat and mncache.dat, resync your chain, upgrade, and if you have a masternode, set masternode=0 before resyncing then back to masternode=1 after syncing then we should all be able to bootstrap our sanctuaries again.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on October 31, 2017, 02:52:16 pm
Robert,nice synced: but can i mining on testnet? cos doesnt working
i set in my config this:

testnet=1
genproclimit=24
gen=1

thanks for help

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on October 31, 2017, 03:37:42 pm
Robert,nice synced: but can i mining on testnet? cos doesnt working
i set in my config this:

testnet=1
genproclimit=24
gen=1

thanks for help

Something does appear to be hanging - but I dont see a problem with the code.  It could be the remaining nodes who havent upgraded yet.  I see that you and I are the only ones that upgraded (I have 3 nodes).

Anyway, I would recommend starting at threadlimit 3 with the new algorithm.  I can mine on 2 of my boxes.  Try 'setgenerate true 3' to see if you get any hashps in getmininginfo.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 01, 2017, 12:18:34 am
no result with mining:
may be this help you where is bug

(https://i.imgur.com/ICFxD8T.png)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 01, 2017, 08:01:34 am
no result with mining:
may be this help you where is bug

(https://i.imgur.com/ICFxD8T.png)

Yes, that helps.  I think the code is OK though.  I see a few guys just upgraded.  Let me see if I can start a hot sanctuary.

Im hoping we can all get synced and rebootstrapped today, and hopefully we dont need any code changes.

Let me do some testing.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 01, 2017, 08:26:15 am
im again stuck with sync  ;D
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 01, 2017, 09:15:01 am
im again stuck with sync  ;D

Ive got a few pieces of info now.

Overall things are looking a little better, as I think about 80% have synced to the right block but we seem to have fractured the masternode network and that part of it will need tackled next, but first we need to get over one more hump.

The miner will not run unless the miner thinks the blockchain is synced.
We are having an issue where the wallet thinks its not synced.  If you type mnsync status, see the row that says IsBlockChainSynced?  That prevents the miner from running.
The reason I can mine on a couple nodes, is because those are not masternodes, and the connected peers are synced.

The other problem we are having is you can not broadcast a masternode to be started unless its mnsync status reaches 999.  It cant reach 999 unless its chain is synced.  Its chain cant sync in the current environment. 

You can set masternode=0 if you want, and go down a level and try to get your chain synced first.  (Synced not only to the tip but synced with mnsync status 999).

Im working on that next on my end; Im taking the nodes that arents synced and rebuilding the chain from 0.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 01, 2017, 09:22:03 am
I was able to get further on one linux node even though this did not work this morning the environment has changed:

stop the node
cd testnet3
rm blocks -R
rm chainstate -R
rm *.dat (except wallet.dat)
restart

Then after the next block came in After resyncing, mnsync status went to 999, and I was able to finally start one hot masternode.

Now I am able to mine on the hot masternode in linux.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 01, 2017, 09:43:46 am
Looks like our masternodes are coming back online now; the list is re-filling.  Things looking a lot better.  Ill wait for your opinions.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on November 01, 2017, 10:45:27 am
I was away for a few days, but I'm back and compiling as we speak :)

EDIT: my masternode shows 'PRE-ENABLED', so I guess I'll be back online soon :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 02, 2017, 11:26:53 am
all working now correct and stable+ mining working now well too

o/

good job Rob
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 03, 2017, 09:41:29 am
Thanks guys, well we seem to be relatively stable now in testnet.

We really need to test this stuff thoroughly - as the last thing we need is go live at Christmas and find something didnt work as intended.

Has anyone decided to test blockchain news?

As far as f8000 goes, lets share some info on it.  Can we please test to see if the HPS in the miner is now more consistent across OS flavors and bitness, and prevents multiple copies from exploiting any increase? 

Here is my hashps using f8000:
Windows 64 bit - 6 core desktop : 4000 hps
Debian 64 bit - 1 core $10 per month vultr vm: 1000 hps

We should also circle back around, and have someone create a real budget item (please create one below 30000 bbp since superblocks in testnet are only 74000 bbp).  Create a thread for it also please.   Lets make one that we all will vote yes on?  I just want to see if this works for someone other than me.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 04, 2017, 02:35:36 pm
 :-*
So I did a test where my controller win wallet is receiving the subsidy for cold sanctuary #1.  I took the windows wallet offline for 30 hours to see if my sanctuary payments were sent by other nodes, and when I came back online sure enough the payments are coming in.  So that tells me we are 98% finished with the actual sanctuary mechanism.

I just created Oct recurring orphan expenses proposal - please vote on it after about an hour it should be available for voting (it has to send itself into the network, and that requires that it sends collateral, then waits 6 blocks, then creates the proposal object, then sends it, etc- the pool does all this for you right now).

Btw, the way I was thinking that pay to preach might work is (that is if P2P is approved in the budget), we create a pool receiving address for P2P, we add a proposal for P2P for say 1Q 2018, when approved, the payment is sent to the pool P2P key.  Then we give the pool the ability to reward "priests" who are on the schedule with subsidies after a successful sermon.  So basically, Priests register on the pool, we set up a biweekly sermon in a chatroom, participants come in, the priest preaches to the biblepay group, then the pool releases the payment after the sermon is over.  We keep doing that until the funds are exhausted, and do not vote on a new P2P campaign until exhausted.  We can add "Priests" and "Sermons" objects to the pool so we can see, and we can add a metric for the P2P balance.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 08, 2017, 04:33:44 pm
Hi guys

I'm trying to set up a test sanctuary .

Can you send me 500K tBBP please :

yd4AaGDNstGbqFPknhAz7uYKHxAPEyqQya

thanks
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on November 09, 2017, 02:44:03 am
Hi guys

I'm trying to set up a test sanctuary .

Can you send me 500K tBBP please :

yd4AaGDNstGbqFPknhAz7uYKHxAPEyqQya

thanks

Good to have another sanctuary tester on board. I have sent you some coins :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 09, 2017, 10:57:33 pm
Good to have another sanctuary tester on board. I have sent you some coins :)

thank you Jaapgvk.  500K received.   
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 10, 2017, 11:22:46 am
finished configuring the test sanctuary .

now it shows in the "masternode list" output  as "PRE_ENABLED" .
Do I need to do anything else to finalize it ?


[email protected]:~/biblepay/src# ./biblepay-cli masternode list
{
  "2b41b04ac488c033073562090aba186ccf57faf8ecae00dbc1f072a0ac9eebdf-1": "ENABLED",
  "82da38dd4db20bc6fa5fd30ebeda707d1edbce1b3890c386497db7f4abffe90c-1": "ENABLED",
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "NEW_START_REQUIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 10, 2017, 01:23:27 pm
finished configuring the test sanctuary .

now it shows in the "masternode list" output  as "PRE_ENABLED" .
Do I need to do anything else to finalize it ?


[email protected]:~/biblepay/src# ./biblepay-cli masternode list
{
  "2b41b04ac488c033073562090aba186ccf57faf8ecae00dbc1f072a0ac9eebdf-1": "ENABLED",
  "82da38dd4db20bc6fa5fd30ebeda707d1edbce1b3890c386497db7f4abffe90c-1": "ENABLED",
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "NEW_START_REQUIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"


status has changed to "ENABLED".   
is it OK now?   can you confirm it from the admin side ?


  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "ENABLED"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 11, 2017, 07:47:49 am


all tutorials doesnt working

0.    installed linux wallet
1.  ./biblepayd -testnet -daemon
2.  ./biblepay-cli -testnet getinfo  if block readed then we can start compilation
3.  ./biblepay-cli -testnet masternode genkey   got it
4.  ./biblepay-cli -testnet getaccountaddress TEST got it
5.  i send 500k from testnet wallet to masternode wallet got it.... i see 500k in da MN wallet and its confirmed 7/7
6.  ./biblepay-cli -testnet masternode outputs  got outputs
7.  im opened masternode.config in tesnet3 folder and addded POKUS IP:40001 93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR 7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c 1

7.5   ./biblepay-cli -testnet mnsync status   ASSETID:999   999 its OK

8.   now on testnet wallet in folder biblapaycore im opened config file and added this

testnet=1
rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Saved it, closed and restarted testnet wallet  WORK

9.on linux the SANCTUARY WALLET STOPED wallet and open biblepay.conf and added this

rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
externalip=IP:40001
maxconnections=256
masternode=1
masternodeprivkey=93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR

saved config and run masternode-linux-wallet again


10. in controller windows wallet opened debug win and write this command masternode start-alias POKUS


(https://i.imgur.com/JebRK0k.png)

(https://i.imgur.com/XLgqeTx.png)


where is bug on my side? any help guys?



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 11, 2017, 09:33:39 am

all tutorials doesnt working

0.    installed linux wallet
1.  ./biblepayd -testnet -daemon
2.  ./biblepay-cli -testnet getinfo  if block readed then we can start compilation
3.  ./biblepay-cli -testnet masternode genkey   got it
4.  ./biblepay-cli -testnet getaccountaddress TEST got it
5.  i send 500k from testnet wallet to masternode wallet got it.... i see 500k in da MN wallet and its confirmed 7/7
6.  ./biblepay-cli -testnet masternode outputs  got outputs
7.  im opened masternode.config in tesnet3 folder and addded POKUS IP:40001 93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR 7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c 1

7.5   ./biblepay-cli -testnet mnsync status   ASSETID:999   999 its OK

8.   now on testnet wallet in folder biblapaycore im opened config file and added this

testnet=1
rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Saved it, closed and restarted testnet wallet  WORK

9.on linux the SANCTUARY WALLET STOPED wallet and open biblepay.conf and added this

rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
externalip=IP:40001
maxconnections=256
masternode=1
masternodeprivkey=93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR

saved config and run masternode-linux-wallet again


10. in controller windows wallet opened debug win and write this command masternode start-alias POKUS


(https://i.imgur.com/JebRK0k.png)

(https://i.imgur.com/XLgqeTx.png)


where is bug on my side? any help guys?

I removed your swear comment.
Please dont swear here. 


Try going to the controller wallet and copy your txid of your collateral to the clipboard, and type

getrawtransaction tx_id_of_collateral 1

Note how nothing comes back.  That means you have no collateral set up for the masternode.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 11, 2017, 03:20:14 pm
Anyone who has "restart required" or "watchdog expired" please check your watchman-on-the-wall status.
If watchman isnt running, POSE fails, then watchdog expires, then your node fails to get paid its sanctuary payment.

In my case, 2 of my sanctuaries crontabs were working fine, but one linux box kept showing watchdog expired.
In this particular case, I had a local user account that was set up to run biblepay and watchman.  However, in my crontab I had the path for watchman configured as the root home directory as the start dir (not the local user).  So please, verify the user that you will run biblepay as, grab the full user path, and ensure the start directory is correct for watchman, then edit your crontab -e as the actual user and make the adjustment.  Once I did that, my watchdog status went back to ENABLED.

So now my 3 nodes are running.  Will you all please ensure your masternodes are running?  As we only have 30 days left for testing.

Also please get ready for a new release.

Those on Linux, go ahead and update to 1.0.5.6.  Then we will try a few retirement account trades.

Windows is compiling now.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 11, 2017, 08:51:22 pm
1.0.5.6-Testnet-Leisure Upgrade

All,

1.0.5.6 is now available for download.  Please upgrade including controller wallets.

To start testing retirement accounts please see this page:

http://wiki.biblepay.org/Retirement_Accounts (http://wiki.biblepay.org/Retirement_Accounts)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 12, 2017, 07:52:29 am
i have to have install any watchdog?what is it? where is here in this forum tutorial how to install it?




please set on your web what wallet is last ... its so hard for you add icon above button downloading wallet what version wallet we downloading?  ::)

(https://i.imgur.com/yNBcFMZ.png)

Watchman has been in the help guide since the beginning.  Watchdog is part of watchman.
It clearly says in the tutorial you have to comment out mainnet and uncomment testnet.
I have no clue how to answer your question when you say "it didnt work" because that could mean a million things.
The question is when you make ONE change not TWO to the watchman conf file, then follow the instructions, run it again and see if it runs without any output - and only do it when biblepay dameon is already running.  You have to do some things yourself, we dont know your machines paths.

As far as the version number on the web download, put a ticket into github with that suggestion and be very detailed as to what you are talking about.

If you dont like the tutorial try using dashs tutorial or tell us how to make it better.  Its NOT for newbies. 

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 12, 2017, 10:46:34 am
These are my notes from doing Masternode testing a month ago:  http://forum.biblepay.org/index.php?topic=16.msg151#msg151

I am going to re-setup a masternode today and make sure every step is correct and clear :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 12, 2017, 12:11:19 pm
togo: your tutorial about run mining under linux is perfect!!!

im tried do my tutorial

.    installed linux wallet
1.  ./biblepayd -testnet -daemon
2.  ./biblepay-cli -testnet getinfo  =if blocks readed then we can start compilation
3.  ./biblepay-cli -testnet masternode genkey   =got it
4.  ./biblepay-cli -testnet getaccountaddress TEST =got it
5.  i send 500k from testnet wallet to masternode wallet got it.... i see 500k in da MN wallet and its confirmed 7/7
6.  ./biblepay-cli -testnet masternode outputs  =got outputs
7.  im opened masternode.config in tesnet3 folder and addded POKUS IP:40001 93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR 7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c 1

7.5   ./biblepay-cli -testnet mnsync status   =ASSETID:999   =999 its OK

8.   now on testnet wallet in folder biblapaycore im opened config file and added this

testnet=1
rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Saved it, closed and restarted testnet wallet  =WORK

9.on linux the SANCTUARY WALLET STOPED wallet and open biblepay.conf and added this

rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
rpcport=9998  biblepay aka admin doesnt know that this rpcport have to/must be add in this config  >:(
listen=1
server=1
daemon=1
logtimestamps=1
externalip=IP:40001
maxconnections=256
masternode=1
masternodeprivkey=93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR

saved config and run masternode-linux-wallet again


and here is your tutorial bugs:

1st bug:

PART 4 - Run Sanctuary Linux Wallet Testnet
On remote Linux machine:
1. Enable & Run Wallet in Testnet mode:  newbies dont know how run testnet wallet add this command

./biblepayd -testnet -daemon
____________________________________________________________________________

when i added rpcport=9999 to linux=masternode wallet WATCHMAN ran without errors:

NOW MY MASTERNODE WORKING OR?


(https://i.imgur.com/ZQNx2Gm.png)

tommorow ill do VIDEO TUTORIAL for idiots=newbies

i have this questions:

masternodewallet is HOT wallet?
controllerwinwallet is COLD wallet?

masternodewallet raising balance=why,when my setup was wrote only testnet=1, why mining?
masternodewallet cancelled/delete= i receive 500k coins back?
masternodewallet raise balance for % reward for block?
controller wallet balance raising same like on masternode wallet? using same like when i have wallet.dat on 2 different wallets,but see same coins on both of it?

thanks for understanding this things


ADMIN: immediately fix your wiki tutorial:

add this line when compiling watchman

on linux config you add this rpcport=9998





Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 12, 2017, 05:55:30 pm
togo: your tutorial about run mining under linux is perfect!!!

im tried do my tutorial

.    installed linux wallet
1.  ./biblepayd -testnet -daemon
2.  ./biblepay-cli -testnet getinfo  =if blocks readed then we can start compilation
3.  ./biblepay-cli -testnet masternode genkey   =got it
4.  ./biblepay-cli -testnet getaccountaddress TEST =got it
5.  i send 500k from testnet wallet to masternode wallet got it.... i see 500k in da MN wallet and its confirmed 7/7
6.  ./biblepay-cli -testnet masternode outputs  =got outputs
7.  im opened masternode.config in tesnet3 folder and addded POKUS IP:40001 93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR 7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c 1

7.5   ./biblepay-cli -testnet mnsync status   =ASSETID:999   =999 its OK

8.   now on testnet wallet in folder biblapaycore im opened config file and added this

testnet=1
rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Saved it, closed and restarted testnet wallet  =WORK

9.on linux the SANCTUARY WALLET STOPED wallet and open biblepay.conf and added this

rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
rpcport=9998  biblepay aka admin doesnt know that this rpcport have to/must be add in this config  >:(
listen=1
server=1
daemon=1
logtimestamps=1
externalip=IP:40001
maxconnections=256
masternode=1
masternodeprivkey=93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR

saved config and run masternode-linux-wallet again


and here is your tutorial bugs:

1st bug:

PART 4 - Run Sanctuary Linux Wallet Testnet
On remote Linux machine:
1. Enable & Run Wallet in Testnet mode:  newbies dont know how run testnet wallet add this command

./biblepayd -testnet -daemon
____________________________________________________________________________

when i added rpcport=9999 to linux=masternode wallet WATCHMAN ran without errors:

NOW MY MASTERNODE WORKING OR?


(https://i.imgur.com/ZQNx2Gm.png)

tommorow ill do VIDEO TUTORIAL for idiots=newbies

i have this questions:

masternodewallet is HOT wallet?
controllerwinwallet is COLD wallet?

masternodewallet raising balance=why,when my setup was wrote only testnet=1, why mining?
masternodewallet cancelled/delete= i receive 500k coins back?
masternodewallet raise balance for % reward for block?
controller wallet balance raising same like on masternode wallet? using same like when i have wallet.dat on 2 different wallets,but see same coins on both of it?

thanks for understanding this things


ADMIN: immediately fix your wiki tutorial:

add this line when compiling watchman

on linux config you add this rpcport=9998

YES, Your Sanctuary is Running!  Right On.

=-=-=-=-=-=



Ill add the biblepay -testnet to the wiki - note daemon is not required as you should have daemon=1 in the config.

Your questions:

masternodewallet is HOT wallet?

-> The Sanctuary is HOT when the BBP is in it (not recommended).  The Sanctuary is Cold when the BBP is in the controller wallet (RECOMMENDED).


masternodewallet raising balance=why,when my setup was wrote only testnet=1, why mining?
-> The Sanctuary Can mine, if it is in sync.  No problem.


masternodewallet cancelled/delete= i receive 500k coins back?
-> Yes, to cash out your sanctuary, Enable coin control from SETTINGS, then go to Send Money, then click COIN CONTROL, then UNLOCK ALL YOUR LOCKED FUNDS BY TOGGLING THE LOCK, Then check the 500k, then click OK, then Send the money Out of the sanctuary and it will not be a sanctuary anymore.


masternodewallet raise balance for % reward for block?
-> I dont know please refrase this.


controller wallet balance raising same like on masternode wallet? using same like when i have wallet.dat on 2 different wallets,but see same coins on both of it?
-> No, the rewards for running the sanctuary go to the Controller wallet (wherever the Hot funds are).


ADMIN: immediately fix your wiki tutorial:

add this line when compiling watchman

on linux config you add this rpcport=9998

-> OK

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 12, 2017, 08:53:41 pm
I updated my Sanctuary/Masternode and Home Wallets to v1.0.5.6
and updated Watchman to 1.0.0.1b

Im getting WATCHDOG_EXPIRED status

The tests for watchman ran fine,
but when I run watchman.py I get the below simplejson.scanner.JSONDecodeError error:

~/.biblepaycore/watchman$ ./venv/bin/python bin/watchman.py

Traceback (most recent call last):
  File "bin/watchman.py", line 244, in <module>
    main()
  File "bin/watchman.py", line 191, in main
    perform_biblepayd_object_sync(biblepayd)
  File "bin/watchman.py", line 24, in perform_biblepayd_object_sync
    GovernanceObject.sync(biblepayd)
  File "lib/models.py", line 87, in sync
    (go, subobj) = self.import_gobject_from_biblepayd(biblepayd, item)
  File "lib/models.py", line 116, in import_gobject_from_biblepayd
    object_hex = biblepaylib.SHIM_deserialise_from_biblepayd(object_hex)
  File "lib/biblepaylib.py", line 204, in SHIM_deserialise_from_biblepayd
    obj = deserialise(biblepayd_hex)
  File "lib/biblepaylib.py", line 229, in deserialise
    obj = simplejson.loads(json, use_decimal=True)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/__init__.py"                                 , line 533, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py",                                  line 370, in decode
    obj, end = self.raw_decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py",                                  line 400, in raw_decode
    return self.scan_once(s, idx=_w(s, idx).end())
simplejson.scanner.JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 115 (                                 char 114)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 12, 2017, 10:57:56 pm
my node is  stuck in "pre-enabled" status.
not sure if it's relevant but it's happening after i upgraded to "1.0.5.6"

"78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 13, 2017, 01:24:07 am
i got same problem like TOGOSHIGEKATA

Im getting WATCHDOG_EXPIRED status

and no coins going to my controller wallet

this all tutorials is bad!!! nobody from my neighborhoods cant setup masternode and 3 guys is IT senior admins: all have same problems like me:
watchdog still expired, coins  in controller wallet no raise and when we tried to start masternode from controller always we see this

(https://i.imgur.com/XLgqeTx.png)

i believe that masternode wont be start if exists still this bugs

and this guide need next university diplom for me
Yes, to cash out your sanctuary, Enable coin control from SETTINGS, then go to Send Money, then click COIN CONTROL, then UNLOCK ALL YOUR LOCKED FUNDS BY TOGGLING THE LOCK, Then check the 500k, then click OK, then Send the money Out of the sanctuary and it will not be a sanctuary anymore.   :o
-from settings? where,in controller wallet?
-go to send money?
-click COIN CONTROL
-unlock all your locked funds by toggling lock?  :o


where is problem by tutorial with RUN MASTERNODE from controller wallet by command MASTERNODE START-ALIAS NICK

important question is: when i sending 500k from controller wallet to masternode wallet: classic way? send 500k and thats all?

BIBLEPAY in wiki can you fix this
7) Use the following command to check status:
masternode status

correct commands for masternode

 ./biblepay-cli -testnet mnsync status
./biblepay-cli masternode list
./biblepay-cli masternode list-conf
./biblepay-cli masternode start-alias
./biblepay-cli masternode help
./biblepay-cli masternode status
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 13, 2017, 07:50:34 am
my node is  stuck in "pre-enabled" status.
not sure if it's relevant but it's happening after i upgraded to "1.0.5.6"

"78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"
Yeah, that happens when watchman is not actually running in the cron.
Please do this:
type 'crontab -e' , copy the exact command you typed into your cron into notepad.
exit crontab.


Now type the command from bash.  Tell me if it throws an error (Im sure it will most likely).
Then fix the crontab.


Klondike,  this guide is not for newbies.  Why dont you have your Senior IT specialists google other coins like Chaincoin and Dash and explain how their video is better?  Its NOT.  It requires patience and doing it exact.  I went through the guide and it works.  I updated the one entry for the crontab yesterday.  I believe your "WATCHDOG EXPIRED" is the same issue as above.  Let me know what the output of the above command is.

Once you figure it out, go ahead and make a video for us, and we will post it here.


By the way, the correct commands are not preceded by biblepay-cli.  Some people use RPC, some use bitnet, some use biblepayd, its common sense to precede your commands with biblepay-cli, so the guide stays as is.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 13, 2017, 08:03:58 am
I updated my Sanctuary/Masternode and Home Wallets to v1.0.5.6
and updated Watchman to 1.0.0.1b

Im getting WATCHDOG_EXPIRED status

The tests for watchman ran fine,
but when I run watchman.py I get the below simplejson.scanner.JSONDecodeError error:

~/.biblepaycore/watchman$ ./venv/bin/python bin/watchman.py

Traceback (most recent call last):
  File "bin/watchman.py", line 244, in <module>
    main()
  File "bin/watchman.py", line 191, in main
    perform_biblepayd_object_sync(biblepayd)
  File "bin/watchman.py", line 24, in perform_biblepayd_object_sync
    GovernanceObject.sync(biblepayd)
  File "lib/models.py", line 87, in sync
    (go, subobj) = self.import_gobject_from_biblepayd(biblepayd, item)
  File "lib/models.py", line 116, in import_gobject_from_biblepayd
    object_hex = biblepaylib.SHIM_deserialise_from_biblepayd(object_hex)
  File "lib/biblepaylib.py", line 204, in SHIM_deserialise_from_biblepayd
    obj = deserialise(biblepayd_hex)
  File "lib/biblepaylib.py", line 229, in deserialise
    obj = simplejson.loads(json, use_decimal=True)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/__init__.py"                                 , line 533, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py",                                  line 370, in decode
    obj, end = self.raw_decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py",                                  line 400, in raw_decode
    return self.scan_once(s, idx=_w(s, idx).end())
simplejson.scanner.JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 115 (                                 char 114)

Togo, could you please try deleting the /watchman directory, and completely reinstalling watchman, and delete mncache.dat, and restart the biblepayd, then retry the test with watchman from the command line? Lets see if it was a permission error when writing the dependencies from the "install.txt" list, or possibly, something loaded into the Watchman database that cant be parsed as JSON.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 13, 2017, 08:33:51 am
im installed my watchman with tutorial: its step by step of course....
then delete # in testnet and add # in mainnet
then setup crontab -e with this * * * * * cd /.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

watchman ran and dont know if working ...

btw: im stuck on 38150 blocks testnet wallet .... how can i fixit?


BIBLEPAY aka ADMIN=   DO VIDEO TUTORIAL FOR ALL !!!!!!!! AND BTW: BITCOINTALK FORUM  is DEAD FOR BBP ... and it looks that BBP ending when doesnt exists no forum  ;D ;D ;D


 
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 13, 2017, 11:19:28 am
These are steps I took to try to pinpoint watchman issue,
I previously before this installed latest versions of biblepay on my Masternode setup from a month ago:

===

On Sanctuary/Masternode Linux Wallet:

=== Stop Biblepay & Delete Old Testnet .Dat Data
cd biblepay/src
./biblepay-cli stop

cd ~/.biblepaycore/testnet3

rm blocks -R
rm chainstate -R
rm banlist.dat
rm fee_estimates.dat
rm governance.dat
rm mncache.dat
rm mnpayments.dat
rm netfulfilled.dat
rm peers.dat

=== Delete, Download and Setup Watchman
cd ..
rm -r -f watchman

git clone https://github.com/biblepay/watchman.git
cd watchman
virtualenv venv
venv/bin/pip install -r requirements.txt

vi watchman.conf
i
(add hashtag # to front of network=mainnet)
(remove hashtag # in front of network=testnet)
ESC
:wq

=== Turn on BiblePay
cd ../../biblepay/src

./biblepayd -daemon

(Wait for full sync)

=== Now Try Watchman
cd ~/.biblepaycore/watchman

venv/bin/python bin/watchman.py

OUTPUT: None, Blank, Yay!

============================================

~/.biblepaycore/watchman$ ./venv/bin/py.test ./test
=========================================================== test session starts ===========================================================
platform linux2 -- Python 2.7.12, pytest-3.0.1, py-1.4.31, pluggy-0.3.1
rootdir: /home/ubuntu/.biblepaycore/watchman, inifile:
collected 12 items / 2 errors

================================================================= ERRORS ==================================================================
___________________________________________ ERROR collecting test/unit/models/test_proposals.py ___________________________________________
test/unit/models/test_proposals.py:10: in <module>
    from models import GovernanceObject, Proposal, Vote
lib/models.py:5: in <module>
    import init
lib/init.py:103: in <module>
    main()
lib/init.py:94: in main
    if not is_database_correctly_configured():
lib/init.py:55: in is_database_correctly_configured
    sys.exit(1)
E   SystemExit: 1
------------------------------------------------------------- Captured stdout -------------------------------------------------------------
[error]: unable to open database file
Cannot connect to database. Please ensure database service is running and user access is properly configured in 'watchman.conf'.
__________________________________________ ERROR collecting test/unit/models/test_superblocks.py __________________________________________
test/unit/models/test_superblocks.py:10: in <module>
    from models import GovernanceObject, Proposal, Superblock, Vote
lib/models.py:5: in <module>
    import init
lib/init.py:103: in <module>
    main()
lib/init.py:94: in main
    if not is_database_correctly_configured():
lib/init.py:55: in is_database_correctly_configured
    sys.exit(1)
E   SystemExit: 1
------------------------------------------------------------- Captured stdout -------------------------------------------------------------
[error]: unable to open database file
Cannot connect to database. Please ensure database service is running and user access is properly configured in 'watchman.conf'.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
========================================================= 2 error in 0.18 seconds ========================================================

=== Watchman Database Poking

sudo apt-get install sqlite3
sqlite3 Watchman
sqlite>
select * from votes;
.table <enter>

== OUTPUT:
1|2|2|1|2017-11-13 16:20:01.419328|2017-11-13 16:20:01.419338|2017-11-13 16:20:01.419344|f2ff8b0970c959e1ea750234593ff358f9ea7ce8e162a6c6ab50c6b31035330c

governance_objects  proposals           signals             votes
outcomes            settings            superblocks         watchdogs

CTRL + D to exit sqlite

=========

=== Windows Home Controller Wallet - Unban, Reindex and Start Masternode
Tools >> Peer List >> (Unban banned peers)

Tools >> Wallet Repair >> Rebuild index

Tools >> Debug Console
masternode list
masternode list-conf
masternode start-alias MASTERNODENAME

setgenerate true 4
(I started mining, and am waiting for Masternode/Sanctuary to get out of PRE_ENABLED state)
(No Watch dog expired state so that seems good)

=== Linux Masternode/Sanctuary Wallet - Check Status

./biblepay-cli masternode status
{
  "vin": "CTxIn(COutPoint(be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add, 1), scriptSig=)",
  "service": "34.208.206.95:40001",
  "payee": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "status": "Masternode successfully started"
}

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 13, 2017, 12:11:12 pm
Yeah, that happens when watchman is not actually running in the cron.
Please do this:
type 'crontab -e' , copy the exact command you typed into your cron into notepad.
exit crontab.


Now type the command from bash.  Tell me if it throws an error (Im sure it will most likely).
Then fix the crontab.


Klondike,  this guide is not for newbies.  Why dont you have your Senior IT specialists google other coins like Chaincoin and Dash and explain how their video is better?  Its NOT.  It requires patience and doing it exact.  I went through the guide and it works.  I updated the one entry for the crontab yesterday.  I believe your "WATCHDOG EXPIRED" is the same issue as above.  Let me know what the output of the above command is.

Once you figure it out, go ahead and make a video for us, and we will post it here.


By the way, the correct commands are not preceded by biblepay-cli.  Some people use RPC, some use bitnet, some use biblepayd, its common sense to precede your commands with biblepay-cli, so the guide stays as is.

thanks Admin,

updaded BBP to  "1.0.5.8"  and it fixed the issue.

crontab  -e  was ok according to the instructions.

grep CRON /var/log/syslog

Code: [Select]
Nov 13 10:07:01 BUS7-14 CRON[11263]: (root) CMD (cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1)
Nov 13 10:08:01 BUS7-14 CRON[11275]: (root) CMD (cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1)
Nov 13 10:09:01 BUS7-14 CRON[11291]: (root) CMD (cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1)

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 13, 2017, 12:19:21 pm
my node is  stuck in "pre-enabled" status.
not sure if it's relevant but it's happening after i upgraded to "1.0.5.6"

"78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"

updaded BBP to  "1.0.5.8"  and it fixed the issue.

Hmmm, my Masternode has been stuck in PRE_ENABLED as well, I waited a good 45+ minutes, but was still stuck in that state, Ill try updating from v1.0.5.6 to v1.0.5.8 and report back
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 13, 2017, 01:27:10 pm
Hmmm, my Masternode has been stuck in PRE_ENABLED as well, I waited a good 45+ minutes, but was still stuck in that state, Ill try updating from v1.0.5.6 to v1.0.5.8 and report back
Sorry if this sounds dumb as I read your prior post, but could you also check this :
Please dump your crontab -e contents and try to exec that manually? Just to ensure the whole line minus the "dev null" part runs without an error?

I had this problem the other day, my watchman ran from the command line but not from crontab- that put me in the "PRE_ENABLED" state.  But since crontab was not running every 5 mins, it never transitioned to "ENABLED".  Once I fixed the crontab, everything was fine, and now ive been up for 2 1/2 days. 

I also learned the way watchdog and POSE work in a more detailed way.

Basically, watchdog enforces the Public IP and the proof-of-service.  If another node catches your nodes public IP not responding once in an 8 hour period it remembers that, and tries to vote you for Non payment.  You have up to 8 hours to fix it.  If a person is on vacation and their node is down more than 8 hours, the watchdog expires. 


This is good, because it means to get paid in Sanctuaries you have to rent public VMs and they have to stay up, otherwise you fall out of payment pool.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 13, 2017, 02:29:11 pm
oooo Interesting, no changes ( other than updating to v1.0.5.8 ) and now later masternode has Enabled status!

My crontab is:

* * * * * cd /home/ubuntu/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

My login name is:  ubuntu
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 13, 2017, 04:31:26 pm
where i have to setup configs+watchman
i see 2 folders with biblepaycore

cd /home/klondike/biblepaycore
or
cd ~/.biblepaycore$
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 13, 2017, 04:33:30 pm
where i have to setup configs+watchman
i see 2 folders with biblepaycore

cd /home/klondike/biblepaycore
or
cd ~/.biblepaycore$
Its possible to put it anywhere, but I recommend ~/.biblepaycore as the logs go there and its considered ONE installation if you put watchman in there.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 13, 2017, 04:35:41 pm
oooo Interesting, no changes ( other than updating to v1.0.5.8 ) and now later masternode has Enabled status!

My crontab is:

* * * * * cd /home/ubuntu/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

My login name is:  ubuntu
Hmm, note that 1058 relaxes the watchdog timeout for the network from 4 hours to 8 hours, so the problem will still reappear if the crontab doesnt work LOL, so anyway just try running the crontab without the >/dev/null suffix, see if it works, if it doesnt try changing to the shortcut ~/.biblepaycore for the beginning CD part of the command etc.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 13, 2017, 07:08:29 pm
Hmm, note that 1058 relaxes the watchdog timeout for the network from 4 hours to 8 hours, so the problem will still reappear if the crontab doesnt work LOL, so anyway just try running the crontab without the >/dev/null suffix, see if it works, if it doesnt try changing to the shortcut ~/.biblepaycore for the beginning CD part of the command etc.

Hahaha, I guess we shall see what happens in a few hours :) , masternode/sanctuary has been live for 5 hours 20 minutes so far. Im not sure if I was just impatient on v1.0.5.6, or if v1.0.5.8 fixed my issue, or if my crontab actually is wrong.

Ive just modified crontab:
crontab -e

Changed this:   
* * * * * cd /home/ubuntu/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

To this:
* * * * * cd /home/ubuntu/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 14, 2017, 08:09:11 am
Hahaha, I guess we shall see what happens in a few hours :) , masternode/sanctuary has been live for 5 hours 20 minutes so far. Im not sure if I was just impatient on v1.0.5.6, or if v1.0.5.8 fixed my issue, or if my crontab actually is wrong.

Ive just modified crontab:
crontab -e

Changed this:   
* * * * * cd /home/ubuntu/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

To this:
* * * * * cd /home/ubuntu/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py


Hows it going guys?  Is it still humming along?

I see 207.244 and 34.208 figured it out (and my 3 nodes).  So we have 5, thats pretty good.
Everyone else is still hosed.

So is anyone ready for a retirement trade? Can someone post their retirement account balance here?


 
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 14, 2017, 08:56:56 am
Im 34.208, been 18+ hours active, still hummin!

Retirement Accounts WIki:
http://wiki.biblepay.org/Retirement_Accounts

Tools >> Debug Console

exec retirementbalance
exec tradehistory
exec orderbook
exec listorders
exec order [  Buy/Sell/Cancel ]   Qty  Symbol [Price]

I placed a buy RBBP order, 1000 RBBP at 0.5 BBP each
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 14, 2017, 10:19:00 am
Im 34.208, been 18+ hours active, still hummin!

Retirement Accounts WIki:
http://wiki.biblepay.org/Retirement_Accounts

Tools >> Debug Console

exec retirementbalance
exec tradehistory
exec orderbook
exec listorders
exec order [  Buy/Sell/Cancel ]   Qty  Symbol [Price]

I placed a buy RBBP order, 1000 RBBP at 0.5 BBP each
Sweet, thats cool, well let me write my retirement balance first before we trade.
Mine is "exec retirementbalance" 572054
Now Im going to trade with you:   exec order sell 1000 rbbp .5
exec orderbook
I see that in order to see this orderbook properly, you have to drag and widen your RPC console out! Please widen it then you can see matching sales and buys
Togo I dont see you in the orderbook.
I just did an exec order buy 5000 rbbp .5
Can you please try an opposing sell now?

Also please write your balance down first so we can see if it changes.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 14, 2017, 10:30:34 am
08:53:40
exec listorders
{
  "Command": "listorders",
  "#": 0
}

08:55:48
exec order buy 1000 rbbp .5
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 1000,
  "Price": 0.5,
  "Rec Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Placing Order": "000000000000000000000000000000003a5a5883a8d0f1f7f18218437bd9f07a"
}

09:01:15
exec listorders
{
  "Command": "listorders",
  "#": 0,
  "#": 1,
  "Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Hash": "000000000000000000000000000000003a5a5883a8d0f1f7f18218437bd9f07a",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 0.5
}

09:01:31
exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 74270
}

10:20:35
exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 75411
}

(I have one thread mining, so I think my retirement balance keeps going up)

10:21:50
exec listorders
{
  "Command": "listorders",
  "#": 0,
  "#": 1,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "000000000000000000000000000000003fd98b148cfb8f195d18d2c585157345",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1000,
  "BBP_Price": 0.5,
  "#": 2,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "00000000000000000000000000000000c054dac5a0557245009b1bcf5a39e04b",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 500,
  "BBP_Price": 0.5,
  "#": 3,
  "Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Hash": "000000000000000000000000000000003a5a5883a8d0f1f7f18218437bd9f07a",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 0.5,
  "#": 4,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000002e2d7d5b52d8193fcd654e3cdbdb58a",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 5000,
  "BBP_Price": 0.5,
  "#": 5,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "00000000000000000000000000000000028e254a8d464cd4d5740c70c4b7f193",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 0.5
}

10:24:29
getinfo
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 7569.69500000,
  "privatesend_balance": 0.00000000,
  "blocks": 39347,
  "timeoffset": 3,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.3709311342166779,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

10:26:43
exec order sell 5000 RBBP 0.5
{
  "Command": "order",
  "Action": "SELL",
  "Symbol": "RBBP",
  "Qty": 5000,
  "Price": 0.5,
  "Rec Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Placing Order": "00000000000000000000000000000000126ea3b627a26003fbbc8bec87d39239"
}

10:26:52
exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 75982
}

10:27:06
exec tradehistory
{
}

10:27:12
exec listorders
{
  "Command": "listorders",
  "#": 0,
  "#": 1,
  "Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Hash": "00000000000000000000000000000000126ea3b627a26003fbbc8bec87d39239",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 5000,
  "BBP_Price": 0.5,
  "#": 2,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "000000000000000000000000000000003fd98b148cfb8f195d18d2c585157345",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1000,
  "BBP_Price": 0.5,
  "#": 3,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "00000000000000000000000000000000c054dac5a0557245009b1bcf5a39e04b",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 500,
  "BBP_Price": 0.5,
  "#": 4,
  "Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Hash": "000000000000000000000000000000003a5a5883a8d0f1f7f18218437bd9f07a",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 0.5,
  "#": 5,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000002e2d7d5b52d8193fcd654e3cdbdb58a",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 5000,
  "BBP_Price": 0.5,
  "#": 6,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "00000000000000000000000000000000028e254a8d464cd4d5740c70c4b7f193",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 0.5
}

10:28:19
getinfo
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 7598.22300000,
  "privatesend_balance": 0.00000000,
  "blocks": 39350,
  "timeoffset": 3,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.7919541757803531,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Hmmmm
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 14, 2017, 10:37:48 am
I see my wallet sent the escrow but nothing happened- is your wallet unlocked btw?

Also please see if there is an error in your debug.log, something about Unable to send escrow for trade?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 14, 2017, 10:53:26 am
Hmm I dont believe my testnet wallet is locked, not seeing a locked symbol in bottom right either?

Heres a paste of my testnet3/debug.log:   https://pastebin.com/YLDU9uSa

Looks like my log is 6 hours ahead of BiblePay RPC


10:28:45
exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 75982
}

10:47:01
getinfo
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 30880.20853400,
  "privatesend_balance": 0.00000000,
  "blocks": 39360,
  "timeoffset": 3,
  "connections": 8,
  "proxy": "",
  "difficulty": 1.357478716573109,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

10:47:15
exec tradehistory
{
}

10:47:25
exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 76124
}

10:50:23
getinfo
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 15373.66638601,
  "privatesend_balance": 0.00000000,
  "blocks": 39361,
  "timeoffset": 3,
  "connections": 8,
  "proxy": "",
  "difficulty": 2.185374434327694,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

10:51:51
exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 76267
}

Hmm my tBBP balance has been changing >.>

(Ill try to keep helping testing, Ill keep periodically checking the thread, Im at work atm hehehe, Dont tell my boss :P)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 14, 2017, 10:57:02 am
I have an issue with my controller node not syncing for 29 hours . 
It happened after I upgraded the sanct node to v "1.0.5.8" . 

Windows wallet is still v.1.0.5.6

telnet to sanct node at port 4001 connects np.

Code: [Select]
mnsync status


11:50:02
{
  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",
  "Attempt": 0,
  "IsBlockchainSynced": false,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true
}


11:52:55
masternode start-alias MNode1
11:52:55
{
  "alias": "MNode1",
  "result": "failed",
  "errorMessage": "Sync in progress. Must wait until sync is complete to start Masternode"
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 14, 2017, 11:43:17 am
hi,
exists anybody except ADMIN whom working stable masternode?


yauWFekmt47YpzzQaZxFRkM7Zk5RjGQTsa- one 1mln please

ill try setup masternode on 2 clean machines(linuxmasternode+wincontroller),may be problem is with my big setups

thanks
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 14, 2017, 12:04:10 pm
I have an issue with my controller node not syncing for 29 hours . 
It happened after I upgraded the sanct node to v "1.0.5.8" . 

Windows wallet is still v.1.0.5.6

telnet to sanct node at port 4001 connects np.

Code: [Select]
mnsync status


11:50:02
{
  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",
  "Attempt": 0,
  "IsBlockchainSynced": false,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true
}


11:52:55
masternode start-alias MNode1
11:52:55
{
  "alias": "MNode1",
  "result": "failed",
  "errorMessage": "Sync in progress. Must wait until sync is complete to start Masternode"
}
whats the IP of the node that wont sync? Ill check to see if you were banned.
Also see if you delete your banlist.dat and restart you may sync?
Next if it does not sync then check the end of the debug.log for an error.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 14, 2017, 12:07:37 pm
Hmm I dont believe my testnet wallet is locked, not seeing a locked symbol in bottom right either?

Heres a paste of my testnet3/debug.log:   https://pastebin.com/YLDU9uSa

Looks like my log is 6 hours ahead of BiblePay RPC


10:28:45
exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 75982
}

(Ill try to keep helping testing, Ill keep periodically checking the thread, Im at work atm hehehe, Dont tell my boss :P)


LOL on the boss.  Hmm, just to verify, your wallet is not encrypted is it?  If not then its probably not locked either.
Maybe we can try this backward as I dont see anything in the log so I would need to add special logging for this but first, maybe if you try selling and I try buying?

Try to sell a different quantity I just did this:
exec order buy 8000 rbbp .01

Try to Sell 8000 ?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 14, 2017, 12:14:55 pm
12:11:48
exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 76552
}

12:11:51
getinfo
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 7655.27900000,
  "privatesend_balance": 0.00000000,
  "blocks": 39416,
  "timeoffset": 3,
  "connections": 8,
  "proxy": "",
  "difficulty": 1.647270259400764,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

12:12:10
exec tradehistory
{
}

12:12:29
exec order sell 8000 rbbp .01
{
  "Command": "order",
  "Action": "SELL",
  "Symbol": "RBBP",
  "Qty": 8000,
  "Price": 0.01,
  "Rec Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Placing Order": "000000000000000000000000000000006df59e1a314da836df3fca893b902280"
}

12:12:35
exec listorders
{
  "Command": "listorders",
  "#": 0,
  "#": 1,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000044bdacb5f92541ae96aa451545cd7427",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 8000,
  "BBP_Price": 0.01,
  "#": 2,
  "Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Hash": "00000000000000000000000000000000126ea3b627a26003fbbc8bec87d39239",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 5000,
  "BBP_Price": 0.5,
  "#": 3,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "000000000000000000000000000000003fd98b148cfb8f195d18d2c585157345",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1000,
  "BBP_Price": 0.5,
  "#": 4,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "00000000000000000000000000000000c054dac5a0557245009b1bcf5a39e04b",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 500,
  "BBP_Price": 0.5,
  "#": 5,
  "Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Hash": "000000000000000000000000000000003a5a5883a8d0f1f7f18218437bd9f07a",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 0.5,
  "#": 6,
  "Address": "yggy2oVuVKTsVJvLycK6V9HW7qP9ybVcbF",
  "Hash": "000000000000000000000000000000006df59e1a314da836df3fca893b902280",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 8000,
  "BBP_Price": 0.01,
  "#": 7,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000002e2d7d5b52d8193fcd654e3cdbdb58a",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 5000,
  "BBP_Price": 0.5,
  "#": 8,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "00000000000000000000000000000000028e254a8d464cd4d5740c70c4b7f193",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 0.5
}

12:12:45
exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 76552
}

12:12:50
getinfo
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 7655.27900000,
  "privatesend_balance": 0.00000000,
  "blocks": 39416,
  "timeoffset": 3,
  "connections": 5,
  "proxy": "",
  "difficulty": 1.647270259400764,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 14, 2017, 12:19:58 pm
Settings >> Encrypt Wallet... shows as option
Settings  >> Change passphrase,  clicked but nothing happens
And no lock symbol in bottom right hmmm

I sent 100 tBBP to 8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW, no password promp popped up to send
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 14, 2017, 12:29:09 pm
Also very strange

I remembered I had like 30+ million tBBP coins

From Yesterday:
12:50:24
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 33548253.56424391,
  "privatesend_balance": 0.00000000,
  "blocks": 38467,
  "timeoffset": 3,
  "connections": 7,
  "proxy": "",
  "difficulty": 0.2178060202002745,
  "testnet": true,
  "keypoololdest": 1507446796,
  "keypoolsize": 1003,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

And now after running some of these retirement commands I now have:

Today/This Morning
10:24:29
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 7569.69500000,
  "privatesend_balance": 0.00000000,
  "blocks": 39347,
  "timeoffset": 3,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.3709311342166779,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Im not sure why I didnt notice this sooner O_O

Inbetween those two getinfo commands, my Console window history shows I ran:

setgenerate false
setgenerate true 2
setgenerate true 1
help
exec retirementbalance
exec tradehistory
exec listorders
exec order buy 1000 rbbp .5
exec listorders
exec listorders
exec retirementbalance
exec retirementbalance
exec listorders
exec tradehistory
exec retirementbalance
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 14, 2017, 12:51:43 pm
Also very strange

I remembered I had like 30+ million tBBP coins

From Yesterday:
12:50:24
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 33548253.56424391,
  "privatesend_balance": 0.00000000,
  "blocks": 38467,
  "timeoffset": 3,
  "connections": 7,
  "proxy": "",
  "difficulty": 0.2178060202002745,
  "testnet": true,
  "keypoololdest": 1507446796,
  "keypoolsize": 1003,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

And now after running some of these retirement commands I now have:

Today/This Morning
10:24:29
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 7569.69500000,
  "privatesend_balance": 0.00000000,
  "blocks": 39347,
  "timeoffset": 3,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.3709311342166779,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Im not sure why I didnt notice this sooner O_O

Inbetween those two getinfo commands, my Console window history shows I ran:

setgenerate false
setgenerate true 2
setgenerate true 1
help
exec retirementbalance
exec tradehistory
exec listorders
exec order buy 1000 rbbp .5
exec listorders
exec listorders
exec retirementbalance
exec retirementbalance
exec listorders
exec tradehistory
exec retirementbalance


Good catch, yeah, I had 80MM tbbp yesterday also, and now only have 300K.

Alright this was worthwhile, I have a huge bug to fix, so lets stop testing retirement accounts til I get back with the patch.

To free up your missing funds, just restart the wallet and it will come back.  (Its technically still there, its just not adding things up right after executing the retirement commands).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 14, 2017, 12:57:50 pm
Hehehe, ok restarted wallet GUI and my coins are back:

12:56:46
getinfo
{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 38499928.07755201,
  "privatesend_balance": 0.00000000,
  "blocks": 39446,
  "timeoffset": 1,
  "connections": 7,
  "proxy": "",
  "difficulty": 0.9647431179155013,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Glad I could help!  :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 14, 2017, 01:36:24 pm
admin+togo=thanks for no help=´

my 500k in masternode wallet was disappeared=

now im broken stick on masternode and all with bbp=

no dev help

happy time with this shit coin

bye

togo+admin= 2 testers= nice, noob coin
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 14, 2017, 02:23:44 pm
lol Klondike, I struggled for hours/days to get my first masternode setup and wrote my own notes/guide, I had to dig into multiple Dash guides to help as well


Lead Dev Sanctuary/Masternode Wiki Guide:
http://wiki.biblepay.org/Create_Sanctuary

My Sanctuary/Masternode Forum Notes
http://forum.biblepay.org/index.php?topic=16.msg151#msg151


Where are you stuck currently?

Are you setting up a Hot Masternode or a Cold Masternode?

Which masternode are you?  ---> https://i.imgur.com/6wslA4K.png

You definitely helped point out the rpcport issue that I found in my notes and you got dev to update on the wiki.

We are the 1st testers. Im just a junior-mid level programmer in real life (though recruiters and resume bots like to say Im a senior programmer...), I have no idea what Im doing, just stumbling along. Im totally new to cryptocurrency as of 3 months ago. But Im willing to dig in, get lost and try to figure things out :)


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 14, 2017, 04:13:33 pm
admin+togo=thanks for no help=´

my 500k in masternode wallet was disappeared=

now im broken stick on masternode and all with bbp=

no dev help

happy time with this shit coin

bye

togo+admin= 2 testers= nice, noob coin

Mine are humming along with no problem, and Im running on 3 different platforms:  Jessie, Vultr debian, and Windows, and havent had any problems.

Maybe just come back after you let the big dogs figure it out.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 14, 2017, 05:14:35 pm
whats the IP of the node that wont sync? Ill check to see if you were banned.
Also see if you delete your banlist.dat and restart you may sync?
Next if it does not sync then check the end of the debug.log for an error.


I 've got it fixed by deleting blocks and chainstate dirs from testnet3 dir.

after the wallet re-synced everything looks good.

it was on my controller node FYI.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 14, 2017, 05:18:53 pm
hi,
exists anybody except ADMIN whom working stable masternode?


yauWFekmt47YpzzQaZxFRkM7Zk5RjGQTsa- one 1mln please

ill try setup masternode on 2 clean machines(linuxmasternode+wincontroller),may be problem is with my big setups

thanks

sent you 1 mil:

To: yauWFekmt47YpzzQaZxFRkM7Zk5RjGQTsa
Debit: -1 000 000.00000000 tBiblepay
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 05:39:55 am
TIRAS thx for tBBP,you read PM here on forum?

may be im found my problem where i did mistake :

im always sending from controller-win wallet 500 000 tBBP to linux wallet-masternode and its probably bad.And i made getaccountaddress [MASTERNODE_ALIAS] on linux-masternode wallet.

dont understand this english sentences:

Record the BBP Address that is emitted from the above command in notepad as ESCROW_ADDRESS).
Next, send some escrow funds to the new escrow address you created in the above step; this escrow is used by sanctuary to provide cool services to users, such as instantsend and retirement account trading:
      sendtoaddress <ESCROW_ADDRESS> 500000

can you explain pls easy this to 1 sentence?

i have to send from other wallet to this controller-win-wallet 500k or i can start controller with exists 500k in wallet?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 06:36:17 am
TOGOSHIKEGATE
your tutorial is weird

Quote
1. Generate private key on Sanctuary Masternode Linux machine

./biblepay-cli -testnet masternode genkey

(Store this as your MASTERNODE_PRIVATE_KEY)

2. Controller Wallet - Show Proof of Coins
getaccountaddress MASTERNODE_NAME #creates MASTERNODE_ADDRESS
sendtoaddress MASTERNODE_ADDRESS 500000 "" ""

3. Wait for 15 confirmations
(Note: Testnet chain mines blocks every 1 minute,
turn on miner if no one else is mining so confirmations can go through: setgenerate true 1)


masternode-address is what?where? when we made masternode wallet? we will be sending 500k from wincontroller wallet to masternodelinux wallet? or how? this is mishmash for all users

15 confirmations? i see 6
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 07:00:21 am
Klondike,
- You only have to send the 500,000 BBP once From somewhere, To the Controller wallet escrow address (using the sendtoaddress command), Once per COLD sanctuary.  Once the funds are sent they are LOCKED.  (see masternode outputs)
- If you want to perform a dry run of emptying out the funds, follow the paragraph we posted about COIN CONTROL.
- If you need more Testnet funds paste your address here and then you can start more
- You cannot accidentally spend the 500,000 locked escrow unless you accidentally went in coin control and unlocked the funds
- The main part of the guide (up to the FAQ beginning) covers everything you need to do to start a new sanctuary, you dont need to follow whats in the FAQ unless you are having troubles

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 07:04:41 am
admin why are you writing still in puzzles?

togoshigekata got in tutorial this

Quote
2. Controller Wallet - Show Proof of Coins
getaccountaddress MASTERNODE_NAME #creates MASTERNODE_ADDRESS
sendtoaddress MASTERNODE_ADDRESS 500000 "" ""

how can to do this command in controller windowswallet when i dont know masternode_adress???

ADMIN and your tutorial http://wiki.biblepay.org/Create_Masternode is bad:

Quote
4) Now on the SANCTUARY WALLET, open biblepay.conf from (Linux: ~/.biblepaycore).

Add:

rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
rpcport=40009
listen=1
server=1
daemon=1
logtimestamps=1
externalip=SANCTUARY_PUBLIC_IP:40001 (if this doesn't work, try just IP without :40001 and restart)
maxconnections=256
masternode=1
masternodeprivkey=SANCTUARY_PRIVATE_KEY
Make sure to replace rpcuser and rpcpassword with your own.

5) Close and restart this sanctuary node.

how you tested this?  you cant add new info to config and then stop wallet, doesnt working: you have to stop wallet on linux and then add to config new infos and then run

 ::)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 08:04:06 am
my steps is this ... show/tell/write me,where i doing mistakes: may be this helps all users.....

1.setup VPS by togo tutorial= easy user-friendly step-by-step = working good
2.run windows wallet and setup testnet=1 in config + syncing chain = working good
3.when is VPS done, run ./biblepayd -testnet -daemon and wait for syncing blocks = working good
4.in VPS ./biblepay-cli -testnet -daemon setgenerate true 0 i dont want mining with VPS = working good
5.in VPS ./biblepay-cli -testnet masternode genkey i got SANCTUARY_PRIVATE_KEY  = working good
6.in controller-windows wallet do in debug win this command getaccountaddress TEST  = working good
7.sent from other wallet to my controller wallet TEST address 500 000 tBBP  = working good
8.in controller-windows wallet in debug win using this command masternode outputs i get TRANSACTIONHASH+ INDEX (1 or 0)
9.in controller-windows wallet open masternode.config and add this line TEST SPACE [VPSIP:40001] SPACE [SANCTUARY_PRIVATE_KEY] SPACE [TRANSACTIONHASH] SPACE [INDEX]  = working good
10.in controller-windows wallet open wallet configuration file and add this
Quote
testnet=1
genproclimit=0
rpcuser=aaaa123
rpcpassword=bbbb123
rpcallowip=127.0.0.1
rpcport=9998
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

working good

11.in VPS close/stop wallet and add this

Quote
rpcuser=aaaa123
rpcpassword=bbbb123
rpcallowip=127.0.0.1
rpcport=40009
listen=1
server=1
daemon=1
logtimestamps=1
externalip=VPS_IP:40001 (if this doesn't work, try just IP without :40001 and restart)
maxconnections=256
masternode=1
masternodeprivkey=SANCTUARY_PRIVATE_KEY

working good

12. in controller-windows wallet in debug win run this command masternode start-alias TEST .... = working good
13.compiling watchman this commands in VPS

Quote
sudo apt update
sudo apt install git python-virtualenv virtualenv
cd ~/.biblepaycore
git clone https://github.com/biblepay/watchman.git
cd watchman
virtualenv venv
venv/bin/pip install -r requirements.txt
  done

14. in nano.watchman.config  deleteing # in testnet and add # in mainnet  done
15. then run watchman this command venv/bin/python bin/watchman.py when you run it,you see nothing
16.run this command in VPS crontab -e and add this line at the end

Quote
* * * * * cd .biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

im still PRE-ENABLED OR NEW_START_REQUIREDE in CONTROLLER-WINDOWS WALLET  :-\

(https://i.imgur.com/YIFVJqs.png)
(https://i.imgur.com/1lNHEA6.png)
(https://i.imgur.com/gRDVl46.png)
(https://i.imgur.com/D3Z1G0e.png)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 08:45:42 am
Klondike for the 3rd time your watchman isnt running properly.

Run the command you have in your crontab without the devnull suffix on the end, and see what the error is.

Your "guide" is too fragile for everyones use.
Thats why we have a wiki guide, its going to cover the general populus.

If another error is discovered let us know and we will add to the wiki.

Make a video for everyone maybe you can help other people out if you are King of IT?

I think we have already passed other masternode guides in accuracy, as obviosuly no one is citing other coins guides as being better, right?

Didnt I mention other guides dont even show where to execute the command from, controller or sanctuary? LOL you would not even be able to get it running to begin with without our wiki guide.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 08:49:17 am
Hmm I dont believe my testnet wallet is locked, not seeing a locked symbol in bottom right either?

Heres a paste of my testnet3/debug.log:   https://pastebin.com/YLDU9uSa

Looks like my log is 6 hours ahead of BiblePay RPC


10:28:45
exec retirementbalance
{
  "Command": "retireme\
  "balance": 30880.20853400,
  "privatese\

Hmm my tBBP balance has been changing >.>

(Ill try to keep helping testing, Ill keep periodically checking the thread, Im at work atm hehehe, Dont tell my boss :P)

Togo, I just pushed out 1059 if you want to upgrade and continue debugging retirement accounts now.

This new version should fix the bug of the diminishing balance, and also I added a new command called "exec listdebug" that will show what your wallet is doing when it tries to send the escrow for the retirement trade to another node, maybe that will reveal why our trade didnt execute.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 09:20:03 am
Quote
Klondike for the 3rd time your watchman isnt running properly.
Run the command you have in your crontab without the devnull suffix on the end, and see what the error is.

when i run watchman what i have to see?  example: watchman running? or?

(https://i.imgur.com/qXCRoOu.png)
(https://i.imgur.com/4wV3Gfh.png)
(https://i.imgur.com/NU2ZpY9.png)


togo had same errors in watchman...is this fixing? im stuck on red command

Quote
=== Watchman Database Poking

sudo apt-get install sqlite3
sqlite3 Watchman
sqlite>
select * from votes;
.table <enter>

== OUTPUT:
1|2|2|1|2017-11-13 16:20:01.419328|2017-11-13 16:20:01.419338|2017-11-13 16:20:01.419344|f2ff8b0970c959e1ea750234593ff358f9ea7ce8e162a6c6ab50c6b31035330c

governance_objects  proposals           signals             votes
outcomes            settings            superblocks         watchdogs

CTRL + D to exit sqlite
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 10:40:06 am
when i run watchman what i have to see?  example: watchman running? or?



togo had same errors in watchman...is this fixing? im stuck on red command


I dont see a problem with your config off the bat.  But for the 4th time, what happens when you *type what is in your crobtab -e into the command line verbatim*?

Next, what is your IP?  I want to look at your masternode status.

Next, what happens when you type select * from votes in Togos guide?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 15, 2017, 11:42:10 am
Togo, I just pushed out 1059 if you want to upgrade and continue debugging retirement accounts now.

Awesome!, I downloaded latest Windows 32 exe from biblepay.org but looks like its version 1.0.5.6

Updating my Linux Masternode right now, I can test from there for now

Edit, updated to 1.0.5.9 on Linux, sadly my account doesnt have any RBBP or BBP, so Im going to let it mine for a bit



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 12:05:43 pm

I dont see a problem with your config off the bat.  But for the 4th time, what happens when you *type what is in your crobtab -e into the command line verbatim*?

Next, what is your IP?  I want to look at your masternode status.

Next, what happens when you type select * from votes in Togos guide?
my IP ending 106 ...

and im wrote STUCK: dont understand what are you meaning
Quote
"what happens when you *type what is in your crobtab -e into the command line verbatim*?"
this ic command in putty  * from votes

 :-X :-X :-X

togo or admin : have you teamviewer? you can via remote check where have i problem. Its sad that only you,togo,tiras we are only the testers masternodes ...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 12:54:48 pm
my IP ending 106 ...

and im wrote STUCK: dont understand what are you meaning
 :-X :-X :-X

togo or admin : have you teamviewer? you can via remote check where have i problem. Its sad that only you,togo,tiras we are only the testers masternodes ...
Oh OK 106, new_start_required OK, yeah something is stll wrong then.  When you typed venv/bin/python bin/watchman.py earlier, and saw no error message it led me to believe you were working fine.

So what I would really like you to do next is open your crontab -e, and copy the command, the whole command including the cd && part, to the command line and type it in, and see if there is an error. 

Next, ensure if you are running venv/bin/python bin/watchman.py as root, that biblepayd is running as root also. On the same box.  As your watchman account must match your biblepayd account.

Another words, you cant run biblepayd as "ubuntu" or "debian" and watchman as "root".  Both must be root if one is root.  Or both must be ubuntu if one is ubuntu.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 12:57:27 pm
Awesome!, I downloaded latest Windows 32 exe from biblepay.org but looks like its version 1.0.5.6

Updating my Linux Masternode right now, I can test from there for now

Edit, updated to 1.0.5.9 on Linux, sadly my account doesnt have any RBBP or BBP, so Im going to let it mine for a bit

Thats sweet, I think I have a command that lets me send you retirement coins now (this can only be done via biblepayers who want to transfer retirement coins to retirementcoins btw of course), what is your receiving address, lets test that too?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 01:26:12 pm
im still as root all commands
after nightshift ill try to do command from crontab to command line
6:20 morning EU TIME ill be here: your -8hour,dont know what USA TIME ZONE are you.. im +1hours EU

added line in crontab line is this  * * * * * cd .biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

what command from this i have to use like run command? this cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py  ?

where i see if watchman running? Verify the output is empty?

thanks

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 01:34:00 pm
im still as root all commands
after nightshift ill try to do command from crontab to command line
6:20 morning EU TIME ill be here: your -8hour,dont know what USA TIME ZONE are you.. im +1hours EU

added line in crontab line is this  * * * * * cd .biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

what command from this i have to use like run command? this cd  .biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1 ?

where i see if watchman running?

thanks

Try to cd to ~/.biblepaycore/watchman, then run this command as root:

Code: [Select]
cd .biblepaycore/watchman && ./venv/bin/python bin/watchman.py

This is what you pasted from your crontab.

Which looks incorrect.

It should be:
cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py



Rob
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 01:40:56 pm
this is need on the end?   >/dev/null 2>&1?

yeah cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 02:03:03 pm
this is need on the end?   >/dev/null 2>&1?

yeah cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1
Ive been saying for 2 pages now to run the command found in your crontab WITHOUT THE /dev/null suffix!  Thats why I left it off in my example.

No wonder you think our guides suck.

So again, what i want you to do is change your crontab to:
cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

Then I want you to exit crontab and cd to ~/.biblepaycore/watchman

Then I want you to execute the command:
cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py


Which is what is in the crontab minus the suffix.

Then I want you to paste the outcome (which should be blank if all is working)

And I want you to tell us if your biblepayd is already running or not.





Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 15, 2017, 02:13:39 pm
Thats sweet, I think I have a command that lets me send you retirement coins now (this can only be done via biblepayers who want to transfer retirement coins to retirementcoins btw of course), what is your receiving address, lets test that too?

Assuming this is command to get default address?
./biblepay-cli getaccountaddress ""

Address:  yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc

Edit: I just tested sending myself 300k tBBP coins and the address is correct :)

[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 0.00000000,
  "retirement_account_balance": 0,
  "unconfirmed_balance": 300000.00000000,
  "immature_balance": 124166.83733995,
  "txcount": 17,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "keys_left": 998,
  "paytxfee": 0.00000000
}

Is there an unconfirmed retirement balance?,
I assume I will get some tRBBP once the immature tBBP coins I have mature?

But yes please send me some! :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 15, 2017, 02:19:05 pm
oh Also another note:
 I still only have 500k tBBP in address/escrow for masternode/sanctuary,
 I believe you raised it to 1.5 million tBBP?  is that requirement in code yet?

Edit:
https://github.com/biblepay/biblepay/blob/master/src/main.cpp#L80
Ok cool, looks like its still 500k :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 02:30:25 pm
ADMIN ok...i understand now what you wanna from me .. thanks
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 03:24:34 pm
oh Also another note:
 I still only have 500k tBBP in address/escrow for masternode/sanctuary,
 I believe you raised it to 1.5 million tBBP?  is that requirement in code yet?

Edit:
https://github.com/biblepay/biblepay/blob/master/src/main.cpp#L80
Ok cool, looks like its still 500k :)

Yeah, still 500k in testnet.  Will confirm the Prod amount on Thanksgiving.

Hmm, let me try to send you some RBBP.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 03:26:37 pm
Assuming this is command to get default address?
./biblepay-cli getaccountaddress ""

Address:  yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc

Edit: I just tested sending myself 300k tBBP coins and the address is correct :)

[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 0.00000000,
  "retirement_account_balance": 0,
  "unconfirmed_balance": 300000.00000000,
  "immature_balance": 124166.83733995,
  "txcount": 17,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "keys_left": 998,
  "paytxfee": 0.00000000
}

Is there an unconfirmed retirement balance?,
I assume I will get some tRBBP once the immature tBBP coins I have mature?

But yes please send me some! :)

Yes, good address.  Ok I just sent you 100,000 rbbp.  I believe you have to wait for 5 confirms before you see it:


15:25:06

exec sendto401k 100000 yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc


15:25:08

{
  "Command": "sendto401k",
  "Destination Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "DefRecAddr": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "OutboundColor": "401",
  "XML": "<color>401</color><transactiontype>OCO</transactiontype><rules><expectedamount>10000000000000.0000</expectedamount><expectedrecipient>yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU</expectedrecipient><expectedcolor></expectedcolor></rules>",
  "txid": "561329bfbb61989793f78cd9f043d6660474e79e272ee3151386f4fc443d05b8"
}


Note, please dont use the exec sendto401k command yet, as there is a bug in it, will be fixed in the next version though (Im running the renegade).

Let me know if your balance increases then we can try trading again?


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 15, 2017, 03:33:55 pm
~/biblepay/src$ ./biblepay-cli exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 1001342
}

Thanks!

===========

I created some sell orders earlier but I dont think they executed:
./biblepay-cli exec order sell 5 rbbp 5
I ran same command twice on accident as well

I just created a buy order:

./biblepay-cli exec order buy 10000 rbbp 3
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 10000,
  "Price": 3,
  "Rec Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Placing Order": "00000000000000000000000000000000fb1dd17f8688dcfed496632d5f035bd8"
}

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 03:47:29 pm
~/biblepay/src$ ./biblepay-cli exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 1001342
}

Thanks!

===========

I created some sell orders earlier but I dont think they executed:
./biblepay-cli exec order sell 5 rbbp 5
I ran same command twice on accident as well

I just created a buy order:

./biblepay-cli exec order buy 10000 rbbp 3
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 10000,
  "Price": 3,
  "Rec Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Placing Order": "00000000000000000000000000000000fb1dd17f8688dcfed496632d5f035bd8"
}

Cool, just got back to the machine.  It looks like we are getting about as far as we got yesterday.
I see your order in the orderbook, I placed my order, and see both orders in the orderbook (I did the sell 10000), I see my escrow went out of my machine, but your escrow didnt leave.

Try to do a

15:45:12

exec listdebug


15:45:12

{
  "Command": "listdebug",
  "1510782211": "PREPARING ESCROW FOR 30000.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID "
}


exec listdebug, and see if anything is there?


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 03:51:03 pm
On a side note, Togo, do you have access to the -qt version?  IE can you run the compiled biblepay-qt?  Im wondering if buying rbbp from the QT version changes any behavior.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 15, 2017, 03:56:08 pm
./biblepay-cli exec listdebug
{
  "Command": "listdebug"
}

For linux I sadly only have command line at the moment
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 04:14:07 pm
./biblepay-cli exec listdebug
{
  "Command": "listdebug"
}

For linux I sadly only have command line at the moment

10-4 on QT, no problem.

Oh wait a minute, not sure if this is it, but, trading requires a background thread, in order to "ask" the other node if its OK to trade and send the escrow out.  Im thinking possibly since you are using biblepay-cli, maybe the thread isnt starting.  Could you try running biblepayd in another window and leave it running, then try the 'exec orderbook' a couple times from cli? 

In the mean time Ill start compiling windows so we can test win-win tomorrow.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 15, 2017, 04:26:49 pm
So I opened a 2nd instance of Putty and connected to AWS Ubuntu server and ran ./biblepayd -daemon

in the 1st instance, I then ran ./biblepay-cli exec orderbook 5 times

Code: [Select]
./biblepay-cli exec orderbook
{
  "0": "[S]Price Quantity  Amount   Total       (RBBP)  Price  Quantity Amount     Total   [B]",
  "0": "0.5000  1000      500.00    500.00       |RBBP| 5.0000  5         25.00     25.00       ",
  "1": "5.0000  5         25.00     525.00       |RBBP| 3.0000  10000     30000.00  30025.00    ",
  "2": "5.0000  5         25.00     550.00       |RBBP| 0.5000  1000      500.00    30525.00    ",
  "3": "                                         |RBBP| 0.5000  5000      2500.00   33025.00    ",
  "4": "                                         |RBBP| 0.5000  1000      500.00    33525.00    ",
  "5": "                                         |RBBP| 0.0100  8000      80.00     33605.00    ",
  "6": "                                         |RBBP|                                         "
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 04:31:23 pm
10-4 on QT, no problem.

Oh wait a minute, not sure if this is it, but, trading requires a background thread, in order to "ask" the other node if its OK to trade and send the escrow out.  Im thinking possibly since you are using biblepay-cli, maybe the thread isnt starting.  Could you try running biblepayd in another window and leave it running, then try the 'exec orderbook' a couple times from cli? 

In the mean time Ill start compiling windows so we can test win-win tomorrow.


So also, I just tested trading from an instance of biblepay-cli to myself and it actually worked, so I think the thread is working :)

Could you please check your log for "Trading Thread started"
and
Orig trade address %s  Orig Trade Amount %f

and see if any of that exists? 

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 04:33:01 pm
So I opened a 2nd instance of Putty and connected to AWS Ubuntu server and ran ./biblepayd -daemon

in the 1st instance, I then ran ./biblepay-cli exec orderbook 5 times

Code: [Select]
./biblepay-cli exec orderbook
{
  "0": "[S]Price Quantity  Amount   Total       (RBBP)  Price  Quantity Amount     Total   [B]",
  "0": "0.5000  1000      500.00    500.00       |RBBP| 5.0000  5         25.00     25.00       ",
  "1": "5.0000  5         25.00     525.00       |RBBP| 3.0000  10000     30000.00  30025.00    ",
  "2": "5.0000  5         25.00     550.00       |RBBP| 0.5000  1000      500.00    30525.00    ",
  "3": "                                         |RBBP| 0.5000  5000      2500.00   33025.00    ",
  "4": "                                         |RBBP| 0.5000  1000      500.00    33525.00    ",
  "5": "                                         |RBBP| 0.0100  8000      80.00     33605.00    ",
  "6": "                                         |RBBP|                                         "
}

Oh cool, well lets see if anything different is happening, I just placed a sell:
exec order sell 1100 rbbp 2.27

You want to try a buy for same amount?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 15, 2017, 04:42:53 pm
Hmmm are the prices being rounded to whole number?, I dont think I see your sell order

Code: [Select]
./biblepay-cli exec orderlist
{
  "Command": "orderlist",
  "#": 0,
  "#": 1,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000046e4601e60d451534891c6eeb990960b",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1100,
  "BBP_Price": 2,
  "#": 2,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000059b84b37ccdbdab2de88921ec0090b16",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1000,
  "BBP_Price": 7,
  "#": 3,
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Hash": "00000000000000000000000000000000eaf5580e5af715a422a3af748be2283a",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 5,
  "BBP_Price": 5,
  "#": 4,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000044f81691000e57a1571f888714925a5d",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 7,
  "#": 5,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000537acece1916dd50bdcfbbaf21ce795d",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 5,
  "BBP_Price": 5,
  "#": 6,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000d9f7a3268fbaf0b915caca43d2d9af68",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 10000,
  "BBP_Price": 3,
  "#": 7,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "000000000000000000000000000000002d024b17482a2f57ca098db92755f7c6",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 5,
  "BBP_Price": 5,
  "#": 8,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000d9f6cd1a06c7e7d84eb267e64fa083c9",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1100,
  "BBP_Price": 2,
  "#": 9,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "00000000000000000000000000000000dd439fa2940d5bc39bc09ce5d468d7cc",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 9.199999999999999,
  "#": 10,
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Hash": "00000000000000000000000000000000fb1dd17f8688dcfed496632d5f035bd8",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 10000,
  "BBP_Price": 3
}

./biblepay-cli exec orderbook
{
  "0": "[S]Price Quantity  Amount   Total       (RBBP)  Price  Quantity Amount     Total   [B]",
  "0": "2.0000  1100      2200.00   2200.00      |RBBP| 9.2000  1000      9200.00   9200.00     ",
  "1": "3.0000  10000     30000.00  32200.00     |RBBP| 7.0000  1000      7000.00   16200.00    ",
  "2": "5.0000  5         25.00     32225.00     |RBBP| 5.0000  5         25.00     16225.00    ",
  "3": "5.0000  5         25.00     32250.00     |RBBP| 3.0000  10000     30000.00  46225.00    ",
  "4": "7.0000  1000      7000.00   39250.00     |RBBP| 2.0000  1100      2200.00   48425.00    ",
  "5": "                                         |RBBP|                                         "
}

Created a buy order after the above commands

./biblepay-cli exec order buy 1100 rbbp 2.27
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 1100,
  "Price": 2.27,
  "Rec Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Placing Order": "00000000000000000000000000000000925b9cb1dbd9d6ce3a42f06eaf823ba6"
}

Code: [Select]
./biblepay-cli exec orderlist
{
  "Command": "orderlist",
  "#": 0,
  "#": 1,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000046e4601e60d451534891c6eeb990960b",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1100,
  "BBP_Price": 2,
  "#": 2,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000059b84b37ccdbdab2de88921ec0090b16",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1000,
  "BBP_Price": 7,
  "#": 3,
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Hash": "00000000000000000000000000000000eaf5580e5af715a422a3af748be2283a",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 5,
  "BBP_Price": 5,
  "#": 4,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000044f81691000e57a1571f888714925a5d",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 7,
  "#": 5,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000537acece1916dd50bdcfbbaf21ce795d",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 5,
  "BBP_Price": 5,
  "#": 6,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000d9f7a3268fbaf0b915caca43d2d9af68",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 10000,
  "BBP_Price": 3,
  "#": 7,
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Hash": "00000000000000000000000000000000925b9cb1dbd9d6ce3a42f06eaf823ba6",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1100,
  "BBP_Price": 2.27,
  "#": 8,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "000000000000000000000000000000002d024b17482a2f57ca098db92755f7c6",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 5,
  "BBP_Price": 5,
  "#": 9,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000d9f6cd1a06c7e7d84eb267e64fa083c9",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1100,
  "BBP_Price": 2,
  "#": 10,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "00000000000000000000000000000000dd439fa2940d5bc39bc09ce5d468d7cc",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 9.199999999999999,
  "#": 11,
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Hash": "00000000000000000000000000000000fb1dd17f8688dcfed496632d5f035bd8",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 10000,
  "BBP_Price": 3
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec orderbook
{
  "0": "[S]Price Quantity  Amount   Total       (RBBP)  Price  Quantity Amount     Total   [B]",
  "0": "2.0000  1100      2200.00   2200.00      |RBBP| 9.2000  1000      9200.00   9200.00     ",
  "1": "3.0000  10000     30000.00  32200.00     |RBBP| 7.0000  1000      7000.00   16200.00    ",
  "2": "5.0000  5         25.00     32225.00     |RBBP| 5.0000  5         25.00     16225.00    ",
  "3": "5.0000  5         25.00     32250.00     |RBBP| 3.0000  10000     30000.00  46225.00    ",
  "4": "7.0000  1000      7000.00   39250.00     |RBBP| 2.2700  1100      2497.00   48722.00    ",
  "5": "                                         |RBBP| 2.0000  1100      2200.00   50922.00    ",
  "6": "                                         |RBBP|                                         "
}

Ok I see my buy order in the orderlist and orderbook
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 05:00:09 pm
Its possible I may have a 5 min timeout on the escrow, so lets move to a new test if you are there, a time sensitive test
I just sold 1100 for 2.29, please try to buy quick
exec order sell 1100 rbbp 2.29

then, a couple mins later, do an exec orderbook once per minute, see if that kicks it through
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 15, 2017, 05:01:21 pm
Code: [Select]
./biblepay-cli exec orderlist
{
  "Command": "orderlist",
  "#": 0,
  "#": 1,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000046e4601e60d451534891c6eeb990960b",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1100,
  "BBP_Price": 2,
  "#": 2,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000059b84b37ccdbdab2de88921ec0090b16",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1000,
  "BBP_Price": 7,
  "#": 3,
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Hash": "00000000000000000000000000000000eaf5580e5af715a422a3af748be2283a",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 5,
  "BBP_Price": 5,
  "#": 4,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "0000000000000000000000000000000044f81691000e57a1571f888714925a5d",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 7,
  "#": 5,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000537acece1916dd50bdcfbbaf21ce795d",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 5,
  "BBP_Price": 5,
  "#": 6,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000d9f7a3268fbaf0b915caca43d2d9af68",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 10000,
  "BBP_Price": 3,
  "#": 7,
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Hash": "00000000000000000000000000000000925b9cb1dbd9d6ce3a42f06eaf823ba6",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1100,
  "BBP_Price": 2.27,
  "#": 8,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "000000000000000000000000000000002d024b17482a2f57ca098db92755f7c6",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 5,
  "BBP_Price": 5,
  "#": 9,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000d9f6cd1a06c7e7d84eb267e64fa083c9",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1100,
  "BBP_Price": 2,
  "#": 10,
  "Address": "8nhyyaPy79cbUvSaMRTdJtaX7wXUo1nFdW",
  "Hash": "00000000000000000000000000000000dd439fa2940d5bc39bc09ce5d468d7cc",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 1000,
  "BBP_Price": 9.199999999999999,
  "#": 11,
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Hash": "00000000000000000000000000000000fb1dd17f8688dcfed496632d5f035bd8",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 10000,
  "BBP_Price": 3
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec orderbook
{
  "0": "[S]Price Quantity  Amount   Total       (RBBP)  Price  Quantity Amount     Total   [B]",
  "0": "2.0000  1100      2200.00   2200.00      |RBBP| 9.2000  1000      9200.00   9200.00     ",
  "1": "3.0000  10000     30000.00  32200.00     |RBBP| 7.0000  1000      7000.00   16200.00    ",
  "2": "5.0000  5         25.00     32225.00     |RBBP| 5.0000  5         25.00     16225.00    ",
  "3": "5.0000  5         25.00     32250.00     |RBBP| 3.0000  10000     30000.00  46225.00    ",
  "4": "7.0000  1000      7000.00   39250.00     |RBBP| 2.2700  1100      2497.00   48722.00    ",
  "5": "                                         |RBBP| 2.0000  1100      2200.00   50922.00    ",
  "6": "                                         |RBBP|                                         "
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec order buy 1100 rbbp 2.29
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 1100,
  "Price": 2.29,
  "Rec Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Placing Order": "0000000000000000000000000000000041346b76d79494179efbc8cfa2b1903d"
}

ok executed buy order real quick
./biblepay-cli exec order buy 1100 rbbp 2.29

but, weird I dont see your order again, very strange
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 05:11:23 pm
Hmm, let me do some more testing, its not behaving quite right.   :P
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 05:42:48 pm

Ahh, ok I see what happened, I crashed the sanctuary due to a buffer overflow.  Ok, luckily this might allow us to test a little more now, but I have to go in about 15 mins.  I restarted my sanctuary and now I can see the orders again.


So now try your orderbook, and lets try another trade :)

I just did this one, can you buy:
exec order sell 2100 rbbp 1.24

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 15, 2017, 07:50:05 pm
Code: [Select]
[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 663838.95482574,
  "retirement_account_balance": 1004565,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 0.00000000,
  "txcount": 36,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "keys_left": 1001,
  "paytxfee": 0.00000000
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 1004565
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec orderbook
{
  "0": "[S]Price Quantity  Amount   Total       (RBBP)  Price  Quantity Amount     Total   [B]",
  "0": "0.5000  1000      500.00    500.00       |RBBP| 9.2000  1000      9200.00   9200.00     ",
  "1": "1.2400  2100      2604.00   3104.00      |RBBP| 5.0000  5         25.00     9225.00     ",
  "2": "2.2700  1100      2497.00   5601.00      |RBBP| 3.0000  10000     30000.00  39225.00    ",
  "3": "2.2900  1100      2519.00   8120.00      |RBBP| 2.2900  1100      2519.00   41744.00    ",
  "4": "3.0000  10000     30000.00  38120.00     |RBBP| 2.2700  1100      2497.00   44241.00    ",
  "5": "5.0000  5         25.00     38145.00     |RBBP| 2.0000  1100      2200.00   46441.00    ",
  "6": "5.0000  5         25.00     38170.00     |RBBP| 1.0000  1         1.00      46442.00    ",
  "7": "                                         |RBBP| 0.5000  1000      500.00    46942.00    ",
  "8": "                                         |RBBP| 0.5000  5000      2500.00   49442.00    ",
  "9": "                                         |RBBP| 0.5000  1000      500.00    49942.00    ",
  "10": "                                         |RBBP| 0.0100  8000      80.00     50022.00    ",
  "11": "                                         |RBBP|                                         "
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec order buy 2100 rbbp 1.24
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 2100,
  "Price": 1.24,
  "Rec Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Placing Order": "0000000000000000000000000000000077707dd750c97dd7d21e316fe8b6e497"
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec orderbook
{
  "0": "[S]Price Quantity  Amount   Total       (RBBP)  Price  Quantity Amount     Total   [B]",
  "0": "0.5000  1000      500.00    500.00       |RBBP| 9.2000  1000      9200.00   9200.00     ",
  "1": "1.2400  2100      2604.00   3104.00      |RBBP| 5.0000  5         25.00     9225.00     ",
  "2": "2.2700  1100      2497.00   5601.00      |RBBP| 3.0000  10000     30000.00  39225.00    ",
  "3": "2.2900  1100      2519.00   8120.00      |RBBP| 2.2900  1100      2519.00   41744.00    ",
  "4": "3.0000  10000     30000.00  38120.00     |RBBP| 2.2700  1100      2497.00   44241.00    ",
  "5": "5.0000  5         25.00     38145.00     |RBBP| 2.0000  1100      2200.00   46441.00    ",
  "6": "5.0000  5         25.00     38170.00     |RBBP| 1.2400  2100      2604.00   49045.00    ",
  "7": "                                         |RBBP| 1.0000  1         1.00      49046.00    ",
  "8": "                                         |RBBP| 0.5000  1000      500.00    49546.00    ",
  "9": "                                         |RBBP| 0.5000  5000      2500.00   52046.00    ",
  "10": "                                         |RBBP| 0.5000  1000      500.00    52546.00    ",
  "11": "                                         |RBBP| 0.0100  8000      80.00     52626.00    ",
  "12": "                                         |RBBP|                                         "
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec listdebug
{
  "Command": "listdebug",
  "1510796794": "PREPARING ESCROW FOR 25.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID ",
  "1510796795": "PREPARING ESCROW FOR 30000.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID ",
  "1510796798": "PREPARING ESCROW FOR 2497.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID ",
  "1510796799": "PREPARING ESCROW FOR 25.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID ",
  "1510796864": "PREPARING ESCROW FOR 2604.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID "
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec tradehistory
{
  "11/15/2017 7:46:35 PM": "BOT 10000 RBBP @ 3.0000 TOTAL 30000.00BBP ORDER 00000000000000000000000000000000fb1dd17f8688dcfed496632d5f035bd8.",
  "11/15/2017 7:46:42 PM": "BOT 1100 RBBP @ 2.2700 TOTAL 2497.00BBP ORDER 00000000000000000000000000000000925b9cb1dbd9d6ce3a42f06eaf823ba6.",
  "11/15/2017 7:46:43 PM": "BOT 1100 RBBP @ 2.2900 TOTAL 2519.00BBP ORDER 0000000000000000000000000000000041346b76d79494179efbc8cfa2b1903d."
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 1034515
}
[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 629715.55447854,
  "retirement_account_balance": 1039531,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 0.00000000,
  "txcount": 45,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "keys_left": 995,
  "paytxfee": 0.00000000
}

Ok placed buy order!
./biblepay-cli exec order buy 2100 rbbp 1.24

Im seeing stuff in listdebug and tradehistory now!

Before buy order I had:
tBBP "balance": 663838.95482574,
tRBBP "balance": 1004565

After buy order I had:
tBBP "balance": 629715.55447854,
tRBBP "balance": 1034515

tBBP Difference:  -34123.4003472
tRBBP Difference: 29950

Hmmm, numbers seem weird, but Im not sure if multiple orders got executed
Looks like I had 1 miner thread running at the time too

Edit: Im now updated to 1.0.5.9b

Edit2: Tradehistory shows I should have:
 lost -35,016 BBP
and gained 12,200 RBBP
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 09:24:13 pm
Code: [Select]
[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 663838.95482574,
  "retirement_account_balance": 1004565,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 0.00000000,
  "txcount": 36,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "keys_left": 1001,
  "paytxfee": 0.00000000
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 1004565
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec orderbook
{
  "0": "[S]Price Quantity  Amount   Total       (RBBP)  Price  Quantity Amount     Total   [B]",
  "0": "0.5000  1000      500.00    500.00       |RBBP| 9.2000  1000      9200.00   9200.00     ",
  "1": "1.2400  2100      2604.00   3104.00      |RBBP| 5.0000  5         25.00     9225.00     ",
  "2": "2.2700  1100      2497.00   5601.00      |RBBP| 3.0000  10000     30000.00  39225.00    ",
  "3": "2.2900  1100      2519.00   8120.00      |RBBP| 2.2900  1100      2519.00   41744.00    ",
  "4": "3.0000  10000     30000.00  38120.00     |RBBP| 2.2700  1100      2497.00   44241.00    ",
  "5": "5.0000  5         25.00     38145.00     |RBBP| 2.0000  1100      2200.00   46441.00    ",
  "6": "5.0000  5         25.00     38170.00     |RBBP| 1.0000  1         1.00      46442.00    ",
  "7": "                                         |RBBP| 0.5000  1000      500.00    46942.00    ",
  "8": "                                         |RBBP| 0.5000  5000      2500.00   49442.00    ",
  "9": "                                         |RBBP| 0.5000  1000      500.00    49942.00    ",
  "10": "                                         |RBBP| 0.0100  8000      80.00     50022.00    ",
  "11": "                                         |RBBP|                                         "
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec order buy 2100 rbbp 1.24
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 2100,
  "Price": 1.24,
  "Rec Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "Placing Order": "0000000000000000000000000000000077707dd750c97dd7d21e316fe8b6e497"
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec orderbook
{
  "0": "[S]Price Quantity  Amount   Total       (RBBP)  Price  Quantity Amount     Total   [B]",
  "0": "0.5000  1000      500.00    500.00       |RBBP| 9.2000  1000      9200.00   9200.00     ",
  "1": "1.2400  2100      2604.00   3104.00      |RBBP| 5.0000  5         25.00     9225.00     ",
  "2": "2.2700  1100      2497.00   5601.00      |RBBP| 3.0000  10000     30000.00  39225.00    ",
  "3": "2.2900  1100      2519.00   8120.00      |RBBP| 2.2900  1100      2519.00   41744.00    ",
  "4": "3.0000  10000     30000.00  38120.00     |RBBP| 2.2700  1100      2497.00   44241.00    ",
  "5": "5.0000  5         25.00     38145.00     |RBBP| 2.0000  1100      2200.00   46441.00    ",
  "6": "5.0000  5         25.00     38170.00     |RBBP| 1.2400  2100      2604.00   49045.00    ",
  "7": "                                         |RBBP| 1.0000  1         1.00      49046.00    ",
  "8": "                                         |RBBP| 0.5000  1000      500.00    49546.00    ",
  "9": "                                         |RBBP| 0.5000  5000      2500.00   52046.00    ",
  "10": "                                         |RBBP| 0.5000  1000      500.00    52546.00    ",
  "11": "                                         |RBBP| 0.0100  8000      80.00     52626.00    ",
  "12": "                                         |RBBP|                                         "
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec listdebug
{
  "Command": "listdebug",
  "1510796794": "PREPARING ESCROW FOR 25.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID ",
  "1510796795": "PREPARING ESCROW FOR 30000.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID ",
  "1510796798": "PREPARING ESCROW FOR 2497.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID ",
  "1510796799": "PREPARING ESCROW FOR 25.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID ",
  "1510796864": "PREPARING ESCROW FOR 2604.00 RBBP FOR SANCTUARY yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci OLD ESCTXID "
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec tradehistory
{
  "11/15/2017 7:46:35 PM": "BOT 10000 RBBP @ 3.0000 TOTAL 30000.00BBP ORDER 00000000000000000000000000000000fb1dd17f8688dcfed496632d5f035bd8.",
  "11/15/2017 7:46:42 PM": "BOT 1100 RBBP @ 2.2700 TOTAL 2497.00BBP ORDER 00000000000000000000000000000000925b9cb1dbd9d6ce3a42f06eaf823ba6.",
  "11/15/2017 7:46:43 PM": "BOT 1100 RBBP @ 2.2900 TOTAL 2519.00BBP ORDER 0000000000000000000000000000000041346b76d79494179efbc8cfa2b1903d."
}
[email protected]:~/biblepay/src$ ./biblepay-cli exec retirementbalance
{
  "Command": "retirementbalance",
  "balance": 1034515
}
[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 629715.55447854,
  "retirement_account_balance": 1039531,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 0.00000000,
  "txcount": 45,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "keys_left": 995,
  "paytxfee": 0.00000000
}

Ok placed buy order!
./biblepay-cli exec order buy 2100 rbbp 1.24

Im seeing stuff in listdebug and tradehistory now!

Before buy order I had:
tBBP "balance": 663838.95482574,
tRBBP "balance": 1004565

After buy order I had:
tBBP "balance": 629715.55447854,
tRBBP "balance": 1034515

tBBP Difference:  -34123.4003472
tRBBP Difference: 29950

Hmmm, numbers seem weird, but Im not sure if multiple orders got executed
Looks like I had 1 miner thread running at the time too

Edit: Im now updated to 1.0.5.9b

Sweet well you should be able to do exec tradehistory, and see if that reconciles?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 09:31:30 pm
I just did a new :

21:30:47

exec order sell 5000 rbbp 1.35

If someone wants to jump on and enter an opposing buy order?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 15, 2017, 09:47:33 pm
Hey Rob, I upgraded my test node and I'm fully synced on testnet. Also just to clarify, the issue also happens on my US machines with the CST timezone and not only the European ones. I'm ready to do any test you would like me to do when you're around.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 15, 2017, 10:16:06 pm
Hey Rob, I upgraded my test node and I'm fully synced on testnet. Also just to clarify, the issue also happens on my US machines with the CST timezone and not only the European ones. I'm ready to do any test you would like me to do when you're around.

Im going to be hitting the sack in a few mins, but through the night you can fully sync in testnet, run the code, then see if you receive a CheckProofOfWork(1) log then post it.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 15, 2017, 10:33:02 pm
Im going to be hitting the sack in a few mins, but through the night you can fully sync in testnet, run the code, then see if you receive a CheckProofOfWork(1) log then post it.

Alright, should I mine at the same time or just be connected and synced to the network?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 15, 2017, 11:55:11 pm
Rob,

i did it by your instrunctions,typed and nothing... and btw: i had in crontab correct
Quote
cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1
   when you checked my screens what i posted here .. you must saw it
it looks,that all your setup is broken.Exists anybody whom working masternode except you? I dont know this person.By me nobody.It will be very hard start masternode when doesnt working still.



(https://i.imgur.com/NDS4uFD.png)

what happened when ill close controller-win-wallet and again run it? its OK?


thanks
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 01:06:02 am
Just posting that here in case you're awake when I'm not!

I have two identical boxes on testnet right now (not mining).

Edit: Woops I'm stupid editing my message.

No errors yet on testnet but this is what one of the node got when it was on mainnet and it was mining.

2017-11-16 01:53:00 ProcessNewBlock : ACCEPTED
2017-11-16 02:01:14 CheckProofOfWork(1.0): BlockHash 333e1c9e6fc52027012f734b2b701a3325591759ec6f29686879faae98a4b585, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510797674.000000, PrevBlockTime 1510797171.000000, BibleHash 0000000000072c18e0c42605b5431bd2e2343ced7942038c6a39f76ffa077225, TargetHash 000000000007e281000000000000000000000000000000000000000000000000, Forensics exec biblehash 333e1c9e6fc52027012f734b2b701a3325591759ec6f29686879faae98a4b585 1510797674 1510797171 16911
2017-11-16 02:01:14 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 16911.000000 pindexPrev f3479b24cae1e5b5fb10572b0eac0ea45492f7f4e32e88029ce72eb6cd48b1bb
2017-11-16 02:01:14 ERROR: CheckBlockHeader(): proof of work failed
2017-11-16 02:01:14 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-11-16 02:01:14 Misbehaving: 217.182.73.71:40000 (0 -> 5)
2017-11-16 02:01:14 UpdateTip: new best=333e1c9e6fc52027012f734b2b701a3325591759ec6f29686879faae98a4b585  height=16912  log2_work=57.78389  tx=28553  date=2017-11-16 02:01:14 progress=1.000000  cache=0.0MiB(7tx)
--
2017-11-16 03:03:15 ProcessNewBlock : ACCEPTED
2017-11-16 03:03:39 CheckProofOfWork(1.0): BlockHash 5468ae8523dbe8fc9d895343f0deb9f27a7d74763eb4d0cf8e71a419c77b5395, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510801402.000000, PrevBlockTime 1510801390.000000, BibleHash 00000000000677ab6388f8cd607de8c458d9083599fef6192c63b517bf3eb730, TargetHash 00000000000a858a000000000000000000000000000000000000000000000000, Forensics exec biblehash 5468ae8523dbe8fc9d895343f0deb9f27a7d74763eb4d0cf8e71a419c77b5395 1510801402 1510801390 16917
2017-11-16 03:03:39 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 16917.000000 pindexPrev 89d18d6ae6043337ed9b650244e7e4fac4004aa7d61e40e892d51ea9dd9e7955
2017-11-16 03:03:39 ERROR: CheckBlockHeader(): proof of work failed
2017-11-16 03:03:39 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-11-16 03:03:39 Misbehaving: 208.113.166.223:40000 (0 -> 5)
2017-11-16 03:03:39 UpdateTip: new best=5468ae8523dbe8fc9d895343f0deb9f27a7d74763eb4d0cf8e71a419c77b5395  height=16918  log2_work=57.785222  tx=28561  date=2017-11-16 03:03:22 progress=0.999999  cache=0.0MiB(16tx)
--
2017-11-16 03:44:09 ProcessNewBlock : ACCEPTED
2017-11-16 03:57:38 CheckProofOfWork(1.0): BlockHash 6c8efa4788a6aa5e42d2d7b5f54fe24e1f9fb4483fa707fcfe4b4c8ec0bbdf57, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510804572.000000, PrevBlockTime 1510803844.000000, BibleHash 0000000000007a70102622f79b71810b12687066d52a06d53ff74f9a59389587, TargetHash 00000000000947eb000000000000000000000000000000000000000000000000, Forensics exec biblehash 6c8efa4788a6aa5e42d2d7b5f54fe24e1f9fb4483fa707fcfe4b4c8ec0bbdf57 1510804572 1510803844 16922
2017-11-16 03:57:38 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 16922.000000 pindexPrev c49314cb92548b7722cccbb773922c48f3eb4fe9fe6a0e3c95a129312f9161c8
2017-11-16 03:57:38 ERROR: CheckBlockHeader(): proof of work failed
2017-11-16 03:57:38 Misbehaving: 208.113.166.223:40000 (5 -> 10)
2017-11-16 03:57:38 ERROR: invalid header received 6c8efa4788a6aa5e42d2d7b5f54fe24e1f9fb4483fa707fcfe4b4c8ec0bbdf57
2017-11-16 03:57:38 UpdateTip: new best=6c8efa4788a6aa5e42d2d7b5f54fe24e1f9fb4483fa707fcfe4b4c8ec0bbdf57  height=16923  log2_work=57.786245  tx=28570  date=2017-11-16 03:56:12 progress=0.999997  cache=0.0MiB(38tx)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 16, 2017, 02:44:10 am
masternode ENABLED finally? ::)

(https://i.imgur.com/NEucPKp.png)

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 05:18:27 am
hmm.. so I decided to turn mining on for one of the node and leave mining off for the other one so I could compare it and....

The node not mining didn't like the blocks of the node mining? This is what appeared immediately after:

2017-11-16 11:07:57 IsBlockPayeeValid -- ERROR: Invalid masternode payment detected at height 41101: CTransaction(hash=88bf52d0cb, ver=1, vin.size=1, vout.size=3, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 038da0000107)
    CTxOut(nValue=7749.70501005, scriptPubKey=2102678e7dc966def90b47ee67e28a)
    CTxOut(nValue=13.02700000, scriptPubKey=2102678e7dc966def90b47ee67e28a)
    CTxOut(nValue=7762.73201004, scriptPubKey=76a914e32c41f9a7dd95011fcdd66e)
2017-11-16 11:07:57 ERROR: ConnectBlock(biblepay): couldn't find masternode or superblock payments
2017-11-16 11:07:57 InvalidChainFound: invalid block=8dc6e2f72ed1ecd72d2dcdfc2349d229c7afe987d886a24edcd027ef0dffc055  height=41101  log2_work=45.429083  date=2017-11-16 11:07:52
2017-11-16 11:07:57 InvalidChainFound:  current best=4235f1419b54be4e2587ed371b1ecad7c116a1744861d429b0df37770f373340  height=41100  log2_work=45.429078  date=2017-11-16 11:07:17
2017-11-16 11:07:57 ERROR: ConnectTip(): ConnectBlock 8dc6e2f72ed1ecd72d2dcdfc2349d229c7afe987d886a24edcd027ef0dffc055 failed
2017-11-16 11:07:57 InvalidChainFound: invalid block=8dc6e2f72ed1ecd72d2dcdfc2349d229c7afe987d886a24edcd027ef0dffc055  height=41101  log2_work=45.429083  date=2017-11-16 11:07:52
2017-11-16 11:07:57 InvalidChainFound:  current best=4235f1419b54be4e2587ed371b1ecad7c116a1744861d429b0df37770f373340  height=41100  log2_work=45.429078  date=2017-11-16 11:07:17
2017-11-16 11:07:57 ProcessNewBlock : ACCEPTED
2017-11-16 11:07:58 ERROR: AcceptBlockHeader: block is marked invalid
2017-11-16 11:07:58 ERROR: invalid header received 8dc6e2f72ed1ecd72d2dcdfc2349d229c7afe987d886a24edcd027ef0dffc055
2017-11-16 11:08:43 ERROR: AcceptBlockHeader: prev block invalid
2017-11-16 11:08:43 Misbehaving: 94.130.49.121:40001 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-11-16 11:08:43 ERROR: invalid header received 8e4bf23f0f469470c24c70fd52d35cac975b36df65a1f5c99f05edae5be0132f
2017-11-16 11:08:43 ERROR: AcceptBlockHeader: prev block invalid
2017-11-16 11:08:43 Misbehaving: [2a01:4f8:10b:26e3::2]:34718 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-11-16 11:08:43 ERROR: invalid header received 8e4bf23f0f469470c24c70fd52d35cac975b36df65a1f5c99f05edae5be0132f
2017-11-16 11:08:49 ERROR: AcceptBlockHeader: prev block invalid
2017-11-16 11:08:49 Misbehaving: [2001:0:9d38:6ab8:34dd:1fdc:d97b:d656]:54081 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-11-16 11:08:49 ERROR: invalid header received 8e4bf23f0f469470c24c70fd52d35cac975b36df65a1f5c99f05edae5be0132f

94.130.49.121 and 2a01:4f8:10b:26e3::2 is the same machine which is the node I just activated mining on btw.

I didn't see any error on the mining node and it is still happily mining.

The node mining is now on block 41112 while the other one seems to be stuck on 41100.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 16, 2017, 06:31:04 am
it looks,that we are stuck on 41100
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 09:14:43 am
Rob,

i did it by your instrunctions,typed and nothing... and btw: i had in crontab correct    when you checked my screens what i posted here .. you must saw it
it looks,that all your setup is broken.Exists anybody whom working masternode except you? I dont know this person.By me nobody.It will be very hard start masternode when doesnt working still.



(https://i.imgur.com/NDS4uFD.png)

what happened when ill close controller-win-wallet and again run it? its OK?


thanks


That command you ran is good.  When it results in an empty result, Watchman is working.  I see your IP is working on the list also, so its obviously working.  The trick is to get the exact command that runs in the crontab working from the command line, then ensure its in the crontab, and then every 5 mins when it runs, your watchdog will not squeal out to the network that your node is down.

I dont think our guide is bad.  I think it needs a couple rough edges polished.  Ive already edited it based on Togo and Your issues over the last 2 days.

What we need is someone to come in here and start a new one and give us fresh advice.  Anyone who wants to start a testnet Sanctuary,
run the Wiki.biblepay.org/Create_Masternode Guide, and let us know if you think it is lacking.  We have to also take into account that it was written in English, and we have no Polish translation, so Im sure communication is part of the problem.  Also, keep in mind not everyone will use biblepayd to run the commands, for example, I set up my Cold node using the windows RPC, and used Samba and nano for all my settings changes.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 16, 2017, 09:27:08 am
now again working masternode= received rewards .... nice

for CZECH+SLOVAK languages i can help
user Slovakia can help with CZECH SLOVAKIA HUNGARY
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 09:40:05 am
Alright, should I mine at the same time or just be connected and synced to the network?

You can mine if you want, no problem, as long as you are synced first.

But now all of a sudden we have a fork.  I dont know if it has anything to do with your nodes coming on? How many did you bring into testnet?

We all need to be synced before I can make any sense out of the test harness forensic commands.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 09:41:20 am
it looks,that we are stuck on 41100
Yeah I see half the network is on 41116 and the other half on 41293....

Looking...  Not sure why this started all of a sudden, we were going so well other than having a rag tag set of sanctuaries we were staying in sync for a long time.  This happened at 5AM this morning (4 hours ago).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 09:42:56 am
Yeah I see half the network is on 41116 and the other half on 41293....

Looking...  Not sure why this started all of a sudden, we were going so well other than having a rag tag set of sanctuaries we were staying in sync for a long time.  This happened at 5AM this morning (4 hours ago).

If you see my post above, I hope it's not my node who broke the network!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 09:59:51 am
If you see my post above, I hope it's not my node who broke the network!

Whats your IP, Id like to see if you are banned on any of my 3 nodes?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 10:04:37 am
Whats your IP, Id like to see if you are banned on any of my 3 nodes?

The mining node now on block 41309 is 94.130.49.121 or 2a01:4f8:10b:26e3::2
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 10:08:23 am
The mining node now on block 41309 is 94.130.49.121 or 2a01:4f8:10b:26e3::2
Ah, good news, we had Exactly 50-50 on both chains!  I just resynced one node, and the balance is shifting.  Im observing this very closely to see if the reset of the net syncs up to 41309+...  I just see one node is reorging by itself.
Unfortunately Ive got company stopping in now, I may be gone for a litle while. 
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 10:11:36 am
Ah, good news, we had Exactly 50-50 on both chains!  I just resynced one node, and the balance is shifting.  Im observing this very closely to see if the reset of the net syncs up to 41309+...  I just see one node is reorging by itself.
Unfortunately Ive got company stopping in now, I may be gone for a litle while.

haha no worries. It's 3 am so I won't be up for long too.

Also,  I only brought the two nodes I talked about in my 2 previous posts above. 1 mining and 1 non-mining that's it.

This is what happened around the time of the "fork" so I'm wondering if it could have been me.

hmm.. so I decided to turn mining on for one of the node and leave mining off for the other one so I could compare it and....

The node not mining didn't like the blocks of the node mining? This is what appeared immediately after:

2017-11-16 11:07:57 IsBlockPayeeValid -- ERROR: Invalid masternode payment detected at height 41101: CTransaction(hash=88bf52d0cb, ver=1, vin.size=1, vout.size=3, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 038da0000107)
    CTxOut(nValue=7749.70501005, scriptPubKey=2102678e7dc966def90b47ee67e28a)
    CTxOut(nValue=13.02700000, scriptPubKey=2102678e7dc966def90b47ee67e28a)
    CTxOut(nValue=7762.73201004, scriptPubKey=76a914e32c41f9a7dd95011fcdd66e)
2017-11-16 11:07:57 ERROR: ConnectBlock(biblepay): couldn't find masternode or superblock payments
2017-11-16 11:07:57 InvalidChainFound: invalid block=8dc6e2f72ed1ecd72d2dcdfc2349d229c7afe987d886a24edcd027ef0dffc055  height=41101  log2_work=45.429083  date=2017-11-16 11:07:52
2017-11-16 11:07:57 InvalidChainFound:  current best=4235f1419b54be4e2587ed371b1ecad7c116a1744861d429b0df37770f373340  height=41100  log2_work=45.429078  date=2017-11-16 11:07:17
2017-11-16 11:07:57 ERROR: ConnectTip(): ConnectBlock 8dc6e2f72ed1ecd72d2dcdfc2349d229c7afe987d886a24edcd027ef0dffc055 failed
2017-11-16 11:07:57 InvalidChainFound: invalid block=8dc6e2f72ed1ecd72d2dcdfc2349d229c7afe987d886a24edcd027ef0dffc055  height=41101  log2_work=45.429083  date=2017-11-16 11:07:52
2017-11-16 11:07:57 InvalidChainFound:  current best=4235f1419b54be4e2587ed371b1ecad7c116a1744861d429b0df37770f373340  height=41100  log2_work=45.429078  date=2017-11-16 11:07:17
2017-11-16 11:07:57 ProcessNewBlock : ACCEPTED
2017-11-16 11:07:58 ERROR: AcceptBlockHeader: block is marked invalid
2017-11-16 11:07:58 ERROR: invalid header received 8dc6e2f72ed1ecd72d2dcdfc2349d229c7afe987d886a24edcd027ef0dffc055
2017-11-16 11:08:43 ERROR: AcceptBlockHeader: prev block invalid
2017-11-16 11:08:43 Misbehaving: 94.130.49.121:40001 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-11-16 11:08:43 ERROR: invalid header received 8e4bf23f0f469470c24c70fd52d35cac975b36df65a1f5c99f05edae5be0132f
2017-11-16 11:08:43 ERROR: AcceptBlockHeader: prev block invalid
2017-11-16 11:08:43 Misbehaving: [2a01:4f8:10b:26e3::2]:34718 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-11-16 11:08:43 ERROR: invalid header received 8e4bf23f0f469470c24c70fd52d35cac975b36df65a1f5c99f05edae5be0132f
2017-11-16 11:08:49 ERROR: AcceptBlockHeader: prev block invalid
2017-11-16 11:08:49 Misbehaving: [2001:0:9d38:6ab8:34dd:1fdc:d97b:d656]:54081 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-11-16 11:08:49 ERROR: invalid header received 8e4bf23f0f469470c24c70fd52d35cac975b36df65a1f5c99f05edae5be0132f

94.130.49.121 and 2a01:4f8:10b:26e3::2 is the same machine which is the node I just activated mining on btw.

I didn't see any error on the mining node and it is still happily mining.

The node mining is now on block 41112 while the other one seems to be stuck on 41100.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on November 16, 2017, 10:27:40 am
I've been trying to get my masternode up and running again (making sure watchdog is functioning).

My sanctuary wallet was indeed stuck on a certain block and wouldn't sync. But I've reindexed both and it seems I'm on the right chain right now (both wallets are on the same block).

Controller wallet:
Code: [Select]

{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 38514484.00745234,
  "privatesend_balance": 0.00000000,
  "blocks": 41330,
  "timeoffset": -2,
  "connections": 3,
  "proxy": "",
  "difficulty": 0.1980807012241197,
  "testnet": true,
  "keypoololdest": 1507285625,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Sanctuary wallet:
Code: [Select]
{
  "version": 1000508,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.8",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 41330,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.1980807012241197,
  "testnet": true,
  "keypoololdest": 1508425662,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

The only thing now is that the 'masternodelist' command gets different results on my controller and sanctuary wallet.

Controller wallet:
Code: [Select]
17:21:14

{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "NEW_START_REQUIRED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "NEW_START_REQUIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "ENABLED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "ENABLED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "ENABLED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "ENABLED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "ENABLED"
}

Sanctuary wallet:

Code: [Select]
{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "NEW_START_REQUIRED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "NEW_START_REQUIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "NEW_START_REQUIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "NEW_START_REQUIRED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "NEW_START_REQUIRED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "NEW_START_REQUIRED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "ENABLED"
}

I am 'a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4' btw.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 01:19:57 pm
haha no worries. It's 3 am so I won't be up for long too.

Also,  I only brought the two nodes I talked about in my 2 previous posts above. 1 mining and 1 non-mining that's it.

This is what happened around the time of the "fork" so I'm wondering if it could have been me.
Cool, I took a look at that log, and I can see how that particular node would go off on its own and ban everyone.  In this case, it did not have the same mncache.dat view that everyone else had, so its mnpayment schedule was different, and since we enforce masternode recipients, it was not going to agree on the next block (because it couldnt fill out a masternode while the supermajority could). The question is how did it get all synced with a different view of mncache?  Probably because of the headers it rejected it was mining on a fork or something earlier.

The other thing is, if we have a supermajority that is synced with synced masternode data, a couple bad fraudulently compiled nodes with hosed up integrated business logic compiled in should not be able to take us down.  Of course with the fragility of testnet, having only 4 synced masternodes, its possible to hose us up if you bring just 2 bad nodes online. 

Either way lets move past this one and wait til you have the checkblock(1) error showing and then maybe that will shed light on why your headers were rejected. 

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 01:21:31 pm
I've been trying to get my masternode up and running again (making sure watchdog is functioning).

My sanctuary wallet was indeed stuck on a certain block and wouldn't sync. But I've reindexed both and it seems I'm on the right chain right now (both wallets are on the same block).

Controller wallet:
Code: [Select]

{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 38514484.00745234,
  "privatesend_balance": 0.00000000,
  "blocks": 41330,
  "timeoffset": -2,
  "connections": 3,
  "proxy": "",
  "difficulty": 0.1980807012241197,
  "testnet": true,
  "keypoololdest": 1507285625,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Sanctuary wallet:
Code: [Select]
{
  "version": 1000508,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.8",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 41330,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.1980807012241197,
  "testnet": true,
  "keypoololdest": 1508425662,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

The only thing now is that the 'masternodelist' command gets different results on my controller and sanctuary wallet.

Controller wallet:
Code: [Select]
17:21:14

{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "NEW_START_REQUIRED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "NEW_START_REQUIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "ENABLED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "ENABLED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "ENABLED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "ENABLED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "ENABLED"
}

Sanctuary wallet:

Code: [Select]
{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "NEW_START_REQUIRED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "NEW_START_REQUIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "NEW_START_REQUIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "NEW_START_REQUIRED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "NEW_START_REQUIRED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "NEW_START_REQUIRED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "ENABLED"
}

I am 'a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4' btw.

Yeah, I have the same problem.  It looks like everyone who reindexed the chain today lost all their masternode data (stored in mncache.dat), all the governance objects are getting revoted on now etc.  So basically the masternode state is very bad in testnet.  We will have to wait a while to see if our 5 masternodes switch back to enabled. 

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 16, 2017, 03:22:49 pm
all 5 MNodes is ENABLED but we are STUCKED? 41124
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 03:42:57 pm
all 5 MNodes is ENABLED but we are STUCKED? 41124
All my 3 nodes rolling at 41534 and synced; status = ENABLED, try on your bad node, try going to peers and ban anyone with a low height, and see if it syncs, if not -reindex.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 04:54:16 pm
I got some errors for you  8)

https://pastebin.com/NaHRQBi7

Also I'm not sure if you saw it but this is what I got on mainnet just before switching that box to testnet

2017-11-16 01:53:00 ProcessNewBlock : ACCEPTED
2017-11-16 02:01:14 CheckProofOfWork(1.0): BlockHash 333e1c9e6fc52027012f734b2b701a3325591759ec6f29686879faae98a4b585, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510797674.000000, PrevBlockTime 1510797171.000000, BibleHash 0000000000072c18e0c42605b5431bd2e2343ced7942038c6a39f76ffa077225, TargetHash 000000000007e281000000000000000000000000000000000000000000000000, Forensics exec biblehash 333e1c9e6fc52027012f734b2b701a3325591759ec6f29686879faae98a4b585 1510797674 1510797171 16911
2017-11-16 02:01:14 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 16911.000000 pindexPrev f3479b24cae1e5b5fb10572b0eac0ea45492f7f4e32e88029ce72eb6cd48b1bb
2017-11-16 02:01:14 ERROR: CheckBlockHeader(): proof of work failed
2017-11-16 02:01:14 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-11-16 02:01:14 Misbehaving: 217.182.73.71:40000 (0 -> 5)
2017-11-16 02:01:14 UpdateTip: new best=333e1c9e6fc52027012f734b2b701a3325591759ec6f29686879faae98a4b585  height=16912  log2_work=57.78389  tx=28553  date=2017-11-16 02:01:14 progress=1.000000  cache=0.0MiB(7tx)
--
2017-11-16 03:03:15 ProcessNewBlock : ACCEPTED
2017-11-16 03:03:39 CheckProofOfWork(1.0): BlockHash 5468ae8523dbe8fc9d895343f0deb9f27a7d74763eb4d0cf8e71a419c77b5395, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510801402.000000, PrevBlockTime 1510801390.000000, BibleHash 00000000000677ab6388f8cd607de8c458d9083599fef6192c63b517bf3eb730, TargetHash 00000000000a858a000000000000000000000000000000000000000000000000, Forensics exec biblehash 5468ae8523dbe8fc9d895343f0deb9f27a7d74763eb4d0cf8e71a419c77b5395 1510801402 1510801390 16917
2017-11-16 03:03:39 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 16917.000000 pindexPrev 89d18d6ae6043337ed9b650244e7e4fac4004aa7d61e40e892d51ea9dd9e7955
2017-11-16 03:03:39 ERROR: CheckBlockHeader(): proof of work failed
2017-11-16 03:03:39 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-11-16 03:03:39 Misbehaving: 208.113.166.223:40000 (0 -> 5)
2017-11-16 03:03:39 UpdateTip: new best=5468ae8523dbe8fc9d895343f0deb9f27a7d74763eb4d0cf8e71a419c77b5395  height=16918  log2_work=57.785222  tx=28561  date=2017-11-16 03:03:22 progress=0.999999  cache=0.0MiB(16tx)
--
2017-11-16 03:44:09 ProcessNewBlock : ACCEPTED
2017-11-16 03:57:38 CheckProofOfWork(1.0): BlockHash 6c8efa4788a6aa5e42d2d7b5f54fe24e1f9fb4483fa707fcfe4b4c8ec0bbdf57, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510804572.000000, PrevBlockTime 1510803844.000000, BibleHash 0000000000007a70102622f79b71810b12687066d52a06d53ff74f9a59389587, TargetHash 00000000000947eb000000000000000000000000000000000000000000000000, Forensics exec biblehash 6c8efa4788a6aa5e42d2d7b5f54fe24e1f9fb4483fa707fcfe4b4c8ec0bbdf57 1510804572 1510803844 16922
2017-11-16 03:57:38 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 16922.000000 pindexPrev c49314cb92548b7722cccbb773922c48f3eb4fe9fe6a0e3c95a129312f9161c8
2017-11-16 03:57:38 ERROR: CheckBlockHeader(): proof of work failed
2017-11-16 03:57:38 Misbehaving: 208.113.166.223:40000 (5 -> 10)
2017-11-16 03:57:38 ERROR: invalid header received 6c8efa4788a6aa5e42d2d7b5f54fe24e1f9fb4483fa707fcfe4b4c8ec0bbdf57
2017-11-16 03:57:38 UpdateTip: new best=6c8efa4788a6aa5e42d2d7b5f54fe24e1f9fb4483fa707fcfe4b4c8ec0bbdf57  height=16923  log2_work=57.786245  tx=28570  date=2017-11-16 03:56:12 progress=0.999997  cache=0.0MiB(38tx)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 06:55:04 pm
I got some errors for you  8)

https://pastebin.com/NaHRQBi7

Also I'm not sure if you saw it but this is what I got on mainnet just before switching that box to testnet

Oh good, thanks :).

Oh I see its in mainnet, so that should be easy to research, hopefully.

Will check it out right now.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 07:28:35 pm
I got some errors for you  8)

https://pastebin.com/NaHRQBi7

Also I'm not sure if you saw it but this is what I got on mainnet just before switching that box to testnet


Thanks, this is extremely helpful as we went out of sync in testnet a couple times, like I said I saw this error a few times in prod in random logs, but it was so elusive I couldnt reproduce it.  Luckily, it looks like our advanced forensic logging yielding some info (knock on wood).  Lets hope we can get to the bottom of this in only a few passes.  Id hate to see this take a month to fix.

Anyway heres what I am seeing.  On the extremely bright side, I am generating the exact same biblehashes as your node was at the time of the problem.  Thats good, because I didnt want to see some type of non-deterministic biblehash.  So to follow me on that part of it, the biblehash requires 4 inputs, for example your first checkblock error requires me to run this command:


exec biblehash 333e1c9e6fc52027012f734b2b701a3325591759ec6f29686879faae98a4b585 1510797674 1510797171 16911
yielding biblehash: 0000000000072c18e0c42605b5431bd2e2343ced7942038c6a39f76ffa077225

Which matches yours, so that is great.

Next I checked the bits in that block that yields the difficulty and therefore the targethash which matches your targethash in the checkblock message. 

Here is where it gets interesting.  If you convert the hex to decimal (if you need to unless you can do this in your head) the biblehash with a 7a7 prefix must be Lower than the uint256 target (947e).  The 7a7 is 1959 decimal and the 947e is 38014, meaning that it passes. 

So basically what I am saying here is your arithmetic library is failing to calculate the less than operator here (LOL).  I know it sounds strange, now Bitcoin is using something called UintToArith256  to convert the uint256 big number to an arithmetic vector, allowing the math problem to be performed.  So of course that leads me to wonder how can the node function at all if that less than is failing? LOL.  So I move on and I tested the next two examples.  Same issue:  677a (26490) is less than (43096) meaning that the test should have passed, and the block was good and the error was a bad call.
Next 72c1 < 7e28: same issue, block was good, bad call.

So what Im going to do now is Ill add some more code to store the biblehash before its compared, and then compare it, then store it again and log both the original and the compared values in the log, then we can see if somehow, your biblehash changes between the hash and the comparison.  Because obviosly you are doing math for all other blocks. 

Alright Ill be back in about a half hour with the new version.

Good Job.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 07:39:29 pm
Welp that is indeed really strange since it's not failing on every block! There must be something special about these numbers :P

It will be interesting to see what the issue is/was.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 07:46:30 pm
Welp that is indeed really strange since it's not failing on every block! There must be something special about these numbers :P

It will be interesting to see what the issue is/was.

Yeah, it will have to reveal itself as either a vector problem in the biblehash accessor, or a problem in that arithmetic lib, or it could even be a BOOST lib issue, maybe one particular boost lib in your version being manipulated a certain way before the call, Oh who knows :)

Anyway, I just pushed out 1.0.6.0 if you want to run that for a while until we get more examples. 
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 07:49:11 pm
Yeah, it will have to reveal itself as either a vector problem in the biblehash accessor, or a problem in that arithmetic lib, or it could even be a BOOST lib issue, maybe one particular boost lib in your version being manipulated a certain way before the call, Oh who knows :)

Anyway, I just pushed out 1.0.6.0 if you want to run that for a while until we get more examples.

Doing that now, would like me to run on testnet or mainnet?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 07:58:27 pm
Doing that now, would like me to run on testnet or mainnet?
Mainnet is probably better.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 08:03:14 pm
Mainnet is probably better.

Alright, finished upgrading a few nodes so hopefully we will get something quickly.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 09:09:20 pm
Not sure if you're still around Rob but I just got that

2017-11-17 02:43:04 ProcessNewBlock : ACCEPTED
2017-11-17 02:56:42 CheckProofOfWork(1.0): BlockHash d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510887401.000000, PrevBlockTime 1510886577.000000, BibleHash1 0004010c0376b246463104ca838735effd6c8d9d8294084276cf15bb4fd602c7, BibleHash2 0004010c0376b246463104ca838735effd6c8d9d8294084276cf15bb4fd602c7, TargetHash 0000000000074772000000000000000000000000000000000000000000000000, Forensics exec biblehash d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb 1510887401 1510886577 17065
2017-11-17 02:56:42 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17065.000000 pindexPrev 7ec3beeb8f2710d57961c2a75687578b19687f7d219d6a062037c764bcb1f712
2017-11-17 02:56:42 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 02:56:42 Misbehaving: 35.199.177.240:40000 (0 -> 5)
2017-11-17 02:56:42 ERROR: invalid header received d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb
2017-11-17 02:56:42 UpdateTip: new best=d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb  height=17066  log2_work=57.808768  tx=28757  date=2017-11-17 02:56:41 progress=1.000000  cache=0.0MiB(7tx)
--
2017-11-17 02:58:23 ProcessNewBlock : ACCEPTED
2017-11-17 03:03:54 CheckProofOfWork(1.0): BlockHash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510887834.000000, PrevBlockTime 1510887502.000000, BibleHash1 0016bc69d09c727fedfac1fda865bf9666d94e4a20d02527c18efebeaaea19fb, BibleHash2 0016bc69d09c727fedfac1fda865bf9666d94e4a20d02527c18efebeaaea19fb, TargetHash 000000000008528c000000000000000000000000000000000000000000000000, Forensics exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067
2017-11-17 03:03:54 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17067.000000 pindexPrev 8c7665df98db007329275eb36a43f6f4d735324af64728e787811dc7d0079578
2017-11-17 03:03:54 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 03:03:54 Misbehaving: 51.15.89.39:40000 (0 -> 5)
2017-11-17 03:03:54 ERROR: invalid header received de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261
2017-11-17 03:03:54 UpdateTip: new best=de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261  height=17068  log2_work=57.809114  tx=28759  date=2017-11-17 03:03:54 progress=1.000000  cache=0.0MiB(9tx)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 16, 2017, 09:53:41 pm
Not sure if you're still around Rob but I just got that

2017-11-17 02:43:04 ProcessNewBlock : ACCEPTED
2017-11-17 02:56:42 CheckProofOfWork(1.0): BlockHash d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510887401.000000, PrevBlockTime 1510886577.000000, BibleHash1 0004010c0376b246463104ca838735effd6c8d9d8294084276cf15bb4fd602c7, BibleHash2 0004010c0376b246463104ca838735effd6c8d9d8294084276cf15bb4fd602c7, TargetHash 0000000000074772000000000000000000000000000000000000000000000000, Forensics exec biblehash d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb 1510887401 1510886577 17065
2017-11-17 02:56:42 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17065.000000 pindexPrev 7ec3beeb8f2710d57961c2a75687578b19687f7d219d6a062037c764bcb1f712
2017-11-17 02:56:42 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 02:56:42 Misbehaving: 35.199.177.240:40000 (0 -> 5)
2017-11-17 02:56:42 ERROR: invalid header received d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb
2017-11-17 02:56:42 UpdateTip: new best=d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb  height=17066  log2_work=57.808768  tx=28757  date=2017-11-17 02:56:41 progress=1.000000  cache=0.0MiB(7tx)
--
2017-11-17 02:58:23 ProcessNewBlock : ACCEPTED
2017-11-17 03:03:54 CheckProofOfWork(1.0): BlockHash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510887834.000000, PrevBlockTime 1510887502.000000, BibleHash1 0016bc69d09c727fedfac1fda865bf9666d94e4a20d02527c18efebeaaea19fb, BibleHash2 0016bc69d09c727fedfac1fda865bf9666d94e4a20d02527c18efebeaaea19fb, TargetHash 000000000008528c000000000000000000000000000000000000000000000000, Forensics exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067
2017-11-17 03:03:54 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17067.000000 pindexPrev 8c7665df98db007329275eb36a43f6f4d735324af64728e787811dc7d0079578
2017-11-17 03:03:54 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 03:03:54 Misbehaving: 51.15.89.39:40000 (0 -> 5)
2017-11-17 03:03:54 ERROR: invalid header received de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261
2017-11-17 03:03:54 UpdateTip: new best=de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261  height=17068  log2_work=57.809114  tx=28759  date=2017-11-17 03:03:54 progress=1.000000  cache=0.0MiB(9tx)

Whats very strange is in these two examples, the exec biblehash command does not produce the same output as the error.  This is very strange, especially since each of your error messages we call it twice.

Anyway, I have to close out soon, in the mean time, what does your node report for this command in prod:

exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067

Mine reports : 000000000005fc7360c14e1b6c3d3a7530d27e942b928bdb17c8801fdafc19ba
Which is a different hash than the error message reports.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 16, 2017, 10:04:01 pm
Whats very strange is in these two examples, the exec biblehash command does not produce the same output as the error.  This is very strange, especially since each of your error messages we call it twice.

Anyway, I have to close out soon, in the mean time, what does your node report for this command in prod:

exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067

Mine reports : 000000000005fc7360c14e1b6c3d3a7530d27e942b928bdb17c8801fdafc19ba
Which is a different hash than the error message reports.

biblepay-cli exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067
{
  "Command": "biblehash",
  "BibleHash": "000000000005fc7360c14e1b6c3d3a7530d27e942b928bdb17c8801fdafc19ba"
}

Same thing as yours
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 16, 2017, 10:41:36 pm
all nodes on testnet are down except for 1 :
./biblepay-cli masternode list
{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "WATCHDOG_EXPIRED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "WATCHDOG_EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "WATCHDOG_EXPIRED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "WATCHDOG_EXPIRED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "WATCHDOG_EXPIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "WATCHDOG_EXPIRED"


I upgraded mine to 1.0.6    and after re-syncing it's showing "watchdog expired"   .  Watchdog is running with no errors. I didn't touch it.

  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 16, 2017, 11:07:29 pm
all nodes on testnet are down except for 1 :
./biblepay-cli masternode list
{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "WATCHDOG_EXPIRED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "WATCHDOG_EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "WATCHDOG_EXPIRED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "WATCHDOG_EXPIRED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "WATCHDOG_EXPIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "WATCHDOG_EXPIRED"


I upgraded mine to 1.0.6    and after re-syncing it's showing "watchdog expired"   .  Watchdog is running with no errors. I didn't touch it.

  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",

looks ok now :

Code: [Select]
./biblepay-cli masternode list
{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "WATCHDOG_EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "ENABLED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "ENABLED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "ENABLED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "EXPIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "EXPIRED"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 12:50:17 am
I got an error message on a different node than the one in my previous post. The exec biblehash command result also doesn't seem to match what's in the log.

2017-11-17 03:52:37 ProcessNewBlock : ACCEPTED
2017-11-17 04:18:58 CheckProofOfWork(1.0): BlockHash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510892191.000000, PrevBlockTime 1510890756.000000, BibleHash1 00122557bcb25dd4eb7085498a23c566de5e187a11d6655685f61333f40ae11a, BibleHash2 00122557bcb25dd4eb7085498a23c566de5e187a11d6655685f61333f40ae11a, TargetHash 00000000000395f6000000000000000000000000000000000000000000000000, Forensics exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
2017-11-17 04:18:58 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17074.000000 pindexPrev b8f34304d7ce0ef3e10f4ea7812d4c85e2e6fd93a72cd51f128eaa32bede2dd6
2017-11-17 04:18:58 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 04:18:58 Misbehaving: 80.211.200.215:52172 (0 -> 5)
2017-11-17 04:18:58 ERROR: invalid header received e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347
2017-11-17 04:18:58 UpdateTip: new best=e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347  height=17075  log2_work=57.811358  tx=28767  date=2017-11-17 04:16:31 progress=0.999994  cache=0.0MiB(20tx)

On the exact same node I use the forensic command and get a different biblehash again..how strange!

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 12:55:23 am
Wow I just noticed something strange. I was spamming the forensic command and got different results?? One of them seems to match what I got in the logs!

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "00122557bcb25dd4eb7085498a23c566de5e187a11d6655685f61333f40ae11a"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 01:03:51 am
Just started a VM to try it and I also managed to get different biblehash!

Note: The mn4 machine above is running OpenSSL 101t while this one is running OpenSSL 102g

}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0014bf432d9989ac1e7a93a8918e37b4aa9694f82fa3d86684a249f2c444394d"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}

Trying on a different machine with OpenSSL 101t

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "00122557bcb25dd4eb7085498a23c566de5e187a11d6655685f61333f40ae11a"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
---
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0014bf432d9989ac1e7a93a8918e37b4aa9694f82fa3d86684a249f2c444394d"


Managed to get 3 different results! one matching what I got with mn4 and OpenSSL101t and the other matching what I got with the vm on Openssl102g. I think I can probably get all 3 different biblehash (if not more) on all 3 machines.

Edit: Doing some more tests, Is it normal to get these results when changing the prev block reference?


[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17079
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd" <= same result with block 17069
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17078
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17073
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17072
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17071
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17070
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17069
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd" <= same result with block 17079

Update:

Just found something interesting which I think confirms my suspicion. Even though in most of the errors I have from the log, both biblehash1 and biblehash2 are the same, since it's computing 3 different times the biblehash, I think the one used in the if statement may actually be different from the one computed before and the one computed after, hence why it is failing the condition.

Look at this one I just found:

2017-11-17 10:03:51 ProcessNewBlock : ACCEPTED
2017-11-17 10:05:14 CheckProofOfWork(1.0): BlockHash 541a323bbf91103d90556af0e5b9143673a2cd36680fffe21bc3b7a9cbc85356, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510913112.000000, PrevBlockTime 1510913025.000000, BibleHash1 00246187e1fe61cac573d808464ecbcbc67a4703fedcc1931ed761a85a50ec57, BibleHash2 00265c4ef603fb643449e68805184db17f1f0242c4a64edd402decb0e96cb0cd, TargetHash 00000000000880b2000000000000000000000000000000000000000000000000, Forensics exec biblehash 541a323bbf91103d90556af0e5b9143673a2cd36680fffe21bc3b7a9cbc85356 1510913112 1510913025 17111
2017-11-17 10:05:14 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17111.000000 pindexPrev 20e9f4416b8e469b23a6fde82f197342086622e9ac827e78875701d001ca3916
2017-11-17 10:05:14 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 10:05:14 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-11-17 10:05:14 Misbehaving: 97.99.69.33:40000 (0 -> 5)
2017-11-17 10:05:14 UpdateTip: new best=541a323bbf91103d90556af0e5b9143673a2cd36680fffe21bc3b7a9cbc85356  height=17112  log2_work=57.818294  tx=28819  date=2017-11-17 10:05:12 progress=1.000000  cache=0.0MiB(112tx)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 06:34:29 am
all nodes on testnet are down except for 1 :
./biblepay-cli masternode list
{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "WATCHDOG_EXPIRED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "WATCHDOG_EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "WATCHDOG_EXPIRED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "WATCHDOG_EXPIRED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "WATCHDOG_EXPIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "WATCHDOG_EXPIRED"


I upgraded mine to 1.0.6    and after re-syncing it's showing "watchdog expired"   .  Watchdog is running with no errors. I didn't touch it.

  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",

Well actually that masternode list in this case is just the view from your local node which is down, checking the masternode list, we have the same 5 ENABLED we had 20 hours ago (after the fork and after everyone restarted), so things are stll improving from that Point, but my guess is you havent actually recovered from that particular fork.

First you will have to sync and then work on the watchdog later.  mnsync status must show 999 before you can work on testing watchman.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 06:36:34 am
ok,in controller wallet i BAN bad nodes and synced= all rewards received .... but linux masternode is stuck ... its need to resync masternode too?

what is command for reindex wallet in testnet i tried

./biblepay-cli -testnet -daemon -reindex
./biblepay-cli -testnet -reindex

and w/result

This isnt really a support thread on how to use the wallet.  Just resync your node and then lets continue testing sanctuaries.

EDIT: It looks like 95% of the network is at block 42122.  I see 65.x is resyncing.  Just try to get up to 42122+.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 06:59:24 am
Just started a VM to try it and I also managed to get different biblehash!

Note: The mn4 machine above is running OpenSSL 101t while this one is running OpenSSL 102g

}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074revheight 17111.000000 pindexPrev 20e9f4416b8e469b23a6fde82f197342086622e9ac827e78875701d001ca3916
2017-11-17 10:05:14 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 10:05:14 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-11-17 10:05:14 Misbehaving: 97.99.69.33:40000 (0 -> 5)
2017-11-17 10:05:14 UpdateTip: new best=541a323bbf91103d90556af0e5b9143673a2cd36680fffe21bc3b7a9cbc85356  height=17112  log2_work=57.818294  tx=28819  date=2017-11-17 10:05:12 progress=1.000000  cache=0.0MiB(112tx)


Nice tests, thanks, you really gave a lot of data to work with and pretty much every condition LOL.

So Im going to make this my top priority today. 

On your question about re-running the biblehash command with a prior blocknumber parameter (the ones you noted 17069, same as 17079) etc, that is fine because the block number parameter being sent into the biblehash is only used for it to determine the chain height, to turn on or off f7000 or f8000, and that is enforced on all nodes so that is secure, so changing that between f7000 start and f8000 start will just give you the same exact biblehash, so that is OK.  Changing the lastblocktime is a similar issue: that only drives when the block becomes "late".  When the block time exceeds 30 minutes then and only then the hash changes, so that is OK too.

On the question regarding the if statement, which hash its using, in this last version 1060, it is actually checking both, first it says if biblehash1 is too high, then if biblehash2 is too high, so your log only yields errors where they both were high hashes.  But thats OK too, because you still exposed enough information.

However I wasnt sure if you had to run the cli command 10,000 times programatically to change the hash in your example because I ran one of your examples 125 times from my RPC and received the same hash every time so so far I have been unable to change the hash like you have, but dont worry, I have enough info from your log for something to go on.

But focusing in on the one where you show that the hash1 and hash2 are actually completely different now that is the big dog right there, that is the smoking gun, I have never seen that.  Imo, that rules out the math operator and math class, that was generated on 101t, so it "points" toward not being openSSL versioning, it really points to either the MD5 function 'caching' the prior result (from the last blockindex check), or the AES512 vector 'caching' the last result.  So I think today, Im going to hone in on making an alternate (compatible of course) biblehash, using a different md5 supplier and refactoring the AES512 call, and we can run that side by side, and see if something changes.



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 07:11:48 am
Oh thanks for the clarifications!

I only have to do it maybe 10 times to get a different hash so it's pretty frequent.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 07:14:49 am
I just tried it again now. This is a straight copy and paste from my console with nothing before. It only took 1 try - well 2 I guess!

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17075
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17075
{
  "Command": "biblehash",
  "BibleHash": "0014bf432d9989ac1e7a93a8918e37b4aa9694f82fa3d86684a249f2c444394d"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17075
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 07:39:37 am
Oh also and I may have misunderstood you. Since everything is the same but the prev block number, shouldn't these hashes be the same?

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17079
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17078
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17069
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 08:24:14 am
Hey Klondike,

I created a thread there. Can you post what issue you're having again? I will do my best to help you.

http://forum.biblepay.org/index.php?topic=38.0
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 08:56:02 am
  im deleted chain+blocks ans im back  ...

question: how long being when status WATCHDOG changed to ENABLED from WATCH_DOG EXPIRED?

thanks

There are multiple layers of issues when you resync. When you have been synced for 24+ hours, if you had a watchdog problem, watchman would update the database and the gui and the votes in 15 minutes.  When you re-sync, your mncache.dat file is hosed and it takes about 6 hours to fix itself.

Lets just ensure your watchman command returns empty, and then wait for something to change once you are synced.  If not fixed in 8 hours something is wrong.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 08:57:57 am
Oh also and I may have misunderstood you. Since everything is the same but the prev block number, shouldn't these hashes be the same?

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17079
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17078
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17069
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd"

Yes, they should be the same - all 3 of them should be the same since only the last parameter is changing, the correct hash is 2aaa in prod - Im running it now in the rpc.  The 11c6 hash is a bad hash.   That looks like the problem.  Its interesting you can generate those hashes so easily.  Would you say that the type of node you are testing on in prod is a very, very slow node with very low ram, or is it a super machine running many threads with a lot of ram?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 09:01:02 am
All the "mn" nodes are Ryzen 7 with 64gb of DDR4 and 2xSSDs in Raid0. So decent machines I think!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 17, 2017, 09:16:42 am
Rob



1.how long being when status WATCHDOG changed to ENABLED from WATCH_DOG EXPIRED when watchman run?
2.where i can see that watcham is running?

3.PRE-ENABLED : watchman doesnt running,right?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 09:17:38 am
All the "mn" nodes are Ryzen 7 with 64gb of DDR4 and 2xSSDs in Raid0. So decent machines I think!
Thats very interesting.  Im honestly thinking, the Ryzen processor may be so fast that one mining thread is loading the AES512 encryption key partially in the core while the other receives a hash based on a faulty encryption key.  I did find a circumstance where I believe that is possible, so all this effort is definitely worth it, as this will "potentially" give us a stable biblehash, if this is the problem.

Ok, I tested the new version to ensure it yields the same hashes and mines in prod and testnet so I am checking it in.
Please grab 1061.

In this version, we use a different call to openssl's md5 (IE directly from the biblehash lib), we change our call to AES512 to be more efficient, and we set up a few miningparams once before we mine to not require those calls for every hash (so thats a slight improvement there too).  The biggest change, the one that might make or break this as the fix, is this:  I found the bibleminer was re-loading the encryption key for every hash, and that could be the problem.  I fixed this! So lets go ahead and try it again and see if it fixes.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 09:19:30 am
Rob

1.how long being when status WATCHDOG changed to ENABLED from WATCH_DOG EXPIRED when watchman run?
2.where i can see that watcham is running?

3.RE-ENABLED : watchman doesnt running,right?
1) If you delete your Watchman.db database and re-sync masternode data, and clear all your sanctuary .dat files (like mncache), then 15 minues, otherwise 8 hours.
2) You run watchman from the command line and see if it returns empty string.
3) Depends, if you just synced, you have to do queries in the watchman database to find the answer.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 09:20:26 am
Alright, I'm compiling the new version now. The "snapshot" node is a small vm with 2 core and 4gb of ram. I also had VMs with 1 core and 512 mb of ram and I have noticed the same issue.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 09:29:57 am
im still PRE-ENABLED  ... shit


by me,this masternodes is PONZI SCHEME like BBP : and i screw on all masternodes..... still not exists guide why watchman doesant running stable,im do all by guide and ROB=ADMIN still wrote with puzzles

ASKING YOU : how long being when you start WATCHMAN and your STATUS in controller wallet changes from preenabled to enabled? immediately?


i hope that masternodes wont be exists on BBP,cos this setuping is massacer

Dude its obvious you have a bad attitude and I dont want it here, why dont you try dash out for a while and see how easy it is to set one up and then come back later and tell us how it went?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 09:33:58 am
Thats very interesting.  Im honestly thinking, the Ryzen processor may be so fast that one mining thread is loading the AES512 encryption key partially in the core while the other receives a hash based on a faulty encryption key.  I did find a circumstance where I believe that is possible, so all this effort is definitely worth it, as this will "potentially" give us a stable biblehash, if this is the problem.

Ok, I tested the new version to ensure it yields the same hashes and mines in prod and testnet so I am checking it in.
Please grab 1061.

In this version, we use a different call to openssl's md5 (IE directly from the biblehash lib), we change our call to AES512 to be more efficient, and we set up a few miningparams once before we mine to not require those calls for every hash (so thats a slight improvement there too).  The biggest change, the one that might make or break this as the fix, is this:  I found the bibleminer was re-loading the encryption key for every hash, and that could be the problem.  I fixed this! So lets go ahead and try it again and see if it fixes.

Hey Rob, I finished updating one node and it is now mining on mainnet. How should I test that new version? Wait until I get an error in the log or should I spam the forensics command and see if I get different hashes again?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 09:38:57 am
Hey Rob, I finished updating one node and it is now mining on mainnet. How should I test that new version? Wait until I get an error in the log or should I spam the forensics command and see if I get different hashes again?

You can do both, go ahead and try to break it.

Yeah, we wont know its broken til it spurts out an error though....

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 09:45:04 am
Well well, I've been spamming the forensics command and I can happily say that it is now giving me the same hash no matter what!

However, with the same parameters but the block height, am I still getting the wrong hash for block 17078 and 17079 for example?

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17078
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17079
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd"

Did you say 0011 was invalid?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 09:52:38 am
Well well, I've been spamming the forensics command and I can happily say that it is now giving me the same hash no matter what!

However, with the same parameters but the block height, am I still getting the wrong hash for block 17078 and 17079 for example?

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17078
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17079
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd"

Did you say 0011 was invalid?

Im not able to reproduce that on 1061, I am running 1061 in testnet and moving from 78 to 79 still yields the 011 (not seeing the 2aaa).
What network are you in and is this definitely 1061?   Yeah, no changes should occur until you hit something like block 27000 etc.

Great on the improvement so far!  I bet we fixed it!  I bet this anomaly you found has a reason, such as cli being connected to 1060 :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 09:53:12 am
Im not able to reproduce that on 1061, I am running 1061 in testnet and moving from 78 to 79 still yields the 011 (not seeing the 2aaa).
What mode are you in and is this definitely 1061?   Yeah, no changes should occur until you hit something like block 27000 etc.

Great on the improvement so far!  I bet we fixed it!  I bet this anomaly you found has a reason, such as cli being connected to 1060 :)

Oh this is mainnet not testnet sorry
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 09:56:30 am
Oh this is mainnet not testnet sorry
Let me restart in mainnet and try that....
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 10:01:57 am
Oh this is mainnet not testnet sorry

Oh I see, OK we have a solid reason for this.  So in mainnet, tithe blocks are active til Christmas but in TestNet they are not.
Since the block the miner works on is n+1, if it will be an *upcoming* tithe block, the hash changes to be Higher, to allow the Diff to be Lower, so is normal for the blocks in Prod that will end in n+1 % 10 to be different, you can see if you increment the height up through n+9 no changes until you hit another tithe block.
Yeah, I confirm that hash is 011 in prod, and 2aaa for the tithe block :).

So far, so good! I guess I can let you burn in for a while longer.


This is excellent, this will most likely fix the reason we went out of sync twice in testnet.

EDIT:  THANKS ALEX FOR YOUR PERSEVERANCE AND FINDING THIS FLAW!!!!!

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 10:15:47 am
Oh I see, OK we have a solid reason for this.  So in mainnet, tithe blocks are active til Christmas but in TestNet they are not.
Since the block the miner works on is n+1, if it will be an *upcoming* tithe block, the hash changes to be Higher, to allow the Diff to be Lower, so is normal for the blocks in Prod that will end in n+1 % 10 to be different, you can see if you increment the height up through n+9 no changes until you hit another tithe block.
Yeah, I confirm that hash is 011 in prod, and 2aaa for the tithe block :).

So far, so good! I guess I can let you burn in for a while longer.


This is excellent, this will most likely fix the reason we went out of sync twice in testnet.

EDIT:  THANKS ALEX FOR YOUR PERSEVERANCE AND FINDING THIS FLAW!!!!!

Ohhhh ok that makes sense. Thanks for the explanation!

Haha thanks for the perseverance too. I must have ruined some of your nights! Glad I could help.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 17, 2017, 10:58:40 am
ROB im enabled now .... i was think,that when i run watchman ... PRE_ENABLED will be immediately ENABLED: we have to wait few minutes
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 17, 2017, 12:09:46 pm
Ok on Linux machine I just realized I never removed the banlist.dat file from the ~/.biblepaycore/testnet3 folder, woops,
I only had 2 connections before, now I have 12! Not sure how much this affected the retirement coin testing  :-\

I assume in the future we will want banlist.dat file?
Is there a linux command to delete the contents inside the file?
I just used rm (remove) command, but I assume that means I cant ban anyone going forward now.

===

Rebuilding/Resyncing Chain:

GUI:  Tools >> Wallet Repair >> Rebuild index
Linux:  ./biblepayd -daemon -reindex

===

Windows GUI Wallet is now v1.0.5.9
Linux Wallet is now v1.0.6.1
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 01:34:34 pm
Ok on Linux machine I just realized I never removed the banlist.dat file from the ~/.biblepaycore/testnet3 folder, woops,
I only had 2 connections before, now I have 12! Not sure how much this affected the retirement coin testing  :-\

I assume in the future we will want banlist.dat file?
Is there a linux command to delete the contents inside the file?
I just used rm (remove) command, but I assume that means I cant ban anyone going forward now.

===

Rebuilding/Resyncing Chain:

GUI:  Tools >> Wallet Repair >> Rebuild index
Linux:  ./biblepayd -daemon -reindex

===

Windows GUI Wallet is now v1.0.5.9
Linux Wallet is now v1.0.6.1

Thanks, well that would have worked its way out after 24 hours as the max ban flag is one day, but yeah, I think Alexs discovery had a lot to do with our shrinking and decomposing network, with increasing banned nodes.

Since a few hours have passed I think the general consensus is that Alex hasnt found any new issues so I will probably ask you all to update to the latest version so we can do a pulse test of stability over the next 10 days.  Id like to see no banned nodes, no lost syncs, and a good masternode list.  But hold off for a couple hours as I am working on a feature we may be able to test together.

Regarding the retirement testing, I did find a bug in there, very minor, and its "technically" corrected in the last version but not tested.  Let me go ahead and test that first before we try more retirement tests.

The other thing is I am hoping to release e-commerce alpha soon.  Then we can test that also.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 17, 2017, 06:37:27 pm
Just checked all my logs and Yup, no errors!

I've also successfully set up a masternode on testnet.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 17, 2017, 07:02:48 pm
Just checked all my logs and Yup, no errors!

I've also successfully set up a masternode on testnet.
Best thing I heard all week!  Great!  Thanks for the help!

Yeah, Im testing the new version and compiling one for windows now, and Im going to send it out as a highly recommended (just short of mandatory upgrade) to Prod & Testnet in a few hours.

(Cant go with Mandatory as it may upset CCEX).



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 07:52:34 am
BiblePay - 1.0.6.1 Available
Mandatory Release for TestNet


- Fix checkblock(1) errors diagnosed with Alex that occasionally results in an invalid BibleHash
- Upgrade wallet graphics with new logo pack
- Show OpenSSL version in Tools | Info

www.biblepay.org | Downloads
https://github.com/biblepay/biblepay/



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:04:28 am
I guess we can try another retirement trade.  Togo?  If not, anyone else?

You must be on 1061 to test retirement trading.  Windows is out there also.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 10:42:37 am
Hey Rob, I was looking through my logs and I'm seeing a new error now from time to time.

I was wondering if you had any idea where it could be coming from?

 ** TestBlockValidity FAILED - pindexNew->pprev != chainActive.Tip() (assert(pindexNew->pprev == chainActive.Tip())); **
2017-11-18 01:32:04 TestBlockValidity failed while creating new block
2017-11-18 01:32:04 BiblepayMiner -- Keypool ran out, please call keypoolrefill before restarting the mining thread

(my wallet has 40000 keys  pre-generated so it's def not running out of that)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 12:50:06 pm
Hey Rob, I was looking through my logs and I'm seeing a new error now from time to time.

I was wondering if you had any idea where it could be coming from?

 ** TestBlockValidity FAILED - pindexNew->pprev != chainActive.Tip() (assert(pindexNew->pprev == chainActive.Tip())); **
2017-11-18 01:32:04 TestBlockValidity failed while creating new block
2017-11-18 01:32:04 BiblepayMiner -- Keypool ran out, please call keypoolrefill before restarting the mining thread

(my wallet has 40000 keys  pre-generated so it's def not running out of that)

That means the best block changed while you were generating a new block for mining.  The keypool error is misleading, should be taken out.

Please verify this only happens once every few hours then that will confirm it.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 04:07:28 pm
That means the best block changed while you were generating a new block for mining.  The keypool error is misleading, should be taken out.

Please verify this only happens once every few hours then that will confirm it.

Yup it's only every few hours. Thanks!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 04:18:43 pm
Yup it's only every few hours. Thanks!
Thanks for checking, yeah Ill fix that area, please follow up with me in a week and we can ensure its right (regarding the keypool test and message), I need to get past this hump with the ecommerce release and need to ask more people to help test these retirement accounts starting tomorrow.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 04:37:26 pm
Thanks for checking, yeah Ill fix that area, please follow up with me in a week and we can ensure its right (regarding the keypool test and message), I need to get past this hump with the ecommerce release and need to ask more people to help test these retirement accounts starting tomorrow.

No worries, I was just curious about that!

How can I help test these retirement accounts? I saw that you wanted to a retirement trade earlier. I'm still going through the posts to find the rpc commands.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 18, 2017, 06:07:37 pm
How can I help test these retirement accounts?

http://wiki.biblepay.org/Retirement_Accounts

exec retirementbalance
exec tradehistory
exec orderbook
exec listorders
exec order [  Buy/Sell/Cancel ]   Qty  Symbol [Price]

Im free to test too :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 06:24:50 pm
http://wiki.biblepay.org/Retirement_Accounts

exec retirementbalance
exec tradehistory
exec orderbook
exec listorders
exec order [  Buy/Sell/Cancel ]   Qty  Symbol [Price]

Im free to test too :)

Got it. Thanks Togo!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:18:08 pm
http://wiki.biblepay.org/Retirement_Accounts

exec retirementbalance
exec tradehistory
exec orderbook
exec listorders
exec order [  Buy/Sell/Cancel ]   Qty  Symbol [Price]

Im free to test too :)

I just got back in and should be around for an hour or two.

Anyone up for a trade?

Dont forget, when you do the exec orderbook, you can widen your rpc display to see it better.

I just did: exec order sell 50000 rbbp .0293

If someone wants to add the opposing Buy order?

Please do an exec retirementbalance before trading so you can see the prior balance.

After 5 confirms on our trade, then you can do an exec tradehistory, and exec retirementbalance and reconcile them..



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:20:01 pm
I just got back in and should be around for an hour or two.

Anyone up for a trade?

Let me add one

I added some sell orders a hour ago.

[email protected]:~# biblepay-cli exec listorders
{
  "Command": "listorders",
  "#": 0,
  "#": 1,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000031a39b9b5928b96d6655a4075808520",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 50000,
  "BBP_Price": 0.0293,
  "#": 2,
  "Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Hash": "00000000000000000000000000000000a85d3b6990b8252024110707367a343e",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 74029,
  "BBP_Price": 9000,
  "#": 3,
  "Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Hash": "000000000000000000000000000000001496a2ae39c8a94a0879530b078e1161",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1000,
  "BBP_Price": 345.1,
  "#": 4,
  "Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Hash": "00000000000000000000000000000000c14a1f858d78c7a87fb4373b3a982cef",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 1,
  "BBP_Price": 1000
}

Are sell orders "broadcasted" so that I know if someone is selling/buying something?

EDIT: nvm found it. what an idiot.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:21:01 pm
I added some sell orders a hour ago.
Yeah, I see one is like 660 MM BBP, I dont think we have enough to execute that one LOL.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:21:55 pm
Haha yeah I was just playing with it.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:23:19 pm
Haha yeah I was just playing with it.

Ok, I did this buy:


exec order buy 1000 rbbp 345.1

Whose is that?
Btw you wont see the trade come back in the wallet for 5 confirms.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:26:13 pm
Ok, I did this buy:


exec order buy 1000 rbbp 345.1

Whose is that?
Btw you wont see the trade come back in the wallet for 5 confirms.

That is mine. I also just bought the sell order you placed before

[email protected]:~# biblepay-cli exec order buy 50000 RBBP 0.0293
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 50000,
  "Price": 0.0293,
  "Rec Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Placing Order": "00000000000000000000000000000000e0e201d1d345628c3938949611c3ccbc"
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:29:18 pm
Ive had some very strange things happen to me while coding Biblepay- hundreds of 777s, too many to go into right now, but get this, my auto-generated BBP address on my test linux node starts with:
Yah Son Qxv 2L Jsus

So, yes, I know its not perfect, but its really wild that Yah is Yahweh (God the Father), Son, is Jesus, Qxv I have not determined (but I think it means To Be command to), 2L is 2Love, Jsus is Jesus.  Its really hard to believe, except the Qxv didnt work out quite too well unless someone has a clue what that could mean in there.  I didnt change the order either of the letters, these are verbatim - of course after the Jsus, its all just normal alphanumeric stuff.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:34:38 pm
Ive had some very strange things happen to me while coding Biblepay- hundreds of 777s, too many to go into right now, but get this, my auto-generated BBP address on my test linux node starts with:
Yah Son Qxv 2L Jsus

So, yes, I know its not perfect, but its really wild that Yah is Yahweh (God the Father), Son, is Jesus, Qxv I have not determined (but I think it means To Be command to), 2L is 2Love, Jsus is Jesus.  Its really hard to believe, except the Qxv didnt work out quite too well unless someone has a clue what that could mean in there.  I didnt change the order either of the letters, these are verbatim - of course after the Jsus, its all just normal alphanumeric stuff.

Oh wow, what are the chances!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:37:32 pm
Also, I just got your RBBP.

[email protected]:~# biblepay-cli exec tradehistory
{
  "11/18/2017 8:28:30 PM": "BOT 50000 RBBP @ 0.0293 TOTAL 1465.00BBP ORDER 00000000000000000000000000000000e0e201d1d345628c3938949611c3ccbc."
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:38:17 pm
That is mine. I also just bought the sell order you placed before

[email protected]:~# biblepay-cli exec order buy 50000 RBBP 0.0293
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 50000,
  "Price": 0.0293,
  "Rec Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Placing Order": "00000000000000000000000000000000e0e201d1d345628c3938949611c3ccbc"
}


Hmm, I see the 50,000 went through, but my retirement balance is only down by 7000, is yours up by 50000?

My 1465 payment went out to you I believe?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:41:35 pm

Hmm, I see the 50,000 went through, but my retirement balance is only down by 7000, is yours up by 50000?

My 1465 payment went out to you I believe?

Lets try a few more:
exec order sell 245111 rbbp .01

Please issue a buy instead I entered the sell, Ill watch the balance this time
(It could be correct, and problem because of 401k Change), but I have to really analyze the txid.

I think if we do a couple big ones like this it will be apparent?


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:45:05 pm
Also, I just got your RBBP.

[email protected]:~# biblepay-cli exec tradehistory
{
  "11/18/2017 8:28:30 PM": "BOT 50000 RBBP @ 0.0293 TOTAL 1465.00BBP ORDER 00000000000000000000000000000000e0e201d1d345628c3938949611c3ccbc."
}

Great, so we are close, but have to verify these retirement amount adjustments:

"11/18/2017 8:28:30 PM": "SOLD 50000 RBBP @ 0.0293 TOTAL 1465.00BBP ORDER 00000000000000000000000000000000031a39b9b5928b96d6655a4075808520."

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:46:24 pm
Oh btw, I believe the only one that can cancel that 666 million BBP one is you, or if we wait 5 days (I forgot how long) for it to expire, do you want to try to cancel it by hash just to try?

Ill try to enter one and cancel also - havent even tested that.

Its exec order cancel hash.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:48:35 pm
Oh btw, I believe the only one that can cancel that 666 million BBP one is you, or if we wait 5 days (I forgot how long) for it to expire, do you want to try to cancel it by hash just to try?

Ill try to enter one and cancel also - havent even tested that.

Its exec order cancel hash.

Ok so its not exec order cancel hash, its exec order cancel  qty symbol price
But hey it worked!  It canceled from the orderbook (my test order) not your order.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:49:35 pm
Nice, I see a nice clean empty orderbook.

Waiting for the adjustment on that biggie.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:53:31 pm
Yup minus -1000RBBP, is that normal?

(unless I made a mistake or somehow someone bought something that is not showing up in my trade history yet?)

That was before:

[email protected]:~# biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 5577339.24096240,
  "retirement_account_balance": 74030,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 91720.31766116,
  "txcount": 730,
  "keypoololdest": 1510812056,
  "keypoolsize": 1018,
  "keys_left": 1018,
  "paytxfee": 0.00000000
}

and that is now

[email protected]:~# biblepay-cli getwalletinfo               
{
  "walletversion": 61000,
  "balance": 5672494.55836656,
  "retirement_account_balance": 123030,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 91726.43499986,
  "txcount": 745,
  "keypoololdest": 1510812056,
  "keypoolsize": 1016,
  "keys_left": 1016,
  "paytxfee": 0.00000000
}

---Just saw your new message, doing it now---

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:54:20 pm
Wait, I think there is a flaw in cancel!  I think whatever we canceled, we canceled every leg of every other order without escrow sent in :) LOL it was going too well, so cancel has a bug.  I think it cancels everything whether is a pending trade or not.  HMMM.
Ok lets not cancel til I check that out.

I will have to re-enter my big trade again, Alex you didnt enter the buy right?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:54:51 pm
Nice, I see a nice clean empty orderbook.

Waiting for the adjustment on that biggie.

hmm I had 2 orders, decided to cancel the one for 1000

[email protected]:~# biblepay-cli exec order cancel 1000 RBBP 9000
{
  "Command": "order",
  "Action": "CANCEL",
  "Symbol": "RBBP",
  "Qty": 1000,
  "Price": 9000,
  "Rec Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Canceling Order": "00000000000000000000000000000000cab1c92ea6dfa4833c8c111e300d7192"
}

but it seems my big 600m order or so disappeared too? Unless someone bought it LOL?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:55:31 pm
Wait, I think there is a flaw in cancel!  I think whatever we canceled, we canceled every leg of every other order without escrow sent in :) LOL it was going too well, so cancel has a bug.  I think it cancels everything whether is a pending trade or not.  HMMM.
Ok lets not cancel til I check that out.

I will have to re-enter my big trade again, Alex you didnt enter the buy right?

I did enter it!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:56:53 pm
Wait, I think there is a flaw in cancel!  I think whatever we canceled, we canceled every leg of every other order without escrow sent in :) LOL it was going too well, so cancel has a bug.  I think it cancels everything whether is a pending trade or not.  HMMM.
Ok lets not cancel til I check that out.

I will have to re-enter my big trade again, Alex you didnt enter the buy right?

That makes sense! I'm putting back my buy order now.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:57:11 pm
Heres a new one Alex if you want to buy the opposing order:

exec order sell 500000 rbbp .07


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 08:59:33 pm
I see your order, I just entered a new sale for 245111 @ .01 also.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 08:59:54 pm
Heres a new one Alex if you want to buy the opposing order:

exec order sell 500000 rbbp .07

I had put the other before you I see this message. Just put that one too so I have 2 buy orders now.

biblepay-cli exec listorders               
{
  "Command": "listorders",
  "#": 0,
  "#": 1,
  "Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Hash": "000000000000000000000000000000008170e899d0c35c0c74c8d65a5675a528",
  "Symbol": "RBBP",
  "Action": "BUY",
  "Qty": 245111,
  "BBP_Price": 0.01,
  "#": 2,
  "Address": "yhXZrX7KCG9W7mSQt2mkkMP4VhePbDeGzU",
  "Hash": "00000000000000000000000000000000829dce4eab5aa41dddf551376c318dee",
  "Symbol": "RBBP",
  "Action": "SELL",
  "Qty": 500000,
  "BBP_Price": 0.07000000000000001
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 09:01:05 pm
hmm someone the 500000 is showing as sell?

But this is what I entered.

[email protected]:~# biblepay-cli exec order buy 500000  rbbp .07     
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 500000,
  "Price": 0.07000000000000001,
  "Rec Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Placing Order": "0000000000000000000000000000000002384ac7111ffe29564bd7296b679166"
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 09:02:35 pm
hmm someone the 500000 is showing as sell?

But this is what I entered.

[email protected]:~# biblepay-cli exec order buy 500000  rbbp .07     
{
  "Command": "order",
  "Action": "BUY",
  "Symbol": "RBBP",
  "Qty": 500000,
  "Price": 0.07000000000000001,
  "Rec Address": "yNKoGx96D7kMDJ3SkkwyZwz4v3Gmqwg453",
  "Placing Order": "0000000000000000000000000000000002384ac7111ffe29564bd7296b679166"
}

I think it was right, mine was Sell yours was buy, here is my exec history:

 "11/18/2017 9:00:02 PM": "SOLD 500000 RBBP @ 0.0700 TOTAL 35000.00BBP ORDER 00000000000000000000000000000000829dce4eab5aa41dddf551376c318dee."

Does your say BOT in tradehistory?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 09:03:57 pm
Well I guess I may have a misunderstand of what the listorders command is but I got all my orders filled:

[email protected]:~# biblepay-cli exec tradehistory
{
  "11/18/2017 8:28:30 PM": "BOT 50000 RBBP @ 0.0293 TOTAL 1465.00BBP ORDER 00000000000000000000000000000000e0e201d1d345628c3938949611c3ccbc.",
  "11/18/2017 9:00:02 PM": "BOT 245111 RBBP @ 0.0100 TOTAL 2451.11BBP ORDER 000000000000000000000000000000008170e899d0c35c0c74c8d65a5675a528.",
  "11/18/2017 9:00:02 PM": "BOT 500000 RBBP @ 0.0700 TOTAL 35000.00BBP ORDER 0000000000000000000000000000000002384ac7111ffe29564bd7296b679166."
}

Before the two:
"retirement_account_balance": 123030,

After the two:
  "retirement_account_balance": 868141,

Seems to match!

Edit: Yup, it says BOT.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 09:09:03 pm
Well I guess I may have a misunderstand of what the listorders command is but I got all my orders filled:

[email protected]:~# biblepay-cli exec tradehistory
{
  "11/18/2017 8:28:30 PM": "BOT 50000 RBBP @ 0.0293 TOTAL 1465.00BBP ORDER 00000000000000000000000000000000e0e201d1d345628c3938949611c3ccbc.",
  "11/18/2017 9:00:02 PM": "BOT 245111 RBBP @ 0.0100 TOTAL 2451.11BBP ORDER 000000000000000000000000000000008170e899d0c35c0c74c8d65a5675a528.",
  "11/18/2017 9:00:02 PM": "BOT 500000 RBBP @ 0.0700 TOTAL 35000.00BBP ORDER 0000000000000000000000000000000002384ac7111ffe29564bd7296b679166."
}

Before the two:
"retirement_account_balance": 123030,

After the two:
  "retirement_account_balance": 868141,

Seems to match!

Edit: Yup, it says BOT.

Yeah, I was probably the one in the listorders at the time, but you can tell by writing down the hash- the hash is different for the Sale and for the Buy.

Im glad about your balance increasing properly, but mine has not gone down by 500,000.
(Which is impossible, because the money in BBP can only be in one wallet at a time).  It has to be either that its not picked up yet because of the confirm time, Or, a caching problem.

Ill wait a couple more blocks and check it.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 09:13:43 pm
Oh ok. I assumed that "listorders" was only to show my own order that I placed that's why (vs orderbook being all of them). My bad.

And yup, on top of seeing my RBBP increasing, I can also see that I sent you my BBP (most recent transaction at 8 confirmations right now)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 09:18:09 pm
Oh ok. I assumed that "listorders" was only to show my own order that I placed that's why (vs orderbook being all of them). My bad.

And yup, on top of seeing my RBBP increasing, I can also see that I sent you my BBP (most recent transaction at 8 confirmations right now)

Yeah that may be a good idea, to filter it by their own orders and have a separate command for all.
Well it worked fairly well but after rebooting I still have 975000 retirement coins, so I have to do some debugging to find out why it didnt decrease. I already traced the coins I sent you and they are all colored, so that part worked.  Ill also look at the cancel order logic.

Thanks for helping test it.  Ill have to take care of some things soon, so have a good night.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 09:22:45 pm
Alright, no worries! Glad I could help.

On a side note, I was wondering what were the param for testnet.
For example, can I fire up some beast nodes to try to speed up the generation of blocks/transaction confirmations or will it just adjust automatically so it would be in vain or not advisable for some other reasons.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 18, 2017, 09:31:16 pm
Alright, no worries! Glad I could help.

On a side note, I was wondering what were the param for testnet.
For example, can I fire up some beast nodes to try to speed up the generation of blocks/transaction confirmations or will it just adjust automatically so it would be in vain or not advisable for some other reasons.

I changed testnet over from 7 mins to 1 min block targets about 45 days ago to speed up sanctuary testing as we were having a horrible time trying to get budgets working, thank God that is past us.  But now  its locked in that way, at least until testing dies off again and a mandatory is scheduled. 
No it would be fruitless to push a lot of power to testnet, it would just make the diff rise.  Then when you stop pumping n dumping us, that block would hang for 30+ minutes but due to our unique feature, the chain would reset back to normal diff after you leave us alone :) LOL.

Alright Ill be back tomorrow got to process some emails.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 18, 2017, 09:33:51 pm
I changed testnet over from 7 mins to 1 min block targets about 45 days ago to speed up sanctuary testing as we were having a horrible time trying to get budgets working, thank God that is past us.  But now  its locked in that way, at least until testing dies off again and a mandatory is scheduled. 
No it would be fruitless to push a lot of power to testnet, it would just make the diff rise.  Then when you stop pumping n dumping us, that block would hang for 30+ minutes but due to our unique feature, the chain would reset back to normal diff after you leave us alone :) LOL.

Alright Ill be back tomorrow got to process some emails.

Haha alright, I won't try that then :P
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 20, 2017, 04:40:03 pm
Ive fixed one of the two bugs in the retirement accounts so far.  I had to put that down for a little while in order to work on these e-commerce features.

So, e-commerce is just about ready to test in testnet. 

So far you can list the products from amazon, buy a product, track your order and see your order status history.

I need to write a wiki though similar to retirement accounts in order for you to understand how to test it.

The code has changed, so that will require an upgrade.  Ill be checking it in in about 15 minutes.

Is anyone out there up for an e-commerce test in about 20 minutes?


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 20, 2017, 05:32:49 pm
Here is a little Primer on BiblePay E-Commerce:

http://wiki.biblepay.org/Ecommerce


Please see directions.


The new Ecommerce code requires 1.0.6.2.   Please upgrade in testnet.



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 21, 2017, 04:54:01 pm
Just a quick summary here, so others know what we're talking about:

Quote
Hey Rob,

I was looking into why my block explorer had wrong values for the network hashrate and difficulty and discovered that is it using
"getnetworkhashps".

However, that call and the information provided by getmininginfo don't seem to match so I was wondering what was the difference?

Ex:

biblepay-cli getnetworkhashps
579044721503.7521

 biblepay-cli getmininginfo
 "networkhashps": 674642175106.5978

and Rob said to me

Quote
Yeah this is a little bit of an issue.  Basically the bitcoin call to getnetworkhashps has a default that is different than the wallet RPC call its making (I think its probably sending in a parameter, like 90 or something), I believe that is the number of blocks to go back.  Its just adding up the chainwork of each block and getting the average, and returning it. 

Since its wrong anyway we might as well try to get the correct networkhashps in testnet somehow and change it.
Since testnet uses f8000 which is different hashps than we are used to something needs lowered.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 21, 2017, 05:19:59 pm
I modified my explorer to instead use the getmininginfo for now and also fixed the difficulty.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 22, 2017, 07:59:46 pm
I modified my explorer to instead use the getmininginfo for now and also fixed the difficulty.

Thats awesome Alex, great job, thanks!

So I know its been really hectic lately especially IT wise, Im being pulled in the day by the other project, but now we should do some f8000 testing.

I did some basic tests on my windows machines, and it seems to solve our multiple-instance issue on the surface but now we should get together and address the block explorer HPS, and compare our testnet f8000 hps.

Alex I know you have some Ryzens, would you like to share your HPS you experience with f8000 with us and Ill share my windows hashes and my Vultr hashes?


Oh one other thing, on the e-commerce, if you will go ahead and set your actual real home delivery address in the client for the test, I am giving a free gift.  Im giving the actual bible seen in the wiki page to testnet testers.  This way we can test, receive a bible and also see the USPS tracking # in the client.  So if anyone wants to put in the info and go ahead and order it let me know the order guid and Ill see if the biblepay Mouse API worked or not.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 23, 2017, 04:21:04 am
what does it mean NEW START REQUIRED?  i have to run watchman again? thanks Rob
why MN jumped to this status?

interesting,that my status is new start req= i get rewarding  :o
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 23, 2017, 04:56:42 am
Thats awesome Alex, great job, thanks!

So I know its been really hectic lately especially IT wise, Im being pulled in the day by the other project, but now we should do some f8000 testing.

I did some basic tests on my windows machines, and it seems to solve our multiple-instance issue on the surface but now we should get together and address the block explorer HPS, and compare our testnet f8000 hps.

Alex I know you have some Ryzens, would you like to share your HPS you experience with f8000 with us and Ill share my windows hashes and my Vultr hashes?


Oh one other thing, on the e-commerce, if you will go ahead and set your actual real home delivery address in the client for the test, I am giving a free gift.  Im giving the actual bible seen in the wiki page to testnet testers.  This way we can test, receive a bible and also see the USPS tracking # in the client.  So if anyone wants to put in the info and go ahead and order it let me know the order guid and Ill see if the biblepay Mouse API worked or not.

So my Ryzen 7 is getting around 13 500 (genproclimit = 18) on f8000 but I need to do more tests with different genproclimits.

For the e-commerce test, that's very generous thank you! However, I was wondering if it would work for ppl living outside of the US or if it only works with US addresses for now?

Also, I'll have more free time starting tmr so tell me if there's anything else that needs to be tested!

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 23, 2017, 06:18:29 am
Alex Ryzen 1700 HPS 1 or HPS2? ... my ryzen give me HPS1=200 000 and HPS2=45000

and again any bug in masternodes syncing?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 23, 2017, 12:22:41 pm
Alex Ryzen 1700 HPS 1 or HPS2? ... my ryzen give me HPS1=200 000 and HPS2=45000

and again any bug in masternodes syncing?
So I think I caused the masternodes to go out of sync. On TestNet Im the only seed node (node.biblepay.org) so this particular issue wont happen in prod.  I shut down my seed node 30 hours ago because I was working on something and forget to restart it.  It looks like I resynced to everyone in testnet.
New start means you need to issue the start-many command from your controller.
I just restarted my 3 testnet nodes and they all say pre-enabled now.

Got to run out to the Thanksgiving family dinner, have a great Thanksgiving everyone!

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 23, 2017, 04:16:05 pm
but my Linux biblepayd doesnt working, i had to run it again: very weird
so i have to run from controller wallet classic command by msaternode alias-start NICK?
ill try when i will be at home: now im on nightshift
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 23, 2017, 06:21:30 pm
but my Linux biblepayd doesnt working, i had to run it again: very weird
so i have to run from controller wallet classic command by msaternode alias-start NICK?
ill try when i will be at home: now im on nightshift
What do you mean when you say linux not working?  Not syncing?  It probably lost all its nodes when I was offline. 
Yes, from the controller wallet, just do a 'masternode start-all'.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 23, 2017, 06:28:49 pm
I have a Ryzen CPU mining BiblePay,

"AMD RYZEN 7 1700 8-Core 3.0 GHz (3.7 GHz Turbo) Socket AM4 65W YD1700BBAEBOX Desktop Processor"
https://www.newegg.com/Product/Product.aspx?Item=N82E16819113428&cm_re=ryzen_7-_-19-113-428-_-Product

It has Ubuntu 16.04 installed and an SSD drive
I overclocked it from 3.0GHz to 3.65GHz

it currently has been solo mining and is running v1.0.6.1 of BiblePay on mainnet
At 26 mining threads (100% CPU) I am getting a HPS of 280k

====

What is f8000?
Ill switch the pc to testnet and report back
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 23, 2017, 06:35:56 pm
So, e-commerce is just about ready to test in testnet. 

So far you can list the products from amazon, buy a product, track your order and see your order status history.

I need to write a wiki though similar to retirement accounts in order for you to understand how to test it.

The code has changed, so that will require an upgrade.  Ill be checking it in in about 15 minutes.

Is anyone out there up for an e-commerce test?

Here is a little Primer on BiblePay E-Commerce:

http://wiki.biblepay.org/Ecommerce

Please see directions.

The new Ecommerce code requires 1.0.6.2.   Please upgrade in testnet.

Oh one other thing, on the e-commerce, if you will go ahead and set your actual real home delivery address in the client for the test, I am giving a free gift.  Im giving the actual bible seen in the wiki page to testnet testers.  This way we can test, receive a bible and also see the USPS tracking # in the client.  So if anyone wants to put in the info and go ahead and order it let me know the order guid and Ill see if the biblepay Mouse API worked or not.

Ill update my masternode to v1.0.6.2 right now

And update my biblepay.conf
delivery_name
delivery_address
delivery_address2
delivery_city
delivery_state
delivery_zip
delivery_phone

Ecommerce Commands:
exec listproducts
exec buyproduct 0718083291
exec orderstatus

===

I think Im the only enabled masternode at the moment? Do I need to reindex?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 23, 2017, 08:04:36 pm
For the ecommerce config,

is it okay to have spaces in the config values?
Do I need to put double quotes around values with spaces?

For state should I use TX or Texas?
For phone do I need to add dashes or anything?

Thanks!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 23, 2017, 09:38:21 pm
./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
Delivery name, address, city, state, zip, and phone must be populated.  Please modify your biblepay.conf file to have: delivery_name, delivery_address, delivery_address2 [OPTIONAL], delivery_city, delivery_state, delivery_zip, and delivery_phone populated.

I have the main biblepay.conf file inside ~/.biblepayconf edited with these values added hmmmm
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 23, 2017, 10:29:23 pm
I tested v1.0.6.2 in testnet on my Ryzen,
at 26 threads I got 12.3-13k HPS, it fluctuated alot in that range
Does this seem correct? >.>
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 23, 2017, 10:32:06 pm
I tested v1.0.6.2 in testnet on my Ryzen,
at 26 threads I got 12.3-13k HPS, it fluctuated alot in that range
Does this seem correct? >.>

I'm getting around 13 500 (genproclimit = 18) with mine so I guess it is!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 24, 2017, 03:14:37 pm
how long will be being ASSETID=999?

ROB: now only you and me ENABLED masternodes
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 24, 2017, 07:43:33 pm
Hmm I just noticed my masternode on testnet actually crashed (biblepayd stopped running on 2017-11-23 10:59:35) . Yet, I've still been receiving rewards from it even though it wasn't running.

I think klondike noticed the same before editing his message.

Edit: Also not sure if useful but I have a block explorer on testnet too (https://testnet.biblepay-explorer.org/). No guaranteeing the uptime of this one as it is on a really small machine and I'm doing tests on it!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 25, 2017, 02:43:08 am
nice testnet explorer,perfect  :o

edit:// for 2 masternodes on 1 controller win wallet is tutorial same?  again send 500k to controller wallet and compile?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 25, 2017, 11:41:26 am
masternode was shut down on it's own.

updated the wallet from git.
started the daemon . 
after re-syncing got the status "NEW_START_REQUIRED"

rebooted the VPS.
started the daemon . 
after a while the same :  "NEW_START_REQUIRED"

checking watchdog :

 cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py
Invalid Masternode Status, cannot continue.

what did I do wrong ?

thanks

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 25, 2017, 05:05:49 pm
after re-syncing got the status "NEW_START_REQUIRED"

I think you just need to run the masternode start-alias command from the controller wallet:

Code: [Select]
masternode start-alias SANCTUARY_ALIAS
replace SANCTUARY_ALIAS with the label/alias you named your masternode address
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 26, 2017, 03:02:56 am
tiras,   yes like togo wrote: i dit it same

VPS rebooted, started daemon then started watchdog and then in controller wallet did command :   masternode start-alias POKUS and worked
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on November 26, 2017, 06:29:32 am
My laptop had some problems, so my masternode went down. But I am syncing as we speak, so I should be online again soon.

Aside from that, I'm taking a step back from the crypto world, for a while at least. In my experience, there is so much power and greed involved in bitcoin at the moment, that I feel I can't really cope with the pressure of 'keeping up with the news'. Core vs Jihan etc. So I'm blocking all bitcoin-related sites for a while.

This forum will be the only crypto-related thing I will be keeping an eye on. I will keep the masternode enabled to support our testnet, and if I find the time I will write a guide for the pool (I'm sorry I didn't get to that Rob, and if anyone else want to give it a go, be my guest).
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 09:14:00 am
For the ecommerce config,

is it okay to have spaces in the config values?
Do I need to put double quotes around values with spaces?

For state should I use TX or Texas?
For phone do I need to add dashes or anything?

Thanks!
Hi Togo,
I tested spaces the other day and the spaces actually work, without quotes. 

For state, please use TX.  For Phone yes please use the dashes so you have a 12 character phone.

This will be interesting, let me know when you place the order and Ill see if any errors occurred.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 09:16:50 am
My laptop had some problems, so my masternode went down. But I am syncing as we speak, so I should be online again soon.

Aside from that, I'm taking a step back from the crypto world, for a while at least. In my experience, there is so much power and greed involved in bitcoin at the moment, that I feel I can't really cope with the pressure of 'keeping up with the news'. Core vs Jihan etc. So I'm blocking all bitcoin-related sites for a while.

This forum will be the only crypto-related thing I will be keeping an eye on. I will keep the masternode enabled to support our testnet, and if I find the time I will write a guide for the pool (I'm sorry I didn't get to that Rob, and if anyone else want to give it a go, be my guest).

Thanks Jaap, I commend your decision!  Im going through the same thing right now- the other community is begging me to do something greedy, to switch to a base of a private version of Ethereum and I said no, I cant take it, I would leave, and besides Im here for BiblePay forever now.  The Greed is killing Americans, and they are choking Jesus out of their lives.  How much is enough?

Anyway yes, once we get this testnet bug-free hopefully you will be back by Christmas to launch a full node.

Have a good one in the mean time.
Rob
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 09:20:08 am
masternode was shut down on it's own.

updated the wallet from git.
started the daemon . 
after re-syncing got the status "NEW_START_REQUIRED"

rebooted the VPS.
started the daemon . 
after a while the same :  "NEW_START_REQUIRED"

checking watchdog :

 cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py
Invalid Masternode Status, cannot continue.

what did I do wrong ?

thanks

I think klondike already answered but I wanted to add:
The masternode requires a status of "999" before it actually listens to our commands (I know, pain), so add this into the process:
After rebooting a masternode wait until 'mnsync status' shows 999, then issue the commands from the controller like start-many etc.

I did prove the other day that you do not have to restart a masternode (physically) when it says new start required.  You can do the start-many and it will respond, as long as its already synced.

Another words life in prod should be like this:

As days go by, and no upgrades are being pushed out:  If you ever see new start required, you go to your controller and issue the start-many command.

Reboots should only be necessary when upgrades (to the software) are required.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 09:31:26 am
So my Ryzen 7 is getting around 13 500 (genproclimit = 18) on f8000 but I need to do more tests with different genproclimits.

For the e-commerce test, that's very generous thank you! However, I was wondering if it would work for ppl living outside of the US or if it only works with US addresses for now?

Also, I'll have more free time starting tmr so tell me if there's anything else that needs to be tested!

Sweet, so Alex was getting 13,500 on a Ryzen, and on my old 3 year old desktop (AMD 6 core, 2.8ghz) I am getting 3500 hps.
This is pretty much inline looking at the processor specs (8 cores, 4.0 ghz, more threads per core, 4* the performance) yielding 4* the hash speed I am seeing on my older hardware. 
I did a test, where I ran biblepay twice on my desktop, and Im not seeing any addl throughput, and that is inline with Alexs observation of consuming the entire 100% of the processor.  So far so good.
Now we have to look at Togos speed.


Edit: I dont see any problems on windows vs linux.  Im running at 3000 HPS in windows on my current desktop.  Ill test Vultr linux instances in a minute.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 09:35:09 am
I tested v1.0.6.2 in testnet on my Ryzen,
at 26 threads I got 12.3-13k HPS, it fluctuated alot in that range
Does this seem correct? >.>
Ah huh, great!  So you are inline with Alex's readings on his ryzen of about 13000.  Yeah, so far so good.  Let me test out vultr and Ill report back.
Its a $40 per month 4 core debian.

EDIT:  Ok, so Im getting about 900 HPS on the $10 a month vultr debian (which is really the same as the $5, it just has 8Gig ram instead of 4Gig), and getting 4000 HPS on the $40 per month 4-core-debian.  Which means the Ryzen is really a beast!  I dont see any problems so far, just a little interesting that my 3 year old desktop matches the $40 per month rented node.  However on the great side, there is no huge disparity between windows and linux now.  I have 3.5K HPS on my windows box, and 4K HPS on the $40 per month rented linux box.




Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 26, 2017, 10:17:25 am
Tested ecommerce again!

Facepalm... I had one config key misspelled... hahaha

I have a new error now:

Code: [Select]
./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
BAD USERID

I believe these are the relevant lines in the code, I couldnt find USERID though:

https://github.com/biblepay/biblepay/blob/9f4868bd447b2346bd1ddd5f04207cec27127a9c/src/rpcblockchain.cpp#L2036

https://github.com/biblepay/biblepay/blob/9f4868bd447b2346bd1ddd5f04207cec27127a9c/src/rpcblockchain.cpp#L1292
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 26, 2017, 01:52:19 pm
guys: when you talking about HPS what you talk HPS1 or HPS2?

my ryzen 1700 linux= 205 000+ HPS 90%loading CPU

(https://i.imgur.com/4gf0exd.png)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 26, 2017, 04:58:01 pm
tiras,   yes like togo wrote: i dit it same

VPS rebooted, started daemon then started watchdog and then in controller wallet did command :   masternode start-alias POKUS and worked

thanks.   I also updated controller node and started with "start-alias"  .  looks good now
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on November 26, 2017, 05:01:35 pm
I think klondike already answered but I wanted to add:
The masternode requires a status of "999" before it actually listens to our commands (I know, pain), so add this into the process:
After rebooting a masternode wait until 'mnsync status' shows 999, then issue the commands from the controller like start-many etc.

I did prove the other day that you do not have to restart a masternode (physically) when it says new start required.  You can do the start-many and it will respond, as long as its already synced.

Another words life in prod should be like this:

As days go by, and no upgrades are being pushed out:  If you ever see new start required, you go to your controller and issue the start-many command.

Reboots should only be necessary when upgrades (to the software) are required.

thanks Admin.  good to know for future
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 05:34:32 pm
guys: when you talking about HPS what you talk HPS1 or HPS2?

my ryzen 1700 linux= 205 000+ HPS 90%loading CPU

(https://i.imgur.com/4gf0exd.png)
In prod, the HPS is faster, but allows the multi-instance exploit.  In Testnet, f8000 is enabled, and offers no gain when running dual instances.
Please do a getmininginfo in Testnet to see your HPS, and compare to Alex's 13,500 HPS.  Im getting 4K HPS on my windows dev machine.

(In f8000)

EDIT: Pool mining should be disabled in testnet for this test; just to ensure the thing isnt trying to reconnect to the pool every 60 secs.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 05:39:58 pm
Tested ecommerce again!

Facepalm... I had one config key misspelled... hahaha

I have a new error now:

Code: [Select]
./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
BAD USERID

I believe these are the relevant lines in the code, I couldnt find USERID though:

https://github.com/biblepay/biblepay/blob/9f4868bd447b2346bd1ddd5f04207cec27127a9c/src/rpcblockchain.cpp#L2036

https://github.com/biblepay/biblepay/blob/9f4868bd447b2346bd1ddd5f04207cec27127a9c/src/rpcblockchain.cpp#L1292


Very interesting, OK cool, Ill try it again and might have a few questions.  I havent bought anything yet from biblepay-cli, I bought mine through windows-qt, from the RPC.  I got my bible in the mail 2 days later, it seems pretty interesting so far.

Let me try to reproduce...


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 26, 2017, 06:24:21 pm
Hmm I just noticed my masternode on testnet actually crashed (biblepayd stopped running on 2017-11-23 10:59:35) . Yet, I've still been receiving rewards from it even though it wasn't running.

I think klondike noticed the same before editing his message.

Edit: Also not sure if useful but I have a block explorer on testnet too (https://testnet.biblepay-explorer.org/). No guaranteeing the uptime of this one as it is on a really small machine and I'm doing tests on it!

Hey Rob, I was wondering if you saw that message.

I would need to check the logs again but I have been receiving masternode rewards for 1 day if not 2 while biblepayd crashed/wasn't running.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 06:43:50 pm
Hey Rob, I was wondering if you saw that message.

I would need to check the logs again but I have been receiving masternode rewards for 1 day if not 2 while biblepayd crashed/wasn't running.

Oh OK cool, I havent had any nagging crashes, but I can investigate if you can provide the last page of the debug log before the crash.

On the payments, if you could please check to see if the masternode status is 'Enabled' on a node other than your masternode - and that your masternode is actually in sync.  If the masternode is in sync, it should be able to vote for itself for payments if its status is 'enabled' on everyone elses client.  Of course it has to have watchman running though.  If you want to give your IP I can tell you right now what the status is on this end?

Great on testnet BX, thats cool.

Yeah, I forgot to answer you on the Ecommerce post a while back when Thanksgiving hit.  Right now, the Mouse API only supports US deliveries.  But whats nice is we have the capaibility to deliver through Walmart and AMazon to the EU!  But first Id like to see how many orders we receive in the US to ensure its worth expanding to the EU (because its more work and more to support).  If we sell quite a few items per month Ill expand the API to include more countries each month.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 26, 2017, 06:52:43 pm
Oh OK cool, I havent had any nagging crashes, but I can investigate if you can provide the last page of the debug log before the crash.

On the payments, if you could please check to see if the masternode status is 'Enabled' on a node other than your masternode - and that your masternode is actually in sync.  If the masternode is in sync, it should be able to vote for itself for payments if its status is 'enabled' on everyone elses client.  Of course it has to have watchman running though.  If you want to give your IP I can tell you right now what the status is on this end?

Great on testnet BX, thats cool.

Yeah, I forgot to answer you on the Ecommerce post a while back when Thanksgiving hit.  Right now, the Mouse API only supports US deliveries.  But whats nice is we have the capaibility to deliver through Walmart and AMazon to the EU!  But first Id like to see how many orders we receive in the US to ensure its worth expanding to the EU (because its more work and more to support).  If we sell quite a few items per month Ill expand the API to include more countries each month.

There wasn't really anything in the log except this:
2017-11-23 10:58:07 ProcessNewBlock : ACCEPTED
2017-11-23 10:59:35 ERROR: AcceptBlockHeader: block is marked invalid
2017-11-23 10:59:35 ERROR: invalid header received d202afcba304c82b59ead0c82bbb545c65d5206f4318fc072ae6aa1f9fa83234

Is there a way to get more things in the debug.log (logging levels)? If so, I will just run it with the most logging possible.

My masternode is enabled right now as I restarted biblepayd when it crashed and restarted it (208.68.37.149 ). What I am going to do now is kill biblepayd manually now and see if it still stays enabled and/or if I still keep receiving reward.

For the ecommerce post, I thought so too. Amazon is set to launch in Australia soon so maybe deliveries here will be possible too!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 07:13:18 pm
Tested ecommerce again!

Facepalm... I had one config key misspelled... hahaha

I have a new error now:

Code: [Select]
./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
BAD USERID

I believe these are the relevant lines in the code, I couldnt find USERID though:

https://github.com/biblepay/biblepay/blob/9f4868bd447b2346bd1ddd5f04207cec27127a9c/src/rpcblockchain.cpp#L2036

https://github.com/biblepay/biblepay/blob/9f4868bd447b2346bd1ddd5f04207cec27127a9c/src/rpcblockchain.cpp#L1292


Hi Togo,

Ok, I tracked down the "BAD USERID" error and I see whats happening- in the abstraction layer where AWS stores the order, there was an issue with having blank Email address, so I fixed that issue and it is deployed again, and, I also tested this on biblepay-cli vs QT and it actually works in both CLI and biblpayd and biblepay-qt, so its OK if you want to test it again on the -cli version.

EDIT: I also added more verbose error messages so if any field in the config is not stored you will get an error for that field - in the next version.



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 07:21:02 pm
There wasn't really anything in the log except this:
2017-11-23 10:58:07 ProcessNewBlock : ACCEPTED
2017-11-23 10:59:35 ERROR: AcceptBlockHeader: block is marked invalid
2017-11-23 10:59:35 ERROR: invalid header received d202afcba304c82b59ead0c82bbb545c65d5206f4318fc072ae6aa1f9fa83234

Is there a way to get more things in the debug.log (logging levels)? If so, I will just run it with the most logging possible.

My masternode is enabled right now as I restarted biblepayd when it crashed and restarted it (208.68.37.149 ). What I am going to do now is kill biblepayd manually now and see if it still stays enabled and/or if I still keep receiving reward.

For the ecommerce post, I thought so too. Amazon is set to launch in Australia soon so maybe deliveries here will be possible too!

Yeah, you can set 'debugmaster=true' if you want, but its going to create Huge debug files.  Those messages are primarily for masternode debugging but I suppose there could be one that is revealing.  Im thinking I am possibly part of the problem here because I didnt upgrade 2 of my 3 nodes to the 1062 version (thats the one where we fixed the biblehash issue) so I might have sent you a bad header.  But still, thats supposed to d-dos ME and not make you crash.   (Edit:  I just upgraded my other 2 nodes).  Building windows now for the controllers.


If you want to run it with that switch, and "possibly" run valgrind again in testnet mode, if you get a crash, I believe valgrind might show the source stack trace of where it died and if you get that I can see what caused it to segfault right there?

Yeah, that would be cool if we could actually create some e-commerce volume through biblepay purchases.  Im interested in seeing 4-5 btc of trading volume due to this, then we could go and get on more exchanges and get a biblepay debit card started if that all came about.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 26, 2017, 07:36:57 pm
Awesome! Ok I tried again:

Code: [Select]
./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
Address Valiation Failed (US Addresses Only)

Hmm I put my address into UPS address validation and it looks good,
only difference is they add the the dash and 4 extra zip code digits at the end
EDIT: Tried dash and extra 4 zip digits, same error hmmm
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 26, 2017, 07:55:52 pm
Yeah, you can set 'debugmaster=true' if you want, but its going to create Huge debug files.  Those messages are primarily for masternode debugging but I suppose there could be one that is revealing.  Im thinking I am possibly part of the problem here because I didnt upgrade 2 of my 3 nodes to the 1062 version (thats the one where we fixed the biblehash issue) so I might have sent you a bad header.  But still, thats supposed to d-dos ME and not make you crash.   (Edit:  I just upgraded my other 2 nodes).  Building windows now for the controllers.


If you want to run it with that switch, and "possibly" run valgrind again in testnet mode, if you get a crash, I believe valgrind might show the source stack trace of where it died and if you get that I can see what caused it to segfault right there?

Yeah, that would be cool if we could actually create some e-commerce volume through biblepay purchases.  Im interested in seeing 4-5 btc of trading volume due to this, then we could go and get on more exchanges and get a biblepay debit card started if that all came about.

Alright I will do that and and come back to you if I see anything.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 08:46:18 pm
Awesome! Ok I tried again:

Code: [Select]
./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
Address Valiation Failed (US Addresses Only)

Hmm I put my address into UPS address validation and it looks good,
only difference is they add the the dash and 4 extra zip code digits at the end
EDIT: Tried dash and extra 4 zip digits, same error hmmm

Ok cool, yeah there is a lot to this, I had to make the Mouse API send messages through SmartyStreets to get it prevalidate the address because the AWS Api will not do that piece of it.  I sent you a pm with a possible solution.

Thanks,
Rob
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 26, 2017, 09:01:13 pm
Code: [Select]
./biblepay-cli getwalletinfo
{
  "balance": 629975.95447854,
}

./biblepay-cli exec listproducts
{
    "Price": 12230,
}

./biblepay-cli exec buyproduct 0718083296
{
  "Command": "buyproduct",
  "OrderID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "TXID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "Status": "SUCCESS"
}

[email protected]1-34-47:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "balance": 617745.95441494,
}

./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "",
    "Status3": "",
    "Details": ""
  }
}

Success!

Looks like for key delivery_address2 it did not like the # I had in the value
For example I had delivery_address=Apt #12345
Removing the Hashtag worked!
Thanks Rob! :)
(Im off to bed for now!)

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 26, 2017, 09:15:49 pm
Code: [Select]
./biblepay-cli getwalletinfo
{
  "balance": 629975.95447854,
}

./biblepay-cli exec listproducts
{
    "Price": 12230,
}

./biblepay-cli exec buyproduct 0718083296
{
  "Command": "buyproduct",
  "OrderID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "TXID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "Status": "SUCCESS"
}

[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "balance": 617745.95441494,
}

./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "",
    "Status3": "",
    "Details": ""
  }
}

Success!

Looks like for key delivery_address2 it did not like the # I had in the value
For example I had delivery_address=Apt #12345
Removing the Hashtag worked!
Thanks Rob! :)
(Im off to bed for now!)

Oh wow, thats great!  Sweet.

It looks like it went through.  Ill check on the tracking status in the morning and see if the message is going through.  Technically you are supposed to be able to do the list orderstatus and see the tracking.  Lets check that in the morning.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 27, 2017, 04:05:18 am
Alright so I killed biblepayd for about 3 hours now, I checked it is actually not running on the node and it is not. However, I am still receiving  rewards for it. I checked from another node and it is also still showing as enabled. Is that normal?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 27, 2017, 06:26:49 am
i have answer how it working :
any  MN script/algo checking how many MN exists in chain, you can check it in masternode winners+masternode winner and rewarding is fall time

205 block mined in 1day=exists 100 masternodes= 205/100=every MN get 2,05 rewards from block and exists any proporcional dividing.On DASH masternode is rewarding proporcional few blocks forward
in debug win you can check it
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 27, 2017, 06:39:12 am
@Klondike

I'm more talking about the fact that I have a non-functioning masternode (since biblepayd isn't running anymore on it) still (active?) and receiving rewards.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 27, 2017, 06:39:59 am
In prod, the HPS is faster, but allows the multi-instance exploit.  In Testnet, f8000 is enabled, and offers no gain when running dual instances.
Please do a getmininginfo in Testnet to see your HPS, and compare to Alex's 13,500 HPS.  Im getting 4K HPS on my windows dev machine.

(In f8000)

EDIT: Pool mining should be disabled in testnet for this test; just to ensure the thing isnt trying to reconnect to the pool every 60 secs.
yes, true, im tested in tesnet ryzen and get HSP=13000 cpuproclimit=20  ;)

Alex how do you know,that your MN is offline? im asked Rob same things like you,w/response from him,but laterz my MN didnt receiving rewards, you getting how long rewards? by me your controller or VPS machine mining :P

yesterday im offed my MN and receiving rewards stoped
(https://i.imgur.com/5nO2PvS.png)

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 27, 2017, 06:43:50 am
yes, true, im tested in tesnet ryzen and get HSP=13000 cpuproclimit=20  ;)

Alex how do you know,that your MN is offline? im asked Rob same things like you,w/response from him,but laterz my MN didnt receiving rewards, you getting how long rewards? by me your controller or VPS machine mining :P

I killed biblepayd myself on that masternode for testing purposes and I'm still receive rewards for it.

Edit: Killed it at 1am CT time and at the time I'm writing this (6.46am CT), I am still receiving rewards for it.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 27, 2017, 06:55:33 am
and checked your falltime in debug win masternode winners?  may your wallet is still between proporcional winners
or
you mining with controller :D

Nah it's masternode reward for that specific node. Hopefully Rob can shed some light on that.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 27, 2017, 07:20:01 am
do princtscreen from winners debug and transactions rewards and post here
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 27, 2017, 07:31:38 am
Alright so I killed biblepayd for about 3 hours now, I checked it is actually not running on the node and it is not. However, I am still receiving  rewards for it. I checked from another node and it is also still showing as enabled. Is that normal?
Yeah, thats normal for up to 1 day.  Basically, when your node goes through the pain of becoming "Enabled" you have convinced all the other sanctuaries into voting you into existence for payment (they send gobject vote commands to each other until they agree on a hard ranked list).  Then they trust you for up to 24 hours.  During those 24 hours, your "watchdog" may expire meaning your sanctuary would have to vote for yourself.  Your vote will only go through if biblepayd is actually UP when you are called (so its risky, its called POSE - proof of service).  The node would definitely get caught within 32 hours of being down at the very longest (as watchdogs are 8 hour durations).

But anyway, once you are Enabled and trusted you have a place in the payment queue.  The other nodes will keep voting for your place to be kept, meaning that when is your turn to be paid, another node will pay you regardless of your real status, to keep the "hard" superblock iterator going.  Thats why our blocks with sancs enabled are about 1/2 the amount: the miner gets about half of position 0, the foreign sanctuary from the payment vector gets the other 1/2 and he may not be online (although with POSE he probably would be online).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 27, 2017, 07:42:28 am
Oh ok that makes sense! Last time I had biblepayd down for about 2 days and I was still receiving rewards for it that why I got worried and actually decided to test it.

I will try to see how long I can go on this run without biblepayd just for fun.

Also, I was thinking of implementing something like this on the block explorer http://hmcexplorer.com/masternode

I see some other explorers have that but I'm not sure where they got it from since it doesn't seem to be from the original iquidus explorer, it must be from a fork but I can't really find it.  I will try to dig it a little bit more else I will just implement it myself since it doesn't seem that hard to do.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 27, 2017, 07:49:56 am
Oh ok that makes sense! Last time I had biblepayd down for about 2 days and I was still receiving rewards for it that why I got worried and actually decided to test it.

I will try to see how long I can go on this run without biblepayd just for fun.

Also, I was thinking of implementing something like this on the block explorer http://hmcexplorer.com/masternode

I see some other explorers have that but I'm not sure where they got it from since it doesn't seem to be from the original iquidus explorer, it must be from a fork but I can't really find it.  I will try to dig it a little bit more else I will just implement it myself since it doesn't seem that hard to do.
Yeah, that would definitely be helpful to know exactly when you stop receiving your payment.  Thats a good exercise for us to go through.  (Id also like to know why we all reset to new-start-required before we are done testing, but I have a hypothesis on that.  I had to run some reports on my two vultr nodes yesterday- and we only have 5 masternodes.  I have a feeling if half the masternodes go offline during watchdog voting, the entire network gets reset.  Why?  Because I believe the gobject id is no long valid for the round.  In prod, obviously with over 100 nodes, one person cant influence the network like that.  )
Thats a good find on that masternode BX.  That would definitely be nice!  I found the 'masternodelist full' command gives you the extra details, if you have to write it yourself.
That reminds me of the web stuff that dash central created.  Im going to have to think about that and ensure we have all that working also  :P.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 27, 2017, 08:14:41 am
Yup it will definitely be interesting to see how long it can go for without biblepayd. I also have a second masternode running with valgrind just in case it crashes again so we get some useful info out of it.

Thanks for the command. It will definitely be useful if I have to implement it myself.

Agreed, something like dash central would be super nice to have !

Oh I also had a quick question, I was looking it at the chain param and I saw that:

Code: [Select]
        vSeeds.push_back(CDNSSeedData("biblepay.org", "dnsseed.biblepay.org"));
        vSeeds.push_back(CDNSSeedData("biblepay.org", "node.biblepay.org"));
        vSeeds.push_back(CDNSSeedData("masternode.io", "dnsseed.masternode.io"));
        vSeeds.push_back(CDNSSeedData("biblepaypay.io", "dnsseed.biblepaypay.io"));

I was wondering what all of these were; Are they (beside biblepay.org), just leftovers?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 27, 2017, 09:26:40 am
Yup it will definitely be interesting to see how long it can go for without biblepayd. I also have a second masternode running with valgrind just in case it crashes again so we get some useful info out of it.

Thanks for the command. It will definitely be useful if I have to implement it myself.

Agreed, something like dash central would be super nice to have !

Oh I also had a quick question, I was looking it at the chain param and I saw that:

Code: [Select]
        vSeeds.push_back(CDNSSeedData("biblepay.org", "dnsseed.biblepay.org"));
        vSeeds.push_back(CDNSSeedData("biblepay.org", "node.biblepay.org"));
        vSeeds.push_back(CDNSSeedData("masternode.io", "dnsseed.masternode.io"));
        vSeeds.push_back(CDNSSeedData("biblepaypay.io", "dnsseed.biblepaypay.io"));

I was wondering what all of these were; Are they (beside biblepay.org), just leftovers?
You may already know this , but if a wallet is opened for the first time with peers.dat missing in the desert on a wifi connection, it will only know about "biblepay.org", and have no clue how to insert any addnodes.  So biblepay.org being on the seed list, will give a list of its known peers to the wallet and then the wallet will populate peers.dat.  (Thats why its a fallacy when people say to addnodes into your config.  You really only need one good addnode in your config, and thats if node.biblepay.org is down). 

Anyway, I forgot to take those others out.  They are useless.

I did add happys old broken BX into the list though, I think I should swap it out with your BX before the Christmas release.

Ill remove those old ones now.

EDIT: Ok, I replaced happy's with explorer.biblepay.org.  Your explorer works great as a seed-node, in case node.biblepay.org is overloaded. 
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 27, 2017, 10:59:12 am
Oh my explorer is behind Cloudflare so it can't be used as a seed node! I could provide a seed node on seed.biblepay-explorer.org instead if you'd like.

Also, I just had an idea and I'm not sure what people think about it. That biblehash algorithm is really interesting and I kind of like to look at the bible verses in blocks sometimes so I decided to extract that information and provide it in a more "graphical way". I enabled it on the testnet block explorer.

Ex: https://testnet.biblepay-explorer.org/block/2680049a32edcd0acc4752f0aae5d5f87a1ac6e62f4cce0b8889ce4adf97f139

Still a work in progress.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 27, 2017, 01:07:44 pm
Oh my explorer is behind Cloudflare so it can't be used as a seed node! I could provide a seed node on seed.biblepay-explorer.org instead if you'd like.

Also, I just had an idea and I'm not sure what people think about it. That biblehash algorithm is really interesting and I kind of like to look at the bible verses in blocks sometimes so I decided to extract that information and provide it in a more "graphical way". I enabled it on the testnet block explorer.

Ex: https://testnet.biblepay-explorer.org/block/2680049a32edcd0acc4752f0aae5d5f87a1ac6e62f4cce0b8889ce4adf97f139

Still a work in progress.

Holy cow, thats cool.  Thats going to make the Prod block explorer something really, really special for the community.
Things like this, going the extra mile will be what makes or breaks this coin!
If we continue with features like this until we have over 9,000 users, this coin will be unstoppable.
I believe we have about 1300 right now.  I was telling Togo its going to be a hard upward drive to attract the next 8700 but I think its possible if we do something PR related like give away 250 BBP for every wallet download (I can install a faucet serial number in the download, and help with this) and Ill give away my seed funds to help.

Anyway thats really great!  This is not a feature request, just an idea, but when I saw your verses and the way you included the Book & Chapter to the right of the verse, it made me think of the possibility of mapping the book to the long book name (There is actually a function in the wallet for that, and I can gladly make it an rpc call also), anyway if you had that mapping you could include this javascript from RefTagger for pop up bible verses in context:

See this example on this page when you hover over a verse:
http://jesus-christ.us/JesusConciseCommandments.htm

Then if you like that verse you could read more about the verse. LOL.

EDIT: Oh ok 10-4 on the seed, well if its easy for you to point a DNS to it sure, dont want you to have to run an extra node.  The only port that they need is 40000 in prod, we probably dont need to worry about a seed for testnet but that port is 40001.



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 27, 2017, 01:44:50 pm
guys: can you to fix Explorer for mobile version? we have no to see difficult and network  ;)
thanks
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 27, 2017, 05:48:03 pm
@Rob oh that's really cool, I can certainly do that. How would that rpc call work?

Got you for the seed. Maybe at some point then depending on how I modify my infrastructure  and if we get really popular!
I will probably put it at dnssseed.biblepay-explorer.org when/if that happens.

@Klondike
It automatically removes it for aesthetic reasons if your screen is under 992px (original iquidus design choice).
I will have a look at it but mobile browsing is not on top of the list for me as it can get really tricky  :(.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 27, 2017, 05:55:59 pm
Code: [Select]
./biblepay-cli getwalletinfo
{
  "balance": 629975.95447854,
}

./biblepay-cli exec listproducts
{
    "Price": 12230,
}

./biblepay-cli exec buyproduct 0718083296
{
  "Command": "buyproduct",
  "OrderID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "TXID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "Status": "SUCCESS"
}

[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "balance": 617745.95441494,
}

./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "",
    "Status3": "",
    "Details": ""
  }
}

Success!

Looks like for key delivery_address2 it did not like the # I had in the value
For example I had delivery_address=Apt #12345
Removing the Hashtag worked!
Thanks Rob! :)
(Im off to bed for now!)

I added quicker order status updates for our users, so whoever orders the next bible in testnet should see more phases within a few hours.

Togo, on yours, you should see the tracking # now, can you please check?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 27, 2017, 06:21:25 pm
@Rob oh that's really cool, I can certainly do that. How would that rpc call work?

Got you for the seed. Maybe at some point then depending on how I modify my infrastructure  and if we get really popular!
I will probably put it at dnssseed.biblepay-explorer.org when/if that happens.

@Klondike
It automatically removes it for aesthetic reasons if your screen is under 992px (original iquidus design choice).
I will have a look at it but mobile browsing is not on top of the list for me as it can get really tricky  :(.

Ok cool, if you have the infrastructure Alex for a port forward, maybe you can forward 40000 to something.biblepay-explorer.org?  If you do just let me know and Ill add it to the base.  It would be nice to have more than me in there, because that external node is maxxed out with connections.  Now that I think about it, I can easily add my vultr4.biblepay.org node to dns seed (that will be a future sanctuary), OK thats done so we are good.

Anyway, on the Bible Verse RefTagger Pop-Ups: This would probably only work for you if you memorize them inside the code first and dump them in.  But for fun lets look at the calls:
exec books

This call gives you a list of all 66 books in the bible and the corresponding short names used in BiblePay during hashing.
So once you know the short names you can type:
exec bookname rev

And receive "REVELATION"
Or exec bookname mat and receive "MATTHEW".

So what you can do is if you saw for example "REV|1|1" in the biblehash you could expand that to "REVELATION 1:1" and place that on the page, include the reftagger javascript (by looking at the source of that prior page) in the BX, and then anytime someone hovers over the verse they would see the full reftagger verse popup :). 

EDIT: Note: You only have to include the reftagger stuff at the top of the page, so no ajax work to do in the page.  In the page, you just have "REVELATION 1:1" in the text somewhere, and reftagger picks that up automatically.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 27, 2017, 06:22:14 pm
Code: [Select]
./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "FILLING ORDER",
    "Status3": "USPS XXXXXXX",
    "Details": ""
  }
}

I see the tracking number! (replaced it with Xs)
USPS tracking service is currently down haha, so cant check online yet, but awesome!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 27, 2017, 06:26:26 pm
Code: [Select]
./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "FILLING ORDER",
    "Status3": "USPS XXXXXXX",
    "Details": ""
  }
}

I see the order status! (replaced it with Xs)

USPS tracking service is currently down haha, so cant check online yet, but awesome!

Oh thats great dude!
Yeah, a week ago I thought man its going to be so awesome to put Amazon inside the wallet, then this article came out :
https://www.thesun.co.uk/news/5004230/amazon-warehouse-working-conditions/

Im sure it will blow over, but its kind of disappointing to see a company with so much success be so greedy for profit.
I thought their warehouse workers made some money, but it says here they have tactics to hire people under minimum wage - similar to how the mechanical turks from AWS make .25 cents an hour...

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 28, 2017, 12:03:03 am
@Rob, found an easier way to do it without the rpc call. I will just swap it myself so I just need a list of all the abbreviations used by biblepay and their corresponding names.

Edit: Added something similar to reftagger.
https://testnet.biblepay-explorer.org/block/9ab71b36d99342ccd3db656e7804e84eec501b67b66ed983d915c5eac3aea15e

Edit2: Found the abbreviation list, will add them soon.

Edit3: Everything has been added. Pushed it to the prod explorer.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 28, 2017, 08:22:23 am
@Rob, found an easier way to do it without the rpc call. I will just swap it myself so I just need a list of all the abbreviations used by biblepay and their corresponding names.

Edit: Added something similar to reftagger.
https://testnet.biblepay-explorer.org/block/9ab71b36d99342ccd3db656e7804e84eec501b67b66ed983d915c5eac3aea15e

Edit2: Found the abbreviation list, will add them soon.

Edit3: Everything has been added. Pushed it to the prod explorer.

Dude, that is simply stunning!  I like the spinner that comes up while its retrieving the verse also!
I figured you would find the book list in the code LOL.

This is really what cryptoenthusiasts are looking for when I said we should find features to add value to BBP.
I know its only 16 hours of your work now, but Im telling you in the future, these type of things will be the cornerstone of biblepay if we dont go through the great trib soon.  Once we have enough organic users, people will be all over the internet mentioning things like this and driving us up to 80MM-120MM market cap.

Now I need to step up and add some myself :). 

Ill mention this feature in our other forum now and then you can talk about it when people reply....

Thanks!

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 28, 2017, 08:29:45 am
Haha Thanks, I'm trying to get the masternodes tab working now so the testnet explorer is going down every 2 min!

The verses feature is available on the prod explorer if somebody wants to look at it!

Edit: Btw, I just formatted the verses, the hover feature is all provided by biblegateway.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 28, 2017, 10:52:09 am
The masternode page is looking good and is pretty much done!

https://testnet.biblepay-explorer.org/sanctuaries
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on November 28, 2017, 03:52:16 pm
The masternode page is looking good and is pretty much done!

https://testnet.biblepay-explorer.org/sanctuaries

Awesome work Alex! Looking good :)

Looking at the masternode list, mine says 'NEW_START_REQUIRED' in your overview (84.29.208.33:40001). That's strange, because my masternode says 'ENABLED' when I call 'masternodelist' and my controller-wallet says 'WATCHDOG_EXPIRED'.

So I've got three different status-things going on with the same sanctuary :p I've been getting my payments and the both the sanctuary and controller-wallet are on the same chain:

Code: [Select]
22:40:29

getblockhash 53371


22:40:29

ad3302691447683831b4d4063211929960c4e3cb589e663119320979af1b2a21

What do you guys think this might mean?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 28, 2017, 05:05:56 pm
Well that's something I haven't figured out yet :P I'm not sure how often these updates are broadcasted/refreshed.

For example, if you "start" a masternode from the controller wallet, the status of that masternode will change automatically to pre-enabled I believe as it locally knows that you clicked on start. So, it's changing the status based on something it locally knows instead of something it receives from the network. Even though it says "successful", it doesn't mean it actually successfully started the masternode as I think it only means there was no error with the conf file and that it found the appropriate escrow amount (no check about the masternode being started!).

If the masternode was actually successfully started, other nodes on the network will take some time before getting the new network state of your masternode and it can be quite long :P

That's why it can be nice to have another node to see if it sees your masternode enabled or not. However as I said, you probably should wait a few hours before looking at that.

Maybe Rob can help us figure out that.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 28, 2017, 05:14:19 pm
Oh also if I may add, you may still receive rewards even if your masternode "dies" / is not valid anymore (up to 36 hours after it dies).
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 28, 2017, 05:25:48 pm
1.starting masternode being few minutes for me between 45-100minutes
2.after offline msaternode,you will be still receiving rewards = its call falltime
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 06:21:24 am
Oh also if I may add, you may still receive rewards even if your masternode "dies" / is not valid anymore (up to 36 hours after it dies).
Yes, that masternode list looks great!   Well at least its pulling the view from the wallet, so that puts the onus on us here to figure the rest out regarding consistency.

Btw, did you ever figure out the exact hours elapsed when you stopped receiving payments?

I have a tad little bit of insight on the PRE-ENABLED flag.   If you blindly call masternode start-alias (as most people do) the command is sent over the P2P port (40001), reaches the actual masternode and the masternode logs something to the effect of "masternode sync data not synced yet" and no error is raised (and a log is logged on the masternode but only if debugmaster=true).  So yeah, its a nuisance, but no work was ever put into it because there is a workaround.  The workaround is you must first go to the masternode and type mnsync status and know that it only follows controller commands if mnsync status is 999.  So in real life, we basically just need to click on the peer height in your controller to see if the node is in sync and then issue the command 5 mins later.  Its just a pitfall we need to know about.

One other thing on this topic:  If the masternode made enemies with a section of the network (IE ddossed 3 out of 5 masternodes), it will no longer follow the same potential fork.  Thats probably what happened here when I shut down my vultr nodes, we lost 2 of 5, and a couple who were only peers of vultr started mining their own chain.  Their mnsync status is then different than the other masternodes (because their payment ranking is different), causing all kinds of potential problems.  So the expectation is, in prod, with over 100 masternodes we will be clinging to the same chain due to the supermajority being on the same sync height.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 06:24:24 am
Awesome work Alex! Looking good :)

Looking at the masternode list, mine says 'NEW_START_REQUIRED' in your overview (84.29.208.33:40001). That's strange, because my masternode says 'ENABLED' when I call 'masternodelist' and my controller-wallet says 'WATCHDOG_EXPIRED'.

So I've got three different status-things going on with the same sanctuary :p I've been getting my payments and the both the sanctuary and controller-wallet are on the same chain:

Code: [Select]
22:40:29

getblockhash 53371


22:40:29

ad3302691447683831b4d4063211929960c4e3cb589e663119320979af1b2a21

What do you guys think this might mean?

Yeah, looking at Alex's testnet masternode list, something does look wrong....

Im showing you on my masternode list as enabled now (84.29.208.33).  First, you are right in that when you issue the command to start, the local wallet just changes the caption blindly.  However, the other values: watchdog_expired, Enabled, new_start_required should be network values. 

But looking at 45.76...64 and 45.76..42 those two are Enabled on my controller, my vultr, my other vultr, my dev machine but "Expired" in the explorer... Hmmmmm, explorer is synced though.  Thats strange.

Alex, what happens if you look at those 2 node statuses from the GUI?  Do they match the explorer?



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 29, 2017, 07:01:09 am
Let me check the timestamps and I will come back to you on when my masternode stopped receiving rewards after killing biblepayd (it looks like about 1 day - 1 day and a half)

Edit: Biblepayd killed on November 27 at 1am (CT) - Last reward received on November 28 at 12.29am (CT).

--

The masternode list is pulling data straight from the masternode list full command every time you call it so you get the most updated view that my node has every time.

For that specific node:

45.76.239.42 and 64 are showing as expired.

84.29.208.33 with new start required.

There's also an api call that gives the result of the masternode list full command on my node (the table is actually built from that):
https://testnet.biblepay-explorer.org/api/getsanctuaries

I know that it takes quite a lot of time for updates on status to be propagated. For example, my local testnet wallet is showing 64 as expired but 42 as new start required.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 29, 2017, 08:04:36 am
Just checked my logs and saw a spam of invalid block headers. I also noticed that there hasn't been any new block since the 28 lol. My explorer somehow went on a fork. I'm going to resync it now.

This is the last block it had:

biblepay-cli showblock 53062
{
  "hash": "6e9ffa1e3dcdd7e4bb71aac09ea7dded84fd60d8f03f9e82c24465049503386a",
  "confirmations": 1,
  "size": 299,
  "height": 53062,
  "version": 536870912,
  "merkleroot": "e587cae90aad4ca604309b0cef7e056ab243faf36d265a4ed8cd4199b99bcf08",
  "tx": [
    "e587cae90aad4ca604309b0cef7e056ab243faf36d265a4ed8cd4199b99bcf08"
  ],
  "time": 1511878192,
  "mediantime": 1511877871,
  "hrtime": "11-28-2017 14:09:52",
  "nonce": 4493,
  "bits": "1e008cae",
  "difficulty": 0.007108238289276392,
  "chainwork": "00000000000000000000000000000000000000000000000000002f38941f9161",
  "subsidy": 7524,
  "blockversion": "1.0.6.1",
  "masternodereward": 265834350462,
  "previousblockhash": "55a590732347a64b46eb06ab6ea5f3a451d5dd9eb9268b9e0b14a0e39b991f3d",
  "verses": "Pro|2|16| To deliver thee from the strange woman, even from the stranger which flattereth with her words;\r\nGen|25|29| And Jacob sod pottage: and Esau came from the field, and he was faint:\r\nJob|6|24| Teach me, and I will hold my tongue: and cause me to understand wherein I have erred.\r\nGen|13|10| And Lot lifted up his eyes, and beheld all the plain of Jordan, that it was well watered every where, before the LORD destroyed Sodom and Gomorrah, even as the garden of the LORD, like the land of Egypt, as thou comest unto Zoar.\r\nPsa|106|19| They made a calf in Horeb, and worshipped the molten image.\r\nExo|21|3| If he came in by himself, he shall go out by himself: if he were married, then his wife shall go out with him.\r\nJoh|20|17| Jesus saith unto her, Touch me not; for I am not yet ascended to my Father: but go to my brethren, and say unto them, I ascend unto my Father, and your Father; and to my God, and your God.\r\nCh2|20|36| And he joined himself with him to make ships to go to Tarshish: and they made the ships in Eziongaber.\r\n",
  "satisfiesbiblehash": "true",
  "biblehash": "00000034d22c72ed61b419b1eba74c1d7a93795445563f3d63dc80e069108c13",
  "prayers": ""
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 08:12:49 am
Just checked my logs and saw a spam of invalid block headers. I also noticed that there hasn't been any new block since the 28 lol. My explorer somehow went on a fork. I'm going to resync it now.

Yeah, btw, I have some inside info on why some forks start to occur (at least part of the problem).  If we have say 8 masternodes, and lets say 2 are only connected via 1 node to the rest, if that 1 node gets ddossed, that masternode will have a propensity to create its own chain (especially with our low diff on testnet).

Now the smoking gun here is our recent fix to the biblehash itself makes it much more likely that those running 1062 are all producing the same hashes.  So, somehow we should probably make an effort to ask everyone on testnet to upgrade to 1062.

What I can do from my side is force an upgrade to 1063, and force a protocol upgrade (meaning everyone lower than 1062 actually gets disconnected).  It might be worth doing between Dec 2 and Dec 20th just to ensure we dont have a lurking problem.

Let me take a look at the retirement issue before monkeying with it.  I think we were close on that but not quite done.

EDIT: BTW, you may have to delete your banlist.dat before resyncing to bring back all nodes into your testnet node.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 29, 2017, 08:22:55 am
I thought I would need to do that too but apparently not. No one has been banned even thought I was receiving "bad headers". I didn't think it would on a fork with 20 connections :(

I also just checked my masternode and it went on a fork too so I'm resyncing it too :(

It prob would be nice to force the upgrade.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 29, 2017, 08:33:57 am
I decided to look at the peers I was connected to using getpeerinfo and I think a lot of them are on a different chain (with the latest block being 53062).
Could you have a look at that on your own nodes Rob?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 08:43:02 am
I decided to look at the peers I was connected to using getpeerinfo and I think a lot of them are on a different chain (with the latest block being 53062).
Could you have a look at that on your own nodes Rob?
Hmm, I see a huge problem in getchaintips.  We have about 30 prior forks due to all those bad headers.
I think if I make a release with a few testnet checkpoints we can eliminte 99% of that  problem.

For now, Im seeing 54088:

08:41:19

getblockhash 54088

ad4510d1c7fa0ca1cda93c4119581374612737ea41fa5e9e338c65ebd273308a


Alex, try deleting mncache.dat on your 3 testnet nodes and banlist.dat and chainstate and blocks and resyncing?


Ill work on adding a few checkpoints now so we can all clear out our chaintips problems.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 29, 2017, 08:47:17 am
I just deleted blocks and chainstates and it's resyncing right now (the testnet explorer is actually already synced. It just takes a few minutes for the mongo database to reindex everything).

Somehow my nodes never banned anyone.

I just checked and I also have ad4510d1c7fa0ca1cda93c4119581374612737ea41fa5e9e338c65ebd273308a for 54088.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 09:10:17 am
I just deleted blocks and chainstates and it's resyncing right now (the testnet explorer is actually already synced. It just takes a few minutes for the mongo database to reindex everything).

Somehow my nodes never banned anyone.

I just checked and I also have ad4510d1c7fa0ca1cda93c4119581374612737ea41fa5e9e338c65ebd273308a for 54088.
Its possible my nodes banned you when you went on the fork originally (as you would be voting to not pay my 3 masternodes :)), thats why it gets so severe.  Your nodes say No Im not going to add a payee that I dont know about.  My nodes say you must pay these 5 nodes, in this order.

Alright I added checkpoints, and I counted 50 forks in getchaintips Before checkpoints.  Let me see how many we have now after checkpoints.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 29, 2017, 09:16:41 am
Oh ok. What is weird though is that I was still connected to 20 nodes and receiving bad headers before I resynced.

I'm now on the good chain and I am pretty sure I am connected to the same 20 nodes. (also isn't one of your node the seed node?). So it looks like I didn't ban anyone and no one banned me?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 09:33:53 am
Oh ok. What is weird though is that I was still connected to 20 nodes and receiving bad headers before I resynced.

I'm now on the good chain and I am pretty sure I am connected to the same 20 nodes. (also isn't one of your node the seed node?). So it looks like I didn't ban anyone and no one banned me?
Yes true, but it is also possible my node.biblepay.org only banned you for 1-8 hours (IE one d-dos level 1 ban per bad header received) putting you on a bad fork and while we were looking at it its possible the ban expired.

Anyway I was going to say this is such a critical test, before Christmas, I think we really need to fix the chaintip issue and force a protocol upgrade to 70709, just to ensure we have a long span of uptime for all of our core masternodes.

Just a heads up everyone, I am writing the code to force a network upgrade on testnet only, so please be ready to upgrade as during the next upgrade, all the nodes will disconnect on each other if they are running a prior to 1.0.6.3 version.

It should be out in about 30 mins....


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 10:57:13 am
1.0.6.3-Mandatory Upgrade for TESTNET

Please all, in testnet, please upgrade to 1.0.6.3.

The entire network is down until we upgrade.

Building windows for controllers now...

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 29, 2017, 11:46:25 am
how big will be traffic on VPS for masternodes?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on November 29, 2017, 11:51:28 am
The testnet BX has been upgraded.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 12:05:00 pm
how big will be traffic on VPS for masternodes?
Not much, masternodes only take up 10% more than bitcoin.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 12:17:20 pm
The testnet BX has been upgraded.

Success!

Upgraded all 3:

12:16:30

getchaintips


12:16:30

[
  {
    "height": 54194,
    "hash": "9a412d5c7faee2f5048a0dec4ba6ed45b81e595a834e43eef9c64a65d38700ac",
    "difficulty": 0.01934920419809971,
    "chainwork": "00000000000000000000000000000000000000000000000000002f6df8bc31f4",
    "branchlen": 0,
    "status": "active"
  }
]

Chaintips is clean!

Crossing fingers this trend continues til Christmas...

Still waiting for windows to finish compiling....

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 01:55:36 pm
A couple more tips:
If your getchaintips is not clean, restart with -reindex flag, and resync.

Next, if your sanctuary list differs from Alex, delete your mncache.dat and restart.

=-=-=-=-=

Windows compile of 1.0.6.3 is out there now, feel free to upgrade controllers.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 29, 2017, 02:13:44 pm
Not much, masternodes only take up 10% more than bitcoin.
wut? do you know what is traffic? how big will be internet traffic for 1 month? will be enough 500GB traffic?

im stuck ...

EDIT:// 1st im deleted mncache.dat and resyncing nad stuck still

EDIT:// 2nd test and still im on bad chain and stuck still

EDIT://3rd test and still on bad chain= deleted chainstate+blocks+peers.dat and stuck still

i gave up
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 29, 2017, 09:47:34 pm
wut? do you know what is traffic? how big will be internet traffic for 1 month? will be enough 500GB traffic?

im stuck ...

EDIT:// 1st im deleted mncache.dat and resyncing nad stuck still

EDIT:// 2nd test and still im on bad chain and stuck still

EDIT://3rd test and still on bad chain= deleted chainstate+blocks+peers.dat and stuck still

i gave up
I think you forgot to describe your question.  Just click Tools | Network Traffic and monitor it for a while.

Just delete your banlist.dat and your peers.dat and your mncache.dat and then sync.



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 30, 2017, 01:03:01 am
Rob: ouch  :o didnt know that we have calculator internet traffic in win: thanks:nice

Rob: im deleted peers.dat mncache and sync and still im on bad chain: banlist i hadnt in folder

EDIT:// im offline and received 2 rewards ... something is wrong after last update wallet

(https://i.imgur.com/o1vm2DD.png)

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 30, 2017, 06:41:57 am
Rob: ouch  :o didnt know that we have calculator internet traffic in win: thanks:nice

Rob: im deleted peers.dat mncache and sync and still im on bad chain: banlist i hadnt in folder

EDIT:// im offline and received 2 rewards ... something is wrong after last update wallet

(https://i.imgur.com/o1vm2DD.png)
Ive gone through this before and something is either cached in your mncache, peers (a ddossed node) or chainstate.

To be on the safe side :
cd \testnet3
rm blocks -R
rm chainstate -R
rm mncache.dat
rm peers.dat
rm banlist.dat

Then remove any extra .dat file for governance
Then resync.  I do not think you will end on the wrong chain after that as we have 6 masternodes on the chain with higher work now.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 30, 2017, 10:36:27 am
so deleted db.log and masternode is alive..... ENABLED

but what i see that we are all stuck on block 54 349  :P

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on November 30, 2017, 03:26:51 pm
so deleted db.log and masternode is alive..... ENABLED

but what i see that we are all stuck on block 54 349  :P

Yeah, it seems we're stuck...

Also, my masternode says 'UPDATE_REQUIRED' when I call 'masternodelist'. Never saw that before. I'm already on 1.0.6.3...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 30, 2017, 03:37:57 pm
now all working.........hmm....... may be Rob started mining,cos if mining is cpuproclimit=0 and nobody mining, we will be stucking on same block.....
now start receiving rewards

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on November 30, 2017, 03:45:28 pm
now all working.........hmm....... may be Rob started mining,cos if mining is cpuproclimit=0 and nobody mining, we will be stucking on same block.....
now start receive rewards

Yeah, I started mining just to be sure :P I'm also getting rewards now.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on November 30, 2017, 03:46:00 pm
Yeah, it seems we're stuck...

Also, my masternode says 'UPDATE_REQUIRED' when I call 'masternodelist'. Never saw that before. I'm already on 1.0.6.3...
UPDATE_REQUIRED seems to happen when your watchman database has your last protocol version active and enough time hasnt passed for it to know you upgraded.  If you were to delete mncache.dat and the watchman.db file, it should alleviate that.
But in reality no one does that, and it does get updated in 24 hours.  It should be fine now.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on November 30, 2017, 03:47:38 pm
what block are you on? im watching in peer list and any MNodes is on differents blocks  :o
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on November 30, 2017, 04:42:43 pm
UPDATE_REQUIRED seems to happen when your watchman database has your last protocol version active and enough time hasnt passed for it to know you upgraded.  If you were to delete mncache.dat and the watchman.db file, it should alleviate that.
But in reality no one does that, and it does get updated in 24 hours.  It should be fine now.

Thank you for the clarification :) I'll just wait it out then.

@klondike: I'm at block 54408 now.

Code: [Select]
23:41:53

getblockhash 54408


23:41:53

d8e499d40537776d83bc9ad893a95c8f37c312abf5a3cd1d4adc7d393576914e
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on November 30, 2017, 10:18:49 pm
I received the Bible in the mail Tuesday morning and got it out today, Thank you Rob!

./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "FILLING ORDER",
    "Status3": "USPS XXXXX",
    "Details": ""
  }
}
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 01, 2017, 12:09:31 am
Hey Rob, I'm modifying some things and I can now provide a dns seed node for mainnnet and testnet (should be available soon).

mainnet:
dnsseed.biblepay-explorer.org

testnet:
test.dnsseed.biblepay-explorer.org

Edit: just to avoid the confusion, these will be dns seed nodes so they will just crawl the network and give back a list fo reliable nodes to connect to! I "may" also provide regular seed nodes.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 01, 2017, 01:56:00 am
jaapgvk your masternode "NEW_START_REQUIRED"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 01, 2017, 10:58:56 am
jaapgvk your masternode "NEW_START_REQUIRED"

Thanks! Tried a restart. Let's see what it does...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 02, 2017, 04:48:01 am
its normall,that my win-controller wallet jump to other chain?  ... will be this forks on PROD? i hope that no ...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 02, 2017, 07:00:31 am
On a good note, both my dns seeds are now up and running!

On a bad one, it looks like my BX went on a fork (stuck on block 55990 now). I'm restarting it now.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 07:26:02 am
Hey Rob, I'm modifying some things and I can now provide a dns seed node for mainnnet and testnet (should be available soon).

mainnet:
dnsseed.biblepay-explorer.org

testnet:
test.dnsseed.biblepay-explorer.org

Edit: just to avoid the confusion, these will be dns seed nodes so they will just crawl the network and give back a list fo reliable nodes to connect to! I "may" also provide regular seed nodes.

Thanks a lot alex, I added your two DNS seed nodes to ThreadOpenAddedConnections.  This is called once when the wallet starts and does a one shot add of normal DNS addresses (we have 4 now in here):
      AddSeedNode("node.biblepay.org"); // Volunteers welcome to run external nodes and we will add during future releases
      AddSeedNode("99.198.174.212");    //PlainKoin
      AddSeedNode("dnsseed.biblepay-explorer.org");  // Alex
      if (!fProd) AddSeedNode("test.dnsseed.biblepay-explorer.org"); // Alex (TESTNET)


So thats great, that should give us start up stability for new users who open the wallet in fringe areas.  Or in AWS for example.

Yeah, dont worry about the elaborate requirement of bitcoin-seed nodes - that requires running another seed server.  These DNS seed nodes should cover us for the foreseeable (foreseedable LOL) future. 

I tested your node (telnet dnsseed.biblepay-explorer.org 40000) and its working.  Will be in the next release.

Thank you for your support :).

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 07:30:12 am
I received the Bible in the mail Tuesday morning and got it out today, Thank you Rob!

./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "FILLING ORDER",
    "Status3": "USPS XXXXX",
    "Details": ""
  }
}

Thats great buddy!  So do you guys think this will be a hit in prod?

I have not received any orders in the pool itself (IE BiblePay Storefront) for anything yet.

We can of course add more items to the list for Prod.... Of course it would be nice to have a popup with an actual picture in an HTML frame, but Id like to see how popular this feature is first.

It will definitely accomplish one thing if used:  market depth - as the sales would create volume on the exchange, and thats what we need for debit card integration.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 07:35:53 am
On a good note, both my dns seeds are now up and running!

On a bad one, it looks like my BX went on a fork (stuck on block 55990 now). I'm restarting it now.

Yeah, I see the same problem you and Klondike have- my main test nodes stayed on the right chain with the masternodes, my controller win wallet just went on a different chain.  Here is the chain I show the enabled masternodes running on:


getblockhash 56000
0f1f17e9bb4e0889b81794708f9bb16908ba2c2b0f5e34dc033d7d2e3d03bc95

Regarding the question about prod, it depends on why this is happening.  Ill look at my windows logs and see if it banned the rest of the network.

EDIT:

Lets try to get to the root of the problem with this one.
On my windows node, if you want to see if you have similar problem, go to peers and take a look at the banlist.  I banned every peer.

This time Im not reindexing the chain, Im going to unban peers and see if it catches up.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 02, 2017, 07:36:13 am
Hahah no worries. I'm actually running a fork of bitcoin-seeder (https://github.com/sipa/bitcoin-seeder) adapted for biblepay which crawls the network and returns a list of reliable nodes which should be plenty!

Example:

Quote
; <<>> DiG 9.9.7-P3 <<>> A dnsseed.biblepay-explorer.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44541
;; flags: qr rd ra; QUERY: 1, ANSWER: 22, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;dnsseed.biblepay-explorer.org.   IN   A

;; ANSWER SECTION:
dnsseed.biblepay-explorer.org. 3599 IN   A   193.70.86.212
dnsseed.biblepay-explorer.org. 3599 IN   A   51.15.196.233
dnsseed.biblepay-explorer.org. 3599 IN   A   54.37.136.161
dnsseed.biblepay-explorer.org. 3599 IN   A   94.177.170.16
dnsseed.biblepay-explorer.org. 3599 IN   A   195.181.247.200
dnsseed.biblepay-explorer.org. 3599 IN   A   208.113.167.108
dnsseed.biblepay-explorer.org. 3599 IN   A   45.77.98.203
dnsseed.biblepay-explorer.org. 3599 IN   A   94.177.233.28
dnsseed.biblepay-explorer.org. 3599 IN   A   54.37.69.161
dnsseed.biblepay-explorer.org. 3599 IN   A   104.196.167.205
dnsseed.biblepay-explorer.org. 3599 IN   A   139.99.101.201
dnsseed.biblepay-explorer.org. 3599 IN   A   85.255.15.55
dnsseed.biblepay-explorer.org. 3599 IN   A   185.13.148.42
dnsseed.biblepay-explorer.org. 3599 IN   A   45.199.176.10
dnsseed.biblepay-explorer.org. 3599 IN   A   217.182.77.165
dnsseed.biblepay-explorer.org. 3599 IN   A   54.37.136.162
dnsseed.biblepay-explorer.org. 3599 IN   A   208.97.140.76
dnsseed.biblepay-explorer.org. 3599 IN   A   85.255.10.54
dnsseed.biblepay-explorer.org. 3599 IN   A   35.199.150.168
dnsseed.biblepay-explorer.org. 3599 IN   A   89.36.219.116
dnsseed.biblepay-explorer.org. 3599 IN   A   192.99.68.192
dnsseed.biblepay-explorer.org. 3599 IN   A   80.211.208.230


On another note, I managed to come back on the main chain but it took me two tries. I'm reindexing the db on the BX now.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 02, 2017, 07:38:14 am
Oh also, that crawler allowed me to see that we have 70709 running on mainnet, is that normal?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 07:53:05 am
Oh also, that crawler allowed me to see that we have 70709 running on mainnet, is that normal?
Wow thats great on the crawler, yeah, on 70709, yes, because the wallet supports some advanced rules.  I copied the prod rules to testnet first before doing this:

On testnet, the minimum required version is 70709, that ultimately forced the upgrade and instructs peers to hang up on peers with a lower protocol version.

On mainnet, the minimum version required is 70708, but it is OK to run a higher version.  After Christmas though, the mandatory would have something like "required minimum version 70709" in it (otherwise peers disconnect).

So thats OK for now.

Im working on the out-of sync condition, we need to get to the bottom of this thing.

I see that it occurred on block 54360 on my win node:

2017-12-02 00:10:19 IsBlockPayeeValid -- ERROR: Invalid masternode payment detected at height 54360: CTransaction(hash=2bbbb94c92, ver=1, vin.size=1, vout.size=3, nLockTime=0)
 

So basically the group of masternodes themselves did not experience this issue, but my win node refused block 54360.  I see that it did not create 54360.  Weve got to think of why did its view of payees differ from the main group (as this happened before the banned nodes occurred).  It banned every other node After this.




Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 02, 2017, 08:17:01 am
Yup that biblepay-seeder is really useful. It's tracking about 800 nodes right now and returning the best ones (and I limited the version to something recent).

Oh ok, understood for 70709 on mainnet.

That actually made me think of checking my (enabled) masternode and it was stuck on a fork way behind (54347) with everyone banned!
I have unbanned everyone but by looking at the logs, it looks like I need to resync it from the start as it's starting to ban again. I will do that now.

For the ecommerce feature, I think it could be really nice!
The main caveat I can think of is that people may be worried about sharing their personal information (especially nowadays with all these leaks/hacks/etc) and so that would probably need to be addressed (how it stored, security measures, who can access it, etc).

I have to go now but I can help with testing if you need testers later. I'm afraid looking through the code to try to find the issue is beyond my capabilities unfortunately so all our hope is with you haha!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 02, 2017, 08:24:26 am
now what block is OK... im resync and my linux wallet sync with same block like controller wallet

(https://i.imgur.com/RyERfI1.png)

Rob,which IP is your? exists any correct chain?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 08:50:39 am
now what block is OK... im resync and my linux wallet sync with same block like controller wallet

(https://i.imgur.com/RyERfI1.png)

Rob,which IP is your? exists any correct chain?
im 97.99.69, and the two 45.x.x's.

We have one shorter chain (block 56061) that seems to be the one with all our masternodes on it.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 08:54:03 am
So, I have a small amount of info as to what is happening:


08:47:13

getchaintips


08:47:13

[
  {
    "height": 56794,
    "hash": "b6309b95902c56470ef27a4442df5db0860e1cc3854db230cb6ede10eef6d906",
    "difficulty": 0.01837265411190288,
    "chainwork": "00000000000000000000000000000000000000000000000000002f88fdc59002",
    "branchlen": 0,
    "status": "active"
  },
  {
    "height": 56057,
    "hash": "6988dfa709707d99ae448da5984be132fdb7f13e274c00be9fb605f32dabac1f",
    "difficulty": 0.007104095844318024,
    "chainwork": "00000000000000000000000000000000000000000000000000002f80151d1740",
    "branchlen": 1708,
    "status": "headers-only"
  }
]

We have two chains : 56061 and 56794.
Heres what is funny about it:  The shorter chain has the masternodes synced on it and in agreement, but less chain work.
The longer chain has more chain work (notice its diff is .01 while the masternode chain is .007).  So the controller wallets pick the chain with more work, because thats part of the active-chain setbestchain rule, however the masternodes have banned those nodes already and prefer their own chain (primarily because of our rule to enforce sanctuary payees in a ranked list, which is part of Dash).

So its kind of interesting that the only way out is for me to blow the chain away and resync.

My question is, if we had the prod chain where obviously all the miners would be mining, and diff would be 10,000 instead of .01 will we stay synced on the chain with the most work in prod?  It SOUNDS like we would, but ..... lets keep thinking about this.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 08:55:39 am
Ive got an idea to test fixing this.  Lets all turn mining ON on our masternodes.
Lets get the diff up above 2.0 on our masternode chain... and then see if we stay in sync....

EDIT: I do see a possible reason that started this.  On TestNet its OK to mine on an out of sync chain with no peers.  On Prod you have to have a synced chain and peers with you.  So thats a huge difference.  Technically, the controller wallets are missing 3 things:  They are synced to best height, but mnode data is NOT synced (that requires masternodes, and mnsync status 999), and they banned every masternode peer.... 

So this does sound like an important exercise for us.  Lets try to fix the sync manually on the non-conforming peers, reindex those, and drive the diff up on the masternodes.


Then regroup for 10 more days and see if we can break the stay-in-sync record (I think thats only 3 days long LOL).



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 02, 2017, 09:00:56 am
then all is gone with my masernode+controller wallet?  :-[ im on 56799 bigger chain ...
and yes... my VPSlinux was on low chain and my controller is on bigger chain ... very interesting ...

how can i fix it now?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 09:07:57 am
then all is gone with my masernode+controller wallet?  :-[ im on 56799 bigger chain ...
and yes... my VPSlinux was on low chain and my controller is on bigger chain ... very interesting ...

how can i fix it now? ill try to ban all bigger nodes and allow all your MN nodes
Try starting with -reindex, and while reindexing ban any peer with a block height higher than the small chain.

Im mining on my 3 masternodes now - diff > .10 so far...

Once masternodes advance 700 more blocks it will be a moot point, but lets hope we stay in sync after we get this back.

Alternatively you can just shut off the nodes on the long chain and wait a day and turn on tomorrow with an empty chain.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 02, 2017, 09:27:53 am
yes,.super..... on VPS and WIN i added bad IPs to banlist and resynced: working!!!

now my masternode immediately ENABLED  :-*
xx.xx.xx.106   vps
xx.xx.xx.58     home controller
now starting testing

now try running 2nd masternode to 1 controllerwallet

Robinho: can i ask,dont know this thing=  when i will be have in controller-wallet (1,550,001 BBP) and rewards ill be receiving: can i to withdraw any BBP from this controller wallet? the balance can not fall under 1,550,001 BBP?

thanks for this question...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 09:50:37 am
yes,.super..... on VPS and WIN i added bad IPs to banlist and resynced: working!!!

now my masternode immediately ENABLED  :-*
xx.xx.xx.106   vps
xx.xx.xx.58     home controller
now starting testing

Robinho: can i ask,dont know this thing=  when i will be have in controller-wallet (1,550,001 BBP) and rewards ill be receiving: can i withdraw any BBP from this controller wallet? the balance can not fall under 1,550,001 BBP?

thanks for this anwer...

Yeah on a side note, I see my controller wallet synced as soon as it saw the masternode chain was .11.  Interesting.  Im hoping that was the problem, knock on wood.  The wallets are designed to sync to the chain with the highest diff (IE the most work).

Anyway lets talk about the escrow now.

During the third week of December I plan on poring through the code and updating any code required for the mandatory for Us and for c-cex.  Obviously one thing is the higher sanctuary escrow requirement.

Lets say you have one controller with 4 million BBP in it, and you decide to start two masternodes.  That means you will dedicate 3100002 BBP over two transactions for the investment of two masternodes leaving 899.9K spendable.

The wallet has code in it that will lock the 3.1MM escrow so that it wont be spent by you under normal circumstances.  For example if you attempt to  spend it, it will balk at you and never select those coins , therefore you cannot spend more than 899.9K.

IF you want out, and you want to relinquish your rights to one of your masternodes, you have to do this to spend it:
You have to enable coin control, and deliberately unlock the escrow (by selecting it) and then deliberately spending the selected escrow.  Once even 1 BBP of it is spent, that particular masternode will never work again until new escrow is set up for it.  Once the escrow is disturbed to no longer be "1,550,001" the rewards stop....



Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 02, 2017, 11:51:53 am
otherwise:

i have in my masternode 2M BBP and when i will be want send 500k controller wallet disable my request?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 12:36:04 pm
otherwise:

i have in my masternode 2M BBP and when i will be want send 500k controller wallet disable my request?
Just re-read what I wrote and then try it in testnet.

And then practice withdrawing as a masternode.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 02, 2017, 12:37:07 pm
I can only see one chain on both the sanctuary and controller-wallet:

Code: [Select]
19:31:52

getchaintips


19:31:52

[
  {
    "height": 56217,
    "hash": "5262f5c3a5f4dd6b233d4882aa84ab17a02cc9aced5cee1be6ad8aeccc5bc84b",
    "difficulty": 0.410893199744191,
    "chainwork": "00000000000000000000000000000000000000000000000000002f916df1cc2f",
    "branchlen": 0,
    "status": "active"
  }
]

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 02, 2017, 01:40:55 pm
built 2 MN in 1 controller wallet: and working stable  ;)

where is tutorial for this?on wiki i see nothing http://wiki.biblepay.org/Create_Masternode

You have to enable coin control, and deliberately unlock the escrow


very important question which doesnt exists on wiki tutorial:
you sending 500k bbp from 1 win wallet to 2nd wallet and this transaction is TX:1 ... cos before i sent alwayss 500k to linux VPS and didnt work....

thanks

need fix this
1.controller shows totally bad info about ENABLED MN... in VPS when i masternode listing,shows different things
2. my 2 vps shows diff things about maternode-list and status about others masternodes

(https://i.imgur.com/FP7ALP2.png)

uff,where is bug?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 02, 2017, 03:52:35 pm
built 2 MN in 1 controller wallet: and working stable  ;)

where is tutorial for this?on wiki i see nothing http://wiki.biblepay.org/Create_Masternode

You have to enable coin control, and deliberately unlock the escrow


very important question which doesnt exists on wiki tutorial:
you sending 500k bbp from 1 win wallet to 2nd wallet and this transaction is TX:1 ... cos before i sent alwayss 500k to linux VPS and didnt work....

thanks

need fix this
1.controller shows totally bad info about ENABLED MN... in VPS when i masternode listing,shows different things
2. my 2 vps shows diff things about maternode-list and status about others masternodes

(https://i.imgur.com/FP7ALP2.png)

uff,where is bug?

See if both VMs have the same best block hash.... First....

See if both vms say mnsync status 999 first...


Regarding relinquising a masternode, I dont understand the problem... Weve talked about it here a few times.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 02, 2017, 03:56:06 pm
same block
ID:999

:-[

and after few hours when i checked in /src getinfo my my masternode on testnet actually crashed biblepayd stopped running= same case like few days ago Alex,jaapkg,me

this things must be fix when you want to run MN

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 03, 2017, 07:57:27 am
next bug: im set sending 500k via DASH tutorial:did REQ 500k and tried send 500k and get this meesage


Thats not a bug; dont make the assumption user errors are bugs.
I see you selected too many inputs.  If you want to spend your masternode escrow, thats One VIN, not a megabyte of inputs.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 03, 2017, 08:01:54 am
same block
ID:999

:-[

and after few hours when i checked in /src getinfo my my masternode on testnet actually crashed biblepayd stopped running= same case like few days ago Alex,jaapkg,me

this things must be fix when you want to run MN

"and after few hours when i checked in /src getinfo my my masternode on testnet actually crashed biblepayd stopped running=

"same case like few days ago Alex,jaapkg,me"


First let me address the statement above - if you want to be a testnet tester then I need higher quality info from you.  Info like what Alex is sending me.
You say above the phrase "same case like a few days ago".

First of all, I dont know if you are referring to the One crash Alex received which he has not gotten back again on and he has valgrind, or being out of sync.  So I cant really even reply properly.  But I do want to say just because your two nodes with mnsync status shows 999, you cant make the assumption the node list is synced yet.  The local watchman database has to populate also.  Id wait 24 hours after mnsync shows 999 then look at the list.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 03, 2017, 12:33:23 pm
Rob: thanks........ important: that its need to wait for ID:999 and 1-6 hours for starting MN:
now working 3 MN in my group o/
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 03, 2017, 05:16:53 pm
Code: [Select]
}
[email protected]:~/biblepay/src$ ./biblepay-cli -testnet getchaintips
[
  {
    "height": 57431,
    "hash": "cfdc45c108c5006a57034f9182920596ef3cd6d0fbc01b7f4acb6951538b3d74",
    "difficulty": 0.1574826801492763,
    "chainwork": "00000000000000000000000000000000000000000000000000003028c49e09e4",
    "branchlen": 0,
    "status": "active"
  },
  {
    "height": 57289,
    "hash": "c82f28914267566b0a2fe54706b3b8b2a846033082f3b3728685432b0ef99447",
    "difficulty": 0.07889528542432625,
    "chainwork": "000000000000000000000000000000000000000000000000000030179bedc3bf",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 57137,
    "hash": "ecd50cf24d0d8ab73f381eea0695858b514331bd2b275844e11787d7f51dbb24",
    "difficulty": 0.1258454022789856,
    "chainwork": "000000000000000000000000000000000000000000000000000030054a5bb364",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 57110,
    "hash": "1f9732a9859de0c92fcc372a90f7be8c69bed22d80a642fe5443d0a9d9a7d47e",
    "difficulty": 0.1457924090507643,
    "chainwork": "00000000000000000000000000000000000000000000000000003002c1a2e5e8",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 57092,
    "hash": "0c772bf579ea0d087c6f48b81bf57bb0e3677121393e4d4c3896a217df6f4e60",
    "difficulty": 0.06886597851478146,
    "chainwork": "000000000000000000000000000000000000000000000000000030007094c533",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 57070,
    "hash": "1dedb07c4e688a5b10e008a7a7bf0317ece35724d0c76ccf0ae734e43732c215",
    "difficulty": 0.05883868673954577,
    "chainwork": "00000000000000000000000000000000000000000000000000002ffdc08fea48",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 57063,
    "hash": "749d3843f6d7439d82a3c83da28fade4e29d01401ef0e2e4a5d76b7b2e9eb830",
    "difficulty": 0.1142015216413931,
    "chainwork": "00000000000000000000000000000000000000000000000000002ffd2201db6e",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 57052,
    "hash": "54fa745231f9545fe0241ac562b4a1d8e40b1d249f40ba34665945cb9ff21935",
    "difficulty": 0.1592460385922879,
    "chainwork": "00000000000000000000000000000000000000000000000000002ffc4a48c732",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 57045,
    "hash": "906f272263e04c6d40d69f614d201ff10a09f86982206ca95a80e88842af83b7",
    "difficulty": 0.1630921687886359,
    "chainwork": "00000000000000000000000000000000000000000000000000002ffb779247b3",
    "branchlen": 2,
    "status": "valid-fork"
  },
  {
    "height": 57026,
    "hash": "17bf49d7296c16cd0ac7a28daca3df67f0faaebea94c18898e713a4f14e0f97d",
    "difficulty": 0.02533936616592403,
    "chainwork": "00000000000000000000000000000000000000000000000000002fe8a04cc7c1",
    "branchlen": 135,
    "status": "valid-fork"
  },
  {
    "height": 57012,
    "hash": "bf0c047b6e0f58b6ab86eee9b5d01dedc028aa92c9a5dce36429c18da763308f",
    "difficulty": 0.03192661676757559,
    "chainwork": "00000000000000000000000000000000000000000000000000002fe86b05d2ef",
    "branchlen": 121,
    "status": "valid-fork"
  },
  {
    "height": 56939,
    "hash": "8b2fb4e08f394139c3cc9b6aee9a79dd32bb07146c059b016b8742334a5d1b2e",
    "difficulty": 0.009930026910395656,
    "chainwork": "00000000000000000000000000000000000000000000000000002fe747a695d6",
    "branchlen": 48,
    "status": "valid-fork"
  },
  {
    "height": 56930,
    "hash": "fe307618a54c4b655ec9eb5e6ec83c322c32d4612165c0cc174f9f798892aec1",
    "difficulty": 0.00925301804970354,
    "chainwork": "00000000000000000000000000000000000000000000000000002fe732b6647a",
    "branchlen": 39,
    "status": "valid-fork"
  },
  {
    "height": 56917,
    "hash": "324698262f73373932f6964632cc1d03cefd308806636eca9ed4f302fee3ed2f",
    "difficulty": 0.009528593778170672,
    "chainwork": "00000000000000000000000000000000000000000000000000002fe703743c5c",
    "branchlen": 26,
    "status": "valid-headers"
  },
  {
    "height": 56875,
    "hash": "c813700ea1ffb368588ebe8e6ea03e71cc8f4659dea5abe5abeafb55e5ddd4a8",
    "difficulty": 0.03615676261390194,
    "chainwork": "00000000000000000000000000000000000000000000000000002fe472c396e2",
    "branchlen": 4,
    "status": "valid-fork"
  },
  {
    "height": 56861,
    "hash": "723ad3981d199d607ef161d821da4226f5b98ed2829a2dbe7fb73237a5110b3a",
    "difficulty": 0.02202176133767037,
    "chainwork": "00000000000000000000000000000000000000000000000000002fdd1a773258",
    "branchlen": 63,
    "status": "valid-fork"
  },
  {
    "height": 56812,
    "hash": "d3c6dc33b89179e383b82108ec720608f109ecb0c8349afbc12244cfe4301d64",
    "difficulty": 0.007849965813988811,
    "chainwork": "00000000000000000000000000000000000000000000000000002f893cc3e551",
    "branchlen": 2463,
    "status": "headers-only"
  },
  {
    "height": 56797,
    "hash": "ca21a8242a6fa9c44a6cf3fc44fc4800bed3c339699c98ead2ca8036a11c9b0c",
    "difficulty": 0.06112569778992384,
    "chainwork": "00000000000000000000000000000000000000000000000000002fdb90409646",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56789,
    "hash": "3793b60805708e3e215e91a35869ec42b1ffbf80f37d49f04d208ad6724389f9",
    "difficulty": 0.1887208106917315,
    "chainwork": "00000000000000000000000000000000000000000000000000002fda6ec143a5",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56773,
    "hash": "e5da1082b224df3c1a386ba6cd84c2610b4f6e40119fac71c3be42e3031c6a64",
    "difficulty": 0.0243726193601941,
    "chainwork": "00000000000000000000000000000000000000000000000000002fd87c3c4767",
    "branchlen": 3,
    "status": "valid-fork"
  },
  {
    "height": 56761,
    "hash": "dfa9ff863e1907168e8085a7ac42da45902e97d4071e21b5c6748387312551e9",
    "difficulty": 0.02080620843163382,
    "chainwork": "00000000000000000000000000000000000000000000000000002fd68aaed608",
    "branchlen": 12,
    "status": "valid-fork"
  },
  {
    "height": 56747,
    "hash": "02f7baa2adb2df859b62eb82aabb1b1ab4001749e9de6bdb6a7017fab68e05d1",
    "difficulty": 0.03541278167170377,
    "chainwork": "00000000000000000000000000000000000000000000000000002fd5fd80da22",
    "branchlen": 5,
    "status": "valid-fork"
  },
  {
    "height": 56736,
    "hash": "93eb50af7ffdf0547f581a397d52e53a87c000d86a74a8793770a4749a24e757",
    "difficulty": 0.02305400585997756,
    "chainwork": "00000000000000000000000000000000000000000000000000002fd4fbc525a1",
    "branchlen": 5,
    "status": "valid-fork"
  },
  {
    "height": 56689,
    "hash": "00973530323fb59b0ecd12ec245ddd397e0ba52d4e972e00be4683750bfd02c0",
    "difficulty": 0.01045604536042603,
    "chainwork": "00000000000000000000000000000000000000000000000000002fce0e939d33",
    "branchlen": 15,
    "status": "valid-fork"
  },
  {
    "height": 56670,
    "hash": "3b5ad6061f3c0943f19473caa942048611542056709e08b163c5a5d102bf0d16",
    "difficulty": 0.09171622062274942,
    "chainwork": "00000000000000000000000000000000000000000000000000002fcc56ad5127",
    "branchlen": 2,
    "status": "valid-fork"
  },
  {
    "height": 56663,
    "hash": "c1797498c8ebf7301051405c07a0b4bae8d62e2da94ba9bdadb09b3f9cd1d3cf",
    "difficulty": 0.04734934692798218,
    "chainwork": "00000000000000000000000000000000000000000000000000002fcb7afc4cc0",
    "branchlen": 4,
    "status": "valid-fork"
  },
  {
    "height": 56630,
    "hash": "a28e5a83860d261c5d0e9fccd4bc7b395aea94b2e8f61031dac74f4a0299ad54",
    "difficulty": 0.02735182497837021,
    "chainwork": "00000000000000000000000000000000000000000000000000002fc5b8142ac9",
    "branchlen": 12,
    "status": "valid-fork"
  },
  {
    "height": 56618,
    "hash": "1a713a5b5878a8dca723537c671f0ed8f834dcff7464bfaa294ae83e98e9a6dc",
    "difficulty": 0.08559561671031235,
    "chainwork": "00000000000000000000000000000000000000000000000000002fc5358d3ee9",
    "branchlen": 3,
    "status": "valid-fork"
  },
  {
    "height": 56608,
    "hash": "21c98aad6b5d6ee756252d6af1aacd2b3e993c6a739ddfbb3fc897f5ba198569",
    "difficulty": 0.03091398990713774,
    "chainwork": "00000000000000000000000000000000000000000000000000002fc3f3616ece",
    "branchlen": 9,
    "status": "valid-fork"
  },
  {
    "height": 56596,
    "hash": "08063cc06938cc6961aa13132a7674e0a1a7c29d9620d22e4614fd8eca5e997d",
    "difficulty": 0.1312871489443539,
    "chainwork": "00000000000000000000000000000000000000000000000000002fc35a669943",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56585,
    "hash": "560c28027148f3369c5a08af8255e6edb206bac8bb141e5a67dbeb0aa062a561",
    "difficulty": 0.01988742748000332,
    "chainwork": "00000000000000000000000000000000000000000000000000002fbd84e4d4fc",
    "branchlen": 46,
    "status": "valid-fork"
  },
  {
    "height": 56554,
    "hash": "5cba05af7a5aaf5b227c54b4f52426a0aa6351098fc43f6072534bb7c4157222",
    "difficulty": 0.01229137623089595,
    "chainwork": "00000000000000000000000000000000000000000000000000002fbcd894c457",
    "branchlen": 15,
    "status": "valid-fork"
  },
  {
    "height": 56534,
    "hash": "474c8ee1d8378a87110af38d92bc1ad8ff105ee808cae9e8f3f4f580867d21e8",
    "difficulty": 0.03573886497269482,
    "chainwork": "00000000000000000000000000000000000000000000000000002fbb2f6ddfd4",
    "branchlen": 5,
    "status": "valid-fork"
  },
  {
    "height": 56526,
    "hash": "911e60ead5ba4fd7794d2e3e53d0b20f0143eacbcfe015e3a8e28584113a8dc7",
    "difficulty": 0.1153208606964124,
    "chainwork": "00000000000000000000000000000000000000000000000000002fba47f0853d",
    "branchlen": 5,
    "status": "valid-fork"
  },
  {
    "height": 56516,
    "hash": "be73e72bb00c6a0917aab524bc3d8edd509479df0eabf1651ad908341c1195a0",
    "difficulty": 0.1426248988012849,
    "chainwork": "00000000000000000000000000000000000000000000000000002fb9281d9620",
    "branchlen": 3,
    "status": "valid-fork"
  },
  {
    "height": 56507,
    "hash": "fd036721815291713d61d01e8a2c070aee95dae464d3ee42b07d2eeb48241dc5",
    "difficulty": 0.1232289423953818,
    "chainwork": "00000000000000000000000000000000000000000000000000002fb809e0d6a1",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56505,
    "hash": "55155024d35b4a4fbf415b063f47dcf3820f653c63690144b3e182e4093431a3",
    "difficulty": 0.08422017146036891,
    "chainwork": "00000000000000000000000000000000000000000000000000002fb7de6faf88",
    "branchlen": 3,
    "status": "valid-fork"
  },
  {
    "height": 56495,
    "hash": "4f30daec41e7a85adf8adf2f3c1a40fa085e34be76d2fa45a58caec13f69f17f",
    "difficulty": 0.1554671487132772,
    "chainwork": "00000000000000000000000000000000000000000000000000002fb68b821696",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56469,
    "hash": "8269ed2917cd2781419282d3c36f0a9f09d4d811cbe8a4c982e20acd7f9e6ba8",
    "difficulty": 0.0853002657864389,
    "chainwork": "00000000000000000000000000000000000000000000000000002fb45678223c",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56447,
    "hash": "67d40858577d7770e2053a1a41b40dfa5ac923b50e3a75fb49a59513f842cbcb",
    "difficulty": 0.06342780157604078,
    "chainwork": "00000000000000000000000000000000000000000000000000002fb1c165e3f2",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56402,
    "hash": "963f35a9821224d72ee6199ff8107effd73712d76f3e3e78ef5a79a4de575b9e",
    "difficulty": 0.06798158942169746,
    "chainwork": "00000000000000000000000000000000000000000000000000002fabbf557b60",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 56402,
    "hash": "63e15ed20a36cd4fe1d434c284d949275dc4a600b8c192c3c661bcdc2004f4db",
    "difficulty": 0.06798158942169746,
    "chainwork": "00000000000000000000000000000000000000000000000000002fabbf557b60",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56314,
    "hash": "0d921d4b7a8adc2397c13f7bcebbb457903a97538c536156047c0d783e0f90f0",
    "difficulty": 0.144210774163309,
    "chainwork": "00000000000000000000000000000000000000000000000000002fa06e8647f7",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56311,
    "hash": "0631b062fc1ba2bd4b7ba4e77f9066e9c7a4d76d6f587c4223cd75bd814aa7f4",
    "difficulty": 0.05500186738620484,
    "chainwork": "00000000000000000000000000000000000000000000000000002fa018a7f8e7",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 56281,
    "hash": "56778e8ebeeeae7703d3ccb0a10610a14d27b6eb6c31054bfbc9ccc23f5149a3",
    "difficulty": 0.08208815943904232,
    "chainwork": "00000000000000000000000000000000000000000000000000002f9b74b3c491",
    "branchlen": 1,
    "status": "valid-fork"
  }
]

Does this mean there are a lot of forks?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 03, 2017, 06:45:48 pm
jaapgvk i can help you....it means that exists more ppls on bad diff chains, you need this bad machines BANs

in your VPS do this commands

./biblepay-cli -testnet getpeerinfo you will see all users on testnet  bad+good

all except this ban this command ./biblepay.cli -testnet setban IP add

this is corret masternodes,dont ban it
217.182.67.106 mine
80.211.200.169 mine
86.105.53.44 mine
97.99.69.33 Rob
45.76.239.64 Rob
207.244.148.187 dont know

then start again ./biblepay-cli -testnet -deamon -reindex

laterz ill show how working with tBBP: locking,unlocking+sending coins with lock masternodes:  ... DASH community is great and helpfully for this ..

DASH+VERTCOIN= MN+CPU=BBP great


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 03, 2017, 07:07:30 pm
Code: [Select]
}
[email protected]:~/biblepay/src$ ./biblepay-cli -testnet getchaintips
[
  {
    "status": "valid-fork"
  }
]

Does this mean there are a lot of forks?

There were a lot of forks before we made 2 changes:
- We realized the masternodes were not hashing, so there was a propensity to fall off the masternode chain, now they are hashing
- The version prior to 1060 had a bug that Alex found that we corrected that could have caused most of the forks

In your case please start with the -reindex flag and let it rebuild, then getchaintips should be clean.



After that, lets run for a few days and see if the masternode list stays ENABLED and getchaintips stays clean....


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 05, 2017, 07:14:13 am
I know it's not really about testing sanctuaries but I saw your post about the block explorer and thought I would share my progress with "revamping" our block explorer.

I just started so the design is still very basic but here are some ss:

http://prntscr.com/hjdime
http://prntscr.com/hjdiv8
https://prnt.sc/hjetp7
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 05, 2017, 09:34:28 am
jaapgvk i can help you....it means that exists more ppls on bad diff chains, you need this bad machines BANs

in your VPS do this commands

./biblepay-cli -testnet getpeerinfo you will see all users on testnet  bad+good

all except this ban this command ./biblepay.cli -testnet setban IP add

this is corret masternodes,dont ban it
217.182.67.106 mine
80.211.200.169 mine
86.105.53.44 mine
97.99.69.33 Rob
45.76.239.64 Rob
207.244.148.187 dont know

then start again ./biblepay-cli -testnet -deamon -reindex

laterz ill show how working with tBBP: locking,unlocking+sending coins with lock masternodes:  ... DASH community is great and helpfully for this ..

DASH+VERTCOIN= MN+CPU=BBP great

Thank you for your help! I've banned all except the ip's in your list.

@admin: Thank you for the clarification. But the strange thing is that I already updated to 1.0.6.3. and was also mining with my sanctuary, and that there was only one chaintip when my setup was like that (see my post from a page back).

But when I tried it again a day later I got the huge list of chaintips I posted. So one day everything is fine and the next there were a lot of chaintips.

I'm reindexing as I speak. But a lot of times then I try './biblepay-cli -testnet getchaintips' biblepay seems to exit and I have to start up again. Maybe I need to do a clean install in the next couple of days, because something doesn't feel quite right with my installation right now...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 06, 2017, 07:40:49 am
Thank you for your help! I've banned all except the ip's in your list.

@admin: Thank you for the clarification. But the strange thing is that I already updated to 1.0.6.3. and was also mining with my sanctuary, and that there was only one chaintip when my setup was like that (see my post from a page back).

But when I tried it again a day later I got the huge list of chaintips I posted. So one day everything is fine and the next there were a lot of chaintips.

I'm reindexing as I speak. But a lot of times then I try './biblepay-cli -testnet getchaintips' biblepay seems to exit and I have to start up again. Maybe I need to do a clean install in the next couple of days, because something doesn't feel quite right with my installation right now...

I dont think its your machine; I see that getchaintips does silently exit on my windows box.  My linux box has less chaintips and finishes the command.

(Although on a side note, I remember seeing a bitcoin getchaintips, and it had a huge amount of tips, so now, I do  not actually think the tips are a problem, as long as we stay on the main chain, but I have to confirm that.  If thats the case, I can modify the command to clean the blockindex while it runs and discard chaintips older than a few hours).

However I would like to fix the code, Alex can you help with valgrind?    Can you see if your getchaintips exits on any of your boxes and if so run it while valgrind is running?  I need to get around to installing valgrind on my gitian machine.

I see one other issue.  Although it looks like we are staying in sync now that we have the diff > .10 in testnet, I see something that I believe Slovakia was mentioning: the windows controller does not have the same masternode list, but its in sync.  I cant fathom how that can be, as Sentinel on the dash side only runs on Linux.  meaning that we are not doing anything special by having windows controller wallets and Nix Watchman.  Ill check into that.  Although it appears to not be hurting anything at the moment, its definitely a nuisance.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 06, 2017, 07:55:26 am
Running valgrind now. I will send you the logs if I see anything!

Edit: Also concerning the masternode list, I had this same issue with other altcoins where it was taking some time for the masternode lists to propagate and be refreshed/in synced. Assumed that there was a reason for that but never looked into it and just accepted it haha.

That is mainly why I'm displaying the masternode list on the BX for people to compare with what they have. I'm going well with the revamp of the BX and improving that page is def on my list.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 06, 2017, 08:29:12 am
Running valgrind now. I will send you the logs if I see anything!

Edit: Also concerning the masternode list, I had this same issue with other altcoins where it was taking some time for the masternode lists to propagate and be refreshed/in synced. Assumed that there was a reason for that but never looked into it and just accepted it haha.

That is mainly why I'm displaying the masternode list on the BX for people to compare with what they have. I'm going well with the revamp of the BX and improving that page is def on my list.

Thanks a lot dude.
I have some further info regarding the masternodelist.
My windows box is the one that is not agreeing, so I deleted all the .dat files related to masternodes (mncache.dat, payment.dat, gov*.dat) and then restarted (note, you do not want to kill your chainstate or blocks in this case).  Then I waited about 20 minutes, and it synced to the same state the nix box was in (Note it was a 2 step sync: step 1 just populated the mnlist, with NEWSTARTREQ for everyone then it took 15 more minutes to pull the states of each node).  So apparently there is an issue where your local mncache view of the masternodes can get out of sync and the wallet is not smart enough to ask to kill and refresh that. 

Thats all I know so far guys :), anyway, I have an IT issue that is on fire so I will be back asap as soon as I can, have a good one.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 06, 2017, 08:30:28 am
thanks guys for fix that controller wallet status of masternodes  ;)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 06, 2017, 08:23:00 pm
Alex your work on the Explorer has been AWESOME! Love what youre doing, puts my explorer to shame :P

I did notice your BTC C-CEX price got stuck
I could never get the Markets tab to work consistently, mine only works like 1/10th the time (whats your secret?)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 06, 2017, 08:38:25 pm
Oh c-cex modified something so I had to rewrite that part a little bit to not throw an error if it wasn't getting the data.

I actually just noticed they modified something else that's what it wasn't updating . I *hopefully* fixed it but I need the rest of the api calls to get out of the maintenance to see if it worked.

I won't maintain that function in the new BX and just get the price from coinmarketcap if I need it.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 07, 2017, 10:19:14 am
Just checking in - looks like everything is looking pretty good for the go live.
We beat our record, weve been in sync and masternode list up for 4+ days now.
The windows node has stayed in sync and MN list agreed with Nix node ever since I deleted those old .dat files!

I added a fake proposal yesterday and it looks like pool paid the necessary 5BBP to make it Live although noone voted on it yet, but I anticipate that to work for us.

Has anyone any consternations or last minute concerns?  Im actually going to have to notify CCEX soon to give them a 2 week notice to upgrade, start finalizing changes and things for our mandatory.

I believe the Amazon in-wallet product feature is going to go live also (for the US only) at Christmas.  That should be interesting.

On a side note, Im going to downplay the retirement accounts.  They will emit coins, but Im not sure how well we can support that feature.  Im a little nervous to go down the path of creating a trading infrastructure for them.  I might make a feature that allows you to trade your rBBP back into BBP (at the internal satoshi exercise rate) in the wallet.  Im thinking my efforts on Stratis may be more beneficial for us right now than to monkey with supporting a new in-wallet exchange.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 08, 2017, 03:27:05 am
thanks for your time Rob ...

is any solution why masternode crashed to NEW START REQUIRED? im wrote more topics about it on DASH and ppl got still this problems,every day checking their masternodes....it can be nervous still checking if something is running ....
1MN working stable 4+days and 1 go to that start req: so i start MN from controller and run watchman ...


andy idea? thanks
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 08, 2017, 08:39:00 am
Hi Alex,
Not sure if you saw this post from Slovakia on the main thread, something to the extent of he believes the pool is stealing peoples blocks by hiding the blocks found, but it made me think of a potential enhancement to your BX.

If you label the MinersOfMen address and the Pool with pool.biblepay.org, then could you potentially make a "Coins Mined in Last 24 hours" metric and put it somewhere? Somewhere that is not hit every time, or, maybe you could cache it and put it right under the address in the richlist?  Another words whatever is convenient for you. (You can do exec getsubsidy height for nTip to nTip-202 when you call it then sum it and cache it for an hour).

Then we could have whoever reads it compare it to pool.biblepay.org coins mined on about page, and know they agree.

Then after that, all we have to worry about is why do we have 65% of the blocks solo mined?  Thats another important project.  Is there any way to see if the non pool blocks are going to random addresses? 

I have an idea that could thwart a botnet, but it needs to be tested in testnet.  I was thinking, if we took an element of proof-of-stake, Spending money to stake, and added it into POW, and required each miner to stake 1BBP while mining, it would make it almost impossible to not CPU mine (as the 1 bbp at stake would need to be added to the block).  Then we would need to require the 1BBP tx to never be older than say 60 seconds, so as to thwart any GPU or asic.  The problem is getadjustedtime() can be skewed up to 15 mins.  This is still a tough issue to solve.

 

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 08, 2017, 08:42:10 am
thanks for your time Rob ...

is any solution why masternode crashed to NEW START REQUIRED? im wrote more topics about it on DASH and ppl got still this problems,every day checking their masternodes....it can be nervous still checking if something is running ....
1MN working stable 4+days and 1 go to that start req: so i start MN from controller and run watchman ...
andy idea? thanks
It looks like NEW_START_REQUIRED is triggered if your node fails the POSE test.  That means it either fails to vote within 24 hours for itself, gets ddossed, loses its static IP or crashes.  Then the other nodes vote to boot your node from the team and requires a restart by the owner of the sanctuary to get back "in" the payment queue.  You lose payments until you restart the node - from the controller - not from the node.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 08, 2017, 09:04:41 am
Hi Alex,
Not sure if you saw this post from Slovakia on the main thread, something to the extent of he believes the pool is stealing peoples blocks by hiding the blocks found, but it made me think of a potential enhancement to your BX.

If you label the MinersOfMen address and the Pool with pool.biblepay.org, then could you potentially make a "Coins Mined in Last 24 hours" metric and put it somewhere? Somewhere that is not hit every time, or, maybe you could cache it and put it right under the address in the richlist?  Another words whatever is convenient for you. (You can do exec getsubsidy height for nTip to nTip-202 when you call it then sum it and cache it for an hour).

Then we could have whoever reads it compare it to pool.biblepay.org coins mined on about page, and know they agree.

Then after that, all we have to worry about is why do we have 65% of the blocks solo mined?  Thats another important project.  Is there any way to see if the non pool blocks are going to random addresses? 

I have an idea that could thwart a botnet, but it needs to be tested in testnet.  I was thinking, if we took an element of proof-of-stake, Spending money to stake, and added it into POW, and required each miner to stake 1BBP while mining, it would make it almost impossible to not CPU mine (as the 1 bbp at stake would need to be added to the block).  Then we would need to require the 1BBP tx to never be older than say 60 seconds, so as to thwart any GPU or asic.  The problem is getadjustedtime() can be skewed up to 15 mins.  This is still a tough issue to solve.

I will add something like that to my list.

I think the block solo mined are probably mined by big miners that:
1) create an account and configure all their miners to point to the pool
2) maybe have a loss of hash power because of the connection between the pool and their miners (I'm guessing it could make a difference at large scale)
3) pay the pool fees
4) have a botnet and don't want to mine on the pool for the reasons above!

I also updated the testing BX with a "preview" of what I'm doing. It's all still very early.

Edit: Reimage is taking longer than expected but should be available soon.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 08, 2017, 09:07:33 am
hm----- im using weak VPS for testing,may be because of ... on VULTR will be stable i hope
explorer changed GH to MH?
hm..... so its HPS2 or HPS1?

now is 72 000 000 HPS2? 1core gives .ca 5000 hps2= 72M/5khs=14400 1cores is 100% of site? or

and im talked with Slovakia and he got true....now is network all day around 72MH/s  Diff=10 000  and rewards is very bad..... we had double rewards on this Diff .. what is bad?

if will be exists botnet on solo mining, all is gone,nobody after new year will be mining bbp=not rentabile, pool died with this botnet=china guys
main idea for all is SUPPORT CHILDREN it will be sad if miners leave and botnet/china will be flourish to the detriment BIBLEPOOL


amen
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 08, 2017, 09:11:22 am
I will add something like that to my list.

I think the block solo mined are probably mined by big miners that:
1) create an account and configure all their miners to point to the pool
2) maybe have a loss of hash power because of the connection between the pool and their miners (I'm guessing it could make a difference at large scale)
3) pay the pool fees
4) have a botnet and don't want to mine on the pool for the reasons above!

I also updated the testing BX with a "preview" of what I'm doing. It's all still very early.

Edit: Reimage is taking longer than expected but should be available soon.

Right, Im with you, I can imagine someone who has 50 servers, who pointed to the pool and then dont maintain those boxes and they all keep solo mining.

Note : I do want to say, the pool scans back 11 blocks after every block just to make sure someone didnt solve a back block.  So the pool goes back and backpays for every block paid to it.

If you have a botnet, and you fall out of the pool those actually start getting signed by You.  So pool never keeps a block not its own.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 08, 2017, 09:12:16 am
The explorer network hash rate is not reliable. It's something that is on the list. I removed it the meantime.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 08, 2017, 09:13:37 am
hm----- im using weak VPS for testing,may be because of ... on VULTR will be stable i hope
explorer changed GH to MH?
hm..... so its HPS2 or HPS1?

now is 72 000 000 HPS2? 1core gives .ca 5000 hps2= 72M/5khs=14400 1cores is 100% of site? or

and im talked with Slovakia and he got true....now is network all day around 72MH/s  Diff=10 000  and rewards is very bad..... we had double rewards on this Diff .. what is bad?

if will be exists botnet on solo mining, all is gone,nobody after new year will be mining bbp=not rentabile, pool died with this botnet=china guys

Dont refer to the total HPS in testnet, its just a sum of how much Chain Diff went into the last 100 blocks.
Pay more attention to the comparable getmininginfo HPS achieved by each processor on testnet.
This f8000 algo is slower and harder to solve than f7000, but not subject to the node mutex.

If you guys like the HPS per processor and OS flavor in testnet, it will succeed very strongly in Prod.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 08, 2017, 10:43:14 am
I guess better late than never. The "preview" is now live on https://testnet.biblepay-explorer.org
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 08, 2017, 10:54:49 am
I guess better late than never. The "preview" is now live on https://testnet.biblepay-explorer.org

Wow man, I love the idea of linking new proposals in there.  That will be awesome for sanctuaries!  Between the pool and BX, we almost have what Dash Central has.  I guess if we force new proposals into a certain thread, you can always pick them up.

I noticed the popup reftagger no longer works, did u remove that?

Its nice.  I think 1 px font size increase might be nice for the main page.  Any chance of our new logo going in?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 08, 2017, 11:13:55 am
Yup I removed it for now. I will just directly provide a link to the scripture if you click on a verse.

The css is def temporary and unfinished. I just needed something to test things. I increased the font size of the verses on the main page though! (prob need to clear your cache to see the difference)

As long as it has an API to let me grab the proposals I'm fine with anything (this forum or another website)

I was actually on my way to maybe totally rewrite it using socket.io but I guess ajax is good enough for now!

I still have a few more functions to add before eventually focusing on the appearance on the website.

Edit: Oh for what it's worth, I also added some cool api calls such as:
https://testnet.biblepay-explorer.org/ext/getverses/54798c78811d466a6dd29144f6bc82838068049fcf4680e05e06709287f1649e

Edit2: reindexing the db so the link above may not work until the block is back in the db.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 08, 2017, 01:13:22 pm
Alex your testnet is on bad chain  ;)

and when i click on my 2 MN wallets i see error

yW3UTp2qhNLoHJfnTP57jkgJ7RHzQYtBTH
yfyTLmXcnn1hXvWBGbKCz4QkRobJiUDeAt
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 08, 2017, 08:26:45 pm
Alex your testnet is on bad chain  ;)

and when i click on my 2 MN wallets i see error

yW3UTp2qhNLoHJfnTP57jkgJ7RHzQYtBTH
yfyTLmXcnn1hXvWBGbKCz4QkRobJiUDeAt

It's not on "bad chain". It just didn't finish indexing everything when you tried and I'm guess your addresses are in the higher blocks so that's why it didn't find any transaction. It should be fine now.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 09, 2017, 08:45:57 am
Yup I removed it for now. I will just directly provide a link to the scripture if you click on a verse.

The css is def temporary and unfinished. I just needed something to test things. I increased the font size of the verses on the main page though! (prob need to clear your cache to see the difference)

As long as it has an API to let me grab the proposals I'm fine with anything (this forum or another website)

I was actually on my way to maybe totally rewrite it using socket.io but I guess ajax is good enough for now!

I still have a few more functions to add before eventually focusing on the appearance on the website.

Edit: Oh for what it's worth, I also added some cool api calls such as:
https://testnet.biblepay-explorer.org/ext/getverses/54798c78811d466a6dd29144f6bc82838068049fcf4680e05e06709287f1649e

Edit2: reindexing the db so the link above may not work until the block is back in the db.

The one in prod is really clean looking though (sorry for constructive criticism) I know you have been pouring time into this:

https://biblepay-explorer.org/block/6fcaabd2b7df5c5e530e32e02ce3ddea56944fbbaf804b0af73dd4f4e6dc544d
and the reftagger popups are cool...

So, couldnt you add your two new widget sections (proposals and threads) to the existing style one in prod?
Or are you recreating an entirely new BX so its going to be the "Alex" branch?




Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 09, 2017, 09:30:14 am
Constructive criticism is always welcome!

There's a lot of new stuff, both in what you see and the backend. I actually added/rewrote a lot of things but I could add the proposals and recent post to the current iquidus explorer easily. The issue is I don't think it scales well and is one of the reasons I'm modifying it.
For example, the current iquidus explorer doesn't keep separate tracks of blocks and transactions so once you get some transactions in, it becomes quite impractical.
(the index page is actually getting data from api calls I created. For example for the proposals, it's something really simple that gets data from the xml feed of smf and get what I need out of it - https://testnet.biblepay-explorer.org/api/getproposals)

For the block page:
I think the current reftagger is a bit useless on the block page because all it does is display the scripture already displayed on that page unless you click on more - then it redirects you to their website where you can read the whole chapter. So, I was just going to have the verses of the block page link directly to that page instead of having that redundancy.

For the main page:
The main page only has the verses so it would make sense to have the reftagger there to get the scriptures so that will be there!

The BX is pretty much brand new in terms of "views". Only the "Wealth distribution page" still uses the old code -for now-, I think everything else has been rewritten. I'm also slowly touching the backend too and I'm now separating transactions and blocks for example . So I'm really moving away from the traditional iquidus explorer most altcoins are using!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 10, 2017, 09:49:51 pm
Hi Admin , 

what will be the procedure of promoting masternodes after or on Christmas ?

Will it be enough to start  a sanctuary and masternode on the main network as we did for testing  or there is anything else involved ?

thanks
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 12, 2017, 08:41:15 am
Hi Admin , 

what will be the procedure of promoting masternodes after or on Christmas ?

Will it be enough to start  a sanctuary and masternode on the main network as we did for testing  or there is anything else involved ?

thanks

Hi Tiras,

It should be very similar to testnet.  Once the mandatory is released we will have a certain block number announced where the Sanctuaries actually enable themselves.  You can still send the escrow to the address early, and get the VM ready.  But the masternodelist wont populate until after that block number kicks over.

Once that kicks over, the sanctuaries should start talking to each other and voting to pay each other.  We will also have a separate block number for the first superblock.  I think we will need to space that out to give time for the new nodes to acclimate themselves (maybe 15-25 days later).

We also need to remember to send instructions for people to switch their watchman-on-the-wall configs over to Prod.

Rob




Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 12, 2017, 10:57:13 pm
Hi Tiras,

It should be very similar to testnet.  Once the mandatory is released we will have a certain block number announced where the Sanctuaries actually enable themselves.  You can still send the escrow to the address early, and get the VM ready.  But the masternodelist wont populate until after that block number kicks over.

Once that kicks over, the sanctuaries should start talking to each other and voting to pay each other.  We will also have a separate block number for the first superblock.  I think we will need to space that out to give time for the new nodes to acclimate themselves (maybe 15-25 days later).

We also need to remember to send instructions for people to switch their watchman-on-the-wall configs over to Prod.

Rob

thanks Rob.

sounds good.  we can set it up before the holidays.

>>We also need to remember to send instructions for people to switch their watchman-on-the-wall configs over to Prod.

Can a test sanctuary be just reconfigured  to run on the main network then ?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 12, 2017, 11:10:24 pm
Ok, so Im stepping through sanctuary (masternode) creation process, this time with Vultr as host
(I was originally using AWS, but the Vultr pricing is a bit cheaper $5/mo vs $8.30/mo for 1CPU 1GB RAM)
[This is also my first time testing the swap file solution to extend the 1GB RAM]

===

Reference: http://wiki.biblepay.org/Create_Sanctuary
Note: 1,500,001 needs to be updated to 1,550,001

===

1. Create Account
https://www.vultr.com/register/

2. Add Payment Information

3. Download & Install PuTTY (SSH Client):
http://www.putty.org/

4. OPTIONAL: Generate SSH Public/Private Keys
https://www.vultr.com/docs/how-do-i-generate-ssh-keys/

5. Deploy Instance
https://my.vultr.com/deploy/

Instance Type:  VC2
  1. Server Location: Random
  2. Server Type: Ubuntu 16.04 x64
  3. Server Size: 1 CPU, 1024MB RAM, $5/mo (*Assuming using SWAP file later for more RAM)
  6. SSH Key: Add and Select Public Key you added in Step #4
  7. Serverhostname: Add unique name

6. Use Putty to Connect to Vultr Server
Enter IP Address, Port 22, Connection type SSH
You can add your private key file: Connection >> SSH >> Auth >> Browse
You can name and save your connection info:
Session >> Saved Sessions >> Enter a Unique Name >> Save

7. Install BiblePay
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

7a. Swap File
Before running last command "sudo make", set up the swap file:
https://digitizor.com/create-swap-file-ubuntu-linux/
http://forum.biblepay.org/index.php?topic=16.msg151#msg151

Code: [Select]
free #check if swap is 0
dd if=/dev/zero of=/var/swap.img bs=1024k count=1000
mkswap /var/swap.img
swapon /var/swap.img
free #check if swap is 1024

===

Comments:
- I failed to do the public/private key correctly I'm not sure what I did wrong, weird
- the swap file thing is interesting I've never done that before

===

8. Continue on with Create Sanctuary Wiki: http://wiki.biblepay.org/Create_Sanctuary
My previous masternode notes: http://forum.biblepay.org/index.php?topic=16.msg151#msg151
(waiting for BiblePay to compile so will continue tomorrow and report back any issues I run into)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 13, 2017, 08:42:27 am
thanks Rob.

sounds good.  we can set it up before the holidays.

>>We also need to remember to send instructions for people to switch their watchman-on-the-wall configs over to Prod.

Can a test sanctuary be just reconfigured  to run on the main network then ?

Yes - the testnet sanctuary can be switched to prod mode, but requires a few adjustments. 

The watchman config should be OK after just changing to point to prod (by uncommenting and recommenting the two lines in the watchman.conf file).    (IE its database should adjust to prod without a problem).

The masternode keypair however Is different in prod than testnet.  So I recommend commenting out the masternodeprivkey in the config file, and then you will need to generate a new keypair and of course send escrow to the correct address and that will yield a new vout txid string.

Once these things are set, booting into prod mode should work.  We should be able to test this tomorrow as soon as c-cex puts us in maintenance.

The mandatory upgrade is almost ready, so, if all goes well I will release it tonight and we can do our "prod" testing with the new version.



Togo, thanks, I noticed that also this morning and updated it.


Yeah, let me know if you have any issues with that $5 vultr node and the instructions, and if I should merge your instructions in, or do you want to clone the Create_Sanctuary wiki and merge yours into a new one to make a more detailed version?  Maybe that would be better then the gurus can use the generic one and move to your detailed one if they fail?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 13, 2017, 09:53:17 am
Yeah, let me know if you have any issues with that $5 vultr node and the instructions, and if I should merge your instructions in, or do you want to clone the Create_Sanctuary wiki and merge yours into a new one to make a more detailed version?  Maybe that would be better then the gurus can use the generic one and move to your detailed one if they fail?

Im open to either! I did originally plan to create a sanctuary guide but didnt move forward on it, I think this would be a good time to do it since Ill be stepping through the process again :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 13, 2017, 07:59:26 pm
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 .

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 13, 2017, 09:29:55 pm
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.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 14, 2017, 01:24:47 pm
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.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 14, 2017, 01:37:30 pm
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
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 15, 2017, 03:12:01 am
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]
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...

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 15, 2017, 03:16:48 am
Try to redownload the blockchain by deleting the "blocks" and "chainstate" folders.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 15, 2017, 03:17:18 am
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"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 15, 2017, 05:23:45 am
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!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 15, 2017, 09:42:56 am
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.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 16, 2017, 07:15:15 am
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 :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 16, 2017, 08:50:43 am
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
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 16, 2017, 09:45:50 am
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.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 16, 2017, 02:30:26 pm
i mean crashed mining, stop mininig,biblepayd stopped after few minutes = before f8000 all my machines was stable weeks
WHERE IS PROBLEM damn it

its VULTR 2 machines 1core and im using next 3 1core machine and same crashed after few minutes ....
same my ryzen1700 at home: i setuped cpulimit=12 and wallet crashed .... same problems got my all 12 friends ...


this update is a pain,with bugs

https://biblepay-explorer.org/  is stuck

I just fixed the explorer.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 16, 2017, 03:13:07 pm
thanks ALEX for your helping BBP ... excellent job with ROB!!!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 16, 2017, 06:04:58 pm
I just updated my masternode-wallet (not the controller, because it isn't out yet), and the status says the following:

Code: [Select]
{
  "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]
  "12161bf30e75b1bebe9d7b0ebf0d73902e0bea07021c400d166debab4a655552-1": "UPDATE_REQUIRED"
Is this concerning? I did a 'masternode start-alias' from the controller wallet.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 16, 2017, 06:20:11 pm
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"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on December 16, 2017, 09:13:59 pm
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?

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 16, 2017, 09:26:29 pm
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."
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Alex on December 16, 2017, 11:31:35 pm
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."

Hey Togo, I replied on bitcointalk with a possible fix. Make sure you controller wallet is also updated.

Edit: Just catching up and saw jaapgvk had that issue too. Try to have a look at my post there and tell me if it works for you. Again, make sure to update your controller wallet too.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 17, 2017, 01:52:35 am
Thank you for your help Alex. I followed your steps and my masternode says 'PRE-ENABLED' now, so I hope it is fixed.

Looks like other masternodes stayed enabled during the upgrade?

Also, on a sidenode: I reached out to coinsmarkets yesterday, and they halted deposits and withdrawals before the update :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: klondike on December 17, 2017, 07:11:00 am
616westwarmoth yes you can mining with MN machine ;)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 17, 2017, 08:35:18 am
Yes I am doing that.  The question is does it impact Masternodes and two, what is the ideal setting for those who are using Vultr.

I won't go above genproclimit=1 for mining if you have 1 or 2 core MN 
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 17, 2017, 10:25:55 pm
if anybody wants to try this provider for mining  :  https://hive.happybeehost.com/cart.php?a=confproduct&i=0


$6 for a 4CPU/2GB VPS is not bad at all 
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 18, 2017, 10:25:36 am
if anybody wants to try this provider for mining  :  https://hive.happybeehost.com/cart.php?a=confproduct&i=0


$6 for a 4CPU/2GB VPS is not bad at all

That's cheap indeed :) I wonder what the hashrate will be.

I've been using your hyperexpert suggestion for my masternode. Working great so far :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: putzlappen on December 18, 2017, 10:35:43 am
I rent a small VS for 5$/month on vultr.com.
Just for testing and learning. But now, after 24 hours of try and error (and 10 reinstalls of debian) iam again at my starting Point: nothing works  :'(

I worked like these tut: https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt (https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt) (and a lot of others, realy similars)

Maybe you got a hint for installing biblepay wallet an miner on an absolutly fresh debian for a noob like me  ;D
If not, no problem, i give my best, in weeks i have solved any problems^^

Best regards, Sebastian!
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 18, 2017, 10:51:06 am
I rent a small VS for 5$/month on vultr.com.
Just for testing and learning. But now, after 24 hours of try and error (and 10 reinstalls of debian) iam again at my starting Point: nothing works  :'(

I worked like these tut: https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt (https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt) (and a lot of others, realy similars)

Maybe you got a hint for installing biblepay wallet an miner on an absolutly fresh debian for a noob like me  ;D
If not, no problem, i give my best, in weeks i have solved any problems^^

Best regards, Sebastian!

Hi Sebastian,

I don't know if it will work with debian, but if you have a fresh installation of ubuntu 16.04, and follow this guide step by step, it should absolutely work:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

If you only have 1GB of RAM, you should also enlarge your swap-file before installation:
Code: [Select]
free (check if swap is 0)
dd if=/dev/zero of=/var/swap.img bs=1024k count=1000
mkswap /var/swap.img
swapon /var/swap.img
free (check if swap is 1024)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: putzlappen on December 18, 2017, 11:14:46 am
Hi Sebastian,

I don't know if it will work with debian, but if you have a fresh installation of ubuntu 16.04, and follow this guide step by step, it should absolutely work:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

If you only have 1GB of RAM, you should also enlarge your swap-file before installation:
Code: [Select]
free (check if swap is 0)
dd if=/dev/zero of=/var/swap.img bs=1024k count=1000
mkswap /var/swap.img
swapon /var/swap.img
free (check if swap is 1024)

WOW, Thanks for your fast Answer. I will try it directly <3
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 18, 2017, 11:24:23 am
WOW, Thanks for your fast Answer. I will try it directly <3

You're welcome :) Just let me know if something doesn't work, and I'll try to help you as best as I can.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 18, 2017, 11:56:00 am
That's cheap indeed :) I wonder what the hashrate will be.

I've been using your hyperexpert suggestion for my masternode. Working great so far :)

forgot to add a ref link .  :)   kidding .  glad it was useful for someone
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: putzlappen on December 18, 2017, 01:29:05 pm
IT WORKS  ;D :D ;D :D ;D

https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/ (https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/) was the answer i have looked for!

The Hashrate is with 570 - 580 H/s not realy fast, but its a momocore. But extrapolated its the same like my i7 per Core. So, not realy bad.
For Test Number 2 i rent such a 6$ Quadcore VS from HappyBee. (there was no reflink, sorry @tiras   :P)
But HappyBee seems to bee realy slow... My order ist stinn in processing since two hours. Maybe tomorrow !

Thank you for your help and support @jaapgvk, and sorry for some stupid questions^^

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 18, 2017, 02:27:48 pm
I applied 1069 on my MN . 

now it shows :

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


what does it mean ?    do I need to update controller to fix it .   WIN wallet is not ready yet for download  .
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 18, 2017, 02:37:14 pm
I applied 1069 on my MN . 

now it shows :

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


what does it mean ?    do I need to update controller to fix it .   WIN wallet is not ready yet for download  .

I also had that problem with a previous update. It will probably fix itself when you start the masternode from the upgraded wallet.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 18, 2017, 02:39:19 pm
IT WORKS  ;D :D ;D :D ;D

https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/ (https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/) was the answer i have looked for!

The Hashrate is with 570 - 580 H/s not realy fast, but its a momocore. But extrapolated its the same like my i7 per Core. So, not realy bad.
For Test Number 2 i rent such a 6$ Quadcore VS from HappyBee. (there was no reflink, sorry @tiras   :P)
But HappyBee seems to bee realy slow... My order ist stinn in processing since two hours. Maybe tomorrow !

Thank you for your help and support @jaapgvk, and sorry for some stupid questions^^

You're welcome :) Good to see that it worked. And you didn't ask any stupid question. I'm (also?) a Linux beginner, and without Togo's guides I wouldn't know where to start.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 18, 2017, 02:50:11 pm
I also had that problem with a previous update. It will probably fix itself when you start the masternode from the upgraded wallet.


just applied WIN apdate and restaarted both MN and controller.   still

 "UPDATE_REQUIRED" and
Code: [Select]
  "vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
  "service": "2:40000",
  "status": "Not capable masternode: Invalid protocol version"


./biblepay-cli getinfo
{
  "version": 1000609,
  "protocolversion": 70712,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.6.9",

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 18, 2017, 03:21:47 pm

just applied WIN apdate and restaarted both MN and controller.   still

 "UPDATE_REQUIRED" and
Code: [Select]
  "vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
  "service": "2:40000",
  "status": "Not capable masternode: Invalid protocol version"


./biblepay-cli getinfo
{
  "version": 1000609,
  "protocolversion": 70712,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.6.9",


answering to myself for the record :

 delete the wallet and start it from scratch ?

sanctuary wallet is empty anyway .

thanks PewPewGoesTheDuck for help
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 18, 2017, 03:22:22 pm

just applied WIN apdate and restaarted both MN and controller.   still

 "UPDATE_REQUIRED" and
Code: [Select]
  "vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
  "service": "2:40000",
  "status": "Not capable masternode: Invalid protocol version"


./biblepay-cli getinfo
{
  "version": 1000609,
  "protocolversion": 70712,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.6.9",


Did you also restart your masternode with the 'masternode start-alias' function?

Anyway, there is a fix that I also applied when it didn't work. It involves generating a new private-key. Let me just try and find it :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 18, 2017, 03:23:34 pm
Did you also restart your masternode with the 'masternode start-alias' function?

Anyway, there is a fix that I also applied when it didn't work. It involves generating a new private-key. Let me just try and find it :)


thanks Jaapgvk  ,    I fixed it by deleting the old wallet and restarting the daemon
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 18, 2017, 03:27:08 pm

thanks Jaapgvk  ,    I fixed it by deleting the old wallet and restarting the daemon

Nice to hear it already worked.

I found the fix that Alex posted. I'll just post it anyway for future reference:

https://bitcointalk.org/index.php?topic=2388064.msg26467807#msg26467807 (https://bitcointalk.org/index.php?topic=2388064.msg26467807#msg26467807)

Quote
1)

On the controller wallet:

i. do masternode genkey
ii. replace the old key in masternodes.conf with the newly generated one.

On the sanctuary:

i. replace the old key in biblepay.conf with the newly generated one.
ii. restart the sanctuary

2)

i. wait for the masternode to display: "status": "Not capable masternode: Masternode not in masternode list" (do masternode status to check)
ii. start it again from the controller.
iii. check if it's now displaying "status": "Masternode successfully started"
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 18, 2017, 03:35:46 pm
Nice to hear it already worked.

I found the fix that Alex posted. I'll just post it anyway for future reference:

https://bitcointalk.org/index.php?topic=2388064.msg26467807#msg26467807 (https://bitcointalk.org/index.php?topic=2388064.msg26467807#msg26467807)


thank you Jaapgvk  ! 
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 18, 2017, 03:43:35 pm

thank you Jaapgvk  !

You're welcome :) I wonder what will happen in the next couple of days, since we both haven't 'won' anything yet.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 18, 2017, 04:01:07 pm
You're welcome :) I wonder what will happen in the next couple of days, since we both haven't 'won' anything yet.


this is unpredictable imho.  I don't understand the secret set of rules here .

in the meantime :
  "21718": "BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS:3",
  "21719": "BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS:7",
  "21720": "BLWrBmujyTdv2qxwn8KDFpUFrTvH7AbmD1:7",
  "21721": "BLWrBmujyTdv2qxwn8KDFpUFrTvH7AbmD1:4",
  "21722": "BNkdFRRo2Cycyvc37tVaNW4FCiFDrR9QDV:4",
  "21723": "BNkdFRRo2Cycyvc37tVaNW4FCiFDrR9QDV:4",
  "21724": "BQ4kjMzQUEcQdMMpvhDMNt2McfhxzKztRX:3",
  "21725": "BQ4kjMzQUEcQdMMpvhDMNt2McfhxzKztRX:7",
  "21726": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:3",
  "21727": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:4",
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 18, 2017, 06:12:12 pm

this is unpredictable imho.  I don't understand the secret set of rules here .

in the meantime :
  "21718": "BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS:3",
  "21719": "BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS:7",
  "21720": "BLWrBmujyTdv2qxwn8KDFpUFrTvH7AbmD1:7",
  "21721": "BLWrBmujyTdv2qxwn8KDFpUFrTvH7AbmD1:4",
  "21722": "BNkdFRRo2Cycyvc37tVaNW4FCiFDrR9QDV:4",
  "21723": "BNkdFRRo2Cycyvc37tVaNW4FCiFDrR9QDV:4",
  "21724": "BQ4kjMzQUEcQdMMpvhDMNt2McfhxzKztRX:3",
  "21725": "BQ4kjMzQUEcQdMMpvhDMNt2McfhxzKztRX:7",
  "21726": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:3",
  "21727": "B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ:4",

Just won for the first time. It was also a 'doubleblock'.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 18, 2017, 10:02:32 pm
Just won for the first time. It was also a 'doubleblock'.

congrats !     I'm still emptyhanded
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 18, 2017, 10:44:19 pm
do we lock ( encrypt )  the wallet on controller node or keep it unlocked with escrow ?   
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 19, 2017, 12:08:14 am
congrats !     I'm still emptyhanded

Is your masternode also hosted on hyperexpert? Maybe it has some kind of weakness that makes it miss some kind of 'check'.

I only won the one 'doubleblock' and that's it.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 19, 2017, 12:48:22 am
Is your masternode also hosted on hyperexpert? Maybe it has some kind of weakness that makes it miss some kind of 'check'.

I only won the one 'doubleblock' and that's it.


yes, it's on hyperexpert.   
Does it matter where the node is located physically ?
 Is it possible that VULTR nodes communicate better with each other .
If that's the case it doesn't seem right .

 I just found it finally won 1/10 of a block .  not much but at least the beginning

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 19, 2017, 03:11:01 am

yes, it's on hyperexpert.   
Does it matter where the node is located physically ?
 Is it possible that VULTR nodes communicate better with each other .
If that's the case it doesn't seem right .

 I just found it finally won 1/10 of a block .  not much but at least the beginning

I have no idea... Did you use the same vps for testing the testnet sanctuaries?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: putzlappen on December 19, 2017, 06:41:57 am
Hi Community,

i just want to give some feedback for the Virtual Server from vultr.com and happybeehost.com:

Vultr.com: Singlecore, 1GB RAM, 5$/month -> 575 - 585 H/s
Happybeehost: Quadcore, 2 GB RAM, 6$/month -> 420 - 440 H/s

But the happybee-4-core hase much more Hs². What does this mean?

If someone have other provider for testing, just tell me ;-)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 19, 2017, 06:47:42 am
Hi Community,

i just want to give some feedback for the Virtual Server from vultr.com and happybeehost.com:

Vultr.com: Singlecore, 1GB RAM, 5$/month -> 575 - 585 H/s
Happybeehost: Quadcore, 2 GB RAM, 6$/month -> 420 - 440 H/s

If someone have other provider for testing, just tell me ;-)

That's very interesting! Just a question: what's your 'genproclimit' on the happybeehost?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: putzlappen on December 19, 2017, 06:51:13 am
That's very interesting! Just a question: what's your 'genproclimit' on the happybeehost?

genproclimit = 4 on happybeehost.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 19, 2017, 07:10:56 am
genproclimit = 4 on happybeehost.

Thanks :) Interesting.

I did a little bit of mining on the hyperexpert VPS, but I can't remember how much hps I got. I think it was around 400-500 HPS with a single-core and 1GB RAM.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 19, 2017, 08:32:31 am
I have no idea... Did you use the same vps for testing the testnet sanctuaries?

yes, I used the same VPS
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 19, 2017, 09:10:06 am
yes, I used the same VPS

Okay, then I don't know what could be it. But I got another 'win' so maybe it will flatten out in the long run. Looking at the other winners, the list seems to diversify a bit. Did you win any, except the '1 part'?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 19, 2017, 09:19:14 am
Okay, then I don't know what could be it. But I got another 'win' so maybe it will flatten out in the long run. Looking at the other winners, the list seems to diversify a bit. Did you win any, except the '1 part'?

yes, I've got 2 more wins shortly after the 1st one.   
looking at other MN stats it's by far not a fair distribution for now. 
Rob was mentioning that some minor updates  will follow.
Hopefully they will improve round -robin algorithm here .
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 19, 2017, 10:11:36 am
https://en.wikipedia.org/wiki/Law_of_large_numbers (https://en.wikipedia.org/wiki/Law_of_large_numbers)

Have to be careful extrapolating from a small data set, there is going to be randomness / fluctuations with smaller amount of data

I think Rob mentioned the algorithm has something to do with a hash number being near a masternode's number, Id have to look into it, sounds interesting
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: putzlappen on December 20, 2017, 01:36:08 am
Good Morning Community (its 08:30 am here )

I got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

Code: [Select]
cd /home/root/biblepay/src
./biblepayd -daemon

and some seconds later i check status with:

Code: [Select]
./biblepay-cli getmininginfo
i only get an error: couldn't connect to server back.

But sometimes, everything works fine, and biblepay runs stable until it stopps random.
I was looking for a log to solve this but cant find something in /var/log or in biblepay directory.


An other thing: i want to testing such an 8-core vps from hyperexpert, but they dont sell any vps. Maybe they are in hollyday.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 20, 2017, 02:18:30 am
https://en.wikipedia.org/wiki/Law_of_large_numbers (https://en.wikipedia.org/wiki/Law_of_large_numbers)

Have to be careful extrapolating from a small data set, there is going to be randomness / fluctuations with smaller amount of data

I think Rob mentioned the algorithm has something to do with a hash number being near a masternode's number, Id have to look into it, sounds interesting

Yeah, you're absolutely right :) It's just that I didn't get any 'win' in the first 140 blocks (counting from block 21600), although my masternode was online or upgrading all that time, so I was getting worried that something might be wrong with my VPS.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 20, 2017, 02:30:37 am
Good Morning Community (its 08:30 am here )

I got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

Code: [Select]
cd /home/root/biblepay/src
./biblepayd -daemon

and some seconds later i check status with:

Code: [Select]
./biblepay-cli getmininginfo
i only get an error: couldn't connect to server back.

But sometimes, everything works fine, and biblepay runs stable until it stopps random.
I was looking for a log to solve this but cant find something in /var/log or in biblepay directory.

An other thing: i want to testing such an 8-core vps from hyperexpert, but they dont sell any vps. Maybe they are in hollyday.

Good morning (also for me, living in the Netherlands) :)

When you get the 'couldn't connect to server' error, that indeed most probably means that biblepay crashed. I've had that in the past with a few installations. You could try a reindex, but I don't know if that would help to be honest. Maybe someone else can answer this question more accurately for you.

About hyperexpert: It checked, and it's probably something temporary and/of holidays, but I can't find an announcement no their blog.

About the hps vs hps2: the hps2 is what the pool is using as your 'actual hps', and uses that to calculate your payout (it's correlated to the amount of shares). And the hps is what your wallet reports, but I don't think it's really accurate as of yet. I don't have enough knowledge te explain the details, but you could try and find information about this on bitcointalk (although it might be kind of hard to find between the mountains of posts).
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 20, 2017, 04:24:13 am
Good Morning Community (its 08:30 am here )

I got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

Code: [Select]
cd /home/root/biblepay/src
./biblepayd -daemon

and some seconds later i check status with:

Code: [Select]
./biblepay-cli getmininginfo
i only get an error: couldn't connect to server back.

But sometimes, everything works fine, and biblepay runs stable until it stopps random.
I was looking for a log to solve this but cant find something in /var/log or in biblepay directory.


An other thing: i want to testing such an 8-core vps from hyperexpert, but they dont sell any vps. Maybe they are in hollyday.

>> got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

is that 1GB or 2GB RAM VPS you've got random daemon failures at ?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: putzlappen on December 20, 2017, 04:31:10 am
>> got a Problem with this happybeecloud-vps: randomly biblepay (v1.0.6.9) stopping. I dont know the reason. When i start it with

is that 1GB or 2GB RAM VPS you've got random daemon failures at ?

Its the 2 GB RAM Quadcore VPS.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 20, 2017, 04:50:29 am
Its the 2 GB RAM Quadcore VPS.

I had the same thing on a 1GB VPS and I just dropped it . 
You could create some kind of a cron job calling a shell script checking if daemon is running and restarting it .
I guess provider does not favor mining on it's premises.  that's it . 
they can control the processes on VPSes .
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: alvin on December 20, 2017, 05:27:16 am
I had the same thing on a 1GB VPS and I just dropped it . 
You could create some kind of a cron job calling a shell script checking if daemon is running and restarting it .
I guess provider does not favor mining on it's premises.  that's it . 
they can control the processes on VPSes .

Same with you , I cancelled it as I tried many times to test,  look like the provider had a detector tool for monitor their vps ....
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: putzlappen on December 20, 2017, 05:31:14 am
Same with you , I cancelled it as I tried many times to test,  look like the provider had a detector tool for monitor their vps ....

Which Provider did you mean?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: alvin on December 20, 2017, 05:54:31 am
Which Provider did you mean?

HappyBee Host
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: putzlappen on December 20, 2017, 06:03:41 am
HappyBee Host

Thank you for telling <3

Then i can stopp to trying solve this problem. And can start to find a "better" provider  ;D
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 20, 2017, 03:46:50 pm
I looked up Rob's notes on the winning algorithm

"As far as "luck" of winning the spot, we are using an algorithm where the nodes rank is determined by how close its vin is to the blockhash its voting on, so its really luck."

"The winner is based on the delta between the masternode vin and the blockhash, so that makes the winner random, thats why they can repeat back to back."

What is the masternode VIN?

This kind of reminds me of the Price is Right LOL but going both ways up and down
I think some VINs could have really unlucky spots being sandwhiched between other VINs, does that make sense?

(http://a.abcnews.com/images/US/150102_atm_price_is_right_fail_16x9_992.jpg)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 20, 2017, 05:00:38 pm
I looked up Rob's notes on the winning algorithm

"As far as "luck" of winning the spot, we are using an algorithm where the nodes rank is determined by how close its vin is to the blockhash its voting on, so its really luck."

"The winner is based on the delta between the masternode vin and the blockhash, so that makes the winner random, thats why they can repeat back to back."

What is the masternode VIN?

This kind of reminds me of the Price is Right LOL but going both ways up and down
I think some VINs could have really unlucky spots being sandwhiched between other VINs, does that make sense?

(http://a.abcnews.com/images/US/150102_atm_price_is_right_fail_16x9_992.jpg)

Yeah, I'd like to have more insight into the technicalities of this, and how random it really is. Although I must say that my payments seem to be spaced apart quite evenly, although less than expected.

Also, did any of you needed to restart your sanctuary after the last update (1.0.7.1)? I just updated my wallets and started my sanctuary and it just kept saying 'ONLINE'.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 20, 2017, 05:21:26 pm
I copied the masternode winners for block 21600 to 22032,

I then pasted it into excel and did Data >> Text to columns and split by Other colon ":"
then I deleted the extra columns (and I only used the first winner in the list)
then I used this excel command in 2nd column to get counts: =COUNTIF(A:A, A1)
then I copy pasted the counts by value to new column and deleted the previous count column
then I removed duplicates in 1st column

Code: [Select]
B4icq9xMoey9SUN14Zosu5eJyh53GpMuDE 4
 B547NvFM2TUeCKxEGcxCxpt8as42pyS4po 20
 B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ 24
 B69kMjn6a8vRH5bmVEdahheKqCqHoJejoz 7
 B6dcexhthQYGEdQZMiMdLNaFyFAyJEYXYE 9
 B6W3399nVAFE9c9AmPBd7qeWLd1r9czz2u 8
 B75XgzyKekgRTJ5JzTgqsCqw482MeH2MW6 21
 B77a6qHMJKmowXMRfTUy8a8dNc1DT5DHn4 18
 B8se8LxzDo9AKmSB9fnY38gbc3ubedRZxJ 20
 B8VyJEETEgaYirHeckJANQBd82AKfLkvfe 1
 B8xCuX4CoaP4nCgazT8sqh3R1f4nxMvdFt 6
 B9bXsooS8fQMpnXEWxMRiTuaCgDN8GeCAm 8
 B9ocKvVZg17at8bGa4dU4xybZ9eFnMu1o2 5
 BBkb2V8oAFex1ZZs4VMo9qB6PUt6gbFZd2 3
 BByjk8Hp9wUvaM6pXEC2yseEjh6GXJTBKm 8
 BC99kkb2mvz6SRdAVYRsgKaoWeuYavYLUT 7
 BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS 18
 BCKNkErkLgFHRdp2SufbWp9vmhyDTVhSUQ 7
 BCrPqL3MchGHogP7cGtxFT7jM2B1aSeAUN 7
 BD7Y9KhJHPNLJCEntbQCjhKrLVjGaDLCgN 17
 BDkocGarpfSBMuT15p9dQzsAfNqsgb2UHh 21
 BDQk4KG2Mhx9u4yiNW83p2nLN4LTm9qKCE 8
 BGAZhgeSqPgVt9L9CT2BJR6yHZy2UfyoVb 8
 BGRYX31E9EgciiEaReCV9GUqBxNZEwv8XE 7
 BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs 8
 BJ8VuuDM2bcDAYEED49Yk7Fm2TEUSgekug 7
 BJbN7u9CKqyCR4QJ7WihchDXaBwYoF9Hcq 8
 BJyURkU96QieSxF73LxcQM1N6tFhghLqmw 7
 BK9wLCCVSRKyiq27GhTrvqsivJBgYC6h7f 8
 BKcPm29NX2BjJ2N9ZD3ZjP1AV1tG5B32Mk 7
 BKFgb6K73erhccQs9FYnq5C7y4AspAMhyu 6
 BL3q4ox7DXzE1WsvvKZjAiFGVBEc5vDKpa 6
 BL3xzrS7rA721F8ztVMs2vQcrp2pHWctSF 6
 BLWrBmujyTdv2qxwn8KDFpUFrTvH7AbmD1 13
 BN6iwaYKKeqVS3QC9MfCXpH1C7CdsEeQbt 1
 BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9 6
 BNkdFRRo2Cycyvc37tVaNW4FCiFDrR9QDV 9
 BPUJUqxGcqKuJsj7gHATX9BsPCyKJ2rN9w 6
 BPXpXpsVAMM2cyzkMsSQ8xVJetbLNX6tQz 8
 BQ4kjMzQUEcQdMMpvhDMNt2McfhxzKztRX 16
 BQfd2t6iEi49ugwU2LkQBhUS3F2AnsZWYY 15
 BQjqyH4QCUhuNmUKw8apELsPqbmEC5jpUV 6
 BQKWtsB8L6DxeWbWVQbm86qvpUot1DWSAb 6
 BQtrk6tacdZwhftqQTmbBwG84fm2o1YFGo 2
 BRUjgRr1nVL4rt8Kks3thFDdsQSLQBCj43 8
 BSrFn8zpC48AykVANWcjVEve5tzn8NQNRE 7
 BSv2sd6jRutxDsFef7tznJjaNLrdvq3nfS 5


The one thing I dont know, is I dont know how long each of these sanctuaries has been online, sanctuary that just started vs one that has been on the past 2 days, if we had that amount of time enabled data, then we could do the statistical analysis

For instance B8VyJEETEgaYirHeckJANQBd82AKfLkvfe is someone I just helped get setup on Slack a few hours ago and he got 1 payment so far
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 20, 2017, 07:51:45 pm
I copied the masternode winners for block 21600 to 22032,

I then pasted it into excel and did Data >> Text to columns and split by Other colon ":"
then I deleted the extra columns (and I only used the first winner in the list)
then I used this excel command in 2nd column to get counts: =COUNTIF(A:A, A1)
then I copy pasted the counts by value to new column and deleted the previous count column
then I removed duplicates in 1st column

Code: [Select]
B4icq9xMoey9SUN14Zosu5eJyh53GpMuDE 4
 B547NvFM2TUeCKxEGcxCxpt8as42pyS4po 20
 B5Ac1kfZd47aogmrHKzQM1SR65f2HidfJJ 24
 B69kMjn6a8vRH5bmVEdahheKqCqHoJejoz 7
 B6dcexhthQYGEdQZMiMdLNaFyFAyJEYXYE 9
 B6W3399nVAFE9c9AmPBd7qeWLd1r9czz2u 8
 B75XgzyKekgRTJ5JzTgqsCqw482MeH2MW6 21
 B77a6qHMJKmowXMRfTUy8a8dNc1DT5DHn4 18
 B8se8LxzDo9AKmSB9fnY38gbc3ubedRZxJ 20
 B8VyJEETEgaYirHeckJANQBd82AKfLkvfe 1
 B8xCuX4CoaP4nCgazT8sqh3R1f4nxMvdFt 6
 B9bXsooS8fQMpnXEWxMRiTuaCgDN8GeCAm 8
 B9ocKvVZg17at8bGa4dU4xybZ9eFnMu1o2 5
 BBkb2V8oAFex1ZZs4VMo9qB6PUt6gbFZd2 3
 BByjk8Hp9wUvaM6pXEC2yseEjh6GXJTBKm 8
 BC99kkb2mvz6SRdAVYRsgKaoWeuYavYLUT 7
 BCb8B85R4mpuiy62Sbs9W4Xv2w5CVEJ5TS 18
 BCKNkErkLgFHRdp2SufbWp9vmhyDTVhSUQ 7
 BCrPqL3MchGHogP7cGtxFT7jM2B1aSeAUN 7
 BD7Y9KhJHPNLJCEntbQCjhKrLVjGaDLCgN 17
 BDkocGarpfSBMuT15p9dQzsAfNqsgb2UHh 21
 BDQk4KG2Mhx9u4yiNW83p2nLN4LTm9qKCE 8
 BGAZhgeSqPgVt9L9CT2BJR6yHZy2UfyoVb 8
 BGRYX31E9EgciiEaReCV9GUqBxNZEwv8XE 7
 BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs 8
 BJ8VuuDM2bcDAYEED49Yk7Fm2TEUSgekug 7
 BJbN7u9CKqyCR4QJ7WihchDXaBwYoF9Hcq 8
 BJyURkU96QieSxF73LxcQM1N6tFhghLqmw 7
 BK9wLCCVSRKyiq27GhTrvqsivJBgYC6h7f 8
 BKcPm29NX2BjJ2N9ZD3ZjP1AV1tG5B32Mk 7
 BKFgb6K73erhccQs9FYnq5C7y4AspAMhyu 6
 BL3q4ox7DXzE1WsvvKZjAiFGVBEc5vDKpa 6
 BL3xzrS7rA721F8ztVMs2vQcrp2pHWctSF 6
 BLWrBmujyTdv2qxwn8KDFpUFrTvH7AbmD1 13
 BN6iwaYKKeqVS3QC9MfCXpH1C7CdsEeQbt 1
 BNidV9kWAZECM1sEtg7ZiQyYn2ghDY6mN9 6
 BNkdFRRo2Cycyvc37tVaNW4FCiFDrR9QDV 9
 BPUJUqxGcqKuJsj7gHATX9BsPCyKJ2rN9w 6
 BPXpXpsVAMM2cyzkMsSQ8xVJetbLNX6tQz 8
 BQ4kjMzQUEcQdMMpvhDMNt2McfhxzKztRX 16
 BQfd2t6iEi49ugwU2LkQBhUS3F2AnsZWYY 15
 BQjqyH4QCUhuNmUKw8apELsPqbmEC5jpUV 6
 BQKWtsB8L6DxeWbWVQbm86qvpUot1DWSAb 6
 BQtrk6tacdZwhftqQTmbBwG84fm2o1YFGo 2
 BRUjgRr1nVL4rt8Kks3thFDdsQSLQBCj43 8
 BSrFn8zpC48AykVANWcjVEve5tzn8NQNRE 7
 BSv2sd6jRutxDsFef7tznJjaNLrdvq3nfS 5


The one thing I dont know, is I dont know how long each of these sanctuaries has been online, sanctuary that just started vs one that has been on the past 2 days, if we had that amount of time enabled data, then we could do the statistical analysis

For instance B8VyJEETEgaYirHeckJANQBd82AKfLkvfe is someone I just helped get setup on Slack a few hours ago and he got 1 payment so far


wonders of excel analytics :)   
 I've been up from day 1 - 8 wins .
   few top  nodes :  24 - 20 .   
 to big  of a difference

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 20, 2017, 08:13:17 pm
Yeah, I'd like to have more insight into the technicalities of this, and how random it really is. Although I must say that my payments seem to be spaced apart quite evenly, although less than expected.

Also, did any of you needed to restart your sanctuary after the last update (1.0.7.1)? I just updated my wallets and started my sanctuary and it just kept saying 'ONLINE'.


Jaapgvk , did you update both sanct MN and controller and it went "enabled"  right away ?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 21, 2017, 12:48:17 am

Jaapgvk , did you update both sanct MN and controller and it went "enabled"  right away ?

It just stayed enabled in the list. After updating both, I restarted (I did the controller first), and after starting the sanctuary wallet it said 'masternode successfully started' after syncing. Didn't have to do anything from the controller wallet.

I've received a payment since then, so I'm guessing all is fine :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 21, 2017, 01:51:43 am
I opened a tech ticket, the bigger issue I think is back-to-back winners, out of 493 block winners (not all actually won BBP mind you), 146 times there was a back-to-back winner.  If there were only 4 enabled MN that would be statistically correct but I think that's what is driving the disparity.

I fully agree, and that's one of the first things I noticed. I wonder how the block distribution was in testnet. I mean, I was there testing, but I didn't look at the winners list to see the actual distribution. I'm gonna look now if I can call the logs on that.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 21, 2017, 02:45:19 am
It seems testnet has been reset unfortunately... Anyone has the winners logs?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 21, 2017, 08:53:36 am
I noticed all the Sanctuaries have fallen into WATCHDOG_EXPIRED state, is something going on? or something we need to do?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 21, 2017, 09:17:03 am
I noticed all the Sanctuaries have fallen into WATCHDOG_EXPIRED state, is something going on? or something we need to do?

Have you reached out to Rob? On my side, it seems that two of the masternodes stayed 'enabled'.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 21, 2017, 11:33:14 am
Weird I think they all went back to ENABLED  ???

they didn't.

as of now only 3 are enabled :

 ./biblepay-cli masternode list  | grep ENAB
  "4a6d5b74939f29f76030fb80204a244f46b2dbdc13656db05e8372e6bfdee8be-1": "ENABLED",
  "068f3610e03782cae8e55ef4d42d0b4773ae10a26c0a30340a6344e582f6327e-1": "ENABLED",
  "b37da1c9e539dbe7f908d927962b8cb4e7636bfcc42a7ded77ec3fd4cc4bcb56-1": "ENABLED",

could it be something caused by yesterdays update ?

running BBP seems like a FT job
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 21, 2017, 11:49:51 am
They're still in 'WATCHDOG EXPIRED' mode on my end (except the three enabled ones).

I used the same commands you used West, and I got approximately the same results:

Code: [Select]
================================================================= ERRORS =================================================================
__________________________________________ ERROR collecting test/unit/models/test_proposals.py ___________________________________________
test/unit/models/test_proposals.py:10: in <module>
    from models import GovernanceObject, Proposal, Vote
lib/models.py:5: in <module>
    import init
lib/init.py:103: in <module>
    main()
lib/init.py:94: in main
    if not is_database_correctly_configured():
lib/init.py:55: in is_database_correctly_configured
    sys.exit(1)
E   SystemExit: 1
------------------------------------------------------------ Captured stdout -------------------------------------------------------------
[error]: unable to open database file
Cannot connect to database. Please ensure database service is running and user access is properly configured in 'watchman.conf'.
_________________________________________ ERROR collecting test/unit/models/test_superblocks.py __________________________________________
test/unit/models/test_superblocks.py:10: in <module>
    from models import GovernanceObject, Proposal, Superblock, Vote
lib/models.py:5: in <module>
    import init
lib/init.py:103: in <module>
    main()
lib/init.py:94: in main
    if not is_database_correctly_configured():
lib/init.py:55: in is_database_correctly_configured
    sys.exit(1)
E   SystemExit: 1
------------------------------------------------------------ Captured stdout -------------------------------------------------------------
[error]: unable to open database file
Cannot connect to database. Please ensure database service is running and user access is properly configured in 'watchman.conf'.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
======================================================== 2 error in 0.86 seconds =========================================================

Code: [Select]
Traceback (most recent call last):
  File "bin/watchman.py", line 244, in <module>
    main()
  File "bin/watchman.py", line 191, in main
    perform_biblepayd_object_sync(biblepayd)
  File "bin/watchman.py", line 24, in perform_biblepayd_object_sync
    GovernanceObject.sync(biblepayd)
  File "lib/models.py", line 87, in sync
    (go, subobj) = self.import_gobject_from_biblepayd(biblepayd, item)
  File "lib/models.py", line 142, in import_gobject_from_biblepayd
    subobj, created = subclass.get_or_create(object_hash=object_hash, defaults=subdikt)
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 4800, in get_or_create
    return query.get(), False
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 3090, in get
    return next(clone.execute())
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 2267, in next
    obj = self.iterate()
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 2253, in iterate
    return self.process_row(row)
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 2331, in process_row
    setattr(instance, column, func(row[i]))
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 1072, in python_value
    return decimal.Decimal(str(value))
  File "/usr/lib/python2.7/decimal.py", line 547, in __new__
    "Invalid literal for Decimal: %r" % value)
  File "/usr/lib/python2.7/decimal.py", line 3873, in _raise_error
    raise error(explanation)
decimal.InvalidOperation: Invalid literal for Decimal: '203,096'

But I have no idea what I'm doing, lol (but not so lol).

It's indeed a full-time job... But hey, as you said Togo: it's a startup. Let's just hope we get the engine spinning nicely soon...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 21, 2017, 11:54:02 am
They're still in 'WATCHDOG EXPIRED' mode on my end (except the three enabled ones).

I used the same commands you used West, and I got approximately the same results:

Code: [Select]
================================================================= ERRORS =================================================================
__________________________________________ ERROR collecting test/unit/models/test_proposals.py ___________________________________________
test/unit/models/test_proposals.py:10: in <module>
    from models import GovernanceObject, Proposal, Vote
lib/models.py:5: in <module>
    import init
lib/init.py:103: in <module>
    main()
lib/init.py:94: in main
    if not is_database_correctly_configured():
lib/init.py:55: in is_database_correctly_configured
    sys.exit(1)
E   SystemExit: 1
------------------------------------------------------------ Captured stdout -------------------------------------------------------------
[error]: unable to open database file
Cannot connect to database. Please ensure database service is running and user access is properly configured in 'watchman.conf'.
_________________________________________ ERROR collecting test/unit/models/test_superblocks.py __________________________________________
test/unit/models/test_superblocks.py:10: in <module>
    from models import GovernanceObject, Proposal, Superblock, Vote
lib/models.py:5: in <module>
    import init
lib/init.py:103: in <module>
    main()
lib/init.py:94: in main
    if not is_database_correctly_configured():
lib/init.py:55: in is_database_correctly_configured
    sys.exit(1)
E   SystemExit: 1
------------------------------------------------------------ Captured stdout -------------------------------------------------------------
[error]: unable to open database file
Cannot connect to database. Please ensure database service is running and user access is properly configured in 'watchman.conf'.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
======================================================== 2 error in 0.86 seconds =========================================================

Code: [Select]
Traceback (most recent call last):
  File "bin/watchman.py", line 244, in <module>
    main()
  File "bin/watchman.py", line 191, in main
    perform_biblepayd_object_sync(biblepayd)
  File "bin/watchman.py", line 24, in perform_biblepayd_object_sync
    GovernanceObject.sync(biblepayd)
  File "lib/models.py", line 87, in sync
    (go, subobj) = self.import_gobject_from_biblepayd(biblepayd, item)
  File "lib/models.py", line 142, in import_gobject_from_biblepayd
    subobj, created = subclass.get_or_create(object_hash=object_hash, defaults=subdikt)
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 4800, in get_or_create
    return query.get(), False
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 3090, in get
    return next(clone.execute())
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 2267, in next
    obj = self.iterate()
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 2253, in iterate
    return self.process_row(row)
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 2331, in process_row
    setattr(instance, column, func(row[i]))
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 1072, in python_value
    return decimal.Decimal(str(value))
  File "/usr/lib/python2.7/decimal.py", line 547, in __new__
    "Invalid literal for Decimal: %r" % value)
  File "/usr/lib/python2.7/decimal.py", line 3873, in _raise_error
    raise error(explanation)
decimal.InvalidOperation: Invalid literal for Decimal: '203,096'

But I have no idea what I'm doing, lol (but not so lol).

It's indeed a full-time job... But hey, as you said Togo: it's a startup. Let's just hope we get the engine spinning nicely soon...


jaapgvk  ,   are trying to say there's an error in python code ?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 21, 2017, 12:04:24 pm
jaapgvk  ,   are trying to say there's an error in python code ?

No, I'm just doing the same West did, so we could compare. Maybe someone else can debug it or something.

I don't have enough Linux knowledge to really contribute here, sorry. But if I can do anything to help, just tell me what to do :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 21, 2017, 12:18:18 pm
No, I'm just doing the same West did, so we could compare. Maybe someone else can debug it or something.

I don't have enough Linux knowledge to really contribute here, sorry. But if I can do anything to help, just tell me what to do :)

I've got the same error output :

Code: [Select]
~/.biblepaycore/watchman# venv/bin/python bin/watchman.py
Traceback (most recent call last):
  File "bin/watchman.py", line 244, in <module>
    main()
  File "bin/watchman.py", line 191, in main
    perform_biblepayd_object_sync(biblepayd)
  File "bin/watchman.py", line 24, in perform_biblepayd_object_sync
    GovernanceObject.sync(biblepayd)
  File "lib/models.py", line 87, in sync
    (go, subobj) = self.import_gobject_from_biblepayd(biblepayd, item)
  File "lib/models.py", line 142, in import_gobject_from_biblepayd
    subobj, created = subclass.get_or_create(object_hash=object_hash, defaults=subdikt)
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 4800, in get_or_create
    return query.get(), False
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 3090, in get
    return next(clone.execute())
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 2267, in next
    obj = self.iterate()
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 2253, in iterate
    return self.process_row(row)
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 2331, in process_row
    setattr(instance, column, func(row[i]))
  File "/root/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/peewee.py", line 1072, in python_value
    return decimal.Decimal(str(value))
  File "/usr/lib/python2.7/decimal.py", line 547, in __new__
    "Invalid literal for Decimal: %r" % value)
  File "/usr/lib/python2.7/decimal.py", line 3873, in _raise_error
    raise error(explanation)
decimal.InvalidOperation: Invalid literal for Decimal: '203,096'
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 21, 2017, 01:07:17 pm
I don't think I did anything differently, but I can say that the first and second one are mine.  So it's possible I borked it but I cannot imagine how.


West , can you  compare getinfo with mine :
 
Code: [Select]
./biblepay-cli getinfo
{
  "version": 1000701,
  "protocolversion": 70712,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.7.1",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 22145,
  "timeoffset": 0,
  "connections": 208,
  "proxy": "",
  "difficulty": 319.8535804163807,
  "testnet": false,
  "keypoololdest": 1513631658,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 21, 2017, 03:24:12 pm
I have BiblePay installed on another PC, and it is showing all sanctuaries as ENABLED or PRE_ENABLED,

My controller wallet shows most sanctuaries as WATCHDOG_EXPIRED.

Theres a note at the top of "My Sanctuaries" that says:

"Note: Status of your sanctuaries in local wallet can potentially be slightly incorrect.
Always wait for wallet to sync additional data and then double check from another node
if your masternode should be running but you still do not see "ENABLED" in "Status" field."

I wonder if we are just seeing incorrect data / experiencing a wallet glitch/bug in our Controller Wallets?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 21, 2017, 04:34:09 pm
At the moment, in my 'normal' wallets, the masternode statuses are a colourful rainbow of:

'enabled'
'pre enabled'
'watchdog expired'
'new start required'

I'm going to get some sleep now. Maybe it will sort itself out in the meantime...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 21, 2017, 04:37:02 pm
The differences on mine are pretty expected

Blocks
Difficulty
Keypoololdest
Keypool Size


Code: [Select]
  "version": 1000701,
  "protocolversion": 70712,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.7.1",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 22156,
  "timeoffset": 0,
  "connections": 116,
  "proxy": "",
  "difficulty": 623.3720306964408,
  "testnet": false,
  "keypoololdest": 1513488324,
  "keypoolsize": 1008,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""


I meant the first few lines:

version": 1000701,
  "protocolversion": 70712,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.7.1",
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 21, 2017, 04:45:29 pm
At the moment, in my 'normal' wallets, the masternode statuses are a colourful rainbow of:

'enabled'
'pre enabled'
'watchdog expired'
'new start required'

I'm going to get some sleep now. Maybe it will sort itself out in the meantime...

I wish we had some feedback of updates from the project leads  if it's normal and we should just disregard .
We were told the "WAtchdog_Expired"  takes the MN off the queue and voting . 
I had a couple of wins today though.




Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: togoshigekata on December 21, 2017, 05:34:37 pm
Okay the other guys were right, there is an error in watchman when getting an object, I bet someone typed in a comma into their proposal amount maybe? hehehe

"decimal.InvalidOperation: Invalid literal for Decimal: '203,096'"

https://github.com/biblepay/watchman/blob/master/bin/watchman.py#L24
https://github.com/biblepay/watchman/blob/master/lib/models.py#L87
https://github.com/biblepay/watchman/blob/master/lib/models.py#L142

"DataString": "[[\"proposal\",{\"end_epoch\":\"1513805540\",\"name\":\"Help Blue Get A Sanctuary\",\"payment_address\":\"BCrxzSM2kLy8ERww4bch1fesRVFCLv2Tce\",\"payment_amount\":\"203,096\",\"start_epoch\":\"1513805540\",\"type\":1,\"url\":\"http://forum.biblepay.org/index.php?topic=52.0\"}]]",
    "Hash": "14ec3b00c46a8f1090be5bc46100e5df547f5e9ed6c3cba8a75ca72b4a9ef572",

LOL
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: tiras on December 21, 2017, 05:48:06 pm
Okay the other guys were right, there is an error in watchman when getting an object, I bet someone typed in a comma into their proposal amount maybe? hehehe

"decimal.InvalidOperation: Invalid literal for Decimal: '203,096'"

https://github.com/biblepay/watchman/blob/master/bin/watchman.py#L24
https://github.com/biblepay/watchman/blob/master/lib/models.py#L87
https://github.com/biblepay/watchman/blob/master/lib/models.py#L142

"DataString": "[[\"proposal\",{\"end_epoch\":\"1513805540\",\"name\":\"Help Blue Get A Sanctuary\",\"payment_address\":\"BCrxzSM2kLy8ERww4bch1fesRVFCLv2Tce\",\"payment_amount\":\"203,096\",\"start_epoch\":\"1513805540\",\"type\":1,\"url\":\"http://forum.biblepay.org/index.php?topic=52.0\"}]]",
    "Hash": "14ec3b00c46a8f1090be5bc46100e5df547f5e9ed6c3cba8a75ca72b4a9ef572",

LOL


means we are having another update coming soon ,   :o


Togo ,  you definitely deserve compensation for your support
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 21, 2017, 06:38:23 pm
Okay the other guys were right, there is an error in watchman when getting an object, I bet someone typed in a comma into their proposal amount maybe? hehehe

So, this 'blue' guy, with his stupid proposal, single handedly crashed watchman. But it's not a bad thing, right? He 'found' a bug and it will be squashed.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on December 21, 2017, 06:47:13 pm
Aren't the proposals stored in the blockchain? I thought they needed six confirmations.

Oh, and the proposal wasn't from the real inblue  ;) Just some guy that - i think - tried impersonating him to get BBP.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on January 19, 2018, 08:25:28 pm
I wish we had some feedback of updates from the project leads  if it's normal and we should just disregard .
We were told the "WAtchdog_Expired"  takes the MN off the queue and voting . 
I had a couple of wins today though.
Well there are different levels of "down" in the core.  We are not deliberately lying :).

So there is Watchdog Expired, POSE ban, Expired with bbp_daemon not responding, watchdog_expired with bbp daemon up and watchman-down, and the mn_payment eviction, the Spork control for Watchdog enforcement, etc.

In our implementation currently, we only evict you from the payment queue if you do this:
- Leave BBP daemon off for 30 hours
- Change your IP
- Get yourself POSE banned by breaking sanc rules
- Spending the Sanc collateral

We do not ban you for:
- Leaving BBP Up while Watchdog Expires due to a watchman issue


So in a nutshell if you do pull your sanc down for more than 30 hours, rewards finally stop.

The queue is set up this way on purpose to keep people in the same positions in the queue.


Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on January 19, 2018, 08:26:46 pm
Im going to go ahead and start a new testnet thread for POL, so we can start nice and fresh.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: inblue on January 30, 2018, 01:57:54 pm
My post from BCT forum, in case it's missed:

pool is dead again, same like 2 days ago...
it is not coincidence...

I wonder if it's coincidence that a large proportion of the MN's have just just gone to WatchDog Expired states ??
Code: [Select]
ENABLED 36
NEW_START_REQUIRED 3
WATCHDOG_EXPIRED 83
PRE_ENABLED 0
UPDATE_REQUIRED 0
EXPIRED 0
https://biblepay.eu/

Those might be running 1.0.8.2.  If the node actually Stopped, their payments will stop.

Anyone who owns one of those 20 nodes, please come online and tell us what happened.

Either way you have to upgrade to 1.0.8.6 to stay up without a crash.

The problem was fixed in 1.0.8.6

On https://biblepay.eu/ we can see the version distribution which is actually protocol distribution, but as I see in GitHub commits, 70715 was introduced in 1.0.8.4? So they are probably not running 1.0.8.2 (right?), but also we don't know if they are running 1.0.8.4-5, or 1.0.8.6+. Maybe Virus can pull the version data to his site, if not, maybe protocol version can be increased with every version, if that makes sense? (I doubt it makes sense :) )

Either way, my MN went to EXPIRED state last night and it's on 1.0.8.7. When I checked it, the daemon had crashed. These are the last lines of debug.log before crashing:

Code: [Select]
2018-01-30 04:12:30 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HKq4s+Yl2VQ42mCFLy84mHKXx0Mludl3BZ+kq2Pv9KUKF3qTUIWWjPA8Yb/8Fg96MzKUfl+HntxlAsW7Di6Eizs=
2018-01-30 04:12:31 Disconnecting unauthorized peer with Network Time off by 7201.000000 seconds!^M
2018-01-30 04:14:37 Disconnecting unauthorized peer with Network Time off by 32401.000000 seconds!^M
2018-01-30 04:19:38 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=GxNu58oFKlDbVCwpq6cFO0iIAm0GUXP7qsPtVDh5oGY5ErU9GC1SmamKLoaNXr0tI1CJbqavmyU2WKGkTIz1f/I=
2018-01-30 04:19:38 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=G4TVJF+oPO5QE6+5xFPWn7w7P25i0zSCgoTSEdq/2u1ZZbwZQPjFfK+G8wz58ULVldQkUAZCUpUvqOqVEfAdrt4=
2018-01-30 04:20:40 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=GxNu58oFKlDbVCwpq6cFO0iIAm0GUXP7qsPtVDh5oGY5ErU9GC1SmamKLoaNXr0tI1CJbqavmyU2WKGkTIz1f/I=
2018-01-30 04:20:40 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=G4TVJF+oPO5QE6+5xFPWn7w7P25i0zSCgoTSEdq/2u1ZZbwZQPjFfK+G8wz58ULVldQkUAZCUpUvqOqVEfAdrt4=
2018-01-30 04:21:50 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HELzseIXLZTQQaCa2MqjUP9VpuCOlQ6zrgBrrRlmq6avSg1waraLOfbXYkYtLVs/c/T2xY6kwhuYN51+OuYOjjo=
2018-01-30 04:21:50 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HKq4s+Yl2VQ42mCFLy84mHKXx0Mludl3BZ+kq2Pv9KUKF3qTUIWWjPA8Yb/8Fg96MzKUfl+HntxlAsW7Di6Eizs=
2018-01-30 04:22:28 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HELzseIXLZTQQaCa2MqjUP9VpuCOlQ6zrgBrrRlmq6avSg1waraLOfbXYkYtLVs/c/T2xY6kwhuYN51+OuYOjjo=
2018-01-30 04:22:28 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HKq4s+Yl2VQ42mCFLy84mHKXx0Mludl3BZ+kq2Pv9KUKF3qTUIWWjPA8Yb/8Fg96MzKUfl+HntxlAsW7Di6Eizs=
2018-01-30 04:25:19 DSEG -- Sent 121 Masternode invs to peer 47696
2018-01-30 04:25:35 Disconnecting unauthorized peer with Network Time off by 14570.000000 seconds!^M
2018-01-30 04:27:14 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=GxNu58oFKlDbVCwpq6cFO0iIAm0GUXP7qsPtVDh5oGY5ErU9GC1SmamKLoaNXr0tI1CJbqavmyU2WKGkTIz1f/I=
2018-01-30 04:27:14 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=G4TVJF+oPO5QE6+5xFPWn7w7P25i0zSCgoTSEdq/2u1ZZbwZQPjFfK+G8wz58ULVldQkUAZCUpUvqOqVEfAdrt4=
2018-01-30 04:27:39 Disconnecting unauthorized peer with Network Time off by 3575.000000 seconds!^M
2018-01-30 04:28:01 Disconnecting unauthorized peer with Network Time off by 7200.000000 seconds!

There is a lot more of these errors repeated, this is just a snippet of the last ones. I hope this can help.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on January 31, 2018, 09:28:39 am
My post from BCT forum, in case it's missed:

I wonder if it's coincidence that a large proportion of the MN's have just just gone to WatchDog Expired states ??
Code: [Select]
ENABLED 36
NEW_START_REQUIRED 3
WATCHDOG_EXPIRED 83
PRE_ENABLED 0
UPDATE_REQUIRED 0
EXPIRED 0
https://biblepay.eu/


Those might be running 1.0.8.2.  If the node actually Stopped, their payments will stop.

Anyone who owns one of those 20 nodes, please come online and tell us what happened.

Either way you have to upgrade to 1.0.8.6 to stay up without a crash.

The problem was fixed in 1.0.8.6


On https://biblepay.eu/ we can see the version distribution which is actually protocol distribution, but as I see in GitHub commits, 70715 was introduced in 1.0.8.4? So they are probably not running 1.0.8.2 (right?), but also we don't know if they are running 1.0.8.4-5, or 1.0.8.6+. Maybe Virus can pull the version data to his site, if not, maybe protocol version can be increased with every version, if that makes sense? (I doubt it makes sense :) )

Either way, my MN went to EXPIRED state last night and it's on 1.0.8.7. When I checked it, the daemon had crashed. These are the last lines of debug.log before crashing:

Code: [Select]
2018-01-30 04:12:30 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HKq4s+Yl2VQ42mCFLy84mHKXx0Mludl3BZ+kq2Pv9KUKF3qTUIWWjPA8Yb/8Fg96MzKUfl+HntxlAsW7Di6Eizs=
2018-01-30 04:12:31 Disconnecting unauthorized peer with Network Time off by 7201.000000 seconds!^M
2018-01-30 04:14:37 Disconnecting unauthorized peer with Network Time off by 32401.000000 seconds!^M
2018-01-30 04:19:38 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=GxNu58oFKlDbVCwpq6cFO0iIAm0GUXP7qsPtVDh5oGY5ErU9GC1SmamKLoaNXr0tI1CJbqavmyU2WKGkTIz1f/I=
2018-01-30 04:19:38 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=G4TVJF+oPO5QE6+5xFPWn7w7P25i0zSCgoTSEdq/2u1ZZbwZQPjFfK+G8wz58ULVldQkUAZCUpUvqOqVEfAdrt4=
2018-01-30 04:20:40 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=GxNu58oFKlDbVCwpq6cFO0iIAm0GUXP7qsPtVDh5oGY5ErU9GC1SmamKLoaNXr0tI1CJbqavmyU2WKGkTIz1f/I=
2018-01-30 04:20:40 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=G4TVJF+oPO5QE6+5xFPWn7w7P25i0zSCgoTSEdq/2u1ZZbwZQPjFfK+G8wz58ULVldQkUAZCUpUvqOqVEfAdrt4=
2018-01-30 04:21:50 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HELzseIXLZTQQaCa2MqjUP9VpuCOlQ6zrgBrrRlmq6avSg1waraLOfbXYkYtLVs/c/T2xY6kwhuYN51+OuYOjjo=
2018-01-30 04:21:50 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HKq4s+Yl2VQ42mCFLy84mHKXx0Mludl3BZ+kq2Pv9KUKF3qTUIWWjPA8Yb/8Fg96MzKUfl+HntxlAsW7Di6Eizs=
2018-01-30 04:22:28 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HELzseIXLZTQQaCa2MqjUP9VpuCOlQ6zrgBrrRlmq6avSg1waraLOfbXYkYtLVs/c/T2xY6kwhuYN51+OuYOjjo=
2018-01-30 04:22:28 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1|1|1|1514729555, vchSig=HKq4s+Yl2VQ42mCFLy84mHKXx0Mludl3BZ+kq2Pv9KUKF3qTUIWWjPA8Yb/8Fg96MzKUfl+HntxlAsW7Di6Eizs=
2018-01-30 04:25:19 DSEG -- Sent 121 Masternode invs to peer 47696
2018-01-30 04:25:35 Disconnecting unauthorized peer with Network Time off by 14570.000000 seconds!^M
2018-01-30 04:27:14 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=0fb4c558fb869b2fb813246c419180a01d316684, pubkeyFromSig=b2e987cffe06e8476276f7a88287362e18e60e74, strMessage=82e9a4def54f95dbc71e1fc2ed452c87e92cc44d004026b7774379d758b9e356-0|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=GxNu58oFKlDbVCwpq6cFO0iIAm0GUXP7qsPtVDh5oGY5ErU9GC1SmamKLoaNXr0tI1CJbqavmyU2WKGkTIz1f/I=
2018-01-30 04:27:14 CGovernanceVote::IsValid -- VerifyMessage() failed, error: Keys don't match: pubkey=b2e987cffe06e8476276f7a88287362e18e60e74, pubkeyFromSig=0fb4c558fb869b2fb813246c419180a01d316684, strMessage=36472b9df495a7fabe447fa9ddafb5423af5e311166fc02b9a5a6b73e8fcfc39-1|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|1|1|1514729478, vchSig=G4TVJF+oPO5QE6+5xFPWn7w7P25i0zSCgoTSEdq/2u1ZZbwZQPjFfK+G8wz58ULVldQkUAZCUpUvqOqVEfAdrt4=
2018-01-30 04:27:39 Disconnecting unauthorized peer with Network Time off by 3575.000000 seconds!^M
2018-01-30 04:28:01 Disconnecting unauthorized peer with Network Time off by 7200.000000 seconds!

There is a lot more of these errors repeated, this is just a snippet of the last ones. I hope this can help.
Who is on our network with these clocks set off by 14 minutes?  Cmon, we are hit with every attack on a Christian Community possible huh?
It even looks like there are various nodes with varying timestamps 3575, 7200, 10000+ etc.

Anyway I cant tell what caused it to crash, but most likely whatever I merged in to fix instantsend, and the invalid vote.  The thing that is challening is Im running some sancs myself and do not mind valgrinding this, but Im not down so its a kind of elusive problem.

Blue, do you have more than 4Gb ram on your sanc?  If you do can you do me a favor?

sudo apt-get install valgrind

cd biblepay/src/qt
valgrind biblepay-qt

Run your sanc in valgrind with the defaults of valgrind set?

If you can do that next time you crash, you can send me the valgrind report which will contain the actual line number of source code that crashed it.

Thanks!

PS If your node is only 2gb RAM, its not worth it.
Btw, Ill run valgrind on my big dog also.

Regarding the protocol version, we can only up that when a large change occurs, but getinfos "version" is a hybrid of the software version and the protocol version, so Virus may be able to use that.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: inblue on January 31, 2018, 01:28:36 pm
Who is on our network with these clocks set off by 14 minutes?  Cmon, we are hit with every attack on a Christian Community possible huh?
It even looks like there are various nodes with varying timestamps 3575, 7200, 10000+ etc.

Anyway I cant tell what caused it to crash, but most likely whatever I merged in to fix instantsend, and the invalid vote.  The thing that is challening is Im running some sancs myself and do not mind valgrinding this, but Im not down so its a kind of elusive problem.

Blue, do you have more than 4Gb ram on your sanc?  If you do can you do me a favor?

sudo apt-get install valgrind

cd biblepay/src/qt
valgrind biblepay-qt

Run your sanc in valgrind with the defaults of valgrind set?

If you can do that next time you crash, you can send me the valgrind report which will contain the actual line number of source code that crashed it.

Thanks!

PS If your node is only 2gb RAM, its not worth it.
Btw, Ill run valgrind on my big dog also.

Regarding the protocol version, we can only up that when a large change occurs, but getinfos "version" is a hybrid of the software version and the protocol version, so Virus may be able to use that.

My MN is actually on a 512 MB RAM instance. :) And I don't have biblepay-qt nor the dependencies for it, because I installed only CLI. Is there any other way to record crash logs?

Also, now that you've mentioned it, those clock delays in seconds are almost exactly: 1 hour, 2 hours, 4 hours and 9 hours. Hmm, what could be the meaning of that, or what are they trying to achieve with that?
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: Rob Andrews on February 02, 2018, 06:53:45 am
My MN is actually on a 512 MB RAM instance. :) And I don't have biblepay-qt nor the dependencies for it, because I installed only CLI. Is there any other way to record crash logs?

Also, now that you've mentioned it, those clock delays in seconds are almost exactly: 1 hour, 2 hours, 4 hours and 9 hours. Hmm, what could be the meaning of that, or what are they trying to achieve with that?
No other way to achieve crash logs- even if you ran with all the switches (instantsend=true, debugmaster=true, masternode=true) etc, would not guarantee that line that caused the segfault would be in the log.  The only thing in the log is what we write to the log.  However valgrind intakes its pointer to the line of source before executing each line, so it is really the only effective way.   

The time attack could be either a) to try to connect and slip a proof-of-work block in that has been pre-hashed on a supercomputer, (because they have the luxury of doing it over time), or b) to try to offset the GetNetworkTime() function - to adulterate it, to bring us as a network forward or back so they can inject a sttring of blocks to make money on their own fork.  We have NTP protection for past & future, of up to 10 minutes, but it relies on the network average time being correct, thats why we hang up on nodes who are off by more than 300 seconds.

Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: MIP on March 02, 2018, 02:41:05 am
Hi, I set up a MN on a Vultr instance (all exactly the same as in the instructions in http://wiki.biblepay.org/Create_Sanctuary_2) and everything went apparently fine.

However

$ ./biblepay-cli masternode status
{
  "vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
  "service": "[::]:0",
  "status": "Not capable masternode: Masternode must accept connections from outside. Make sure listen configuration option is not overwritten by some another parameter."
}

I set up the firewall with rules as in the instructions, and did not create another extra firewall group at Vultr dashboard.

Any ideas for troubleshooting? Thank you


EDIT: just in case:

$  ./biblepay-cli mnsync status
{
  "AssetID": 999,
  "AssetName": "MASTERNODE_SYNC_FINISHED",
  "Attempt": 0,
  "IsBlockchainSynced": true,
  "IsMasternodeListSynced": true,
  "IsWinnersListSynced": true,
  "IsSynced": true,
  "IsFailed": false,
  "MasternodesEnabled": true
}

EDIT 2: ok it was my fault, for some reason I had "listen=0" in conf.

Now it says "Not capable masternode: Masternode not in masternode list"

I understand that it's fine now and I have to wait a few hours to get it listed, don't I?

thanks again!

EDIT 3: now it says "Masternode successfully created", but controller wallet still says "PRE_ENABLED". I will wait few hours more and see...
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on March 02, 2018, 05:22:02 am
Haha, great to see that you've solved your own problems ;D

Yes, I think the MN will be enabled soon.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: MIP on March 02, 2018, 05:24:36 am
Haha, great to see that you've solved your own problems ;D

Yes, I think the MN will be enabled soon.

There is always a first time for everything my friend.
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on March 02, 2018, 06:22:38 am
There is always a first time for everything my friend.

Very true, I learn every day :)
Title: Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
Post by: jaapgvk on April 07, 2018, 04:18:03 am
Is there  a reason the MN payments have plummeted?  I understand there is a variation based on time to solve the block, but when PoDC came about, the payments and timing issues seemed solved for the most part.  Yet today, the MN payments seem more than 10% below what the average had been and are trending towards to an under 4000 / payment level when before they were trending to a just under 5000 / payment level.  There is not a lot of data to look at yet, so maybe I'm getting ahead of things, but the root question is has anything been changed in the last two or three days that would impact this or am I just hitting a run of poor luck?

https://bitcointalk.org/index.php?topic=2388064.msg34061945#msg34061945

Don't know if this is a definitive answer, but it's what I think is the case.