Hi, so you were mining to your own wallet or the exchanges wallet? I know that both exchanges have said not to mine to their wallet, so only mine to your own wallet.
If it was your own wallet, the payment ID would not have mattered since any valid payment ID will still show on your wallet. If it was the exchange then yes it needs to be the correct payment ID, otherwise they wont credit you.

If the above is not correct, than ask one of us on discord for help so we can better understand the problem.

I posted about a week and half ago we would release code for the POS in one to two weeks.

We have decided to write this in C, since it will be more efficient.

You can follow the github Proof of stake repo since we will be working on this every few days
https://github.com/X-CASH-official/Proof_of_stake

The other one is for test right now, to build programs to test out the stuff from the POS repo
https://github.com/X-CASH-official/Proof_of_stake_test

More details on the system will be released soon, as the code develops, but their is still to many test to perform before we release more details.

First upload of code
https://github.com/X-CASH-official/Proof_of_stake/commit/f6111174dd7c4129c2a726f9667e66ff41001c03

Were building a lot of other products in the X-network, that will utilize X-CASH.
https://medium.com/x-cash/rebranding-and-project-updates-8f48bdf87612

Also just talking about X-CASH
First CN Coin with private and public tx, that mimic the real fiat system. This is also from the same account, you dont need two separate accounts like some other privacy coins
https://medium.com/x-cash/x-cash-major-update-1-4-0-flexprivacy-cnv2-bulletproof-and-fixed-ring-size-106a20ce0b06

Also we plan on having proof of stake as well, and more details will be released on this soon.

Maternode / POS is in the whitepaper. More details we be released in the next month or two. Code will hopefully be posted soon on github (the small part that is done of it) and will be worked on on github.

Hi,
Its going to be only proof of stake when we switch. More details on this will be coming soon!

Thank you for bringing your concerns to our attention.
The "An error has occurred" is from a false positive from a check we have on the website to make sure people dont try to signup for multiple accounts to get more of the airdrop.

Usually the fix for this is to try another connection, like a mobile phone to signup. Once your signed up you can then login with any connection including a VPN.


For the GUI wallet, we are aware that sometimes when switching from the account tab to any of the other tabs, it can get stuck, and show the text from both of the tabs. We have been aware of this for a little bit, but this bug was moved to the end as far as priority since some of the other issues were more important to solve, especially since re clicking on the tab will make the error go away. This bug will be fixed in the next release of the GUI wallet.






The proof of stake consensus algorithm is currently being researched and worked on in parallel. We have been working on this for about 3-4 weeks now. We plan to have the consensus algorithm built and deployed in Q1 2019. I cant really say much about the details of the proof of stake, but we will be releasing more on it as it is developed.

This was brought up actually on launch day (the 9th post on the first page)
here is the response

This is a good question
This will be a long post, but I think this needs to be explained in a simple yet still technical way to understand public txs

Public tx were created to solve 2 issues
#1 Allow the user to send public or private tx from the same wallet on the same blockchain
#2 Allow the user to prove who was the sender.

(1) Our public tx allow someone at send time, to make it public to assist them in proving that they paid X person Y amount. That is the purpose we had in mind when building them, since our coin is a privacy blockchain at its core.

(2) Currently on any cryptonote coin their is a way to prove that X amount was sent to Y address, but there is no way to prove what address was the sender and what address was the receiver. You could only prove the addresses and the amounts in that tx, but could not prove which address initiated the transfer.

Example lets use this tx hash as our example (these are my two test accounts I use for testing on the live mainchain)
https://explorer.x-cash.org/Transaction?data=7ecd79d7ead6c2f23cb404409aca01f8c9e30d7b07bcd4e9332a1c4872d1dd93

if you decode this tx for both addresses involved you can see that
XCA1kzoR3ZLNg5zxNmxrY8FYKtgEvPZqC2xoRpm1axCpQcrrZfoKTSkSNsASDspdt3j1WcEnQJyuuB5 VPSB56WWy36A4sQtQhe            got paid              62,995.273
XCA1cH8Qs5hLYnzQTDuJqkJiQEZbgQsUM3BgA6vBod5T5Eindas5sikKJaLbkhM3YBW7PtoJY6BtNLk ZuahksLFX5eSPDcmCLL              got paid                       5




But this does no good in the sense of who is the sender and who is the receiver? We cant tell since in regular cryptonote that is not possible.

But if you go to https://explorer.x-cash.org/Transaction?data=7ecd79d7ead6c2f23cb404409aca01f8c9e30d7b07bcd4e9332a1c4872d1dd93 you can clearly see it will say that
XCA1kzoR3ZLNg5zxNmxrY8FYKtgEvPZqC2xoRpm1axCpQcrrZfoKTSkSNsASDspdt3j1WcEnQJyuuB5 VPSB56WWy36A4sQtQhe            sent        5      to  
      XCA1cH8Qs5hLYnzQTDuJqkJiQEZbgQsUM3BgA6vBod5T5Eindas5sikKJaLbkhM3YBW7PtoJY6BtNLk ZuahksLFX5eSPDcmCLL

So how we can tell this is accurate? well you can use a function to verify the sender
https://explorer.x-cash.org/VerifySender?public_address=XCA1kzoR3ZLNg5zxNmxrY8FYKtgEvPZqC2xoRpm1axCpQcrrZfoKTSkSNsASDspdt3j1WcEnQJyuuB5VPSB56WWy36A4sQtQhe&tx_private_key=4a5fb3c39caf223eacfe4bcc2db84811c333b52ea30df5c16a6d62b0163cce0b&tx_signature=SigV1Fog4nV3sThaLbVDQDnyo2xSNt4Qx4vZz5Ln1AAz3CJe3NVWJzuorWRzR7WTV4FxtycjccJ2DLdkSDWES8bPDUQvK



We will be releasing a yellow paper on public tx soon.







As for the question about does your balance get revealed on the explorer now.
In our public tx we kept two aspects of privacy (ringCT and stealth addresses)
this allows for two things
#1 the balance cant be shown
#2 the inputs of the tx are not shown (meaning no one can go back in the explorer and see that X address sent you those funds that you spent public) This is the major non privacy aspect of Bitcoin.

We felt that these two things still needed to be in public TX to still keep the privacy of the sender

(1) https://explorer.x-cash.org/TXSearchResults?data=public_address%7CXCA1cH8Qs5hLYnzQTDuJqkJiQEZbgQsUM3BgA6vBod5T5Eindas5sikKJaLbkhM3YBW7PtoJY6BtNLkZuahksLFX5eSPDcmCLL
as you can see, you can see all the PUBLIC tx I have made and received but not any of my PRIVATE tx show up


again looking at the balance it shows I received 122 XCASH yet my balance right now on this test wallet is  56.206675


(2) looking at our example tx https://explorer.x-cash.org/Transaction?data=7ecd79d7ead6c2f23cb404409aca01f8c9e30d7b07bcd4e9332a1c4872d1dd93
we can see we still have the mixins, meaning you cant see from which input I spent or received the actual XCASH from.






I have also included all of the pictures I took for this post at https://imgur.com/a/iWm2iVQ
you can also look at the 2 pictures for decoding and verifying a tx in the CLI wallet, to show that our explorer is accurate.



I hope this clarifies public tx at least the purpose, privacy, use case, and mechanics of them.

I agree with the forum vs social media stuff, I used to only use reddit and BTC talk for information, that is why I try to keep things posted on here as well, because I know people only use this website for their information.

we just released 1.4.1!
https://github.com/X-CASH-official/X-CASH/releases/tag/1.4.1

its not mandatory but highly suggested you update

so we basically fixed the biggest issues in this release
fixed the unspents issue, meaning everyone should not get any TX not possible errors anymore, and it will be easier to send large amounts
this also should allow STEX to up their limit of 200K

we also fixed the remote node syncing issue as well
took about 20 seconds for me now on GUI wallet with remote node

also the legacy issue of older wallets saying ring size of 2 is too small in the CLI is fixed

