bitcoinxt / bitcoinxt Goto Github PK

Bitcoin XT. Most recent release is K.

License: MIT License

Shell 0.76% QMake 0.03% Python 13.62% Makefile 1.47% C++ 69.13% C 10.21% HTML 0.72% CSS 0.02% Objective-C++ 0.10% Java 0.43% Objective-C 0.31% M4 2.55% Roff 0.26% Assembly 0.40%

bitcoinxt's Introduction

Bitcoin XT

Bitcoin XT is an implementation of a Bitcoin Cash (BCH) full node that embraces Bitcoin's original vision of simple, reliable, low-cost transactions for everyone in the world. Bitcoin XT originated as a series of patches on top of Bitcoin Core and is now a independently maintained software fork. See some selected features.

Bitcoin XT downloads are code signed and are built reproducibly using gitian. Discussion can be found at the XT Gitter.

Data Directory Compatibility

If using a data directory from a different BCH or BTC full node, specify -reindex on first launch.

Set aside wallet.dat from Bitcoin Core or Bitcoin ABC (reason: HD wallet not yet supported). Also delete fee_estimates.dat from these clients.

Bitcoin XT can run in BTC chain mode by specifying -uahftime=0. Please note that Bitcoin XT does not validate segwit, and the conversion notes above still apply.

Development process

Ideas for useful features are tracked in Issues. Pull requests from developers, including well-done cherry picks from other clients or cryptos, are very welcome.

To discuss Bitcoin Cash development in general, you are welcome to use the mailing list.

We have a manifesto that lays out things we believe are important, which you can read about here:

https://bitcoinxt.software/

bitcoinxt's People

Contributors

Stargazers

Watchers

Forkers

dgenr8 aalness chrisfranko hasimir codehalo davidajohnston rubensayshi rebroad gavinandresen mikehearn superscud ptschip kleetus seweso xtbit lismore programerone redpola nathan-at-least shenckel thesoftwarejedi baero gazbert odemolliens andres-root rrobukef jisr jlopp drwasho dagurval roughpandaz icede keo bitcoinsulting rromanchuk isghe cryptarc pradeeproark royosherove thenicholasnick gandrewstone habibmasuro jonghyeopkim ekankyesme priestc jtoomim thetimpotter keyvanjs blinkystitt har01d tadasvaranavicius error10 invisible-college jameshilliard patpenetrante dgmib compumatrix bryceweiner sebrandon1 nietzschetmh pulman4973 bradfrost1 test-betta-inc gvsurenderreddy rjaugust krzysiekj shojayxt almoharebh sndesign rimmington simulationcoin psdgithub michaelporterconsulting shnici allandoensen freewing-jp banglykim deadalnix jheathco ajinkya93 slamj1 coinstash izyp chgrp-hung dwijen peauge saisandeepvuppala robzhang2017 sramos30 qtlab sibbstar lixiandai bblrd mexicoin dogs4ever jack-sdabi 21commuter noonarai echterago avik13

bitcoinxt's Issues

bitcoinxt broadcasts my ipv6 address when running with tor

I am running bitcoinxt through a tor proxy on osx, but I have just noticed that even though my ipv4 address is hidden by tor, that there is a client connected to my real ipv6 address.

For info, I am running osx 10.10.5, tor 0.2.6.10, bitcoinxt v0.11.0.0-30017c1, and I have the following in my bitcoin.conf file:

proxy=127.0.0.1:9050
onion=127.0.0.1:9050
listen=1
discover=1

Enable pruning during node creation from latest check block

When setting up a new BitcoinXT node, it's required to download all the blocks from the genesis block. Once everything is caught up, then you can restart your node with -prune=550 in order to prune the old blocks and allow the node to use less hard drive space.

In order to allow BitcoinXT to be spread far-and-wide, we should allow new nodes to start with pruning from the first step by contacting several other nodes to determine the latest checkpoint block that's older than the minimum pruning age. Then we can start building the chain from that block.

This will allow smaller VPS's to set up BitcoinXT nodes.

Also, I'm unfamiliar with the reasoning for the 550 limit. Is it worth re-evaluating that number as the absolute number of minimum blocks?

Misbehaving nodes against XT

Feel free to close, would be nice to have a working document (gist?) where we could keep track of some of these hosts.

37.187.136.15

Undocumented dependency on libcurl in 0.11A

bitconxt-0.11A appears to have a dependency on libcurl. When executing ./autogen.sh && ./configure:

...
checking for CURL... no
configure: error: libcurl not found

This dependency is not present in bitcoin core nor in bitcoinxt-0.10.2A as far as I can tell.

The dependency is not documented in docs/build-unix.md. This is a problem because Unix systems typically have a choice of three different libcurl-dev packages and there is no indication of which I should use:

libcurl4-gnutls-dev - development files and documentation for libcurl (GnuTLS flavour)
libcurl4-nss-dev - development files and documentation for libcurl (NSS flavour)
libcurl4-openssl-dev - development files and documentation for libcurl (OpenSSL flavour)

Switch to disable tor group download and anti-dos scheduling

As outlined in this comment:
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010379.html
the automatic download of tor exit nodes has serious privacy concerns, and should be disabled by default.

Is it possible to completely disable the use of anti-DoS resource scheduling via a commandline switch or configuration setting?

The complete text of the original comment follows:

Bitcoin XT contains an unmentioned addition which periodically downloads
lists of Tor IP addresses for blacklisting, this has considerable privacy
implications for hapless users which are being prompted to use the
software. The feature is not clearly described, is enabled by default, and
has a switch name which intentionally downplays what it is doing
(disableipprio). Furthermore these claimed anti-DoS measures are trivially
bypassed and so offer absolutely no protection whatsoever.

