Quote from: bible_pay on October 30, 2019, 11:45:19 PM

Quote from: bible_pay on October 30, 2019, 11:23:20 PM

Quote from: capulo on October 30, 2019, 10:37:17 PM

Quote from: bible_pay on October 30, 2019, 02:50:02 AM

Quote from: capulo on October 29, 2019, 11:26:34 PM

Quote from: bible_pay on October 29, 2019, 09:34:32 PM

Quote from: capulo on October 29, 2019, 08:32:18 AM

Quote from: bible_pay on October 28, 2019, 03:48:37 PM

Quote from: capulo on October 28, 2019, 08:29:16 AM

i'm not able to rejoin pog...

}
capo@xeon4:~$ biblepay-cli exec cpk capulinko true
{
  "Command": "cpk",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"
}
capo@xeon4:~$ biblepay-cli exec join pog true
{
  "Command": "join",
  "Results": false,
  "Error": "ALREADY_IN_CHAIN"

how to fix this, seems force is not working for me

cpk command works, but join or sendgscc still not:

09:28:50
?
exec join pog

09:29:07
?
sendgscc pog 2000

how to force join? i'm sure i did several unjoin so i should not be joined yet

Well if you did an 'unjoin pog' and waited 5 blocks then did a 'join pog' that should have done it; but anyway, please send me the output of 'exec sentgsc'.
If you sent a gsc with 'sendgscc pog 2000', then received an empty response (that means success), then we should see the txid of the sent GSC and be able to track it.

00:21:51
?
exec sentgsc

sendgscc returns empy, but nothing is sent, i think i need somehow rejoin pog but dont know how

So Im double checking our code, and it appears a person could get out and in like this (for future reference) - say we joined with nickname 'cap' - if you did : exec cpk cap, then exec join pog, then we have "cap" being used. If you did a new force on the cpk without unjoining pog: exec cpk cap2 email user true, then exec unjoin pog, then exec join pog, you would be fine (as far as I can see). But just ignore this part for now lets move on to your two accounts.

As far as 'capulinko2' I dont see a config issue: I see BHKIV* being used for the CPK - and it looks fine, it has your sig, then we have the exec join pog being successful also for the BHIV* (capulinko2). (On a side note I also see a successful BLUL capulo and BLUL pog capulo). But moving back to capulinko2, I dont see anything stopping your pog.

Could you please do this - try erasing debug.log, and after a restart, unlock the wallet and try the 'sendgscc pog 2000' again and look in the log and see if there is a specific error message? It could just be at the time you had < 5 in depth. And maybe that error was only in the log.

If that does not work, tonight while we are sleeping you can try: exec unjoin pog, wait 5 blocks, then exec join pog and re-report. (But I dont see that helping the situation).

only this is in log after trying to tithe
2019-10-30 21:39:52
Tithing 2000.000000 BBP into the Orphan Foundation for POG, because expected ROI is 2394.548592 percent.Misbehaving: 107.172.188.132:40000 peer=20 (0 -> 1)
2019-10-30 21:40:08 Misbehaving: 107.172.188.132:40000 peer=20 (1 -> 2)

and when i try unjoin and then join i get error; already in chain...
i still think i'm not joined, how to force join cmd?

I'm sooo surprised that unjoin join did not work. Well at least we know your CPK is in.
I'm also surprised you don't receive an error or anything after the confirmation that it will tithe.

Let me add an RPC option for you to force a 'join' and Ill report back in a bit.

Capulo,

I released this just now for windows:
https://github.com/biblepay/biblepay-evolution/commit/a63bab6a14717dbaf4bcb8e634ae9c3a58d522a7

Hopefully this will solve your problem.

MIP is building the Linux version, but I'm not sure yet of the eta.

To use the command please type:
exec join pog nickname true

Good luck.

MIP notified me this version is ready.

Btw, you can type 'exec join' to see 'v1.1' to know you have upgraded.