Search content
Sort by
Showing 20 of 34 results by willowrose
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.2
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.2
Today build in miner was working fine but at the afternoon gave this error.
Code:
2016-10-27 18:26:46 QubitcoinMiner started
2016-10-27 18:26:46 Error in QubitcoinMiner: Keypool ran out, please call keypoolrefill before restarting the mining thread
2016-10-27 18:26:46 Error in QubitcoinMiner: Keypool ran out, please call keypoolrefill before restarting the mining thread
This happens when your list of keys have been all used by the miner. Your wallet is probably locked, so it can't create new addresses for you.
You can manually top up your key pool with:
walletpassphrase 'mypassword' 1000
keypoolrefill
I think the miner should automatically refill the keypool if you mine with your wallet unlocked, I haven't checked this myself.
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
QubitCoin 0.11.2.2
* Increase default maximum fee
* UI text changes
Win32, Win64 and OSX versions:
https://github.com/willowrose/QubitCoin/releases/tag/v0.11.2.2
Note, VirusTotal detects 3 potential issues with the Win32 version, but as far as I can tell those are false positives.
* Increase default maximum fee
* UI text changes
Win32, Win64 and OSX versions:
https://github.com/willowrose/QubitCoin/releases/tag/v0.11.2.2
Note, VirusTotal detects 3 potential issues with the Win32 version, but as far as I can tell those are false positives.
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
When I try to send some Qubits my wallet freezes i.e. spinning beachball of death.
Any ideas what I can do, it's the mac wallet v0.11.2.1
Any ideas what I can do, it's the mac wallet v0.11.2.1
I tried sending on OSX 10.11 and it worked on my setup. Which version of OSX are you using? Does it always happen? Maybe try reindex or redownloading the blockchain.
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
Good news!
What about diff being so big that no new block shown in about 15-20 minutes? :-)
"blocks" : 2021151,
What about diff being so big that no new block shown in about 15-20 minutes? :-)
Code:
"blocks" : 2021151,
Qubit retargets every 20 blocks, by cutting difficulty up to half. It is possible to modify the algorithm, but it will require a hard fork. Even if we change difficulty with every block, there's not much you can do when 90% of the hash rate is suddenly removed, it is going to take time to find the next block before it adjusts, and then it will also take a few more blocks to adjust to target.
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
willowrose -maxtxfee= work fine thx!
Great! I'll change the default in the next release.
We currently use the default of 1000 satoshi's / byte (carried over from the Bitcoin code base) as transaction fee. A satoshi in Bitcoin (0.00000001) is smaller than a Satoshi in Qubitcoin (0.00001).
I did a transaction with 35 inputs and the fee was about 0.2 Q2C, which seems acceptable to me. Lowering fees will probably require a hard fork, otherwise old nodes will reject the lower fee transactions.
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
So...
tl;dr
If someone is shitting blocks like a machine gun and network diff is not able to catch up, so blocks still come out in 1 sec periods between them
pool is not able to make all its work and stops working
TODO;
re-target diff from block to block in good way.
tl;dr
If someone is shitting blocks like a machine gun and network diff is not able to catch up, so blocks still come out in 1 sec periods between them
pool is not able to make all its work and stops working
TODO;
re-target diff from block to block in good way.
The difficulty or speed of blocks is not related to the 'transaction too large' error you get.
A 'transaction too large' error is when you have too many inputs that make up a transaction, causing a transaction that is too large (in bytes). You can solve this by combining the inputs by sending it to a new address.
See here for more information:
http://bitcoin.stackexchange.com/questions/37172/transaction-too-large-error
https://bitcoin.stackexchange.com/questions/5583/how-can-i-combine-all-the-tiny-amounts-ive-received-to-minimise-transaction-fee
Thanks for trying to help, but this is not exactly "Transaction too large" but "Transaction too large for fee policy" error, which is quite different story.
In other coin pool I was easy able to make single transactions of 20k coins made of many parts of which no single one was bigger than 15 coins, with few screens of tx moving thru the screen.
Here I can't make payout of 40 from 40*1coin, where 1 coin is full block reward :-D
Still, transactions as big as 10 coins go out without problem. For me it is more this coin wallet transaction limit,
what I just confirmed by manually sending 100 coins, with result:
Code:
.
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 50
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 40
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 30
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 20
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 15
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 14
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 13
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 12
c6c3cb34c59d7372bee5c733025c315dd45b563f45640bd1df4c431d682463a6
This is really a joke, you can't send more than 12 coins, made of parts of 1 coin.marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 50
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 40
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 30
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 20
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 15
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 14
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 13
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 12
c6c3cb34c59d7372bee5c733025c315dd45b563f45640bd1df4c431d682463a6
I'm also even more worried about other error E0005, which stops payouts in 1st place, and occurs, as I said, when new blocks start to flood wallet.
Try using a larger transaction fee.
Code:
./qubitcoin-cli help sendtoaddress
sendtoaddress "bitcoinaddress" amount ( "comment" "comment-to" subtractfeefromamount )
Send an amount to a given address. The amount is a real and is rounded to the nearest 0.00000001
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address to send to.
2. "amount" (numeric, required) The amount in btc to send. eg 0.1
3. "comment" (string, optional) A comment used to store what the transaction is for.
This is not part of the transaction, just kept in your wallet.
4. "comment-to" (string, optional) A comment to store the name of the person or organization
to which you're sending the transaction. This is not part of the
transaction, just kept in your wallet.
5. subtractfeefromamount (boolean, optional, default=false) The fee will be deducted from the amount being sent.
The recipient will receive less bitcoins than you enter in the amount field.
Result:
"transactionid" (string) The transaction id.
sendtoaddress "bitcoinaddress" amount ( "comment" "comment-to" subtractfeefromamount )
Send an amount to a given address. The amount is a real and is rounded to the nearest 0.00000001
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address to send to.
2. "amount" (numeric, required) The amount in btc to send. eg 0.1
3. "comment" (string, optional) A comment used to store what the transaction is for.
This is not part of the transaction, just kept in your wallet.
4. "comment-to" (string, optional) A comment to store the name of the person or organization
to which you're sending the transaction. This is not part of the
transaction, just kept in your wallet.
5. subtractfeefromamount (boolean, optional, default=false) The fee will be deducted from the amount being sent.
The recipient will receive less bitcoins than you enter in the amount field.
Result:
"transactionid" (string) The transaction id.
Code:
./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 50 "" "" true
error: {"code":-4,"message":"Transaction too large for fee policy"}
error: {"code":-4,"message":"Transaction too large for fee policy"}
Still not working :-D
Try running the wallet with -maxtxfee=1
Let me know if that works.
We might have to change the fee policy defaults in a next release to reduce the required fee.
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
So...
tl;dr
If someone is shitting blocks like a machine gun and network diff is not able to catch up, so blocks still come out in 1 sec periods between them
pool is not able to make all its work and stops working
TODO;
re-target diff from block to block in good way.
tl;dr
If someone is shitting blocks like a machine gun and network diff is not able to catch up, so blocks still come out in 1 sec periods between them
pool is not able to make all its work and stops working
TODO;
re-target diff from block to block in good way.
The difficulty or speed of blocks is not related to the 'transaction too large' error you get.
A 'transaction too large' error is when you have too many inputs that make up a transaction, causing a transaction that is too large (in bytes). You can solve this by combining the inputs by sending it to a new address.
See here for more information:
http://bitcoin.stackexchange.com/questions/37172/transaction-too-large-error
https://bitcoin.stackexchange.com/questions/5583/how-can-i-combine-all-the-tiny-amounts-ive-received-to-minimise-transaction-fee
Thanks for trying to help, but this is not exactly "Transaction too large" but "Transaction too large for fee policy" error, which is quite different story.
In other coin pool I was easy able to make single transactions of 20k coins made of many parts of which no single one was bigger than 15 coins, with few screens of tx moving thru the screen.
Here I can't make payout of 40 from 40*1coin, where 1 coin is full block reward :-D
Still, transactions as big as 10 coins go out without problem. For me it is more this coin wallet transaction limit,
what I just confirmed by manually sending 100 coins, with result:
Code:
.
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 50
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 40
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 30
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 20
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 15
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 14
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 13
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 12
c6c3cb34c59d7372bee5c733025c315dd45b563f45640bd1df4c431d682463a6
This is really a joke, you can't send more than 12 coins, made of parts of 1 coin.marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 50
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 40
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 30
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 20
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 15
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 14
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 13
error: {"code":-4,"message":"Transaction too large for fee policy"}
marek@vps68798:~/.QubitCoin$ ./qubitcoin-cli sendtoaddress GUBxdJx6iqBDxuWVHhZ2CbzZu5dmzCt5Ve 12
c6c3cb34c59d7372bee5c733025c315dd45b563f45640bd1df4c431d682463a6
I'm also even more worried about other error E0005, which stops payouts in 1st place, and occurs, as I said, when new blocks start to flood wallet.
Try using a larger transaction fee.
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
So...
tl;dr
If someone is shitting blocks like a machine gun and network diff is not able to catch up, so blocks still come out in 1 sec periods between them
pool is not able to make all its work and stops working
TODO;
re-target diff from block to block in good way.
tl;dr
If someone is shitting blocks like a machine gun and network diff is not able to catch up, so blocks still come out in 1 sec periods between them
pool is not able to make all its work and stops working
TODO;
re-target diff from block to block in good way.
The difficulty or speed of blocks is not related to the 'transaction too large' error you get.
A 'transaction too large' error is when you have too many inputs that make up a transaction, causing a transaction that is too large (in bytes). You can solve this by combining the inputs by sending it to a new address.
See here for more information:
http://bitcoin.stackexchange.com/questions/37172/transaction-too-large-error
https://bitcoin.stackexchange.com/questions/5583/how-can-i-combine-all-the-tiny-amounts-ive-received-to-minimise-transaction-fee
Re: Pascal Coin: P2P cryptocurrency without need of historical operations
Is there any documentation on RPC calls ? Is there something like getblocktemplate or getwork implemented ? We'd like to setup a pool but there is not much documentation
See here for the current rpc calls:
https://github.com/PascalCoin/PascalCoin/blob/master/HOWTO_DEVELOP_GPU_MINER_FOR_PASCALCOIN.txt
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
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
}
}
]
}
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
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
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?
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.
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
root@s3c:~/QubitCoin/src# ./qubitcoind
Error:
what is wrong?
Error:
what is wrong?
What is the error message?
usually you run it:
./qubitcoind --daemon
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
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.
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
Re: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.1
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
}
}
]
}
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
}
}
]
}
Re: [ANN][Q2C] QubitCoin new secure hashing (CPU/GPU) (NEW) Update 0.8.4.1
How to mine with this new wallet??
"setgenerate true" or anyone else command doesn't work..
.conf file is same or I must change tham (port or something)?
"setgenerate true" or anyone else command doesn't work..
.conf file is same or I must change tham (port or something)?
If you're using linux, the commands are done with the new qubitcoin-cli utility, for example, old:
qubitcoind --daemon
qubitcoind getinfo
qubitcoind setgenerate true 1
With the new wallet:
qubitcoind --daemon
qubitcoin-cli getinfo
qubitcoin-cli setgenerate true 1
Re: [ANN][Q2C] QubitCoin new secure hashing (CPU/GPU) (NEW) Update 0.8.4.1
willowrose you can explain what happened to my ~500. 000 q2c, which were gone from the wallet when sending you a donate
The change from your transaction goes to one of your other addresses. This is how all Bitcoin based crypto currencies work.
http://bitcoin.stackexchange.com/questions/1629/why-does-bitcoin-send-the-change-to-a-different-address
Your balance should only decrease by the amount you send.
Edit:
Your second transaction was sent from the change you received in the first transaction, so obviously you have control of the change.
Re: [ANN][Q2C] QubitCoin new secure hashing (CPU/GPU) (NEW) Update 0.8.4.1
New wallet release:
https://bitcointalk.org/index.php?topic=576815.msg16353302#msg16353302
0.11.2.1
Fix built-in Qubit miner
https://github.com/willowrose/QubitCoin/releases/tag/v0.11.2.1
https://github.com/willowrose/QubitCoin/releases/download/v0.11.2.1/q2c-0.11.2.1-win32.zip
https://github.com/willowrose/QubitCoin/releases/download/v0.11.2.1/q2c-0.11.2.1-win64.zip
https://bitcointalk.org/index.php?topic=576815.msg16353302#msg16353302
0.11.2.1
Fix built-in Qubit miner
https://github.com/willowrose/QubitCoin/releases/tag/v0.11.2.1
https://github.com/willowrose/QubitCoin/releases/download/v0.11.2.1/q2c-0.11.2.1-win32.zip
https://github.com/willowrose/QubitCoin/releases/download/v0.11.2.1/q2c-0.11.2.1-win64.zip
Re: [ANN][Q2C] QubitCoin new secure hashing (CPU/GPU) (NEW) Update 0.8.4.1
There is a bug in latest wallet for windows. I couldn't mining with it, got this error when set gen=1 in config or setgenerate true in wallet
https://ipfs.pics/ipfs/QmR46z5Q2ijJsrQ4iKg4VxyA3tQSyDXhgJVKNcSjMNJjUg
https://ipfs.pics/ipfs/QmR46z5Q2ijJsrQ4iKg4VxyA3tQSyDXhgJVKNcSjMNJjUg
Thanks for reporting this. I'm working on a fix.