Test Case #2:
- Unchained wallet generated: yU41ehpvX8UBgPJ4v5TNTYdLRtVxCis7U6
- Sent 7777 tBBP from core to unchained (TXID=78257706f1124f94715633de1c442c7db1cbd4b23732e65cca28b7998268df61)
- Balance appeared on unchained after one confirmation
- 777 tBBP sent back to core wallet (TXID=9b50ece056d940d87a16714f6de768abfa792bc4b18a97a336abe3ec68321d46), unchained balance reduced
- Waited 2 blocks, deposit did not appear in core wallet
- Made another transaction from unchained to core (77 tBBP, TXID=9670f1d4c2b7d87549f6371e0495b6524ec86fecfb12e8b79d8a8d4d95a9820f), unchained balance reduced
- Waited 2 more blocks, no sign of both deposits
Ok I see you had success from steps 1-4, then we started to collapse in 5,6,7.
So Ive been very busy testing these issues, and I found that these particular features are working in PROD, but not in testnet, so looking deeper, I can see bitcoin has actually changed a couple fundamental things in the core wallet (that dash inherited) that break testnet!
One they changed the way transactions are pushed to the network (they require Promises now which we dont have). So arggggh, this stuff compiles but doesnt work.
Another thing I found is a bug in our superblock which required a change anyway.
This actually requires a mandatory upgrade for everyone including the sancs.
So, I was able to port in the changes to get money transfer, tipping, and normal behavior working in unchained against tesnet this morning.
Now Im compiling a new version that fixes the superblock issue also (on a side note, this is what was required for us to have before we can create a UTXO stake in Unchained so we can test a GSC reward next -- thats what Im trying to get to next so I can make more utxo test cases).
Anyway we will need to upgrade to 0.17.0.7 now, in order to move further.
Please hang on and I will release this, and then guys, be sure to verify the version is definiately 0.17.0.7 when you restart.
Also, double check the hash again, Ill post a new one.
On another side note: Andrew mentioned this: You mentioned there is a big lag during the load, then we load (you mentioned an exit or crash but I havent seen that so if that ever happens again please give me the debug.log details and let me know if you mean silent exit, or actual crash, could be that your port is still listening etc), anyway back to the screen loading time: I did a very light analysis on this, and I see that the wallet is really just wasting time during the initialization (its not even checking the efficacy of the blockchain... on my system its lagging about 50 seconds during each boot).. Lets do this: LLMQ should start within 48 hours after the next release (the height is passing now). We will revisit this as soon as LLMQ successfully forms and see if its waiting for quorums.
Thanks.
