Can you be more specific about the coin control fix? Was this simply a GUI change hiding the orphans, or is there something more fundamental that was fixed?
Not a GUI change, but under the hood there is something more fundamental. I changed the coin selection function to only return coins with at least 1 confirmation. Something about this with the new stuff in bitcoin core with HD wallets is causing the math to get thrown off, there is a "TODO" comment in the code from one of the core devs on one of the functions that says it has to be fixed  Anyway, the coin control issue and the orphans issue are two separate problems. The coin control bug is basically if you were breaking blocks down doing transactions really fast one after another, you could cause the wallet to get "out of sync", your balance would display wrong or maybe 2x your real balance, etc. and it is because of the math with the spent vs unspent coins and change addresses. Can we do a wallet update from the console, or do we need to backup, download, and reinstall? With the old/existing version you have to backup/download/reinstall. |
|
|
|
Can you be more specific about the coin control fix? Was this simply a GUI change hiding the orphans, or is there something more fundamental that was fixed?
Not a GUI change, but under the hood there is something more fundamental. I changed the coin selection function to only return coins with at least 1 confirmation. Something about this with the new stuff in bitcoin core with HD wallets is causing the math to get thrown off, there is a "TODO" comment in the code from one of the core devs on one of the functions that says it has to be fixed Anyway, the coin control issue and the orphans issue are two separate problems. The coin control bug is basically if you were breaking blocks down doing transactions really fast one after another, you could cause the wallet to get "out of sync", your balance would display wrong or maybe 2x your real balance, etc. and it is because of the math with the spent vs unspent coins and change addresses. |
|
|
|
so what exactly am i looking at? Wallet fix is done, masternodes and fork on monday?
I am about to activate a masternode on mainnet. :evilgrin: edit: Yes. |
|
|
|
 Also added kinetic scrolling to the overview page (so you can scroll with your finger on mobile like in other apps). Fix for coin control I have it not show unconfirmed coins. This seems to be the root of the issue that throws it off. Unfortunately what this means is if you are splitting down a large block of coins in one address, you have to wait for 1 block in between each send.  |
