February 2021 Testnet Thread (Tribulation)

There has to be a problem for America users. I have been trying for days to download the wallet from biblepay.org and most of the time getting this message: Forbidden
You don't have permission to access this resource.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

I was able to get it downloaded right now no problem by switching my vpn to Europe. Before today i had been trying  to download using linux and windows with and without vpn (set in usa)  using chrome, firefox, and opera browsers with no luck.

Next question: with the new client downloaded i replaced the wallet.dat file with my backup wallet file. and I got the error: wallet.dat file corrupt, salvage failed. Ideas?

Next question: with the new client downloaded i replaced the wallet.dat file with my backup wallet file. and I got the error: wallet.dat file corrupt, salvage failed. Ideas?

If the wallet.dat is corrupt and the salvage failed, the best advice I have is to go back to a prior wallet.dat before the corrupt file.  (Its always good to have a backup).

If you don't have another wallet.dat you could try downloading the bitcoin python wallet utilities and look for the one that manually allows extraction of the private keys from the file (as long as they are not encrypted) to a text file and manually import the private keys into a new wallet.

Ill comment on the download access later as soon as time permits.

There has to be a problem for America users. I have been trying for days to download the wallet from biblepay.org and most of the time getting this message: Forbidden
You don't have permission to access this resource.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

I was able to get it downloaded right now no problem by switching my vpn to Europe. Before today i had been trying  to download using linux and windows with and without vpn (set in usa)  using chrome, firefox, and opera browsers with no luck.

Hmm, I believe I see the problem with the 403 error:
Our server had all of California blocked.  I believe this is because of the incident we had a few months ago.

This issue should be resolved now. 

Hello Rob.
This is abit off topic but i was thinking if it would be possible to add https://2miners.com/  their monero mining pool as a option for the random x mining.
Why im thinking this is because they have this partnership with a mining OS called: RaveOS and then its no cost to use the os if you are using 2miners pools.

This would help out alot for people who have alot of mixed rigs, gpus and cpus.   Currently i saw RaveOS dont support cpu mining but they are working on it. 
Anyways just some thoughts i had.

Hmm, I believe I see the problem with the 403 error:
Our server had all of California blocked.  I believe this is because of the incident we had a few months ago.

This issue should be resolved now.

We had in telegram some portuguese speaking user saying the same. But I don't know if he was from Portugal (Europe) or Brazil (South America).

1.5.3.9 - Mandatory Upgrade for TestNet

- Increment e-mail protocol version to 2 (to prevent duplicate e-mails and empty From and To lines)
- Add rpc command for new user to cash in a newbie reward
- Add multiple verse support to memorize scriptures



Earlz pointed out that the e-mails are coming through more than once.  I believe this is due to a prior bug in v1 emails.  Anyway, now we have moved up to v2 emails (this fixes the blank header issue also, and theoreticlly fixes the duplicate issue).

Will everyone please upgrade to 1.5.3.9+ and lets delete all of our e-mails in our test inbox and start over.  Then once upgraded please send me an email with #11000 or higher and we will reply to each other.. And please see if we have eliminated any duplicates going forward!

Thanks!

I sent you a and Earlz an email yesterday, with #11000 in subject.
However I didn't receive any from you. It now happens to me that my client is stuck at block 61913. It has some peers but it doesn't seem to be enough to make progress up to the latest block

This is what I see from here

Code: [Select]

09:57:55

getpeerinfo


09:57:55

[
  {
    "id": 0,
    "addr": "149.28.249.117:40001",
    "addrlocal": "213.77.168.185:58250",
    "services": "0000000000000005",
    "relaytxes": true,
    "lastsend": 1612288650,
    "lastrecv": 1612288650,
    "bytessent": 5740,
    "bytesrecv": 3089,
    "conntime": 1612287683,
    "timeoffset": -3,
    "pingtime": 0.549419,
    "minping": 0.308941,
    "version": 70762,
    "subver": "/BiblePay Core:1.5.3.9/",
    "inbound": false,
    "addnode": false,
    "startingheight": 62575,
    "banscore": 0,
    "synced_headers": 62575,
    "synced_blocks": 61724,
    "inflight": [
    ],
    "whitelisted": false,
    "bytessent_per_msg": {
      "addr": 55,
      "emailrequest": 3864,
      "getaddr": 24,
      "getheaders": 925,
      "ping": 288,
      "pong": 288,
      "qsendrecsigs": 25,
      "sendcmpct": 33,
      "senddsq": 25,
      "sendheaders": 24,
      "verack": 24,
      "version": 165
    },
    "bytesrecv_per_msg": {
      "*other*": 25,
      "addr": 1640,
      "headers": 425,
      "mnauth": 152,
      "ping": 288,
      "pong": 288,
      "sendcmpct": 33,
      "senddsq": 25,
      "sendheaders": 24,
      "verack": 24,
      "version": 165
    }
  },
  {
    "id": 31,
    "addr": "162.248.163.231:40001",
    "addrlocal": "213.77.168.185:58691",
    "services": "0000000000000005",
    "relaytxes": true,
    "lastsend": 1612288641,
    "lastrecv": 1612288642,
    "bytessent": 4367,
    "bytesrecv": 2064,
    "conntime": 1612288521,
    "timeoffset": -2,
    "pingtime": 0.282603,
    "minping": 0.262398,
    "version": 70762,
    "subver": "/BiblePay Core:1.5.3.6/",
    "inbound": false,
    "addnode": false,
    "startingheight": 62575,
    "banscore": 0,
    "synced_headers": -1,
    "synced_blocks": -1,
    "inflight": [
    ],
    "whitelisted": false,
    "bytessent_per_msg": {
      "addr": 55,
      "emailrequest": 3864,
      "getaddr": 24,
      "ping": 64,
      "pong": 64,
      "qsendrecsigs": 25,
      "sendcmpct": 33,
      "senddsq": 25,
      "sendheaders": 24,
      "verack": 24,
      "version": 165
    },
    "bytesrecv_per_msg": {
      "*other*": 25,
      "addr": 1640,
      "ping": 64,
      "pong": 64,
      "sendcmpct": 33,
      "senddsq": 25,
      "sendheaders": 24,
      "verack": 24,
      "version": 165
    }
  }
]


