Topic: [ANN][Q2C] QubitCoin secure hashing (NEW) Update 0.11.2.2 - page 22. (Read 47765 times)
yeah right, but add to 5 price 00
when will price go down so i can purchase some, wgd want to sell now q2c for 5 satoshi or you already sell all
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
I also supported network on Polish node, relax guys.
This is not a bakery, everything slowly will explain why these nerves
RELAX GUYS !!
This is not a bakery, everything slowly will explain why these nerves
RELAX GUYS !!
You were certainly not the only one who was doing that.
I really don't understand you. You were doing everything to keep the block chain running and now when situation is getting better you are posting such stupid things.
If you really mean well for QubitCoin, you will stop spamming and start helping.
Will not argue with you anymore...
I really don't understand you. You were doing everything to keep the block chain running and now when situation is getting better you are posting such stupid things.
If you really mean well for QubitCoin, you will stop spamming and start helping.
Will not argue with you anymore...
Then stop spamming and start helping.
I am helping about 2,5 years hosting a node and spining the blockchain when all of you disapeared.
Then stop spamming and start helping.
@ zex24 not afraid of negative comments when they have a direct answer for trust in the group.
I still have all of my wallets in double copies.
You probably had a lot of Q2C which you lost/deleted and now, out of anger, you are trying to find every little bug/thing which will put down the coin.
I still have all of my wallets in double copies.
Block explorer fix it http://qubitxplorer.cf/ and working fine.
Edit: anyone with email from block explorer?
Edit: anyone with email from block explorer?
kOstas,
there is no need to post these kind of things. It is obvious that dev overlooked the name of the coin. It's good that you noticed it but send PM to me or willowrose directly and it will be corrected.
I already sent you PM regarding your posting in this thread but you still continue to undermine everything we are trying to do here. You probably had a lot of Q2C which you lost/deleted and now, out of anger, you are trying to find every little bug/thing which will put down the coin.
there is no need to post these kind of things. It is obvious that dev overlooked the name of the coin. It's good that you noticed it but send PM to me or willowrose directly and it will be corrected.
I already sent you PM regarding your posting in this thread but you still continue to undermine everything we are trying to do here. You probably had a lot of Q2C which you lost/deleted and now, out of anger, you are trying to find every little bug/thing which will put down the coin.
This hapens when i try to engrypt my new wallet i will lose my zetacoins.
The wallet dev probably forgot to replace it with QubitCoins. This shows nobody is perfect in crypto world, instead you should be grateful Qubitcoin is still around.
This hapens when i try to engrypt my new wallet i will lose my zetacoins.
Who in charge for qubitxplorer?
I have create temporary iquidus explorer with better seo for tittle and added market, unfortunately I can't host it on my server.
here is the demo:
source code:
I have create temporary iquidus explorer with better seo for tittle and added market, unfortunately I can't host it on my server.
here is the demo:
Code:
https://q2c.altexplorer.xyz/
source code:
Code:
https://github.com/jemekite/q2c-explorer
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.
W00t... 
Is this all yours networkhashps?Code:
"networkhashps" : 549147501
Have you resolve your rpc problem for p2pool?
P2Pool Logs:
Code:
dev@dev-mint ~/src/p2pool-q2c $ ./run_p2pool.py --net qubitcoin --give-author 0 -f 0
2016-09-29 09:13:29.039084 p2pool (version 16.0-4-gde1be30-dirty)
2016-09-29 09:13:29.039154
2016-09-29 09:13:29.039214 Testing bitcoind RPC connection to 'http://127.0.0.1:7799/' with username 'qubitrpc'...
2016-09-29 09:13:29.042899 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:30.049286 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:31.054248 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:32.060554 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:29.039084 p2pool (version 16.0-4-gde1be30-dirty)
2016-09-29 09:13:29.039154
2016-09-29 09:13:29.039214 Testing bitcoind RPC connection to 'http://127.0.0.1:7799/' with username 'qubitrpc'...
2016-09-29 09:13:29.042899 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:30.049286 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:31.054248 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:32.060554 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
No, I'm not mining right now.
I still can't resolve P2Pool RPC problem, can you help? repo is here:
Code:
https://github.com/jemekite/p2pool-qubitcoin
It's work great with v0.8.4.1
I have the same problem with rpc i can't help i am not a programmer.
W00t...
Is this all yours networkhashps?Code:
"networkhashps" : 549147501
Have you resolve your rpc problem for p2pool?
P2Pool Logs:
Code:
dev@dev-mint ~/src/p2pool-q2c $ ./run_p2pool.py --net qubitcoin --give-author 0 -f 0
2016-09-29 09:13:29.039084 p2pool (version 16.0-4-gde1be30-dirty)
2016-09-29 09:13:29.039154
2016-09-29 09:13:29.039214 Testing bitcoind RPC connection to 'http://127.0.0.1:7799/' with username 'qubitrpc'...
2016-09-29 09:13:29.042899 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:30.049286 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:31.054248 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:32.060554 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
No, I'm not mining right now.
I still can't resolve P2Pool RPC problem, can you help? repo is here:
Code:
https://github.com/jemekite/p2pool-qubitcoin
It's work great with v0.8.4.1
W00t...
Is this all yours networkhashps?Code:
"networkhashps" : 549147501
Have you resolve your rpc problem for p2pool?
P2Pool Logs:
Code:
dev@dev-mint ~/src/p2pool-q2c $ ./run_p2pool.py --net qubitcoin --give-author 0 -f 0
2016-09-29 09:13:29.039084 p2pool (version 16.0-4-gde1be30-dirty)
2016-09-29 09:13:29.039154
2016-09-29 09:13:29.039214 Testing bitcoind RPC connection to 'http://127.0.0.1:7799/' with username 'qubitrpc'...
2016-09-29 09:13:29.042899 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:30.049286 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:31.054248 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:32.060554 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
W00t...
Code:
"networkhashps" : 549147501
...
Drama here is, that in crontab going 1 time to minute, I'm limited to pay 12 coins
workers can easy spam with block finding shares getting much more than I'm able to send them LOL :-D
Drama here is, that in crontab going 1 time to minute, I'm limited to pay 12 coins
workers can easy spam with block finding shares getting much more than I'm able to send them LOL :-D
Jump to: