|
Hi,
I see the mining software does not generate valid shares for Dashcoin on Minergate's pool since the update took place today (block 91452). I tried it and it does not generate bad shares, but also do not generate valid shares also and my balance is becoming negative.
I also tried it on alternative pool (my test pool) through the "Other pools" section and it generates valid shares.
|
|
|
|
|
It seems like extremepool still haven't updated. Move your hashrate until they update or you are just waisting hashrate.
|
|
|
|
poloniex Cannot be deposited in the show Error: Invalid payment ID usage. Please, use -p <payment_id>. See help for detai ls. Poloniex example is wrong. Here is the correct usage payment_id: transfer 0 ADDRESS AMOUNT -p payment_id |
|
|
|
What is the fix / improvement? 2014-11-06 16:38:11 (4 hours ago) 00b925a92587a7f30b00c6021a4d6de3fdaa258946d79677ffb0dd0d1930e175 965,444.80742286 30.00000000 1 19108 bytes
2014-11-06 16:38:11 (4 hours ago) 75ecd29619d6cbc08e5c2f595ea94b597fb522755a11e6a18d456fdc112d48cc 12,029,453.89000000 0.01000000 2 18644 bytes
2014-11-06 16:38:11 (4 hours ago) cb7874b18e41073e69dce72f8f239446f5460f43297734da6957060d0682377f 636,207.96000000 15.00000000 4 14061 bytes
2014-11-06 16:38:11 (4 hours ago) c7c87e7b1f7239fbfa917053a359ecb6673542d9bb032f770b11a2d320c5d648 305,583.09000000 10.00000000 4 16262 bytes Those big sized transactions will be included in the blockchain much easier. The update will take effect in 4 days, which is plenty of time for all pools to update. We need 90% consensus (mined blocks) on the update and this is the reason to be mandatory. |
|
|
|
|
There is a mandatory update for Dashcoin released today. Please update as soon as possible.
|
|
|
|
Yes. Their last block. {
"id": "test",
"jsonrpc": "2.0",
"result": {
"block_header": {
"depth": 7,
"difficulty": 24488107,
"hash": "eba4534399aaba4418efaf91fe25f4d09aa58e4f6aed4e8c99008d6a8e42d152",
"height": 83534,
"major_version": 1,
"minor_version": 1,
"nonce": 4097,
"orphan_status": false,
"prev_hash": "41714863e91a12948f56f6141bffd132d561c3de5a4e0e598e0921f5d85f2ca6",
"reward": 51248761271202,
"timestamp": 1414594682
},
"status": "OK"
}
} I am not mining there if I was at your place. |
|
|
|
I have setup and ran this script @ Extremepool. Thanks SLB! haven't received my missing payments yet. how many rejected payments were reprocessed? looks like i've started receiving my missing funds from extremepool. thanks for getting around to this and thanks again to slb for the script. on a side note will this script work for other CN coins mined on similar pools? It works for every CN coin. Both fancoder/cryptonote-universal-pool and zone117x/node-cryptonote-pool are supported |
|
|
|
Network fork / glitch.  http://dsh.extremepool.org/ last block 81770 2 hours ago. https://minergate.com/pool-stats/dsh last block 81786 10 minutes ago. WTF. 2014-Oct-27 00:16:17.098774 [P2P9][123.164.206.70:5065 INC]Sync data returned unknown top block: 81762 -> 81787 [25 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Oct-27 00:16:23.282495 [P2P1]Block <d2fbfe96ef2e63bc3a7e408010aad520fd1953344d9068fe050039292246952a> has at least one unknown transaction: <5ebea1ccf6f9f84f3e9d1eafb7f0b355b665e6e83f95972500d01bffaeafe3ab>
2014-Oct-27 00:16:26.448655 [P2P8][178.63.62.93:49305 INC]Sync data returned unknown top block: 81762 -> 81787 [25 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Oct-27 00:16:27.635627 [P2P1]Block <d2fbfe96ef2e63bc3a7e408010aad520fd1953344d9068fe050039292246952a> has at least one unknown transaction: <5ebea1ccf6f9f84f3e9d1eafb7f0b355b665e6e83f95972500d01bffaeafe3ab>
2014-Oct-27 00:16:32.902702 [P2P1][123.164.206.70:15370 INC]Sync data returned unknown top block: 81762 -> 81787 [25 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Oct-27 00:16:38.827922 [P2P3][68.199.229.205:54163 INC]Sync data returned unknown top block: 81762 -> 81787 [25 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Oct-27 00:16:39.211630 [P2P8]Block <d2fbfe96ef2e63bc3a7e408010aad520fd1953344d9068fe050039292246952a> has at least one unknown transaction: <5ebea1ccf6f9f84f3e9d1eafb7f0b355b665e6e83f95972500d01bffaeafe3ab>
2014-Oct-27 00:16:39.806772 [P2P8]Block <d2fbfe96ef2e63bc3a7e408010aad520fd1953344d9068fe050039292246952a> has at least one unknown transaction: <5ebea1ccf6f9f84f3e9d1eafb7f0b355b665e6e83f95972500d01bffaeafe3ab>
over and over. network attack? edit: http://dsh.democats.org/# just found block 81787 but no other pool is recognizing it Both extremepool and democats were under attack. Democats is up now. We were under 51 attack at the same time. Currently the trusted working pools are: https://www2.coinmine.pl/dsh/http://dsh.extremepool.orghttp://dsh.shscrypto.nethttp://dsh.democats.orgI expect http://dsh.extremepool.org to resume work shortly. Extremepool are still in process of resending the refused transfers, they have huge count of transfers, and the current version of the script I provided is not very fast. If you have some DSH stuck there don't worry. I am starting to build an open source blockchain explorer compatible with the open source pools. I think there is big need for it and it will spread the Dashcoin idea much far. Edit: http://dsh.extremepool.org resumed work |
|
|
|
Hi folks! First of all, I use the latest version of dashcoind from 16 Sep on my pool. Here is the --version output: > dashcoind --version
2014-Oct-20 10:18:48.631403 Starting...
2014-Oct-20 10:18:48.633060 dashcoin v1.0.2.358()
dashcoin v1.0.2.358()
Secondly the statement that MinerGate has moved to modified daemon code on 10/06/2014 is totally incorrect. CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE represents a base median value of block total transactions size and can be shifted forward. As you can see the current median of 63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110 ' malicious' block equals 23,142 bytes, which means it can contain up to 23 Kb of transactions. Real block size depends on the daemon's tx pool state - the mining pool have nothing to include into the block if it is empty. So, since this isn't correct, the remaining statements are incorrect also. Lastly for whose benefit? Please answer what my pool will gain from this potential modification? Instead of blaming the honest mining pool you should better ask the network maintainers to check the Dashcoin code. print_block 79399 block_id: <2019486df631cfc5e822c38069a57ffc27526820443933540635e4467d8fa5ac> { "majorVersion": 1, "minorVersion": 0, In which cases this version of a block is generated? All minergate's blocks have and majorVersion 1 and minorVersion 0. |
|
|
|
THe updated site and API!!  nice work. |
|
|
|
I think i messed up when trying to send coins to myself...
transfer 0 address 100000
Money successfully sent, transaction <txnumber>
They didnt show up in my wallet afterwords...any ideas?
See FAQ: http://dashcoin.net/faq/"My transaction says sent, but it never showed up." okay...moving my miners off mg.
but can you tell me how sending large amounts from mg seems to work almost all the time and i struggle with amounts 10x smaller from simplewallet given they reduced this parameter? i've was able to send 3 separate 24M DSH txns from there that arrived within a very short period of time when my 2M DSH txns from my simple wallet would take hours if not a day to get there
Long story short: * Your daemon is programmed to sends transactions up to 20,000 bytes * Minergate is programmed to accept and send transactions up to 10,000 bytes * Minergate controls big chunk of the network Result: Transactions in range 10,000 - 20,000 have hard time to pass If an attacker flood the network with transactions just over 10,000 bytes (like 10,536 bytes or 11,057 bytes), it makes practically impossible for real transactions over 10,000 bytes to pass. The transaction size depends on the number of inputs, outputs (payees), and mixin. You can easily have a transactions for amount 10,000DSH with size 12,000 bytes and in the same time you can easily have a transaction for amount 5,000,000DSH with size 3,000bytes. |
|
|
|
I have some finding about the recent transaction problem. I knew what was the problem when I fixed my test pool - transactions with size bigger than 10,000 bytes were hardly accepted in the blockchain. I took my investigation further and here are my finding:
So what about transactions that never made it from pools like extremepool or even democats (or any of the open source pools)? Will those failed TXs ever be resent to miners that never received them or is it a manual process? I know extremepool won't be doing any manual payouts like that for me, I already asked. Between extremepool and democats I never received >50M DSH that should have made it to me. I expect to complete the script for sending the payments later today or tomorrow. I already automated the process of getting the failed transactions and I am halfway through sending. |
|
|
|
once dash have ease of sending transaction, i'll send some donation..
I have some finding about the recent transaction problem. I knew what was the problem when I fixed my test pool - transactions with size bigger than 10,000 bytes were hardly accepted in the blockchain. I took my investigation further and here are my finding: 1. Minergate uses old or modified code:This is the code from the current version on Dashcoin: #define CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE 20000 Here is what they probably use: #define CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE 10000 2. Minergate started to use this code on 2014/10/06 10:28:17I looked at the blockchain for odd blocks and they started to appear here: http://chainradar.com/dsh/blocks/2241/3067225 14-10-06 10:28:17 576 1 63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110 Before this block all blocks have size >17,000 bytes, which means all pools have honest code before this point of time (CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE with value 20000) http://chainradar.com/dsh/block/63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110Proof that the block is Minergate's: https://minergate.com/pool-stats/dsh/23491Search for 63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110 3. Minergate used correct code before 2014/10/06 10:28:17Here is a Minergate's block just 2 blocks below the first strange block I showed above. 67225 14-10-06 10:28:17 576 1 63d91c6d5f7f9eab1cc2ad3f3be0435fba2427694ba4579e1cdb6077e8e47110
67224 14-10-06 10:28:43 27286 3 87e8bd5e525649322ed3e5a7d582629917353b06680ba4c035736c03d6834a40
67223 14-10-06 10:17:47 23295 4 4e2dad2aa98dab526f9ea269c0d6dc0388ebb20af159e95c71df3f0bcd8bfdbe Proof that the block is Minergate's: https://minergate.com/pool-stats/dsh/23491Search for 4e2dad2aa98dab526f9ea269c0d6dc0388ebb20af159e95c71df3f0bcd8bfdbe How this is affecting the network:1. Transactions with >10000 bytes will break with frequency, related to how much of the hashrate Minergate controls. This produce a snowball effect - the more failed transaction - more people goes to Minergate, because the other pools cannot send transactions. 2. The higher number of transaction failed leads to the constant need of reset and cache delete. How to act:DO NOT MINE AT MINERGATETo improve the effective transaction median and reduce the rejected transactions, we must put Minergate's hashrate percent to minimum as possible until they fix their daemon. Spread the hashrate between poolsLets don't make the same mistake again and give so much power to a single pool. Make sure you are running dashcoind with version 1.0.2dashcoind --version The fact that Minergate had a version with CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE 20000 before their version with value 10000 makes me almost certain this is not a simple mistake. |
|
|
|
I haven't receive the DSH I mined from extrempool 3 days ago,what's wrong? Practically no transaction with fee less than 10 DSH passes currently. It seems like this is causing the problems with the pools. Currently the pools with correct fee are: http://dsh.extremepool.org/http://dashcoin.xminingpool.com/https://www2.coinmine.pl/dsh/http://dsh.democats.org/https://minergate.comI strongly recommend to use the first 3 instead of Minergate and spread the hashrate. We must be assured no pool have more than 40% of the network hashrate if we want to become more valuable network.The payments stuck in Democats will be processed as soon as possible. Still have no news from Extremepool but I am sure they will correct the problem shortly. Edit: Extremepool works properly now. |
|
|
|
Dashcoin's source generator is now open source: https://github.com/dashcoin/dashcoin-generator/The Dashcoin generator gives you the ability to generate the latest Dashcoin's source code with 1 command. It practically eliminates a potential 'missing developer' problem. Even if for some reason the main repository is not updated, the community does not loose the ability to get the latest source code. For more info read the README file in the repository.
|
|
|
|
i'm trying to use the -p <payment id> and -f <fee> options but these don't appear to be supported in the simplewallet client. can someone paste the exact transfer statement. i tried "transfer 0 <address> <amount> -p <payment id> -f <fee>" but it didn't like it. Only this works for me "transfer 0 <address> <amount> <payment id>" Do you have the latest version? The latest version is v1.0.2.358 You can check your wallet version by running " dashcoind --version " You can download the latest version from OP or from http://dashcoin.net . If you still have problems PM me |
|
|
|
|
Show Posts
