Bible Pay

Read 47008 times

  • Rob Andrews
  • Administrator

    • 1392


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #105 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.



  • jaapgvk
  • Hero Member

    • 590


    • 26
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #106 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"
    }
  }
}



  • Rob Andrews
  • Administrator

    • 1392


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #107 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 :)

« Last Edit: October 16, 2017, 11:28:21 pm by admin »


  • jaapgvk
  • Hero Member

    • 590


    • 26
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #108 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).


  • Rob Andrews
  • Administrator

    • 1392


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #109 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).



  • jaapgvk
  • Hero Member

    • 590


    • 26
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #110 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?


  • Rob Andrews
  • Administrator

    • 1392


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #111 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.


« Last Edit: October 18, 2017, 10:41:57 am by admin »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #112 on: October 21, 2017, 03:42:11 pm »
You should raise the cost of proposals to 5000 but have it so that if it passes, that fee is refunded.


  • Rob Andrews
  • Administrator

    • 1392


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #113 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. 


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #114 on: October 23, 2017, 11:14:29 am »
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.


  • klondike
  • Full Member

    • 175


    • -13
    • October 10, 2017, 09:00:24 am
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #115 on: October 24, 2017, 10:03:37 am »
hello, after restarted win testnet wallet i get this error



im stuck on this error and dont know where is problem


thanks for your help


  • jaapgvk
  • Hero Member

    • 590


    • 26
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #116 on: October 24, 2017, 12:22:44 pm »
hello, after restarted win testnet wallet i get this error



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


  • Rob Andrews
  • Administrator

    • 1392


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #117 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 :)



  • Rob Andrews
  • Administrator

    • 1392


    • 25
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #118 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?



  • klondike
  • Full Member

    • 175


    • -13
    • October 10, 2017, 09:00:24 am
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #119 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?

« Last Edit: October 25, 2017, 03:15:59 am by klondike »