[ANN] xCash : First Coin Feat. 100% Stealth Anon - NEW xChange P2P OTC

[Lyricz]

only 3 day remain,.... dev..come on.

[Jonesd]

only 3 day remain,.... dev..come on.

Three days?

[lab rat hoax]

I apologize, I got held up with work to pay the bills , so its hard to get on here, but I'm still interested in this coin or the new version of it anyways.

There are a few things that are going to need to be made clear in regards to the current xCash holders.  Integrating the old coin value into the new coin I plan on attempting will be difficult if I attempt to do it directly.  By directly I mean, add into the code special conditions to look at the existing xCash online database and transfer etc...  Therefore, we'll have to come to some community assessment for how we plan to transfer xCash holders to the new coin.  I do have a few ideas for how it could be done.

Since the amount of major xCash holders is so small this should not be too difficult to do.

Possible Ideas

1.) We put the xCash funds into an address online that is public and visible for xCash holders currently.  I can then hardcode an equivalent amount of currency to preexisting addresses in the blockchain of the new coin I create.  As long as this is public knowledge which funds are going to what addresses and we are open about that here I think it will be okay for the coin just starting out.

Pros

• Very easy to transfer funds
• Proof you will receive funds within the blockchain of the new coin

Cons

• Requires trust that I will integrate into the new coin

This is the first idea I have so far, I'll put more as I think of them, but I want to do something to reward the current holders of xCash and transfer them over as best as possible.

sounds good x11joe, i have no reason not to trust you....thank you

[Lyricz]

only 3 day remain,.... dev..come on.

Three days?

Bittex wil delete their XCash-Wallt on April 1th,...so the dev should give us an adress to save the coins.

[Jonesd]

only 3 day remain,.... dev..come on.

Three days?

Bittex wil delete their XCash-Wallt on April 1th,...so the dev should give us an adress to save the coins.

If you just read one page back, you can read an instruction on how to create a normal wallet address:

You go to the debug console and type:

Code:

getnewaddress '' normal

[Lyricz]

Oh    thanks, don´t red it.

edit://

..works perfekt 

[Jonesd]

Oh    thanks, don´t red it.

edit://

..works perfekt 

Good to hear

[pille]

For those of you who don't want to setup a wallet to get your coins out of bittrex to cryptsy, I offer to transfer it:

1. (!) post amount, cryptsy address and (optional) donation amount/percentage here

2. send to OVER

3. receive amount -0.2 XCASH bittrex fee -donation on your cryptsy account

[Messwith]

Pille:

9885.65583584 xcash   / 885.65583584 for U
cryptsy:
xr14VTRmbK7mW1e7uvWZx6GKwbZBxQ9Kqcg5D82GCqBLsXmzPCVGs6uUTjLKXpVwWHMpwg3D9hWxGuQ 55dCD26n9pRg9xJicsrXm7k

TY

[pille]

Pille:

9885.65583584 xcash   / 885.65583584 for U
cryptsy:
xr14VTRmbK7mW1e7uvWZx6GKwbZBxQ9Kqcg5D82GCqBLsXmzPCVGs6uUTjLKXpVwWHMpwg3D9hWxGuQ 55dCD26n9pRg9xJicsrXm7k

TY

http://xcash.blockexplorer.cc/tx/64edf1b1daee579231c88c453ea7c64b489582c62d6553aec6ef0f3a2470655f#i0
 

Edit: hm I still dont see my last deposit on cryptsy. I hope you've got yours?

[Messwith]

Pille : I've got mine. Thank You for your help

[torshammer]

Hi Pille

I am getting invalid address message from bittrex trying to transfer to cryptsy, is your method a workaround for this ...? 

Pille:

9885.65583584 xcash   / 885.65583584 for U
cryptsy:
xr14VTRmbK7mW1e7uvWZx6GKwbZBxQ9Kqcg5D82GCqBLsXmzPCVGs6uUTjLKXpVwWHMpwg3D9hWxGuQ 55dCD26n9pRg9xJicsrXm7k

TY

http://xcash.blockexplorer.cc/tx/64edf1b1daee579231c88c453ea7c64b489582c62d6553aec6ef0f3a2470655f#i0
 

Edit: hm I still dont see my last deposit on cryptsy. I hope you've got yours?

[pille]

yes because my address is "normal", cryptsy has this long stealth addresses. At the moment I have problems receiving xcash to my cryptsy at all, for hours now. I hope its only a bug with them. You can save coins to my address anyway but I will send them out later, when cryptsy is ok again.

[torshammer]

yes because my address is "normal", cryptsy has this long stealth addresses. At the moment I have problems receiving xcash to my cryptsy at all, for hours now. I hope its only a bug with them. You can save coins to my address anyway but I will send them out later, when cryptsy is ok again.

Ok thx. Will send you a pm.

[socoban]

I apologize, I got held up with work to pay the bills , so its hard to get on here, but I'm still interested in this coin or the new version of it anyways.

