Messages

541

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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?

542

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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).

543

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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"
    }
  }
}


544

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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

545

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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?

546

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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...

547

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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.'

548

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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 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"
    }
  }
}


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.

549

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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).

550

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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...

551

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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?

552

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: October 15, 2017, 03:44:31 AM »

I've had a busy week, but I think I've finally got a masternode working 

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:

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:

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 
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...

553

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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

554

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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.

555

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« 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