Messages

3691

Archived Proposals / Re: Unquestionably Horrible Proposal

« on: December 19, 2017, 07:27:34 AM »

Unfortunately get 'Unable to locate Proposal'  when I click it in the pool and try to copy the ID. I'm still getting the hang of this, so I might be doing something wrong...

It takes the system a while to put the proposal in the chain- it has to make a hex proposal, insert it, wait for confirm, send collateral, wait 6 blocks, then it finally sets up a "Submitted" datetimestamp on it, then you can finally vote on it  .

3692

Archived Proposals / Unquestionably Horrible Proposal

« on: December 19, 2017, 06:31:57 AM »

I have the dumbest idea ever, but would like to receive 1000 BBP for it.

Lets branch BiblePay into a version for non-believers and launch it on April Fools day 2018?

Thanks.

Budget Source: PR Budget

Amount: 1000 BBP


I think this move will be good for PR.

3693

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

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

3694

Archived Proposals / Re: Togo Sanctuary Guide and Testing

« on: December 15, 2017, 09:32:59 PM »

Wow, what a great deal, Ill be voting yes for this in the morning.

EDIT:


21:57:58

gobject vote-many e6ff30af51064a281752a6b5fdc03bd9d2fa457af89e1a0021a93661a726c96e funding yes


21:57:58

{
  "overall": "Voted successfully 3 time(s) and failed 0 time(s).",
  "detail": {
    "vultr4": {
      "result": "success"
    },
    "vultr5": {
      "result": "success"
    },
    "vultr8": {
      "result": "success"
    }
  }
}

3695

Archived Proposals / Re: First Prod Test Proposal

« on: December 15, 2017, 02:40:56 PM »

Rob , how voting is supposed to work .  What do I do to approve or disapprove it ?


BTW,   I am an experienced SQL dev and admin . worked for big banks and telecoms.  If you think I can be of any use for SQL related stuff pls let me know or PM

Once the Proposal has 6 confirms it should be in the chain (youll see Proposal Submitted Time populate), then you can right click on the proposal and click copy vote for proposal.  Then copy that command to the clipboard and vote for it from your sanctuary.

10-4 On the SQL, that might work someday when I am ready for vacation maybe you can be my backup. 

EDIT: I just took a look at the operations behind the scenes; this proposals escrow only has 2 confirms out of 6, so that is why its not "Submitted" yet, so far there are no issues with the system in prod, we just have to wait longer.  We'll see how Togos goes also.

3696

Archived Proposals / First Prod Test Proposal

« on: December 15, 2017, 01:43:35 PM »

This is a test proposal. 

Im asking 250 BBP for fixing an SQL query deadlock in the pool.

EDIT: Please charge this 250 BBP to IT.

3697

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

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

3698

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

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

3699

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

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

3700

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

« 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

3701

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

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

3702

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

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

3703

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

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

3704

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

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

3705

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

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