Lunatics - LTSX - Rare like the Moon - CryptoNight Algo |CPU - GPU|

[998kb]

jacko0088
Russian translation? Do you need?

Well as you have seen there's no bounty, it's up to you

Ok then. I'll do it. But it won't be fast.

[Vegan97]

Dev are you promoting somewhere the coin?

Hi Vegan97,
not yet! There's still a problem with pools, (maybe most of you haven't noticed yet) but seems like the payment processor on forknote-source pools engines is sending out payments in a wrong way sometimes. I've already contacted the two major pool operators, and they're already working on it. Probably during next 48 hours pools will go down for a reset.

I perfer have everything 100% working, pools too, before taking action on some kind of promotion. Even if pools are not connected with coin source.

Understood. Please, keep us updated with the news. Thank you!

[jacko0088]

jacko0088
Russian translation? Do you need?

Well as you have seen there's no bounty, it's up to you

Ok then. I'll do it. But it won't be fast.

Thanks

Dev are you promoting somewhere the coin?

Hi Vegan97,
not yet! There's still a problem with pools, (maybe most of you haven't noticed yet) but seems like the payment processor on forknote-source pools engines is sending out payments in a wrong way sometimes. I've already contacted the two major pool operators, and they're already working on it. Probably during next 48 hours pools will go down for a reset.

I perfer have everything 100% working, pools too, before taking action on some kind of promotion. Even if pools are not connected with coin source.

Understood. Please, keep us updated with the news. Thank you!

Don't worry, if you have locked funds in your wallet for log time, like happened to the user stupidboy, then the pool which sent you that payment is probably affected by this issue.

[998kb]

jacko0088
It was faster than i thought.

So, russian topic:
https://bitcointalk.org/index.php?topic=2085435.msg20841951#msg20841951

[998kb]

It's getting crazy

[jacko0088]

It's getting crazy

This is what i was talking about:

35dcc778c04b22ae9d332ce0fbcc14cfc63e8713f74f5d950d76a79223700bd6 (sent from sobpool)

871ebf8bd36fcaefe3baf78aae0c9d4891521314fc27598aa687662b0f3cc55e (sent from m42cx pool)

those are both weird transaction sent out without funds or without a proper fee, the pool keep sending those. You see your coin unconfirmed, but daemon will never accept those because sent wrong (and continuosly resend).

That's why I've told both pools to stop, resync their chain from scratch, and manual pay those funds. I'm still waiting for their replies.

[noormcs5]

The Moon is not exactly rare is it? I'm just giving you a hard time but what exactly sets your coin and your project departs far as Rarity among the vast number of all coins that are already out there? There are quite a few that are being released on a weekly a daily basis you're going to have to do something to set Yours apart.

[Vegan97]

Dev can you set up a pool yourself?

[jacko0088]

The Moon is not exactly rare is it? I'm just giving you a hard time but what exactly sets your coin and your project departs far as Rarity among the vast number of all coins that are already out there? There are quite a few that are being released on a weekly a daily basis you're going to have to do something to set Yours apart.

Well, I've nothing to do with other coins that are being released in those days, I've maded this as a gift (as you can even read on the main OP).

[jacko0088]

Dev can you set up a pool yourself?

I can set up a miningpool without any problem, even now. The issue is the mainteniance. I work as an IT Technician, and I'm everyday (even weekends ) around fixing pc, servers and techs for clients. If something go wrong, should be fixed in no time. And that's not the kind of support I'm able to provide atm.

[Madcard]

it is hoped that at least somewhere to trade?

[Vegan97]

Dev can you provide us a roadmap?

[Vegan97]

2017-Aug-14 17:08:19.522518 INFO    ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 8168
2017-Aug-14 17:08:19.522518 INFO    id: 2dcd21ebab0d61aea568baa703ba97422e497194b7e56b51f57ec5e8f1cfc7f8
2017-Aug-14 17:08:19.522518 INFO    PoW:        01aeb5a1d8a121e12baa6e35c0dd9d2ec05c07b5e87fee428256727124000000
2017-Aug-14 17:08:19.522518 INFO    difficulty: 1729782
2017-Aug-14 17:15:39.060385 INFO    ###### REORGANIZE on height: 8168 of 8168 with cum_difficulty 12157597779
2017-Aug-14 17:15:39.060385 INFO     alternative blockchain size: 2 with cum_difficulty 12159324447
2017-Aug-14 17:15:39.257911 INFO    ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 8168
2017-Aug-14 17:15:39.257911 INFO    id: 68a93dd3a8c62d81d9174fa12ab2956d3d67d526e5354d980b6072c10e4dc157
2017-Aug-14 17:15:39.257911 INFO    PoW:        73c7bb78024334fb241641780be15537a87ca3d31c1a215e784a14b2b7050000
2017-Aug-14 17:15:39.257911 INFO    difficulty: 1729782
2017-Aug-14 17:15:39.273953 INFO    REORGANIZE SUCCESS! on height: 8168, new blockchain size: 8170


What is this?

[jacko0088]

2017-Aug-14 17:08:19.522518 INFO    ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 8168
2017-Aug-14 17:08:19.522518 INFO    id: 2dcd21ebab0d61aea568baa703ba97422e497194b7e56b51f57ec5e8f1cfc7f8
2017-Aug-14 17:08:19.522518 INFO    PoW:        01aeb5a1d8a121e12baa6e35c0dd9d2ec05c07b5e87fee428256727124000000
2017-Aug-14 17:08:19.522518 INFO    difficulty: 1729782
2017-Aug-14 17:15:39.060385 INFO    ###### REORGANIZE on height: 8168 of 8168 with cum_difficulty 12157597779
2017-Aug-14 17:15:39.060385 INFO     alternative blockchain size: 2 with cum_difficulty 12159324447
2017-Aug-14 17:15:39.257911 INFO    ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 8168
2017-Aug-14 17:15:39.257911 INFO    id: 68a93dd3a8c62d81d9174fa12ab2956d3d67d526e5354d980b6072c10e4dc157
2017-Aug-14 17:15:39.257911 INFO    PoW:        73c7bb78024334fb241641780be15537a87ca3d31c1a215e784a14b2b7050000
2017-Aug-14 17:15:39.257911 INFO    difficulty: 1729782
2017-Aug-14 17:15:39.273953 INFO    REORGANIZE SUCCESS! on height: 8168, new blockchain size: 8170


What is this?

Quoting from the net https://monero.stackexchange.com/questions/2018/block-added-as-alternative-on-height-xxxxx

Reorgs happen when there is temporarily a disagreement about what the longest chain is. It happens in every Cryptocurrency, and the shorter the block time, the more frequent it happens. Basically, picture a guy in the Philippines and a guy in Spain each mining what they say is block 780000 at almost exactly the same time. Half the network sees the one guys block first and accepts it, while rejecting the other guys block. The other half the network does the opposite. It's actually not that uncommon for this to happen, but usually someone mining on one of those two chains finds another block and adds it on, and then everyone goes "oh look, that chain is longer" and ditches the other one. BUT, sometimes, the near tie in finding blocks can happen two or three or four times in a row. Eventually, one side wins out, and anyone on the wrong chain has to reorganize. This is why merchants are recommended to wait for a few confirmations before fully crediting a payment for big ticket items. The more confirmations (or the more blocks that get added on top of the one your transaction is in), the harder it is to happen on a reorg. The whole problem is caused by a slight delay in sending signals to all corners of the earth that a miner found a block. The total lag is pretty much ~15 seconds or so. The shorter the block time, the larger an effect that lag has. i.e. for a 1 minute block, that lag is 1/4th the block time, but for a 2 minute block, it is 1/8th the block time. In bitcoin's case, it is 1/40th the block time. The smaller that fraction gets, the less likely a reorg is to occur.

[stupidboy123]

2017-Aug-14 17:08:19.522518 INFO    ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 8168
2017-Aug-14 17:08:19.522518 INFO    id: 2dcd21ebab0d61aea568baa703ba97422e497194b7e56b51f57ec5e8f1cfc7f8
2017-Aug-14 17:08:19.522518 INFO    PoW:        01aeb5a1d8a121e12baa6e35c0dd9d2ec05c07b5e87fee428256727124000000
2017-Aug-14 17:08:19.522518 INFO    difficulty: 1729782
2017-Aug-14 17:15:39.060385 INFO    ###### REORGANIZE on height: 8168 of 8168 with cum_difficulty 12157597779
2017-Aug-14 17:15:39.060385 INFO     alternative blockchain size: 2 with cum_difficulty 12159324447
2017-Aug-14 17:15:39.257911 INFO    ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 8168
2017-Aug-14 17:15:39.257911 INFO    id: 68a93dd3a8c62d81d9174fa12ab2956d3d67d526e5354d980b6072c10e4dc157
2017-Aug-14 17:15:39.257911 INFO    PoW:        73c7bb78024334fb241641780be15537a87ca3d31c1a215e784a14b2b7050000
2017-Aug-14 17:15:39.257911 INFO    difficulty: 1729782
2017-Aug-14 17:15:39.273953 INFO    REORGANIZE SUCCESS! on height: 8168, new blockchain size: 8170


What is this?

Quoting from the net https://monero.stackexchange.com/questions/2018/block-added-as-alternative-on-height-xxxxx

Reorgs happen when there is temporarily a disagreement about what the longest chain is. It happens in every Cryptocurrency, and the shorter the block time, the more frequent it happens. Basically, picture a guy in the Philippines and a guy in Spain each mining what they say is block 780000 at almost exactly the same time. Half the network sees the one guys block first and accepts it, while rejecting the other guys block. The other half the network does the opposite. It's actually not that uncommon for this to happen, but usually someone mining on one of those two chains finds another block and adds it on, and then everyone goes "oh look, that chain is longer" and ditches the other one. BUT, sometimes, the near tie in finding blocks can happen two or three or four times in a row. Eventually, one side wins out, and anyone on the wrong chain has to reorganize. This is why merchants are recommended to wait for a few confirmations before fully crediting a payment for big ticket items. The more confirmations (or the more blocks that get added on top of the one your transaction is in), the harder it is to happen on a reorg. The whole problem is caused by a slight delay in sending signals to all corners of the earth that a miner found a block. The total lag is pretty much ~15 seconds or so. The shorter the block time, the larger an effect that lag has. i.e. for a 1 minute block, that lag is 1/4th the block time, but for a 2 minute block, it is 1/8th the block time. In bitcoin's case, it is 1/40th the block time. The smaller that fraction gets, the less likely a reorg is to occur.

Nice explaination! 

[jacko0088]

To all linux users and pools!
Make sure to the on this forknote version!

https://github.com/forknote/forknote/releases/tag/1.0.11

If you're not on this version you should stop your wallet, delete your blockchain data, resync again and perform a wallet reset. This should solve the unconfirmed tx issue.

[Vegan97]

To all linux users and pools!
Make sure to the on this forknote version!

https://github.com/forknote/forknote/releases/tag/1.0.11

If you're not on this version you should stop your wallet, delete your blockchain data, resync again and perform a wallet reset. This should solve the unconfirmed tx issue.

Should everyobody update the wallet or just pools?

[jacko0088]

To all linux users and pools!
Make sure to the on this forknote version!

https://github.com/forknote/forknote/releases/tag/1.0.11

If you're not on this version you should stop your wallet, delete your blockchain data, resync again and perform a wallet reset. This should solve the unconfirmed tx issue.

Should everyobody update the wallet or just pools?

If you've downloaded the wallet from the zip I've posted since start, you should be on the correct release. I think pools have just forked the last unstable release. That's why we got some stuck transactions. To check your version, launch your daemon, it should be like this:

forknote v1.0.11.697 ()

[Vegan97]

To all linux users and pools!
Make sure to the on this forknote version!

https://github.com/forknote/forknote/releases/tag/1.0.11

If you're not on this version you should stop your wallet, delete your blockchain data, resync again and perform a wallet reset. This should solve the unconfirmed tx issue.

Should everyobody update the wallet or just pools?

If you've downloaded the wallet from the zip I've posted since start, you should be on the correct release. I think pools have just forked the last unstable release. That's why we got some stuck transactions. To check your version, launch your daemon, it should be like this:

forknote v1.0.11.697 ()

It is. When i open it asks me: forknoted.exe click yes and use the right version.

[jacko0088]

To all linux users and pools!
Make sure to the on this forknote version!

https://github.com/forknote/forknote/releases/tag/1.0.11

If you're not on this version you should stop your wallet, delete your blockchain data, resync again and perform a wallet reset. This should solve the unconfirmed tx issue.

Should everyobody update the wallet or just pools?

If you've downloaded the wallet from the zip I've posted since start, you should be on the correct release. I think pools have just forked the last unstable release. That's why we got some stuck transactions. To check your version, launch your daemon, it should be like this:

forknote v1.0.11.697 ()

It is. When i open it asks me: forknoted.exe click yes and use the right version.

All's good then!