Ethereum is becoming Blocknet-enabled!
http://cointelegraph.com/news/114228/blocknet-adding-ethereum-to-suite-of-supported-currencies
Topic: [ANN] xCash : First Coin Feat. 100% Stealth Anon - NEW xChange P2P OTC - page 3. (Read 141943 times)
May 12, 2015, 01:25:39 PM
Ethereum is becoming Blocknet-enabled!
http://cointelegraph.com/news/114228/blocknet-adding-ethereum-to-suite-of-supported-currencies
May 06, 2015, 01:21:32 PM
Just wanted to give a status update.
I have been busy with work lately, so I have not had a chance to update anything as of yet. I apologize, and don't want to make any promises or deadlines, but I can say that I have not forgotten this project and will be working on it as soon as I can.
Since I am creating an engine from scratch though, I'm not going to be able to easily give this to an exchange anytime soon, this is going to be a very long term project. I would like to discuss some of the ideas with you all though as I work on this.
To recap:
I will be using C++ and probably the Boost Libraries for networking support as my dependencies, same as every other bitcoin client. I will be using an HTML/CSS Interface for the UI so it will easily work on all operating systems and browsers and allow for customizable design and other nifty features.
The major difference will be an attempt to write code that is easily understandable and easy to work with, and who better to consult this with then the people here on the forum as I write the code. I also plan to use SQLite for the database (although slower to query records its much easier to understand and better documented in my opinion). Also, it won't be as bad since I plan to have a limited ledger that won't grow to ridiculous sizes as time goes on. As such this will be a public work in progress.
I have not decided on Proof of Work or Proof of Stake, or something like Proof of Resource, but I'm open to suggestions. My hope is that the energy used in proving the block can be used for something useful instead of just burning electricity, or if I can at least minimize it as is the case with proof of stake.
My only concern is copy cats running away with the code and creating a clone coin which would undermine my efforts. Any suggestions to protect the source code while we work on this?
I have been busy with work lately, so I have not had a chance to update anything as of yet. I apologize, and don't want to make any promises or deadlines, but I can say that I have not forgotten this project and will be working on it as soon as I can.
Since I am creating an engine from scratch though, I'm not going to be able to easily give this to an exchange anytime soon, this is going to be a very long term project. I would like to discuss some of the ideas with you all though as I work on this.
To recap:
I will be using C++ and probably the Boost Libraries for networking support as my dependencies, same as every other bitcoin client. I will be using an HTML/CSS Interface for the UI so it will easily work on all operating systems and browsers and allow for customizable design and other nifty features.
The major difference will be an attempt to write code that is easily understandable and easy to work with, and who better to consult this with then the people here on the forum as I write the code. I also plan to use SQLite for the database (although slower to query records its much easier to understand and better documented in my opinion). Also, it won't be as bad since I plan to have a limited ledger that won't grow to ridiculous sizes as time goes on. As such this will be a public work in progress.
I have not decided on Proof of Work or Proof of Stake, or something like Proof of Resource, but I'm open to suggestions. My hope is that the energy used in proving the block can be used for something useful instead of just burning electricity, or if I can at least minimize it as is the case with proof of stake.
My only concern is copy cats running away with the code and creating a clone coin which would undermine my efforts. Any suggestions to protect the source code while we work on this?
May 06, 2015, 04:41:27 AM
Hi x11joe
Rumor has it that a certain exchange - one of the last hosting xcash - might be headed for the exits very soon for not following state rules. For those of us who have hung in there waiting, is it possible for you to set up some kind of a wallet for storing Xcash while waiting for your new project? Seeing as how wallets don't work anymore etc.
thx
Rumor has it that a certain exchange - one of the last hosting xcash - might be headed for the exits very soon for not following state rules. For those of us who have hung in there waiting, is it possible for you to set up some kind of a wallet for storing Xcash while waiting for your new project? Seeing as how wallets don't work anymore etc.
thx
I can store your xcash while waiting. I give you an adress in my wallet. You can send your xcash and get a screenshot of them. I get 5% of stored coins for this service.
May 05, 2015, 06:07:22 AM
Hi x11joe
Rumor has it that a certain exchange - one of the last hosting xcash - might be headed for the exits very soon for not following state rules. For those of us who have hung in there waiting, is it possible for you to set up some kind of a wallet for storing Xcash while waiting for your new project? Seeing as how wallets don't work anymore etc.
thx
Rumor has it that a certain exchange - one of the last hosting xcash - might be headed for the exits very soon for not following state rules. For those of us who have hung in there waiting, is it possible for you to set up some kind of a wallet for storing Xcash while waiting for your new project? Seeing as how wallets don't work anymore etc.
thx
I can store your xcash while waiting. I give you an adress in my wallet. You can send your xcash and get a screenshot of them. I get 5% of stored coins for this service.
May 02, 2015, 11:44:24 AM
Hi x11joe
Rumor has it that a certain exchange - one of the last hosting xcash - might be headed for the exits very soon for not following state rules. For those of us who have hung in there waiting, is it possible for you to set up some kind of a wallet for storing Xcash while waiting for your new project? Seeing as how wallets don't work anymore etc.
thx
Rumor has it that a certain exchange - one of the last hosting xcash - might be headed for the exits very soon for not following state rules. For those of us who have hung in there waiting, is it possible for you to set up some kind of a wallet for storing Xcash while waiting for your new project? Seeing as how wallets don't work anymore etc.
thx
April 21, 2015, 11:46:33 AM
Update::
I've been busy with my business this week. I will be down for 2 weeks while I take care of business emergencies, I will update once I'm done. Need to pay the bills
.
I'm still working on this and will give a more serious update as soon as I can. I'm aiming for end of April at this point. This is going to be a very long term project.
I do know that I've decided to use C++ and go with a browser UI & SqLite for now, just need to put together a little demo starter app ASAP and then finish my diagrams/plan.
Ok thanks, how long term, months/years? I've been busy with my business this week. I will be down for 2 weeks while I take care of business emergencies, I will update once I'm done. Need to pay the bills
.I'm still working on this and will give a more serious update as soon as I can. I'm aiming for end of April at this point. This is going to be a very long term project.
I do know that I've decided to use C++ and go with a browser UI & SqLite for now, just need to put together a little demo starter app ASAP and then finish my diagrams/plan.
April 17, 2015, 07:07:20 AM
Update::
I've been busy with my business this week. I will be down for 2 weeks while I take care of business emergencies, I will update once I'm done. Need to pay the bills.
I'm still working on this and will give a more serious update as soon as I can. I'm aiming for end of April at this point. This is going to be a very long term project.
I do know that I've decided to use C++ and go with a browser UI & SqLite for now, just need to put together a little demo starter app ASAP and then finish my diagrams/plan.
I've been busy with my business this week. I will be down for 2 weeks while I take care of business emergencies, I will update once I'm done. Need to pay the bills
.I'm still working on this and will give a more serious update as soon as I can. I'm aiming for end of April at this point. This is going to be a very long term project.
I do know that I've decided to use C++ and go with a browser UI & SqLite for now, just need to put together a little demo starter app ASAP and then finish my diagrams/plan.
April 17, 2015, 06:51:13 AM
I seem to be unable to use the non-stealth address I made to get my coins from Bittrex and cannot get those coins. Anybody else has this issue?
April 17, 2015, 06:13:55 AM
Updates?
April 03, 2015, 06:19:25 AM
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.
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.
Thx for information x11joe. Good to see sth is goin on...
April 02, 2015, 05:38:47 PM
hey joe !
https://www.youtube.com/watch?v=DpkDdLZGg30
so hey joe, will the new xcash still have about 2 1/2 million coins at 5% stake ?
thanks
https://www.youtube.com/watch?v=DpkDdLZGg30
so hey joe, will the new xcash still have about 2 1/2 million coins at 5% stake ?
thanks
April 01, 2015, 03:14:36 PM
I'm not putting anything on Craptsy. Is the new coin keeping the name?
If new coin will be created using same balances like old coin, than there must be either technical possibility to continue with old blockchain or old coins have to be moved to trusted authority and then redistributed. Every exchange which trades XCASH now, is automatically suitable for that. They will simply swith their old wallets in cooperation with dev to new wallets. Without that, you can't do it. If it is technically impossible to use old blockchain, than new coin should have new name and old cash should be kept as is now. If the only reason to such changes is heavy client with 2 db running, and wallet is working fine, than I don't see it as a good enough reason to kill old coin. XCASH is on Crypty. Cryptsy stopped to add new coins. Beeing on cryptsy is question of existance. Any new coin will fail if it does not hit Cryptsy. I prefer old XCASH with heavy client and complicated development than cool new coin without future. If Cryptsy does not cooperate and does not agree to switch their wallet to new one with keeping users balances, than I don't see any future for new coin.
March 31, 2015, 07:11:00 PM
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?
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.
Sent PM. In hope.
March 31, 2015, 10:35:30 AM
I'm not putting anything on Craptsy. Is the new coin keeping the name?
March 31, 2015, 06:34:40 AM
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?
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.
March 31, 2015, 06:31:55 AM
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.
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.
March 31, 2015, 05:38:55 AM
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?
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? March 31, 2015, 04:26:38 AM
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.
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.
March 31, 2015, 03:20:23 AM
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.
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.
March 30, 2015, 03:09:36 PM
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
Cons
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.
, 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?
Jump to: