Topic: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.2 - page 21. (Read 47760 times)
i am waiting it on 1 satoshi
some fool has sold for 3-5 Satoshi and now probably stand in sell order 78 
where do you watch it?
0.00000004 532000.00000000 0.02128000 0.02128000
0.00000003 3356265.75060000 0.10068797 0.12196797
0.00000002 2682154.50000000 0.05364309 0.17561106
0.00000001 2342755.00000000 0.02342755 0.19903861
0.00000004 532000.00000000 0.02128000 0.02128000
0.00000003 3356265.75060000 0.10068797 0.12196797
0.00000002 2682154.50000000 0.05364309 0.17561106
0.00000001 2342755.00000000 0.02342755 0.19903861
Now we have bootstrap.dat creation bot, it will be daily update
Code:
https://github.com/jemekite/q2c-bootstrap
some desperate gave q2c for free
2016-10-20 11:28 SELL 0.00000003 305547.91606667 0.00916644 0.00916644
2016-10-20 11:28 SELL 0.00000004 50000.00000000 0.00200000 0.00200000
2016-10-20 11:28 SELL 0.00000004 37425.00000000 0.00149700 0.00149700
2016-10-20 11:28 SELL 0.00000005 367027.08393333 0.01835135 0.01835135
2016-10-20 11:21 SELL 0.00000005 1231972.91606667 0.06159865 0.06159865
2016-10-20 11:21 SELL 0.00000005 1004695.04318333 0.05023475 0.05023475
2016-10-20 10:57 SELL 0.00000005 97554.95681667 0.00487775 0.00487775
2016-10-20 10:57 SELL 0.00000006 33333.33333333 0.00200000 0.00200000
2016-10-20 10:57 SELL 0.00000020 25000.00000000 0.00500000 0.00500000
2016-10-20 10:57 SELL 0.00000035 12500.00000000 0.00437500 0.00437500
2016-10-20 10:57 SELL 0.00000036 16850.70985000 0.00606626 0.00606626
2016-10-20 10:57 SELL 0.00000037 4761.00000000 0.00176157 0.00176157
2016-10-20 11:28 SELL 0.00000003 305547.91606667 0.00916644 0.00916644
2016-10-20 11:28 SELL 0.00000004 50000.00000000 0.00200000 0.00200000
2016-10-20 11:28 SELL 0.00000004 37425.00000000 0.00149700 0.00149700
2016-10-20 11:28 SELL 0.00000005 367027.08393333 0.01835135 0.01835135
2016-10-20 11:21 SELL 0.00000005 1231972.91606667 0.06159865 0.06159865
2016-10-20 11:21 SELL 0.00000005 1004695.04318333 0.05023475 0.05023475
2016-10-20 10:57 SELL 0.00000005 97554.95681667 0.00487775 0.00487775
2016-10-20 10:57 SELL 0.00000006 33333.33333333 0.00200000 0.00200000
2016-10-20 10:57 SELL 0.00000020 25000.00000000 0.00500000 0.00500000
2016-10-20 10:57 SELL 0.00000035 12500.00000000 0.00437500 0.00437500
2016-10-20 10:57 SELL 0.00000036 16850.70985000 0.00606626 0.00606626
2016-10-20 10:57 SELL 0.00000037 4761.00000000 0.00176157 0.00176157
Here is another one, created using linearize.py script, up to block 2024168.
sha256sum:
Code:
https://transfer.sh/9xnZP/q2c-bootstrap-20161020.zip
sha256sum:
Code:
820aa28f8521781ae895fec3a095811b8dbd87b66cddcd0e39d78aa4875ba658 q2c-bootstrap-20161020.zip
any blockchain bootstrap for Q2c? Tired to sync, 2 years 37 weeks 
Here we go, just made Q2C blockchain bootstrap today, enjoy ( #2023321 dated 20.10.2016, 400MB ),
link: https://mega.nz/#!jF0UHTDS!SQLOwEN-GssISEqGgFBjSBcKfTZULImntHGwWavINR8
Q2C tips welcome: GbdyWQcFvgzcceGYXTNhFd2zhxPFQ5T1Vu
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.
How do I re-index?, I guess it's quicker than redownloading the blockchain
any blockchain bootstrap for Q2c? Tired to sync, 2 years 37 weeks
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.
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.
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
Good news!
What about diff being so big that no new block shown in about 15-20 minutes? :-)
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.
Yup, more than hard fork Q2C need some constant miners base :-)
and also good price!
Good news!
What about diff being so big that no new block shown in about 15-20 minutes? :-)
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.
Good news!
What about diff being so big that no new block shown in about 15-20 minutes? :-)
What about diff being so big that no new block shown in about 15-20 minutes? :-)
Code:
"blocks" : 2021151,
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.
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.
Nice!
With fee=1 tx with 50coins goes without a problem, thanks!
Diff is so high I can't even get a block in 10 min on Fury X today?
willowrose -maxtxfee= work fine thx!
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.
Jump to: