Pages:
Author

Topic: Lunatics - LTSX - Rare like the Moon - CryptoNight Algo |CPU - GPU| - page 4. (Read 15672 times)

hero member
Activity: 1148
Merit: 562
Blockchain Core Dev
All right guys, just some little new things.
The wallet which was causing the unconfirmed transactions (forever locked transactions) was the sobersu pool one. That's because it was running on a different version of forknote. Network is now kicking the invalid transactions. Also a wallet "reset" is suggested to everyone.

GPU miners are now moving to  http://ltsx.m42.cx/
(Please note: CPU mining is still more profitable than pool mining)

I hope the pool op has already checked his version, to avoid more issues.

Also I've created a donation address in order to store some funds for further moving!

Code:
Wallet: FXn85gwEX8a1fzC3gQPKGs7hSR3BHecdF2vHH7hprVUxALAiAScL4pyMqy5P1eWGfN5NBCEHRCUd9EAtiuJUzJLfRTQzPkS
hero member
Activity: 812
Merit: 500
When is the exchange?
newbie
Activity: 13
Merit: 0
The pool http://212.73.150.254/
Is not making payments

Pending Balance: 0.398816211005 LTSX

wallet FQynyr8TjNMRgT3i2kjwANVu6w2aFWKWNHvEp2vj5TMMWNEBoYqs6Zf6rMszLW3XspWxDZHBsQ9e4Yf AaL2q6PRoAm2PJ3Q
hero member
Activity: 1148
Merit: 562
Blockchain Core Dev
Pool removed as asked!
I'll setup a donation address to support LTSX in the evening Smiley
newbie
Activity: 67
Merit: 0
I close ltsx.sobpools.ru for mining. When pending balance will be 0 - i close web.
Please, remove my pool from pool's list.
full member
Activity: 144
Merit: 100
Dev, did you set up a community funding address? I think I might donate a bit for promotion. Projects without premine are very rare today!
hero member
Activity: 1148
Merit: 562
Blockchain Core Dev
We are almost at 100 LTSX mined, global hashrate is low now, so solo mining with your CPU is gives you more gains that may a pool can give Smiley
full member
Activity: 224
Merit: 100
Hey dev!
Wouldn't you want to create a slack so the community can discuss more easily?

Yes, great idea.

I'm holding my mined coins, this is small project, but what is most important - there's no premine. So we have lots of potential Smiley
full member
Activity: 378
Merit: 100
Short BTC at: https://www.bitmex.com/register/spz2
Hey dev!
Wouldn't you want to create a slack so the community can discuss more easily?
hero member
Activity: 1148
Merit: 562
Blockchain Core Dev
To all pools, please read my MP. Make sure you're using the correct forknote version. Still waiting for the two major pools to replay.
newbie
Activity: 41
Merit: 0

All's good then!


Indeed! Going smoothly here, getting payouts from both http://ltsx.sobpools.ru/ and http://212.73.150.254/ !

Code:
2017-Aug-15 20:54:59.920064 INFO           0.010000000000       bf93da8e64eea379e43e063c
0ba5a30c
2017-Aug-15 20:54:59.924065 INFO            amount
2017-Aug-15 20:54:59.927065 INFO           0.010000000000       e8444812b59dce18709448f7
f67b8c1a
2017-Aug-15 20:54:59.931065 INFO            amount
2017-Aug-15 20:54:59.934065 INFO           0.010000000000       d917c1f18563adbbcdd559c7
6f3ff56b
2017-Aug-15 20:54:59.938065 INFO            amount
2017-Aug-15 20:54:59.941065 INFO           0.010000000000       58b29c103af927013a022cba
11de219a
2017-Aug-15 20:54:59.945066 INFO            amount
2017-Aug-15 20:54:59.948066 INFO           0.001147670000       c1c659cc1667aee9c427863e
7319ddbf
2017-Aug-15 20:54:59.952066 INFO            amount
2017-Aug-15 20:54:59.954066 INFO           0.010000000000       fda5e71c447408d622033732
bbf9aa23
hero member
Activity: 1148
Merit: 562
Blockchain Core Dev
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:

Quote
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!
full member
Activity: 378
Merit: 100
Short BTC at: https://www.bitmex.com/register/spz2
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:

Quote
forknote v1.0.11.697 ()

It is. When i open it asks me: forknoted.exe click yes and use the right version.
hero member
Activity: 1148
Merit: 562
Blockchain Core Dev
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:

Quote
forknote v1.0.11.697 ()
full member
Activity: 378
Merit: 100
Short BTC at: https://www.bitmex.com/register/spz2
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?
hero member
Activity: 1148
Merit: 562
Blockchain Core Dev
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.
member
Activity: 118
Merit: 11
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

Quote
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!  Smiley
hero member
Activity: 1148
Merit: 562
Blockchain Core Dev
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

Quote
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.
full member
Activity: 378
Merit: 100
Short BTC at: https://www.bitmex.com/register/spz2
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?
Pages:
Jump to: