Wow! what I`m miss? XCN is delisted from btc38?!
Btc38 closing all trading, like all the other chinese exchanges.
Topic: [ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties! - page 94. (Read 215807 times)
September 25, 2017, 12:09:17 PM
Btc38 closing all trading, like all the other chinese exchanges.
September 25, 2017, 11:57:42 AM
Wow! what I`m miss? XCN is delisted from btc38?!
Btc38 closing all trading, like all the other chinese exchanges.
September 25, 2017, 11:50:23 AM
Wow! what I`m miss? XCN is delisted from btc38?!
September 25, 2017, 11:47:34 AM
Sorry if this is the wrong place, but I'm getting errors when attempting a build on Arch Linux 4.12.6-1-ARCH x86_64
Here is a full output of the error:
Code:
Making all in src
make[1]: Entering directory '/home/severoraz/lab/builds/Cryptonite/src'
make all-recursive
make[2]: Entering directory '/home/severoraz/lab/builds/Cryptonite/src'
Making all in .
make[3]: Entering directory '/home/severoraz/lab/builds/Cryptonite/src'
CXX addrman.o
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h:56:24: error: invalid use of incomplete type ‘BIGNUM {aka struct bignum_st}’
class CBigNum : public BIGNUM
^~~~~~
In file included from /usr/include/openssl/crypto.h:31:0,
from allocators.h:15,
from serialize.h:9,
from netbase.h:13,
from addrman.h:8,
from addrman.cpp:5:
/usr/include/openssl/ossl_typ.h:80:16: note: forward declaration of ‘BIGNUM {aka struct bignum_st}’
typedef struct bignum_st BIGNUM;
^~~~~~~~~
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h: In constructor ‘CBigNum::CBigNum()’:
bignum.h:61:9: error: ‘BN_init’ was not declared in this scope
BN_init(this);
^~~~~~~
bignum.h:61:9: note: suggested alternative: ‘BN_print’
BN_init(this);
^~~~~~~
BN_print
bignum.h: In copy constructor ‘CBigNum::CBigNum(const CBigNum&)’:
bignum.h:66:9: error: ‘BN_init’ was not declared in this scope
BN_init(this);
^~~~~~~
bignum.h:66:9: note: suggested alternative: ‘BN_print’
BN_init(this);
^~~~~~~
BN_print
bignum.h:67:30: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘BIGNUM* BN_copy(BIGNUM*, const BIGNUM*)’
if (!BN_copy(this, &b))
^
bignum.h:69:31: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘void BN_clear_free(BIGNUM*)’
BN_clear_free(this);
^
bignum.h: In member function ‘CBigNum& CBigNum::operator=(const CBigNum&)’:
bignum.h:76:30: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘BIGNUM* BN_copy(BIGNUM*, const BIGNUM*)’
if (!BN_copy(this, &b))
^
bignum.h: In destructor ‘CBigNum::~CBigNum()’:
bignum.h:83:27: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘void BN_clear_free(BIGNUM*)’
BN_clear_free(this);
^
bignum.h: In constructor ‘CBigNum::CBigNum(signed char)’:
bignum.h:87:37: error: ‘BN_init’ was not declared in this scope
CBigNum(signed char n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^~~~~~~
bignum.h:87:37: note: suggested alternative: ‘BN_print’
CBigNum(signed char n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(short int)’:
bignum.h:88:37: error: ‘BN_init’ was not declared in this scope
CBigNum(short n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^~~~~~~
bignum.h:88:37: note: suggested alternative: ‘BN_print’
CBigNum(short n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(int)’:
bignum.h:89:37: error: ‘BN_init’ was not declared in this scope
CBigNum(int n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^~~~~~~
bignum.h:89:37: note: suggested alternative: ‘BN_print’
CBigNum(int n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(long int)’:
bignum.h:90:37: error: ‘BN_init’ was not declared in this scope
CBigNum(long n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^~~~~~~
bignum.h:90:37: note: suggested alternative: ‘BN_print’
CBigNum(long n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(long long int)’:
bignum.h:91:37: error: ‘BN_init’ was not declared in this scope
CBigNum(long long n) { BN_init(this); setint64(n); }
^~~~~~~
bignum.h:91:37: note: suggested alternative: ‘BN_print’
CBigNum(long long n) { BN_init(this); setint64(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(unsigned char)’:
bignum.h:92:37: error: ‘BN_init’ was not declared in this scope
CBigNum(unsigned char n) { BN_init(this); setulong(n); }
^~~~~~~
bignum.h:92:37: note: suggested alternative: ‘BN_print’
CBigNum(unsigned char n) { BN_init(this); setulong(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(short unsigned int)’:
bignum.h:93:37: error: ‘BN_init’ was not declared in this scope
CBigNum(unsigned short n) { BN_init(this); setulong(n); }
^~~~~~~
bignum.h:93:37: note: suggested alternative: ‘BN_print’
CBigNum(unsigned short n) { BN_init(this); setulong(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(unsigned int)’:
bignum.h:94:37: error: ‘BN_init’ was not declared in this scope
CBigNum(unsigned int n) { BN_init(this); setulong(n); }
^~~~~~~
bignum.h:94:37: note: suggested alternative: ‘BN_print’
CBigNum(unsigned int n) { BN_init(this); setulong(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(long unsigned int)’:
bignum.h:95:37: error: ‘BN_init’ was not declared in this scope
CBigNum(unsigned long n) { BN_init(this); setulong(n); }
^~~~~~~
bignum.h:95:37: note: suggested alternative: ‘BN_print’
CBigNum(unsigned long n) { BN_init(this); setulong(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(long long unsigned int)’:
bignum.h:96:37: error: ‘BN_init’ was not declared in this scope
CBigNum(unsigned long long n) { BN_init(this); setuint64(n); }
^~~~~~~
bignum.h:96:37: note: suggested alternative: ‘BN_print’
CBigNum(unsigned long long n) { BN_init(this); setuint64(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(uint256)’:
bignum.h:97:37: error: ‘BN_init’ was not declared in this scope
explicit CBigNum(uint256 n) { BN_init(this); setuint256(n); }
^~~~~~~
bignum.h:97:37: note: suggested alternative: ‘BN_print’
explicit CBigNum(uint256 n) { BN_init(this); setuint256(n); }
^~~~~~~
BN_print
bignum.h: In constructor ‘CBigNum::CBigNum(const std::vector&)’:
bignum.h:101:9: error: ‘BN_init’ was not declared in this scope
BN_init(this);
^~~~~~~
bignum.h:101:9: note: suggested alternative: ‘BN_print’
BN_init(this);
^~~~~~~
BN_print
bignum.h: In member function ‘void CBigNum::setulong(long unsigned int)’:
bignum.h:107:33: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_set_word(BIGNUM*, long unsigned int)’
if (!BN_set_word(this, n))
^
bignum.h: In member function ‘long unsigned int CBigNum::getulong() const’:
bignum.h:113:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘long unsigned int BN_get_word(const BIGNUM*)’
return BN_get_word(this);
^
bignum.h: In member function ‘unsigned int CBigNum::getuint() const’:
bignum.h:118:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘long unsigned int BN_get_word(const BIGNUM*)’
return BN_get_word(this);
^
bignum.h: In member function ‘int CBigNum::getint() const’:
bignum.h:123:43: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘long unsigned int BN_get_word(const BIGNUM*)’
unsigned long n = BN_get_word(this);
^
bignum.h:124:33: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_is_negative(const BIGNUM*)’
if (!BN_is_negative(this))
^
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h: In member function ‘void CBigNum::setint64(int64_t)’:
bignum.h:172:37: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘3’ to ‘BIGNUM* BN_mpi2bn(const unsigned char*, int, BIGNUM*)’
BN_mpi2bn(pch, p - pch, this);
^
bignum.h: In member function ‘void CBigNum::setuint64(uint64_t)’:
bignum.h:199:37: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘3’ to ‘BIGNUM* BN_mpi2bn(const unsigned char*, int, BIGNUM*)’
BN_mpi2bn(pch, p - pch, this);
^
bignum.h: In member function ‘void CBigNum::setuint256(uint256)’:
bignum.h:227:37: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘3’ to ‘BIGNUM* BN_mpi2bn(const unsigned char*, int, BIGNUM*)’
BN_mpi2bn(pch, p - pch, this);
^
bignum.h: In member function ‘uint256 CBigNum::getuint256() const’:
bignum.h:232:50: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
unsigned int nSize = BN_bn2mpi(this, NULL);
^
bignum.h:236:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
BN_bn2mpi(this, &vch[0]);
^
bignum.h: In member function ‘void CBigNum::setvch(const std::vector&)’:
bignum.h:257:46: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘3’ to ‘BIGNUM* BN_mpi2bn(const unsigned char*, int, BIGNUM*)’
BN_mpi2bn(&vch2[0], vch2.size(), this);
^
bignum.h: In member function ‘std::vectorCBigNum::getvch() const’:
bignum.h:262:50: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
unsigned int nSize = BN_bn2mpi(this, NULL);
^
bignum.h:266:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
BN_bn2mpi(this, &vch[0]);
^
bignum.h: In member function ‘CBigNum& CBigNum::SetCompact(unsigned int)’:
bignum.h:302:36: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_set_word(BIGNUM*, long unsigned int)’
BN_set_word(this, nWord);
^
bignum.h:306:36: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_set_word(BIGNUM*, long unsigned int)’
BN_set_word(this, nWord);
^
bignum.h:307:46: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_lshift(BIGNUM*, const BIGNUM*, int)’
BN_lshift(this, this, 8*(nSize-3));
^
bignum.h:309:40: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘void BN_set_negative(BIGNUM*, int)’
BN_set_negative(this, fNegative);
^
In file included from bignum.h:17:0,
from chainparams.h:9,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h: In member function ‘unsigned int CBigNum::GetCompact() const’:
bignum.h:320:30: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_num_bits(const BIGNUM*)’
unsigned int nSize = BN_num_bytes(this);
^
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h:324:40: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘long unsigned int BN_get_word(const BIGNUM*)’
nCompact = BN_get_word(this) << 8*(3-nSize);
^
bignum.h:328:45: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_rshift(BIGNUM*, const BIGNUM*, int)’
BN_rshift(&bn, this, 8*(nSize-3));
^
bignum.h:329:39: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘long unsigned int BN_get_word(const BIGNUM*)’
nCompact = BN_get_word(&bn);
^
bignum.h:339:41: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_is_negative(const BIGNUM*)’
nCompact |= (BN_is_negative(this) ? 0x00800000 : 0);
^
bignum.h: In member function ‘std::__cxx11::string CBigNum::ToString(int) const’:
bignum.h:380:35: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘void BN_set_negative(BIGNUM*, int)’
BN_set_negative(&bn, false);
^
bignum.h:383:29: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
if (BN_cmp(&bn, &bn0) == 0)
^
bignum.h:385:32: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
while (BN_cmp(&bn, &bn0) > 0)
^
bignum.h:387:54: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_div(BIGNUM*, BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_div(&dv, &rem, &bn, &bnBase, pctx))
^
bignum.h:393:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_is_negative(const BIGNUM*)’
if (BN_is_negative(this))
^
bignum.h: In member function ‘bool CBigNum::operator!() const’:
bignum.h:426:31: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_is_zero(const BIGNUM*)’
return BN_is_zero(this);
^
bignum.h: In member function ‘CBigNum& CBigNum::operator+=(const CBigNum&)’:
bignum.h:431:35: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_add(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_add(this, this, &b))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator*=(const CBigNum&)’:
bignum.h:445:41: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_mul(BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_mul(this, this, &b, pctx))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator<<=(unsigned int)’:
bignum.h:464:41: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_lshift(BIGNUM*, const BIGNUM*, int)’
if (!BN_lshift(this, this, shift))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator>>=(unsigned int)’:
bignum.h:475:28: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
if (BN_cmp(&a, this) > 0)
^
bignum.h:481:41: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_rshift(BIGNUM*, const BIGNUM*, int)’
if (!BN_rshift(this, this, shift))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator++()’:
bignum.h:490:47: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_add(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_add(this, this, BN_value_one()))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator--()’:
bignum.h:507:45: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_sub(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_sub(&r, this, BN_value_one()))
^
bignum.h: In function ‘const CBigNum operator+(const CBigNum&, const CBigNum&)’:
bignum.h:532:27: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_add(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_add(&r, &a, &b))
^
bignum.h: In function ‘const CBigNum operator-(const CBigNum&, const CBigNum&)’:
bignum.h:540:27: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_sub(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_sub(&r, &a, &b))
^
bignum.h: In function ‘const CBigNum operator-(const CBigNum&)’:
bignum.h:548:43: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_is_negative(const BIGNUM*)’
BN_set_negative(&r, !BN_is_negative(&r));
^
bignum.h: In function ‘const CBigNum operator*(const CBigNum&, const CBigNum&)’:
bignum.h:556:33: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_mul(BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_mul(&r, &a, &b, pctx))
^
bignum.h: In function ‘const CBigNum operator/(const CBigNum&, const CBigNum&)’:
bignum.h:565:39: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_div(BIGNUM*, BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_div(&r, NULL, &a, &b, pctx))
^
In file included from bignum.h:17:0,
from chainparams.h:9,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h: In function ‘const CBigNum operator%(const CBigNum&, const CBigNum&)’:
bignum.h:574:10: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘2’ to ‘int BN_div(BIGNUM*, BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_mod(&r, &a, &b, pctx))
^
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h: In function ‘const CBigNum operator<<(const CBigNum&, unsigned int)’:
bignum.h:582:33: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_lshift(BIGNUM*, const BIGNUM*, int)’
if (!BN_lshift(&r, &a, shift))
^
bignum.h: In function ‘bool operator==(const CBigNum&, const CBigNum&)’:
bignum.h:594:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator==(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) == 0); }
^
bignum.h: In function ‘bool operator!=(const CBigNum&, const CBigNum&)’:
bignum.h:595:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator!=(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) != 0); }
^
bignum.h: In function ‘bool operator<=(const CBigNum&, const CBigNum&)’:
bignum.h:596:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator<=(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) <= 0); }
^
bignum.h: In function ‘bool operator>=(const CBigNum&, const CBigNum&)’:
bignum.h:597:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator>=(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) >= 0); }
^
bignum.h: In function ‘bool operator<(const CBigNum&, const CBigNum&)’:
bignum.h:598:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator<(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) < 0); }
^
bignum.h: In function ‘bool operator>(const CBigNum&, const CBigNum&)’:
bignum.h:599:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator>(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) > 0); }
^
make[3]: *** [Makefile:881: addrman.o] Error 1
make[3]: Leaving directory '/home/severoraz/lab/builds/Cryptonite/src'
make[2]: *** [Makefile:903: all-recursive] Error 1
make[2]: Leaving directory '/home/severoraz/lab/builds/Cryptonite/src'
make[1]: *** [Makefile:675: all] Error 2
make[1]: Leaving directory '/home/severoraz/lab/builds/Cryptonite/src'
make: *** [Makefile:509: all-recursive] Error 1
Also, pallas do you think it would be wise to point people to this thread from the github README.md file? Perhaps I'm too dumb but it took me days to find out that this project was actually not dead.
README.md links to the coin website, which in turn links to all the other resources like this thread, twitter, etc.
Oh yeah now I see it in the BCT thread, just didn't know what that meant.
EDIT 2017-09-25T1801
Issue fixed; errors resulted from the compiler not using openssl1.0. Fix taken from linked github ticket comment [1]. The following build script may be useful to you too:
Code:
export PKG_CONFIG_PATH="/usr/lib/openssl-1.0/pkgconfig" #CHANGE TO OWN OPENSSL PATH
export CXXFLAGS+=" -I/usr/include/openssl-1.0" #CHANGE TO OWN OPENSSL PATH
export LDFLAGS+=" -L/usr/lib/openssl-1.0 -lssl" #CHANGE TO OWN OPENSSL PATH
./autogen.sh
./configure CFLAGS="-O3 -march=native" CXXFLAGS="-O3 -march=native" --with-incompatible-bdb
make -j4
1: https://github.com/reddcoin-project/reddcoin/issues/103#issuecomment-322001599
September 25, 2017, 03:07:35 AM
Also, pallas do you think it would be wise to point people to this thread from the github README.md file? Perhaps I'm too dumb but it took me days to find out that this project was actually not dead.
README.md links to the coin website, which in turn links to all the other resources like this thread, twitter, etc.
September 25, 2017, 02:07:30 AM
Sorry if this is the wrong place, but I'm getting errors when attempting a build on Arch Linux 4.12.6-1-ARCH x86_64:
to name a few... am I the only one getting these errors? Am I missing something?
Also, pallas do you think it would be wise to point people to this thread from the github README.md file? Perhaps I'm too dumb but it took me days to find out that this project was actually not dead.
Code:
bignum.h:56:24: error: invalid use of incomplete type ‘BIGNUM {aka struct bignum_st}’
class CBigNum : public BIGNUM
^~~~~~
Code:
bignum.h:76:30: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’Code:
bignum.h:101:9: error: ‘BN_init’ was not declared in this scope
Code:
bignum.h:383:29: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’to name a few... am I the only one getting these errors? Am I missing something?
Also, pallas do you think it would be wise to point people to this thread from the github README.md file? Perhaps I'm too dumb but it took me days to find out that this project was actually not dead.
September 25, 2017, 01:32:47 AM
My ISP likes to change my ip too often, and that ruins my mining setup until i restart wallet.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
Are you on Windows or Linux? On my Ubuntu machine I can close the wallet just fine.
Windows QT wallet, latest rls.
Main wallet window closes, but "Cryptonite core is shutting down" remains until last miner disconnects.
Could you please try using the daemon version?
daemon version works fine! it can be closed and the miners idle until reloaded.
The problem when internet service is interrupted remains. Maybe its a network thing. Criptonited shows "finalize node". Then, when line comes back, it syncs again. But miners shows json error. And i have to restart wallet.
btw, What is the output for cryptonited hitting a block??
Sorry I can't reproduce that issue.
When it finds a block, you will have this line in debug.log:
proof-of-work found
Details follow after that.
September 24, 2017, 05:41:15 PM
My ISP likes to change my ip too often, and that ruins my mining setup until i restart wallet.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
Are you on Windows or Linux? On my Ubuntu machine I can close the wallet just fine.
Windows QT wallet, latest rls.
Main wallet window closes, but "Cryptonite core is shutting down" remains until last miner disconnects.
Could you please try using the daemon version?
daemon version works fine! it can be closed and the miners idle until reloaded.
The problem when internet service is interrupted remains. Maybe its a network thing. Criptonited shows "finalize node". Then, when line comes back, it syncs again. But miners shows json error. And i have to restart wallet.
btw, What is the output for cryptonited hitting a block??
September 24, 2017, 03:57:35 PM
So what and where is the current wallet for Windows?
Use the link in the OP?
Use the link in the OP?
Yes.
Cryptonite.info or github.
September 24, 2017, 03:55:38 PM
So what and where is the current wallet for Windows?
Use the link in the OP?
Use the link in the OP?
September 24, 2017, 03:37:55 PM
XCN wallet eats twice more then my previous champ - XVG. It consumes ~800Mb.
Is it possible todo something woth memory consumption?
Is it possible todo something woth memory consumption?
September 24, 2017, 03:17:57 PM
My ISP likes to change my ip too often, and that ruins my mining setup until i restart wallet.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
Are you on Windows or Linux? On my Ubuntu machine I can close the wallet just fine.
Windows QT wallet, latest rls.
Main wallet window closes, but "Cryptonite core is shutting down" remains until last miner disconnects.
Could you please try using the daemon version?
September 24, 2017, 02:44:47 PM
My ISP likes to change my ip too often, and that ruins my mining setup until i restart wallet.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
Are you on Windows or Linux? On my Ubuntu machine I can close the wallet just fine.
Windows QT wallet, latest rls.
Main wallet window closes, but "Cryptonite core is shutting down" remains until last miner disconnects.
September 24, 2017, 12:39:18 PM
My ISP likes to change my ip too often, and that ruins my mining setup until i restart wallet.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
Are you on Windows or Linux? On my Ubuntu machine I can close the wallet just fine.
September 24, 2017, 11:22:54 AM
My ISP likes to change my ip too often, and that ruins my mining setup until i restart wallet.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
But XCN wallet cant be closed while there are miners connecting to it. So i have to shut down each rig, everytime the damn ip changes...
Is there any workaround for that?
A faster restart of the wallet, or the ability to close it while miners are still connected would be nice.
September 23, 2017, 02:19:27 PM
The first example of the attack can be seen in this block: http://xcn-explorer.selektion21.de/?b=1007085
That block was mined late June, did this exploit have something to do with wallet problems during summer? I mean there were speculations about bad nodes and stuff like that?My mistake, didn't look dates closely enough, I thought it was June 2017. Now that all starts to make sense.
Someone made a shitton of money out of this, looks like xcn was just a small part of a bigger game, game that is getting closer to first overtime.
September 23, 2017, 07:23:19 AM
is there any news about the exploited blocks?
September 22, 2017, 03:20:07 PM
Does anyone in here have some experience with this P2P exchange?
--> bisq.network
Reason I'm asking: I just did a quick google for online exchanges (FIAT to crypto) that don't require ID and are non-centralized and bisq popped up.
The concept is very intriguing.
I will look into the exchange and see whether it's possible to add XCN.
Here are the requirements to get XCN listed:
https://forum.bisq.io/t/how-to-add-your-favorite-altcoin/46
Summary:
I think that suits us perfectly well, doesn't it? Especially as we might tick the special feature fast path requirement box.
--> bisq.network
Reason I'm asking: I just did a quick google for online exchanges (FIAT to crypto) that don't require ID and are non-centralized and bisq popped up.
The concept is very intriguing.
I will look into the exchange and see whether it's possible to add XCN.
Here are the requirements to get XCN listed:
https://forum.bisq.io/t/how-to-add-your-favorite-altcoin/46
Summary:
Quote
Here is a basic rule set to make the process and requirements transparent:
If the altcoin has a market cap or trading volume in the top 10 range we might add it without further requirements.
If we think that an altcoin has some outstanding novelty or properties we want to support we might add it without further requirements.
Other altcoins need to fulfill the following requirements:
The requesting person needs to be associated with the official coin (use an email address indicating that you are from the team)
They need to add Bitsquare as official exchange to their webpage.
There need to be an active block explorer available.
They need to send an example address of the altcoin.
The ticker symbol does not conflict with any Fiat or Altcoin symbol (Check here: https://en.wikipedia.org/wiki/ISO_4217142, https://coinmarketcap.com/currencies/13).
The requirements to add the coin does not cause extra effort for Bitsquare like adding additional input fields (e.g. if the addresss alone is not sufficient for the trade).
They need to provide the rules for validating a correct altcoin address. Input verification for the coin address will be added soon and we would need to get the specifics of a altcoin delivered from those who are interested that it get added (if the one who want to add a coin is not a developer he needs to request those information form the altcoin developers - Bitsquare will not do that task). A pull request with actual code contribution is preferred over pure text based information.
There need to be some trading activity. If for a period of 2 months no trade activity is visible that coin might get removed again.
If a coin represents political values which are diametral to Bitsquare’s values we reject it (e.g. fascistic, racist,…)
UPDATE:
Additional new requirement:
Pullrequest for the Altcoin address validation (Regex test + checksum test or anything else if there is anything specific) and Unittest for it (use Dev branch NOT master branch for PR).
Validation class is here37.
Unittest is here30.
IMPORTANT NOTICE:
In case the PR contains major flaws (e.g. the unit test fails, code is not compiling) I will reject the addition and not accept further requests. Unfortunately that happened quite often in the past and I don’t want to spend my limited time to test other developers untested PRs.
Another issue is that many don’t read this requirements and request addition of an altcoin without a PR.
I will ignore such requests in future.
If the altcoin has a market cap or trading volume in the top 10 range we might add it without further requirements.
If we think that an altcoin has some outstanding novelty or properties we want to support we might add it without further requirements.
Other altcoins need to fulfill the following requirements:
The requesting person needs to be associated with the official coin (use an email address indicating that you are from the team)
They need to add Bitsquare as official exchange to their webpage.
There need to be an active block explorer available.
They need to send an example address of the altcoin.
The ticker symbol does not conflict with any Fiat or Altcoin symbol (Check here: https://en.wikipedia.org/wiki/ISO_4217142, https://coinmarketcap.com/currencies/13).
The requirements to add the coin does not cause extra effort for Bitsquare like adding additional input fields (e.g. if the addresss alone is not sufficient for the trade).
They need to provide the rules for validating a correct altcoin address. Input verification for the coin address will be added soon and we would need to get the specifics of a altcoin delivered from those who are interested that it get added (if the one who want to add a coin is not a developer he needs to request those information form the altcoin developers - Bitsquare will not do that task). A pull request with actual code contribution is preferred over pure text based information.
There need to be some trading activity. If for a period of 2 months no trade activity is visible that coin might get removed again.
If a coin represents political values which are diametral to Bitsquare’s values we reject it (e.g. fascistic, racist,…)
UPDATE:
Additional new requirement:
Pullrequest for the Altcoin address validation (Regex test + checksum test or anything else if there is anything specific) and Unittest for it (use Dev branch NOT master branch for PR).
Validation class is here37.
Unittest is here30.
IMPORTANT NOTICE:
In case the PR contains major flaws (e.g. the unit test fails, code is not compiling) I will reject the addition and not accept further requests. Unfortunately that happened quite often in the past and I don’t want to spend my limited time to test other developers untested PRs.
Another issue is that many don’t read this requirements and request addition of an altcoin without a PR.
I will ignore such requests in future.
I think that suits us perfectly well, doesn't it? Especially as we might tick the special feature fast path requirement box.
September 22, 2017, 08:54:09 AM
wow hectic ... yeah i felt somthing was not right about this coin a while back ... some dishonest mining going down ... exploits .....who knows ......solo mining certainly was not working correctly like it used to before that . shame to hear this and good luck with stuff .
solo mining (since the krnlx fix) is working pretty fine now, less than 10% orphans; much better than before, for sure.
full member
Activity: 140
Merit: 100
your damned if you do, your damned if you dont lol
September 22, 2017, 08:47:20 AM
wow hectic ... yeah i felt somthing was not right about this coin a while back ... some dishonest mining going down ... exploits .....who knows ......solo mining certainly was not working correctly like it used to before that . shame to hear this and good luck with stuff .
Jump to: