Topic: [ANN] [CV2] ColossusCoin2.0 | Yobit.net | NovaExchange - Swap to COLX is closed - page 72. (Read 116176 times)

I'm not sure, I've always had problems with Cryptsy :S

Anyways, I've gotten the newest versions of ColossusCoin2 compiled. There is a known bug in the Statistics page which isn't reading the money supply correctly, I thought I had corrected the problem and had it rebuilt but I guess not but "getinfo" shows the correct money supply and I'll fix up the bug in a later release.

The newest version comes with

-LiteStake - Reduce your CPU load when Staking up to 100x
-MultiSend RPC - MultiSend is a revamp of Stake for Charity and allows you to automatically send a portion of your Stake to as many addresses of your Choosing.
-Coin Control RPC - Use Coin Control on the RPC command line
-SplitBlock - Split your Blocks into sizes of your choosing for better Staking Rewards
-Delete address GUI - Delete old addresses *warning please make backups before deleting addresses*
-Reduction of the Blockdrift from 30 minutes down to 1 minute
-Doc's updated for Windows build
-Themes - Choose from 4 different themes










You can download the newest Wallet here and also comes with an updated .conf file

http://www.mediafire.com/download/49ma65yj4o5eztm/ColossusCoin2-qt-win-1-0-2.zip
http://www.mediafire.com/download/caarot1nvntswfn/ColossusCoin2-Qt-mac-1-0-2.zip

My whole CollossusCoin V1 balance just got disappeared at Cryptsy 

What is happening?!   

Yeah that would be very easy to do, the Staking week was actually a very simple idea and doesn't require any extra coding. Fees are returned through Staking, and you can set your own TX Fee so the Weelets, Yanglets, Primelets etc. was just auto send scripts with a higher TX Fee.

It would be like this.

Decide on what amount to be given away through Staking and fill up a wallet on a node.

Type ./PayCond settxfee 3 (to set the tx fee for sending a transaction to 3 Coins)

Create a script to send Coins

#!/bin/bash

for n in {1..30}
do
./PayCond sendtoaddress PJW2iA4ijs5aXt9iEpgdfgdf645gdFSD5e 10
sleep 120
done

Then it would send 10 Coins every 120 seconds, 30 times with a tx fee of 3 Coins, the Coins are received back into Staking so it acts like a reverse Prime Node.

I took it a step further and set a time varience and set the scripts to begin at the exact time when the countdowns were to end.

I wouldn't expect that there would be anything near a 100% swap for ColossusCoin and lots of Coins were lost. I had originally got the idea from experimenting with different sources and that once there would be decided that there would be an end to the swap it would be likely that there would be a lot of Coins left over so it would be a good way of redistributing the Coins.

Well, if source is the same, can we expect a "staking week", younglets/primelets and other awesomeness coded in here too? 

Yes I already sent him a message asking Sudo if he could join in the conversation here so we can progress this a little faster. I have also updated the CV2 source with the latest commits from PayCon and doing some light testing to make sure the litestake functions correctly. The two sources are for the most part the same source, if you were to search and replace the names and lay them on top of each other the differences are more in the retargeting, inflation rates, and Fees. This is beneficial because updates from one source can easily be applied to the other so I wouldn't really want to see ColossusCoin2 be abandoned when it is already one of the most efficient Coins.

Yes, lets proceed with this. Sending the wallet.dat actually is not a big problem. You pointed out possible security issues sending wallet.dat, but that is easy to resolve. For example you can request the "wallet.dat" to be encrypted, and request the user send the password via PM here on the forum. So users send the encrypted "wallet.dat" in email, then send the password+email address via PM on the forum. This way there is a kind of two-factor authentication, so no security issues could arise.

Crestington, I know you are very busy with your excellent work on PayCon. So could you please ask sudo23 to look into the thread here. We need this swap to get off the ground finally. It is a long time I don't see any progress on that, and as a result the COLv2 is suffering too. I personally don't have any COLv1 outside of Cryptsy, but I really want this swap task to move forward, as I hope some old community from COLv1 will be moved to COLv2 and give a new breath to the coin.

Sudo is managing the Coins for the swap so yes we can do it like that. I personally do not have enough of the Coin to do a direct swap (I have about 5% of CV2) but will direct him here so we can get this moving as I don't want to be spending extra time and money working on the V1 chain. I'd like to take the old COL chain out back and shoot it and be over and done with it and focus on improving the working chain.

Hmm,
interesting issue how to swap coins when V1 blockchain is Stuck to a V2 Wallet.

How about this:

Users
Step 1: Write down your Total Number of coins in your V1 wallet,
           Write down your password if encrypted
           Then Rename the V1 directory under c:\users\%username\appdata\roaming\colossuscoin
           with Old in front.
           Then Download and install the new V2 Client and sync with new blockchain.
           Then Write down your version 2 wallet address.
           Send Email to Dev, included # of coins, password, & New V2 Address.
           (FYI for Users: Never use that old V1 password again)

Dev
Step 2:  Upon Receiving the email.
            Dev confirms the number emailed matches the number in the wallet.dat by using V1 software.
            The fact that you emailed the wallet.dat and included the password proves that you own it.
            Then the Dev sends you the V2 coins which are Reversed Split on the V2 Client,
            (Dev manually calculates what the reversed split amount would be from the V1 Total)
            so you receive the right number of coins in your new wallet at the V2 address in your email.

