Topic: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.2 - page 10. (Read 47574 times)

Your pool is good. And you put a new feature: workers
I really like this new feature on your pool.
I think the main problem is the coin dev.

I also started the mining NDC with 6 GH on your pool.

What confirmations? You should continue mine it.  You can try mine solo if my pool works badly.  
You increased coin difficulty too much with your 2 GH/S, other miners can't find any block now.  

Please mine it not more than 0,5 gh/s.   

Yes there are some problems on the pool or on the wallet.
Sometimes it works well sometimes not.
I hope it will be fixed soon.

I m still waiting for the confirmations for the mined coins.

Please stop trolling. Update is coming...

5 hours between blocks,   no update, dev is waiting the coin dies 

There is no problem with my pool:

Your pool not working now. I was mining with 10 gh but it fails now.

all blocks orphaned. @dev please fix it.

i believe Q2C will be alive again.

Why no update?

I recently had a problem - the wallet on the server has stuck and I was needed to restart it manually.
This never happened to my on any coin,  what the reason can be?

Someone mines Q2C on my pool with 2gh/s  
Once he goes we will stay without blocks for a week

people who have large q2c bag and think that their passive profits steady are wrong, the supply of coins will cause the price to fall (theory pos with little investor interest reworked many times) the only rescue is the high value added to the project, pos technology from the past crypto era. I think the reward for a block should be set above 1q2c in some sense algorithm, let alone qubitcoin die

@ penambang and startsts

Thanks for the suggestions.  I haven't yet had the spare time to see if these potential solutions work yet though.


How much cutting-and-pasting or manipulation of code would this really be?  Also, would the block-reward for POW stay at 1 Q2C per block? This is extremely minuscule for a coin with potentially into the hundred millions of supply and with definitely more than 12 million currently sitting in sell-orders on Cryptopia.  What would the POS staking percentage be? 2? 5%? 10? or something that makes the inflation-rate potentially ridiculous with new coins generated "like funnel-cakes at a state-fair" such as with Buzzcoin (1200% per year), 808coin (variable POS, but 808% at the peak if I understand properly) or Philosopher Stones (50%)?

As it relates to the question of supply and the three canonical/classical functions of money (a means of indirect exchange, a store of value, and a unit or basis of account) it is perhaps worth considering what's termed the "Quantity Theory of Money" (for instance see: http://www.investopedia.com/articles/05/010705.asp ).  I'm pretty into the Austrian economics school, so I do think excessive creation of money will reduce the buying power of each unit of that type of money and experience will show that theory to be inductively sound.

