Bible Pay

Read 3614 times

Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #90 on: September 17, 2021, 06:01:52 PM »
Also, plz try adding a prayer or a town hall in testnet; lets see that your User Name is on those things?

It is showing on the video and I added a test prayer and it also shows there.


  • AndrewScribner
  • Developer

    • 74


    • 7
    • June 21, 2018, 07:17:43 PM
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #91 on: September 20, 2021, 06:19:29 AM »
When trying to create a proposal, I got this error: Address is not valid for this chain.
« Last Edit: September 20, 2021, 06:29:37 AM by AndrewScribner »


  • AndrewScribner
  • Developer

    • 74


    • 7
    • June 21, 2018, 07:17:43 PM
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #92 on: September 20, 2021, 06:28:53 AM »
Rob, this is really odd. I can't seem to log into the unchained. I am not sure if it's me or something changed.


  • earlzmoade
  • Developer

    • 284


    • 46
    • August 02, 2018, 03:22:01 AM
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #93 on: September 21, 2021, 03:46:39 AM »
Rob, this is really odd. I can't seem to log into the unchained. I am not sure if it's me or something changed.


Hello Andrew.
I saw a few pages back Rob posted:

Btw everyone, we just had a major upgrade to Unchained, so please recreate your accounts; please re-test sending biblepay back and forth etc.

So we have to create new accounts or perhaps use the seedwords.
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • Rob Andrews
  • Administrator

    • 3850


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #94 on: September 21, 2021, 08:23:52 AM »

Hello Andrew.
I saw a few pages back Rob posted:

Btw everyone, we just had a major upgrade to Unchained, so please recreate your accounts; please re-test sending biblepay back and forth etc.

So we have to create new accounts or perhaps use the seedwords.
Yeah thanks for stepping in and helping Earlz, yes Andy let me clarify:
We had a major upgrade due to upcoming specs and (although on a side note, the Sidechain data never gets erased, but the entities have all changed), so that we do need to create new accounts.

We moved from the seed-word model to a new model, where your User has an e-mail address as a Login, its protected by a Password (which the Hash is stored in the sidechain so people cant log in as you), we now have 2fa support for protected spending, and the BiblePay address is now also, a new format!  So you get a biblepay address assigned to you when you create your account (youll see it in the User account record).
Now the way we protect your account is your Private key is encrypted with RSA (and this way a biblepay.dll user Or a satellite web site cant access your private key) and also, whats nice is people on your computer or in your household cant get the private key either!

We also improved the security where the password is never cached by the browser, and 2fa can prevent spending (without the 2fa key, the signer will not work!).

So yeah if everyone could start over on unchained and try to fulfill all the tests that would help us.



« Last Edit: September 21, 2021, 08:25:28 AM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 3850


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #95 on: September 21, 2021, 08:27:10 AM »
When trying to create a proposal, I got this error: Address is not valid for this chain.

Question, did you do this from testnet mode?  (To enter testnet you have to go to your User Account in foundation, and change the chain to Testnet, then look on the page and see if it says Chain: Testnet) then try?

Cause if I remember right, I was able to add one; second prong:  Be sure you are requesting proposal funds for a testnet address (these start with a y*)?

Thanks!



  • AndrewScribner
  • Developer

    • 74


    • 7
    • June 21, 2018, 07:17:43 PM
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #96 on: September 22, 2021, 07:41:22 PM »
All is well now. I missed the message about creating new accounts.

I also posted two of the videos of scholars. One is in senior high school, and the other boy is in elementary.

https://unchained.biblepay.org/Media?id=6354bd20ff46eb092319bc058df1852d8c95f9e2a3d96b15a4006b4c9d066923

I didn't see the other video yet. Maybe still processing...


  • earlzmoade
  • Developer

    • 284


    • 46
    • August 02, 2018, 03:22:01 AM
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #97 on: September 23, 2021, 10:21:09 AM »
Hello Rob.

Creating a new testnet unchained account went fine.
email adress, password and 2fa went fine for me. 2fa i used Google Authenticator. No problems there.
On the cellphone setup i did receive the SMS on the phone with the verification code, should the pin go were you input the cellphone number? anyways that just gives me a error:
Code: [Select]
Error sorry this pin you have entered is invalid
Tested the diffrent themes and black looks nice. I also set up a avatar.
Now i will redo some testcases.
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • Rob Andrews
  • Administrator

    • 3850


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #98 on: September 24, 2021, 07:56:12 AM »
Hello Rob.

Creating a new testnet unchained account went fine.
email adress, password and 2fa went fine for me. 2fa i used Google Authenticator. No problems there.
On the cellphone setup i did receive the SMS on the phone with the verification code, should the pin go were you input the cellphone number? anyways that just gives me a error:
Code: [Select]
Error sorry this pin you have entered is invalid
Tested the diffrent themes and black looks nice. I also set up a avatar.
Now i will redo some testcases.

Hi Bro. Earlz,

So I was actually (probably right around the time of your post) receiving another complaint (from our other testing group) about SMS pins too, and I decided to just remove the Send SMS code, and Verify pin for now (as its causing some confusion in registration flow).  Of course, I love having the 'higher verified' weight for votes eventually but I feel we can do that later when we have more than 500 users (in the advanced area).  For now everyone gets 1.0 weight votes, and I hid those features and its deployed.



  • Rob Andrews
  • Administrator

    • 3850


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #99 on: September 24, 2021, 08:19:10 AM »
All is well now. I missed the message about creating new accounts.

I also posted two of the videos of scholars. One is in senior high school, and the other boy is in elementary.

https://unchained.biblepay.org/Media?id=6354bd20ff46eb092319bc058df1852d8c95f9e2a3d96b15a4006b4c9d066923

I didn't see the other video yet. Maybe still processing...

Hi Andy,

Yes, the videos do take between 1-20 minutes to show up (as we inform the user of that in the message after each upload), this is because we have to transcode them, and we go through an AI process now also (to Transcript them too).  We also just recently started showing the AI Transcript on the right side of the screen while you play the video, we now highlight the paragraph you are in (check out the audio bible) for example.

So I see your two videos in TESTNET, very nice.

I want to make a distinction for everyone:  Once we go to prod, these links you post - for example of a video with an id in it, those refer to PROD (MAINNET).  So thats why the users here cant simply click on the link and see the video.  But for us testers, here is what we have to do:  You go to unchained, click "TESTNET" first.  Then while your session is in testnet, if you click Andys link you will see the video.  I just tested this for mainnet (for a video) and confirmed people can share mainnet videos out with the world (and google should see them etc) also.

But hey anyway I just added a new feature to help provide Channels to churches...  If you go to TestNet, then click PEOPLE, then drill into Andys profile (Andrew Scribner), notice the link that says "My Video Channel".  Now you can click on that link (or give it out) and others will see your channel.  Isnt that cool?

We can also start testing our social media features; if everyone will please fill out the My User Record extraneous fields (like Professional Info, About Me Public info, etc).  Ill make a test case for that as we see progress here on the prior test cases come to a close. 

Andy, if you want you can upload a few videos into Mainnet so we can see your mainnet video channel? 

Looking good Andy!  Thanks!



  • earlzmoade
  • Developer

    • 284


    • 46
    • August 02, 2018, 03:22:01 AM
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #100 on: September 25, 2021, 01:18:29 AM »
Mornin.
Hello Brother Rob.

Quote
Of course, I love having the 'higher verified' weight for votes eventually but I feel we can do that later when we have more than 500 users (in the advanced area).  For now everyone gets 1.0 weight votes, and I hid those features and its deployed.

Yeah i suppose that makes sence.

I seem to be having trouble syncing up the windows wallet beyond sept 18. Also i noticed the version 0.17.0.9 crashes upon start sometimes.

Odd part in debug log i saw was :
Code: [Select]
2021-09-25T06:01:55Z GUI: Platform customization: windows
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "79:ad:16:a1:4a:a0:a5:ad:4c:73:58:f4:07:13:2e:65" ("Microsoft Root Certificate Authority") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "00" ("Thawte Timestamping CA") () ("Thawte Certification")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "c1:00:8b:3c:3c:88:11:d1:3e:f6:63:ec:df:40" ("Microsoft Root Authority") () ("Microsoft Corporation", "Copyright (c) 1997 Microsoft Corp.")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" ("Microsoft Authenticode(tm) Root Authority") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" () () ("Copyright (c) 1997 Microsoft Corp.", "Microsoft Time Stamping Service Root", "Microsoft Corporation")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "4a:19:d2:38:8c:82:59:1c:a5:5d:73:5f:15:5d:dc:a3" () () ("NO LIABILITY ACCEPTED, (c)97 VeriSign, Inc.", "VeriSign Time Stamping Service Root", "VeriSign, Inc.")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "44:be:0c:8b:50:00:24:b4:11:d3:36:2d:e0:b3:5f:1b" ("UTN-USERFirst-Object") () ("http://www.usertrust.com")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "1d" ("Sonera Class2 CA") () ()
2021-09-25T06:01:55Z Windows Exception: EXCEPTION_ACCESS_VIOLATION
No debug information available for stacktrace. You should add debug information and then run:
biblepay-qt.exe -printcrashinfo=cfbgsytmmvigc6kdojqxg2cjnztg6aiab5rgsytmmvygc6jnof2c4zlymuwvo2lomrxxo4zaiv4ggzlqoruw63r2ebcvqq2fkbkest2ol5augq2fknjv6vsjj5gecvcjj5haaaa=
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "14:98:26:66:dc:7c:cd:8f:40:53:67:7b:b9:99:ec:85" ("Microsoft ECC Product Root Certificate Authority 2018") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" ("AddTrust External CA Root") () ("AddTrust External TTP Network")
2021-09-25T06:01:55Z GUI: PaymentServer::LoadRootCAs: Loaded  47  root certificates
2021-09-25T06:01:55Z

