Pages:
Author

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

hero member
Activity: 1246
Merit: 708
How I wish I sold my 500k for 50sat each Sad
Now it is  123sat at
https://novaexchange.com/market/BTC_Q2C/
wgd
legendary
Activity: 1815
Merit: 1005
~90 searches per day in last week - a keyword "QubitCoin"  Shocked

https://www.google.pl/trends/explore?date=today%203-m&q=qubitcoin

hero member
Activity: 796
Merit: 505
Hi,

I'm making new stratum pool for you, testing it atm.

legendary
Activity: 2534
Merit: 1129
yes, I have already written pm to the person who can do something with it Smiley

ps. network looks really well ..


blocks : 2013391,
connections" : 15,


Yes, I was surprised at the number of connections, even at this early stage of revival.

I was involved with Q2C in 2014, and it was  quite well distributed.  I think it was even traded on over 10 exchanges at one time, so the infrastructure was good. I believe that there are quite a lot of coins which are permanently unavailable to the market, but there is no way of estimating that number.
wgd
legendary
Activity: 1815
Merit: 1005
yes, I have already written pm to the person who can do something with it Smiley

ps. network looks really well ..


blocks : 2013391,
connections" : 15,
hero member
Activity: 548
Merit: 501
block explorer seems stuck on block 2009297
newbie
Activity: 34
Merit: 0
The different block chains is due to the new 0.11 clients starting to enforce the soft-forks from Bitcoin (BIP34, BIP65, etc).

These are enforced if a certain number of blocks are mined on the new wallet.

Since the majority seems to be on the new wallet, I suggest everyone upgrade to the new version to remain compatible.

To get the fork info on the new wallet you can type:

getblockchaininfo


{
"chain" : "main",
"blocks" : 2010486,
"headers" : 2010486,
"bestblockhash" : "00000006a0f46da556779ea27b0ae43054ab294500ea1bfbe5a97871a8c35eed",
"difficulty" : 0.13478134,
"verificationprogress" : 1.00000026,
"chainwork" : "000000000000000000000000000000000000000000000000001dc91cf4f3258c",
"pruned" : false,
"softforks" : [
{
"id" : "bip34",
"version" : 2,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
},
{
"id" : "bip66",
"version" : 3,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
},
{
"id" : "bip65",
"version" : 4,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
}
]
}


I've been running 0.8.4.1 on a mac since April 2014, the last couple of days I get the message
'Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.'
As there is no new mac wallet available, what do I do? 
Type in the above commands in Debug Window/Console?

Here's a Mac build I created from the 0.11.2.1 source. Give it a try:

https://github.com/willowrose/QubitCoin/releases/download/v0.11.2.1/q2c-0.11.2.1-osx.dmg

legendary
Activity: 2534
Merit: 1129
i want to purchase some q2c, paying 2 satoshi per coin

Last trade on Nova Exchange was 123 sats, and there have been a lot for more than that, so maybe you need to revise your price !

I will be putting a few bids in on the exchange, hopefully can get some around 120 sats.
sr. member
Activity: 637
Merit: 250
The different block chains is due to the new 0.11 clients starting to enforce the soft-forks from Bitcoin (BIP34, BIP65, etc).

These are enforced if a certain number of blocks are mined on the new wallet.

Since the majority seems to be on the new wallet, I suggest everyone upgrade to the new version to remain compatible.

To get the fork info on the new wallet you can type:

getblockchaininfo


{
"chain" : "main",
"blocks" : 2010486,
"headers" : 2010486,
"bestblockhash" : "00000006a0f46da556779ea27b0ae43054ab294500ea1bfbe5a97871a8c35eed",
"difficulty" : 0.13478134,
"verificationprogress" : 1.00000026,
"chainwork" : "000000000000000000000000000000000000000000000000001dc91cf4f3258c",
"pruned" : false,
"softforks" : [
{
"id" : "bip34",
"version" : 2,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
},
{
"id" : "bip66",
"version" : 3,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
},
{
"id" : "bip65",
"version" : 4,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
}
]
}


I've been running 0.8.4.1 on a mac since April 2014, the last couple of days I get the message
'Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.'
As there is no new mac wallet available, what do I do? 
Type in the above commands in Debug Window/Console?
wgd
legendary
Activity: 1815
Merit: 1005
willowrose 'm already ok, I mess with libdb*  Roll Eyes

--

Cryptopia added QubitCoin to vote list, today reset counter  Grin

https://www.cryptopia.co.nz/Vote

hero member
Activity: 526
Merit: 502
Long time no solo mining and things changed i looking for the right cpu miner.
newbie
Activity: 34
Merit: 0
root@s3c:~/QubitCoin/src# ./qubitcoind --daemon
Qubitcoin server starting
root@s3c:~/QubitCoin/src# Error:


debug.log:

2016-10-15 18:42:27 Qubitcoin version v0.11.2.1 (2016-09-24 20:19:42 +0200)
2016-10-15 18:42:27 Using OpenSSL version OpenSSL 1.0.1t  3 May 2016
2016-10-15 18:42:27 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-10-15 18:42:27 Default data directory /root/.QubitCoin
2016-10-15 18:42:27 Using data directory /root/.QubitCoin
2016-10-15 18:42:27 Using config file /root/.QubitCoin/QubitCoin.conf
2016-10-15 18:42:27 Using at most 125 connections (1024 file descriptors available)
2016-10-15 18:42:27 Using 0 threads for script verification
2016-10-15 18:42:27 Binding RPC on address :: port 7799 (IPv4+IPv6 bind any: 1)
2016-10-15 18:42:27 Using wallet wallet.dat
2016-10-15 18:42:27 init message: Verifying wallet...
2016-10-15 18:42:27 CDBEnv::Open: LogDir=/root/.QubitCoin/database ErrorFile=/root/.QubitCoin/db.log
2016-10-15 18:42:27 ERROR: CDBEnv::Open: Error 22 opening database environment: Invalid argument

