### CWI-TRADE - EXCHANGE
Hi All ...
VERY important update here - https://bitcointalksearch.org/topic/m.48783659
#crysx
Topic: ### A ChainWorks Industries (CWI) Project - OzzieCoin | OZC - page 2. (Read 27842 times)
### CWI-COINS - OZZIECOIN
Hi All ...
Just to let you all know that we are working tirelessly to bring the next version of the OZC code to being. In the meantime, we have removed the links from the OP, and change it somewhat to reflect this. OZC itself has changed, and due to the latest issues we have been notified with, are making a few more changes to the CodeBase so that these issues are kept to a minimal.
So bear with us as we move towards these changes this coming week, and we will release the new code and wallets as soon as we have fully tested them.
Thanks for your patience. Cryptopia will be notified in the coming days also.
#crysx
Hi All ...
Just to let you all know that we are working tirelessly to bring the next version of the OZC code to being. In the meantime, we have removed the links from the OP, and change it somewhat to reflect this. OZC itself has changed, and due to the latest issues we have been notified with, are making a few more changes to the CodeBase so that these issues are kept to a minimal.
So bear with us as we move towards these changes this coming week, and we will release the new code and wallets as soon as we have fully tested them.
Thanks for your patience. Cryptopia will be notified in the coming days also.
#crysx
Crysx, please help.
I have OZC and need to transfer it off the exchange. I downloaded the 17 RC2 wallet from your website (i'm not familiar with wallets on PC, I normally send to exchanges). It's telling me that I need to download 4 years worth of blockchain ?? How do I stop this! I just want to be able to send the coins to somewhere safe. Can I use public and private keys ? A generator of some kind? Please let me know some legitimate examples.
I have OZC and need to transfer it off the exchange. I downloaded the 17 RC2 wallet from your website (i'm not familiar with wallets on PC, I normally send to exchanges). It's telling me that I need to download 4 years worth of blockchain ?? How do I stop this! I just want to be able to send the coins to somewhere safe. Can I use public and private keys ? A generator of some kind? Please let me know some legitimate examples.
download link is dead..
Which link is that? ...
And where please? We will fix as soon as possible.
#crysx
Thank you, it is working now. Is V0.17.99.0 what I have ( Ozziecoin version v0.17.0.99-14161d50f (64-bit)) - V0.17.99.0 vs v0.17.0.99
Glad it worked out ...
As for the version info - that is obviously a typo no one seemed to notice at the time.
We will fix this when we HardFork OZC to the new Algo soon.
#crysx
download link is dead..
Thank you, it is working now. Is V0.17.99.0 what I have ( Ozziecoin version v0.17.0.99-14161d50f (64-bit)) - V0.17.99.0 vs v0.17.0.99
I install wallet Ozziecoin version v0.17.0.99-14161d50f (64-bit), but I have 0 active connections, should I add any nodes ?
Yes ...
- Locate the (or create if you don't have one) the ozziecoin.conf file (I am unsure where it is located in Windows if you have it)
- Close the wallet if you have it running.
- Go to this link - https://chainz.cryptoid.info/ozc/#!network - and click on the 'node list' button where /CWI_OZC:0.17.99/ is located.
- Copy and paste these node listings (no matter how many) to the ozziecoin.conf file.
- Save the ozzeicoin.conf file.
- Restart your wallet and wait till the wallet finds an active peer.
The alternative is ...
- Run the wallet .
- Click on the 'Help' Menu Item.
- Click on 'Debug Window'
- When the 'Debug Window' opens, click on the 'Console' Tab.
- At the bottom there is a Navigation/Input Pane where you should punch in the node addresses from the Block Explorer, except in this form below -
Code:
addnode 108.170.1.134 add
- Continue doing this until you have entered at least three nodes.
- Close the 'Debug Window' and wait until the wallets finds an active peer.
Syncing should start from there.
If syncing does not start, then there is another issue you need to look at, whether it be a firewall port exception, or opening the P2P port in the Modem/Router you are using. This is beyond the scope of this post as each have different settings.
Currently, below is the listings of nodes in my currently active wallet.
Code:
[
{
"id": 0,
"addr": "159.148.186.132:39042",
"addrlocal": "49.176.248.102:41874",
"addrbind": "192.168.0.71:41874",
"services": "000000000000040d",
"relaytxes": true,
"lastsend": 1544597556,
"lastrecv": 1544597635,
"bytessent": 85988,
"bytesrecv": 514160,
"conntime": 1544442813,
"timeoffset": 0,
"pingtime": 0.40021,
"minping": 0.396583,
"version": 70015,
"subver": "/CWI_OZC:0.17.99/",
"inbound": false,
"addnode": false,
"startingheight": 847602,
"banscore": 0,
"synced_headers": 848632,
"synced_blocks": 848632,
"inflight": [
],
"whitelisted": false,
"minfeefilter": 0.00000000,
"bytessent_per_msg": {
"addr": 110,
"feefilter": 32,
"getaddr": 24,
"getdata": 1098,
"getheaders": 1053,
"headers": 530,
"inv": 305,
"ping": 41280,
"pong": 41280,
"sendcmpct": 99,
"sendheaders": 24,
"verack": 24,
"version": 129
},
"bytesrecv_per_msg": {
"addr": 1520,
"cmpctblock": 320184,
"getheaders": 1053,
"headers": 212,
"inv": 1159,
"ping": 41280,
"pong": 41280,
"sendcmpct": 66,
"sendheaders": 24,
"tx": 107231,
"verack": 24,
"version": 127
}
},
{
"id": 1,
"addr": "188.165.39.224:39042",
"addrlocal": "49.176.248.102:50946",
"addrbind": "192.168.0.71:50946",
"services": "0000000000000003",
"relaytxes": true,
"lastsend": 1544597635,
"lastrecv": 1544597636,
"bytessent": 121111,
"bytesrecv": 1183671,
"conntime": 1544442814,
"timeoffset": 0,
"pingtime": 0.455879,
"minping": 0.367661,
"version": 70004,
"subver": "/Satoshi:0.9.1.4/",
"inbound": false,
"addnode": false,
"startingheight": 847602,
"banscore": 0,
"synced_headers": 848632,
"synced_blocks": 847602,
"inflight": [
],
"whitelisted": false,
"minfeefilter": 0.00000000,
"bytessent_per_msg": {
"addr": 165,
"alert": 192,
"getaddr": 24,
"getheaders": 1053,
"inv": 64355,
"ping": 41280,
"tx": 13889,
"verack": 24,
"version": 129
},
"bytesrecv_per_msg": {
"addr": 14042,
"getblocks": 1077219,
"getdata": 427,
"headers": 106,
"inv": 50447,
"pong": 41280,
"verack": 24,
"version": 126
}
},
{
"id": 3,
"addr": "5.196.117.40:39042",
"addrlocal": "49.176.248.102:55836",
"addrbind": "192.168.0.71:55836",
"services": "000000000000040d",
"relaytxes": true,
"lastsend": 1544597569,
"lastrecv": 1544597635,
"bytessent": 106044,
"bytesrecv": 248207,
"conntime": 1544442831,
"timeoffset": -1,
"pingtime": 0.372827,
"minping": 0.369817,
"version": 70015,
"subver": "/SatOzzie:0.17.99/",
"inbound": false,
"addnode": false,
"startingheight": 847602,
"banscore": 0,
"synced_headers": 848632,
"synced_blocks": 848632,
"inflight": [
],
"whitelisted": false,
"minfeefilter": 0.00000010,
"bytessent_per_msg": {
"addr": 55,
"feefilter": 32,
"getaddr": 24,
"getdata": 5551,
"getheaders": 1053,
"headers": 15794,
"inv": 732,
"ping": 41280,
"pong": 41280,
"sendcmpct": 66,
"sendheaders": 24,
"verack": 24,
"version": 129
},
"bytesrecv_per_msg": {
"addr": 2385,
"cmpctblock": 27074,
"feefilter": 32,
"getheaders": 1053,
"headers": 108862,
"inv": 732,
"ping": 41280,
"pong": 41280,
"sendcmpct": 66,
"sendheaders": 24,
"tx": 25267,
"verack": 24,
"version": 128
}
},
{
"id": 256,
"addr": "178.128.56.201",
"addrlocal": "49.176.248.102:58698",
"addrbind": "192.168.0.71:58698",
"services": "000000000000040d",
"relaytxes": true,
"lastsend": 1544597635,
"lastrecv": 1544597635,
"bytessent": 79694,
"bytesrecv": 136174,
"conntime": 1544532733,
"timeoffset": 0,
"pingtime": 0.325885,
"minping": 0.323263,
"version": 70015,
"subver": "/CWI_OZC:0.17.99/",
"inbound": false,
"addnode": true,
"startingheight": 848201,
"banscore": 0,
"synced_headers": 848632,
"synced_blocks": 848632,
"inflight": [
],
"whitelisted": false,
"minfeefilter": 0.00000010,
"bytessent_per_msg": {
"addr": 55,
"feefilter": 32,
"getaddr": 24,
"getdata": 183,
"getheaders": 1053,
"headers": 43142,
"inv": 305,
"ping": 17312,
"pong": 17312,
"sendcmpct": 99,
"sendheaders": 24,
"verack": 24,
"version": 129
},
"bytesrecv_per_msg": {
"addr": 740,
"cmpctblock": 61488,
"feefilter": 32,
"getheaders": 1053,
"headers": 24910,
"inv": 305,
"ping": 17312,
"pong": 17312,
"sendcmpct": 66,
"sendheaders": 24,
"tx": 12781,
"verack": 24,
"version": 127
}
}
]
{
"id": 0,
"addr": "159.148.186.132:39042",
"addrlocal": "49.176.248.102:41874",
"addrbind": "192.168.0.71:41874",
"services": "000000000000040d",
"relaytxes": true,
"lastsend": 1544597556,
"lastrecv": 1544597635,
"bytessent": 85988,
"bytesrecv": 514160,
"conntime": 1544442813,
"timeoffset": 0,
"pingtime": 0.40021,
"minping": 0.396583,
"version": 70015,
"subver": "/CWI_OZC:0.17.99/",
"inbound": false,
"addnode": false,
"startingheight": 847602,
"banscore": 0,
"synced_headers": 848632,
"synced_blocks": 848632,
"inflight": [
],
"whitelisted": false,
"minfeefilter": 0.00000000,
"bytessent_per_msg": {
"addr": 110,
"feefilter": 32,
"getaddr": 24,
"getdata": 1098,
"getheaders": 1053,
"headers": 530,
"inv": 305,
"ping": 41280,
"pong": 41280,
"sendcmpct": 99,
"sendheaders": 24,
"verack": 24,
"version": 129
},
"bytesrecv_per_msg": {
"addr": 1520,
"cmpctblock": 320184,
"getheaders": 1053,
"headers": 212,
"inv": 1159,
"ping": 41280,
"pong": 41280,
"sendcmpct": 66,
"sendheaders": 24,
"tx": 107231,
"verack": 24,
"version": 127
}
},
{
"id": 1,
"addr": "188.165.39.224:39042",
"addrlocal": "49.176.248.102:50946",
"addrbind": "192.168.0.71:50946",
"services": "0000000000000003",
"relaytxes": true,
"lastsend": 1544597635,
"lastrecv": 1544597636,
"bytessent": 121111,
"bytesrecv": 1183671,
"conntime": 1544442814,
"timeoffset": 0,
"pingtime": 0.455879,
"minping": 0.367661,
"version": 70004,
"subver": "/Satoshi:0.9.1.4/",
"inbound": false,
"addnode": false,
"startingheight": 847602,
"banscore": 0,
"synced_headers": 848632,
"synced_blocks": 847602,
"inflight": [
],
"whitelisted": false,
"minfeefilter": 0.00000000,
"bytessent_per_msg": {
"addr": 165,
"alert": 192,
"getaddr": 24,
"getheaders": 1053,
"inv": 64355,
"ping": 41280,
"tx": 13889,
"verack": 24,
"version": 129
},
"bytesrecv_per_msg": {
"addr": 14042,
"getblocks": 1077219,
"getdata": 427,
"headers": 106,
"inv": 50447,
"pong": 41280,
"verack": 24,
"version": 126
}
},
{
"id": 3,
"addr": "5.196.117.40:39042",
"addrlocal": "49.176.248.102:55836",
"addrbind": "192.168.0.71:55836",
"services": "000000000000040d",
"relaytxes": true,
"lastsend": 1544597569,
"lastrecv": 1544597635,
"bytessent": 106044,
"bytesrecv": 248207,
"conntime": 1544442831,
"timeoffset": -1,
"pingtime": 0.372827,
"minping": 0.369817,
"version": 70015,
"subver": "/SatOzzie:0.17.99/",
"inbound": false,
"addnode": false,
"startingheight": 847602,
"banscore": 0,
"synced_headers": 848632,
"synced_blocks": 848632,
"inflight": [
],
"whitelisted": false,
"minfeefilter": 0.00000010,
"bytessent_per_msg": {
"addr": 55,
"feefilter": 32,
"getaddr": 24,
"getdata": 5551,
"getheaders": 1053,
"headers": 15794,
"inv": 732,
"ping": 41280,
"pong": 41280,
"sendcmpct": 66,
"sendheaders": 24,
"verack": 24,
"version": 129
},
"bytesrecv_per_msg": {
"addr": 2385,
"cmpctblock": 27074,
"feefilter": 32,
"getheaders": 1053,
"headers": 108862,
"inv": 732,
"ping": 41280,
"pong": 41280,
"sendcmpct": 66,
"sendheaders": 24,
"tx": 25267,
"verack": 24,
"version": 128
}
},
{
"id": 256,
"addr": "178.128.56.201",
"addrlocal": "49.176.248.102:58698",
"addrbind": "192.168.0.71:58698",
"services": "000000000000040d",
"relaytxes": true,
"lastsend": 1544597635,
"lastrecv": 1544597635,
"bytessent": 79694,
"bytesrecv": 136174,
"conntime": 1544532733,
"timeoffset": 0,
"pingtime": 0.325885,
"minping": 0.323263,
"version": 70015,
"subver": "/CWI_OZC:0.17.99/",
"inbound": false,
"addnode": true,
"startingheight": 848201,
"banscore": 0,
"synced_headers": 848632,
"synced_blocks": 848632,
"inflight": [
],
"whitelisted": false,
"minfeefilter": 0.00000010,
"bytessent_per_msg": {
"addr": 55,
"feefilter": 32,
"getaddr": 24,
"getdata": 183,
"getheaders": 1053,
"headers": 43142,
"inv": 305,
"ping": 17312,
"pong": 17312,
"sendcmpct": 99,
"sendheaders": 24,
"verack": 24,
"version": 129
},
"bytesrecv_per_msg": {
"addr": 740,
"cmpctblock": 61488,
"feefilter": 32,
"getheaders": 1053,
"headers": 24910,
"inv": 305,
"ping": 17312,
"pong": 17312,
"sendcmpct": 66,
"sendheaders": 24,
"tx": 12781,
"verack": 24,
"version": 127
}
}
]
Hope this helps.
#crysx
I install wallet Ozziecoin version v0.17.0.99-14161d50f (64-bit), but I have 0 active connections, should I add any nodes ?
Hi, should we still stay on CRYPTOPIA or withdraw to Ozziecoin 0.17 Release Candidate 2 wallet ?
Move all coins ...
The links to the wallets have been provided, and when Cryptopia is ready to reopen the market for withdrawals, move ALL your coins contained in their wallet to your own personal wallet.
Make sure YOUR wallet is the latest 0.17RC2 wallet, otherwise after Cryptopia finish the update, you will not be able to withdraw. The BlockChain is already well past the V4 Block activation and SegWit activation, so there will be major issues if you try and transfer to an old wallet. Issues that will NOT be the fault of either Cryptopia, or CWI if you do not update.
If you have issues running the new wallets, please ask here, or join the Official CWI Discord Group and post in the coins/#ozziecoin-ozc channel.
Thanks.
#crysx
Hi, should we still stay on CRYPTOPIA or withdraw to Ozziecoin 0.17 Release Candidate 2 wallet ?
Please do NOT send anything out of Cryptopia ...
At least not until they have updated the wallet to the latest version, which is the latest basecode V0.17.99.0
Once they update, the new wallet should be fully functional on the newest network protocol version, and will have no issues with sending out your coins to your wallet, which should also be the new wallet version. Please do NOT use the old wallets, as this will become an issue with sending and receiving of OZC.
We do not know the reason why Cryptopia are delisting both OZC and INFX, but they have mentioned that this is something they do not take lightly. In the few years our coins have been on Cryptopia, we have have VERY little issue, if at all with the exchange, and the service behind the Exchange. In fact, cryptopia have been FAR better than the 'other' bigger Exchange, that treated us like nothing more than garbage when they got very big. At the very least we have been on Cryptopia for a few years now, with GRN, OZC and INFX, and so far remains one of the best exchanges we have experienced to date.
We shall continue to develop OZC further, and with the solid basecode that OZC will ultimately have, will rebase all our coins with that basecode.
Now we need to look for an exchange that will allow us to setup 'home' for our coins, and become the foundation for the growth of the developments coming in the year ahead. Especially the integration of all our coins into the Master Coin/Wallet that we have planned for next year.
So sit tight, Cryptopia will do their bit as they always have, and remove all your coins to the new wallets that you can download from github for Windows and OSX, and await the next Exchange we deem to be our new trade place.
Thanks.
#crysx
At least not until they have updated the wallet to the latest version, which is the latest basecode V0.17.99.0
Once they update, the new wallet should be fully functional on the newest network protocol version, and will have no issues with sending out your coins to your wallet, which should also be the new wallet version. Please do NOT use the old wallets, as this will become an issue with sending and receiving of OZC.
We do not know the reason why Cryptopia are delisting both OZC and INFX, but they have mentioned that this is something they do not take lightly. In the few years our coins have been on Cryptopia, we have have VERY little issue, if at all with the exchange, and the service behind the Exchange. In fact, cryptopia have been FAR better than the 'other' bigger Exchange, that treated us like nothing more than garbage when they got very big. At the very least we have been on Cryptopia for a few years now, with GRN, OZC and INFX, and so far remains one of the best exchanges we have experienced to date.
We shall continue to develop OZC further, and with the solid basecode that OZC will ultimately have, will rebase all our coins with that basecode.
Now we need to look for an exchange that will allow us to setup 'home' for our coins, and become the foundation for the growth of the developments coming in the year ahead. Especially the integration of all our coins into the Master Coin/Wallet that we have planned for next year.
So sit tight, Cryptopia will do their bit as they always have, and remove all your coins to the new wallets that you can download from github for Windows and OSX, and await the next Exchange we deem to be our new trade place.
Thanks.
#crysx
YoBit.Net is in the alternative exchange that is available for OZC, but depositing OZC to this exchange is not available now.
What is your plan for the next home exchange for OZC?
Is there any online wallet that we could keep our coins there safely?
Yobit is NOT an alternative exchange ...
PLEASE stay away from these scumbags. What you do with them is at your own risk.
Yobit themselves have no sense of honesty, respect, or business knowledge. They will do what it takes to rip off those people (and developers and development teams) as much as they can. We have not dealt with Yobit for a couple of years now for three main reasons.
1 - They are GREED focused and have no intention on helping ANYONE with wallet issues, unless it is paid for EVERY SINGLE TIME. Even then it takes them MONTHS before they bother.
2 - Backup service is ZERO. They do not respond to emails from official team members, and refuse to acknowledge any form of work and even if they did, takes a LONG time before they react. Cases in point - DRZ has now been 3Years, OZC has now been over 2Years, and INFX is also over 2Years, since requests (many at a time) have been forwarded to this pathetic excuse of an exchange.
3 - The Yobit team (I honestly believe there must be one or two people at most) refuse to act on work required on any of our coins, and CWI is not the only ones suffering and complaining about this lack of service and care.
So if you do decide to use Yobit, you are doing at your OWN risk, and believe me, at your own EXPENSE. You will lose out with this exchange.
We at CWI will categorically state, in no uncertain terms, that we will NOT endorse, nor factor in that this scumbag of a site, will be part of our advertising, commitment to professionalism and stability, nor will they be part of our discussion if we can help it (with certain times like this being the exception).
Please be patient and we will get our coins onto an exchange that is a damned site more reputable (which really isn't difficult when comparing to Yobit), and will start to trade when we have tested the new Exchange thoroughly. Patience is the key. Alternatively, you could join our Discord Group, and trade in our #trade channel as I update all new trades to the Pinned post on that channel regularly.
The day that Yobit cleans their act up, is the day that MOST of the Crypto Market will start to have respect anewed for them. Till then, avoid Yobit like the plague. You have been warned.
#crysx
,,,, Cryptopia are delisting this due to a possible SECURITY ISSUE of stealing bitcoins .?
please explain ?
please explain ?
Deleted ...
Your response is uncalled for and unfounded, based on garbage and the lack of knowledge of the project. We have been around for a LONG time and I will NEVER tolerate that sort of response from you or any one esle.
Respond in a civil manner, or go elsewhere to post the verbal diarrhea that you just spewed.
#crysx
.... the only verbal diarrhoea is off your fingers to your input device . you did say you were in Australia ?
have you heard of these guys .... https://www.acorn.gov.au/ ....
they watch people like you .
.....
ACORN - what a great company ...
Funny how we are not even on their radar don't you think, when you cry scam everywhere you go.
I have NO remorse for people like yourself that have absolutely NO IDEA about the history of a project, what has been created and what has not, what the core value of the team behind AND the company behind the projects are, and the PEOPLE behind that all. You direct your attack on my person? Then I challenge you to 'dig up dirt' by contacting ACORN and place a complaint. Let THEM do the research YOU are supposed to be doing, but so lazy to.
We have covered (in so many ways, and so many times) the process we acquired the project, what has happened (which is almost nothing up until a month ago), and what is happening to not only this project, but all the others we have in our project list. Your inherent lack of thought, and research acumen goes far beyond lazy. It touches on the realm of stupidity, such that it makes no sense that a veiled threat of the mention of ACORN would even move us (let alone me personally), a millimeter off our seats.
Yes, I am personally situated in Australia, as is the COMPANY you are referring to. ChainWorks Industries Pty Ltd. go ahead, look it up and see who I am and THEN go and complain to ACORN about us doing nothing but being transparent AND law abiding, under Australian jurisdiction. See how far you get with you incessant bleating of wrongdoing. It won't stick. We have been above board ALL the way here, in ALL we do and ALL we decide to do. Nothing underhanded and certainly not illegal, hence the reason the company was born.
Just because YOU are too damned lazy to research the project and coin, is of no consequence to me or us.
So please, go right ahead and place your complaints to ANY legal entity here in Australia. You will find at your cost and irreverence, that not only will you be wasting your time, but we are actually one of the SOLID entities in this CryptoIndustry that is wrought with scammers and thieves, and are here in Australia ... to stay!
#crysx
Please do NOT send anything out of Cryptopia ...
At least not until they have updated the wallet to the latest version, which is the latest basecode V0.17.99.0
Once they update, the new wallet should be fully functional on the newest network protocol version, and will have no issues with sending out your coins to your wallet, which should also be the new wallet version. Please do NOT use the old wallets, as this will become an issue with sending and receiving of OZC.
We do not know the reason why Cryptopia are delisting both OZC and INFX, but they have mentioned that this is something they do not take lightly. In the few years our coins have been on Cryptopia, we have have VERY little issue, if at all with the exchange, and the service behind the Exchange. In fact, cryptopia have been FAR better than the 'other' bigger Exchange, that treated us like nothing more than garbage when they got very big. At the very least we have been on Cryptopia for a few years now, with GRN, OZC and INFX, and so far remains one of the best exchanges we have experienced to date.
We shall continue to develop OZC further, and with the solid basecode that OZC will ultimately have, will rebase all our coins with that basecode.
Now we need to look for an exchange that will allow us to setup 'home' for our coins, and become the foundation for the growth of the developments coming in the year ahead. Especially the integration of all our coins into the Master Coin/Wallet that we have planned for next year.
So sit tight, Cryptopia will do their bit as they always have, and remove all your coins to the new wallets that you can download from github for Windows and OSX, and await the next Exchange we deem to be our new trade place.
Thanks.
#crysx
At least not until they have updated the wallet to the latest version, which is the latest basecode V0.17.99.0
Once they update, the new wallet should be fully functional on the newest network protocol version, and will have no issues with sending out your coins to your wallet, which should also be the new wallet version. Please do NOT use the old wallets, as this will become an issue with sending and receiving of OZC.
We do not know the reason why Cryptopia are delisting both OZC and INFX, but they have mentioned that this is something they do not take lightly. In the few years our coins have been on Cryptopia, we have have VERY little issue, if at all with the exchange, and the service behind the Exchange. In fact, cryptopia have been FAR better than the 'other' bigger Exchange, that treated us like nothing more than garbage when they got very big. At the very least we have been on Cryptopia for a few years now, with GRN, OZC and INFX, and so far remains one of the best exchanges we have experienced to date.
We shall continue to develop OZC further, and with the solid basecode that OZC will ultimately have, will rebase all our coins with that basecode.
Now we need to look for an exchange that will allow us to setup 'home' for our coins, and become the foundation for the growth of the developments coming in the year ahead. Especially the integration of all our coins into the Master Coin/Wallet that we have planned for next year.
So sit tight, Cryptopia will do their bit as they always have, and remove all your coins to the new wallets that you can download from github for Windows and OSX, and await the next Exchange we deem to be our new trade place.
Thanks.
#crysx
YoBit.Net is in the alternative exchange that is available for OZC, but depositing OZC to this exchange is not available now.
What is your plan for the next home exchange for OZC?
Is there any online wallet that we could keep our coins there safely?
,,,, Cryptopia are delisting this due to a possible SECURITY ISSUE of stealing bitcoins .?
please explain ?
please explain ?
Deleted ...
Your response is uncalled for and unfounded, based on garbage and the lack of knowledge of the project. We have been around for a LONG time and I will NEVER tolerate that sort of response from you or any one esle.
Respond in a civil manner, or go elsewhere to post the verbal diarrhea that you just spewed.
#crysx
.... the only verbal diarrhoea is off your fingers to your input device . you did say you were in Australia ?
have you heard of these guys .... https://www.acorn.gov.au/ ....
they watch people like you .
.....
### CWI-PYROXENE (theMINE) - MPOS BRANCH
Hi All ...
VERY important update here for the miners - https://bitcointalksearch.org/topic/m.48343202
#crysx
Hi All ...
VERY important update here for the miners - https://bitcointalksearch.org/topic/m.48343202
#crysx
,,,, Cryptopia are delisting this due to a possible SECURITY ISSUE of stealing bitcoins .?
please explain ?
please explain ?
Deleted ...
Your response is uncalled for and unfounded, based on garbage and the lack of knowledge of the project. We have been around for a LONG time and I will NEVER tolerate that sort of response from you or any one esle.
Respond in a civil manner, or go elsewhere to post the verbal diarrhea that you just spewed.
#crysx
,,,, Cryptopia are delisting this due to a possible SECURITY ISSUE of stealing bitcoins .?
please explain ?
please explain ?
Explain what? ...
What you wrote there? Nothing to explain as Cryptopia have not published any reason why they are delisting except to send us (and anyone asking in support) a link to their delisting and coins policy.
So no - we will NOT explain that statement considering you lucked that out of somewhere, to insinuate that something is going on in a underhanded way. It isn't! Cryptopia are delisting more than 70 coins in the last few weeks and they have every right to. It is THEIR exchange and they seem to be culling all the low cap coins, which ours are part of. It is what happens when you corporatize the policies, and HAVE to abide by regulation from the Governments.
#crysx
..Cryptopia specifically stated this coin to be a security risk due to back doors in software . end of story .
DYOR PPL >
Jump to: