Seems like a hell of a lot to lose out on if the coin comes back as original and not take over. I have millions of v1s seems a lot to lose out on
I doubt WAS v1 will make any kind of comeback, at this point it would be a coin where over 50% of the minted coins are owned by one person. How long will it take to move over 40+ million or so coins ?
A few mins. I had hundreds of millions. I think you can do 20 million at a time The newest v1 client that was released shouldn't have the 20 million limit.
|
|
|
Is there any incentive to hold WAS V1?
Unless the coins are being destroyed somebody could host nodes and release a new wallet with massively centralized value regulation due to the swap.
I wouldn't think so, if you have V1 remaining I would trade it in ASAP
|
|
|
im kinda around - i see a git merge request but im confused why so many files in the src tree have changed including a ton of stuff in the qt gui...
anyone review this?
The main things that are changed are the Scrypt functions to support Scrypt Adaptive-N, added KGW, new alert key and related functions, and increased the version number and reject old clients starting on the hardfork date. The Qt changes are so it supports Qt version 5 and not just the older Qt 4.
|
|
|
Yeah, remove all the addnodes and your peers.dat. Then start the client and it will connect to the seed nodes within 30-60 seconds.
|
|
|
So a technical question for MrData and ACN- How do we reflect the true number of WSX in circulation after the drop dead date?
I can modify the client so the getinfo call subtracts the amount of the burned coins. (And comment the code with the reason and burn address.) So you'll have to release another wallet? I hope that we can all come up with a wish list that have all features that we all agree to work and eliminate extra work for you. It wouldn't be a hardfork so it wouldn't be a big deal or anything.
|
|
|
So a technical question for MrData and ACN- How do we reflect the true number of WSX in circulation after the drop dead date?
I can modify the client so the getinfo call subtracts the amount of the burned coins. (And comment the code with the reason and burn address.)
|
|
|
Hello i send 500k romancoin to the adress 1.5 hour ago still havent received anything in my moneta wallet?
Sorry, the swap hot wallet ran out overnight while I was sleeping; I'm sending more to it now so you should receive your coins shortly
|
|
|
Great, I have some RomanCoins stuck in my Qt wallet that I want to swap.
If you can't get Romancoin synced up feel free to send me your wallet.dat and the swap address the coin swap page gave you and I'll do the swap for you.
|
|
|
The Moneta clients are up now in the Moneta ANN thread. After you run your Moneta client you can go here to swap your Romancoin in for new Moneta: Coin Swap.
|
|
|
Cannot get v1 to synch, any current nodes?
This should get you connected: addnode=192.99.37.224 If not if you send me your wallet.dat and v2 address I'll swap them manually for you.
|
|
|
2.0.3 is the latest version, not sure where you saw 2.0.4 at???
|
|
|
Downloaded new wallet. Now it will not sync. stuck at 112995. It keeps changing between 141 and 84xx blocks behind but still says same block number.
I just synced a clean wallet with no problems, you may just want to restart it or let it sit a while and it should sync up.
|
|
|
So as I've learned so far, we need to keep the mix POW/POS to keep the network moving per MrData. I'm taking down the poll, sorry for the extra vote guys. I have a couple suggestions:
1. Change WSX to 60 second block 2. Rename the data directory to WeAreSatoshiX (can that be incorporated into the executable as a rename while upgrading the wallet?)
I don't think that will require a fork but MrData should let us know soon. Thanks,
Changing the block time will fork. I can rename the data folder if people are worried about it, I don't know if anyone would care about that though??? I think we need to get the fork going. We keep on loosing pools and it's easy to notice a few pools and 3 exchanges now. MrData, please let us know when you can work on it. Renaming the data directory is up to you, but it will be nice though I can do it whenever you are ready, just need to know when you want it to kick in (block number or date/time). I guess the other thing would be if you want to change the PoW reward structure since the block time is going to change.
|
|
|
I didnt get which exact version of WeAreSatoshi is tradind on C-Cex ?
It is the version in this thread, WeAreSatoshi v2.
|
|
|
So as I've learned so far, we need to keep the mix POW/POS to keep the network moving per MrData. I'm taking down the poll, sorry for the extra vote guys. I have a couple suggestions:
1. Change WSX to 60 second block 2. Rename the data directory to WeAreSatoshiX (can that be incorporated into the executable as a rename while upgrading the wallet?)
I don't think that will require a fork but MrData should let us know soon. Thanks,
Changing the block time will fork. I can rename the data folder if people are worried about it, I don't know if anyone would care about that though???
|
|
|
MrData, would you mind weighing in on hybrid PoW / PoS vs just PoS? It's a highly technical question / decision involving network security and stability, and I don't know that I fully understand the pro's & con's on both sides.
Is one method more secure than the other? If switched to 100% PoS, in your opinion would that pose a risk or potential problems?
I like keeping both active just because it makes coins more reliable; you don't have to have wallets open all the time and there are no periods of slowness when there are periods of less weight on the network. When we reach 1 coin per block, how many coin will be mined in a year? Do I need addnodes in the latest wallet? It doesn't sync on a new PC. If you keep the current 30 second block time 1,051,200 WSX would be minted per year. No addnodes are needed, it has the seednodes built-in. From a blank install it will connect to them within about 30-45 seconds. ACN mentioned earlier that it will help fixing forks if we go up to to 60 or 90 second block. What do you think about that and that means the total coin minted per year will reduce to 525600 or 350400 per year? It's a good idea and should definitely help the pools, etc. Yep, it would reduce to 525600/350400 per year.
|
|
|
MrData, would you mind weighing in on hybrid PoW / PoS vs just PoS? It's a highly technical question / decision involving network security and stability, and I don't know that I fully understand the pro's & con's on both sides.
Is one method more secure than the other? If switched to 100% PoS, in your opinion would that pose a risk or potential problems?
I like keeping both active just because it makes coins more reliable; you don't have to have wallets open all the time and there are no periods of slowness when there are periods of less weight on the network. When we reach 1 coin per block, how many coin will be mined in a year? Do I need addnodes in the latest wallet? It doesn't sync on a new PC. If you keep the current 30 second block time 1,051,200 WSX would be minted per year. No addnodes are needed, it has the seednodes built-in. From a blank install it will connect to them within about 30-45 seconds.
|
|
|
MrData, would you mind weighing in on hybrid PoW / PoS vs just PoS? It's a highly technical question / decision involving network security and stability, and I don't know that I fully understand the pro's & con's on both sides.
Is one method more secure than the other? If switched to 100% PoS, in your opinion would that pose a risk or potential problems?
I like keeping both active just because it makes coins more reliable; you don't have to have wallets open all the time and there are no periods of slowness when there are periods of less weight on the network.
|
|
|
Are you synced up on the right chain? It should be on block 34,000 right now but you can check at http://www.carpediemexplorer.com/Also how many peer connections do you have?
|
|
|
I don't know if anyone kept the original client chain going or not, it could be stuck at 517,200 still. Even our hardfork client still works and could be made to start putting out rewards again (of course I would have over 50% of the coins lol.)
I will tell you one weird thing though, there is a guy out there who is still changing his coins over 5,000.00 WAS -> 5.00 WAS2 at a time; just everyday you'll see little bursts of them. No idea the logic behind that.
I got past 517200 so I'll know for sure what's going on with MrBrew's client. So what if one mined on the old block chain, sent his WAS to europex.eu and transferred them back to your WAS v1 client and convert to WAS v2? That would only work if they were accepting deposits with MrBrew's client but sending payouts with mine; so I doubt it would work.
|
|
|
|