altmarkets got hacked, we all lost coins. Now there are other better markets open  check out httpq://www.finexbox.com Happy New Year! fyi, finexbox is a scam , most orders executed arent happening, withdraws arent working good luck |
|
|
|
 QMC Is now trading on Bisq ! i threw some cheap QMC for sale on it  also, keep in mind that without usage , Bisq will delist the coin |
|
|
|
QMC Is now trading on Bisq ! i threw some cheap QMC for sale on it once someone buys it , QMC might be on CMC (as Bisq is indexed by CMC) |
|
|
|
I really hope you pulled before compiling today - otherwise you'll be annoyed.
i did We should add -lcap -as-needed ; though I think it only applies to ubuntus (doesn't seem to happen on the debian gitian image)
this was on a debian jessie |
|
|
|
fixed it, just missed a -lcap who knew you had to link to libraries to use them also, would be nice if this 'hardfork' would have mentioned that the datadir moved from 'qmc2' to 'qmc' , made me scratch my head a while so you basically just replaced -all- the sourcecode, what for? why couldnt you just merge the updates? at least it'll be interesting to see if staking now finally works |
|
|
|
(i notice commits to the git master, i'll try building again)
fresh new errors; CXXLD qmcd
../tor/src/common/libor.a(compat.o): In function `drop_capabilities':
compat.c:(.text+0xed): undefined reference to `cap_get_proc'
compat.c:(.text+0x101): undefined reference to `cap_clear'
compat.c:(.text+0x116): undefined reference to `cap_set_flag'
compat.c:(.text+0x12e): undefined reference to `cap_set_flag'
compat.c:(.text+0x149): undefined reference to `cap_set_flag'
compat.c:(.text+0x151): undefined reference to `cap_set_proc'
compat.c:(.text+0x15b): undefined reference to `cap_free'
../tor/src/common/libor.a(compat.o): In function `have_capability_support':
compat.c:(.text+0x25f5): undefined reference to `cap_get_proc'
compat.c:(.text+0x2604): undefined reference to `cap_free'
collect2: error: ld returned 1 exit status
Makefile:3071: recipe for target 'qmcd' failed
make[2]: *** [qmcd] Error 1
make[2]: Leaving directory '/home/buzz/QMC/src'
Makefile:8040: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/buzz/QMC/src'
Makefile:603: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
|
|
|
|
A hasty commit
what was the reason to be hasty and not precise? (i notice commits to the git master, i'll try building again) |
|
|
|
Strange - have you done a 'make clean' before make ?
its a fresh pull git clone http:///..
cd QMC
./autogen.sh
LDFLAGS="-L/home/buzz/DB48/lib/" CPPFLAGS="-I/home/buzz/DB48/include/" ./configure --disable-tests
make
boom error , on exact same platform previous worked fine , i noticed diff was 99% formatting mods, what gives? |
|
|
|
also, seems current git no longer compiles ; CXXLD qmcd
qmcd-qmcd.o: In function `AppInit(int, char**)':
/home/buzz/QMC/src/qmcd.cpp:73: undefined reference to `FormatFullVersion()'
libbitcoin_server.a(libbitcoin_server_a-init.o): In function `AppInit2(boost::thread_group&)':
/home/buzz/QMC/src/init.cpp:1084: undefined reference to `FormatFullVersion()'
/home/buzz/QMC/src/init.cpp:1084: undefined reference to `CLIENT_DATE'
libbitcoin_server.a(libbitcoin_server_a-net.o): In function `ThreadMapPort()':
/home/buzz/QMC/src/net.cpp:1035: undefined reference to `FormatFullVersion()'
libbitcoin_server.a(libbitcoin_server_a-net.o): In function `CNode::PushVersion()':
/home/buzz/QMC/src/net.cpp:486: undefined reference to `CLIENT_NAME'
/home/buzz/QMC/src/net.cpp:486: undefined reference to `FormatSubVersion(std::string const&, int, std::vector<std::string, std::allocator<std::string> > const&)'
libbitcoin_server.a(libbitcoin_server_a-alert.o): In function `CAlert::AppliesToMe() const':
/home/buzz/QMC/src/alert.cpp:124: undefined reference to `CLIENT_NAME'
/home/buzz/QMC/src/alert.cpp:124: undefined reference to `FormatSubVersion(std::string const&, int, std::vector<std::string, std::allocator<std::string> > const&)'
libbitcoin_server.a(libbitcoin_server_a-rpcnet.o): In function `getnetworkinfo(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::string> >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::string> > > > const&, bool)':
/home/buzz/QMC/src/rpcnet.cpp:387: undefined reference to `CLIENT_NAME'
/home/buzz/QMC/src/rpcnet.cpp:387: undefined reference to `FormatSubVersion(std::string const&, int, std::vector<std::string, std::allocator<std::string> > const&)'
libbitcoin_util.a(libbitcoin_util_a-rpcprotocol.o): In function `HTTPPost(std::string const&, std::map<std::string, std::string, std::less<std::string>, std::allocator<std::pair<std::string const, std::string> > > const&)':
/home/buzz/QMC/src/rpcprotocol.cpp:50: undefined reference to `FormatFullVersion()'
libbitcoin_util.a(libbitcoin_util_a-rpcprotocol.o): In function `HTTPReplyHeader(int, bool, unsigned long, char const*)':
/home/buzz/QMC/src/rpcprotocol.cpp:128: undefined reference to `FormatFullVersion()'
libbitcoin_util.a(libbitcoin_util_a-rpcprotocol.o): In function `HTTPError(int, bool, bool)':
/home/buzz/QMC/src/rpcprotocol.cpp:106: undefined reference to `FormatFullVersion()'
libbitcoin_wallet.a(libbitcoin_wallet_a-rpcdump.o): In function `dumpwallet(std::vector<json_spirit::Value_impl<json_spirit::Config_vector<std::string> >, std::allocator<json_spirit::Value_impl<json_spirit::Config_vector<std::string> > > > const&, bool)':
/home/buzz/QMC/src/rpcdump.cpp:369: undefined reference to `CLIENT_DATE'
/home/buzz/QMC/src/rpcdump.cpp:369: undefined reference to `CLIENT_BUILD'
collect2: error: ld returned 1 exit status
Makefile:3071: recipe for target 'qmcd' failed
make[2]: *** [qmcd] Error 1
make[2]: Leaving directory '/home/buzz/QMC/src'
Makefile:8040: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/buzz/QMC/src'
Makefile:603: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
|
|
|
|
We forked the network.
Please update your wallets ! (v1.1.1)
does staking work now? |
|
|
|
I'm just having a doubt about the concept
Yeah i see literally -zero- masternoders casting -any- votes on torrents over 99% of the torrents (even those of high quality) are -not- 'yay'd inside the budget proposals hack |
|
|
|
(this can also be done manually as tor is built in!)
every coin that forked off of bitcoin has tor support though , not really special  |
|
|
|
... at some point before we had to halt trading...
are you saying you operate a exchange? |
|
|
|
|
there's just a single line of notification in the top post saying there was a hardfork
|
|
|
|
|
thats with that latest version , oh wait, you guys released a newer version since without announcing , thanks
|
|
|
|
Anyone still able to sync from zero?
Just setup a new node -and- its connecting to peers, but they all have -1 height, so no blocks to sync to.
just a whole lot of this in debug.log; 2018-10-24 14:05:04 socket sending timeout: 1201s
2018-10-24 14:05:04 SOCKS5 connecting 54.38.76.79
2018-10-24 14:05:04 SOCKS5 connected 54.38.76.79
2018-10-24 14:05:20 PROCESSMESSAGE: INVALID MESSAGESTART dseep peer=49
2018-10-24 14:06:28 SOCKS5 connecting 54.38.76.75
2018-10-24 14:06:28 SOCKS5 connected 54.38.76.75
2018-10-24 14:07:32 SOCKS5 connecting 54.38.145.192
2018-10-24 14:07:32 SOCKS5 connected 54.38.145.192
2018-10-24 14:07:53 SOCKS5 connecting 54.38.76.75
2018-10-24 14:07:53 SOCKS5 connected 54.38.76.75
2018-10-24 14:08:01 keypool reserve 4
2018-10-24 14:08:01 keypool return 4
2018-10-24 14:08:15 SOCKS5 connecting 136.243.26.230
2018-10-24 14:08:15 SOCKS5 connected 136.243.26.230
2018-10-24 14:08:39 SOCKS5 connecting 54.38.148.199
2018-10-24 14:08:49 SOCKS5 connected 54.38.148.199
2018-10-24 14:09:09 SOCKS5 connecting 51.38.75.175
2018-10-24 14:09:09 ERROR: Proxy error: connection refused
2018-10-24 14:09:32 SOCKS5 connecting 54.38.145.192
2018-10-24 14:09:32 SOCKS5 connected 54.38.145.192 |
|
|
|
|
Anyone still able to sync from zero?
Just setup a new node -and- its connecting to peers, but they all have -1 height, so no blocks to sync to.
|
|
|
|
It has been sorted. Just some kid DDoSing Masternodes - can happen to any network.
And one of the MN is also the webserver? tsk tsk |
|
|
|
Some DDoS going on - guess we're doing something right  you cant DDoS a cryptocurrency network, there's no central servers to attack and the -code- doesnt have a DoS (and if it -did- it would absolute mean you ARENT doing something right, because you would have added that) |
|
|
|
|
Show Posts
