@Invis
The 10-15 seconds you mention is spooky near by the delay after which blocks arrive at my local node daemon.
I've tried to modify my pool to compare mined blocks against official explorer list. That worked stable but is also incorrect.
Block on height 84404 has same hash in my pool and in explorer list. One can assume, origin of block is my pool. Due to my changed this block get unlocked and *not* marked as orphaned. But looking in my pool wallet, I can see, that the reward for this block was cancelled. Don't know why. But I'm getting more crazy. I'm spending money on blocks that are orphaned really, even if official block list claims not.
Same with block 84430 and 84431, where both are contained in official list but only 84430 is accepted by network. To summarize: I think one can trust on accepted blocks by network and do NOT trust block list on official coin website.
Topic: Leviar.io - Official thread - page 44. (Read 160623 times)
I sent a pack of coins to the stock exchange, less than half came.
The second part is hanging somewhere. What now with this?
Hah! See block list at Dark's pool. Even if official explorer list claims, that my block hash at 84230 is correct, Dark's pool has unlock his invalid block!
I saw same at your pool and our test pools. Blockchain says that block is "ok", but after 10-15 seconds its got orphaned by network. This started after big hashrate increase, from 90-100kh/s to 600+kh/s.
Hum, really sad.
I've tried to debug block at height 84230:
1) My pool shows hash 14cc2ff
2) Explorer list shows hash 14cc2ff
3) Dark's pool shows hash 810601
4) And - that's creepy - my local coin daemon shows hash 810601 also
My coin daemon accepted block from Dark's pool. From this point of view, it's understable why the block get's marked as orphaned. And *this* is really a bug in blockchain.
Most strange thing is, that blockchain is always one block ahead. So block height 84230 in my local blockchain is 84229 in official explorer list.
Hah! See block list at Dark's pool. Even if official explorer list claims, that my block hash at 84230 is correct, Dark's pool has unlock his invalid block!
I've tried to debug block at height 84230:
1) My pool shows hash 14cc2ff
2) Explorer list shows hash 14cc2ff
3) Dark's pool shows hash 810601
4) And - that's creepy - my local coin daemon shows hash 810601 also
My coin daemon accepted block from Dark's pool. From this point of view, it's understable why the block get's marked as orphaned. And *this* is really a bug in blockchain.
Code:
print_block 84229
block_id: b4e06219188e0527ab56add3bb03f6dc20cfdee0b4e15384f74a8b6c998923a7
{"major_version":1,"miner_tx":{"extra":"01163759b3f005d8a3478db1d87658a240bcfbcaf2ea3c36cdc9564786f88791dc02080000000011788473","unlock_time":84288,"version":1,"vin":[{"type":"ff","value":{"height":84228}}],"vout":[{"amount":306601,"target":{"data":{"key":"b6b7bef8cd2d3870fb49a9406cdf7d43054c0e251b27ea4c917748cbbc1c9d4e"},"type":"02"}},{"amount":3000000,"target":{"data":{"key":"e7a8419e72acf5fe44379369411d136dea82eacc927bf5b5bd2f131c14d19e17"},"type":"02"}},{"amount":80000000,"target":{"data":{"key":"2b0faa547391b04860883b9e6e27ff6aa653ac86b25d6d130827a1cb9f516b1c"},"type":"02"}},{"amount":800000000,"target":{"data":{"key":"d0985af6793a64d69bde027ac7727793200bace868abe831a6f1d8e3c429cf0b"},"type":"02"}}]},"minor_version":0,"nonce":"0a0921b2","prev_id":"5a60691574d6e5f1f3e753b848d9452cb84889c4bade6f4f37ddcc3236a49f19","timestamp":1505461640,"tx_hashes":[]}
print_block 84230
block_id: 9e865479889a6bf69a16b6917604f894979a3aa2378a03e488e57f6a93f19f1d
{"major_version":1,"miner_tx":{"extra":"01296f27f29b3e6a88f20eb355f984b9925e1b547119f635b16e17b541390319c502080000000037e4d162","unlock_time":84289,"version":1,"vin":[{"type":"ff","value":{"height":84229}}],"vout":[{"amount":306391,"target":{"data":{"key":"83eeb99766b79287932b424dd4711cc1b7319f90a0b453e3aa526ee2ce982d37"},"type":"02"}},{"amount":3000000,"target":{"data":{"key":"ce1b475ac4ccece87515f4ccb3c9975e68cba9a1d52a17626c2d946603108a14"},"type":"02"}},{"amount":80000000,"target":{"data":{"key":"b2127a8410662f8d69ac16392f5af463d8a9535876bdb3da3a82f859c3272908"},"type":"02"}},{"amount":800000000,"target":{"data":{"key":"1d8b73034a694d10d6cc65bd62765836505f5a12c83955bda1d65d042879521d"},"type":"02"}}]},"minor_version":0,"nonce":"b5100000","prev_id":"b4e06219188e0527ab56add3bb03f6dc20cfdee0b4e15384f74a8b6c998923a7","timestamp":1505461725,"tx_hashes":[]}
print_block 84231
block_id: 8106016049118d9d4659d40101f3fb850cf1ee7edb7e29dc98c8a8cccbab374d
{"major_version":1,"miner_tx":{"extra":"01c376e9a4801976e6383a26e753a7390b4faecc65ee82751801297adb43dc380e0208000000001fb7e4db","unlock_time":84290,"version":1,"vin":[{"type":"ff","value":{"height":84230}}],"vout":[{"amount":306180,"target":{"data":{"key":"3e0f24dd55d1ee56954cb15870f49a517f0e8837b6108ff36fce60b225e84745"},"type":"02"}},{"amount":3000000,"target":{"data":{"key":"60748d4f398aa59b5df5ca813811a754ea9b71bcbb8f91a9bbc2a88e8a8f99c4"},"type":"02"}},{"amount":80000000,"target":{"data":{"key":"89bf02af8c9183ec4fa99d4d5d729527d46393a7ba8337d6096dd81f799e7c4b"},"type":"02"}},{"amount":800000000,"target":{"data":{"key":"a6512c0a438f88f71cfbffd358557c07f23071bc5c6ff0b7dfac0c1219305efb"},"type":"02"}}]},"minor_version":0,"nonce":"53360000","prev_id":"9e865479889a6bf69a16b6917604f894979a3aa2378a03e488e57f6a93f19f1d","timestamp":1505461770,"tx_hashes":[]}
Most strange thing is, that blockchain is always one block ahead. So block height 84230 in my local blockchain is 84229 in official explorer list.
Hah! See block list at Dark's pool. Even if official explorer list claims, that my block hash at 84230 is correct, Dark's pool has unlock his invalid block!
Really, I've overlooked the blocks. Thank, I'll dig into it and give feedback.
I know that Dark's pool is not yours, but you've written you are in contact with him. Don't you think net hashrate is going down because many miners are bad-tempered?
And yes, most orphaned blocks are blockchain related, but I think it's a combination of short block time and long sync time.
I don't think a coin will die because maintainer is not reachable for 3 days. Keep cool and wait some more days.
Last contact with Mark - 8 days ago. I know that Dark's pool is not yours, but you've written you are in contact with him. Don't you think net hashrate is going down because many miners are bad-tempered?
And yes, most orphaned blocks are blockchain related, but I think it's a combination of short block time and long sync time.
I don't think a coin will die because maintainer is not reachable for 3 days. Keep cool and wait some more days.
Really, I've overlooked the blocks. Thank, I'll dig into it and give feedback.
I know that Dark's pool is not yours, but you've written you are in contact with him. Don't you think net hashrate is going down because many miners are bad-tempered?
And yes, most orphaned blocks are blockchain related, but I think it's a combination of short block time and long sync time.
I don't think a coin will die because maintainer is not reachable for 3 days. Keep cool and wait some more days.
I know that Dark's pool is not yours, but you've written you are in contact with him. Don't you think net hashrate is going down because many miners are bad-tempered?
And yes, most orphaned blocks are blockchain related, but I think it's a combination of short block time and long sync time.
I don't think a coin will die because maintainer is not reachable for 3 days. Keep cool and wait some more days.
@minerpool.de
Blocks:
84123, 84105, 84100, 84099, 84092, 84091
and more more more
All this blocks are valid, but counted as orphaned by your pool.
Dark pool is not my pool.
Me and my friends make 3 private pools to make some tests, each with 10-15kh/s.
But netdiff still going down, and all pools have same issue with alot of orphaned by blockchain blocks. This is not pool related bug, this is blockchain related.
And really bad things - Mark readed all messages about this situation in telegramm, but didnt answer to anybody. And no fixes for 3 days. Seems coin dying
Blocks:
84123, 84105, 84100, 84099, 84092, 84091
and more more more
All this blocks are valid, but counted as orphaned by your pool.
Dark pool is not my pool.
Me and my friends make 3 private pools to make some tests, each with 10-15kh/s.
But netdiff still going down, and all pools have same issue with alot of orphaned by blockchain blocks. This is not pool related bug, this is blockchain related.
And really bad things - Mark readed all messages about this situation in telegramm, but didnt answer to anybody. And no fixes for 3 days. Seems coin dying
Also, I don't think that more hashpower means more orphaned blocks. Since yesterday the hash power doesn't has increased. As you've already said, hashpower of network is decreasing instead. So your theory might be wrong.
But as you've noted, Dark's pool has more orphaned blocks since yesterday. And (sorry for repeating), I think, that's because Dark's pool owned nearly all hash power in past. But now, that some of its hashpower has migrated to other pools, there is a really hard competition between pools to find next block. Because block time is so short and blockchain sync seems to be too slow, there arise different blocks on same height.
I wonder why it takes 10-20 seconds until a block, that was found by Dark's pool and accepted by blockchain as new top block will appear in my local coin daemon. So my pool often works 10-20 seconds for nothing until it get's notified about new top block. And when block time is 60 seconds, it's plausible that there appear many orphaned blocks.
But as you've noted, Dark's pool has more orphaned blocks since yesterday. And (sorry for repeating), I think, that's because Dark's pool owned nearly all hash power in past. But now, that some of its hashpower has migrated to other pools, there is a really hard competition between pools to find next block. Because block time is so short and blockchain sync seems to be too slow, there arise different blocks on same height.
I wonder why it takes 10-20 seconds until a block, that was found by Dark's pool and accepted by blockchain as new top block will appear in my local coin daemon. So my pool often works 10-20 seconds for nothing until it get's notified about new top block. And when block time is 60 seconds, it's plausible that there appear many orphaned blocks.
@Invis
So much investigation is needed ^^
1) I cannot find blocks in my pool (when comparing block height and hash with official list in explorer) that are valid but marked as orphaned. Please mention some blocks which are marked as orphaned but have to be unlocked.
2) I cannot explain why blocks in explorer are doubled!? Sure, some of my valid blocks appear multiple times in this list, but there are much more blocks in explorer list, that were not found by my pool. So this should be nothing related to my pool setup.
3) The seems to be a big misunderstanding. I wonder, why your pool displays a much more hash rate than the network totally has. I think this is the reason why you pay only 30-40% of really earned coins. The hash rate that my pool runs at is plausible. So, are you really sure, that there is not a wrong configuration in Dark's pool?
4) Thanks for hint about missing explorer links.
I want to mention, that it's not my intention to bring other pools down. But as I'm operating pools for KRB, AEON and some other coins, which run fine, I'm interested in solving the issues, that all pool operators and miners can participate at this coin.
So much investigation is needed ^^
1) I cannot find blocks in my pool (when comparing block height and hash with official list in explorer) that are valid but marked as orphaned. Please mention some blocks which are marked as orphaned but have to be unlocked.
2) I cannot explain why blocks in explorer are doubled!? Sure, some of my valid blocks appear multiple times in this list, but there are much more blocks in explorer list, that were not found by my pool. So this should be nothing related to my pool setup.
3) The seems to be a big misunderstanding. I wonder, why your pool displays a much more hash rate than the network totally has. I think this is the reason why you pay only 30-40% of really earned coins. The hash rate that my pool runs at is plausible. So, are you really sure, that there is not a wrong configuration in Dark's pool?
4) Thanks for hint about missing explorer links.
I want to mention, that it's not my intention to bring other pools down. But as I'm operating pools for KRB, AEON and some other coins, which run fine, I'm interested in solving the issues, that all pool operators and miners can participate at this coin.
@minepool.de, your pool have problem with block unlocking, it count some valid blocks as orphaned, like xlc.globalpool.cc. Look at blockchain explorer, it doubles alot of blocks in list. Seems something with masternodes
As I've written, orphaned blocks are related to the fact, that there is another big pool with more hashpower which finds a block earlier mostly. So my guess is, when I gain more hash power, the orphaned blocks should decrease. But that is a fact that belongs to blockchain itself, really.
More hashpower = more orphaned blocks.Here is limit for block luck, that makes block go orphaned.
Seems that some bug in blockchain, like with sumocoin.
Also - fix links to blockchain explorer.
I wish to investigate in pool's situation now.
Now network hashrate is about 108kh, Dark's pool hashrate 150kh. Network hasrate decreases every minute. About 50-60% blocks orphaned. Pool get payments for 60kh/s only, and spread all coins for all miners, who makes 150kh/s. So each miner gets only 30-40% of desired coins. This situation affected all XLC pools at the moment. We already contacted Mark to fix this problem. Seems this is blockchain bug, because all blocks shares/diff higher than 60% count as orphaned and didnt paid by network. Any hashrate burst only decreases network speed. That situation started then XLC get listed by Cryptopia, because alot of new miners connected, and pool hashrate sometimes raised up to 600kh/s. But network hasrate and diff only decreased from this moment.
Just to repeat for all.Now network hashrate is about 108kh, Dark's pool hashrate 150kh. Network hasrate decreases every minute. About 50-60% blocks orphaned. Pool get payments for 60kh/s only, and spread all coins for all miners, who makes 150kh/s. So each miner gets only 30-40% of desired coins. This situation affected all XLC pools at the moment. We already contacted Mark to fix this problem. Seems this is blockchain bug, because all blocks shares/diff higher than 60% count as orphaned and didnt paid by network. Any hashrate burst only decreases network speed. That situation started then XLC get listed by Cryptopia, because alot of new miners connected, and pool hashrate sometimes raised up to 600kh/s. But network hasrate and diff only decreased from this moment.
All pools affected same thing. (we have tested with 3 private pools)
@OrangeJam @vitik @rabudde
It's a bit off topic, but as it is in beta state yet, I will open a separate ANN thread later.
I think my pool is running stable now, payments are working. Calculation of hashrates and payments are also correct.
There are many orphaned blocks still. I really believe it's due to short block time. To verify this, it would be great to get some more hash power. Even though for some hours.
If possible let's test at https://xlc.minepool.de
hello good night, i just moved 1.4 khs to your pool but i see that blocks are found and still 0 reward for me? hmmm i will wait a little more before switching to another hmmm pplns or pps pool? most of blocks are uncle and not getting paid by blockchain? waiting for your answers It's a bit off topic, but as it is in beta state yet, I will open a separate ANN thread later.
I think my pool is running stable now, payments are working. Calculation of hashrates and payments are also correct.
There are many orphaned blocks still. I really believe it's due to short block time. To verify this, it would be great to get some more hash power. Even though for some hours.
If possible let's test at https://xlc.minepool.de
https://s26.postimg.org/bspkxa5zd/image.png
Thanks for support.
There is no bug, you should have been payed yet (I can see so in payment list).
It's a PPS pool, at this time (early stage/new coin) I think it's not really necessary to use PPLNS, due to short block times and high rewards. Maybe in future.
As I've written, orphaned blocks are related to the fact, that there is another big pool with more hashpower which finds a block earlier mostly. So my guess is, when I gain more hash power, the orphaned blocks should decrease. But that is a fact that belongs to blockchain itself, really.
https://pp.userapi.com/c837233/v837233014/57a11/2ZBLfNUMOCU.jpg
I sent a pack of coins to the stock exchange, less than half came.
The second part is hanging somewhere. What now with this?
I sent a pack of coins to the stock exchange, less than half came.
The second part is hanging somewhere. What now with this?
Looks like we can forget this as there are too many problems that are not going to be fixed and thus the price ai not going to grow but instead will continue to drop.
anyone have "unable to generate deposit address " on cryptopia ?
whats your problem?
when try to deposit on cryptopia i got this " failed to create deposit address for XLC
if this continue persist please contact support "
i just want to make sure if someone got this
@OrangeJam @vitik @rabudde
It's a bit off topic, but as it is in beta state yet, I will open a separate ANN thread later.
I think my pool is running stable now, payments are working. Calculation of hashrates and payments are also correct.
There are many orphaned blocks still. I really believe it's due to short block time. To verify this, it would be great to get some more hash power. Even though for some hours.
If possible let's test at https://xlc.minepool.de
hello good night, i just moved 1.4 khs to your pool but i see that blocks are found and still 0 reward for me? hmmm i will wait a little more before switching to another hmmm pplns or pps pool? most of blocks are uncle and not getting paid by blockchain? waiting for your answers It's a bit off topic, but as it is in beta state yet, I will open a separate ANN thread later.
I think my pool is running stable now, payments are working. Calculation of hashrates and payments are also correct.
There are many orphaned blocks still. I really believe it's due to short block time. To verify this, it would be great to get some more hash power. Even though for some hours.
If possible let's test at https://xlc.minepool.de
https://s26.postimg.org/bspkxa5zd/image.png
Please HELP!
I've launched the daemon, it just finished syncing, then I checked my wallet and I've lost all my balance??!! now it shows 0.000000
what is going on??
Edit: I reset the wallet cache, it synced again and now I have my balance back.
I've launched the daemon, it just finished syncing, then I checked my wallet and I've lost all my balance??!! now it shows 0.000000
what is going on??
Edit: I reset the wallet cache, it synced again and now I have my balance back.
anyone have "unable to generate deposit address " on cryptopia ?
whats your problem?
@OrangeJam @vitik @rabudde
It's a bit off topic, but as it is in beta state yet, I will open a separate ANN thread later.
I think my pool is running stable now, payments are working. Calculation of hashrates and payments are also correct.
There are many orphaned blocks still. I really believe it's due to short block time. To verify this, it would be great to get some more hash power. Even though for some hours.
If possible let's test at https://xlc.minepool.xyz
It's a bit off topic, but as it is in beta state yet, I will open a separate ANN thread later.
I think my pool is running stable now, payments are working. Calculation of hashrates and payments are also correct.
There are many orphaned blocks still. I really believe it's due to short block time. To verify this, it would be great to get some more hash power. Even though for some hours.
If possible let's test at https://xlc.minepool.xyz
Jump to: