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 - orbis

Pages: [1] 2 3 4 5 6 7 8 ... 14
1
Thanks for answers.
That question about more WCG accounts was just a curiosity.
I don't have more accounts, so I wouldn't be able even to test it. Thanks for clarification.

2
Wau, I received my first wcg reward :)
So, it looks that I've made it all good :)
I have few questions :)
1. Rob, what happens if my wallet will be closed during "next_podc_gsc_transmission"? Is it enough to send "sendgscc wcg" once per day?
2. When the wallet is open, it's needed to have it unlocked?
3. Will setautounlockpassword and -headlesspassword works if it's needed?
4. When I send "sendgscc wcg" manually e.g. 10 blocks before "next_podc_gsc_transmission" and I forget to close wallet will the gsc tx run again?
5. What happens if my coinage in that second tx will be lower then expected, but in first tx it was enough?
6. It's possible to associate more wcg accounts into one wallet?
Thanks

3
So, after latest update I'm finally in :)
Thank you for catching it.
Code: [Select]
10:41:19 exec rac
10:41:19
{
  "Command": "rac",
  "cpid": "04fba56d89a5eb38b1b82f8a6240132c",
  "CPK": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 15375,
  "team_name": "Biblepay",
  "researcher_nickname": "orbis",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 7973175.77,
  "total_wcg_points": 55812230.39,
  "external_purse_total_coin_age": 50251.48444444445,
  "coin_age_percent_required": 0.99,
  "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count.  (See current depth in coin control).",
  "coin_age_required": 81196.20475721419,
  "wcg_id": 1065540,
  "rac": 5978.138139
}

10:42:02 sendgscc wcg
10:42:03
{
  "Results": true
}

4
Can you do me a favor... please try the exec associate again with force=true after it, and see if it shows your CPID and RAC right after association?
CLARIFICATION:  Plz do it this way:
exec associate wcg_username wcg_verificationcode true

Ill have to try to reproduce this; so far Ive associated my cpid 4 times successfully.  Lets also see if anyone else has tested this yet.
So, it looks that I'm totally noob, because it still doesn't work.
Code: [Select]
21:32:50
exec associate orbis XXXXX true

21:32:53
{
  "Command": "associate",
  "wcg_member_id": 1065540,
  "wcg_points": 55771096,
  "cpid": "",
  "rac": 0,
  "researcher_nickname": "",
  "Purse Status": "Successful",
  "External Purse Address": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"
}
After six block still nothing and here is result of exec rac:
Code: [Select]
  "Command": "rac",
  "Error": "Not Linked.  First, you must link your researcher CPID in the chain using 'exec associate'.",