Connections are made over clearnet even when using a proxy or onlynet=tor,
which leaks connections on the P2P network with the real location of the
node. Knowledge of this traffic along with uptime metrics from
bitnodes.io can allow observers to easily correlate the location and
identity of persons running Bitcoin nodes. Denial of service can also be
used to crash and force a restart of an interesting node, which will cause
them to make a new request to the blacklist endpoint via the clearnet on
relaunch at the same time their P2P connections are made through a proxy.
Requests to the blacklisting URL also use a custom Bitcoin XT user agent
which makes users distinct from other internet traffic if you have access
to the endpoints logs.

GUI unable to launch on Arch with Cinnamon

On initial launch if you set the client to start with system then reboot no applet is visible. Launching from menu then tells you that a lock can not be established.

I fixed this temporarily using top and finding the PID and executing kill XXX and launching BitcoinXT manually from the menu and unselecting start with system.

I installed via yaourt -S bitcoinxt-gui-git from the AUR https://aur.archlinux.org/packages/bitcoinxt-gui-git/

0.10 Final Mac DMG is corrupt

I tried to download and install the 0.10 Final DMG but upon unpacking and attempting to run, OSX reports it is corrupt. The RC version runs without error.

add an auto-kick to strange client (steal upload bandwith, no synchro. evolution)

In this example, i have a strange client with an old client revision (or fake ... ?).
The blocks synchro. don't up to actual number of block ... but it sucks all my upload bandwidth for nothing.

Can you implement an auto-kick feature to liberate the connexion from this "problem" ?
Like : if block number don't rise after 10 min but uploaded size is more than 3 blocks = kick.

to complete the proof, here is a good client :

Prevent App Nap Check box missing on OSX build

I'm having problems with the node going to sleep on OSX 10.10, Basically it stops updating when the mac-book goes into sleep mode and the node becomes unreachable. In Core there is an option Prevent App Nap Checkbox that comes up on the app Get Info screen, this solved the problem in the past however that check box is not available in the XT osx app.

Enable bountysource contribution.

Given the recent block size issues and Gavin's message, I would like to show support by contributing some funds to this project.

Currently contributions are disabled and it would be nice if this changed.

https://www.bountysource.com/teams/bitcoinxt

README.md doesn't mention ip prioritization changes

Currently it contains the following additional changes:

I think the text from https://bitcoinxt.software/patches.html regarding Anti-DOS patches would suffice.

Not installing properly from apt repository

Error message as follows:

Unpacking bitcoinxt (0.11A) ...
dpkg: error processing archive /var/cache/apt/archives/bitcoinxt_0.11A_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/bitcoin-qt', which is also in package bitcoin-qt 0.11.0-trusty1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/bitcoinxt_0.11A_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Ubuntu 14.04. installation issue: error processing the archive

I currently have BitcoinQT installed and I get an error when I try to install BitcoinXT with apt-get on Ubuntu 14.04. Should I remove BitcoinQT first? (I am afraid to lose the already downloaded blockchain if I do that.) This is the error message:

dpkg: error processing the archive /var/cache/apt/archives/bitcoinxt_0.11A_amd64.deb (--unpack):
  Attempt to "/ usr / bin / bitcoin-qt" to overwrite that bitcoin-qt is also in package 0.11.0-trusty1
dpkg-deb: error: Insert sub-process was (interrupted data transfer (broken pipe)) by signal killed
Errors were encountered while processing:
  /var/cache/apt/archives/bitcoinxt_0.11A_amd64.deb
E: Sub-process / usr / bin / dpkg returned on error code (1)

Implement SIGHASH_WITHINPUTVALUE

This would make life SO MUCH easier for all hardware wallets and software wallets that don't have access to the full blockchain.

Bitcointalk discussion: https://bitcointalk.org/index.php?topic=181734.0
Bitcoin-dev discussion: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-January/007185.html

Will there be an update to libsecp256k1?

"Block size should be raised, but only in step with can reasonably be accomplished with engineering improvements to ensure a decentralized, policy neutral network. All that we ask for is the time for due process, not ultimatums and hostile forks"

-------- EDIT --------
I just dont want to see the Bitcoin Community fighting with each other, as I said in the IRC channel "just try to convince people and calm things. WE NEED A UNITED COMMUNITY!"

I dont care if blocks are 1MB, 8MB or 21MB, I just want peace.

Tags/commits aren't PGP signed

Should be following best-practice used by parent Bitcoin Core project.

Checksums for sources do not match

Downloading the source archive from this link:
https://github.com/bitcoinxt/bitcoinxt/releases
https://github.com/bitcoinxt/bitcoinxt/archive/v0.11B.tar.gz
Gives me a sha256sum of:
f9fa35a0996d8b8b4eb20d77087b4463d84dc907124b73250cd82e81eed38139 bitcoinxt-0.11B.tar.gz

Whereas, the signed Gitian assert files claim the source sha256sum should be:
https://github.com/bitcoinxt/gitian.sigs/blob/master/0.11B-linux/gavinandresen/bitcoin-linux-0.11-build.assert
4af0c59de2c5d46ca250cb8b95877eae98298abfa52e9e90c71f7f785219aa6e src/bitcoin-xt-0.11.0-B.tar.gz

I suspect this is because the source archive is being generated by Github, which is somehow different from the sources being used by Gitian. If possible, I would like to get the source tar.gz that has been signed.

Thank you!

75% consensus too risky?

Hello,

It's a good idea to put the hard fork to a vote, but why was 75% chosen? It may appear to be a high majority, but 25% of miners disagreeing could mean a significant opposition. Even though they would be a minority, couldn't they still cause a vocal opposition? Maybe a significant number of people would maintain a legacy chain and perhaps brand it as the "True Bitcoin". It's not only miners but a hard fork needs users to be OK with it as well, though I would assume most people would just go along with it without any concern.

I'm not saying 75% is a bad idea, but I'd like to know what reasoning has gone behind that number, and if there have been other considerations about non-miner user consensus.

I do agree though that the blocksize should be increased.

Matthew

Mempool size protection improvements for current flooding style

@gavinandresen wrote in #56:

Implement a simple strategy to keep the memory pool from consuming
all of memory, by limiting the number of tranasctions stored in
the memory pool.

Today there was a flooding of the mempool that didn't rely on the amount of transactions but instead used 500 inputs to bloat each transaction to ~73kb and using a 1 satoshi/byte fee to have it linger around long. Resulting in peaks of ~48mb of mempool even though the backlog didn't go far above 3500 TX (even in between 50min blocks). For reference, plenty of the 1MB blocks saw >2200 TX (example).

Had this "tester" decided to generate these at a faster rate this could have incurred a lot more RAM usage while keeping TX count small. And a smaller bad TX : good TX ratio means higher odds the random removal will find a legitimate TX.

Perhaps an additional setting that limits the maximum mempool total size should be added to trigger a random remove besides just -maxmempooltx. For example -maxmempoolsize=4096 to set a 4096KB limit.

Note that blockchain.info instead decided to reject the TX completely:

Transaction rejected by our node. Reason:
The Maximum number of inputs in a single transaction is 200

But that is an option I believe would need to be part of the protocol to sanely enforce.

Instead, perhaps large input TX like these should be written to disk after we're done propagating it to not rely on RAM as it could be a while before these are taken up into a block. Recent fee estimation code could help decide if it's worth the I/O too, writing out large TX with low odds of making it into the next block.

ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large

It is almost certainly an upstream issue and has been (posted here)[https://github.com/bitcoin/bitcoin/issues/5668] but I will post a note here, close it and then tell them about it as well.

It is annoying because my lighthouse server went out of sync twice now. (not for long, still annoying though, I need to setup daemontools)

0.11B debian build autostarts, but not documented that way

Near the bottom of https://bitcoinxt.software/apt.html

Note that the server binary is named "bitcoinxt" in this package,
not bitcoind. There are no init scripts or other such things installed,
so please be aware that the node will not be started, and if you do
an apt-get upgrade, you will have to restart the server yourself for
the update to take effect.

But since 0.11B it actually does auto-start when you've got systemd.
In fact it even auto-restarts. Which is confusing when you're not expecting it.

I'm not sure what the intended behaviour is, but either should be updated to be consistent.

0.11B and only-bigblocks branches aren't compiling after miniupnpc update

Compilation appears to fail after miniupnpc update. Core latest Git master branch is building fine.

https://aur.archlinux.org/packages/bitcoinxt-git/
https://aur.archlinux.org/packages/bitcoinxt-only-bigblocks-git/

0.11B:

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_DIRS, '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'
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /bin/automake line 3936.
configure.ac:10: installing 'build-aux/compile'
configure.ac:5: installing 'build-aux/config.guess'
configure.ac:5: installing 'build-aux/config.sub'
configure.ac:9: installing 'build-aux/install-sh'
configure.ac:9: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
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_DIRS, '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'
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /bin/automake line 3936.
configure.ac:54: installing 'build-aux/compile'
configure.ac:17: installing 'build-aux/config.guess'
configure.ac:17: installing 'build-aux/config.sub'
configure.ac:27: installing 'build-aux/install-sh'
configure.ac:27: installing 'build-aux/missing'
Makefile.am:5: warning: user variable 'GZIP_ENV' defined here ...
/usr/share/automake-1.15/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here
Makefile.am:55: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.15/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am: installing 'build-aux/depcomp'
src/Makefile.am:420: warning: user target '.mm.o' defined here ...
/usr/share/automake-1.15/am/depend2.am: ... overrides Automake target '.mm.o' defined here
parallel-tests: installing 'build-aux/test-driver'
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
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 for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... 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... /bin/ld
checking if the linker (/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /bin/nm -B
checking the name lister (/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
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 /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 /bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : 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 (/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++ -E
checking for ld used by g++... /bin/ld -m elf_x86_64
checking if the linker (/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/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 (/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... /bin/ar
checking for ranlib... /bin/ranlib
checking for strip... /bin/strip
checking for gcov... /bin/gcov
checking for lcov... no
checking for java... /bin/java
checking for genhtml... no
checking for git... /bin/git
checking for ccache... no
checking for xgettext... /bin/xgettext
checking for hexdump... /bin/hexdump
checking for pkg-config... /bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if 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 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 for library containing getaddrinfo_a... -lanl
checking for library containing inet_pton... none required
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 library containing clock_gettime... none required
checking for visibility attribute... yes
checking miniupnpc/miniwget.h usability... yes
checking miniupnpc/miniwget.h presence... yes
checking for miniupnpc/miniwget.h... yes
checking for main in -lminiupnpc... yes
checking miniupnpc/miniupnpc.h usability... yes
checking miniupnpc/miniupnpc.h presence... yes
checking for miniupnpc/miniupnpc.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnpcommands.h usability... yes
checking miniupnpc/upnpcommands.h presence... yes
checking for miniupnpc/upnpcommands.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnperrors.h usability... yes
checking miniupnpc/upnperrors.h presence... yes
checking for miniupnpc/upnperrors.h... yes
checking for main in -lminiupnpc... (cached) yes
checking whether to build Bitcoin Core GUI... no (Qt)
checking for boostlib >= 1.20.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 SSL... yes
checking for CRYPTO... yes
checking for CURL... yes
checking for RAND_egd in -lcrypto... yes
checking openssl/ec.h usability... yes
checking openssl/ec.h presence... yes
checking for openssl/ec.h... yes
checking whether to build bitcoind... yes
checking whether to build utils (bitcoin-cli bitcoin-tx)... yes
checking whether to build libraries... yes
checking if ccache should be used... no
checking if wallet should be enabled... no
checking whether to build with support for UPnP... yes
checking whether to build with UPnP enabled by default... no
checking whether to build test_bitcoin... 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 src/test/buildenv.py
config.status: creating qa/pull-tester/run-bitcoind-for-test.sh
config.status: creating qa/pull-tester/tests-config.sh
config.status: creating src/config/bitcoin-config.h
config.status: executing depfiles commands
config.status: executing libtool commands
=== configuring in src/secp256k1 (/home/user/Projects/aur4/bitcoinxt/src/bitcoinxt-0.11B/src/secp256k1)
configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr'  '--sbindir=/usr/bin' '--libexecdir=/usr/lib/bitcoin' '--sysconfdir=/etc' '--sharedstatedir=/usr/share/bitcoin' '--localstatedir=/var/lib/bitcoin' '--enable-hardening' '--with-gui=no' '--disable-wallet' '--with-gnu-ld' 'CXXFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4' 'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro' 'CPPFLAGS=-D_FORTIFY_SOURCE=2' 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4' '--disable-shared' '--with-pic' '--with-bignum=no' --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... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
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... /bin/ld
checking if the linker (/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /bin/nm -B
checking the name lister (/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
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 /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 /bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : 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 (/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... /bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for ar... /bin/ar
checking for ranlib... /bin/ranlib
checking for strip... /bin/strip
checking for gcc option to accept ISO C89... (cached) none needed
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 for __int128... yes
checking for __builtin_expect... yes
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 whether byte ordering is bigendian... no
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
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.
Making all in src
make[1]: Entering directory '/home/user/Projects/aur4/bitcoinxt/src/bitcoinxt-0.11B/src'
make[2]: Entering directory '/home/user/Projects/aur4/bitcoinxt/src/bitcoinxt-0.11B/src'
  CXX      crypto/libbitcoinconsensus_la-hmac_sha512.lo
  CXX      crypto/libbitcoinconsensus_la-ripemd160.lo
  CXX      crypto/libbitcoinconsensus_la-sha1.lo
  CXX      crypto/libbitcoinconsensus_la-sha256.lo
  CXX      crypto/libbitcoinconsensus_la-sha512.lo
  CXX      libbitcoinconsensus_la-eccryptoverify.lo
  CXX      libbitcoinconsensus_la-ecwrapper.lo
  CXX      libbitcoinconsensus_la-hash.lo
  CXX      primitives/libbitcoinconsensus_la-transaction.lo
  CXX      libbitcoinconsensus_la-pubkey.lo
  CXX      script/libbitcoinconsensus_la-bitcoinconsensus.lo
  CXX      script/libbitcoinconsensus_la-interpreter.lo
  CXX      script/libbitcoinconsensus_la-script.lo
  CXX      libbitcoinconsensus_la-uint256.lo
  CXX      libbitcoinconsensus_la-utilstrencodings.lo
  CXXLD    libbitcoinconsensus.la
/bin/ar: `u' modifier ignored since `D' is the default (see `U')
  CXX      bitcoind-bitcoind.o
  CXX      libbitcoin_server_a-addrman.o
  CXX      libbitcoin_server_a-alert.o
  CXX      libbitcoin_server_a-bloom.o
  CXX      libbitcoin_server_a-chain.o
  CXX      libbitcoin_server_a-checkpoints.o
  CXX      libbitcoin_server_a-init.o
  CXX      libbitcoin_server_a-ipgroups.o
  CXX      libbitcoin_server_a-leveldbwrapper.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
net.cpp: In function ‘void ThreadMapPort()’:
net.cpp:1060:74: error: invalid conversion from ‘int*’ to ‘unsigned char’ [-fpermissive]
     devlist = upnpDiscover(2000, multicastif, minissdpdpath, 0, 0, &error);
                                                                          ^
net.cpp:1060:74: error: too few arguments to function ‘UPNPDev* upnpDiscover(int, const char*, const char*, int, int, unsigned char, int*)’
In file included from net.cpp:28:0:
/usr/include/miniupnpc/miniupnpc.h:62:1: note: declared here
 upnpDiscover(int delay, const char * multicastif,
 ^
Makefile:3672: recipe for target 'libbitcoin_server_a-net.o' failed
make[2]: *** [libbitcoin_server_a-net.o] Error 1
make[2]: Leaving directory '/home/user/Projects/aur4/bitcoinxt/src/bitcoinxt-0.11B/src'
Makefile:6552: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/Projects/aur4/bitcoinxt/src/bitcoinxt-0.11B/src'
Makefile:631: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

bigblocks-only:

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_DIRS, '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'
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /bin/automake line 3936.
configure.ac:10: installing 'build-aux/compile'
configure.ac:5: installing 'build-aux/config.guess'
configure.ac:5: installing 'build-aux/config.sub'
configure.ac:9: installing 'build-aux/install-sh'
configure.ac:9: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
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_DIRS, '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'
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /bin/automake line 3936.
configure.ac:52: installing 'build-aux/compile'
configure.ac:15: installing 'build-aux/config.guess'
configure.ac:15: installing 'build-aux/config.sub'
configure.ac:25: installing 'build-aux/install-sh'
configure.ac:25: installing 'build-aux/missing'
Makefile.am:5: warning: user variable 'GZIP_ENV' defined here ...
/usr/share/automake-1.15/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here
Makefile.am:55: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.15/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am: installing 'build-aux/depcomp'
src/Makefile.am:417: warning: user target '.mm.o' defined here ...
/usr/share/automake-1.15/am/depend2.am: ... overrides Automake target '.mm.o' defined here
parallel-tests: installing 'build-aux/test-driver'
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
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 for g++... g++
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... 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... /bin/ld
checking if the linker (/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /bin/nm -B
checking the name lister (/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
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 /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 /bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : 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 (/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++ -E
checking for ld used by g++... /bin/ld -m elf_x86_64
checking if the linker (/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/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 (/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... /bin/ar
checking for ranlib... /bin/ranlib
checking for strip... /bin/strip
checking for gcov... /bin/gcov
checking for lcov... no
checking for java... /bin/java
checking for genhtml... no
checking for git... /bin/git
checking for ccache... no
checking for xgettext... /bin/xgettext
checking for hexdump... /bin/hexdump
checking for pkg-config... /bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether byte ordering is bigendian... no
checking if compiler needs -Werror to reject unknown flags... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if 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 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 for library containing getaddrinfo_a... -lanl
checking for library containing inet_pton... none required
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 library containing clock_gettime... none required
checking for visibility attribute... yes
checking miniupnpc/miniwget.h usability... yes
checking miniupnpc/miniwget.h presence... yes
checking for miniupnpc/miniwget.h... yes
checking for main in -lminiupnpc... yes
checking miniupnpc/miniupnpc.h usability... yes
checking miniupnpc/miniupnpc.h presence... yes
checking for miniupnpc/miniupnpc.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnpcommands.h usability... yes
checking miniupnpc/upnpcommands.h presence... yes
checking for miniupnpc/upnpcommands.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnperrors.h usability... yes
checking miniupnpc/upnperrors.h presence... yes
checking for miniupnpc/upnperrors.h... yes
checking for main in -lminiupnpc... (cached) yes
checking whether to build Bitcoin Core GUI... no (Qt)
checking for boostlib >= 1.20.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 SSL... yes
checking for CRYPTO... yes
checking for RAND_egd in -lcrypto... yes
checking openssl/ec.h usability... yes
checking openssl/ec.h presence... yes
checking for openssl/ec.h... yes
checking whether to build bitcoind... yes
checking whether to build utils (bitcoin-cli bitcoin-tx)... yes
checking whether to build libraries... yes
checking if ccache should be used... no
checking if wallet should be enabled... no
checking whether to build with support for UPnP... yes
checking whether to build with UPnP enabled by default... no
checking whether to build test_bitcoin... 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 src/test/buildenv.py
config.status: creating qa/pull-tester/run-bitcoind-for-test.sh
config.status: creating qa/pull-tester/tests-config.sh
config.status: creating src/config/bitcoin-config.h
config.status: executing depfiles commands
config.status: executing libtool commands
=== configuring in src/secp256k1 (/home/user/.src/bitcoinxt-only-bigblocks-git/src/bitcoinxt/src/secp256k1)
configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr'  '--sbindir=/usr/bin' '--libexecdir=/usr/lib/bitcoin' '--sysconfdir=/etc' '--sharedstatedir=/usr/share/bitcoin' '--localstatedir=/var/lib/bitcoin' '--enable-hardening' '--with-gui=no' '--disable-wallet' '--with-gnu-ld' 'CXXFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4' 'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro' 'CPPFLAGS=-D_FORTIFY_SOURCE=2' 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4' '--disable-shared' '--with-pic' '--with-bignum=no' --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... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
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... /bin/ld
checking if the linker (/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /bin/nm -B
checking the name lister (/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
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 /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 /bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : 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 (/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... /bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for ar... /bin/ar
checking for ranlib... /bin/ranlib
checking for strip... /bin/strip
checking for gcc option to accept ISO C89... (cached) none needed
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 for __int128... yes
checking for __builtin_expect... yes
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 whether byte ordering is bigendian... no
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
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.
Making all in src
make[1]: Entering directory '/home/user/.src/bitcoinxt-only-bigblocks-git/src/bitcoinxt/src'
make[2]: Entering directory '/home/user/.src/bitcoinxt-only-bigblocks-git/src/bitcoinxt/src'
  CXX      crypto/libbitcoinconsensus_la-hmac_sha512.lo
  CXX      crypto/libbitcoinconsensus_la-ripemd160.lo
  CXX      crypto/libbitcoinconsensus_la-sha1.lo
  CXX      crypto/libbitcoinconsensus_la-sha256.lo
  CXX      crypto/libbitcoinconsensus_la-sha512.lo
  CXX      libbitcoinconsensus_la-eccryptoverify.lo
  CXX      libbitcoinconsensus_la-ecwrapper.lo
  CXX      libbitcoinconsensus_la-hash.lo
  CXX      primitives/libbitcoinconsensus_la-transaction.lo
  CXX      libbitcoinconsensus_la-pubkey.lo
  CXX      script/libbitcoinconsensus_la-bitcoinconsensus.lo
  CXX      script/libbitcoinconsensus_la-interpreter.lo
  CXX      script/libbitcoinconsensus_la-script.lo
  CXX      libbitcoinconsensus_la-uint256.lo
  CXX      libbitcoinconsensus_la-utilstrencodings.lo
  CXXLD    libbitcoinconsensus.la
/bin/ar: `u' modifier ignored since `D' is the default (see `U')
  CXX      bitcoind-bitcoind.o
  CXX      libbitcoin_server_a-addrman.o
  CXX      libbitcoin_server_a-alert.o
  CXX      libbitcoin_server_a-bloom.o
  CXX      libbitcoin_server_a-chain.o
  CXX      libbitcoin_server_a-checkpoints.o
  CXX      libbitcoin_server_a-init.o
  CXX      libbitcoin_server_a-leveldbwrapper.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
net.cpp: In function ‘void ThreadMapPort()’:
net.cpp:1015:74: error: invalid conversion from ‘int*’ to ‘unsigned char’ [-fpermissive]
     devlist = upnpDiscover(2000, multicastif, minissdpdpath, 0, 0, &error);
                                                                          ^
net.cpp:1015:74: error: too few arguments to function ‘UPNPDev* upnpDiscover(int, const char*, const char*, int, int, unsigned char, int*)’
In file included from net.cpp:27:0:
/usr/include/miniupnpc/miniupnpc.h:62:1: note: declared here
 upnpDiscover(int delay, const char * multicastif,
 ^
Makefile:3635: recipe for target 'libbitcoin_server_a-net.o' failed
make[2]: *** [libbitcoin_server_a-net.o] Error 1
make[2]: Leaving directory '/home/user/.src/bitcoinxt-only-bigblocks-git/src/bitcoinxt/src'
Makefile:6487: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/.src/bitcoinxt-only-bigblocks-git/src/bitcoinxt/src'
Makefile:627: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Bitcoin classic support

Is it coming / possible?

Create and test script to convert from Bitcoin Core to Bitcoin XT

Since BitcoinXT and Bitcoin Core are so similar in operation until a big block fork, in theory the database schema should be compatible.

I do not have a Bitcoin Core instance to test with, but it would be a good idea to test the following procedure

Stop bitcoind
Replace bitcoin binaries with bitcoinxt binaries
Restart daemon
Let BitcoinXT pick up where Bitcoin Core left off

If this does work, it might be good to write a good script to accomplish this in an automated way that can be executed like

wget https://raw.githubusercontent.com/bitcoinxt/bitcoinxt/master/upgrade_from_core.sh | sh

wget https://bitcoinxt.software/upgrade | sh

If we make it so a single line can convert Bitcoin Core to Bitcoin XT in a few moments, we might see an increase of people switching implementations.

If there is support for this concept, I can put together the upgrade script and test it.

link maxmempooltx to ping of RPC server.

Hello,
SPAM network is great to find somes setting to automate the purge system of the maxmempooltx.

So, i use P2Pool with a Bitcoin XT node in server/deamon enabled.
When i hit SPAM traffic, my bitcoin RPC don't answer to the P2Pool process (linked to ASIC machines).

maxmempooltx work great (like 500-1000-2000-3000) in SPAM period, but the mempool size can be less than 1Mb of block when the SPAM don't exist.

can you link the value of the maxmempooltx to a ping command on the RPC bitcoin ?

or, other possibility : monitoring the CPU usage (like when CPU usage is 100% in 10 second = decrease the maxmempooltx ... and the user can choose the range like 500-50 000 and the time of the 100% CPU).

or something like that. :)

Other capture to see the others setting and debug.log

And final capture when the CPU is free and the manual limite of maxmempooltx is to low to create a 1Mb block.
That's i would want a automated maxmempooltx linked to something like the CPU or the ping of the RPC server (latency).

Somes couple of days after ... i have retry to move the limit of this setting but CPU of my node always saturate with the 2500 setting :

And the global of the bitcoind latency from the P2Pool process.

Activity Monitor reports process in OS X as "Bitcoin-Qt"

Present in OS X with v0.10.1.0-7dd901c.

Shouldn't this be changed to be "Bitcoin-XT", or is there a reason for it being "Bitcoin-Qt"?

No .sig file for (at least) Bitcoin.XT.0.10.1.dmg

Just as the title says - there is no .sig file to verify the download of Bitcoin.XT.0.10.1.dmg. As I am unsure of how to otherwise build Bitcoin XT, this is the method that I want to use, but I want to be able to GPG verify the download.

I have not checked if there is a lack of .sig files for other downloads too, I just noticed it for the Bitcoin.XT.0.10.1.dmg download.

Potentially outdated example bitcoin.conf file?

The bitcoin.conf file (bitcoinxt/contrib/debian/examples/bitcoin.conf) looks like it might be outdated. It was last updated on March 21, and the one in the Bitcoin Core repo (https://github.com/bitcoin/bitcoin/blob/master/contrib/debian/examples/bitcoin.conf) was updated on September 22. There are differences between the Core and XT example bitcoin.conf files currently. And the XT bitcoin.conf file might need to be changed to better fit XT ideas.

Getting an issue in my docker build using 0.11C

Setting up bitcoinxt (0.11C) ...
[91mdebconf: unable to initialize frontend: Dialog 
[0m [91mdebconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline
[0m [91mdebconf: unable to initialize frontend: Readline
[0m [91mdebconf: (This frontend requires a controlling tty.) 
[0m [91mdebconf: falling back to frontend: Teletype
[0m [91madduser: The user `bitcoin' already exists. Exiting. 
[0m [91mdpkg: error processing package bitcoinxt (--configure): subprocess installed post-installation script returned error exit status 1 
[0m Processing triggers for libc-bin (2.19-0ubuntu6.6) ... 
[91mErrors were encountered while processing: bitcoinxt

Any idea what's going wrong? Didn't have this problem with 0.11B.

0.11D bip65-cltv test failure: JSONRPC error: CreateNewBlock(): TestBlockValidity failed

Running 2nd level testscript bip65-cltv.py...
  File "/builddir/build/BUILD/bitcoinxt-0.11D/qa/rpc-tests/test_framework/test_framework.py", line 118, in main
    self.run_test()
  File "/builddir/build/BUILD/bitcoinxt-0.11D/qa/rpc-tests/bip65-cltv.py", line 31, in run_test
    self.nodes[1].generate(10)
  File "/builddir/build/BUILD/bitcoinxt-0.11D/qa/rpc-tests/test_framework/authproxy.py", line 126, in __call__
    raise JSONRPCException(response['error'])
Initializing test directory /tmp/testHaj57g
JSONRPC error: CreateNewBlock(): TestBlockValidity failed
Stopping nodes
Cleaning up
Failed

Possibly related to #93

Clarify policy on consensus deviation from Bitcoin-Core.

When I first read about this project some time ago the synopsis I was left with was along the lines of "Bitcoin-XT improves networking and other implementation aspects of Bitcoin while being consensus compatible." So I imagined, maybe there's an "XT backbone" that core nodes can't understand, but the blocks flowing between that network and the mainstream network were all part of the blockchain.

In recent discussions around block size, it sounds like the max blocksize may be increased in Bitcoin-XT. I believe this would deviate from consensus in the mainnet, and introduce a hard fork if deployed.

Could we add some documentation near the top of the README about Xt's consensus policy?

Am I mistaken in that Xt doesn't actually ever connect to the production network?

Are consensus deviating changes only on development or test branches and/or a test net?

Supporting BIP65

Adoption of BIP65 has been started and around 1/5 of miners are now mining v4 blocks. XT should merge BIP65 as soon as possible

Startup info box image pixelation

OS: OS X 10.10.4
XT: v0.11.0.0-2b918be

The XT logo image in the startup page (with "Activating best chain...", etc.) is rather pixelated.

You can also faintly see the square outline of the background of the logo image.

These obviously aren't very high priority issues, but it would be one very easy way to enhance the software. It would also make a better first impression of the app.

Fork Bitcoin Core explicitly

Bitcoin XT, while being a fork of Bitcoin Core, isn't considered as one by GitHub. Unfortunally this prevents comparing the changes made to Bitcoin XT, for example via GitHub's fork compare/pull request mechanism, which is handy to answer the question: "what exactly is the diff between XT and Core?"

If this wasn't intentional, then I suggest to fork the upstream project explicitly.

0.11B - many UPnP messages

At regular intervals the UPnP mapping seems to be done again. This is rather unexpected behaviour for me. I would have expected this at startup / shutdown, and perhaps if some network unreachable events occur.

However, this seems to happen at about 20 minute intervals.

2015-09-14 09:26:14 progress=0.999999 cache=51.7MiB(10478tx)
2015-09-14 09:34:46 Pre-allocating up to position 0xa00000 in rev00352.dat
2015-09-14 09:34:46 UpdateTip: new best=0000000000000000033ac13d7f4d3defee41e0ce2c34d1b190a88a582c595f91 height=374475 log2_work=83.34495 tx=83660397 date=2015-09-14 09:33:54 progress=0.999999 cache=64.7MiB(16762tx)
2015-09-14 09:38:53 UPnP Port Mapping successful.
2015-09-14 09:58:53 UPnP Port Mapping successful.
2015-09-14 10:09:07 UpdateTip: new best=000000000000000004260f338d0c65ff887d50320864e148e172201cdbc3866e height=374476 log2_work=83.344979 tx=83662582 date=2015-09-14 10:12:50 progress=1.000003 cache=43.5MiB(10704tx)
2015-09-14 10:18:53 UPnP Port Mapping successful.
2015-09-14 10:25:20 UpdateTip: new best=000000000000000003783910316c65a836a613c62ed625dd639c7cc25c6d8c5e height=374477 log2_work=83.345007 tx=83664123 date=2015-09-14 10:24:31 progress=0.999999 cache=59.4MiB(14948tx)
2015-09-14 10:26:52 UpdateTip: new best=00000000000000000ac9616939732fef37fcf40f25ab99fd35042973a5ea3255 height=374478 log2_work=83.345036 tx=83664292 date=2015-09-14 10:26:06 progress=0.999999 cache=7.4MiB(956tx)
2015-09-14 10:38:53 UPnP Port Mapping successful.

Tunnel Tor IP download connections through the same proxy as the overall bitcoin connections.

From here

TL;DR: By downloading Tor IPs in cleartext always we can accidentally leak the real IP of someone operating from behind Tor. Not good.

I may have the time to make a pull request to fix this. Alternatively disabling the lookup if any proxy/tor options are enabled would fix the issue.

bitcoind crashed on Initializing databases phase

OS: Linux Mint 17.1 Rebecca
Kernel: 3.14.39-031439-generic #201504211206 SMP Tue Apr 21 11:09:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

I compiled from latest source and it compiled ok.
./configure --disable-wallet --without-gui
make -j2

But when I launched bitcoind binary, it crashed immediately every time to:

"bitcoind: main.cpp:1983: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed."

2016-01-18 11:56:48 Bitcoin XT version v0.11.0D-b504e06 (2015-12-07 12:54:51 +0100)
2016-01-18 11:56:48 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2016-01-18 11:56:48 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2016-01-18 11:56:48 Default data directory /home/jepu/.bitcoin
2016-01-18 11:56:48 Using data directory /home/jepu/.bitcoin
2016-01-18 11:56:48 Using config file /home/jepu/.bitcoin/bitcoin.conf
2016-01-18 11:56:48 Using at most 125 connections (60000 file descriptors available)
2016-01-18 11:56:48 Using 2 threads for script verification
2016-01-18 11:56:48 Binding RPC on address ::1 port 8332 (IPv4+IPv6 bind any: 0)
2016-01-18 11:56:48 Binding RPC on address 127.0.0.1 port 8332 (IPv4+IPv6 bind any: 0)
2016-01-18 11:56:48 Using wallet wallet.dat
2016-01-18 11:56:48 init message: Verifying wallet...
2016-01-18 11:56:48 CDBEnv::Open: LogDir=/home/jepu/.bitcoin/database ErrorFile=/home/jepu/.bitcoin/db.log
2016-01-18 11:56:48 scheduler thread start
2016-01-18 11:56:48 Bound to [::]:8333
2016-01-18 11:56:48 Bound to 0.0.0.0:8333
2016-01-18 11:56:48 Cache configuration:
2016-01-18 11:56:48 * Using 62.5MiB for block index database
2016-01-18 11:56:48 * Using 117.4MiB for chain state database
2016-01-18 11:56:48 * Using 320.1MiB for in-memory UTXO set
2016-01-18 11:56:48 init message: Loading block index...
2016-01-18 11:56:48 Opening LevelDB in /home/jepu/.bitcoin/blocks/index
2016-01-18 11:56:48 Opened LevelDB successfully
2016-01-18 11:56:48 Opening LevelDB in /home/jepu/.bitcoin/chainstate
2016-01-18 11:56:48 Opened LevelDB successfully
2016-01-18 11:56:52 LoadBlockIndexDB: last block file = 420
2016-01-18 11:56:52 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=185, size=127051015, heights=393682...393866, time=2016-01-17...2016-01-18)
2016-01-18 11:56:52 Checking all blk files are present...
2016-01-18 11:56:52 LoadBlockIndexDB: transaction index enabled
2016-01-18 11:56:52 Initializing databases...

Then I downloaded compiled binary from here (0.11D Linux 64-bit):
http://xtnodes.com/ and same problem occurred.
These logs are from this binary.

But original bitcoind daemon working ok with 0.11.99 (compiled about 3 week ago).
EDIT: Compiled also Bitcoin 0.12 and it compiled ok and it's up and running.
Mayde problem seems to be on Bitcoin XT side...

Should I use same bitcoin.conf or different one?
What might caused this crash?

Build / git issues with 0.10.1

While trying to reproduce the 0.10.1 gitian build, I've run into a few minor but confusing issues.

The first is that the "0.10.1" tag points to some old commit. A somewhat related issue is that there exists a branch and a tag both named "0.10.1" which is somewhat confusing with git, and extremely confusing on GitHub.

By somewhat confusing with git, I simply mean that if I ask gbuild to build 0.10.1, git selects the old 0.10.1 tag instead of what I wanted (the head of the 0.10.1 branch).

By extremely confusing on GitHub, I mean:

If you attempt to select the tag named "0.10.1", you end up viewing the head of the 0.10.1 branch instead (this appears to be a GitHub bug).
If you go to the 0.10.1 release page:
- the release is dated Dec 28, 2014 (the date of the commit the old tag points to; the most recent release is listed as 0.10.0 final)
- the branch link (upper left) links to the current 0.10.1 branch
- the commit link links to the old 0.10.1 tagged commit
- the binaries are the ones that were recently uploaded presumably from the current 0.10.1 branch
- the source tarball is from (I believe) the old 0.10.1 commit

In short, really confusing....

The second issue was just a question: which commit is the (new) 0.10.1 release? Is it 7dd901c as listed in the gitian sigs? That commit does not appear to be connected to any branches:

$ git clone https://github.com/bitcoinxt/bitcoinxt.git
Cloning into 'bitcoinxt'...
remote: Counting objects: 44988, done.
remote: Total 44988 (delta 0), reused 0 (delta 0), pack-reused 44988
Receiving objects: 100% (44988/44988), 32.94 MiB | 6.66 MiB/s, done.
Resolving deltas: 100% (33751/33751), done.
Checking connectivity... done.
$ git checkout 7dd901c7f6571afdfeda260f5bc2990cab3dcb7a
fatal: reference is not a tree: 7dd901c7f6571afdfeda260f5bc2990cab3dcb7a

Was that commit amended into 2a1ebf1 perhaps?

How can we stay tunned about XT?

Theymos and his hounds seem to be doing some censoring at /r/Bitcoin. I saw a very detailed post that only enumerated facts about the debate (eg: it included some quotes from Satoshi, facts about Gavin, Mike, Blockstream, etc) but then it was gone.

So I'm afraid that when the time comes, you won't be able to inform the users since Theymos controls r/Bitcoin, bitcointalk.org, bitcoin.org, and bitcoin.it. Any ideas?

By the way I read part of the debate in the mailing list and I want to thank you for what you are doing. It must be stressful to discuss all day with people who claim to want the same as you, but in the end are just filibusters (by stopping all progress they win by default).

If you get big companies and miners on board you should be fine. Imagine if Coinbase and similar companies coordinated to send an email to inform their users about the upgrade. Users who run full nodes would get the memo for sure one way or another.

Windows installer defaults to same directory as Bitcoin Core

I installed 0.11A on Windows 7 and while all is working fine, it left the bitcoin-core folder in the Start menu and added a bitcoin-XT folder. Aside from being messy, this gives the impression both are installed on the system when in fact bitcoin-xt overwrites bitcoin-core.

I forgot to check the uninstall section to see if it's listed twice there and my Windows system is off for the day, but I would guess it is.

Might want to remove the download from github link

Now that you have a domain...i didn't realize latest binaries were already built.

sighashlimit and accuratesigoplimit reported as max unsigned 64-bit integer

My BitcoinXT node running on an ODROID-XU4 (an ARM development board) reports the sighashlimit and accuratesigoplimit values in getblocktemplate as the maximum unsigned 64-bit integer (18446744073709551615).

Since many JSON parsers (eg. jansson used by cgminer) fail to parse the response due to the extremely large integer, this also has the side effect of breaking some applications which depend on being able to parse the JSON response returned by getblocktemplate.

build broken - net.cpp - error `CLIENT_VERSION_XT_SUBVER` not declared

Just did a pull, tried to make and got this error. This probably shouldn't happen.
(I had built before, maybe about two weeks ago, no problems)

net.cpp: In member function ‘void CNode::PushVersion()’:
net.cpp:438:103: error: ‘CLIENT_VERSION_XT_SUBVER’ was not declared in this scope
                 nLocalHostNonce, FormatSubVersion(CLIENT_NAME, CLIENT_VERSION, std::vector<string>(), CLIENT_VERSION_XT_SUBVER), nBestHeight, true);

tried doing a make clean, make, but still nothing, guess I'll try to run ./configure again.

Running 2nd level testscript forknotify.py...
Initializing test directory /tmp/testc3MPBy
JSONRPC error: CreateNewBlock(): TestBlockValidity failed
  File "/home/error/bitcoinxt-0.11D/qa/rpc-tests/test_framework/test_framework.py", line 118, in main
    self.run_test()
  File "/home/error/bitcoinxt-0.11D/qa/rpc-tests/forknotify.py", line 41, in run_test
    self.nodes[0].generate(1)
  File "/home/error/bitcoinxt-0.11D/qa/rpc-tests/test_framework/authproxy.py", line 126, in __call__
    raise JSONRPCException(response['error'])
Stopping nodes
Failed

I think this is the same problem as in #101, only with a different test, but I would appreciate someone else (@dgenr8?) reviewing it.

Node debug logs are included:
node0-regtest-debug.txt
node1-regtest-debug.txt
node2-regtest-debug.txt

Rate limit the popup warnings?

This happened when I tried to send a transaction with one of the publicized private keys.

0.11B -stealth-mode is not mentioned in command line usage

bitcoinxt-qt -? | grep stealth is blank.

It does work though, connecting to a 0.11A node using -stealth-mode makes it report.

receive version message: /Satoshi:0.11.0/: version 70002, blocks=222611, us=0.0.0.0:0, peerid=2959

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.