Leviar.io - Official thread

[danycoman]

work now update 2.0.6


http://xlc.mine-pool.ro/  0.5 fee

[Invis]

http://xlc.dark-mine.su (ex http://xlc.my-mine.su)
Fee 0.2%, payments fixed, enabled and works now! 

Enjoy 

[danycoman]

xlc.mine-pool.ro  cloesed definitive.




sorry

[ddmmtt7]

When hitBTC open deposit&withdraw for XLC?

[grm]

Hye,

http://leviarcoin.chickenkiller.com:8000/# updated with last wallet.

Let's spread the hash !

Grm

[V3n0m]

Hye,

http://leviarcoin.chickenkiller.com:8000/# updated with last wallet.

Let's spread the hash !

Grm

All blocks are orphaned - can you address the scrypt issue.

[grm]

Hye,

http://leviarcoin.chickenkiller.com:8000/# updated with last wallet.

Let's spread the hash !

Grm

All blocks are orphaned - can you address the scrypt issue.

Yeah, i saw that.

I updated the wallet and blockcain today.

I hope it will solve the issue.
If not, any idea of what i should check ?

Grm

[V3n0m]

No idea but I'll throw my cpu miners on the pool to see should be enough toget a block around 500 hash.

Lots of times coins with short block times produce lots of orphans , it happens to when your pool finds the block simultaneously with a dominant pool and the other pool gets the result submitted quicker. This coin has one dominate pool currently so it may not have coding issues at all. We can just try for a few hours and see what happens.

[grm]

No idea but I'll throw my cpu miners on the pool to see should be enough toget a block around 500 hash

I just have another one orphaned.

To check i changed the pool source using the mainstream one and recompile everything.

Hope it will work.

Maybe other pool owners can point me to the sources they are using for the pool ? (or send me a config.json)

[V3n0m]

No idea but I'll throw my cpu miners on the pool to see should be enough toget a block around 500 hash.

Lots of times coins with short block times produce lots of orphans , it happens to when your pool finds the block simultaneously with a dominant pool and the other pool gets the result submitted quicker. This coin has one dominate pool currently so it may not have coding issues at all. We can just try for a few hours and see what happens.

edited my post as you were responding. lets see what happens over the next couple hours.

[danycoman]

Is problem  scrypt, Invis solve this.


I close my pool , because no support for this



just add one line...

[grm]

Having only one pool is not good for the future of the coin.

@Invis : how did you solved it please?

[squashen]

I have latest source compiled and up and running. But think something is wrong

Code:

2017-Aug-05 23:41:40.128047 WARNING Transaction b7dae1e0eecaa294c32cb7db6b5f825b0a120109feb19d52c8cf74362d936191 is not valid. Reason: Transaction uses spent key image
2017-Aug-05 23:41:40.128109 INFO    [138.68.176.26:18001 OUT] Tx verification failed
2017-Aug-05 23:41:40.259457 INFO    [91.126.237.243:18001 OUT] SYNCHRONIZED OK
2017-Aug-05 23:41:47.782005 WARNING Block e83bbc5414358ef11f36016e304d0ecea1e914773bf38c803903727eb07f2f93 has too big cumulative size
2017-Aug-05 23:41:49.055631 WARNING Transaction ab94ba68ee523fb76a46736e6dca016349ef541377d506cb226ab04ef2fa6b75 is not valid. Reason: Transaction uses spent key image
2017-Aug-05 23:41:49.055735 INFO    [138.68.176.26:49866 INC] Tx verification failed
2017-Aug-05 23:41:49.056287 WARNING Transaction b7dae1e0eecaa294c32cb7db6b5f825b0a120109feb19d52c8cf74362d936191 is not valid. Reason: Transaction uses spent key image
2017-Aug-05 23:41:49.056358 INFO    [138.68.176.26:49866 INC] Tx verification failed
2017-Aug-05 23:41:52.816353 WARNING Transaction ab94ba68ee523fb76a46736e6dca016349ef541377d506cb226ab04ef2fa6b75 is not valid. Reason: Transaction uses spent key image
2017-Aug-05 23:41:52.816453 INFO    [138.68.176.26:18001 OUT] Tx verification failed
2017-Aug-05 23:41:52.816960 WARNING Transaction b7dae1e0eecaa294c32cb7db6b5f825b0a120109feb19d52c8cf74362d936191 is not valid. Reason: Transaction uses spent key image
2017-Aug-05 23:41:52.817015 INFO    [138.68.176.26:18001 OUT] Tx verification failed
2017-Aug-05 23:41:53.247236 WARNING Block e83bbc5414358ef11f36016e304d0ecea1e914773bf38c803903727eb07f2f93 has too big cumulative size
2017-Aug-05 23:42:05.609369 WARNING Transaction ab94ba68ee523fb76a46736e6dca016349ef541377d506cb226ab04ef2fa6b75 is not valid. Reason: Transaction uses spent key image
2017-Aug-05 23:42:05.609477 INFO    [138.68.176.26:39349 INC] Tx verification failed
2017-Aug-05 23:42:05.609984 WARNING Transaction b7dae1e0eecaa294c32cb7db6b5f825b0a120109feb19d52c8cf74362d936191 is not valid. Reason: Transaction uses spent key image
2017-Aug-05 23:42:05.610047 INFO    [138.68.176.26:39349 INC] Tx verification failed
2017-Aug-05 23:42:19.166101 WARNING Block e83bbc5414358ef11f36016e304d0ecea1e914773bf38c803903727eb07f2f93 has too big cumulative size
2017-Aug-05 23:42:23.049314 WARNING [92.235.59.26:54723 INC] error during write: TcpConnection::write, events & (EPOLLERR | EPOLLHUP) != 0
2017-Aug-05 23:42:25.460459 WARNING Block e83bbc5414358ef11f36016e304d0ecea1e914773bf38c803903727eb07f2f93 has too big cumulative size
2017-Aug-05 23:42:27.688456 WARNING Block e83bbc5414358ef11f36016e304d0ecea1e914773bf38c803903727eb07f2f93 has too big cumulative size
2017-Aug-05 23:42:31.162534 WARNING Block e83bbc5414358ef11f36016e304d0ecea1e914773bf38c803903727eb07f2f93 has too big cumulative size
2017-Aug-05 23:42:32.312106 WARNING Block e83bbc5414358ef11f36016e304d0ecea1e914773bf38c803903727eb07f2f93 has too big cumulative size

[V3n0m]

@matroska-leviar

Wondering what the plan moving forward for this coin is? I see development don't get me wrong so just a couple of answers as best you can.

1. Does the roadmap still apply for this coin?
2. Have any key players backed out of development since the ICO was not 100% successful?
3. Is there plans to attempt further funding?
4. Can we get support for solo mining in an attempt to decentralize and or support for secondary pools as most individuals have failed to create a functioning pool.

I like the idea behind the coin, no disrespect but things are just looking to be a bit of a mess right now. It would be wise to post a formal update and or roadmap to show what we can expect in the coming weeks/months.

Cheers. THanks.

[Dr.Lecter]

please help me to check the payment on 2017-08-01, i do not received my coin when i update wallet from 1.2.1 => 2.0.6. all coin unconfimed send by xlc.m42.cx on 2017-08-01  was lost.

[danycoman]

Hello everyone!

At this moment we have  up  pools:
------------------------------------

http://chrc.mine-pool.ro/ ==>0.5%fee

http://bcn.mine-pool.ro/  ==>0.5%fee

http://sumo.mine-pool.ro/ ==>0.4%fee

------------------------------------
Thank you for your interest!

Do not forget! We are with you 12/24! Support live!

Daniel

Support mine-pool.ro

[matejbilahora]

Well it looks like you guys made it and everything is just fine. I hope that Nova will add XLC soon.

[squashen]

U guys can Always try this pool just fpr fun:)   http://85.224.141.178

[squashen]

Hi everybody.
I have for fun set up a pool (Powered by  cryptonote-charna-pool v1.2.1 ) for xlc but got some problems.
The pool start and running without problem. i can connect miners both from lan and outside the router and se miner and pool stats like speed, shares etc from both out and in the lan, can se the networkstat and market stat to.
I can even se that i have found 4 blocks, BUT my minerstat show no pending and no paided coins, adminpage show no owned, no payed, no mined coins at all, but adminpage tells me that 17 coins are in poolwallet and 17 locked (thats those 4 block)

So what have i missed?? the poolwalletadress is the same i have used on miners, is that the problem?

Any help from one of u guys that have succesfull got this to work??

Thanks!!!!!

[ThorthChariot]

OK   i make a update to  WALLET 2.0.6

delete all, from %appdata% ... etc....


start to sync from 0 ...  and NOW ...  remain at 22196 ...