I checked that associate  command many times, it looks good, but I'm now not sure because it still doesn't work :)
I read your posts again and I found, that in this post you wrote this:
The normal newbie would do this:
exec cpk nickname
wait 5 blocks
exec associate orbis wcg_userid wcg_code
wait 5 blocks
type :
exec rac
So, I tried it didn't help too (my nickname on WCG and CPK is the same "orbis"):
Code: [Select]
exec associate orbis orbis XXXX true
Unable to find orbis.  Please type exec rac to see helpful hints to proceed.  (code -1)
I really don't know what I'm doing bad :(
I'm using downloaded WIN wallet 1469.
BTW after each associate it still get 5k tBBP from me: https://prnt.sc/purfwj
I've tried do make "exec cpk orbis" again, but it didn't worked, because nickname is already taken.

5
BTW, it's needed to run any command after associate (e.g. sendgscc) to run WCG within BBP network? Or it's enough to wait?

6
No wonder you are having so many issues Orbis, you are on the wrong chain, please resync with "-erasechain=1" then verify this hash:

getblockhash 14700
92c8c16680413fb1f36bd8c9b389c5ad87cbf14f377a7936509656e714c11ea0

Then, start over with the 'exec cpk your_nickname' then the 'exec associate wcg_username wcg_verification_code' command, and see if that is successful?

I will not be able to track the 5K you refer to until you are on the same chain as me.  If it happens again please re-paste.

Sorry, but I was few days away. Now It looks that I'm on right chain and associate was successful.
Code: [Select]
  "Command": "associate",
  "wcg_member_id": 1065540,
  "wcg_points": 55771096,
  "cpid": "",
  "rac": 0,
  "researcher_nickname": "",
  "Purse Status": "Successful",
  "External Purse Address": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"
My associate TX was again with 5k tBBP. here is: 0fcb5b796acc141badc30954ac5fafa3d4d1fd458398b24cbde31ea2da0642a7
I sent all of my tBBP (75k) to external purse so I'll be waiting if it goes good. Thanks

7
Ok your right, there is a problem when people do the 'exec join' instead of 'exec associate' it puts you in a state you cannot escape from!  So I had to add a line of code to allow the wallet to honor the 'true' (force) to always re-send the association in the next version.

For now, could you please try this:  exec unjoin wcg
Then wait just 2 blocks, then do the 'exec associate' again?  (With force=true)?  Then I think it will go out.

You should not be sending 5000 bbp for association; could you please give me the txid so I can analyze how that occurred?
Here are my results :)
Code: [Select]
17:17:50  exec unjoin wcg
17:17:52
{
  "Command": "unjoin",
  "Results": true
}
So, it looks good.
Then, after 2 blocks, my first try:
Code: [Select]
17:22:47  exec associate orbis XXXXX true
17:22:47
Unable to find orbis.  Please type exec rac to see helpful hints to proceed.  (code -1)
So, I wasn't successful.
After 6+ blocks:
Code: [Select]
18:26:00 exec associate orbis XXXXX true
18:26:00
Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)
Still unsuccessful :(
It looks, that I'll wait for new wallet version.
BTW: after "exec unjoin" there were -5000tBBP tx again: 875df26d46d3667f1443a5f3e13aedddad0a0142687faf28c893047e42ad6986
So, it looks, that "join" and "unjoin" tx are "paid".

8
It clearly says in the PODC manual you have to wait 3 blocks after the registration before trying exec rac.

So now you have to wait (if the tx went out).
It didn't create any tx.
Just give me this error.
Only one tx created was from those "exec join wcg your_username your_verification_code" command.
It took me 5000tBBP in Christian Public Keypair Association tx: 41c946bb680e21fc56d44ad360e2b205fdcd376a6fa9af4fd2f50147de81759b
Since this tx there is only error message when I try "associate".
Ok, let it be for today. I'll check it tommorow, maybe it'll be OK.
Thanks

9
result:

00:00:45
exec associate orbis XXXXX true


00:00:46
Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)

10
I dont see your 'exec associate' in the chain; it looks like it has no verification code; please try 'exec associate wcg_username wcg_verificationcode true'.
OK, I'll try it.
Meanwhile, which method is correct?
exec rac: " Step 3": "From our RPC console, type, exec join wcg your_username your_verification_code""
or PODC manual: "exec associate wcg_username wcg_verification_code"
It looks that PODC manual, or those method in exec RAC is something different?

11
Hi Orbis, Welcome aboard !  Let's look forward to the new positive age of BiblePay.

Could you please give me your CPK (public key) so I can try to do some queries?

EDIT: I don't see your exec associate in the chain; when you did the associate, did you include the correct verification code, and after that did it emit your RAC?  Please paste cpid also.
Hi,
my cpk: ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg
my CPID: 04fba56d89a5eb38b1b82f8a6240132c

12
Hi Rob.
I want to try testnet WCG, but I'm stuck on the beginning :D
I've made a mistake.
I've read sequence in "exec rac" and it looks that it  was bad.
There is written" Step 3": "From our RPC console, type, exec join wcg your_username your_verification_code"", so I've made it.
Then wait 6 blocks and try "exec rac" again,but didn't happen.
Still "Error": "Not Linked.  First, you must link your researcher CPID in the chain using 'exec associate'.",
After that I've read PODC manual again and there was command "exec associate wcg_username wcg_verification_code"
I tried it and this is my result:
Code: [Select]
Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)I don't know what to do. I'm in Biblepay team from beginning, so maybe there is something wrong and I don't know what.
Or it's enough to wait?