I think there is a way to implement a poll on this thread (from what I've seen on other threads).  I wonder what the bag-or-stakeholders think(?).

I received (partially done) update from one developer but I don't want to use this as the communication with him was really poor. He updated only the wallet. The rest of the the files were not updated.
As you already seen, block reward was already set to be 1 Q2C so that part was OK. What was changed is the difficulty algorithm.

I am currently looking someone to properly do the update and if all goes OK continue working on PoS/PoW hybrid.

Any developers interested? Or maybe someone knows who would be willing to work on this?

Any news about Q2C update?

Cryptohub now has GUI miner and some more users are mining Q2C 

If you using ubuntu, installing BDB4.8 via PPA is more simple,


Read here for more details on building under unix:
https://github.com/willowrose/QubitCoin/blob/master/doc/build-unix.md

heratys111  Did you check debug.log ?

@ penambang and startsts

I was hoping it would be as simple as adding listen=1 in the config file, but the same result/error/nothing-productive occurred.

> penambang: Are you using bdb 5.3? I have no problem compiling qt wallet on ubuntu 16.04 with bdb 4.8 from bitcoin ppa.

It's probably using BDB version 5.3... For example, after some searching online, I saw this suggested command:

$ apt-cache search berkeley

The output to that command in the terminal was this long list of applications located:

bind9 - Internet Domain Name Server
db-util - Berkeley Database Utilities
db5.3-doc - Berkeley v5.3 Database Documentation
db5.3-util - Berkeley v5.3 Database Utilities
dnsutils - Clients provided with BIND
libberkeleydb-perl - use Berkeley DB databases from Perl
libbind-export-dev - Development files for the exported BIND libraries
libbind9-140 - BIND9 Shared Library used by BIND
libdb++-dev - Berkeley Database Libraries for C++ [development]
libdb-dev - Berkeley Database Libraries [development]
libdb-java-dev - Berkeley Database Libraries for Java [development]
libdb-sql-dev - Berkeley Database Libraries [SQL development]
libdb5.3 - Berkeley v5.3 Database Libraries [runtime]
libdb5.3++ - Berkeley v5.3 Database Libraries for C++ [runtime]
libdb5.3++-dev - Berkeley v5.3 Database Libraries for C++ [development]
libdb5.3-dbg - Berkeley v5.3 Database Libraries [debug]
libdb5.3-dev - Berkeley v5.3 Database Libraries [development]
libdb5.3-java - Berkeley v5.3 Database Libraries for Java
libdb5.3-java-dev - Berkeley v5.3 Database Libraries for Java [development]
libdb5.3-java-gcj - Berkeley v5.3 Database Libraries for Java (native code)
libdb5.3-java-jni - Berkeley v5.3 Database Libraries for Java
libdb5.3-sql - Berkeley v5.3 Database Libraries [SQL runtime]
libdb5.3-sql-dev - Berkeley v5.3 Database Libraries [SQL development]
libdb5.3-stl - Berkeley v5.3 Database Libraries [STL runtime]
libdb5.3-stl-dev - Berkeley v5.3 Database Libraries [STL development]
libdns-export162 - Exported DNS Shared Library
libdns162 - DNS Shared Library used by BIND
libirs-export141 - Exported IRS Shared Library
libirs141 - DNS Shared Library used by BIND
libisc-export160 - Exported ISC Shared Library
libisc160 - ISC Shared Library used by BIND
libisccc-export140 - Command Channel Library used by BIND
libisccc140 - Command Channel Library used by BIND
libisccfg-export140 - Exported ISC CFG Shared Library
libisccfg140 - Config File Handling Library used by BIND
liblwres141 - Lightweight Resolver Library used by BIND
libnss-db - NSS module for using Berkeley Databases as a naming service
libsasl2-modules-db - Cyrus SASL - pluggable authentication modules (DB)
python-bsddb3 - Python interface for Berkeley DB
python-bsddb3-dbg - Python interface for Berkeley DB (debug extension)
python-bsddb3-doc - Documentation for the python Berkeley DB interface module
python3-bsddb3 - Python interface for Berkeley DB (Python 3.x)
python3-bsddb3-dbg - Python interface for Berkeley DB (debug extension, Python 3.x)
bdbvu - simple GUI tool to browse Berkeley DB databases
bdii - Berkeley Database Information Index (BDII)
berkeley-abc - ABC - A System for Sequential Synthesis and Verification
berkeley-express - Streaming quantification for high-throughput sequencing
berkeley-express-doc - Documentation for RNA-Seq tool eXpress
blcr-testsuite - Userspace tools to Checkpoint and Restart Linux processes
blcr-util - Userspace tools to Checkpoint and Restart Linux processes
bogofilter-bdb - fast Bayesian spam filter (Berkeley DB)
boinc - metapackage for the BOINC client and the manager
boinc-client - core client for the BOINC distributed computing infrastructure
boinc-client-fglrx - metapackage for AMD/ATI fglrx-savvy BOINC client and manager
boinc-client-nvidia-cuda - metapackage for CUDA-savvy BOINC client and manager
boinc-client-opencl - metapackage for AMD/ATI OpenCL-savvy BOINC client and manager
boinc-dbg - debugging symbols for BOINC binaries
boinc-manager - GUI to control and monitor the BOINC core client
boinc-screensaver - screen saver auto-controlling volunteer computing
btyacc - Backtracking parser generator based on byacc
byacc - public domain Berkeley LALR Yacc parser generator
byacc-j - Berkeley YACC parser generator extended to generate Java code
clisp-module-berkeley-db - clisp module that adds an interface to Berkeley DB
db-upgrade-util - Berkeley Database Utilities (old versions)
db5.3-sql-util - Berkeley v5.3 SQL Database Utilities
flex-old - Old version of the fast lexical analyzer generator
hesiod - Project Athena's DNS-based directory service - utilities
jflex - lexical analyzer generator for Java
kamailio-berkeley-bin - Berkeley database module for Kamailio - helper program
kamailio-berkeley-modules - Berkeley database module for Kamailio
lib32cr0 - (32bit) Libraries to Checkpoint and Restart Linux processes
libbind-confparser-perl - Parser class for BIND configuration files
libboinc-app-dev - development files to build applications for BOINC projects
libboinc-app7 - libraries for BOINC's scientific applications
libboinc7 - libraries of BOINC the client depends on
libcache-bdb-perl - object caching wrapper around BerkeleyDB
libcr-dbg - Libraries to Checkpoint and Restart Linux processes
libcr-dev - Development files for BLCR
libcr0 - Libraries to Checkpoint and Restart Linux processes
libdb-java - Berkeley Database Libraries for Java
libdb-je-java - Oracle Berkeley Database Java Edition
libdb1-compat - Berkeley database routines [glibc 2.0/2.1 compatibility]
libdb5.3-tcl - Berkeley v5.3 Database Libraries for Tcl [module]
libhawknl - Hawk game oriented network library API
libhawknl-dbg - Hawk game oriented network library API (debug package)
libhawknl-dev - Hawk game oriented network library API (development headers)
libhesiod-dev - Project Athena's DNS-based directory service - development files
libhesiod0 - Project Athena's DNS-based directory service - libraries
libicedb35v5 - Libraries for persistent backends for ZeroC Ice
liblo-dev - Lightweight OSC library -- development files
liblo-tools - Lightweight OSC library
liblo7 - Lightweight OSC library
liblwipv6-2 - User level (lightweight) TCP/IP stack with IPv6 support
liblwipv6-dev - Development files for the LWIPv6 library
libpantomime1.2-dev - GNUstep framework for mail handling (development files)
libqxt-berkeley0 - Berkeley databases module for Qt (LibQxt)
libsmpeg-dev - SDL MPEG Player Library - development files
libsmpeg0 - SDL MPEG Player Library - shared libraries
lprng - lpr/lpd printer spooling system
lprng-doc - lpr/lpd printer spooling system (documentation)
magic - VLSI layout tool
memcachedb - Persistent storage engine using the memcache protocol
netsniff-ng - Linux network packet sniffer toolkit
oregano - tool for schematical capture of electronic circuits
perdition - POP3 and IMAP4 Proxy server
perl-byacc - Berkeley LALR parser generator, Perl version
reprepro - Debian package repository producer
ruby-bdb - interface to Berkeley DB for Ruby
s-nail - feature-rich BSD mail(1)
skksearch - SKK dictionary server handling multiple dictionaries
smpeg-gtv - SMPEG GTK+ MPEG audio/video player
smpeg-plaympeg - SMPEG command line MPEG audio/video player
spamprobe - Bayesian spam filter
tcsh - TENEX C Shell, an enhanced version of Berkeley csh
tophat - fast splice junction mapper for RNA-Seq reads
ucblogo - dialect of lisp using turtle graphics famous for teaching kids
cluster3 - Reimplementation of the Eisen-clustering software
libdb4.8 - Berkeley v4.8 Database Libraries [runtime]
libdb4.8-dev - Berkeley v4.8 Database Libraries [development]
libdb4.8++ - Berkeley v4.8 Database Libraries for C++ [runtime]
libdb4.8++-dev - Berkeley v4.8 Database Libraries for C++ [development]
libdb4.8-tcl - Berkeley v4.8 Database Libraries for Tcl [module]
db4.8-util - Berkeley v4.8 Database Utilities
libdb4.8-dbg - Berkeley v4.8 Database Libraries [debug]
libdb4.8-java - Berkeley v4.8 Database Libraries for Java
libdb4.8-java-dev - Berkeley v4.8 Database Libraries for Java [development]
libdb4.8-java-gcj - Berkeley v4.8 Database Libraries for Java (native code)
db4.8-doc - Berkeley v4.8 Database Documentation

I downloaded Berkeley version 4.8 into a folder but I'm not sure how to get autogen.sh and/or configure to incorporate this directory while compiling (yet?) .  I also can't claim to understand what the function of Berkelely DB actually is (or what it does).  It's probably really simple... for example, when I type ".configure --help" in the bottom-level directory for QubitCoin, it outputs a long of possible flags or options that might be used (and it's probably some simple input to configure that will allow Berkeley 4.8 to be incorporated and hopefully after providing the suitable commands this thing will work effectively from there.

Are you using bdb 5.3?
I have no problem compiling qt wallet on ubuntu 16.04 with bdb 4.8 from bitcoin ppa.

heratys111

Perhaps you need add to conf

listen=1


I have 16.04 on server and I don't remember any problem with qubit wallet.
Can you check debug.log?

Hi,

There doesn't seem to be an "issues" page at the Github so...

The application seemed to build in Ubuntu 16.04 LTS but doesn't function.  For the configure (pre-build) I used the "--build-with-incompatible-bdb" flag (as it wouldn't compile otherwise).

However, the qt aborts with a "Segmentation fault" message.  Also, while "./qubitcoind --daemon" outputs "Qubitcoin server starting" it doesn't take RPC commands, and "./qubitcoin-cli " outputs "error: couldn't connect to server".

My config file (named QubitCoin.conf and located in the folder where altcoins usually look for it): contains: the rpcuser, rpcpassword, and addnodes with :7788 as the port on other nodes to connect to (none of which is likely to be the problem).  I've also got (including comments):

~~~~~~~~ From Config file ~~~~~~~~~

...

rpcallowip=127.0.0.1 #Used for solomining? or to communicate using client?

rpcport=7799  # listen for RPC connections on this port
port=7788 # port on other nodes to connect to
gen=0 # not attempting to generate QubitCoin, whereas gen=1 would
server=1 # tells QubitCoin.conf to accept JSON-RPC commands

#mining=0
# mining=1 attempting to solo-mine
#commented these out because simply trying to download blockchain/initialize

keypool=1000 #pre-generate this many key-pairs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

What am I missing or what could be the problem here? 
Is 7799 the right rpcport (it would be helpful if this info was in the announcement/OP page)

Do I need to rebuild this without the --with-incompatible-bdb flag or with this:
 ./configure --with-qt --enable-wallet --with-incompatible-bdb or is the problem something missing from the config file?

Thanks in advance for any help.

I made a request on Coinmarketcap to delete non existing explorer link and change the link for website.