Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Rob Andrews

Pages: [1] 2 3 4 5 6 7 8 ... 244
1
Hello brother and sisters,
Receive much greetings from Kenya family. We did with our first phase which had Mattresses, blankets and digging of the bit latrine. We seek to start our phase II construction of the latrine after digging. We need to buy building materials.
Sand
2 Lorries @17,000=34,000

Ballast

2 [email protected] 12,000=24,000
Total                     58,000                   
seeking 2.4MM bbp for this Phase II project. $ 580
May the Lord richly bless you and multiple the work of your hands.
Pastor Joshua - kenya


Congratulations on finishing Phase 1, Pastor!


I wish you the best on receiving funding for Phase 2's governance proposal.


2
Rob I was able to log in. I created a NFT called Great is the Lord, then realized that I don't have any balance since this is a new account. So I shouldn't have been able to create a NFT right?

Hi Bro Andy,

Thats cool; but remember if you have a balance in Prod, always send it out because I cant recover lost funds from the sidechain (the keys are private).
But I can replenish your testnet balance if you give me your address.

Regarding creating an object, upvoting and creating comments in testnet with a 0 balance:
You can do that, yes, and you can create an NFT simply because we have this model called the 'content creator economy' which allows new users to do things for free (and the server pays for it).  Of course they cant Send Tips or spend bbp, but they can perform actions.  The idea is that a content creator, who made a new video, should be able to upload it and share it.

Later Im going to create a wiki doc and ask the community to help me finish off the rules - but basically I envision that Tippers will be in general, keeping the system alive.

One thing that you should not be able to do with 0 is create a new UTXO record (I believe we charge 500 bbp for that).  Also greeting cards charge a fee.

