Bible Pay

Recent Posts

Pages: 1 2 [3] 4 5 6 7 8 9 10
21
General Support / Re: What are the correct PoG setting for foundation donation amount?
« Last post by sunk818 on September 26, 2019, 05:11:35 pm »
If you give me wiki edit access again, I can make the change and remove amount.
23
General Support / What are the correct PoG setting for foundation donation amount?
« Last post by sunk818 on September 26, 2019, 04:54:00 pm »

Hello, some users are asking me what the correct biblepay.conf setting is for PoG foundation amount.


On one page: https://wiki.biblepay.org/Quick_Start - it says to use pog_foundationdonationamount=nnnn


On this page: https://wiki.biblepay.org/Getting_Started_with_Evolution - it says to pog_foundationdonation


I am not sure if this is the correct place to look, but this seems to suggest using the line without amount
https://github.com/biblepay/biblepay-evolution/blob/master/src/smartcontract-client.cpp#L357


Can you clarify?
24
Thank you. It was not working with ip:port but adding port=8080 as an extra line in the config works. Now shows ready.

Syncing was not the issue. I accidentally deleted the entire .biblepayevolution folder but I learnt my lesson from before and restored from a backup wallet.dat. So all 3 sancs synced and ready.

Thats great!  I'll be back after we release this mandatory in mainnet.

25
Active Discussions / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Last post by oncoapop on September 25, 2019, 06:06:04 pm »
1) It appears your remote sanc node is not listening on 8080 (I tried to telnet to it).
Try to add "port=8080" to your sanctuary config file and restart it.

2) Were you able to resolve not being synced yesterday, was it a non issue?

Thank you. It was not working with ip:port but adding port=8080 as an extra line in the config works. Now shows ready.

Syncing was not the issue. I accidentally deleted the entire .biblepayevolution folder but I learnt my lesson from before and restored from a backup wallet.dat. So all 3 sancs synced and ready.
26
Update to non standard port not working

The sanc appears enabled on the list but is unable to connect to the non standard port.

 >sanc status
Code: [Select]
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "104.167.116.179:8080",
  "proTxHash": "71ac8f0a0b11a7070b4aa2e1862c19a8c5d5106bc5172502ebe8ce87772afc5d",
  "collateralHash": "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583",
  "collateralIndex": 1,
  "dmnState": {
    "service": "104.167.116.179:8080",
    "registeredHeight": 6092,
    "lastPaidHeight": 6097,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "yQkfqAeFpZzwHmpXti7avavNAu6etwCjAn",
    "votingAddress": "yQkfqAeFpZzwHmpXti7avavNAu6etwCjAn",
    "payoutAddress": "yTwJA2VCYQWpWXH8HS7UvEpqRE3Aj5ciUV",
    "pubKeyOperator": "139234c6a2d2f2f449fe5b25006fef684a5be440372756d903f1c793da49812202933c13a8d750ebeb270ea96b62480d"
  },
  "state": "ERROR",
  "status": "Error. Could not connect to 104.167.116.179:8080"
}

>sudo ufw status
Code: [Select]
Status: active

To                         Action      From
--                         ------      ----
22/tcp                     LIMIT       Anywhere                 
8080/tcp                   ALLOW       Anywhere                 
40000/tcp                  ALLOW       Anywhere                 
9998/tcp                   ALLOW       Anywhere                 
19998/tcp                  ALLOW       Anywhere                 
40001/tcp                  ALLOW       Anywhere                 
22/tcp (v6)                LIMIT       Anywhere (v6)             
8080/tcp (v6)              ALLOW       Anywhere (v6)             
40000/tcp (v6)             ALLOW       Anywhere (v6)             
9998/tcp (v6)              ALLOW       Anywhere (v6)             
19998/tcp (v6)             ALLOW       Anywhere (v6)             
40001/tcp (v6)             ALLOW       Anywhere (v6) 

1) It appears your remote sanc node is not listening on 8080 (I tried to telnet to it).
Try to add "port=8080" to your sanctuary config file and restart it.

2) Were you able to resolve not being synced yesterday, was it a non issue?

27
Active Discussions / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Last post by oncoapop on September 25, 2019, 04:40:01 pm »
Update to non standard port not working