2016-10-15 18:42:27 Moved old /root/.QubitCoin/database to /root/.QubitCoin/database.1476556947.bak. Retrying.
2016-10-15 18:42:27 CDBEnv::Open: LogDir=/root/.QubitCoin/database ErrorFile=/root/.QubitCoin/db.log
2016-10-15 18:42:27 ERROR: CDBEnv::Open: Error 22 opening database environment: Invalid argument

2016-10-15 18:42:27 Error:
2016-10-15 18:42:27 Shutdown: In progress...
2016-10-15 18:42:27 StopNode()
2016-10-15 18:42:27 Shutdown: done



can not see work qubitcoin wallet process, a vps with 1gb ram, maybe here is the problem?

Looks like some file format issue.

Are you sure your wallet was created with the same version of bdb 4.8.30? If you compile with different versions of bdb your wallets won't be compatible.
wgd
legendary
Activity: 1815
Merit: 1005
root@s3c:~/QubitCoin/src# ./qubitcoind --daemon
Qubitcoin server starting
root@s3c:~/QubitCoin/src# Error:


debug.log:

2016-10-15 18:42:27 Qubitcoin version v0.11.2.1 (2016-09-24 20:19:42 +0200)
2016-10-15 18:42:27 Using OpenSSL version OpenSSL 1.0.1t  3 May 2016
2016-10-15 18:42:27 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2016-10-15 18:42:27 Default data directory /root/.QubitCoin
2016-10-15 18:42:27 Using data directory /root/.QubitCoin
2016-10-15 18:42:27 Using config file /root/.QubitCoin/QubitCoin.conf
2016-10-15 18:42:27 Using at most 125 connections (1024 file descriptors available)
2016-10-15 18:42:27 Using 0 threads for script verification
2016-10-15 18:42:27 Binding RPC on address :: port 7799 (IPv4+IPv6 bind any: 1)
2016-10-15 18:42:27 Using wallet wallet.dat
2016-10-15 18:42:27 init message: Verifying wallet...
2016-10-15 18:42:27 CDBEnv::Open: LogDir=/root/.QubitCoin/database ErrorFile=/root/.QubitCoin/db.log
2016-10-15 18:42:27 ERROR: CDBEnv::Open: Error 22 opening database environment: Invalid argument

2016-10-15 18:42:27 Moved old /root/.QubitCoin/database to /root/.QubitCoin/database.1476556947.bak. Retrying.
2016-10-15 18:42:27 CDBEnv::Open: LogDir=/root/.QubitCoin/database ErrorFile=/root/.QubitCoin/db.log
2016-10-15 18:42:27 ERROR: CDBEnv::Open: Error 22 opening database environment: Invalid argument

2016-10-15 18:42:27 Error:
2016-10-15 18:42:27 Shutdown: In progress...
2016-10-15 18:42:27 StopNode()
2016-10-15 18:42:27 Shutdown: done



can not see work qubitcoin wallet process, a vps with 1gb ram, maybe here is the problem?
newbie
Activity: 34
Merit: 0
root@s3c:~/QubitCoin/src# ./qubitcoind
Error:

what is wrong? Wink



What is the error message?

usually you run it:

./qubitcoind --daemon
wgd
legendary
Activity: 1815
Merit: 1005
root@s3c:~/QubitCoin/src# ./qubitcoind
Error:

what is wrong? Wink

newbie
Activity: 34
Merit: 0
Blockchain stoped working the old wallets 8.4.1-8.4.3 are on block 2008003 things not going very well.
New wallet 11.2.1 ccminer fails on json_rpc_call.
To many problems again.
Two blockchains working in parallel the old wallets on block 2008003 at this moment and the new wallet on block 2008990.
Never liked unnecessary upgrade.

In later Bitcoin they changed the rpc interface. It now uses a new call "getblocktemplate"

https://en.bitcoin.it/wiki/Getblocktemplate

Have you tried an updated miner? This one looks like it supports qubit and getblocktemplate:

https://github.com/Atrides/sph-sgminer

full member
Activity: 162
Merit: 100
newbie
Activity: 23
Merit: 0
i want to purchase some q2c, paying 2 satoshi per coin
newbie
Activity: 34
Merit: 0
The different block chains is due to the new 0.11 clients starting to enforce the soft-forks from Bitcoin (BIP34, BIP65, etc).

These are enforced if a certain number of blocks are mined on the new wallet.

Since the majority seems to be on the new wallet, I suggest everyone upgrade to the new version to remain compatible.

To get the fork info on the new wallet you can type:

getblockchaininfo


{
"chain" : "main",
"blocks" : 2010486,
"headers" : 2010486,
"bestblockhash" : "00000006a0f46da556779ea27b0ae43054ab294500ea1bfbe5a97871a8c35eed",
"difficulty" : 0.13478134,
"verificationprogress" : 1.00000026,
"chainwork" : "000000000000000000000000000000000000000000000000001dc91cf4f3258c",
"pruned" : false,
"softforks" : [
{
"id" : "bip34",
"version" : 2,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
},
{
"id" : "bip66",
"version" : 3,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
},
{
"id" : "bip65",
"version" : 4,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
}
]
}
hero member
Activity: 526
Merit: 502
Nice try to revive Q2C but its very hard i am wathcing this coin from the begining and strange things always happen, the most secure version so far is the initial 0.8.4.1.
Pages:
Jump to: