### A ChainWorks Industries (CWI) Project - SweepStakeCoin | Fast Fun Secure

[chrysophylax]

Any exchanges?. Where i can buy coin?

No Exchange just yet ...

But as posted in the main CWI BCT Thread here - https://bitcointalk.org/index.php?topic=1563601.msg48783659#msg48783659 - where SweepStakeCoin (SWEEP) is slated to be active on the Zapple Exchange this Friday (28th December 2018) if it syncs and tests run well.

So far INFX is now active there, and SWEEP is next in line. Our other coins will be added every Friday there after.

Buying the coins currently (or selling) is on our CWI Discord Group in the #trade channel.

#crysx

If it started synching the 27th or early 28th, it will take 15 days to synch from scratch.

So we have found out ...

It has never taken that long to sync before, but with about 2.2Million Blocks now, and TOR being the primary sync process, this could be a factor here.

The Zapple daemon is fast approaching the current block, and the Citrine Mine daemon is almost there. So looks like Friday next (in the New Year) will be the time to list and also to mine. Let's just hope that it will speed up a little more than what it has been doing. Either way, the week coming is 2019, the integration of SWEEP in Citrine and the integration of SWEEP in Zapple as well, with the possible integration of GRN also in Zapple if they work through the week.

Tomorrow night is off (New Years Eve) and New Years Day is off for me also, so the 2nd January 2019 is when I will be back full time again.

2019 is going to be a very productive year for us here at CWI!

#crysx

Well happy new year but you really need to strip off that TOR thing.

...

After OZC is finished, that CodeBase will be the template being used for all 5 coins we have. There is no TOR in this new CodeBase

Have a great 2019!

#crysx

[Grafschmidt]

You also have to give a thought about rescheduling your work tasks.

As for now we need a new wallet for SWEEP. It takes forever to load and forever to synch, we also may not be able to trade anything for this very reason.

[meyerjoer5]

I'd love to see some sort of timeline for when the wallet will get done. Even if it's subjective, it would be nice to just have a general idea. It would give people who haven’t been following the thread more reason to be interested in the coin/community.

Also one of the biggest problems for me is consolidating coins in coin control because you can only send about 67 blocks at a time due to the large transaction size. Which as Grafschmidt mentioned might create problems with trading.

[chrysophylax]

I'd love to see some sort of timeline for when the wallet will get done. Even if it's subjective, it would be nice to just have a general idea. It would give people who haven’t been following the thread more reason to be interested in the coin/community.

Also one of the biggest problems for me is consolidating coins in coin control because you can only send about 67 blocks at a time due to the large transaction size. Which as Grafschmidt mentioned might create problems with trading.

As has suggested beforehand ...

The new wallet will NOT happen unless the OZC CodeBase and new wallet is completed first. This is due to a number of factors, but the main being that OZC is the 'experimental' Coin that has the more recent CodeBase, and will also have the new Algo as well. This means that the CodeBase that OZC is completed with, will be the template CodeBase for all the coins we have under our development wing.

As for the consolidation - it is necessary due to the high volume of blocks, transactions and fragmentation of the transactions within the wallet/database. The best way to do this is to send coins to an internal wallet address, starting at a small number of coins (to consolidate a number of transactions) and keep increasing the number of the coins sent to that same address until ALL the coins in the wallet can be sent to that same internal wallet address. Obviously if you know how to use the coin control feature, then you need to use the smaller number of blocks and defragment the transactions within the wallet that way, so that the wallet can access the coins easier with less blocks to consolidate per transaction. This unfortunately restarts the Coin Age (back to zero), and Coin Weight (increases weight), which is never a bad thing when staking.

This should be resolved in the new CodeBase (which currently is based on the BTC 0.17.1.0 Code).

#crysx

[chrysophylax]

### CWI-TRADE - EXCHANGE

Hi All ...

Important update here - https://bitcointalk.org/index.php?topic=1563601.msg49025664#msg49025664

#crysx

[meyerjoer5]

I'd love to see some sort of timeline for when the wallet will get done. Even if it's subjective, it would be nice to just have a general idea. It would give people who haven’t been following the thread more reason to be interested in the coin/community.

Also one of the biggest problems for me is consolidating coins in coin control because you can only send about 67 blocks at a time due to the large transaction size. Which as Grafschmidt mentioned might create problems with trading.

As has suggested beforehand ...

The new wallet will NOT happen unless the OZC CodeBase and new wallet is completed first. This is due to a number of factors, but the main being that OZC is the 'experimental' Coin that has the more recent CodeBase, and will also have the new Algo as well. This means that the CodeBase that OZC is completed with, will be the template CodeBase for all the coins we have under our development wing.

As for the consolidation - it is necessary due to the high volume of blocks, transactions and fragmentation of the transactions within the wallet/database. The best way to do this is to send coins to an internal wallet address, starting at a small number of coins (to consolidate a number of transactions) and keep increasing the number of the coins sent to that same address until ALL the coins in the wallet can be sent to that same internal wallet address. Obviously if you know how to use the coin control feature, then you need to use the smaller number of blocks and defragment the transactions within the wallet that way, so that the wallet can access the coins easier with less blocks to consolidate per transaction. This unfortunately restarts the Coin Age (back to zero), and Coin Weight (increases weight), which is never a bad thing when staking.

This should be resolved in the new CodeBase (which currently is based on the BTC 0.17.1.0 Code).

#crysx

Thanks for the reply, most of this I've already read about and I understand that OZC will be first. However it still would be nice to have some sort of timeline on any development being made (on OZC) that way we can have a general idea of whats going on. I understand the process is slow and you all are working. I've seen the daily posts on the discord channel and I appreciate the work/consistency, but maybe some more in depth updates are necessary to start building a community around the coin and the other coins that you'll transfer the codebase to. It's probably more marketing than anything but I think it could help with future growth!

And I've done what you're saying I just wanted to mention the issues with consolidation due to the coin being listed soon, not sure if it will have a major effect or not.

[chrysophylax]

I'd love to see some sort of timeline for when the wallet will get done. Even if it's subjective, it would be nice to just have a general idea. It would give people who haven’t been following the thread more reason to be interested in the coin/community.

Also one of the biggest problems for me is consolidating coins in coin control because you can only send about 67 blocks at a time due to the large transaction size. Which as Grafschmidt mentioned might create problems with trading.

As has suggested beforehand ...

The new wallet will NOT happen unless the OZC CodeBase and new wallet is completed first. This is due to a number of factors, but the main being that OZC is the 'experimental' Coin that has the more recent CodeBase, and will also have the new Algo as well. This means that the CodeBase that OZC is completed with, will be the template CodeBase for all the coins we have under our development wing.

As for the consolidation - it is necessary due to the high volume of blocks, transactions and fragmentation of the transactions within the wallet/database. The best way to do this is to send coins to an internal wallet address, starting at a small number of coins (to consolidate a number of transactions) and keep increasing the number of the coins sent to that same address until ALL the coins in the wallet can be sent to that same internal wallet address. Obviously if you know how to use the coin control feature, then you need to use the smaller number of blocks and defragment the transactions within the wallet that way, so that the wallet can access the coins easier with less blocks to consolidate per transaction. This unfortunately restarts the Coin Age (back to zero), and Coin Weight (increases weight), which is never a bad thing when staking.

This should be resolved in the new CodeBase (which currently is based on the BTC 0.17.1.0 Code).

#crysx

Thanks for the reply, most of this I've already read about and I understand that OZC will be first. However it still would be nice to have some sort of timeline on any development being made (on OZC) that way we can have a general idea of whats going on. I understand the process is slow and you all are working. I've seen the daily posts on the discord channel and I appreciate the work/consistency, but maybe some more in depth updates are necessary to start building a community around the coin and the other coins that you'll transfer the codebase to. It's probably more marketing than anything but I think it could help with future growth!

And I've done what you're saying I just wanted to mention the issues with consolidation due to the coin being listed soon, not sure if it will have a major effect or not.

No worries meyerjoer5 ...

We are working, but unfortunately only fragmented this last week due to Christmas, New Years Celebrations, and our people still getting back onboard next week. Though the details of the plan for the developments is sketchy, the plan for what will happen is not. It is very clear about how we will move forward with the coins, the infrastructure, the trade bots and mining systems (possibly integrating the two also), along with the more 'private' projects going on in the background. We have setup a new channel in our CWI Discord Group for the new coin that will integrate all our coins (coins/mastercoin-coinx) for suggestions and discussion as to what the community AND the developers AND those that would utilize the coin (such as merchants like us at CWI), so that when OZC GRN SWEEP INFX and DRZ eventually do get integrated into CoinX, that there will be no loss of value, usage can be discussed and a plan to develop CoinX to spec can be started. This will happen later of course, but discussion of such is never too soon.

SWEEP has one of the fastest transaction transmission in the whole of Crypto, and so the best of all the coins could probably make up the 'base' of what we should be looking at so that ALL the coins I mentioned earlier, will have a place in the EcoSystem before CoinX get's to move in. What this means is that SWEEP will not be updated until OZC is done, and (currently) GRN as well as INFX is done also. Though this may take another month or two to finish, the new OZC Maintenance Release is close, and we should have the one issue holding it back, squashed soon enough.

Confirmation of GRN and SWEEP being integrated and running in Zapple had come through earlier, and we should see GRN and SWEEP active on Zapple Exchange in the coming hours. So transfers to SWEEP will be easy IF you have consolidated the coins to as little transactional fragmentation as possible. Otherwise the wallet will just spit out a response saying that the transaction could not be created. The Zapple Exchange wallet needs to be as non-fragmented as possible, and we will be working with Zapple to ensure this is the case at all times. So to ease the pressure on the Zapple Exchange Wallet, if we all defragment our local wallets first, and send all the funds we will be using to trade with in ONE transaction across to Zapple Exchange, then there should be little to no issue in the fragmentation respect for Zapple.

I have to admit, that I am personally quite excited about it all.

#crysx

[Grafschmidt]

I must say I don't like very much that KYC on zapple.

[chrysophylax]

I must say I don't like very much that KYC on zapple.

Everything improves in time ...

Zapple and Zapple Exchange are no different to anyone else in this space.

#crysx

[chrysophylax]

### CWI-TRADE - EXCHANGE

Hi All ...

Urgent update here - https://bitcointalk.org/index.php?topic=1563601.msg49079718#msg49079718

#crysx

[Grafschmidt]

I must say I don't like very much that KYC on zapple.

Everything improves in time ...

Zapple and Zapple Exchange are no different to anyone else in this space.

#crysx

My worries are about my documents and how will they handle them not only the inconsistency with the anonymity of the cryptocurrencies and the need of indexing who's trading them.
How can I be sure they won't steal my ID on their platform?
That's way I see more favourably an exchange like Flyp.me.

[chrysophylax]

I must say I don't like very much that KYC on zapple.

Everything improves in time ...

Zapple and Zapple Exchange are no different to anyone else in this space.

#crysx

My worries are about my documents and how will they handle them not only the inconsistency with the anonymity of the cryptocurrencies and the need of indexing who's trading them.
How can I be sure they won't steal my ID on their platform?
That's way I see more favourably an exchange like Flyp.me.

Understood ...

Soon, no matter what exchange you use, the government of the country that the exchange resides (if it is a legitimate enterprise) WILL require your details. It is the natural process with which the controlling powers take control from decentralized and anonymous parties. So These Exchange systems like flyp.me will not last long, unless the country the servers reside, allow anonymity.

Currently the crackdown on anonymity AND decentralization by the ruling powers are breaking down every effort to make sure they know not only WHO you are, but HOW MUCH you are trading with. That is what it all boils down to for them. Money. If they don't get their cut, then they will make it VERY difficult allow an anonymous transaction to take place.

It is the way the world works at the moment, until we get rid of/overthrow the controlling powers. Now do you really think that is going to happen any time soon?



#crysx

[chrysophylax]

### CWI-PYROXENE (theMINE) - CITRINE

Hi All ...

Update for PYROXENE (theMINE) here - https://bitcointalk.org/index.php?topic=3829887.msg49083177#msg49083177

#crysx

[lyolyalya]

what is the last version of a win wallet??

[chrysophylax]

what is the last version of a win wallet??

SweepStakeCoin 1.3.0.0 ...

It is still in the previous wallet format, and no development has occurred just yet for SWEEP. OZC has now been fully rebased, and is currently being rolled out on the new CodeBase (0.17.1.0) which will be HardForked shortly to get OZC to the stage we would like it to be. When that happens, SWEEP wallet will be HardForked also, and based on the same CodeBase.

For now, it is still SweepStakeCoin 1.3.0.0 Wallet.

#crysx

[lyolyalya]

what is the last version of a win wallet??

SweepStakeCoin 1.3.0.0 ...

It is still in the previous wallet format, and no development has occurred just yet for SWEEP. OZC has now been fully rebased, and is currently being rolled out on the new CodeBase (0.17.1.0) which will be HardForked shortly to get OZC to the stage we would like it to be. When that happens, SWEEP wallet will be HardForked also, and based on the same CodeBase.

For now, it is still SweepStakeCoin 1.3.0.0 Wallet.

#crysx

ok.thanks.
so, zapple is working on 1.3 too i guess? are their deposits okay?send 1000 sweep few hours ago and no tx.

[chrysophylax]

what is the last version of a win wallet??

SweepStakeCoin 1.3.0.0 ...

It is still in the previous wallet format, and no development has occurred just yet for SWEEP. OZC has now been fully rebased, and is currently being rolled out on the new CodeBase (0.17.1.0) which will be HardForked shortly to get OZC to the stage we would like it to be. When that happens, SWEEP wallet will be HardForked also, and based on the same CodeBase.

For now, it is still SweepStakeCoin 1.3.0.0 Wallet.

#crysx

ok.thanks.
so, zapple is working on 1.3 too i guess? are their deposits okay?send 1000 sweep few hours ago and no tx.

Of course they are - yes ...

They compiled from the same Git/Source that we, and everyone else does.

SWEEP NEVER takes hours to go from one wallet to another. There is definitely something wrong there, and needs to be looked at. You have two things to do, and two options on the second ...

1 - Check your transaction on the Block Explorer and make sure that the transaction was actually made. If so then proceed to contacting Zapple Exchange.

2 - Contact via two options.
   i - Directly via the their Support EMail in the Zapple Exchange.
   ii - Join our CWI Discord Group and go to the trade/#exchange channel and ask the question there.

If the transaction does not exist on the Block Explorer here - https://chainz.cryptoid.info/sweep/ - then the transaction never happened on the current BlockChain (or was rejected).

Let us know what happens.

#crysx

[lyolyalya]

what is the last version of a win wallet??

SweepStakeCoin 1.3.0.0 ...

It is still in the previous wallet format, and no development has occurred just yet for SWEEP. OZC has now been fully rebased, and is currently being rolled out on the new CodeBase (0.17.1.0) which will be HardForked shortly to get OZC to the stage we would like it to be. When that happens, SWEEP wallet will be HardForked also, and based on the same CodeBase.

For now, it is still SweepStakeCoin 1.3.0.0 Wallet.

#crysx

ok.thanks.
so, zapple is working on 1.3 too i guess? are their deposits okay?send 1000 sweep few hours ago and no tx.

Of course they are - yes ...

They compiled from the same Git/Source that we, and everyone else does.

SWEEP NEVER takes hours to go from one wallet to another. There is definitely something wrong there, and needs to be looked at. You have two things to do, and two options on the second ...

1 - Check your transaction on the Block Explorer and make sure that the transaction was actually made. If so then proceed to contacting Zapple Exchange.

2 - Contact via two options.
   i - Directly via the their Support EMail in the Zapple Exchange.
   ii - Join our CWI Discord Group and go to the trade/#exchange channel and ask the question there.

If the transaction does not exist on the Block Explorer here - https://chainz.cryptoid.info/sweep/ - then the transaction never happened on the current BlockChain (or was rejected).

Let us know what happens.

#crysx

well..here we are -

Status: 83 confirmations
Date: 06.01.2019 12:05
To: zapple Sbt3KwGTYY5g8UA2rxhbKpP9DFPLK55Kiw
Debit: -1000.00 SWEEP
Transaction fee: -0.00001 SWEEP
Net amount: -1000.00001 SWEEP
Transaction ID: cb79c12f2ff0938a2eeb563cc95a8b76e1b2d3e7e422531b1a60c29584fb2708



there is no that tx in explorer - https://chainz.cryptoid.info/sweep/search.dws?q=cb79c12f2ff0938a2eeb563cc95a8b76e1b2d3e7e422531b1a60c29584fb2708

maybe there is tx fee problem???UPDATE.something wierd with my wallet.reopen it and after 10 minutes offline have 19000 blocks to sync...maybe it's just not syncing?but few minutes ago it was okay...

[lyolyalya]

yepp...something is wrong with syncing.have plenty of active nodes but 'blocks remaining' just go higher and higher.any 100% working nodes?


after 2 minutes



after 30 minutes

[chrysophylax]

yepp...something is wrong with syncing.have plenty of active nodes but 'blocks remaining' just go higher and higher.any 100% working nodes?


after 2 minutes



after 30 minutes

This may be a corrupt blockchain ...

Now this will not be a positive thing to hear, but a full resync is probably what you will need. In order to do that, you will need to delete the BlockChain component from your SWEEP folder (which is pretty much everything EXCEPT the wallet.dat and SweepstakeCoin.conf file if you have one), and then ropen/restart the wallet. ALWAYS backup your wallet by making a copy of your wallet.dat file or keep your private keys somewhere safe, or both.

The issue with this is that the BlockChain takes a huge amount of time of late to sync, which is something that really can't be pushed in anyway, even by a bootstrap.

Current working nodes are all listed here - https://chainz.cryptoid.info/sweep/#!network - which you can add to the .conf file, but it will still take some time before you download the entire BlockChain.

Let us know how you fare with it all.

#crysx