limxtec / bitcore Goto Github PK
View Code? Open in Web Editor NEWBitCore (BTX) - Cryptocurrency 220 Byte Datacarriersize
Home Page: https://bitcore.cc
License: MIT License
BitCore (BTX) - Cryptocurrency 220 Byte Datacarriersize
Home Page: https://bitcore.cc
License: MIT License
There is a memory leak in the miner (gpu) using an NVidia 1070 under Windows 10 (latest NVidia driver). Over a few hours the ccminer process consumes all the available memory on the machine; in my case 32GB.
There should not be a memory leak.
There is a memory leak.
Using the latest miner under https://github.com/LIMXTEC/BitCore/releases
no logs are produced by the miner.
When trying to open the wallet, it throws a serious error and does not finish loading. Attached is debug log.
Yes
System error while flushing: Database I / O error, see below
Finish synchronization and load the wallet with my balance.
Starts the program and remains checking blocks, then throws internal error or synchronizes up to 1.34% and crashes. It does not respond
Windows download from https://github.com/LIMXTEC/BitCore/releases/download/0.14.1.6/2.Windows-0-14-1-16.zip
2017-11-22 16:11:01 BitCore version v0.14.1.6-g814d134
2017-11-22 16:11:01 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-11-22 16:11:01 Assuming ancestors of block 580a107e111bea326b64dc098c057a3b96622c1521c23e4f5b51647aa5e41ecb have valid signatures.
2017-11-22 16:11:01 GUI: "registerShutdownBlockReason: Successfully registered: BitCore Core no se ha cerrado de forma segura todavÃa..."
2017-11-22 16:11:02 Default data directory C:\Users\PC\AppData\Roaming\BitCore
2017-11-22 16:11:02 Using data directory C:\Users\PC\AppData\Roaming\BitCore
2017-11-22 16:11:02 Using config file C:\Users\PC\AppData\Roaming\BitCore\bitcore.conf
2017-11-22 16:11:02 Using at most 125 automatic connections (2048 file descriptors available)
2017-11-22 16:11:02 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-11-22 16:11:02 Using 4 threads for script verification
2017-11-22 16:11:02 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-11-22 16:11:02 Using wallet wallet.dat
2017-11-22 16:11:02 scheduler thread start
2017-11-22 16:11:02 init message: Verificando monedero...
2017-11-22 16:11:02 CDBEnv::Open: LogDir=C:\Users\PC\AppData\Roaming\BitCore\database ErrorFile=C:\Users\PC\AppData\Roaming\BitCore\db.log
2017-11-22 16:11:03 Bound to [::]:8555
2017-11-22 16:11:03 Bound to 0.0.0.0:8555
2017-11-22 16:11:03 Cache configuration:
2017-11-22 16:11:03 * Using 2.0MiB for block index database
2017-11-22 16:11:03 * Using 8.0MiB for chain state database
2017-11-22 16:11:03 * Using 590.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-11-22 16:11:03 init message: Cargando el Ãndice de bloques...
2017-11-22 16:11:03 Opening LevelDB in C:\Users\PC\AppData\Roaming\BitCore\blocks\index
2017-11-22 16:11:03 Opened LevelDB successfully
2017-11-22 16:11:03 Using obfuscation key for C:\Users\PC\AppData\Roaming\BitCore\blocks\index: 0000000000000000
2017-11-22 16:11:03 Opening LevelDB in C:\Users\PC\AppData\Roaming\BitCore\chainstate
2017-11-22 16:11:03 Opened LevelDB successfully
2017-11-22 16:11:03 Using obfuscation key for C:\Users\PC\AppData\Roaming\BitCore\chainstate: 424fe5d1aef53f5e
2017-11-22 16:11:05 LoadBlockIndexDB: last block file = 1
2017-11-22 16:11:05 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=2584, size=130131042, heights=78133...80720, time=2017-11-05...2017-11-10)
2017-11-22 16:11:05 Checking all blk files are present...
2017-11-22 16:11:05 LoadBlockIndexDB: transaction index disabled
2017-11-22 16:11:05 LoadBlockIndexDB: hashBestChain=ae90b4a966ab2501538b0585b46881df500150b13ee7ad3431df0d2a826297a8 height=80720 date=2017-11-10 03:24:04 progress=0.000295
2017-11-22 16:11:05 init message: Verificando bloques...
2017-11-22 16:11:19 IO error: C:\Users\PC\AppData\Roaming\BitCore\chainstate\000013.ldb: Error de datos (comprobación de redundancia cíclica).
2017-11-22 16:11:19 *** System error while flushing: Database I/O error
2017-11-22 16:11:55 Aborted block database rebuild. Exiting.
2017-11-22 16:11:55 scheduler thread interrupt
2017-11-22 16:11:55 Shutdown: In progress...
2017-11-22 16:11:55 IO error: C:\Users\PC\AppData\Roaming\BitCore\chainstate\000013.ldb: Error de datos (comprobación de redundancia cíclica).
2017-11-22 16:11:55 *** System error while flushing: Database I/O error
2017-11-22 16:13:47
2017-11-22 16:13:47 BitCore version v0.14.1.6-g814d134
2017-11-22 16:13:47 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-11-22 16:13:47 Assuming ancestors of block 580a107e111bea326b64dc098c057a3b96622c1521c23e4f5b51647aa5e41ecb have valid signatures.
2017-11-22 16:13:47 GUI: "registerShutdownBlockReason: Successfully registered: BitCore Core no se ha cerrado de forma segura todavÃa..."
2017-11-22 16:13:48 Default data directory C:\Users\PC\AppData\Roaming\BitCore
2017-11-22 16:13:48 Using data directory C:\Users\PC\AppData\Roaming\BitCore
2017-11-22 16:13:48 Using config file C:\Users\PC\AppData\Roaming\BitCore\bitcore.conf
2017-11-22 16:13:48 Using at most 125 automatic connections (2048 file descriptors available)
2017-11-22 16:13:48 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-11-22 16:13:48 Using 4 threads for script verification
2017-11-22 16:13:48 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-11-22 16:13:48 scheduler thread start
2017-11-22 16:13:48 Using wallet wallet.dat
2017-11-22 16:13:48 init message: Verificando monedero...
2017-11-22 16:13:48 CDBEnv::Open: LogDir=C:\Users\PC\AppData\Roaming\BitCore\database ErrorFile=C:\Users\PC\AppData\Roaming\BitCore\db.log
2017-11-22 16:13:48 Bound to [::]:8555
2017-11-22 16:13:48 Bound to 0.0.0.0:8555
2017-11-22 16:13:48 Cache configuration:
2017-11-22 16:13:48 * Using 2.0MiB for block index database
2017-11-22 16:13:48 * Using 8.0MiB for chain state database
2017-11-22 16:13:48 * Using 590.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-11-22 16:13:48 init message: Cargando el Ãndice de bloques...
2017-11-22 16:13:48 Opening LevelDB in C:\Users\PC\AppData\Roaming\BitCore\blocks\index
2017-11-22 16:13:48 Opened LevelDB successfully
2017-11-22 16:13:48 Using obfuscation key for C:\Users\PC\AppData\Roaming\BitCore\blocks\index: 0000000000000000
2017-11-22 16:13:48 Opening LevelDB in C:\Users\PC\AppData\Roaming\BitCore\chainstate
2017-11-22 16:13:48 Opened LevelDB successfully
2017-11-22 16:13:48 Using obfuscation key for C:\Users\PC\AppData\Roaming\BitCore\chainstate: 424fe5d1aef53f5e
2017-11-22 16:13:50 LoadBlockIndexDB: last block file = 1
2017-11-22 16:13:50 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=2584, size=130131042, heights=78133...80720, time=2017-11-05...2017-11-10)
2017-11-22 16:13:50 Checking all blk files are present...
2017-11-22 16:13:50 LoadBlockIndexDB: transaction index disabled
2017-11-22 16:13:50 LoadBlockIndexDB: hashBestChain=ae90b4a966ab2501538b0585b46881df500150b13ee7ad3431df0d2a826297a8 height=80720 date=2017-11-10 03:24:04 progress=0.000295
2017-11-22 16:13:50 init message: Verificando bloques...
2017-11-22 16:14:01 init message: Verificando bloques...
2017-11-22 16:14:01 Verifying last 24 blocks at level 3
2017-11-22 16:14:01 [0%]...[12%]...[20%]...[33%]...[41%]...[50%]...[62%]...[70%]...[83%]...[91%]...[DONE].
2017-11-22 16:14:04 No coin database inconsistencies in last 25 blocks (60 transactions)
2017-11-22 16:14:04 block index 16373ms
2017-11-22 16:14:04 init message: Cargando monedero...
2017-11-22 16:14:05 nFileVersion = 140106
2017-11-22 16:14:05 Keys: 103 plaintext, 0 encrypted, 103 w/ metadata, 103 total
2017-11-22 16:14:05 wallet 302ms
2017-11-22 16:14:05 setKeyPool.size() = 100
2017-11-22 16:14:05 mapWallet.size() = 6
2017-11-22 16:14:05 mapAddressBook.size() = 2
2017-11-22 16:14:05 mapBlockIndex.size() = 80721
2017-11-22 16:14:05 nBestHeight = 80720
2017-11-22 16:14:05 torcontrol thread start
2017-11-22 16:14:05 Imported mempool transactions from disk: 1 successes, 0 failed, 0 expired
2017-11-22 16:14:05 AddLocal([2001:0:5ef5:79fd:2495:2b0d:4161:e93e]:8555,1)
2017-11-22 16:14:05 Discover: oms - 2001:0:5ef5:79fd:2495:2b0d:4161:e93e
2017-11-22 16:14:05 init message: Cargando direcciones...
2017-11-22 16:14:05 Loaded 15914 addresses from peers.dat 267ms
2017-11-22 16:14:05 init message: Cargando banlist...
2017-11-22 16:14:05 init message: Iniciando funciones de red...
2017-11-22 16:14:05 net thread start
2017-11-22 16:14:05 dnsseed thread start
2017-11-22 16:14:05 addcon thread start
2017-11-22 16:14:05 opencon thread start
2017-11-22 16:14:05 msghand thread start
2017-11-22 16:14:05 init message: Se terminó de cargar
2017-11-22 16:14:05 GUI: Platform customization: "windows"
2017-11-22 16:14:05 GUI: PaymentServer::LoadRootCAs: Loaded 0 root certificates
2017-11-22 16:14:06 receive version message: /BitCore:0.14.1.6/: version 70015, blocks=87827, us=190.158.22.193:50443, peer=0
2017-11-22 16:14:07 receive version message: /BitCore:0.14.1.6/: version 70015, blocks=87827, us=190.158.22.193:50444, peer=1
2017-11-22 16:14:10 UpdateTip: new best=29a2b211ee84c5cd68f7f1cc34cdcd0f73e59183d236b321bf08c031979f1a4d height=80721 version=0x20000000 log2_work=59.237968 tx=159659 date='2017-11-10 03:29:39' progress=0.000295 cache=0.1MiB(9tx)
2017-11-22 16:14:10 UpdateTip: new best=8a2a82f5b0a709de4d7d0b071120b1c5c96968e21aa4f832012defe652cb772b height=80722 version=0x20000000 log2_work=59.23803 tx=159660 date='2017-11-10 03:34:57' progress=0.000295 cache=0.1MiB(10tx)
..........................
version=0x20000000 log2_work=59.531078 tx=176782 date='2017-11-18 09:28:56' progress=0.000955 cache=57.1MiB(20082tx)
2017-11-22 16:16:04 UpdateTip: new best=408eba4251615dd73e056b3f182bc8c47bfbb0c963f7f4d82d4f69d074df2746 height=85415 version=0x20000000 log2_work=59.531192 tx=176784 date='2017-11-18 09:29:52' progress=0.000955 cache=57.1MiB(20084tx)
2017-11-22 16:16:17 LevelDB read failure: IO error: C:\Users\PC\AppData\Roaming\BitCore\chainstate\000013.ldb: Error de datos (comprobación de redundancia cíclica).
2017-11-22 16:16:17 IO error: C:\Users\PC\AppData\Roaming\BitCore\chainstate\000013.ldb: Error de datos (comprobación de redundancia cíclica).
2017-11-22 16:36:05 socket sending timeout: 1201s
2017-11-22 16:36:05 socket sending timeout: 1201s
2017-11-22 16:36:05 socket sending timeout: 1201s
After CTRL-bypassing app security on OSX 10.13.4, the app in https://github.com/LIMXTEC/BitCore/releases/download/0.15.0.3/bitcore-qt-macOS-High-Sierra.10.13.4.dmg never opens, never shows up in the dock for any human-perceptible amount of time. Activity Monitor doesn't show it either.
When I run bitcored, it panics the segment fault and quit. the debug.log have a bundle of messages like the following
2017-11-15 02:33:07 UpdateTip: new best=de7e53d7898a80fa2a7a5465feb9a0b643325e0a13d0abc8f1038afcba257430 height=3798 version=0x30000003 log2_work=53.841346 tx=7089 date='2017-05-19 03:57:58' progress=0.000001 cache=0.0MiB(109tx) warning='100 of last 100 blocks have unexpected version'
2017-11-15 02:33:07 UpdateTip: new best=a40fd316ef64321c4d916edbac1edf575ce33e5aef62f7d42afca596e0074fca height=3799 version=0x30000003 log2_work=53.841636 tx=7092 date='2017-05-19 04:16:33' progress=0.000001 cache=0.0MiB(114tx) warning='100 of last 100 blocks have unexpected version'
my installation is through the download link https://github.com/LIMXTEC/BitCore/archive/0.14.1.6.tar.gz
I tried following the install manual but got an error on:
sudo add-apt-repository ppa:bitcore/bitcore
Cannot add PPA: 'ppa:~bitcore/ubuntu/bitcore'.
ERROR: '~bitcore' user or team does not exist.
I tried running the precompiled binaries, but this wouldn't work because the ubuntu install is missing dependencies.
I'm now attempting to install them so I can run this bitcore.
I already have a bitcoin bitcore running.
Any ideas?
I have it copied in both internal storage top level directory /Download & external SD card top level directory /Download
Yet I get the "No wallet backup was found. Make sure it is placed in external storage (/Download)." message anyway.
ETA1: I generated a new backup file & attempted to restore it with apparent pass success, now I guess I'm waiting for peers...
ETA2: ... that apparently don't exist because this wallet was abandoned for Coinomi.
How do you get your private keys out of your original BTX Android wallet backup file?
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
leveldb/port/port_posix.cc: In function ‘bool leveldb::port::HasAcceleratedCRC32C()’:
leveldb/port/port_posix.cc:60:15: warning: ‘ecx’ may be used uninitialized in this function [-Wmaybe-uninitialized]
return (ecx & (1 << 20)) != 0;
^
AR leveldb/libleveldb.a
CXX leveldb/port/leveldb_libleveldb_sse42_a-port_posix_sse.o
AR leveldb/libleveldb_sse42.a
CXX leveldb/helpers/memenv/leveldb_libmemenv_a-memenv.o
AR leveldb/libmemenv.a
CXXLD bitcored
/usr/bin/ld: crypto/libbitcore_crypto.a(crypto_libbitcore_crypto_a-blake.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC
crypto/libbitcore_crypto.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:3750: recipe for target 'bitcored' failed
make[2]: *** [bitcored] Error 1
make[2]: Leaving directory '/home/user/src/BitCore/src'
Makefile:9737: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/src/BitCore/src'
Makefile:741: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
This happens inside this folder.
ccminer-btx-timetravel
I get an error saying invalid device see picture
This is the error I get.
[2017-10-02 18:24:37] Starting on stratum+tcp://btx.suprnova.cc:3629
[2017-10-02 18:24:37] NVML GPU monitoring enabled.
[2017-10-02 18:24:37] NVAPI GPU monitoring enabled.
[2017-10-02 18:24:37] 1 miner thread started, using 'timetravel' algorithm.
[2017-10-02 18:24:38] Stratum difficulty set to 4 (0.01563)
[2017-10-02 18:24:38] GPU #0: Intensity set to 19, 524288 cuda threads
Cuda error in func 'qubit_luffa512_cpu_init' at line 455 : invalid device symbol.
Tell us what should happen
it should start processing the packets send by the server in green
Tell us what happens instead
[2017-10-02 18:24:37] Starting on stratum+tcp://btx.suprnova.cc:3629
[2017-10-02 18:24:37] NVML GPU monitoring enabled.
[2017-10-02 18:24:37] NVAPI GPU monitoring enabled.
[2017-10-02 18:24:37] 1 miner thread started, using 'timetravel' algorithm.
[2017-10-02 18:24:38] Stratum difficulty set to 4 (0.01563)
[2017-10-02 18:24:38] GPU #0: Intensity set to 19, 524288 cuda threads
Cuda error in func 'qubit_luffa512_cpu_init' at line 455 : invalid device symbol.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
OS: Windows 10
CPU: i3
RAM: 8GB
Disk size: 250
Disk Type (HD/SDD):SSD
This is normally the contents of a debug.log
or config.log
file. Raw text or a link to a pastebin type site are preferred.
Ubuntu 17.04
Bitcore 0.14.1.6
$ ./bitcore-qt
./bitcore-qt: error while loading shared libraries: libboost_system.so.1.58.0: cannot open shared object file: No such file or directory
Hey. I made a payment from my android wallet on the 22nd of September. It is still showing me message: this payment has not been transmitted yet. How can i sync my wallet or what can i do to get the coins transmitted before tomorrows airdrop?
Is it safe just to copy the Makefile from the Master branch?
On 0.15 branch it's not working when I type make
.
https://github.com/LIMXTEC/BitCore/tree/0.15/depends
. . .
I typed:
$ cd BitCore
$ ./autogen.sh
$ ./configure --prefix=`pwd`/depends/x86_64-pc-linux-gnu
$ make
Looks like it does not need to type make
into depends
directory (I have the libraries needed on my system).
I need to compile the app in a static form where the binary that outputs doesn't require the installation of more libraries. For example:
"Bitcore: error while loading shared libraries: libboost_program_options.so.1.58.0: cannot open shared object file: No such file or directory." This happens when I move the binary and try to compile it in another server.
Thanks
The SHA256 checksum for the file linux.Ubuntu.16.04.LTS_non_static.tar.gz
of version 0.15.0.2 appears to be wrong on your releases site (https://github.com/LIMXTEC/BitCore/releases).
The site says 09CBED2086B10881EEFAA8D89A18B626B916E41531F980D7FE0CE1278CEBFE14
while when downloaded and sha256sum
is called, checksum c2440dacda1534c156ad17ad6d517a3393eeadc95e04223b503492b09a218a2a
is displayed.
Could you please look into that?
I would like to enable pruning
I downloaded version 0.90.9.0 (bitcore-osx64.dmg
) MacOS wallet, but it cannot synchronize any blocks. How can I update my wallet on MacOS?
Virus detected. Novice users are unable to determine if it is safe. Also you seem to have an imposter, bitcore.io
Some benefit to using MD5 just for OSX when you can put shasum -a 256 [path] in Terminal?
user@zbox:~/Downloads/Bitcore-0.14.1.6$ autoconf
configure.ac:32: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:36: error: possibly undefined macro: AM_MAINTAINER_MODE
configure.ac:186: error: possibly undefined macro: AM_CONDITIONAL
configure.ac:219: error: possibly undefined macro: AC_MSG_ERROR
configure.ac:267: error: possibly undefined macro: AC_CHECK_LIB
configure.ac:819: error: possibly undefined macro: AC_CHECK_HEADER
user@zbox:~/Downloads/Bitcore-0.14.1.6$ automake --add-missing
/usr/share/automake-1.15/am/depend2.am: error: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.15/am/depend2.am: The usual way to define 'am__fastdepCC' is to add 'AC_PROG_CC'
/usr/share/automake-1.15/am/depend2.am: to 'configure.ac' and run 'aclocal' and 'autoconf' again
/usr/share/automake-1.15/am/depend2.am: error: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.15/am/depend2.am: The usual way to define 'AMDEP' is to add one of the compiler tests
/usr/share/automake-1.15/am/depend2.am: AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC, AC_PROG_OBJCXX,
/usr/share/automake-1.15/am/depend2.am: AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.15/am/depend2.am: to 'configure.ac' and run 'aclocal' and 'autoconf' again
src/Makefile.am: error: C source seen but 'CC' is undefined
src/Makefile.am: The usual way to define 'CC' is to add 'AC_PROG_CC'
src/Makefile.am: to 'configure.ac' and run 'autoconf' again.
/usr/share/automake-1.15/am/depend2.am: error: am__fastdepCXX does not appear in AM_CONDITIONAL
/usr/share/automake-1.15/am/depend2.am: The usual way to define 'am__fastdepCXX' is to add 'AC_PROG_CXX'
/usr/share/automake-1.15/am/depend2.am: to 'configure.ac' and run 'aclocal' and 'autoconf' again
/usr/share/automake-1.15/am/depend2.am: error: am__fastdepOBJCXX does not appear in AM_CONDITIONAL
/usr/share/automake-1.15/am/depend2.am: The usual way to define 'am__fastdepOBJCXX' is to add 'AC_PROG_OBJCXX'
/usr/share/automake-1.15/am/depend2.am: to 'configure.ac' and run 'aclocal' and 'autoconf' again
parallel-tests: installing 'build-aux/test-driver'
/usr/share/automake-1.15/am/check2.am: error: am__EXEEXT does not appear in AM_CONDITIONAL
Cannot build, automake and autoconf barf on Ubuntu 17.04 & 16.04
yes
Trying to build, see above
Linux download from https://github.com/LIMXTEC/BitCore/releases/tag/0.14.1.6
The Bitcore Segwit is start by block 3000. But the miner produce a wrong hexversion.
https://github.com/LIMXTEC/BitCore/blob/master/src/validation.cpp#L3084:L3102
We need a good solution or we delete this part.
Block 3000
"version": 805306371,
"versionHex": "30000003"
Block 13001
"version": 536870912,
"versionHex": "20000000",
We can pay a small bounty in BTX.
latest xenial release
!root :
Impossible d’obtenir un verrou sur le répertoire de données /home/mika/.bitcore. BitCore Core fonctionne probablement déjà. Permission non accordée.
(impossible to get a lock on data directory)
root :
*Impossible de se lier à 0.0.0.0:8555 sur cet ordinateur. BitCore Core fonctionne probablement déjà.
(impossible to link to 0.0.0.0:8555 bitcore probably already running
did i miss some dependencies ? (i have b3coin running fine)
Problems with functionality and acessing wallet registration, a long way off to be a functional product
This issue tracker is only for technical issues related to bitcore-core.
General bitcore questions and/or support requests and are best directed to the bitcoretalk.io forums.
For reporting security issues, please contact the BitCore developers on the #bitcore-dev Freenode IRC channel or alternatively you can email us at [email protected].
After reinstalling windows 10, I downloaded the bitcore wallets but when I start bitcore-qt, starts loading wallet. it first pops up and "Error reading wallet.dat! All keys read correctly, but transaction data or address book entries might be missing or incorrect." This happens on first run. Then when I click 'ok' it says.. "Error: A fatal internal error occurred, see debug.log for details"
The wallet should run
it crashes
Version v0.14.1.6-g814d134 an official binary.
This is normally the contents of a debug.log
or config.log
file. Raw text or a link to a pastebin type site are preferred.
/usr/bin/bitcored -daemon
Running bitcored daemon
$ tail debug.log
2018-06-13 07:30:29 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-06-13 07:30:29 Using 4 threads for script verification
2018-06-13 07:30:29 scheduler thread start
2018-06-13 07:30:29 Binding RPC on address :: port 8556 failed.
2018-06-13 07:30:29 Binding RPC on address 0.0.0.0 port 8556 failed.
2018-06-13 07:30:29 Unable to bind any endpoint for RPC server
2018-06-13 07:30:29 Error: Unable to start HTTP server. See debug log for details.
2018-06-13 07:30:29 scheduler thread interrupt
2018-06-13 07:30:29 PrepareShutdown: In progress...
2018-06-13 07:30:29 Shutdown: done
# netstat -ap | grep 8556
tcp 0 0 localhost:8556 0.0.0.0:* LISTEN 9747/megacoind
I use 0.15.0.3 - both bitcored and megacoind
It's probably this line.
This issue tracker is only for technical issues related to bitcore-core.
General bitcore questions and/or support requests and are best directed to the bitcoretalk.io forums.
For reporting security issues, please contact the BitCore developers on the #bitcore-dev Freenode IRC channel or alternatively you can email us at [email protected].
I compiled the project on ubuntu 16.04 successfully. After the installation I put bitcored to boot with the operating system.
The bitcored process is running. I created the /etc/bitcore/bitcore.conf file and put the necessary info. Here is my configuration:
##
## bitcore.conf configuration file. Lines beginning with # are comments.
##
# Network-related settings:
# Run on the test network instead of the real bitcore network.
#testnet=1
# Run a regression test network
#regtest=0
# Connect via a SOCKS5 proxy
#proxy=127.0.0.1:9050
# Bind to given address and always listen on it. Use [host]:port notation for IPv6
#bind=<addr>
# Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6
#whitebind=<addr>
##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################
# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8555
# Alternatively use as many connect= settings as you like to connect ONLY to specific peers
#connect=69.164.218.197
#connect=10.0.0.1:8555
# Listening mode, enabled by default except when 'connect' is being used
listen=1
# Maximum number of inbound+outbound connections.
maxconnections=20
#
# JSON-RPC options (for controlling a running BitCore/bitcored process)
#
# server=1 tells BitCore-Qt and bitcored to accept JSON-RPC commands
server=1
# Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6.
# This option can be specified multiple times (default: bind to all interfaces)
#rpcbind=<addr>
# If no rpcpassword is set, rpc cookie auth is sought. The default `-rpccookiefile` name
# is .cookie and found in the `-datadir` being used for bitcored. This option is typically used
# when the server and client are run as the same user.
#
# If not, you must set rpcuser and rpcpassword to secure the JSON-RPC api. The first
# method(DEPRECATED) is to set this pair for the server and client:
rpcuser=myuser
rpcpassword=mypassword
#
# The second method `rpcauth` can be added to server startup argument. It is set at intialization time
# using the output from the script in share/rpcuser/rpcuser.py after providing a username:
#
# ./share/rpcuser/rpcuser.py alice
# String to be appended to bitcore.conf:
# rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae
# Your password:
# DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
#
# On client-side, you add the normal user/password pair to send commands:
#rpcuser=alice
#rpcpassword=DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=
#
# You can even add multiple entries of these to the server conf file, and client can use any of them:
# rpcauth=bob:b2dd077cb54591a2f3139e69a897ac$4e71f08d48b4347cf8eff3815c0e25ae2e9a4340474079f55705f40574f4ec99
# How many seconds bitcore will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
#rpcclienttimeout=30
# By default, only RPC connections from localhost are allowed.
# Specify as many rpcallowip= settings as you like to allow connections from other hosts,
# either as a single IPv4/IPv6 or with a subnet specification.
# NOTE: opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED,
# because the rpcpassword is transmitted over the network unencrypted.
# server=1 tells BitCore-Qt to accept JSON-RPC commands.
# it is also read by bitcored to determine if RPC should be enabled
#rpcallowip=10.1.1.34/255.255.255.0
#rpcallowip=1.2.3.4/24
#rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96
# Listen for RPC connections on this TCP port:
rpcport=40332
# You can use BitCore or bitcored to send commands to BitCore/bitcored
# running on another host using this option:
rpcconnect=127.0.0.1
# Transaction Fee Changes in 0.10.0
# Send transactions as zero-fee transactions if possible (default: 0)
#sendfreetransactions=0
# Create transactions that have enough fees (or priority) so they are likely to begin confirmation within n blocks (default: 1).
# This setting is over-ridden by the -paytxfee option.
#txconfirmtarget=n
# Miscellaneous options
# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
keypool=10000
# Pay an optional transaction fee every time you send bitcores. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
#paytxfee=0.00
# User interface options
# Start BitCore minimized
#min=1
# Minimize to the system tray
#minimizetotray=1
prune=600
daemon=1
maxuploadtarget=20
Now let's get to the fact.
bitcore@bitcore:~$ bitcore-cli -conf=/etc/bitcore/bitcore.conf getinfo error: couldn't connect to server: unknown (code -1) (make sure server is running and you are connecting to the correct RPC port)
Can someone help me? This is the first time I compile a full node.
I am trying to buld the 0.15 branch on Ubuntu 16.04.3 LTS.
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
leveldb/port/port_posix.cc: In function ‘bool leveldb::port::HasAcceleratedCRC32C()’:
leveldb/port/port_posix.cc:60:15: warning: ‘ecx’ may be used uninitialized in this function [-Wmaybe-uninitialized]
return (ecx & (1 << 20)) != 0;
^
AR leveldb/libleveldb.a
CXX leveldb/port/leveldb_libleveldb_sse42_a-port_posix_sse.o
AR leveldb/libleveldb_sse42.a
CXX leveldb/helpers/memenv/leveldb_libmemenv_a-memenv.o
AR leveldb/libmemenv.a
CXXLD bitcored
/usr/bin/ld: crypto/libbitcore_crypto.a(crypto_libbitcore_crypto_a-blake.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC
crypto/libbitcore_crypto.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:3750: recipe for target 'bitcored' failed
make[2]: *** [bitcored] Error 1
make[2]: Leaving directory '/home/user/src/BitCore/src'
Makefile:9737: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/user/src/BitCore/src'
Makefile:741: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
Possibly related to #24.
There is no binary available to download for the latest 0.15.0.2, so I am trying to build from source. I get the following error:
make[1]: *** No rule to make target `bitcored.1', needed by `all-am'. Stop.
make: *** [all-recursive] Error 1
Full compiler output attached. I'm running Sierra 10.12.6 with all dependencies installed through MacPorts.
make log.txt
When trying to build the 0.14.1.6 version I get errors (in the depends
directory):
make: execvp: ./config.guess: Permission denied
make: execvp: ./config.guess: Permission denied
make: execvp: ./config.guess: Permission denied
make: execvp: ./config.sub: Permission denied
make: execvp: ./config.guess: Permission denied
make: execvp: ./config.sub: Permission denied
Makefile:72: hosts/.mk: No such file or directory
Makefile:74: builders/.mk: No such file or directory
The fix is:
chmod 764 ./config.guess
chmod 764 ./config.sub
The master version is affected too.
When you launch the client on a 4K screen the text is too small to read. It doesn't scale.
The text should scale according to your resolution.
Text is too small to read.
v0.15.0.2-gba8ed3a93be (32-bit)
The Core 0.15.0.1 is nearly done. We have two open task currently.
The wallet connected only with addnode "addnode 188.68.52.172 onetry".
The connection with lots of nodes is possible. The wallet looks the correct chain high. But the sync is not possible. It is possible to move the chain in the appfolder. After then works the wallet normal.
https://github.com/LIMXTEC/BitCore/blob/0.15/src/chainparams.cpp#L134
The wallet connected only with addnode "addnode 188.68.52.172 onetry" or similar.
Bounty for this task 100 Bitcore. (Only for tested pullrequest)
I have the older core wallet and it will not connect to peers. It is version 0.15.2.0 for the Mac.
I am hoping to access my BTX. Is there a newer Mac wallet that can access my current wallet.dat?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.