I sent you a and Earlz an email yesterday, with #11000 in subject.
However I didn't receive any from you. It now happens to me that my client is stuck at block 61913. It has some peers but it doesn't seem to be enough to make progress up to the latest block

This is what I see from here

I have not received any mail from you MIP only i have gotten 2 mails from Rob.
Also  i belive i was stuck aswell, currently trying reindex to see if i can get client to launch and sync up.

I have not received any mail from you MIP only i have gotten 2 mails from Rob.
Also  i belive i was stuck aswell, currently trying reindex to see if i can get client to launch and sync up.

Those emails showed as "delivered' in the mail client, so this is strange.
Not receiving from you is expected as the client is not fully synced yet.
Which block are you stuck in?

I have not received any mail from you MIP only i have gotten 2 mails from Rob.
Also  i belive i was stuck aswell, currently trying reindex to see if i can get client to launch and sync up.

I'm not sure we were stuck - I believe no one was mining.

After I started mining, the chain advanced.  If we were stuck, please analyze the log for "ERROR"; as we definitely need that information to fix any issue.
Please do not reindex until we solve if there was a problem.

MIP:  I didn't send you one cause I was waiting for you to send it, although I sent one today to you and another one to Earlz & you, so I think two were sent.

So I have 4 connections and I did not resync the chain, I only started mining, so will you guys please verify this hash matches:


13:04:06

getblockhash 62580


13:04:06

b644524f9572c14a74eae79ffa14a160164974c43e3a9b7c04fc69a898a93b53

Hello Rob.
This is abit off topic but i was thinking if it would be possible to add https://2miners.com/  their monero mining pool as a option for the random x mining.
Why im thinking this is because they have this partnership with a mining OS called: RaveOS and then its no cost to use the os if you are using 2miners pools.

This would help out alot for people who have alot of mixed rigs, gpus and cpus.   Currently i saw RaveOS dont support cpu mining but they are working on it. 
Anyways just some thoughts i had.

Thanks, I'm checking out raveos and 2miners.

Just to clarify the big challenge in this space, there are a lot of things backed up that are important, that I'm trying to get to, for example, the state of the dapps (dash dapps), for example MIP sent me this article:
https://hackernoon.com/building-dapps-on-dash-an-interview-with-readme-ay3a342g
Im trying to get to the point where we can make a sample dapp and see if we can leverage any of Dashs existing infrastructure for decentralizing more of our features.
And also, Ive been trying to get to a rather important one:  Leveraging the op_return (and dash financial transaction) tx_type to send some of our blockchain messages.
The other big one is re-basing our codebase to the latest (around June).

So I have 4 connections and I did not resync the chain, I only started mining, so will you guys please verify this hash matches:


13:04:06

getblockhash 62580


13:04:06

b644524f9572c14a74eae79ffa14a160164974c43e3a9b7c04fc69a898a93b53

I am still at the same block, I will reindex or erase chain and see.

Code: [Select]

11:14:01

getinfo


11:14:01

{
  "version": 1050309,
  "protocolversion": 70762,
  "walletversion": 61000,
  "balance": 24729841.81530737,
  "privatesend_balance": 0.00000000,
  "blocks": 61913,
  "timeoffset": -1,
  "connections": 4,
  "proxy": "",
  "difficulty": 5.942651004834048e-06,
  "testnet": true,
  "keypoololdest": 1597656144,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": ""
}

Regarding the emails, they show as delivered so it is strange you didn't receive them (see attached image)

I am still at the same block, I will reindex or erase chain and see.

Code: [Select]

11:14:01

getinfo


11:14:01

{
  "version": 1050309,
  "protocolversion": 70762,
  "walletversion": 61000,
  "balance": 24729841.81530737,
  "privatesend_balance": 0.00000000,
  "blocks": 61913,
  "timeoffset": -1,
  "connections": 4,
  "proxy": "",
  "difficulty": 5.942651004834048e-06,
  "testnet": true,
  "keypoololdest": 1597656144,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": ""
}

Regarding the emails, they show as delivered so it is strange you didn't receive them (see attached image)

Like I mentioned in the post just above (2 posts ago) please do not resync the chain, lets try to find the problem.

So I have 4 connections and I did not resync the chain, I only started mining, so will you guys please verify this hash matches:


13:04:06

getblockhash 62580


13:04:06

b644524f9572c14a74eae79ffa14a160164974c43e3a9b7c04fc69a898a93b53

the -reindex seemed to do the magic and now it seems I am on block 62580.