Development Update #2![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FRPRYAoP.png&t=663&c=7HDvWBfkmSITNg) New wallets released, updated to 1.0.4, with links added to the main post. This includes a mandatory update before block 2880. We have sent emails to relevant pools to make sure the correct fork is used beyond the Proof Of Work period. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FRPRYAoP.png&t=663&c=7HDvWBfkmSITNg) We have anticipated a further issue with the proof of stake function from the previous codebase Vault is forked from. We'd like to summarize the complexity of the issue before going into detail about how we're going to handle it and maintain network integrity. Since the original codebase is a modification of ppcoin, the value of COIN is only 6 decimal places. When used with the low supply of Vault, this raises an issue with stake rewards. In more detail, the transactions generated as rewards for low balances supporting the Vault network via staking will be below 0.000001, and therefore will effectively have no PoS reward for smaller balances (due to the internal integer representation). As a quick fix to allow staking users to see reward, we could increase the stake reward by a multiplier, but we would prefer to instead stick to the original technical outline for Vault. Further complexity is raised when attempting to alter the value of COIN, which is a very delicate variable, highly integrated into the core codebase. It is certainly not something we'd like to be pushing fixes for with limited time until the PoS switchover. A full fix to this issue will require a codebase cleanup, thorough checks and a little stress-testing, something we'd like to take a period of time to complete to a level we're confident with. For these reasons, we have decided to implement a temporary repression of staking rewards until we are satisfied with a cleaner, bug-free codebase. What does this mean for you? Well, not much, besides a short period of staking with zero reward. The core members of the development team have managed to mine around 22 Vault which we will commit to staking 24/7 during the zero reward period, allowing the network to continue it's mobility and allow transactions to confirm as normal. We are already working on the permanent solution, and integrating this solution with VaultNodes, which is the first novel unique innovation we're implementing into Vault. Please remember, this update is mandatory. Any staking you perform with previous clients will exist on a fork that is not valid to the main network. We will provide another update when the permanent fix is prepared for public upgrade. Thank you for your continued support, we hope that we have displayed a devotion to the continued development of Vault and the avoidence of problems before they occur. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FRPRYAoP.png&t=663&c=7HDvWBfkmSITNg) Approaching the end of the Proof Of Work period, only 100 or so blocks remaining to mine. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FRPRYAoP.png&t=663&c=7HDvWBfkmSITNg) We are preparing a documentation of future development plans, including an explanation of VaultNodes, and additional technical contributions, but would like to fix the ppcoin codebase's staking issues before we proceed with announcing the more complex developments. Thanks for your patience and continued support! 1.0.4 Windows client: (download)1.0.4 Mac client: (download)See code changes: (github) pool.mn has updated to v1.0.4
|
|
|
pool diff cheaters.... ![Undecided](https://bitcointalk.org/Smileys/default/undecided.gif) 20 minutes in Block time: 60 seconds 144 blocks mined? HOW? ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) diff retarget is not perfect and is not instant. This is common for most, if not all, coins.
|
|
|
I've been waiting hours for this launch. When its launched I can see 15 people mining all the easy coins on pool.mn, but I can't get on. This goes on for a good 5 minutes. I try several times to get on to your pool and its "waiting for work". I tried both sgminer and my nvidia ccminer, both said nope, no work. As soon as I switched to another pool I was on straight away. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) same here im at http://mts.minerpools.com, and im LATE ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) 150 blocks already mined Well, this is at least one reason why you should use failovers or just user other pools. When a large number of miners are trying to connect to a single pool some of the connections can get stuck.
|
|
|
WHy are there 57 people already on POOL.MN mining, when I'm not let on?
Already up to block 95!!
Try another pool got straight on to another pool. WTF POOL.MN?! I am sorry, I don't quite understand what is the issue? I've been waiting hours for this launch. When its launched I can see 15 people mining all the easy coins on pool.mn, but I can't get on. This goes on for a good 5 minutes. I try several times to get on to your pool and its "waiting for work". I tried both sgminer and my nvidia ccminer, both said nope, no work. As soon as I switched to another pool I was on straight away. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) I am really sorry for this, but I guess that there was a problem with the TCP connection to the pool. Have you tried to reconnect or were you waiting for the work?
|
|
|
WHy are there 57 people already on POOL.MN mining, when I'm not let on?
Already up to block 95!!
Try another pool got straight on to another pool. WTF POOL.MN?! I am sorry, I don't quite understand what is the issue?
|
|
|
We are ready for the launch, the wallet has been compiled. When the dev says go I will launch the pool
|
|
|
Development Update![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FRPRYAoP.png&t=663&c=7HDvWBfkmSITNg) New wallets released, updated to 1.0.3, links in main OP. This includes a hard fork at block 2350. We have sent emails to relevant pools to make sure no hashing time is lost. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FRPRYAoP.png&t=663&c=7HDvWBfkmSITNg) We anticipated an issue with staking, and have thus corrected the staking reward via the hard fork due to arrive at block 2350. This is a fix of the staking modifer interval, and also cleans up some issues with the code of the coin we originally forked. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FRPRYAoP.png&t=663&c=7HDvWBfkmSITNg) Fixed anticipated problem with difficulty reset for Proof Of Stake switchover. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FRPRYAoP.png&t=663&c=7HDvWBfkmSITNg) Corrected the height for staking GUI. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FRPRYAoP.png&t=663&c=7HDvWBfkmSITNg) Checkpointed in new wallet release. Thanks for your patience and continued support! 1.0.3 Windows client: (download)1.0.3 Mac client: (download)See code changes: (github) pool.mn has updated to v1.0.3
|
|
|
pool.mn is up now. I had a wrong time in my calendar, sorry for this delay.
Darn man, might have some trouble cause there's some mega pools -- try and get word out about the coin to get people and come to your pool. Which pool is a mega pool? There is one chinese pool which has one big worker. It is not clear from where the hashrate is coming.
|
|
|
pool.mn is up now. I had a wrong time in my calendar, sorry for this delay.
|
|
|
maybe permitted.
When we need, we will contact you, please leave your email。
It is in my signature
|
|
|
Reward in blocks 200-15000:2300 , in 60 minutes
We are getting these errors: WARNING: ProcessBlock(): check proof-of-stake failed for block key2 00000000036e08d905f1471adfaa274e79c0af953a8f6330cfb63148f64c56b3 ERROR: ProcessBlock() : AcceptBlock FAILED Blocks are rejected. Working on it. I am shutting down the pool. Blocks from the pool are not accepted. Was anyone successful in finding a block by solomining?
|
|
|
Reward in blocks 200-15000:2300 , in 60 minutes
We are getting these errors: WARNING: ProcessBlock(): check proof-of-stake failed for block key2 00000000036e08d905f1471adfaa274e79c0af953a8f6330cfb63148f64c56b3 ERROR: ProcessBlock() : AcceptBlock FAILED Blocks are rejected. Working on it.
|
|
|
Dev went offline 2 minutes before launch time, it is now 17 minutes past launch time. When will this be released?
Wallets are up but the source is not, now it says that the source will be available tomorrow. Dev, what does this all mean?
|
|
|
Pool.mn has the pool ready but I am hesitant to run the pool, due to the instamine. Dev, could you comment on the instamine?
Blockchain is stuck all ready. True, at height 1324. Dev, are you gonna let your coin die like this?
|
|
|
Pool.mn has the pool ready but I am hesitant to run the pool, due to the instamine. Dev, could you comment on the instamine?
|
|
|
So there are 2 or 3 forks on the network right now , look at dedicate pool and pool.mn and suprnova , my pool was on other fork to , i resync the wallet with pool.mn so we need dev to tell us which is the right fork
EDIT: The block explorer from op is down
Thank you for making us aware of this, we're working to restore the network. The pool.mn fork is the correct one, please use this. We're hoping to put another block explorer online as the developer for the current one is having hosting issues. I'm not wondering that this is correct fork.. Since this coin started everything was "pool.mn"... Please, don't accuse us. I am quite surprised that the dev made a call that our fork is the correct one and not the dedicated. I am not sure how to proceed, probably shutting down the pool would be the best thing to do. Dev, how should we proceed? We're investigating the issue now. Your pool is synchronised with the seed node and our dedicated pool though so, as far as we're concerned, it is on the "correct" fork. As for the issues ocminer raised, we believe these to be FUD. As you can see, suprnova rented a large NIST5 mining rig at launch ( https://www.miningrigrentals.com/rigs/7086/) and we believe they are trying to get a large percentage of the second half of the mining parabola by spreading distrust. This is further called into question when you look at the praise he has given Vaultcoin initially, it seems like he's trying to establish a large holding to profit. Our PoW checking code is identical to the most recent version of PPCoin and currently we're not running in "hybrid mode", there is a 3-day pure PoW period before PoS begins. Please treat his claims with caution. Firstly, ocminer is a trusted member and I doubt that he would do anything close to what you are saying. Even if he was renting rigs it was not to highjack the coin but probably to get his pool going. Secondly, dedicatedpool.com is usually the largest pool and we are on two different forks. This should be resolved asap.
|
|
|
So there are 2 or 3 forks on the network right now , look at dedicate pool and pool.mn and suprnova , my pool was on other fork to , i resync the wallet with pool.mn so we need dev to tell us which is the right fork
EDIT: The block explorer from op is down
Thank you for making us aware of this, we're working to restore the network. The pool.mn fork is the correct one, please use this. We're hoping to put another block explorer online as the developer for the current one is having hosting issues. I'm not wondering that this is correct fork.. Since this coin started everything was "pool.mn"... Please, don't accuse us. I am quite surprised that the dev made a call that our fork is the correct one and not the dedicated. I am not sure how to proceed, probably shutting down the pool would be the best thing to do. Dev, how should we proceed?
|
|
|
to pool.mn
wrong option --difficulty-multiplier 256 for this miner
SPH-sgminer for Windows: Download here SGMiner SOURCE for Linux: Download here Example miner settings:
./sgminer -k qubitcoin -o stratum+tcp://stratum.pool.mn:7823 -u Weblogin.Worker -p Worker password --difficulty-multiplier 256
and still rejected shares
Thanks, the option has been removed from the gettingstarted page. I haven't tried to mine myself, could you please confirm that you can mine with the same settings other qubit coins?
|
|
|
Pool.mn has updated. As a note - old code still works and blocks are accepted. Old code not works, rpc version blocked. accepted only new version. Manualy sync at to block 2908, because you have the biggest pool. Waiting to updated block exlorers... sorry, you are right. I made a mistake with updating the pool's wallet. Everything has been fixed now.
|
|
|
|