Topic: [XC][XCurrency] Decentralised Trustless Privacy Platform / Encrypted XChat / Pos - page 414. (Read 1484248 times)

Your statement says Jasin was never a developer.

Your PR person says Jasin was never a developer.

Dan is saying Jasin was a developer.

Jasin was a developer until I blew the whistle.

Dan is now trying to say Jasin stepped down on his own merit.


HELLO PEOPLE?!

Your statement says Jasin was never a developer.

Your PR person says Jasin was never a developer.

Dan is saying Jasin was a developer.

Jasin was a developer until I blew the whistle.

Dan is now trying to say Jasin stepped down on his own merit.


HELLO PEOPLE?!

Do you have any link confirming this?

Fibonacci is my company, we sponsored the conference and paid for the xc booth and tickets

Great, now as you promised, 1 hour for questions:

Why was Jasinlee listed as a developer on your website and then removed less than an hour after I contacted Dan and Arlyn with all this info about the Fibonacci project. You can't keep beating around this bush.

Great, now as you promised, 1 hour for questions:

Why was Jasinlee listed as a developer on your website and then removed less than an hour after I contacted Dan and Arlyn with all this info about the Fibonacci project. You can't keep beating around this bush.

That is a worry if it is true, considering his company was the major sponsor of the bitcoin beltway conference. When was the money paid to Jasin?

have you ever been on Poloniex? the whole chatroom is an XC pump

It irks me that his reviews are essentially being used as a pump device for other coins at this point.

Well if you want to get in before the news spreads too much.  LXC has also asked Dan to review Librexcoin.  He agreed under the conditions of compensation for his time.   If his reviews do pump every other coin, then you best get in on LXC soon before the word gets out

XCHAT HOW TO:


Hey all,

So, I have searched everywhere to try to find a “How to” for using XChat and after searching for quite some time I could not find one.  Therefore, in wanting to test this out, I have decided to write my own.  Hoping this is as ID10T proof as possible, and I hope this helps!  I am donating this to the community.  Feel free to copy, use, edit, etc.  Please feel free to comment or give corrections if I am in error on anything.  Thanks!

Donations Accepted:XaAAJU1DXTmu89GYbC34LhGe7rDw9qmr6Q

HOW TO USE XCURRENCY XCHAT

1.  Create new wallet address.  Because XChat is currently in beta, I highly suggest creating a new wallet address for any testing purposes.  First, make sure your existing wallet.dat is backed up.  To locate your wallet, for Windows users, go into Windows Explorer and type in %appdata% in the address bar and press Enter.  Double-click on directory labeled XCurrency.  Locate wallet.dat within that directory and rename to something like walletbackup.dat

2.  Start the XC App.  If you have just renamed your wallet.dat as stated in step 1, a new address will be automatically created.  For additional privacy (to prevent someone from somehow stealing your new wallet.dat file and sending message pretending to be from you, I suggesst you encrypt this new wallet with a password.

3.  Label your XC address as XChat.
Explanation:  Within XC App, click on tab “Receive Coins”.  This will show your XC address in the right-hand column.  Double-click the box in the column to the left of that address, under “Label”, and change it to to “XChat” (exclude quotes).

4.  Now, within XC App, click on tab “XChat.”
You should now see three rows labeled:  “my”, “remote”, and “key”.
Within XChat tab:  my = your XC address, remote = recipient's XC address, key = recipient's public key

Explanation:
In the column to the right of “my” should be your XC address that you previously labeled XChat.  If it is not there, click on the little address book icon on the right to auto-fill it.
In the column to the right of “remote” you should input the XC address for the recipient (i.e. person whom you are trying to send an XChat message to).
In the column to the right of “key” you need to input the public key for the recipient's address.

5.  Give it shot!  Type in a message and click “Send”! Keep in mind that if you want your recipient to be able to reply, they will also need your public key.  In other words, you will have to send it to them within the message, or give it to them in some other way.

Locating your public key: You can locate your public key within XC App → “Receive Coins” tab → right-click your XC address → “Copy public key”.

Hope this helps.  If you would like to test it out with me, feel free to send me a message.

My address:XGWQvHzpH7owVeVPZPKTRuff4LyW1Sg4KG
My public key:bcDH7uctqSpD8PPtYpWxArARyw1VFvdkT6edB5jFKibP

P.S.  Remember to send me your public key so I can reply!

Wasn't the agreement with the community to announce other code reviews made by dan in this thread before the review?

I had issues with btc-e when there was the huge dds attack in january/feb and had 10 btc withdrawn from my account
but the transfer never appeared on the blockchain. There we at least 10 of us in that position and the support is very slow -
but they do get round to it eventually.

Here is a link to that issue - you see that eventually they came good for us all so don't worry.

http://www.reddit.com/r/Bitcoin/comments/1y7con/btce_not_sending_bitcoins_after_one_week_be/

The other thing you can do is to post a reply on

https://bitcointalksearch.org/topic/btc-ecom-exchange-btcnmcltcnvctrcppcftcxpm-usdeurrur-fee-02-433283

If you can google translate it into russian it seems to work faster - (I usually did an english and russian version
in the same message). Also you can keep submitting tickets - my first one was never looked at but the second one
suddenly worked.

You can pm me if you need more advice -


 

Jesus DAN is the master of pumping every other coin but his.....

https://bitcointalksearch.org/topic/m.8713122


Edit: DO not LIST for SUPERNET!!!! SHIT IS SCAM CENTRAL

Have to admit - I laughed out loud

Jesus DAN is the master of pumping every other coin but his.....