February 2021 Testnet Thread (Tribulation)

Yeah i understand that you guys have alot on ur plates..
It was just a thought i had, about raveOS and 2miners.

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

Sadly i had already  reindexed Rob when i saw your message there.

I see in console now that im at block  62587.
I will check log if i see any errors or something.

Also i checked mail now and i see that i got a duplicate in inbox.

Perhaps it was because i reindexed because i didnt see any duplicates before i reindex.

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 see now in mailbox a mail from you called : #11002 test mensage Earlz CC Rob
I just got it a few minutes ago but date stamp on it says: 2021-02-01  15:57
In my case i think it might have been like Rob said, just wasnt mining because i cant see any error in my log.

I see now in mailbox a mail from you called : #11002 test mensage Earlz CC Rob
I just got it a few minutes ago but date stamp on it says: 2021-02-01  15:57
In my case i think it might have been like Rob said, just wasnt mining because i cant see any error in my log.

I also received mail #11002 and replied to both of you.
No duplicates so far.

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

Have to excuse my many posts but i cant "edit" so.

heres my output from getblockhash command:

Code: [Select]

21:22:27

getblockhash 62580


21:22:27

b644524f9572c14a74eae79ffa14a160164974c43e3a9b7c04fc69a898a93b53


Also i checked mail now and i see that i got a duplicate in inbox.

Perhaps it was because i reindexed because i didnt see any duplicates before i reindex.

Thanks man, well I think the e-mail system is "close" but there is probably at least one more bug.  Today, I added support for sending to "all" and I have it disregarding corrupt emails (like with empty Subject for example), and, I am very close to releasing the "encrypted email" feature.

Let me do this, let me take a look at the uuid->hash algorithm we are using and ensure that it prevents duplicates.  It might be that the Pop3 LIST is slightly different than our hash, Ill check.
(The reindexing was not it because the hash ends up being the same).  I think its something to do with the pop3-list possibly.

I think you guys can stop testing e-mails until the next version now.

Thanks.

Have to excuse my many posts but i cant "edit" so.

heres my output from getblockhash command:

Code: [Select]

21:22:27

getblockhash 62580


21:22:27

b644524f9572c14a74eae79ffa14a160164974c43e3a9b7c04fc69a898a93b53


Yes you and I and my sancs agree with you now.

As long as you guys dont have an "ERROR" in the log from syncing, we are still on the same chain.
Its possible you both came on and didnt have enough peers, mined a block and created a false chain.

So far I havent found any broken fork logic in testnet at all.  Please let me know if either of you fork.

I also received mail #11002 and replied to both of you.
No duplicates so far.

Ok great, I will release the next version of e-mail asap after I look into duplicates.

Could you please test BiblePay University?

Have to excuse my many posts but i cant "edit" so.

heres my output from getblockhash command:

Code: [Select]

21:22:27

getblockhash 62580


21:22:27

b644524f9572c14a74eae79ffa14a160164974c43e3a9b7c04fc69a898a93b53


I think you should be able to edit though, you are a full member, question, does your button array have the "Modify" button on there?

If not we can do something about this.

I think you should be able to edit though, you are a full member, question, does your button array have the "Modify" button on there?

If not we can do something about this.

I do not see any modify button or edit message button or how to say.
Only the  quote button, report to moderator and my own ip section i see on already posted messages.

Sweet it works now!

I do not see any modify button or edit message button or how to say.
Only the  quote button, report to moderator and my own ip section i see on already posted messages.

Very interesting; yeah, we are using the basic default SMF member group permissions here so it was not intentional.

I went ahead and modified Full Member, Developer, Sr Member and above to have Modify Post, Start new Poll, and some other permissions.

Please see if it works now?

Very interesting; yeah, we are using the basic default SMF member group permissions here so it was not intentional.

I went ahead and modified Full Member, Developer, Sr Member and above to have Modify Post, Start new Poll, and some other permissions.

Please see if it works now?

Yeah i see it now, sweet.
Edit works.

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.

Thank you,  I have several old backups, so far all of them that i put in place of the wallet.dat file i get the same error message. I tried using python, but so far not having much luck. The salvage wallet button under wallet repair is always unselectable. What about importwallet cmd in the console? Im not sure what to put after it I have tried copying the backup wallet file and I get this message:
18:25:58

importwallet file:///C:/Users/fishe/OneDrive/Documents/biblepay back up.dat


18:25:58

importwallet "filename"

Imports keys from a wallet dump file (see dumpwallet).

Arguments:
1. "filename"    (string, required) The wallet file

Examples:

Dump the wallet
> biblepay-cli dumpwallet "test"

Import the wallet
> biblepay-cli importwallet "test"

Import using the json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "importwallet", "params": ["test"] }' -H 'content-type: text/plain;' http://127.0.0.1:9998/
 (code -1)
Any help appreciated. Thanks

Thank you,  I have several old backups, so far all of them that i put in place of the wallet.dat file i get the same error message. I tried using python, but so far not having much luck. The salvage wallet button under wallet repair is always unselectable. What about importwallet cmd in the console? Im not sure what to put after it I have tried copying the backup wallet file and I get this message:
18:25:58

importwallet file:///C:/Users/fishe/OneDrive/Documents/biblepay back up.dat


18:25:58

importwallet "filename"

Imports keys from a wallet dump file (see dumpwallet).

Arguments:
1. "filename"    (string, required) The wallet file

Examples:

Dump the wallet
> biblepay-cli dumpwallet "test"

Import the wallet
> biblepay-cli importwallet "test"

Import using the json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "importwallet", "params": ["test"] }' -H 'content-type: text/plain;' http://127.0.0.1:9998/
 (code -1)
Any help appreciated. Thanks

1) Do you happen to have any backups in the ~/.biblepay/backups folder ?  There is usually one made on every successful boot.  They are called wallet.dat+mmddyyyy
2) I think the salvagewallet button is broken - Ive seen that problem on my end (inherited from dash).  But the command line option works (-salvagewallet).  However if the wallet already tried it on boot (salvage failed) that wont work at this point on that particular wallet.dat.
3) Yes the dumpwallet and importwallet work- but to use importwallet, you have to have a text file that was written in the format of dumpwallet first.  If you can get dumpwallet 'filename' to write your keys to a text file, then you can open the text file, and see if anything is in there.  If it is, you can either import the keys with 'importprivkey privkey' or the importwallet command.   (I do recommend #1 first however because if some sector is corrupted in the file, a working wallet.dat backup is better -- unless you know you added a privkey for example later than the backup date -- but most privkeys are created when the wallet file is created).
4) How much bbp was in there roughly, so I know which option to recommend next?
5) I can help with python but let me know about these 4 first.

Yeah i see it now, sweet.
Edit works.

Great to hear.
So I did find the issue with the duplicates in email:  Turns out we need to keep a little database of "read" email hash codes, because the mail client only 'remembers' which hashes it pulled down for a limited time.  So that is coming next along with encrypted emails and emails to all.  Ill try to release this in the next few hours.

Btw, I just went through some heavy duty drama with Amazon web hosting (I actually use vultr), but AWS for my rapture videos on foundation.biblepay.org.  Someone from another Country copied the God URLs and exploited them, and ran up a high bandwidth bill (they downloaded the videos over 1 million times, I think around 4gb per download) and the bill was over $2,900.  I called them to ask for a 75% discount with my defense being that my users did not benefit from this and it appears to be hacking activity.  They are now looking into it.  What an uphill battle.

Anyway, on a separate note, we still have BiblePay-TV to test also (although, Im removing 'mining' from it because it doesnt really fit properly in our infrastructure, so ignore that menu option).   EDIT: I just removed 'mining' from BiblePay TV.

Does anyone have Roku here?  If so you can also test BiblePay TV.