cool, I wrote the GPU miner for Balloon algo. Message me if you need the miner also you can donate some btc for my hardwork it was hard to crack it. if you'd like to move over to pool.deft.host, even for a few minutes; i'm happy to analyse the shares and show whether they have/havent been produced by a gpu. if you are found to be truthful, im happy to endorse your gpu miner. this source code contains no changes from standard ccminer. I don't believe there's a GPU miner yet
Read back one page? shh petal
|
|
|
In these mining pools, can any miner be used, that is, mining by the CPU, or video cards AMD e NVIDIA ?
cool, I wrote the GPU miner for Balloon algo. Message me if you need the miner also you can donate some btc for my hardwork it was hard to crack it. Thanks Man, its working good. I have transferred the BTC to your address. are you able to show any evidence, screenshot perhaps? i'd love to give everyone the benefit of the doubt, but this is crypto
|
|
|
This coin is a scam whereby the developer cannot even handle some criticism and scamming people around. Immatured and noob developer. Same goes to the scammy coin.
open to all criticism matey
|
|
|
7 8700k 4.7Ghz (Ubuntu 18.04 // 12 hilos): ~ 630H / s 4.4Ghz i7 4790k (MacOSX // 8 hilos): ~ 270h / s i7 860 2.8Ghz (MacOSX // 4 hilos): ~ 145H / s Pentium G4440 (Windows 10 // 2 hilos): ~ 100 h / s Intel Core 1.2Ghz M5 (MacOSX // 4 hilos): ~ 90h / s
dZ3fGxJr1zdh1Ceu2pKvUVKz8HJdcAZkKZ 0 0 99.8% 440.17 KH dHpqKwtaQG8ZWnN4BABgT5CFrGmTpUyKFT 0 0 99.78% 268.53 KH This is impossible with only CPU
those are consumer grade CPUs can you benchmark a farm filled with Dual Socket Mobo https://www.amazon.com/Supermicro-H11DSI-Dual-Socket-Motherboard/dp/B077YV53TZUsing 2x Epyc 7601 https://www.newegg.com/Product/Product.aspx?Item=N82E16819113471? Or can you benchmark someone that just throws 10k usd per day to a cloud computing service like digital ocean, amazon aws or google thingies ? You know that you can mine to a single address with multiple rigs at the same time and the hashrate will be combined, right ? Its scam. Avoid this "cpu" coin
how ? Can you elaborate ? I mean, maybe, who knows but you don't say why. That's typical merican, guilty until proven innocent, right ? fucking hellWe are not fools here, this is ONLY CPU COIN, now thread are edited, and there is no "only cpu" So someone have gpu miner, and that is reason why hashrate is so high It's an open source project on an open network. Anybody is free to develop a GPU miner, and it is inevitable that people will. In fact, it would be disappointing if nobody did. Devs said it is only cpu coin. When all people saw that there is gpu miner, dev edited thread...so...you know what i want to say It's likely that a GPU miner surfaced in the very recently, and the dev reacted accordingly. I can attest first hand that the coin was CPU minable for several days. CPU WITH 600KH in 1 wallet?? O yea 100000 ryzens... i've personally spoken with the person whose wallet this belongs to, as i was concerned about a gpu miner; as well as the load it was placing on the server (no longer an issue). this person owns 400 machines each with twin x2630 cpus (4800 cores total). i was somewhat taken back, as few people have this sort of hardware 'laying around' at their disposal. i went as far as to checking their share traffic, and to my relief they were all within standard distribution of cpu share size; just lots of them - there is never going to be a solution which prevents a person with this much processing horsepower. he was pretty upfront about it, so it doesnt bother me at all. there are a few members with ryzen cpus which achieve several kh due to the ryzen's 20mb l3 cache. one hundred of these machines could easily achieve 400kh. the best part? 4800 cores and only 600kh? i think some people seriously need a reality check regarding the possibility of a gpu miner? entirely possible. any algorithm devised could have a gpu miner written for it; the actual part that matters is the efficiency, if the miner is only 25h/s faster than a cpu, is it even a concern? you know there are publically available GPU miners for argon2? do you realise that they arent even twice as fast as a cpu? they are opencl concepts written for that exact purpose, a concept. feel free to checkout arionum's gpu miner ( https://bitbucket.org/guli13/arionum-gpu-miner); to find that it is not popular at all. i've openly stated that i will attempt my own gpu miner; not in the quest for more speed, but to offset the load placed on the cpu (several members have mentioned their machines being too sluggish to use). i've also stated that once a working one is complete, it will be a public release for all. i'm not going to remove any posts regarding gpu miner accusations; i've even screenshotted them for later embarrassment as i know the posters will likely retract later. thats crypto for you james
|
|
|
hi scorpio18, please revert to commit ff6700b82918f718c8155bc9f06d9e1d28453613, yesterday's commit was a patch to force segwit signalling to help diagnose icemining but this resulted in a fork as you can see. i'd inserted a shim between nomp and the daemon a few days ago (to observe the json 'chatter'), and it receives a 'default_witness_commitment' when it requests getblocktemplate - unsure why yiimp is having trouble in this regard. james
|
|
|
Somebody is mining with 56 KH/s. Is it really using CPU? I am curious somebody is using GPU rigs to mine this coin. Please enlight me...
at the moment it is all cpu. i realise that to anyone skeptical, 56kh might look like a lot, but in reality it is either a set of physical/virtual servers working as a single user. i have started working on an implementation for gpu, but this is more to offload the hashing algorithm so it doesnt bog down the user's machine, as it won't hold a great deal of advantage over cpu due to the way the hashing works. i'm currently separating balloon from it's dependency on the openssl library (sha, evp and aes functions); i'm about 1/3 of the way through, once it is independent, i will attempt an opencl kernel. however this is all being communicated clearly and will be publically released, not a private or 'for sale' miner. james
|
|
|
I've been trying to learn about this project over and over, but still don't get a hint on what is this project really working for? Is there any easier material that can be read to know about the project?
It's nice to see a new algorithm for the CPU. Unfortunately, there is very little information about the project. Can you show a road map?
balloon hashing is quite a unique and versatile hashing algorithm, not to mention being the first implementation of it; instead of the same algorithm being copy and pasted as we seem to find quite regularly these days. in addition to the firm yet forgiving dual_kgw3 retargeting algorithm, the coin itself has quite a small supply; which will take a small while to reach its full reward as to ensure a stable value without 'instaminers' disrupting the market. the biggest point i'm trying to make here is the following.. i've been cryptoprogramming for 3-4 years now, yet in this time i havent released my own currency; the work has always been for others. now that i have some time to put the requisite effort into my own cryptocurrency, im able to do this without the pressure of deadlines and can simply enjoy the fruition of my work. in my mind this will translate directly into a usable coin that will retain value in times to come; not to mention being done for enjoyments sake, not profit. a roadmap isn't out of the question - but not at the moment. things like an electrum wallet, mobile wallet are definitely going to happen in the future; lets see how the currency is received by the public first.. james
|
|
|
Do you plan to release the NOMP module or the source for the pool that has DEFT implemented since it is open source
interesting phrasing; but i'll let that one pass as i had already uploaded it a few hours previous ( https://github.com/deftchain/multi-hashing-balloon).. enjoy
|
|
|
Good luck with your project, it's always nice to see a new cpu coin.
Do you offer translation bounties ? If so I'd like to reserve french translation.
please read the first post for information relating to translation bounties.
|
|
|
Pool really sucks, we don't have any information about what we are mining !
i will add a module later today which displays current earnings/balances.
|
|
|
setgenerate works decently or prefer the cpuminer..?
for solo cpuminer to wallet RPC.. setgenerate is disabled If you go to the '%AppData%\Roaming\Deft' folder and create Deft.conf with the following: server=1 daemon=1 rpcuser=chooseausername rpcpassword=chooseapassword rpcbind=127.0.0.1 rpcallowip=127.0.0.1 Then save, launch Deft wallet.. you should be able to solo-mine by changing your launch.cmd to read: cpuminer.exe -a balloon -o http://127.0.0.1:12668 -u chooseausername -p chooseapassword --no-getwork --coinbase-addr=anaddressfromyourwallet
|
|
|
setgenerate works decently or prefer the cpuminer..?
unfortunately setgenerate was removed early on (in 0.13 i think), i did briefly visit this but decided that external cpuminer/getblocktemplate or stratum would be the way to go.
|
|
|
Hm, have problem with compiling on ubuntu 16.04: CXXLD deftd /usr/bin/ld: libbitcoin_consensus.a(libbitcoin_consensus_a-balloon.o): relocation R_X86_64_PC32 against undefined symbol `SHA256_Init@@OPENSSL_1.0.0' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:3641: recipe for target 'deftd' failed make[2]: *** [deftd] Error 1 Can dev to fix this? Please. can you do a git pull and recompile again? issue should be resolved, apologies..
|
|
|
Hm, have problem with compiling on ubuntu 16.04: CXXLD deftd /usr/bin/ld: libbitcoin_consensus.a(libbitcoin_consensus_a-balloon.o): relocation R_X86_64_PC32 against undefined symbol `SHA256_Init@@OPENSSL_1.0.0' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:3641: recipe for target 'deftd' failed make[2]: *** [deftd] Error 1 Can dev to fix this? Please. this was brought to my attention shortly before ANN ( https://github.com/deftchain/deft/issues/1).
|
|
|
ok, that code works; but is unclear as to what its doing/if it is actually doing anything. will post back with results later
james
|
|
|
Did barrysty1e replied at the end ?
barrysty1e's gone dark. I was in a convo with him, he shared some commercially-sensitive material with me. I was hoping to collaborate, he seemed up for it. Then he suddenly went dark. He's a Kiwi I think, apropos of nothing in particular. I just hope he's okay. Cheers Graham Still here. Was on the other side of the country (Australia); with my primary employer. The NOMP/UNOMP pool is at the point where it is accepting and validating shares (meaning that independently the pool and miner agree on the blockheader); however once the pool sends the solved block to the daemon; the daemon segfaults, as even though the hash is technically correct (matches claimed PoW/nBits), the transaction data differs. NOMP/UNOMP (or any opensource pool for that matter) have a fairly basic way of constructing a coinbase transaction which includes the pool's designated address. It does this by using fairly sparse details that it receives when polling the daemon for a block template. The pool then passes this information (coinb1 and coinb2 in stratum 'params') to the miner - the miner adds their extranonce value and hashes it for what is known as the transaction merkleroot. The issue here is that Slimcoin (or any of the Peercoin family) has an odd transaction format that most pools have no idea about; using a set of zeroes for the sequence 'lock' rather than the bitcoin-standard 'ffffffff'; not to mention other oddities like giving the transaction itself its own timestamp, rather than just a timestamp on the input and output. Have asked openly before on this topic ( https://bitcointalk.org/index.php?topic=1844717.msg). When the pool submits what it thinks is a valid block, the daemon gives the nod because preliminary checks pass - then has an Exception error; while giving a stack dump (while continuing to run). Basically the same thing that was happening years ago - https://bitcointalk.org/index.php?topic=613213.3995;wap. Anyway; i've started writing a pool from scratch that gets around this by using some getwork trickery; stay tuned. james
|
|
|
Seems pool it is not finding blocks?
The problem that the pool is having is due to Slimcoin's custom transaction format (as mentioned by d5000). The pool will correctly identify a blockheader with the correct amount of work, however when it sends this to the daemon using submitblock (along with the transaction data) the daemon then segfaults, as although the dcrypt hash matches - the block contents aren't correct. The issue was encountered years ago with no proposed solution ( https://bitcointalk.org/index.php?topic=613213.3995;wap). I've worked with another currency 'Cryptonite' that an identical issue, where the solution was to only submit the blockheader (no tx data) using 'getwork'. The reason this works, is the daemon already knows about the transactions it has received via p2p (and its own coinbasetxn for the potential block) - the calculated merkleroot then matches the merkleroot provided in the blockheader. It's not quite 'getwork over stratum', as its only used for the solution, not the work propagation. My miner does not work on this pool (works perfectly in solo). crazy hashrate (27 000 khash ?) and all rejected.
I recently came across the GPU solo-mining code (not the stratum gpu miner @ https://github.com/JonnyLatte/slimminerGPU); this will not work against the pool due to differences in getwork/stratum work format and byteswapping of the nonces (and several other fields). Even when the daemon had died, while the stratum was still up; it will still return valid hashes as it keeps the last blocktemplate in memory. More than happy to do some testing if you like. anywayI'm writing a small patch to allow the block to be submitted using getwork; will post back on my results in an hour. james
|
|
|
Regarding the movement of coins: Why only refer to the open source-code being available for experts to look at? That does not answer the questions. The dev of the code should be here and wholeheartedly ready to explain how the "locking" of the coins was planned and how this could fail, simple as that. It is a main part of his job and is common standard in crypto-world and IT in general. The detailed analysis of a malfunction is a must, to show competence, as well as dedication and is the prerequisite to regain trust in a product and the developer/team/company. And last but not least: the investors deserve that.
You obviously make no effort to really help investigate on how the movement of the said to be "locked" coins to the former devs wallet could happen. Instead it seems that this issue should be swept under the rug, as good as possible. As long as this is not worked on and investigated as good as possible and people don't see, that devs help on this and try to explain with their best efforts, Mooncoin is no option for serious crypto-investors.
if there is sufficient need, i'm more than happy to give a detailed explanation of how the locking works. however if its just for yourself, i just see more disagreements and time wasted. i've seen over time you are not a programmer nor do you possess much in the way of low-level understanding as to how cryptocurrency works. the coin locking has existed since december 2016 - and no interest has been shown in it until now, until after other people have forked the wallet code, at which point stolen funds did move. mooncoin has been a fairly good example to me of the strange way in which cryptocurrency works; essentially the developer does all the work, investors then purchase the coins off the exchange, or mine it themselves - under the 'whim' that they are supporting the currency and its development. even after it was becoming obvious that mooncoin was being put off due to my workload (ie. supporting myself, roof over head); i still managed to get the initial 0.13 codebase out; to find not even mooncoin's supporters cared enough to approach the exchanges, get them to update - menial tacts where i simply didnt have the time. it is great when everyone has ideas and strong opinions about how things should be; but if there is noone actually doing work, what is the point? james
|
|
|
the big hint would be: configure: WARNING: Found Berkeley DB other than 4.8; wallets opened by this build will not be portable!anyway.. compiling repo https://github.com/mooncoincore/wallet from scratch on debian 8.10 x64: root@moon:~# apt-get update root@moon:~# apt-get install -y build-essential autoconf automake libssl-dev libdb5.3-dev libdb5.3++-dev libboost-all-dev pkg-config libtool libevent-dev git screen
The following extra packages will be installed: autotools-dev binutils cpp cpp-4.9 dpkg-dev fakeroot g++ g++-4.9 gcc gcc-4.9 gcc-4.9-base git-man icu-devtools libalgorithm-diff-perl libalgorithm-diff-xs-perl libalgorithm-merge-perl libasan1 libatomic1 libboost-atomic-dev libboost-atomic1.55-dev libboost-atomic1.55.0 libboost-chrono-dev libboost-chrono1.55-dev libboost-chrono1.55.0 libboost-context-dev libboost-context1.55-dev libboost-context1.55.0 libboost-coroutine-dev libboost-coroutine1.55-dev libboost-date-time-dev libboost-date-time1.55-dev libboost-date-time1.55.0 libboost-dev libboost-exception-dev libboost-exception1.55-dev libboost-filesystem-dev libboost-filesystem1.55-dev libboost-filesystem1.55.0 libboost-graph-dev libboost-graph-parallel-dev libboost-graph-parallel1.55-dev libboost-graph-parallel1.55.0 libboost-graph1.55-dev libboost-graph1.55.0 libboost-iostreams-dev libboost-iostreams1.55-dev libboost-locale-dev libboost-locale1.55-dev libboost-locale1.55.0 libboost-log-dev libboost-log1.55-dev libboost-log1.55.0 libboost-math-dev libboost-math1.55-dev libboost-math1.55.0 libboost-mpi-dev libboost-mpi-python-dev libboost-mpi-python1.55-dev libboost-mpi-python1.55.0 libboost-mpi1.55-dev libboost-mpi1.55.0 libboost-program-options-dev libboost-program-options1.55-dev libboost-program-options1.55.0 libboost-python-dev libboost-python1.55-dev libboost-python1.55.0 libboost-random-dev libboost-random1.55-dev libboost-random1.55.0 libboost-regex-dev libboost-regex1.55-dev libboost-regex1.55.0 libboost-serialization-dev libboost-serialization1.55-dev libboost-serialization1.55.0 libboost-signals-dev libboost-signals1.55-dev libboost-signals1.55.0 libboost-system-dev libboost-system1.55-dev libboost-system1.55.0 libboost-test-dev libboost-test1.55-dev libboost-test1.55.0 libboost-thread-dev libboost-thread1.55-dev libboost-thread1.55.0 libboost-timer-dev libboost-timer1.55-dev libboost-timer1.55.0 libboost-tools-dev libboost-wave-dev libboost-wave1.55-dev libboost-wave1.55.0 libboost1.55-dev libboost1.55-tools-dev libc-dev-bin libc6-dev libcilkrts5 libcloog-isl4 libcr0 libdb5.3++ libdpkg-perl liberror-perl libevent-core-2.0-5 libevent-extra-2.0-5 libevent-openssl-2.0-5 libevent-pthreads-2.0-5 libexpat1-dev libfakeroot libfile-fcntllock-perl libgcc-4.9-dev libgcc1 libgfortran3 libgomp1 libhwloc-dev libhwloc-plugins libhwloc5 libibverbs-dev libibverbs1 libicu-dev libicu52 libisl10 libitm1 liblsan0 libltdl-dev libltdl7 libmpc3 libmpfr4 libnuma-dev libnuma1 libopenmpi-dev libopenmpi1.6 libpciaccess0 libpython-dev libpython2.7 libpython2.7-dev libquadmath0 libssl-doc libssl1.0.0 libstdc++-4.9-dev libstdc++6 libtsan0 libubsan0 linux-libc-dev make manpages-dev mpi-default-bin mpi-default-dev ocl-icd-libopencl1 openmpi-bin openmpi-common python-dev python2.7-dev rsync zlib1g-dev Suggested packages: autoconf-archive gnu-standards autoconf-doc gettext binutils-doc cpp-doc gcc-4.9-locales debian-keyring g++-multilib g++-4.9-multilib gcc-4.9-doc libstdc++6-4.9-dbg gcc-multilib flex bison gdb gcc-doc gcc-4.9-multilib libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan1-dbg liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libquadmath0-dbg git-daemon-run git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-arch git-cvs git-mediawiki git-svn libboost-doc graphviz libboost1.55-doc gccxml libmpfrc++-dev libntl-dev xsltproc doxygen docbook-xml docbook-xsl default-jdk fop glibc-doc blcr-dkms db5.3-doc libhwloc-contrib-plugins icu-doc libtool-doc libstdc++-4.9-doc automaken gfortran fortran95-compiler gcj-jdk make-doc opencl-icd openmpi-checkpoint iselect screenie byobu The following NEW packages will be installed: autoconf automake autotools-dev binutils build-essential cpp cpp-4.9 dpkg-dev fakeroot g++ g++-4.9 gcc gcc-4.9 git git-man icu-devtools libalgorithm-diff-perl libalgorithm-diff-xs-perl libalgorithm-merge-perl libasan1 libatomic1 libboost-all-dev libboost-atomic-dev libboost-atomic1.55-dev libboost-atomic1.55.0 libboost-chrono-dev libboost-chrono1.55-dev libboost-chrono1.55.0 libboost-context-dev libboost-context1.55-dev libboost-context1.55.0 libboost-coroutine-dev libboost-coroutine1.55-dev libboost-date-time-dev libboost-date-time1.55-dev libboost-date-time1.55.0 libboost-dev libboost-exception-dev libboost-exception1.55-dev libboost-filesystem-dev libboost-filesystem1.55-dev libboost-filesystem1.55.0 libboost-graph-dev libboost-graph-parallel-dev libboost-graph-parallel1.55-dev libboost-graph-parallel1.55.0 libboost-graph1.55-dev libboost-graph1.55.0 libboost-iostreams-dev libboost-iostreams1.55-dev libboost-locale-dev libboost-locale1.55-dev libboost-locale1.55.0 libboost-log-dev libboost-log1.55-dev libboost-log1.55.0 libboost-math-dev libboost-math1.55-dev libboost-math1.55.0 libboost-mpi-dev libboost-mpi-python-dev libboost-mpi-python1.55-dev libboost-mpi-python1.55.0 libboost-mpi1.55-dev libboost-mpi1.55.0 libboost-program-options-dev libboost-program-options1.55-dev libboost-program-options1.55.0 libboost-python-dev libboost-python1.55-dev libboost-python1.55.0 libboost-random-dev libboost-random1.55-dev libboost-random1.55.0 libboost-regex-dev libboost-regex1.55-dev libboost-regex1.55.0 libboost-serialization-dev libboost-serialization1.55-dev libboost-serialization1.55.0 libboost-signals-dev libboost-signals1.55-dev libboost-signals1.55.0 libboost-system-dev libboost-system1.55-dev libboost-system1.55.0 libboost-test-dev libboost-test1.55-dev libboost-test1.55.0 libboost-thread-dev libboost-thread1.55-dev libboost-thread1.55.0 libboost-timer-dev libboost-timer1.55-dev libboost-timer1.55.0 libboost-tools-dev libboost-wave-dev libboost-wave1.55-dev libboost-wave1.55.0 libboost1.55-dev libboost1.55-tools-dev libc-dev-bin libc6-dev libcilkrts5 libcloog-isl4 libcr0 libdb5.3++ libdb5.3++-dev libdb5.3-dev libdpkg-perl liberror-perl libevent-core-2.0-5 libevent-dev libevent-extra-2.0-5 libevent-openssl-2.0-5 libevent-pthreads-2.0-5 libexpat1-dev libfakeroot libfile-fcntllock-perl libgcc-4.9-dev libgfortran3 libgomp1 libhwloc-dev libhwloc-plugins libhwloc5 libibverbs-dev libibverbs1 libicu-dev libisl10 libitm1 liblsan0 libltdl-dev libltdl7 libmpc3 libmpfr4 libnuma-dev libnuma1 libopenmpi-dev libopenmpi1.6 libpciaccess0 libpython-dev libpython2.7 libpython2.7-dev libquadmath0 libssl-dev libssl-doc libstdc++-4.9-dev libtool libtsan0 libubsan0 linux-libc-dev make manpages-dev mpi-default-bin mpi-default-dev ocl-icd-libopencl1 openmpi-bin openmpi-common pkg-config python-dev python2.7-dev rsync screen zlib1g-dev The following packages will be upgraded: gcc-4.9-base libgcc1 libicu52 libssl1.0.0 libstdc++6 5 upgraded, 164 newly installed, 0 to remove and 10 not upgraded. Need to get 111 MB of archives. After this operation, 444 MB of additional disk space will be used.
(Reading database ... 39178 files and directories currently installed.) Preparing to unpack .../libssl1.0.0_1.0.1t-1+deb8u8_amd64.deb ... Unpacking libssl1.0.0:amd64 (1.0.1t-1+deb8u8) over (1.0.1t-1+deb8u7) ... Selecting previously unselected package libasan1:amd64. Preparing to unpack .../libasan1_4.9.2-10+deb8u1_amd64.deb ... Unpacking libasan1:amd64 (4.9.2-10+deb8u1) ... Selecting previously unselected package libatomic1:amd64. Preparing to unpack .../libatomic1_4.9.2-10+deb8u1_amd64.deb ... Unpacking libatomic1:amd64 (4.9.2-10+deb8u1) ...
.. trimmed to allow pasting in bitcointalk forum..
Setting up libfile-fcntllock-perl (0.22-1+b1) ... Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ... Setting up libssl-dev:amd64 (1.0.1t-1+deb8u8) ... Setting up libssl-doc (1.0.1t-1+deb8u8) ... Setting up libtool (2.4.2-1.11) ... Setting up manpages-dev (3.74-1) ... Setting up pkg-config (0.28-1) ... Setting up rsync (3.1.1-3+deb8u1) ... Setting up screen (4.2.1-3+deb8u1) ... Setting up libdb5.3-dev (5.3.28-9+deb8u1) ... Setting up libdb5.3++-dev (5.3.28-9+deb8u1) ... Setting up libhwloc-plugins (1.10.0-3) ... Processing triggers for libc-bin (2.19-18+deb8u10) ... Processing triggers for systemd (215-17+deb8u7) ... root@moon:~# git clone https://github.com/mooncoincore/wallet.git mooncoin Cloning into 'mooncoin'... remote: Counting objects: 1815, done. remote: Total 1815 (delta 0), reused 0 (delta 0), pack-reused 1815 Receiving objects: 99% (1797/1815), 3.93 MiB | 2.26 MiB/s Receiving objects: 100% (1815/1815), 3.93 MiB | 2.26 MiB/s Receiving objects: 100% (1815/1815), 9.48 MiB | 2.26 MiB/s, done. Resolving deltas: 100% (417/417) Resolving deltas: 100% (417/417), done. Checking connectivity... done. root@moon:~# cd mooncoin/ root@moon:~/mooncoin# ./autogen.sh libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'. libtoolize: copying file `build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `build-aux/m4'. libtoolize: copying file `build-aux/m4/libtool.m4' libtoolize: copying file `build-aux/m4/ltoptions.m4' libtoolize: copying file `build-aux/m4/ltsugar.m4' libtoolize: copying file `build-aux/m4/ltversion.m4' libtoolize: copying file `build-aux/m4/lt~obsolete.m4' libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'. libtoolize: copying file `build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `build-aux/m4'. libtoolize: copying file `build-aux/m4/libtool.m4' libtoolize: copying file `build-aux/m4/ltoptions.m4' libtoolize: copying file `build-aux/m4/ltsugar.m4' libtoolize: copying file `build-aux/m4/ltversion.m4' libtoolize: copying file `build-aux/m4/lt~obsolete.m4' libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'. libtoolize: copying file `build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `build-aux/m4'. libtoolize: copying file `build-aux/m4/libtool.m4' libtoolize: copying file `build-aux/m4/ltoptions.m4' libtoolize: copying file `build-aux/m4/ltsugar.m4' libtoolize: copying file `build-aux/m4/ltversion.m4' libtoolize: copying file `build-aux/m4/lt~obsolete.m4' Makefile.am:9: warning: user variable 'GZIP_ENV' defined here ... /usr/share/automake-1.14/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here src/Makefile.qt.include:168: warning: whitespace following trailing backslash src/Makefile.am:504: 'src/Makefile.qt.include' included from here src/Makefile.am:475: warning: user target '.mm.o' defined here ... /usr/share/automake-1.14/am/depend2.am: ... overrides Automake target '.mm.o' defined here root@moon:~/mooncoin# ./configure --with-incompatible-bdb checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking whether make supports nested variables... (cached) yes checking for g++... g++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... gcc3 checking whether g++ supports C++11 features by default... no checking whether g++ supports C++11 features with -std=c++11... yes checking whether std::atomic can be used without link library... yes checking whether we are using the GNU Objective C++ compiler... no checking whether g++ -std=c++11 accepts -g... no checking dependency style of g++ -std=c++11... gcc3 checking how to print strings... printf checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... mt checking if mt is a manifest tool... no checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking how to run the C++ preprocessor... g++ -std=c++11 -E checking for ld used by g++ -std=c++11... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ -std=c++11 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ -std=c++11 option to produce PIC... -fPIC -DPIC checking if g++ -std=c++11 PIC flag -fPIC -DPIC works... yes checking if g++ -std=c++11 static flag -static works... yes checking if g++ -std=c++11 supports -c -o file.o... yes checking if g++ -std=c++11 supports -c -o file.o... (cached) yes checking whether the g++ -std=c++11 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for ar... /usr/bin/ar checking for ranlib... /usr/bin/ranlib checking for strip... /usr/bin/strip checking for gcov... /usr/bin/gcov checking for lcov... no checking for java... no checking for python3.6... no checking for python3.5... no checking for python3.4... /usr/bin/python3.4 checking for genhtml... no checking for git... /usr/bin/git checking for ccache... no checking for xgettext... no checking for hexdump... /usr/bin/hexdump checking for readelf... /usr/bin/readelf checking for c++filt... /usr/bin/c++filt checking for objcopy... /usr/bin/objcopy checking whether C++ compiler accepts -Werror... yes checking whether C++ compiler accepts -Wall... yes checking whether C++ compiler accepts -Wextra... yes checking whether C++ compiler accepts -Wformat... yes checking whether C++ compiler accepts -Wformat-security... yes checking whether C++ compiler accepts -Wunused-parameter... yes checking whether C++ compiler accepts -Wself-assign... no checking whether C++ compiler accepts -Wunused-local-typedef... no checking whether C++ compiler accepts -Wdeprecated-register... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking whether byte ordering is bigendian... no checking whether gcc is Clang... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking whether more special flags are required for pthreads... no checking for PTHREAD_PRIO_INHERIT... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking whether strerror_r is declared... yes checking for strerror_r... yes checking whether strerror_r returns char *... yes checking whether the linker accepts -Wl,--large-address-aware... no checking for __attribute__((visibility))... yes checking for __attribute__((dllexport))... no checking for __attribute__((dllimport))... no checking for library containing clock_gettime... none required checking whether C++ compiler accepts -fPIC... yes checking whether C++ compiler accepts -Wstack-protector... yes checking whether C++ compiler accepts -fstack-protector-all... yes checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes checking whether C++ preprocessor accepts -U_FORTIFY_SOURCE... yes checking whether the linker accepts -Wl,--dynamicbase... no checking whether the linker accepts -Wl,--nxcompat... no checking whether the linker accepts -Wl,-z,relro... yes checking whether the linker accepts -Wl,-z,now... yes checking whether C++ compiler accepts -fPIE... yes checking whether the linker accepts -pie... yes checking endian.h usability... yes checking endian.h presence... yes checking for endian.h... yes checking sys/endian.h usability... no checking sys/endian.h presence... no checking for sys/endian.h... no checking byteswap.h usability... yes checking byteswap.h presence... yes checking for byteswap.h... yes checking stdio.h usability... yes checking stdio.h presence... yes checking for stdio.h... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for strings.h... (cached) yes checking for sys/types.h... (cached) yes checking for sys/stat.h... (cached) yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking sys/prctl.h usability... yes checking sys/prctl.h presence... yes checking for sys/prctl.h... yes checking whether strnlen is declared... yes checking whether le16toh is declared... yes checking whether le32toh is declared... yes checking whether le64toh is declared... yes checking whether htole16 is declared... yes checking whether htole32 is declared... yes checking whether htole64 is declared... yes checking whether be16toh is declared... yes checking whether be32toh is declared... yes checking whether be64toh is declared... yes checking whether htobe16 is declared... yes checking whether htobe32 is declared... yes checking whether htobe64 is declared... yes checking whether bswap_16 is declared... yes checking whether bswap_32 is declared... yes checking whether bswap_64 is declared... yes checking for MSG_NOSIGNAL... yes checking for visibility attribute... yes checking for Berkeley DB C++ headers... default configure: WARNING: Found Berkeley DB other than 4.8; wallets opened by this build will not be portable! checking for main in -ldb_cxx-4.8... no checking for main in -ldb_cxx... yes checking miniupnpc/miniwget.h usability... no checking miniupnpc/miniwget.h presence... no checking for miniupnpc/miniwget.h... no checking miniupnpc/miniupnpc.h usability... no checking miniupnpc/miniupnpc.h presence... no checking for miniupnpc/miniupnpc.h... no checking miniupnpc/upnpcommands.h usability... no checking miniupnpc/upnpcommands.h presence... no checking for miniupnpc/upnpcommands.h... no checking miniupnpc/upnperrors.h usability... no checking miniupnpc/upnperrors.h presence... no checking for miniupnpc/upnperrors.h... no checking for QT... no checking for QT... no configure: WARNING: Qt dependencies not found; bitcoin-qt frontend will not be built checking whether to build Mooncoin Core GUI... no (Qt5) checking for boostlib >= 1.47.0... yes checking whether the Boost::System library is available... yes checking for exit in -lboost_system... yes checking whether the Boost::Filesystem library is available... yes checking for exit in -lboost_filesystem... yes checking whether the Boost::Program_Options library is available... yes checking for exit in -lboost_program_options... yes checking whether the Boost::Thread library is available... yes checking for exit in -lboost_thread... yes checking whether the Boost::Chrono library is available... yes checking for exit in -lboost_chrono... yes checking whether the Boost::Unit_Test_Framework library is available... yes checking for dynamic linked boost test... yes checking for mismatched boost c++11 scoped enums... mismatched checking for SSL... yes checking for CRYPTO... yes checking for EVENT... yes checking for EVENT_PTHREADS... yes checking for ZMQ... no configure: WARNING: libzmq version 4.x or greater not found, disabling checking whether to build mooncoind... yes checking whether to build utils (mooncoin-cli mooncoin-tx)... yes checking whether to build libraries... yes checking if ccache should be used... no checking if wallet should be enabled... yes checking whether to build with support for UPnP... no checking whether to build test_mooncoin... yes checking whether to reduce exports... no checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating libbitcoinconsensus.pc config.status: creating Makefile config.status: creating src/Makefile config.status: creating share/setup.nsi config.status: creating share/qt/Info.plist config.status: creating qa/pull-tester/run-bitcoind-for-test.sh config.status: creating qa/pull-tester/tests_config.py config.status: creating contrib/devtools/split-debug.sh config.status: creating src/config/bitcoin-config.h config.status: executing depfiles commands config.status: executing libtool commands === configuring in src/univalue (/root/mooncoin/src/univalue) configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr/local' '--with-incompatible-bdb' '--disable-shared' '--with-pic' '--with-bignum=no' '--enable-module-recovery' --cache-file=/dev/null --srcdir=. checking whether make supports nested variables... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to print strings... printf checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... mt checking if mt is a manifest tool... no checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... no checking whether to build static libraries... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating pc/libunivalue.pc config.status: creating pc/libunivalue-uninstalled.pc config.status: creating univalue-config.h config.status: executing depfiles commands config.status: executing libtool commands === configuring in src/secp256k1 (/root/mooncoin/src/secp256k1) configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr/local' '--with-incompatible-bdb' '--disable-shared' '--with-pic' '--with-bignum=no' '--enable-module-recovery' --cache-file=/dev/null --srcdir=. checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking how to print strings... printf checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... mt checking if mt is a manifest tool... no checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... no checking whether to build static libraries... yes checking whether make supports nested variables... (cached) yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for ar... /usr/bin/ar checking for ranlib... /usr/bin/ranlib checking for strip... /usr/bin/strip checking for gcc... gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) gcc3 checking how to run the C preprocessor... gcc -E checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... gcc3 checking if gcc supports -std=c89 -pedantic -Wall -Wextra -Wcast-align -Wnested-externs -Wshadow -Wstrict-prototypes -Wno-unused-function -Wno-long-long -Wno-overlength-strings... yes checking if gcc supports -fvisibility=hidden... yes checking for __int128... yes checking for __builtin_expect... yes checking native compiler: gcc... ok checking for x86_64 assembly availability... yes checking for CRYPTO... yes checking for main in -lcrypto... yes checking for EC functions in libcrypto... yes checking for javac... no configure: WARNING: cannot find JDK; try setting $JAVAC or $JAVA_HOME checking jni headers... none configure: WARNING: jni headers/dependencies not found. jni support disabled checking whether byte ordering is bigendian... no configure: Using static precomputation: yes configure: Using assembly optimizations: x86_64 configure: Using field implementation: 64bit configure: Using bignum implementation: no configure: Using scalar implementation: 64bit configure: Using endomorphism optimizations: no configure: Building ECDH module: no configure: Building ECDSA pubkey recovery module: yes configure: Using jni: no checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating libsecp256k1.pc config.status: creating src/libsecp256k1-config.h config.status: executing depfiles commands config.status: executing libtool commands Fixing libtool for -rpath problems. root@moon:~/mooncoin# make -j2 Making all in src make[1]: Entering directory '/root/mooncoin/src' make[2]: Entering directory '/root/mooncoin/src' CXX libbitcoinconsensus_la-arith_uint256.lo CXX libbitcoinconsensus_la-hash.lo CXX libbitcoinconsensus_la-pubkey.lo CXX libbitcoinconsensus_la-uint256.lo CXX libbitcoinconsensus_la-utilstrencodings.lo make[3]: Entering directory '/root/mooncoin/src/secp256k1' gcc -I. -g -O2 -Wall -Wextra -Wno-unused-function -c src/gen_context.c -o gen_context.o CXX mooncoind-bitcoind.o gcc gen_context.o -o gen_context ./gen_context CC src/libsecp256k1_la-secp256k1.lo CCLD libsecp256k1.la make[3]: Leaving directory '/root/mooncoin/src/secp256k1' CXX libbitcoin_server_a-addrman.o CXX libbitcoin_server_a-bloom.o CXX libbitcoin_server_a-blockencodings.o CXX libbitcoin_server_a-chain.o CXX libbitcoin_server_a-checkpoints.o CXX libbitcoin_server_a-httprpc.o CXX libbitcoin_server_a-httpserver.o CXX libbitcoin_server_a-init.o CXX libbitcoin_server_a-dbwrapper.o CXX libbitcoin_server_a-main.o CXX libbitcoin_server_a-merkleblock.o CXX libbitcoin_server_a-miner.o CXX libbitcoin_server_a-net.o CXX libbitcoin_server_a-noui.o CXX libbitcoin_server_a-pow.o CXX libbitcoin_server_a-rest.o CXX script/libbitcoin_server_a-sigcache.o CXX script/libbitcoin_server_a-ismine.o CXX libbitcoin_server_a-timedata.o CXX libbitcoin_server_a-torcontrol.o CXX libbitcoin_server_a-txdb.o CXX libbitcoin_server_a-txmempool.o CXX libbitcoin_server_a-ui_interface.o CXX libbitcoin_server_a-validationinterface.o CXX libbitcoin_server_a-versionbits.o CXX libbitcoin_common_a-amount.o CXX libbitcoin_common_a-base58.o CXX libbitcoin_common_a-chainparams.o CXX libbitcoin_common_a-coins.o CXX libbitcoin_common_a-compressor.o CXX libbitcoin_common_a-core_read.o CXX libbitcoin_common_a-core_write.o CXX libbitcoin_common_a-key.o CXX libbitcoin_common_a-keystore.o CXX libbitcoin_common_a-netbase.o CXX libbitcoin_common_a-protocol.o CXX libbitcoin_common_a-scheduler.o CXX script/libbitcoin_common_a-sign.o CXX script/libbitcoin_common_a-standard.o make[3]: Entering directory '/root/mooncoin/src/univalue' CXX lib/libunivalue_la-univalue.lo CXX libbitcoin_util_a-chainparamsbase.o CXX lib/libunivalue_la-univalue_read.lo CXX libbitcoin_util_a-random.o CXX lib/libunivalue_la-univalue_write.lo CXXLD libunivalue.la make[3]: Leaving directory '/root/mooncoin/src/univalue' CXX rpc/libbitcoin_util_a-protocol.o CXX support/libbitcoin_util_a-cleanse.o CXX libbitcoin_util_a-sync.o CXX libbitcoin_util_a-util.o CXX libbitcoin_util_a-utilmoneystr.o CXX libbitcoin_util_a-utilstrencodings.o CXX libbitcoin_util_a-utiltime.o CXX policy/libbitcoin_wallet_a-rbf.o CXX libbitcoin_consensus_a-arith_uint256.o CXX consensus/libbitcoin_consensus_a-merkle.o CXX libbitcoin_consensus_a-hash.o CXX primitives/libbitcoin_consensus_a-block.o CXX primitives/libbitcoin_consensus_a-transaction.o CXX libbitcoin_consensus_a-pubkey.o CXX script/libbitcoin_consensus_a-bitcoinconsensus.o CXX script/libbitcoin_consensus_a-interpreter.o CXX script/libbitcoin_consensus_a-script.o CXX script/libbitcoin_consensus_a-script_error.o CXX libbitcoin_consensus_a-uint256.o CXX libbitcoin_consensus_a-utilstrencodings.o CXX crypto/crypto_libbitcoin_crypto_a-aes.o CXX crypto/crypto_libbitcoin_crypto_a-hmac_sha256.o CXX crypto/crypto_libbitcoin_crypto_a-hmac_sha512.o CXX crypto/crypto_libbitcoin_crypto_a-ripemd160.o CXX crypto/crypto_libbitcoin_crypto_a-scrypt.o CXX crypto/crypto_libbitcoin_crypto_a-sha1.o CXX crypto/crypto_libbitcoin_crypto_a-sha256.o CXX crypto/crypto_libbitcoin_crypto_a-sha512.o CC lyra2m/crypto_libbitcoin_crypto_a-Lyra2.o CC lyra2m/crypto_libbitcoin_crypto_a-Sponge.o CC balloon/crypto_libbitcoin_crypto_a-bitstream.o CC balloon/crypto_libbitcoin_crypto_a-compress.o CC balloon/crypto_libbitcoin_crypto_a-encode.o CC balloon/crypto_libbitcoin_crypto_a-hash_state.o CC balloon/crypto_libbitcoin_crypto_a-balloonpow.o balloon/balloonpow.c: In function balloonpow_hash: balloon/balloonpow.c:29:25: warning: passing argument 2 of hash_state_extract discards const qualifier from pointer target type hash_state_extract(&s,output); ^ In file included from balloon/balloonpow.c:11:0: balloon/hash_state.h:48:5: note: expected uint8_t * but argument is of type const void * int hash_state_extract (const struct hash_state *s, uint8_t out[BLOCK_SIZE]); ^ CXX mooncoin_cli-bitcoin-cli.o CXX rpc/libbitcoin_cli_a-client.o CXX mooncoin_tx-bitcoin-tx.o CXX crypto/libbitcoinconsensus_la-aes.lo CXX crypto/libbitcoinconsensus_la-hmac_sha256.lo CXX crypto/libbitcoinconsensus_la-hmac_sha512.lo CXX crypto/libbitcoinconsensus_la-ripemd160.lo CXX crypto/libbitcoinconsensus_la-scrypt.lo CXX crypto/libbitcoinconsensus_la-sha1.lo CXX crypto/libbitcoinconsensus_la-sha256.lo CXX crypto/libbitcoinconsensus_la-sha512.lo CC lyra2m/libbitcoinconsensus_la-Lyra2.lo CC lyra2m/libbitcoinconsensus_la-Sponge.lo CC balloon/libbitcoinconsensus_la-bitstream.lo CC balloon/libbitcoinconsensus_la-compress.lo CC balloon/libbitcoinconsensus_la-encode.lo CC balloon/libbitcoinconsensus_la-hash_state.lo CC balloon/libbitcoinconsensus_la-balloonpow.lo balloon/balloonpow.c: In function 'balloonpow_hash': balloon/balloonpow.c:29:25: warning: passing argument 2 of 'hash_state_extract' discards 'const' qualifier from pointer target type hash_state_extract(&s,output); ^ In file included from balloon/balloonpow.c:11:0: balloon/hash_state.h:48:5: note: expected 'uint8_t *' but argument is of type 'const void *' int hash_state_extract (const struct hash_state *s, uint8_t out[BLOCK_SIZE]); ^ CXX consensus/libbitcoinconsensus_la-merkle.lo CXX primitives/libbitcoinconsensus_la-block.lo CXX primitives/libbitcoinconsensus_la-transaction.lo CXX script/libbitcoinconsensus_la-bitcoinconsensus.lo CXX script/libbitcoinconsensus_la-interpreter.lo CXX script/libbitcoinconsensus_la-script.lo CXX script/libbitcoinconsensus_la-script_error.lo CXX policy/libbitcoin_server_a-fees.o CXX policy/libbitcoin_server_a-policy.o CXX rpc/libbitcoin_server_a-blockchain.o CXX rpc/libbitcoin_server_a-mining.o CXX rpc/libbitcoin_server_a-misc.o CXX rpc/libbitcoin_server_a-net.o CXX rpc/libbitcoin_server_a-rawtransaction.o CXX rpc/libbitcoin_server_a-server.o AR libbitcoin_common.a CXX support/libbitcoin_util_a-pagelocker.o CXX libbitcoin_util_a-clientversion.o CXX compat/libbitcoin_util_a-glibc_sanity.o CXX compat/libbitcoin_util_a-glibcxx_sanity.o CXX compat/libbitcoin_util_a-strnlen.o CXX wallet/libbitcoin_wallet_a-crypter.o CXX wallet/libbitcoin_wallet_a-db.o CXX wallet/libbitcoin_wallet_a-rpcdump.o CXX wallet/libbitcoin_wallet_a-rpcwallet.o CXX wallet/libbitcoin_wallet_a-wallet.o CXX wallet/libbitcoin_wallet_a-walletdb.o AR libbitcoin_consensus.a AR crypto/libbitcoin_crypto.a CXX leveldb/db/leveldb_libleveldb_a-builder.o CXX leveldb/db/leveldb_libleveldb_a-c.o CXX leveldb/db/leveldb_libleveldb_a-dbformat.o CXX leveldb/db/leveldb_libleveldb_a-db_impl.o CXX leveldb/db/leveldb_libleveldb_a-db_iter.o CXX leveldb/db/leveldb_libleveldb_a-dumpfile.o CXX leveldb/db/leveldb_libleveldb_a-filename.o CXX leveldb/db/leveldb_libleveldb_a-log_reader.o CXX leveldb/db/leveldb_libleveldb_a-log_writer.o CXX leveldb/db/leveldb_libleveldb_a-memtable.o In file included from ./leveldb/util/arena.h:9:0, from ./leveldb/db/skiplist.h:33, from ./leveldb/db/memtable.h:11, from leveldb/db/memtable.cc:5: leveldb/db/memtable.cc: In member function void leveldb::MemTable::Add(leveldb::SequenceNumber, leveldb::ValueType, const leveldb::Slice&, const leveldb::Slice&): leveldb/db/memtable.cc:104:31: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] assert((p + val_size) - buf == encoded_len); ^ CXX leveldb/db/leveldb_libleveldb_a-repair.o CXX leveldb/db/leveldb_libleveldb_a-table_cache.o CXX leveldb/db/leveldb_libleveldb_a-version_edit.o CXX leveldb/db/leveldb_libleveldb_a-version_set.o CXX leveldb/db/leveldb_libleveldb_a-write_batch.o CXX leveldb/table/leveldb_libleveldb_a-block_builder.o CXX leveldb/table/leveldb_libleveldb_a-block.o CXX leveldb/table/leveldb_libleveldb_a-filter_block.o CXX leveldb/table/leveldb_libleveldb_a-format.o CXX leveldb/table/leveldb_libleveldb_a-iterator.o CXX leveldb/table/leveldb_libleveldb_a-merger.o CXX leveldb/table/leveldb_libleveldb_a-table_builder.o CXX leveldb/table/leveldb_libleveldb_a-table.o CXX leveldb/table/leveldb_libleveldb_a-two_level_iterator.o CXX leveldb/util/leveldb_libleveldb_a-arena.o CXX leveldb/util/leveldb_libleveldb_a-bloom.o CXX leveldb/util/leveldb_libleveldb_a-cache.o leveldb/util/bloom.cc: In member function virtual void leveldb::{anonymous}::BloomFilterPolicy::CreateFilter(const leveldb::Slice*, int, std::string*) const: leveldb/util/bloom.cc:50:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] for (size_t i = 0; i < n; i++) { ^ CXX leveldb/util/leveldb_libleveldb_a-coding.o CXX leveldb/util/leveldb_libleveldb_a-comparator.o CXX leveldb/util/leveldb_libleveldb_a-crc32c.o CXX leveldb/util/leveldb_libleveldb_a-env.o CXX leveldb/util/leveldb_libleveldb_a-env_posix.o CXX leveldb/util/leveldb_libleveldb_a-env_win.o CXX leveldb/util/leveldb_libleveldb_a-filter_policy.o CXX leveldb/util/leveldb_libleveldb_a-hash.o CXX leveldb/util/leveldb_libleveldb_a-histogram.o CXX leveldb/util/leveldb_libleveldb_a-logging.o leveldb/util/logging.cc: In function bool leveldb::ConsumeDecimalNumber(leveldb::Slice*, uint64_t*): leveldb/util/logging.cc:58:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] (v == kMaxUint64/10 && delta > kMaxUint64%10)) { ^ CXX leveldb/util/leveldb_libleveldb_a-options.o CXX leveldb/util/leveldb_libleveldb_a-status.o CXX leveldb/port/leveldb_libleveldb_a-port_posix.o CXX leveldb/helpers/memenv/leveldb_libmemenv_a-memenv.o AR libbitcoin_cli.a CXX bench/bench_bench_mooncoin-bench_bitcoin.o CXX bench/bench_bench_mooncoin-bench.o CXX bench/bench_bench_mooncoin-Examples.o CXX bench/bench_bench_mooncoin-rollingbloom.o CXX bench/bench_bench_mooncoin-crypto_hash.o CXX bench/bench_bench_mooncoin-base58.o CXXLD libbitcoinconsensus.la AR libbitcoin_server.a AR libbitcoin_util.a AR libbitcoin_wallet.a AR leveldb/libleveldb.a AR leveldb/libmemenv.a CXXLD mooncoin-cli CXXLD mooncoin-tx CXXLD mooncoind CXXLD bench/bench_mooncoin make[2]: Leaving directory '/root/mooncoin/src' make[1]: Leaving directory '/root/mooncoin/src' make[1]: Entering directory '/root/mooncoin' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/root/mooncoin' root@moon:~/mooncoin# cd src root@moon:~/mooncoin/src# ./mooncoind -server -deaemon -rpcuser=testuser -rpcpassword=testpassword -rpcbind=127.0.0.1 -rpclallowip=127.0.0.1 Mooncoin server starting root@moon:~/mooncoin/src# tail -fn 100 /root/.mooncoin/debug.log 2018-04-17 05:14:39 keypool added key 32, size=32 2018-04-17 05:14:39 keypool added key 33, size=33 2018-04-17 05:14:39 keypool added key 34, size=34 2018-04-17 05:14:39 keypool added key 35, size=35 2018-04-17 05:14:39 keypool added key 36, size=36 2018-04-17 05:14:39 keypool added key 37, size=37 2018-04-17 05:14:39 keypool added key 38, size=38 2018-04-17 05:14:39 keypool added key 39, size=39 2018-04-17 05:14:39 keypool added key 40, size=40 2018-04-17 05:14:39 keypool added key 41, size=41 2018-04-17 05:14:39 keypool added key 42, size=42 2018-04-17 05:14:39 keypool added key 43, size=43 2018-04-17 05:14:39 keypool added key 44, size=44 2018-04-17 05:14:39 keypool added key 45, size=45 2018-04-17 05:14:39 keypool added key 46, size=46 2018-04-17 05:14:39 keypool added key 47, size=47 2018-04-17 05:14:39 keypool added key 48, size=48 2018-04-17 05:14:39 keypool added key 49, size=49 2018-04-17 05:14:39 keypool added key 50, size=50 2018-04-17 05:14:39 keypool added key 51, size=51 2018-04-17 05:14:39 keypool added key 52, size=52 2018-04-17 05:14:39 keypool added key 53, size=53 2018-04-17 05:14:39 keypool added key 54, size=54 2018-04-17 05:14:39 keypool added key 55, size=55 2018-04-17 05:14:39 keypool added key 56, size=56 2018-04-17 05:14:39 keypool added key 57, size=57 2018-04-17 05:14:39 keypool added key 58, size=58 2018-04-17 05:14:39 keypool added key 59, size=59 2018-04-17 05:14:39 keypool added key 60, size=60 2018-04-17 05:14:39 keypool added key 61, size=61 2018-04-17 05:14:39 keypool added key 62, size=62 2018-04-17 05:14:39 keypool added key 63, size=63 2018-04-17 05:14:39 keypool added key 64, size=64 2018-04-17 05:14:39 keypool added key 65, size=65 2018-04-17 05:14:39 keypool added key 66, size=66 2018-04-17 05:14:39 keypool added key 67, size=67 2018-04-17 05:14:39 keypool added key 68, size=68 2018-04-17 05:14:39 keypool added key 69, size=69 2018-04-17 05:14:39 keypool added key 70, size=70 2018-04-17 05:14:39 keypool added key 71, size=71 2018-04-17 05:14:39 keypool added key 72, size=72 2018-04-17 05:14:39 keypool added key 73, size=73 2018-04-17 05:14:39 keypool added key 74, size=74 2018-04-17 05:14:39 keypool added key 75, size=75 2018-04-17 05:14:39 keypool added key 76, size=76 2018-04-17 05:14:39 keypool added key 77, size=77 2018-04-17 05:14:39 keypool added key 78, size=78 2018-04-17 05:14:39 keypool added key 79, size=79 2018-04-17 05:14:39 keypool added key 80, size=80 2018-04-17 05:14:39 keypool added key 81, size=81 2018-04-17 05:14:39 keypool added key 82, size=82 2018-04-17 05:14:39 keypool added key 83, size=83 2018-04-17 05:14:39 keypool added key 84, size=84 2018-04-17 05:14:39 keypool added key 85, size=85 2018-04-17 05:14:40 keypool added key 86, size=86 2018-04-17 05:14:40 keypool added key 87, size=87 2018-04-17 05:14:40 keypool added key 88, size=88 2018-04-17 05:14:40 keypool added key 89, size=89 2018-04-17 05:14:40 keypool added key 90, size=90 2018-04-17 05:14:40 keypool added key 91, size=91 2018-04-17 05:14:40 keypool added key 92, size=92 2018-04-17 05:14:40 keypool added key 93, size=93 2018-04-17 05:14:40 keypool added key 94, size=94 2018-04-17 05:14:40 keypool added key 95, size=95 2018-04-17 05:14:40 keypool added key 96, size=96 2018-04-17 05:14:40 keypool added key 97, size=97 2018-04-17 05:14:40 keypool added key 98, size=98 2018-04-17 05:14:40 keypool added key 99, size=99 2018-04-17 05:14:40 keypool added key 100, size=100 2018-04-17 05:14:40 keypool added key 101, size=101 2018-04-17 05:14:40 keypool reserve 1 2018-04-17 05:14:40 keypool keep 1 2018-04-17 05:14:40 wallet 525ms 2018-04-17 05:14:40 UpdateTip: hash=bd687cbba.. height=0 diff=1e0ffff0 algo=scrypt ver=0x00000001 log2_work=20.000022 tx=1 date='2013-12-27 15:36:43' prog=0.000000 cache=0.0MiB(0tx) 2018-04-17 05:14:40 mapBlockIndex.size() = 1 2018-04-17 05:14:40 nBestHeight = 0 2018-04-17 05:14:40 setKeyPool.size() = 100 2018-04-17 05:14:40 mapWallet.size() = 0 2018-04-17 05:14:40 mapAddressBook.size() = 1 2018-04-17 05:14:40 init message: Loading addresses... 2018-04-17 05:14:40 torcontrol thread start 2018-04-17 05:14:40 ERROR: Read: Failed to open file /root/.mooncoin/peers.dat 2018-04-17 05:14:40 Invalid or missing peers.dat; recreating 2018-04-17 05:14:40 init message: Loading banlist... 2018-04-17 05:14:40 ERROR: Read: Failed to open file /root/.mooncoin/banlist.dat 2018-04-17 05:14:40 Invalid or missing banlist.dat; recreating 2018-04-17 05:14:40 init message: Starting network threads... 2018-04-17 05:14:40 AddLocal(159.65.131.130:44664,1) 2018-04-17 05:14:40 Discover: IPv4 eth0: 159.65.131.130 2018-04-17 05:14:40 AddLocal([2400:6180:0:d1::2d2:9001]:44664,1) 2018-04-17 05:14:40 Discover: IPv6 eth0: 2400:6180:0:d1::2d2:9001 2018-04-17 05:14:40 dnsseed thread start 2018-04-17 05:14:40 Loading addresses from DNS seeds (could take a while) 2018-04-17 05:14:40 init message: Done loading 2018-04-17 05:14:40 opencon thread start 2018-04-17 05:14:40 msghand thread start 2018-04-17 05:14:40 net thread start 2018-04-17 05:14:40 addcon thread start 2018-04-17 05:14:41 0 addresses found from DNS seeds 2018-04-17 05:14:41 dnsseed thread exit root@moon:~/mooncoin/src#
|
|
|
|