|
|
|
Testing the fixes and adrenaline nodes now. I put the keepass stuff in too but don't really have a way to test it so I'd say avoid that for now. Just have to test the automated masternode payments function from staking again....have to wait for it to stake  Solid progress, thank you. Will make sure to tip you a percentage of the profits from running a masternode. Have you decided on the level of investment required for a masternode? Again, my recommendation is to stick with 1000 CRAVE. If it's too low, there will be too many masternodes, and little to no profit. I went with 500 CRAVE. |
|
|
|
Testing the fixes and adrenaline nodes now. I put the keepass stuff in too but don't really have a way to test it so I'd say avoid that for now. Just have to test the automated masternode payments function from staking again....have to wait for it to stake |
|
|
|
I'm working on trying to solve the annoying Coin Control bug once and for all, I've also experienced it and it is kind of unsettling, if you split lots of blocks at once or do it from the RPC console, the wallet seems to kind of get "out of sync" with itself and takes a bit to "catch up" and show the right balance info etc. So for now, avoid splitting lots of blocks at one time. The guys who are experienced "stakers" know this is kind of an important feature to have, so its a high priority fix to get in now.
Haven't checked yet, but I think this bug might actually be reproducible in the latest Bitcoin Core. It seems to be related to the change to HD wallets. |
|
|
|
|
I'm working on trying to solve the annoying Coin Control bug once and for all, I've also experienced it and it is kind of unsettling, if you split lots of blocks at once or do it from the RPC console, the wallet seems to kind of get "out of sync" with itself and takes a bit to "catch up" and show the right balance info etc. So for now, avoid splitting lots of blocks at one time. The guys who are experienced "stakers" know this is kind of an important feature to have, so its a high priority fix to get in now.
|
|
|
|
|
Yeah you got bit by the coin control bug that Crave inherited from Blackcoin and that you guys inherited from us and some other coins like BitBean also have. I'm working on a fix in $CRAVE for this to roll into our next update, once I have it figured out I'll let you guys know the fix. For now I would avoid splitting lots of blocks at once in coin control. Kind of a pain, but you have to do just one at a time and kind of let the wallet "settle".
|
|
|
|
I'm scared to buy back in now, The second that buy wall gets pulled its headed right back down below 45k. I think I'll wait this out. Not 100% on this dev yet either, lots of talk but no show YET!
no show what all the things we initially said we did 1st 1 time tx first 40 mb blockchain 1st colored coin asset exchange thru tor masternodes were added to the mix AFTER the first objectives were achieved and is a blessing from the dev. giving u a chance to own a stake in infrastructure Yeah we pretty much hit the entire 1st roadmap already. Adrenaline Nodes + stake diff/orphan fix + coin control fix will finish it off then its on to the next batch of features.  |
|
|
|
200k sat  not at the moment were heading down. we have like 4 days until any news of nodes. 1st date missed now there is doubt of second date so people will be cautious. 30k is possible doubt is not good Who said 4 days?  |
|
|
|
Problem is that there is no roadmap with dates.
That's it.
It's all based on "when i have time","Today,maybe monday etc etc".
Real crypto with real and solid team working on it know the real date of releases.
Easy.
lol yeah if all the works already done and they're just sitting on tech till the "release dates" then fine (would rather they release all at once if it's ready from the start) or if they are actually developing code/tech then I don't think dates are a good idea. stuff happens, new ideas come out, or testing reveals more work than they thought etc etc... then if they don't get it ready or rush it for the date it's far worse, as well as drk has done it would have done much better if they didn't have to revert back changes soo many times on their forks. I hope CRAVE is taking their time and testing as much as they can before they release any projects etc Specific dates are always a bad idea IMO. Stuff comes up, like this orphan fix and coin control fix, etc. In any event, the build is compiled and just needs some shakeout testing after some rest (i.e. must sleep  ). The "experts" always come out without fail  Only in crypto.... AFAIK we are, at least for now, the only masternode implementation on a PoS codebase. Although our code is somewhat closer to Bitcoin Core than other stake coins, but it still meant backporting/"un-refactoring" a fair amount of the bitcoin core classes/object references etc. |
|
|
|
any news from the masternodes ?
Still waiting, I think. Won't be too long. I mentioned earlier I'm rolling in a patch to help with the orphan problem some cravers have experienced. So this update will be a protocol switch like a hardfork, which means everyone will have to update their wallets by a certain point in time. I was going to make that 2 weeks, but with the orphan patch I'm making it 4 days / by Monday in case exchange people or others aren't around over the weekend. and masternodes will be released when? After all?  |
|
|
|
any news from the masternodes ?
Still waiting, I think. Won't be too long. I mentioned earlier I'm rolling in a patch to help with the orphan problem some cravers have experienced. So this update will be a protocol switch like a hardfork, which means everyone will have to update their wallets by a certain point in time. I was going to make that 2 weeks, but with the orphan patch I'm making it 4 days / by Monday in case exchange people or others aren't around over the weekend. |
|
|
|
any word on the the orphans/pos getting fixed? I think that would give a lot of confidence to the market... some of us actually stake the coins we buy lol not just endlessly trade them back and forth all day (on some coins I will but not if it's got a good pos like crave does)
There is a lot of competition on the network for stake, the best thing you can do is to ensure you are well connected to the network. We can also look at rolling in a protocol change to allow the difficulty to adjust higher faster. I don't think competition is causing this. I think it's highly likely there's some sort of data corruption going on. You might want to check to make sure you're not overflowing any buffers or something in code you've added. No, this is wrong, there is no data corruption. It is exactly because of more stakers on the network and difficulty adjustment and the way POS2 works. I will roll a change in with masternode protocol switch for masternode payment enforcement. |
|
|
|
This project remains me of Crave coin.
They forked old $CRAVE code. Which is ok, if you guys make some unique tech that's cool. Concept of this coin is cool, gfx are cool, specs are nice, for some reason reminds me of SYNC maybe. But, you have couple of things to fix/clean up... First is simple, you have the bug where it reindexes the address index completely every wallet start. You have to change default of reindexaddr argument parsing in init.cpp from true to false, so that it only does it if user specifies -reindexaddr on command line. For now workaround is put -reindexaddr=false and it won't do it. Second, is you set the alert and checkpoint keys to "". You need to generate keypairs and put the public key in there. Otherwise, you cannot broadcast alert to network, and you cannot run checkpointing node. You have PoS coin, need to run checkpointing from any node or your own wallet by putting the checkpointkey in your .conf and putting your private key there. Otherwise over time you will have syncing problems and people going off on own forks. To make keypairs, just open your wallet and use makekeypair command...easy! You could make wallet really cool if reskin to be like a HUD or panel from crysis or far cry Anyway nethash already high on this one so maybe I wait for exchange to scoop up. |
|
|
|
Sell order book has officially gone dry. Price has consolidated and over the past 24 hours has created a mini fractal of last week's larger increase...
This is officially referred to as being on the rocket launching pad.
Say goodbye to these sub-0.00091 prices.
JL
I'll believe it, when i see 45 bitcoin on the buy side. @Dev why the delay with the Masternodes? No delay. Working on some anti-cloning things to put into it before putting it out. Oh thank god i bought more before this. Was told about another coin that maybe is waiting to bite our tech, but they left gaping backdoor in their code so maybe not a problem. Can least make it challenging for them if they survive before somebody forks them a million ways... |
|
|
|
Sell order book has officially gone dry. Price has consolidated and over the past 24 hours has created a mini fractal of last week's larger increase...
This is officially referred to as being on the rocket launching pad.
Say goodbye to these sub-0.00091 prices.
JL
I'll believe it, when i see 45 bitcoin on the buy side. @Dev why the delay with the Masternodes? No delay. Working on some anti-cloning things to put into it before putting it out. |
|
|
|
any word on the the orphans/pos getting fixed? I think that would give a lot of confidence to the market... some of us actually stake the coins we buy lol not just endlessly trade them back and forth all day (on some coins I will but not if it's got a good pos like crave does)
There is a lot of competition on the network for stake, the best thing you can do is to ensure you are well connected to the network. We can also look at rolling in a protocol change to allow the difficulty to adjust higher faster. |
|
|
|
Embrace the sound of silence! It only means 2 things...ICM is working hard as usual and whales are suppressing price 2 accumulate cheap coins! patience padawans...
 >Soon< |
|
|
|
|
Show Posts
