[ANN] [XSH] TOR/i2p, Quantum proof, MN, PoS/PoW, Fully ano, SHIELD

[TheKryptonian]

No worries, it's good to talk these things out.  I don't know much about this stuff, still learning.

For anyone trying to follow the conversation: it looks like all three pools are still on the same chain.

Still, how would you explain the difficulty discrepancy for the Confirmed blocks on the Bearded pool vs the difficulties for the same block height on their explorer? Maybe their explorer is on the right chain, but their pool daemon is not?

I'm not sure I follow.  Again, I'm new at this, so sorry if I'm reasoning something wrong:

https://beardedpool.fr/site/block?id=1899 shows the last confirmed beardedpool block was 63716, right?  With 59.0268308 diff?

That's the same diff shown by umine's explorer: https://umine.org/explorer/XSH?height=63716

If you see a specific discrepancy, I'll take a look (though I probably won't know much).

[jdbao]

is this coin still live?

[Wmj0FSsK9ofql0ZFm]

No worries, it's good to talk these things out.  I don't know much about this stuff, still learning.

For anyone trying to follow the conversation: it looks like all three pools are still on the same chain.

Still, how would you explain the difficulty discrepancy for the Confirmed blocks on the Bearded pool vs the difficulties for the same block height on their explorer? Maybe their explorer is on the right chain, but their pool daemon is not?

I'm not sure I follow.  Again, I'm new at this, so sorry if I'm reasoning something wrong:

https://beardedpool.fr/site/block?id=1899 shows the last confirmed beardedpool block was 63716, right?  With 59.0268308 diff?

That's the same diff shown by umine's explorer: https://umine.org/explorer/XSH?height=63716

If you see a specific discrepancy, I'll take a look (though I probably won't know much).

Yup, but just do the same thing with the Confirmed blocks before the Orphans (block 63336 and earlier).

[TheKryptonian]

is this coin still live?

Yeah we're just talking about whether there's a fork, but it looks like there isn't one.  As far as I know, you can solomine Lyra2v2, Scrypt, or Myr-Gr, or you can pool mine Myr-Gr chain.  Recommend pool-mining myr-gr at umine for now, as other pools aren't getting enough hash support.

X17 and Blake2s chains not working as far as I know.

[Wmj0FSsK9ofql0ZFm]

is this coin still live?

Yeah we're just talking about whether there's a fork, but it looks like there isn't one.  As far as I know, you can solomine Lyra2v2, Scrypt, or Myr-Gr, or you can pool mine Myr-Gr chain.  Recommend pool-mining myr-gr at umine for now, as other pools aren't getting enough hash support.

X17 and Blake2s chains not working as far as I know.

X17 and blake2s chains work on the newest daemons, but mining them will cause you to fork from umine's chain, since the daemon version is not the same.

[TheKryptonian]

No worries, it's good to talk these things out.  I don't know much about this stuff, still learning.

For anyone trying to follow the conversation: it looks like all three pools are still on the same chain.

Still, how would you explain the difficulty discrepancy for the Confirmed blocks on the Bearded pool vs the difficulties for the same block height on their explorer? Maybe their explorer is on the right chain, but their pool daemon is not?

I'm not sure I follow.  Again, I'm new at this, so sorry if I'm reasoning something wrong:

https://beardedpool.fr/site/block?id=1899 shows the last confirmed beardedpool block was 63716, right?  With 59.0268308 diff?

That's the same diff shown by umine's explorer: https://umine.org/explorer/XSH?height=63716

If you see a specific discrepancy, I'll take a look (though I probably won't know much).

Yup, but just do the same thing with the Confirmed blocks before the Orphans (block 63336 and earlier).

Yeah you're right, it is weird.  Maybe there's something wrong with beardedpool's tracking.  I don't know how well Yiimp and these guys have adjusted for multi-algo.  But I have no explanation for this, so I guess we just need to wait for dev.  

Really it's like was said, need the pools to keep their daemons up to date.  And we need to spread the hash better.  I like umine but I'm not mining on it for this reason.

[Wmj0FSsK9ofql0ZFm]

No worries, it's good to talk these things out.  I don't know much about this stuff, still learning.

For anyone trying to follow the conversation: it looks like all three pools are still on the same chain.

Still, how would you explain the difficulty discrepancy for the Confirmed blocks on the Bearded pool vs the difficulties for the same block height on their explorer? Maybe their explorer is on the right chain, but their pool daemon is not?

I'm not sure I follow.  Again, I'm new at this, so sorry if I'm reasoning something wrong:

https://beardedpool.fr/site/block?id=1899 shows the last confirmed beardedpool block was 63716, right?  With 59.0268308 diff?

That's the same diff shown by umine's explorer: https://umine.org/explorer/XSH?height=63716