The sanc appears enabled on the list but is unable to connect to the non standard port.

 >sanc status
Code: [Select]
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "104.167.116.179:8080",
  "proTxHash": "71ac8f0a0b11a7070b4aa2e1862c19a8c5d5106bc5172502ebe8ce87772afc5d",
  "collateralHash": "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583",
  "collateralIndex": 1,
  "dmnState": {
    "service": "104.167.116.179:8080",
    "registeredHeight": 6092,
    "lastPaidHeight": 6097,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "yQkfqAeFpZzwHmpXti7avavNAu6etwCjAn",
    "votingAddress": "yQkfqAeFpZzwHmpXti7avavNAu6etwCjAn",
    "payoutAddress": "yTwJA2VCYQWpWXH8HS7UvEpqRE3Aj5ciUV",
    "pubKeyOperator": "139234c6a2d2f2f449fe5b25006fef684a5be440372756d903f1c793da49812202933c13a8d750ebeb270ea96b62480d"
  },
  "state": "ERROR",
  "status": "Error. Could not connect to 104.167.116.179:8080"
}

>sudo ufw status
Code: [Select]
Status: active

To                         Action      From
--                         ------      ----
22/tcp                     LIMIT       Anywhere                 
8080/tcp                   ALLOW       Anywhere                 
40000/tcp                  ALLOW       Anywhere                 
9998/tcp                   ALLOW       Anywhere                 
19998/tcp                  ALLOW       Anywhere                 
40001/tcp                  ALLOW       Anywhere                 
22/tcp (v6)                LIMIT       Anywhere (v6)             
8080/tcp (v6)              ALLOW       Anywhere (v6)             
40000/tcp (v6)             ALLOW       Anywhere (v6)             
9998/tcp (v6)              ALLOW       Anywhere (v6)             
19998/tcp (v6)             ALLOW       Anywhere (v6)             
40001/tcp (v6)             ALLOW       Anywhere (v6) 
28
Production Proposals / Re: October payment for Kairos Childrens Fund
« Last post by AndrewScribner on September 24, 2019, 07:27:41 pm »
I submitted the proposal very late. Hope that it will be voted for :)
29

Will instructions differ for someone who creates a sanctuary after having bought 4.55M from an exchange and want to self-host?


The upgradesanc only applies if a 4.55M sanctuary already exists but upgrading to a newer version?


I want to write a sanctuary set up guide but it is not clear what the sanctuary creation options are.


Well, its not that the instructions change based on receiving the funds, its more of which route you want to go when you create the deterministic sanc:

Route A)  If you follow the Dash instructions, they are a full page and pretty complicated. 

Route B)  We ask you to create the sanctuary the legacy way, and that allows you to implement the first phase of the deterministic sanc.  Then we ask you to run the upgradesanc command to finish it. 

One other thing to consider is Apollon is actually adding a new twist to this - they are having us add a couple RPC commands for them - one that will allow them to generate the bls privkey first and give it to the user- so there is a great chance we can make a special command that is different than upgradesanc soon, once I hear back from them.

So best bet is to wait for this info.

30
Active Discussions / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Last post by sunk818 on September 24, 2019, 04:40:54 pm »

In my case, I used our upgradesanc command.  Heres how I created a deterministic using the legacy with upgrade method:
- Send 4,500,001 to myself using QT wallet
- Type masternode outputs - copy the TXID and ordinal
- Edit the controllers testnet3/masternode.conf file
- Past IP:Port MNP txid ordinal (in the file)
- Type 'upgradesanc sancname 0' .  Verify this will work.
- Type 'upgradesanc sancname 1'.  Copy the masternode bls priv key to the Sanc "biblepay.conf" file.  Also ensure the sanc has masternode=1 in it.
- Reboot the sanc so it uses the bls priv key.


Will instructions differ for someone who creates a sanctuary after having bought 4.55M from an exchange and want to self-host?


The upgradesanc only applies if a 4.55M sanctuary already exists but upgrading to a newer version?


I want to write a sanctuary set up guide but it is not clear what the sanctuary creation options are.
Pages: 1 2 [3] 4 5 6 7 8 9 10