Anyways after the crash i can just reopen the biblepay-qt and it works , still i have trouble syncing up the wallet.
i have tested from cmd a few times the erasechain=1 command and it tries to resync from zero , but after testing 2 times i noticed it looks like it stops syncing at sept 18. Blocknumber 118074

Gonna do it again and go make some mornin coffe and i post again.
« Last Edit: September 25, 2021, 02:08:33 AM by earlzmoade »
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • Rob Andrews
  • Administrator

    • 3850


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #101 on: September 26, 2021, 01:37:34 PM »
Mornin.
Hello Brother Rob.

Yeah i suppose that makes sence.

I seem to be having trouble syncing up the windows wallet beyond sept 18. Also i noticed the version 0.17.0.9 crashes upon start sometimes.

Odd part in debug log i saw was :
Code: [Select]
2021-09-25T06:01:55Z GUI: Platform customization: windows
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "79:ad:16:a1:4a:a0:a5:ad:4c:73:58:f4:07:13:2e:65" ("Microsoft Root Certificate Authority") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "00" ("Thawte Timestamping CA") () ("Thawte Certification")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "c1:00:8b:3c:3c:88:11:d1:3e:f6:63:ec:df:40" ("Microsoft Root Authority") () ("Microsoft Corporation", "Copyright (c) 1997 Microsoft Corp.")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" ("Microsoft Authenticode(tm) Root Authority") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" () () ("Copyright (c) 1997 Microsoft Corp.", "Microsoft Time Stamping Service Root", "Microsoft Corporation")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "4a:19:d2:38:8c:82:59:1c:a5:5d:73:5f:15:5d:dc:a3" () () ("NO LIABILITY ACCEPTED, (c)97 VeriSign, Inc.", "VeriSign Time Stamping Service Root", "VeriSign, Inc.")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "44:be:0c:8b:50:00:24:b4:11:d3:36:2d:e0:b3:5f:1b" ("UTN-USERFirst-Object") () ("http://www.usertrust.com")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "1d" ("Sonera Class2 CA") () ()
2021-09-25T06:01:55Z Windows Exception: EXCEPTION_ACCESS_VIOLATION
No debug information available for stacktrace. You should add debug information and then run:
biblepay-qt.exe -printcrashinfo=cfbgsytmmvigc6kdojqxg2cjnztg6aiab5rgsytmmvygc6jnof2c4zlymuwvo2lomrxxo4zaiv4ggzlqoruw63r2ebcvqq2fkbkest2ol5augq2fknjv6vsjj5gecvcjj5haaaa=
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "14:98:26:66:dc:7c:cd:8f:40:53:67:7b:b9:99:ec:85" ("Microsoft ECC Product Root Certificate Authority 2018") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" ("AddTrust External CA Root") () ("AddTrust External TTP Network")
2021-09-25T06:01:55Z GUI: PaymentServer::LoadRootCAs: Loaded  47  root certificates
2021-09-25T06:01:55Z

Anyways after the crash i can just reopen the biblepay-qt and it works , still i have trouble syncing up the wallet.
i have tested from cmd a few times the erasechain=1 command and it tries to resync from zero , but after testing 2 times i noticed it looks like it stops syncing at sept 18. Blocknumber 118074

Gonna do it again and go make some mornin coffe and i post again.
So first of all on the "ReportInvalidCertificate" errors, for the payment server, those errors are all OK:  Dash wallets have the same issue... I think that is the dummy HTTPS for the web server that we dont use (unless we want to run a payment server, which I think is a merchant only feature).

However the crash during this line:
2021-09-25T06:01:55Z Windows Exception: EXCEPTION_ACCESS_VIOLATION


That is definitely a problem.

I think what I will do is give everyone a debug version of windows that should throw a stack trace during the next blow up.

Give me a while and I will make a new release and while Im at it, Ill sync from zero and see if we broke the chain.
(We might have broke it with the last release of unchained, cause now the utxos are on the sidechain).





  • Rob Andrews
  • Administrator

    • 3850


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #102 on: September 26, 2021, 08:35:14 PM »
Mornin.
Hello Brother Rob.

Yeah i suppose that makes sence.

I seem to be having trouble syncing up the windows wallet beyond sept 18. Also i noticed the version 0.17.0.9 crashes upon start sometimes.

Odd part in debug log i saw was :
Code: [Select]
2021-09-25T06:01:55Z GUI: Platform customization: windows
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "79:ad:16:a1:4a:a0:a5:ad:4c:73:58:f4:07:13:2e:65" ("Microsoft Root Certificate Authority") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "00" ("Thawte Timestamping CA") () ("Thawte Certification")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "c1:00:8b:3c:3c:88:11:d1:3e:f6:63:ec:df:40" ("Microsoft Root Authority") () ("Microsoft Corporation", "Copyright (c) 1997 Microsoft Corp.")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" ("Microsoft Authenticode(tm) Root Authority") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" () () ("Copyright (c) 1997 Microsoft Corp.", "Microsoft Time Stamping Service Root", "Microsoft Corporation")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "4a:19:d2:38:8c:82:59:1c:a5:5d:73:5f:15:5d:dc:a3" () () ("NO LIABILITY ACCEPTED, (c)97 VeriSign, Inc.", "VeriSign Time Stamping Service Root", "VeriSign, Inc.")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "44:be:0c:8b:50:00:24:b4:11:d3:36:2d:e0:b3:5f:1b" ("UTN-USERFirst-Object") () ("http://www.usertrust.com")
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "1d" ("Sonera Class2 CA") () ()
2021-09-25T06:01:55Z Windows Exception: EXCEPTION_ACCESS_VIOLATION
No debug information available for stacktrace. You should add debug information and then run:
biblepay-qt.exe -printcrashinfo=cfbgsytmmvigc6kdojqxg2cjnztg6aiab5rgsytmmvygc6jnof2c4zlymuwvo2lomrxxo4zaiv4ggzlqoruw63r2ebcvqq2fkbkest2ol5augq2fknjv6vsjj5gecvcjj5haaaa=
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "14:98:26:66:dc:7c:cd:8f:40:53:67:7b:b9:99:ec:85" ("Microsoft ECC Product Root Certificate Authority 2018") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" ("AddTrust External CA Root") () ("AddTrust External TTP Network")
2021-09-25T06:01:55Z GUI: PaymentServer::LoadRootCAs: Loaded  47  root certificates
2021-09-25T06:01:55Z

Anyways after the crash i can just reopen the biblepay-qt and it works , still i have trouble syncing up the wallet.
i have tested from cmd a few times the erasechain=1 command and it tries to resync from zero , but after testing 2 times i noticed it looks like it stops syncing at sept 18. Blocknumber 118074

Gonna do it again and go make some mornin coffe and i post again.

Hey great news:  We didn't break the chain; the problem was just that no one was mining... My sancs were stalled there also... Once I started mining the network recovered and Im in sync on all 4 nodes.

So I did test syncing from zero, and I was able to successfully sync without any issue, here is the latest hash - please verify you are in sync with me?


20:34:46
getblockhash 118716


20:34:46
238e75d5ded9c5fd4bc66225343f7d5a435e8ab6630a6f0e8ac2350d28d3e806



I have not created the Debug version of windows; let me get to that so we can detect this Crash next...




  • Rob Andrews
  • Administrator

    • 3850


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #103 on: September 27, 2021, 08:30:18 AM »
Mornin.
Hello Brother Rob.

Yeah i suppose that makes sence.

I seem to be having trouble syncing up the windows wallet beyond sept 18. Also i noticed the version 0.17.0.9 crashes upon start sometimes.

Odd part in debug log i saw was :
Code: [Select]
2021-09-25T06:01:55Z GUI: Platform customization: windows
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "79:ad:16:a1:4a:a0:a5:ad:4c:73:58:f4:07:13:2e:65" ("Microsoft Root Certificate Authority") () ()
2021-09-25T06:01:55Z GUI: "ReportInvalidCertificate: Paymen

2021-09-25T06:01:55Z Windows Exception: EXCEPTION_ACCESS_VIOLATION
No debug information available for stacktrace. You should add debug information and then run:
biblepay-qt.exe -printcrashinfo=cfbgsytmmvigc6kdojqxg2cjnztg6aiab5rgsytmmvygc6jnof2c4zlymuwvo2lomrxxo4zaiv4ggzlqoruw63r2ebcvqq2fkbkest2ol5augq2fknjv6vsjj5gecvcjj5haaaa=


Authority 2018") () ()
2021-09-25T06:01:55Z

Anyways after the crash i can just reopen the biblepay-qt and it works , still i have trouble syncing up the wallet.
i have tested from cmd a few times the erasechain=1 command and it tries to resync from zero , but after testing 2 times i noticed it looks like it stops syncing at sept 18. Blocknumber 118074

Gonna do it again and go make some mornin coffe and i post again.
Hey bro Earlz,

So I found a little more info on the Windows crash you had.
(On a side note, creating a debug executable for windows make an EXE file that is over 1 GIGabyte, which is absolutely insane, its so big we cant even package it for a release because it doesnt finish zipping into the installer, so we would have to release the EXE binary naked as a lone download and have people run it manually).  But I don't think that will be necessary if we work around the problem with the stack-trace deserializer.

Anyway I ran your stack trace through my windows build (you can do this by running the --printcrashinfo command that it spit out during the crash, and dash-qt takes that hex and deserializes the trace and prints it.

In this case, it looks like its a windows 10 specific issue, something to do with Data Access Prevention (similar to what mac did with gatekeeper) - it keeps monitoring the code to see if it wants to execute any binary instructions at run time outside the scope of the allowed memory; but the problem is for randomx, randomx has a virtual machine that does just that.

And realize we actually call randomx hash functions for every block (even if your not mining) so I can see how this might occur; and I dont think its *every* hash that triggers DEP; I think its more like 1 in 10000 hashes (at least thats what we observed on mac).

So one *possible* solution is to disable DEP or tuen off UAC:
https://www.thewindowsclub.com/exception-access-violation-windows
(I still dont have windows 10 here, so I dont know for sure).

I suppose if you want to try it you can at least tell us that if UAC is OFF and DEP is off, if biblepay runs solid for a certain amount of time?  Then we can at least be fairly sure it had something to do with that.

And what I can do from my end, is offer a release switch to disable randomx.  Note that I do this for MAC, but I dont want to do it for Everyone (because that would impact our security).  I would rather it be an obscure feature that makes biblepay into an SPV client...

So let me know if you want to expiriment with that first and if it helps Ill add the disable randomx switch to windows for people who want to run with all the security on (if thats the problem) ...

The randomx virtual machine executes dynamic instructions at run time that It makes up in its own memory space...

Also one other thing we can do once we know its UAC or DEP, is we can reach out to Tevador who supports xmrig, and ask for help, as he might be able to give us a solution that works with windows 10 ; out of curiosity do we need to disable dep and uac on xmrig to mine on windows 10?


Thanks!




  • earlzmoade
  • Developer

    • 284


    • 46
    • August 02, 2018, 03:22:01 AM
    more
Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release
« Reply #104 on: September 27, 2021, 10:26:04 AM »
Evenin.

I did the erasechain command  and now it have resynced so im all good there.
What i noticed is the client crashes before it opens but then you can just reopen the client 1 or 2 times and it boots up and syncs up...

I will test out the uac idea and will see if anything changes. Figure first test  via the task scheduler  see if anything changes and i could disable uac for all programs aswell ofcourse.. Will do some tinkering later.

Quote
do we need to disable dep and uac on xmrig to mine on windows 10?

On my mining machines the uac is disabled by default so i havent thought about it.
On this machine i do have to give permission every time i run Xmrig. 

Gonna get some chow and then i will do some test scenarios.

Quote
So I did test syncing from zero, and I was able to successfully sync without any issue, here is the latest hash - please verify you are in sync with me?


20:34:46
getblockhash 118716


20:34:46
238e75d5ded9c5fd4bc66225343f7d5a435e8ab6630a6f0e8ac2350d28d3e806

Code: [Select]
17:27:42
getblockhash 118716


17:27:42
238e75d5ded9c5fd4bc66225343f7d5a435e8ab6630a6f0e8ac2350d28d3e806

Yeah looks like we are synced up Rob.
« Last Edit: September 27, 2021, 10:28:49 AM by earlzmoade »
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.