0.16 wallet and bounty news??

IGJ · Post by **IGJ** » 08 Oct 2018, 13:51

Ok, here is my test:

I think all is working.

I will leave the wallet 16.3 with libssl 1.1.1 during the night to do full sync but dont see reasons it will not work. I guess the things will be same on current stable debian release (debian 9 - stretch). Will be useful if izknv can make test on ubuntu too.

Pttn · Post by **Pttn** » 08 Oct 2018, 15:28

It now seems works with LibSsl 1.0 in Debian 9 Sid, but it still does nothing at start in my Debian 9 Sid + LibSsl 1.1. Not sure how you were able to get it working...

Do you think that you could set up a 0.16.3 node? I don't know if you read my post in BitcoinTalk about transactions not broadcasting, I would like to know if I can broadcast them to a 0.16.3 node.

IGJ · Post by **IGJ** » 08 Oct 2018, 16:40

Yes I will setup one node 16.3. It is syncing now but will take time (if my patience over I will push the block chain and will speed it up)

Posted all commands I used during the test. The debian on which I tested someday will become debian 11 because now it is sid - unstable. What do you mean with debian 9 - sid ? Debian 9 is current stable release with code name stretch (always debian sid == debian unstable). If you mean that long time ago you installed debian 9 when it was still sid - unstable and never upgrade it since then, It could be the reason, because a lot of libraries maybe changed and a lot of bugs are fixed since then (sid repository is updating every 6 hours I think). Do "ldd file_binary" and it will show all libs that the shared binary needs and compare with what I posted to see if there are difference. Also can do strace -f or debug with valgrind or gdb they will show eventually where it stuck during code execution. Keep in mind that if during compilation are used old header files (.h) and in linking newer library (.so/.a) unpredicted behavior will happen.

I successfully compiled 16.3 with the patch on debian 9 updated to max - debian 9.5 with libssl 1.1 and all working.

Pttn · Post by **Pttn** » 08 Oct 2018, 16:59

It was a normal Debian 9, then I added sid repositories in the sources.list. Now I realize with "cat /etc/issue" that I am actually running "buster/sid"... I never realized that until now and thought that I was just running Debian 9 + more recent packages, hence the expression "Debian 9 Sid"... It never came to my mind that it actually upgraded the whole system...
But then, I should also have the latest packages and not have any issue to compile if you can...

IGJ · Post by **IGJ** » 08 Oct 2018, 17:32

If your machine is for production environment that is bad really bad.
If you don't have any valuable information or softwares on it I strongly recommend you to reinstall it with debian 9 - stretch. Current sid will have huge numbers of updates during next few years and you will have to update almost every day and swearing because things will stop work when you dont expect it :). Maybe around 2020 or 2021 it will become stable. Downgrading not always possible to be done easily some config files maybe was changed and some parts from newer packages may still be living on your hard drive, so to not mess your future software installations or code you may write or project you would like to build better reinstall on clean.
Ten years ago made such mistake on one production server and was pain in the a*s to servicing it, good it was from stable to testing only (from deb4 to deb5) and only after 1 year it become stable but config checks and test everything proper work after each update is time eating.

My patience is over and pushed the BC to 16.3 node, so it is synced now. Its IP address is 78.83.27.28 . What do you need for your test ?

Pttn · Post by **Pttn** » 08 Oct 2018, 18:54

This machine is more meant for fun activities, I have the other one with Debian 9 Stable for more serious things.

So what I wanted to do is to see if I could broadcast a transaction to a 0.16.3 node, as I cannot broadcast anything currently. I thought at start that there might be a compatibility problem with other nodes, with version 0.10.2. But even with your 0.16.3 node, this does still not work. I should get the text "broadcast though 1 node" when opening the transactions details, but this is not the case. So, my transactions are stuck, until I mine them or double spend with another wallet.

Did you try to send a transaction via Riecoin 0.16.3? Am I the only one that cannot broadcast anything?

IGJ · Post by **IGJ** » 08 Oct 2018, 22:33

Pttn wrote: ↑
08 Oct 2018, 18:54
Did you try to send a transaction via Riecoin 0.16.3? Am I the only one that cannot broadcast anything?

I can receive and send coins from the wallet 16.3 compiled with libssl 1.1 with my patch on debian sid. Receiving goes as normal, I have a feel sending is little slower and there could be a problem with tx broadcasting or the fee is too low and not all miners accept it. I will do more tests and will tell you but for now seems to work.

here are the binaries if you want to try them:
http://download.riecoin-community.com/1 ... bin.tar.gz

Pttn · Post by **Pttn** » 09 Oct 2018, 07:39

Weird...
It was compiled a while ago, without your patch, in Debian 9 Stable, I do not even remember which LibSsl version I used.
If you say so, I might just have to recompile... I will try later.

IGJ · Post by **IGJ** » 09 Oct 2018, 09:42

There is some kind of problem with sending transactions in 16.3 !

My first transactions went, but as I told before had a feel it was slowly. Second transaction Is still not confirmed (after 9 hours) and I see messages in the log, that wallet trying to broadcast it:
2018-10-09 08:56:31 ResendWalletTransactions: rebroadcast 1 unconfirmed transactions
Now I am trying to understand how first one went. During the time it was unconfirmed I play a lot with these cli commands listtransactions, gettransaction, decoderawtransaction and maybe some more. Decoded transactions from 10.2 on 16.3 and vice versa and tried to see if there will be some differences.

Pttn · Post by **Pttn** » 09 Oct 2018, 09:55

Was your transaction confirmed in 966239? I mined my own 0.16.3 transaction here, but there is a second one, and it might be yours.

Is your stuck transaction ID 562821b32337ee7bc2a8318f2c6a331664f0f10a7ddaa096205f260a4573f585 ? I see that in my 0.16.3, but not 0.10.2. You might have successfully broadcast it to me, but not to all others 0.10.2 nodes. If I find another block, it will be confirmed. This explains why your first transaction was confirmed.

So after all, transactions broadcasting might work between 0.16.3 nodes, but there seems to be an incompatibility with the 0.10.2 ones.
In this case, I think that you have the same issue as me.

As an experiment, I will try to send something to a MultiSig "T" address (equivalent to "3" Bitcoin addresses) and see if I can confirm it. Do you see the transaction 0db9d7dc617c85f4150831253e020dfc692c91c9e28c4b1a2141209f1c1348a4 when you do GetBlockTemplate?

Riecoin Community Board

0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??

Re: 0.16 wallet and bounty news??