Dev
Step 3:  Declares V1 is Dead, because if the blockchain is stuck , it basically is.
            V2 is now up and running.
            All Done.  

FYI:  Dev
In the old V1 Block Explorer print out the rich list down to zero and check them off before you send the V2 coins out. You can set a deadline for everyone to have emailed you, after the deadline, then begin processing the v1 wallets. I would use a spreadsheet or database to match up the email , amount, V1 Address, & new V2 address, before sending out any V2 , in case someone tried double sending their wallet with a 2nd v2 address. That way if you receive a duplicate wallet , you will know there is a problem before sending out V2 coins. Plus you can do the exchanges 1st or last in the list your choice unless they complain. If wallets are over 9 meg, then link to a dropbox instead of emailing it.
Whew that is a fair amount of work. 


             
 

And how would the Coins be destroyed in the transfer?

If it is possible to transfer COL from one Cryptsy account to another at this time:
/
Why not open a cryptsy account. Have COL users transfer their cryptsy COL to said account. Have the user send an email/PM in with their info, CV2 address, transaction, possibly a screenshot of transaction confirmation from their cryptsy account, etc. The user can then be sent their CV2 to the CV2 address provided.

I think that would be the easiest option to get started so how can we do it to send it safely?

The CV2 Blockchain is already running smoothly but for me the holders off the exchange would need to be swapped over first since the earliest you swap, the more Coinage you begin to aquire so if Cryptsy was swapped over first before a majority of people (atleast on best effort) then Cryptsy has the ability to Stake easier over the smaller holders. I'm not saying they would Stake their Coins and receive a huge benefit but highest advantage should go to the holders off the exchange.

I would suggest the opposite. The coins at Cryptsy are easy to swap, as the numbers are known, and coins are there. The problematic part are the coins kept by community members in their local wallets. The blockchain is not moving, so it is hard to send the coins to swap them.

However (here my suggestion comes) - why not to swap based on "wallet.dat" files? Instead of sending COLv1 coins via blockchain, let people send their "wallet.dat" files to sudo23, so he could check them using his own copy of blockchain, and then send the appropriate amount of COLv2 to the address specified by owner of wallet.

In this case there is no need to repair the blockchain of COLv1 and make it move.

What would community tell? Crestington, sudo23, is that doable and do you think that's viable approach? Some part of the BALLS/10K/TEETH swap was done that way, BTW.

  Can then exchange to give to you their wallet.dat?

This is the thing we are struggling with the most, we have ColossusCoin2 running and continuing to update but ColossusCoin 1.52 has so many bugs that it's hard to identify what are the specific issues. To just swap it over directly with Cryptsy puts a situation where it hurts the ones who have COL in their wallet that they can't send or even sell if they want to.

Okay. But there is another problem. How do I release my colossuscoin v1 locked in Crypsty? The wallet of Crypsty is under maintenance to several days.

I am here to stay! No worries!
We are working a web based coin swap form for colossuscoin.org
Draft:


Issue:
The Colossuscoin COL V1 Block Chain is currently not moving and Col1.52 blockchain is stuck on block 845190. I added this node 107.170.179.27

We want to add a Colossuscoin v1 Burn Address to the swap form where you first send your COL to this address in order to get ColossuscoinV2 CV2 in exchange (20:1 Colossuscoin-Colossucoin2.0 ratio)
 
Colossuscoins2.0 (CV2) are still secure in an offline address and reserved for a full swap over: http://bitexp.net/address.php?coin=Colossuscoin&address=Cec7KK4hZdrKajB7nDSoNmfsx5HuQd5HFa
"KaiDev" received 360 Million Colossuscoin2.0 CV2 reimbursement of lost Colossuscoins so far ( https://bitcointalksearch.org/topic/m.10557611 )

best wishes
sudo23

That would be good, I have been very busy with PayCon lately but also making a little time to do work on ColossusCoin/ColossusCoin2. I am a bit worried I haven't had much word from Sudo, it would be great to get some more involvement from everyone.

Crestington, read his latest posts https://bitcointalksearch.org/user/mullick-99433 They work on the exchange and may be able to add Colv2 and exchange our Colv1

I just found my old v1 wallet, let's see if I can sync it

I have been working recently on some further upgrades for integration. The two projects I work exclusively on are ColossusCoin2 and PayCon, I took over PayCon but coded and launched ColossusCoin2 and keep them in line so I can work on both at the same time meaning that upgrades for one means upgrades for both. I won't give a timeline (as it's prudent to make promises you can't keep) but in the works I have swappable theme's, additions to Coin control for viewing and sorting Blocks by age and weight, listing of transactions based on a date range (which makes it useful for determining the amount of Stake over a given period), Coin control through RPC, Delete address GUI along with a few extra features. The only cost to this would just be the rebuilds of the wallets but I would also like to sort out some hosting for a built-in DNS seeder or two which would eliminate the need for the ColossusCoin2.conf file but that isn't really mandatory atm and can be included in one of the wallet updates.