I really hope that RC4 is not going to get shadow released in the middle of the night or something. For all the effort put into this by the dev team and the community on testnet it would be a shame to have the rhetoric be about the way it was launched. The professional thing to do is give a notification of a the launch date a day or two in advance so that people know that they should be ready to update their MNs. Just my 2duffs...
What about services that check for only one tx? It will be harder to implement if an automated service if there are multiple transactions.
What of the pools that will not update to the new version? If the enforce is not active they would still be paying the old masternode? (I didn't update for 2 days, was still on .15 while network was on .16 and .17, and my tp2pool payee in block template was from my pool that wasn't updated)
So I guess what we are requesting, as masternode owners, is clear guidance about what to do and when.
Hmm? I'm not sure where you got this from, but it's not the case at all. The 5000DRK limit is a hard limit for the entire wallet. Lets say a user has 100k DRK, the wallet would actually end up making a bunch of 500DRK inputs and 100DRK inputs. The only reason I added the hard limit was because there's no easy way to denominate a portion of the wallet without doing the rest.
so splitting in 5k pieces before denomination is not a solution right? it was discussed on the previous page.. wouldn't it be possible that the user could determine the hard limit of the wallet?
Before DS+ I was hoping Evan would create a similar wallet like the pre-DS+ wallets, which we would just check mark the Darksend box and send any amount of drk and let the network do the anonymizing. Now it doesn't work like that, and DS+ doesn't work with amounts larger than 5000. So does it mean users will need two wallets, one with DS+ and one with no DS+ to be able to do both?
Well once all of the masternodes are running the new version and everyone is updated, I can release that after the fact and it will work without any change to the network.
I'm not getting this Evan... So essentially there will be two MN active "forks" ? If mining pools do not get orphaned, what will their incentive to update! At best, they might even revert back to the 10% version. It was such a hard battle to get to 95% consensus, if we need to do another round without the "fear" of orphaned blocks... most will just go "whhat? again? oh bugger off" .
So it seems that the current testnet version v0.10.12.17-2-g695af70-beta is working swimmingly. What now needs to be tested as far as bad actors, closing of wallets, shutting down MN's, etc..? Also eduffield, did you ever receive the message of the person offering half a dozen ec2 instances to be used for testing purposes? The offer was from user stonehedge.
The offer still stands. I can offer clean installs but will hand credentials to trusted devs to configure however they can be useful. EDIT: I will build them now whilst I have the time. Just in case they can be helpful.
6 EC2 instances built and ready to go. I'll keep them running for a month or two. First dev to message me gets them
All yours! I'll check my Amazon billing status but I might be able to spare some more instances depending on funds.
Well I have no clue what the fargle I was doing wrong last night but tried again today and everything's smooth, fast, and frisky. I'd still like to see Total balance / anonymised / unconfirmed in the Send tab though. Please.
I have a wallet on Windows updated to the latest version (v0.10.12.17-gf266a9a-beta) for which a Darksend Denominate transaction has been stuck for more than 36 hours. I can attach the wallet or send it to a dev if interested...
I just sent a post and immediately deleted it when I saw the denominating resume on my wallet (after an hour). Also, just got the first collateral fee (Win wallet v.17).
This is where a user friendly wallet with some kind of status / progress % would be ideal. I can picture a lot of freaked out people, Where's my money gone! lol
Imo its worth delaying RC4 release a few days to work solely on optimizing wallet UI and in-wallet messaging. Doing all this stuff optimally is critical to the success of rc4 release since its very important for users to know and understand what's going on and to have all the necessary things neatly presented.
