Messages

4081

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

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

4082

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

« 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

4083

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

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

4084

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

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

4085

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

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

4086

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

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

4087

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

« 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

4088

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

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

4089

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

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

4090

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

« on: October 15, 2017, 06:16:37 PM »

you want to run masternode without windows support?  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.

4091

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

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

4092

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

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

4093

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

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

4094

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

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

4095

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

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