There are a few things that are going to need to be made clear in regards to the current xCash holders.  Integrating the old coin value into the new coin I plan on attempting will be difficult if I attempt to do it directly.  By directly I mean, add into the code special conditions to look at the existing xCash online database and transfer etc...  Therefore, we'll have to come to some community assessment for how we plan to transfer xCash holders to the new coin.  I do have a few ideas for how it could be done.

Since the amount of major xCash holders is so small this should not be too difficult to do.

Possible Ideas

1.) We put the xCash funds into an address online that is public and visible for xCash holders currently.  I can then hardcode an equivalent amount of currency to preexisting addresses in the blockchain of the new coin I create.  As long as this is public knowledge which funds are going to what addresses and we are open about that here I think it will be okay for the coin just starting out.

Pros

• Very easy to transfer funds
• Proof you will receive funds within the blockchain of the new coin

Cons

• Requires trust that I will integrate into the new coin

This is the first idea I have so far, I'll put more as I think of them, but I want to do something to reward the current holders of xCash and transfer them over as best as possible.

Why do you want to create new coin? What is wrong with XCash? Is there some serious bug? If no, than why to destroy such a nice coin. If yes, what kind of bug requires such dramatic changes?

[x11joe]

It's not a bug, its about understanding the codebase in a way that makes sense.  The xCash codebase is organized like spaghetti code with a mishmash of different solutions that were coded for problems, ESPECIALLY in regards to the database.  There is 2 separate databases to track currency value when really there should be only 1. One uses BerklyDB the other LevelDB, 2 separate hash table database engines.  BerklyDB was the original, and LevelDB was supposed to better faster, but had problems on Mac with corruption etc...  So the programmers who did this initially half finished the conversion of the code for BerklyDB and left the other half LevelDB, leaving a huge mess to clean up.

So doing it the way I proposed will be less prone to errors and more secure long term.  Hope this clears some things up.

Note::

My solution is going to use an SQL table, which is slower if the ledger kept growing... HOWEVER... since I plan to have a limited ledger it will wind up being faster overall long-term and easier to maintain and understand.  Probably will use SQLite.

[socoban]

It's not a bug, its about understanding the codebase in a way that makes sense.  The xCash codebase is organized like spaghetti code with a mishmash of different solutions that were coded for problems, ESPECIALLY in regards to the database.  There is 2 separate databases to track currency value when really there should be only 1. One uses BerklyDB the other LevelDB, 2 separate hash table database engines.  BerklyDB was the original, and LevelDB was supposed to better faster, but had problems on Mac with corruption etc...  So the programmers who did this initially half finished the conversion of the code for BerklyDB and left the other half LevelDB, leaving a huge mess to clean up.

So doing it the way I proposed will be less prone to errors and more secure long term.  Hope this clears some things up.

Note::

My solution is going to use an SQL table, which is slower if the ledger kept growing... HOWEVER... since I plan to have a limited ledger it will wind up being faster overall long-term and easier to maintain and understand.  Probably will use SQLite.

Did you discuss this code change with cryptsy? Will it be possible to change wallet and all balances? Will cryptsy agree to that changes? If they agree, than simplest solution will be if everyone load their coins to cryptsy, they are trusted authority. Than wallet can be changed and people can withdraw from them to new wallet. In that case, they can have everything in 1 wallet and it will be simple to do the change.

[pille]

I'm now in the 2nd level of tech support of cryptsy for my deposit problem Unfortunatly I cannot double check again if I sent my coins to the correct stealth address, because its not displayed on blockexplorer or in my wallet transactionlist (xcashd). Is there another opportunity to see the stealth address again where its been sent?

[torshammer]

It's not a bug, its about understanding the codebase in a way that makes sense.  The xCash codebase is organized like spaghetti code with a mishmash of different solutions that were coded for problems, ESPECIALLY in regards to the database.  There is 2 separate databases to track currency value when really there should be only 1. One uses BerklyDB the other LevelDB, 2 separate hash table database engines.  BerklyDB was the original, and LevelDB was supposed to better faster, but had problems on Mac with corruption etc...  So the programmers who did this initially half finished the conversion of the code for BerklyDB and left the other half LevelDB, leaving a huge mess to clean up.

So doing it the way I proposed will be less prone to errors and more secure long term.  Hope this clears some things up.

Note::

My solution is going to use an SQL table, which is slower if the ledger kept growing... HOWEVER... since I plan to have a limited ledger it will wind up being faster overall long-term and easier to maintain and understand.  Probably will use SQLite.

Good plan. We are with ya bud.

[torshammer]

I'm now in the 2nd level of tech support of cryptsy for my deposit problem Unfortunatly I cannot double check again if I sent my coins to the correct stealth address, because its not displayed on blockexplorer or in my wallet transactionlist (xcashd). Is there another opportunity to see the stealth address again where its been sent?

I spent a couple weeks at second level with no real response. Eventually I got my issue solved by politely flagging down a mod in the chat. You might even get an answer on the stealth issue that leads to a mod getting involved. Worth a try if your ticket gets hung up.