If you see a specific discrepancy, I'll take a look (though I probably won't know much).

Yup, but just do the same thing with the Confirmed blocks before the Orphans (block 63336 and earlier).

Yeah you're right, it is weird.  Maybe there's something wrong with beardedpool's tracking.  I don't know how well Yiimp and these guys have adjusted for multi-algo.  But I have no explanation for this, so I guess we just need to wait for dev.  

Really it's like was said, need the pools to keep their daemons up to date.  And we need to spread the hash better.  I like umine but I'm not mining on it for this reason.

Both bigmine and bearded mined their last block 3 hours ago.

I think what might've happened is someone tried to mine X17 on the newest daemon 3 hours ago, and both bearded and bigmine accepted it (new daemon) but umine rejected it (old daemon), causing a split. Umine outcompeted all other chains (>51%) and rejected all their new blocks, hence these discrepancies...   That's the best explanation I can think of.

[Atotarho]

Electrum wallet has ceased to be synchronized

[umine.org]

Hello everyone, sorry for the delay.
We've updated wallet to "v2.1.0.0-ada57c6-funky-beta" version

[TheKryptonian]

Hello everyone, sorry for the delay.
We've updated wallet to "v2.1.0.0-ada57c6-funky-beta" version

I think you forked from the other pools, or at least from my daemon.  But you're probably the legitimate fork?

[umine.org]

Hello everyone, sorry for the delay.
We've updated wallet to "v2.1.0.0-ada57c6-funky-beta" version

I think you forked from the other pools, or at least from my daemon.  But you're probably the legitimate fork?

We hope so

[trgnn]

No worries, it's good to talk these things out.  I don't know much about this stuff, still learning.

For anyone trying to follow the conversation: it looks like all three pools are still on the same chain.

Still, how would you explain the difficulty discrepancy for the Confirmed blocks on the Bearded pool vs the difficulties for the same block height on their explorer? Maybe their explorer is on the right chain, but their pool daemon is not?

I'm not sure I follow.  Again, I'm new at this, so sorry if I'm reasoning something wrong:

https://beardedpool.fr/site/block?id=1899 shows the last confirmed beardedpool block was 63716, right?  With 59.0268308 diff?

That's the same diff shown by umine's explorer: https://umine.org/explorer/XSH?height=63716

If you see a specific discrepancy, I'll take a look (though I probably won't know much).

Yup, but just do the same thing with the Confirmed blocks before the Orphans (block 63336 and earlier).

Yeah you're right, it is weird.  Maybe there's something wrong with beardedpool's tracking.  I don't know how well Yiimp and these guys have adjusted for multi-algo.  But I have no explanation for this, so I guess we just need to wait for dev.  

Really it's like was said, need the pools to keep their daemons up to date.  And we need to spread the hash better.  I like umine but I'm not mining on it for this reason.

Hello everyone ! I'm investigating this issue but it would be surprising to see another chain poping out without any odd change on the pool or on your side. We updated the wallet before block 50'000, as asked by the dev so, please, monitor your payouts, we'll see what's happening.

Also, yeah, spread the hash We just lowered our fee to 0.4% guys, come It's not a good thing to have 80% of the hash centralized, one error or late update from the hash holder and the chain break. Fortunately, it's solved now. To secure the network, please, spread the hash.

https://beardedpool.fr

Code:

-a myr-gr -o stratum+tcp://beardedpool.fr:5433 -u YOUR_WALLET -p c=XSH

[borderline]

now my wallet don't  synch

[nicog5]

now my wallet don't  synch

My wallet too.

[SHIELDcurrency]

now my wallet don't  synch

My wallet too.

Make sure you have the newest wallet: https://github.com/ShieldCoin/SHIELD/releases/download/v1.1/Electrum-Windows-2.4.2.zip
and if that doesn't help you can try this:

Ok, solved. Go to your roaming/AppData folder and delete everything in the Electrum-XSH folder. Start your wallet and use your seed to restore it. And poof, all transactions are shown confirmed and everything is back to normal.

To be sure, backup the Electrum-XSH folde, just in case

Hope this solves it,

The Shield Team

[gerietis]

Electrum wallet has ceased to be synchronized

closed Electrum
deleted everything in AppData\Roaming\Electrum-XSH\ , except AppData\Roaming\Electrum-XSH\wallets directory
started Electrum
everything is ok

[borderline]

work perfect thanks dev

[Fluffyfart]

Can some one please explain me why these security coins are any different from each other ?
Or what makes them better then the other .. at the moment there are so many coins that are referring to secure and privacy.

Of course this is important but what make shield any special in compare with the other coins.
Don't hate me I am interested just digging around a bit.

 

[avirdoz]

Chain splited, after full resync height on our node not match umine height.

[gerietis]

is there normal explorer ?