You were going to create a proposal in Foundation.biblepay, right? (Not sure if you've read my replies to you).


3
Evenin Brother Rob.

Test Case #5

Q1. What is the name of your NFT so we can buy it?


The name of my NFT is called: Take me home, country roads


Q2. Did you buy the NFT successfully, and you can see the NFT in your nft list?


Indeed, bought back  footprints in the sand.
Code: [Select]
Success


You have successfully purchased NFT 25cf90e3d9f4ed22abf3010f44d8536c59261ca6ab2ac5c09b91547336b1d3d4 on TXID 25cf90e3d9f4ed22abf3010f44d8536c59261ca6ab2ac5c09b91547336b1d3d4!

Q3. Were you able to Edit your NFT and can you see that your NFT is now visible in the NFT marketplace?


Edited worked just fine changed the prices aswell as reposted the NFT to the marketplace.

I noticed that someone bought another of my NFT "take me home, country roads" 
well my balance went from 200 000tBBP to 225 000tBBP so it looks successfull to me.
It showed up in invoices aswell.



Nice, looks like we are getting closer...

My sancs started up llmq again; you can test a send to yourself and it should change back to a lightning bolt quickly again.


4
I wanted to send Biblepay to my new test account. I couldn't log into my testnet account, although the mainnet is working fine. Am I doing something wrong here?

When I bid on a NFT, sometimes my bid will show but sometimes it will not. I was able to increase the high offer for the "cat v1" but when I bid for "test3" it didn't increase the high offer.

Hi Andy,

Yeah, your right there was a problem with bidding on NFTs; every other bid got erased... (IE the browser was Alternating in what it was accepting from the user).


FIXED.

Please try bidding now.

Also the NFTs have been improved to show a better gallery, and they also send out an email when you buy one now.

This is especially important when you sponsor an orphan NFT, so both the buyer and seller can receive an email.

Todd from Cameroon-One is creating an orphan NFT in testnet for us over the next few days.

Andy, would you like to create an orphan NFT in testnet?  You can use one of your production orphan bios.


5
Hmm you should be able to log in i just log in to testnet unchained a few hours ago.  Let me test again.

A "bug" that i noticed is that pushing "Enter" on the keyboard dosent log you in have to use the mouse  to  hit the log in button.

Looks like enter works just fine for me now to enter unchained.

Andrew, i tested both on desktop computers that i  have and chromebook and cellphone with opera browser and i can log in just fine.

Are you still having trouble to log in ?

Yeah, LOL, they asked for that ENTER button to work, from the Login page, so thats why its working now, lol.

Thanks for testing.

Ill continue to look at the NFT bid and buy now.


6
I wanted to send Biblepay to my new test account. I couldn't log into my testnet account, although the mainnet is working fine. Am I doing something wrong here?

When I bid on a NFT, sometimes my bid will show but sometimes it will not. I was able to increase the high offer for the "cat v1" but when I bid for "test3" it didn't increase the high offer.

I think I know what this is- and let me explain why Id like to leave it like this because it will be more convenient in Prod.
We have another testing group testing our system (they are a potential client), and they requested a new feature to make it easier to log in from prod (they basically dont want to have to type in the password every time they come to our site even if the session expires).  So what we have is an auto-login with cookie, as long as you havent Hit "LOG OUT".  If you hit "LOG OUT" we erase the cookie...

So whats probably happening is every time you come to our site, we log you into MAINNET.  Simply click LOG OUT of mainnet first... then once you see "GUEST" in the top left, THEN switch the chain and log in again to TESTNET.

Ill look at NFT Cat.  On a strange side note, a lot of our nfts looked badly formatted this morning and I fixed all that code, but its not related to bidding on an nft , so ill look at that.

EDIT: Ok, on the login issue, I made it so when you click Change Chain, it also clears that cookie, so that should be resolved now.  Plz try testnet again.



7
*** TESTING IS NOT OVER ***

Someone asked me if testing was over, No, its far from over, we need help with testing so we can have a quality release.

Feel free to join us.

I believe testing is 40% complete.


8
Hey bro. Earlz, Thanks for testing man.

Alright I will go in and create a DOGE ASAP and see if there is a problem, and try to see whats up with ETH too.

Thanks,
Rob

Yeah we did have a few little kinks, in testnet to work through...
I just realized something, for us to remember in the future.. Although we automatically lock the sanctuary collateral on boot, I discovered that if you erase the blockchain and restart, the collateral is not locked (which makes sense because the code is already past the lock point).  So I accidentally deleted all of my prod sancs (which blew out the LLMQ quorums).  Thats OK, because these will re-form after 48 hours , so that explains why all the transactions are slower (because instantsend is off).  I recreated 3 of my 4 sancs and they are running (but LLMQ is still forming).  (Why did I resync; only because remember we were testing that windows build a while back, and I resynced to prove I could sync from scratch, but my big mistake was I sent a transaction out which spent all 3 of my sancs LOL).

Anyway moving on to todays issues:  In testnet, the server was actually running out of money (it has to have a DSQL balance in order to read or write sidechain tx's).  So that explains part of the problem; where it was not pulling up a couple of the non BBP tx's... However I did find a bug while I was in there, which helps us in the long run thanks to Earlz tx for ETH.  It turns out we dont regard the last zero in 5 digit pins ending in 0 so we needed a little more sidechain code (FIXED).   So thats really why it didnt find your ETH tx in the leaderboard (I see you are in there now man).

Btw thats a good transaction to test with, because it shows you are only 1.55% 'covered'. Another words, it shows that if you increase your position in BBP, you will earn more per day (exercising that condition).  So first lets of course make sure you actually receive the reward, then if you could please Up your BBP stake some and verify the 100% coverage works etc, and of course let me know if you need more tBBP?

So I created a DOGE and an ETH and an LTC position and they appeared, praise God.

Let me know guys if you see any other bugs in Testnet....

I went into foundation to see if anyone recreated more proposals in TESTNET and I didnt see any yet; so I assume Andy didnt get to that yet.


9
Mornin.

 I tested the portfolio builder for ETH  and it does not show up my ethereum stake, not sure if i messed up with the pin or whatever. 

Here you have my information Rob.

On the eth explorer: https://etherscan.io/tx/0x415bab62666718918f24dc8de06399ace714994e2d9065d7f02473814f3b4698

so what i did was move into portfolio builder>coin ticker>ethereum>pasted my adress>received pin 47070
went into ledger wallet and sent some funds.

Still Query UTXO shows no transaction.

Hey bro. Earlz, Thanks for testing man.

Alright I will go in and create a DOGE ASAP and see if there is a problem, and try to see whats up with ETH too.

Thanks,
Rob

10
Evenin brother Rob.

I saw your 2 uploaded videos. I tipped 1 of them with 700tBBP
Tested the 2fa for the tipping function and it looks solid aswell.

Code: [Select]
Success
You have successfully paid this invoice [] on TXID 419b53d7f2c409ff99ffdce07a33fb090dd38f20484ffb82c33903576320682c for 700 BBP.

Test Case #3 - Tip a Video

Added a video myself that i named: Gods list is bigger then yours!  Trust in God and have faith.

my testnet name being : earlz testnet

Test Case #4 - Add a Portfolio Builder Position

Q1. Verify the portfolio builder position was recognized in the leaderboard?


Yep. I see them in the leaderboard.

Q2. Verify more than one PB position correctly adds in Summary and Details show each detail?


Created 3 tBBP positions and it looks all good to me. Gonna test out eth and see if it works out for me.

Q3. Wait 24 hours, and look for the next superblock (you can get the height by typing getgovernanceinfo). Verify that you received the correct daily reward?

Will come back to this one once next payment been done and also the ethereum stake.

Talk to you laters Rob.

10-4 on all this Earlz, awesome.

I tipped you back (you should see it in "Receivables").


Let me know if your Ethereum position shows up too.


11
Figure i redo from second test case hence its new unchained account.

Test Case #2 - Send BIBLEPAY back and forth from your wallet to Unchained and back to yourself

Sent 20 000 tBBP and was credited the same amount, so yes.  Took around 1 confirmation in core wallet.
Q2. Did your biblepaycore balance successfully increase, and your unchained balance decrease by the correct amount?

From core wallet
Code: [Select]
Status: 0/unconfirmed, in memory pool, verified via InstantSend
Date: 9/27/2021 20:19
From: unknown
[b]Test Case #3 - Tip a Video
[/b]

Will rotate back to this one because we need to upload new videos , i see nothing in there.
On a sidenote Rob i got some error trying to access Community>Add New Video Or Media
showing me:
[b]Test Case #4 - Add a Portfolio Builder Position
[b]
Q1. Verify the portfolio builder position was recognized in the leaderboard?[/b]
[b]Q2. Verify more than one PB position correctly adds in Summary and Details show each detail?[/b]
[code]TXID Amount
196223052409f9795aec8dbccc31817eec3074e5de077c4a2e10f3ceb4ec7b07 1500
a3465d3a4c9ac1c1d7940fe59fa6795db41858b38b7dc10154e799043bd05708 1000

Neither one i see yet in the leaderboard. Will sheck back tomorrow.

Q3. Wait 24 hours, and look for the next superblock (you can get the height by typing getgovernanceinfo). Verify that you received the correct daily reward? Will come back to this one.

Hi Bro Earlz,

Great on the send back and forth test for user->user payment.
As far as tipping, I have a couple short videos in there now.  (For the other guys, plz go to your Editing room and Edit the video then select a category and hit save, Or upload a couple new videos guys).


So yeah, on portfolio builder, it looks like this was (mostly broken) due to the last round of unchained upgrades.
One thing that changed that I failed to tell everyone, is we now require a new pin (its still 5 digit, but its calculated using both your unchained address and your core wallet UTXO address), this is for higher security, but the only downside is everyone has to recreate their Portfolio Builder positions.
So could you please add a new one, then wait a block and see if it shows?
I recreated mine, and now Im in the leaderboard.
(Note that it takes 48 hours to actually start receiving the rewards, and they should come into your Core wallet now).

I realize I need to re-test non-bbp currencies; I will try to set up a DOGE soon, then some others.


12
I will reply to the post asap, but in the mean time :
I see the error that occurred with the video category:  We now require the category to be chosen during the upload and apparently they were all empty in testnet; FIXED.

(Im working on adding AI for the categories still) but at least for now you can upload again.

I believe all the other videos are empty because their categories are blank; each user will need to go to 'my editing room' and choose a category, then their videos will reappear).


13
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!



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



15
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).




Pages: [1] 2 3 4 5 6 7 8 ... 244