13
A) Testing the latest version, I click Bible | Read Bible, click a book and chapter and I see the contents, so I do not see a bug here.  Please be sure you are testing 1.4.3.1.  EDIT: 1.4.3.1 has no extra boxes in the About page - please re-test.

B)  Antivirus:  This is common with cryptos that have miners - the algorithm makes a false positive for that section, however the scan will eventually return negative once we have more than 100 downloads, so this should be solved (just like our prior versions of biblepaycore.exe).

C) On the log, I don't believe we copy the installer contents to %appdata%, are you sure this debug.log is not your log, could you please delete it and reinstall our EXE and see if we write it again?  If we do, Ill do a more in-depth search to see how we could have left that in our build process - Im 50-50 on this, could you help us by checking?  EDIT:  Please be sure this installer is the 1.4.3.1 installer.  I cleaned up the build directory before building 1.4.3.1. 
    EDIT:  I just tested 1.4.3.1 windows install - we don't write the debug.log to the %appdata% directory - please test again.


EDIT:  One thing I didn't explain, I've been deploying the 1.4.3.0+ versions to:
https://www.biblepay.org | See the top level Downloads Menu | Evolution downloads

This might be the problem.
I was using 1429 because I didn't know that there is new version. I didn't found any mention about new version here ;)
Now I have 1431 and here are my answers:
A) Yes, I agree 1.4.3.1 has no extra boxes in the About page
B) I've got a message from my antivirus (Avast) that the file is clear and it's working good now
C) That debug.log is still there. BUT  this debug.log is not in %appdata%. It's in install DOC folder. Here is a screenshot: https://prnt.sc/nrhg7t This file is from end of the March and here is the beginning of that file:
Code: [Select]
2019-03-29 16:54:05 BiblePay Core version 1.4.0.5
2019-03-29 16:54:05 InitParameterInteraction: parameter interaction: -externalip set -> setting -discover=0
2019-03-29 16:54:05 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-03-29 16:54:05 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-03-29 16:54:05 GUI: QCssParser::parseHexColor: Unknown color name '#yellow'
2019-03-29 16:54:05 GUI: QCssParser::parseHexColor: Unknown color name '#grey'
2019-03-29 16:54:05 ***************************************** BIBLEPAY  ***************************************************
2019-03-29 16:54:05 ProdMode: Prod 0.000000BiblePayVersion 1.4.0.5 (BiblePay Core)

It's nice that the BiblepayEvo insttall file is on main page. But I have question for Ubuntu packages. Will they be ready on Evo start? Will be there any changes in repository or the ppa:biblepay-official/mainnet remains the same? Because I'm using packages for my VPS and it wouldn't be fair to be in a disadvantage :)

And I have another wish :) It would be nice to have smart contract reward txs on wallet main page Recent transactions list, because now they are only in tx page.

14
Hi,
after few days I'm back and I'm testing 64bit WIN version.
It's working good, but I've had problems with install.
My antivirus report it as Dyna:BitcoinMiner-CR [PUP]||mul and moved it to Virus vault.
But after set it as "trusted" it works good, mining and GSC is working good.

And maybe I found some bug.
There are Book and Chapter option in "About Biblepay Core" window, but they aren't working.
I cannot choose anything from it and it's empty.

And Rob you still didn't remove those old March debug.log from WIN install file and it's still more than 60MB big :)

15
I have an error from my VPS which I am sure does not have a GPU, but does not appear to have any consequences as I am still able to receive immature 3500 tBBP payments which I presume to be mining rewards.

from getmininginfo:

{
  "gsc_errors": "anti-gpu triggered on my CPK",
}
I have same error too.

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