If anyone needs any help with an issue ask one of us on discord/telegram or just post it here, I try to check BTC talk every day, but 1.4.1 should fix most issues for everyone



copy from discord @COO: X-CASH_Paul

"UPDATE 1.4.1:mega:
Hello @everyone
We have uploaded the update 1.4.1.
This release brings some minor fixes, notably increasing the transactions input capacity. This directly translates to the amount of XCASH you can send in one transaction, fixing an issue where users would have to process payments in multiple small payments.
Release note:
-    Changed the input limit on outgoing transactions
-    Fixed the ring size to 21 in the CLI;
-    Added 5 trusted remote nodes in the GUI (faster synchronization time)

This update is not mandatory but strongly recommended if you are trying to send large amounts to exchanges, or if you are mining with a small payment threshold

:warning:️The exchange’s wallets have been in maintenance on our demand. They have been given the update and will open soon. When they have updated, you will be able to withdraw more XCASH in one transaction:warning:️

Download: https://x-cash.org/downloads/
GitHub Release: https://github.com/X-CASH-official/X-CASH/releases/tag/1.4.1

Thank you for your understanding and support !"

please try a different node if using a remote node. The EU node is currently in service

Hi,
Your payment has been sent
https://explorer.x-cash.org/Transaction?data=3bf61fb642f306f1359157593affda360be82e44a0c5bd1c2f86e6d01578f470

Thank you for the feedback on the KYC process of the airdrop. Nothing is official yet, we just mentioned it was something we were looking into as a possible solution or part of a solution. We will let everyone know if changes like this will be occurring.

The exchanges do take some time to compile the wallet and rebuild and reset. All exchanges should support the fork because they should upgrade, thus any X-CASH you have on the exchanges should be on the right block chain.

its the IP system banning you
make sure your not on a vpn proxy
try a mobile phone if its still not working

make sure to use cryptonight_v8 as the algorithm in the pool.txt

Hi Everyone!

were forking to Cryptonight V8 (CNv2) at block 136000
its 6PM paris time and 6AM EST on Nov 6

Yes its going good. Were looking at Nov 6-7 launch since we need to give the pool operators the binaries 24 hours in advanced, so were not the only pool that works right after the fork, since the proof of work algorithm is changing.

also for any one that is running a pool, please join our discord and we can make you a pool op
yesterday I posted how to upgrade the pool to be compatible with CNv2 as well as how to enable your pool to be able to send out the new public tx in this fork.

our pool will support users choice, which means every user has the choice if they want their pool payments to be public or private (by default their private of course)
this was people mining to a paper wallet will be able to check their pool payments by address in the explorer

Yes were going to upgrade soon, Guilhem will have more info shortly!






their is no installation, you just run
./xcashd
then
./xcash-wallet-cli

or double click on the X-CASH_GUI file








no, try running the GUI as admin this is the number one reason why it gets stuck on windows at the syncing progress bar page

Yes make sure if using windows GUI you run it as admin. this is the number one reason why it will say syncing and just sit their showing no progress

here is our proposed solution to the problem
https://medium.com/x-cash/preventing-nicehash-pumps-911f9ee78637

we setup testing today (creating private testnet and private pool for the testnet)
tomorrow we are going to start testing the solutions and see what settings react best with our coin

we will update in a day or two how its going
I am logging the data points for all test, so I think at the end of this we can display a chart of a simulated nicehash pump to show the difference of how the old algo reacts vs the new implementation for a visual representation of the fix

in the article we also briefly mention what our next hard fork in a few weeks will bring
Guilhem will post another article in a few days explaining more on the public TX that were building and the other points to this release

I will probably write one in depth article on the public TX a few days before launch

Hi Everyone I just wanted to keep this forum updated since I know some people dont have time to stop by telegram or discord.

we had a meeting today about the hashrate and I believe we have come up with a solution.
I implemented it today into the code, and tomorrow were going to have another meeting on it and then compile and run on the testnet and start testing the code to see how it reacts.
after tomorrows meeting Guilhem is going to create an article on what our plan is and when we plan on actually implementing it on the main net