[ANN][XCH] ⚡ xChangeum ⚡ [Scrypt PoW/15% Premined] Exchange Listing Guarantee

[DigitalFinex]

We've noticed some nodes are having problems with orphaned blocks.  To remedy this, please delete your blocks and chainstate folders and freshly sync from the network again.

You can find those folders in:
Windows:
c:\Users\<your username>\AppData\Roaming\xChangeum\

Linux:
~/.xchangeum

If you're having problems, only delete those two folders. 

Remember to backup your wallets folder as those contain your private keys to your coins.

[FreakCoder]

We've noticed some nodes are having problems with orphaned blocks.  To remedy this, please delete your blocks and chainstate folders and freshly sync from the network again.

You can find those folders in:
Windows:
c:\Users\<your username>\AppData\Roaming\xChangeum\

Linux:
~/.xchangeum

If you're having problems, only delete those two folders. 

Remember to backup your wallets folder as those contain your private keys to your coins.

After doing a resync of the chain on the pool, we continue to find orphans. In looking at the debug.log, it appears the nodes provided are refusing connection. Not sure if that is the culprit but I will continue to investigate.

[sidgrip]

After doing a resync of the chain on the pool, we continue to find orphans. In looking at the debug.log, it appears the nodes provided are refusing connection. Not sure if that is the culprit but I will continue to investigate.

If two pools are having the same issue, It would most likely be the nodes are refusing connections.

[DigitalFinex]

We've noticed some nodes are having problems with orphaned blocks.  To remedy this, please delete your blocks and chainstate folders and freshly sync from the network again.

You can find those folders in:
Windows:
c:\Users\<your username>\AppData\Roaming\xChangeum\

Linux:
~/.xchangeum

If you're having problems, only delete those two folders. 

Remember to backup your wallets folder as those contain your private keys to your coins.

After doing a resync of the chain on the pool, we continue to find orphans. In looking at the debug.log, it appears the nodes provided are refusing connection. Not sure if that is the culprit but I will continue to investigate.

The P2P port is 5680

The RPCPort is 5679

Let me know if that helps at all!?

[alorotomca]

Transactions are not getting confirmed. I sent some coins from one wallet to another yesterday.

Status: 0/unconfirmed, in memory pool
Date: 5/22/2018 15:46
From: unknown

[FreakCoder]

We've noticed some nodes are having problems with orphaned blocks.  To remedy this, please delete your blocks and chainstate folders and freshly sync from the network again.

You can find those folders in:
Windows:
c:\Users\<your username>\AppData\Roaming\xChangeum\

Linux:
~/.xchangeum

If you're having problems, only delete those two folders.  

Remember to backup your wallets folder as those contain your private keys to your coins.

After doing a resync of the chain on the pool, we continue to find orphans. In looking at the debug.log, it appears the nodes provided are refusing connection. Not sure if that is the culprit but I will continue to investigate.

The P2P port is 5680

The RPCPort is 5679

Let me know if that helps at all!?

It appears the refused connections aren't the nodes provided by other connections. I have made sure the RPC port is the one you provided and resend the chain. However, we continue to only find orphans. A block explorer may help or once your pool is up, we can sync to that. It seems anyone mining is probably on there own chain until it can be verified somewhere.

[DigitalFinex]

Transactions are not getting confirmed. I sent some coins from one wallet to another yesterday.

Status: 0/unconfirmed, in memory pool
Date: 5/22/2018 15:46
From: unknown

What block is your client showing you're on?

You can check the current block height by typing getmininginfo in to the xChangeum Core Console Window (Help->Debug window->Console).

Mine is showing block 888 as the latest block (as I write this).

[alorotomca]

The transaction was confirmed just now. Thanks.

[FreakCoder]

Transactions are not getting confirmed. I sent some coins from one wallet to another yesterday.

Status: 0/unconfirmed, in memory pool
Date: 5/22/2018 15:46
From: unknown

What block is your client showing you're on?

You can check the current block height by typing getmininginfo in to the xChangeum Core Console Window (Help->Debug window->Console).

Mine is showing block 885 as the latest block (as I write this).

Our pool is roughly the same height but all orphans. I can only suggest that someone is solo mining with a higher hashrate.

[DigitalFinex]

Transactions are not getting confirmed. I sent some coins from one wallet to another yesterday.

Status: 0/unconfirmed, in memory pool
Date: 5/22/2018 15:46
From: unknown

What block is your client showing you're on?

You can check the current block height by typing getmininginfo in to the xChangeum Core Console Window (Help->Debug window->Console).

Mine is showing block 885 as the latest block (as I write this).

Our pool is roughly the same height but all orphans. I can only suggest that someone is solo mining with a higher hashrate.

Mine is showing 1954396171 networkhashps.  What is the pool averaging?

[DigitalFinex]

Transactions are not getting confirmed. I sent some coins from one wallet to another yesterday.

Status: 0/unconfirmed, in memory pool
Date: 5/22/2018 15:46
From: unknown

What block is your client showing you're on?

You can check the current block height by typing getmininginfo in to the xChangeum Core Console Window (Help->Debug window->Console).

Mine is showing block 885 as the latest block (as I write this).

Our pool is roughly the same height but all orphans. I can only suggest that someone is solo mining with a higher hashrate.

I will add you pool to the ANN, hopefully you will receive more hashing power.

[index932]

Transactions are not getting confirmed. I sent some coins from one wallet to another yesterday.

Status: 0/unconfirmed, in memory pool
Date: 5/22/2018 15:46
From: unknown

What block is your client showing you're on?

You can check the current block height by typing getmininginfo in to the xChangeum Core Console Window (Help->Debug window->Console).

Mine is showing block 885 as the latest block (as I write this).

Our pool is roughly the same height but all orphans. I can only suggest that someone is solo mining with a higher hashrate.

I will add you pool to the ANN, hopefully you will receive more hashing power.

I added this coin to my pool and getting all orphans as well! Please do add me to the pool list.
http://Weekendpool.net

[DigitalFinex]

Transactions are not getting confirmed. I sent some coins from one wallet to another yesterday.

Status: 0/unconfirmed, in memory pool
Date: 5/22/2018 15:46
From: unknown

What block is your client showing you're on?

You can check the current block height by typing getmininginfo in to the xChangeum Core Console Window (Help->Debug window->Console).

Mine is showing block 885 as the latest block (as I write this).

Our pool is roughly the same height but all orphans. I can only suggest that someone is solo mining with a higher hashrate.

I will add you pool to the ANN, hopefully you will receive more hashing power.

I added this coin to my pool and getting all orphans as well! Please do add me to the pool list.
http://Weekendpool.net

We've added your pool too.  Thanks!

[ChainMapper]

@ DEV

Please contact me to get XCH added to https://chainmapper.com

[Samuiel]

Project with good concept and I think it's worth the support. Good luck for this project
Egretia.

[alorotomca]

Transactions are not getting confirmed again.
Curent block hight is 1435.

Status: 0/unconfirmed, in memory pool, broadcast through 14 nodes
Date: 5/24/2018 09:39

[DigitalFinex]

Transactions are not getting confirmed again.
Curent block hight is 1435.

Status: 0/unconfirmed, in memory pool, broadcast through 14 nodes
Date: 5/24/2018 09:39

We believe a miner with the most hashing power across the network is not mining any transactions.

A form of Selfish Mining, which could also explain the orphaned blocks the pools were encountering.

We will need more hashing power on our network to solve this problem.

In the meantime, hopefully when our pool launches we'll have enough hashing power to stop this style of mining.

As a precaution, we've raised the number of confirmations required to get the coins on our exchange to 110.  This should prevent any form of Double Spend (if the miner was considering that also).

[kurbeks]

Is windows wallet available?

[DigitalFinex]

Is windows wallet available?

Yes, you can download it from xchangeum.com

[kurbeks]

Is windows wallet available?

Yes, you can download it from xchangeum.com

Thanx!

Any working pools ( i read about orphans but still would try). Weekend pool doesn't accept any shares.