0.16 wallet and bounty news??
Re: 0.16 wallet and bounty news??
Yes transactions from 16.3 are broadcasted to 10.2 , but they are rejected. Found the reason why - version of the transaction. 10.2 checks if transaction version is bigger or lower than 1 and reject to add it to mempool + generating this error in the logs:
2018-10-09 11:23:12 ERROR: AcceptToMemoryPool : nonstandard transaction: version
16.3 set transaction version = 2 .
I am not familiar what tx version do (maybe clo1 could explain) but start experimenting and created another one transaction in 16.3 with version = 1. It is still not appear in 10.2 nodes, but I am not sure if it is stuck because the first stucked transaction which is in my 16.3 mempool or there is other reason. I will wait you to mine one more block with 16.3 and then we will see.
I see your transaction 0db9d7dc617c85f4150831253e020dfc692c91c9e28c4b1a2141209f1c1348a4 in my 16.3 mempool so I guess T adresses are broadcasted ok between 16.3 nodes.
What do you see in your 16.3 mempool ( riecon-cli getrawmempool ) ?
EDIT:
Ok you mined one block, and both my stuck transactions gone. After that I put another transaction with changed version number from 2 (default in 16.3) to 1 (10.2 accept only 1) and it was broadcasted and appeared in 10.2 mempool. So the problem is transaction version, clo1 maybe have to explain what can go wrong if we change transaction version. Another one important observation from these tests are that if you have one stuck transaction all other transactions created from the same 16.3 wallet, after that will stuck too when broadcasted to 10.2.
2018-10-09 11:23:12 ERROR: AcceptToMemoryPool : nonstandard transaction: version
16.3 set transaction version = 2 .
I am not familiar what tx version do (maybe clo1 could explain) but start experimenting and created another one transaction in 16.3 with version = 1. It is still not appear in 10.2 nodes, but I am not sure if it is stuck because the first stucked transaction which is in my 16.3 mempool or there is other reason. I will wait you to mine one more block with 16.3 and then we will see.
I see your transaction 0db9d7dc617c85f4150831253e020dfc692c91c9e28c4b1a2141209f1c1348a4 in my 16.3 mempool so I guess T adresses are broadcasted ok between 16.3 nodes.
What do you see in your 16.3 mempool ( riecon-cli getrawmempool ) ?
EDIT:
Ok you mined one block, and both my stuck transactions gone. After that I put another transaction with changed version number from 2 (default in 16.3) to 1 (10.2 accept only 1) and it was broadcasted and appeared in 10.2 mempool. So the problem is transaction version, clo1 maybe have to explain what can go wrong if we change transaction version. Another one important observation from these tests are that if you have one stuck transaction all other transactions created from the same 16.3 wallet, after that will stuck too when broadcasted to 10.2.
Last edited by IGJ on 09 Oct 2018, 16:54, edited 1 time in total.
Re: 0.16 wallet and bounty news??
Great, I am glad that this transaction involving a "T" address went through :D !
Now, I cannot spend what I sent to this address, the Debug.log says "CommitTransaction(): Transaction cannot be broadcast immediately, no-witness-yet", so the wallet is not willing to broadcast it. I think that now, it is the clo1's or some other Core specialist's turn to intervene.
I will also let the specialists talk about the transaction version, although there should be plenty of documentation about this in the web.
Now, I cannot spend what I sent to this address, the Debug.log says "CommitTransaction(): Transaction cannot be broadcast immediately, no-witness-yet", so the wallet is not willing to broadcast it. I think that now, it is the clo1's or some other Core specialist's turn to intervene.
I will also let the specialists talk about the transaction version, although there should be plenty of documentation about this in the web.
rieMiner - Riecoin solo + pooled miner
Personal Riecoin page (links, download,...)
freebitco.in - earn up to $200 in BTC each hour!
Personal Riecoin page (links, download,...)
freebitco.in - earn up to $200 in BTC each hour!
Re: 0.16 wallet and bounty news??
These errors seems to be because your mingw gcc compiler version (eventually try using more recent). On what OS version you are trying to build ? What is your mingw gcc version ?Pon13 wrote: When i execute the last make command i get the following output
....
Re: 0.16 wallet and bounty news??
hi man, thanks for the help !
i re-checked again and since i am in ubuntu 18 (embedded in windows 10) for the first time i missed the following command
Ubuntu Bionic 18.04 1:
so i started from scratch and now i have a different problem. when i execute the command
i get the following:
any thoughts or suggestions? thanks again !
i re-checked again and since i am in ubuntu 18 (embedded in windows 10) for the first time i missed the following command
Ubuntu Bionic 18.04 1:
Code: Select all
sudo update-alternatives --config x86_64-w64-mingw32-g++ # Set the default mingw32 g++ compiler option to posix.
Code: Select all
CONFIG_SITE=$PWD/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/
Code: Select all
checking whether __builtin_clzll is declared... yes
checking for MSG_NOSIGNAL... yes
checking for MSG_DONTWAIT... yes
checking for getmemoryinfo... yes
checking for mallopt M_ARENA_MAX... yes
checking for visibility attribute... yes
checking for thread_local support... yes
checking for Linux getrandom syscall... yes
checking for getentropy... yes
checking for getentropy via random.h... yes
checking for sysctl KERN_ARND... no
checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, Riecoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)
Re: 0.16 wallet and bounty news??
sudo apt-get install libboost-all-dev libssl-dev libdb++-dev libevent-dev
This will install header files (you will need them to compile the wallet). Highly likely you will have to compile and the libs (or at least some of them) with mingw first so this process will produce .dll/.a/.la files windows libraries files. After that you will be able to compile the wallet source code. If you want to have and graphical interface you will need and:
libprotobuf, protobuf-compiler, libqt4
Compiling windows executables under linux is hard and usually takes a huge amount of time to setup proper environment. So if you going to take that task prepare with elephant patience and to fight with different problems :)
First here is some theory how the things work:
EDIT:
Started to build my environment and needed libs for windows build of 16.3 . Maybe later today will be able to give you windows binary to test, and if it works will write step by step command line how to compile your own 16.3 for windows :)
EDIT2:
Can you test this windows64 build:
http://download.riecoin-community.com/1 ... xv2.tar.gz
This will install header files (you will need them to compile the wallet). Highly likely you will have to compile and the libs (or at least some of them) with mingw first so this process will produce .dll/.a/.la files windows libraries files. After that you will be able to compile the wallet source code. If you want to have and graphical interface you will need and:
libprotobuf, protobuf-compiler, libqt4
Compiling windows executables under linux is hard and usually takes a huge amount of time to setup proper environment. So if you going to take that task prepare with elephant patience and to fight with different problems :)
First here is some theory how the things work:
My advice is your first step to be native compilation of 16.3 (you can see my test on the previous page there I posted all commands you will need to compile the wallet under linux for linux). Then you can start it under linux vm and play with. After that you may start cross compile with all needed libraries. Soon or later I or somebody else from the community will build it for windows and maybe will post nice step by step howto but as you can see this is time eating process and many things can go wrong.
EDIT:
Started to build my environment and needed libs for windows build of 16.3 . Maybe later today will be able to give you windows binary to test, and if it works will write step by step command line how to compile your own 16.3 for windows :)
EDIT2:
Can you test this windows64 build:
http://download.riecoin-community.com/1 ... xv2.tar.gz
Re: 0.16 wallet and bounty news??
I now have my own Riecoin page. There, you can currently find general links about Riecoin, and download Riecoin-Qt Deb64 and Win64 binaries.
You will even find the full blockchain up to Block 968981 for Riecoin Core 0.16.3, to avoid having to sync everything.
If I had more time, I would complete this page to make it more useful. If you wish IGJ, you can make a redirection from Pttn.Riecoin-Community.com to ric.Pttn.me.
Step by Step how I compiled for Windows:
You will even find the full blockchain up to Block 968981 for Riecoin Core 0.16.3, to avoid having to sync everything.
If I had more time, I would complete this page to make it more useful. If you wish IGJ, you can make a redirection from Pttn.Riecoin-Community.com to ric.Pttn.me.
Step by Step how I compiled for Windows:
rieMiner - Riecoin solo + pooled miner
Personal Riecoin page (links, download,...)
freebitco.in - earn up to $200 in BTC each hour!
Personal Riecoin page (links, download,...)
freebitco.in - earn up to $200 in BTC each hour!
Re: 0.16 wallet and bounty news??
Thank you @Pttn, I am now using your Win64 exe(riecoin-qt0.16.3_7667f75_Win64.exe).
Re: 0.16 wallet and bounty news??
I now have a fork with correct icons and using Db5.3 instead of 4.8 by default (in a separate branch) for straightforward cross compilation (and compilation without having to pass --with-incompatible-bdb).
While I did a pull request for the icons in RiecoinTeam/Riecoin, I did not for the Db version change.
I am in favor to take advantage of the huge update from 0.10.2 to ditch the prehistoric Db4.8 and use Db5.3 instead (thing that Bitcoin Core cannot do, only because it is so widely used, unlike for us, that they do not want to break wallet compatibility).
This should not introduce problems, and will make the compilation easier in many cases until Bitcoin Core developers finally decide to get rid of Db4.8.
But maybe people have objections for this change, so I am waiting some feedbacks. Else, I will do a pull request for this as well.
Deb64 and Win64 Binaries (commit e16c1349a) now available in my Riecoin page. In practice, there is not really any change, but the icon for the Windows executable is now correct.
How to compile Riecoin Core 0.16.3 in Debian 9 for Linux and Windows available.
While I did a pull request for the icons in RiecoinTeam/Riecoin, I did not for the Db version change.
I am in favor to take advantage of the huge update from 0.10.2 to ditch the prehistoric Db4.8 and use Db5.3 instead (thing that Bitcoin Core cannot do, only because it is so widely used, unlike for us, that they do not want to break wallet compatibility).
This should not introduce problems, and will make the compilation easier in many cases until Bitcoin Core developers finally decide to get rid of Db4.8.
But maybe people have objections for this change, so I am waiting some feedbacks. Else, I will do a pull request for this as well.
Deb64 and Win64 Binaries (commit e16c1349a) now available in my Riecoin page. In practice, there is not really any change, but the icon for the Windows executable is now correct.
How to compile Riecoin Core 0.16.3 in Debian 9 for Linux and Windows available.
rieMiner - Riecoin solo + pooled miner
Personal Riecoin page (links, download,...)
freebitco.in - earn up to $200 in BTC each hour!
Personal Riecoin page (links, download,...)
freebitco.in - earn up to $200 in BTC each hour!
Re: 0.16 wallet and bounty news??
Hi IGJ, thanks for posting the detailed commands! I managed to compile without error message on Ubuntu 18.04. However the binary does not function.IGJ wrote: ↑08 Oct 2018, 13:51Ok, 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.
src/qt/riecoin-qt exists but running it does not show anything - no error, no qt window.
riecoind -version shows: v0.16.3-(something)
riecoind: segmentation fault(core dumped)
Any ideas where I can get better error messages to help diagnosing? Thanks!
Re: 0.16 wallet and bounty news??
Hi, I followed your instructions and managed to compile and run riecoin-qt on debian. Thank you very much for putting these instructions together.Pttn wrote: ↑15 Oct 2018, 18:59I now have a fork with correct icons and using Db5.3 instead of 4.8 by default (in a separate branch) for straightforward cross compilation (and compilation without having to pass --with-incompatible-bdb).
While I did a pull request for the icons in RiecoinTeam/Riecoin, I did not for the Db version change.
I am in favor to take advantage of the huge update from 0.10.2 to ditch the prehistoric Db4.8 and use Db5.3 instead (thing that Bitcoin Core cannot do, only because it is so widely used, unlike for us, that they do not want to break wallet compatibility).
This should not introduce problems, and will make the compilation easier in many cases until Bitcoin Core developers finally decide to get rid of Db4.8.
But maybe people have objections for this change, so I am waiting some feedbacks. Else, I will do a pull request for this as well.
Deb64 and Win64 Binaries (commit e16c1349a) now available in my Riecoin page. In practice, there is not really any change, but the icon for the Windows executable is now correct.
How to compile Riecoin Core 0.16.3 in Debian 9 for Linux and Windows available.
I highly recommend to add the following tips to your how-to, so that future users can save hours of time and be less frustrated:
apt install libdb5.3++-dev (I spent an hour to figure out ++ is needed to avoid a compile error)
apt install libevent-dev
....and more. I also found this doc quite useful.
configure --disable-tests --with-gui