Search results

Looks like things are back up and running.

You can see the status of testnet here: https://dash-testnet.freshstatus.io/

Qwizzie’s advice is solid. I would add — DON’T FORGET to back up your wallet (the wallet.dat file) before doing any troubleshooting. You don’t want to lose any coins accidentally.

Update: as of 2/9/21 this has been resolved. Dash is now 1 confirmation to deposit and 2 to withdraw on Binance. Good work to all those involved!

@pille It’s working now. Thanks for the fix!

@pille Hey man, in recent months I have not had any luck with the address balance lookup feature. Has this been depreciated? Or maybe I have messed something up with the url... not sure.

Ok. That makes sense. No matter how many distinct pieces make up a masternode, the DML only keeps track of complete masternodes so it won’t grow to be unwieldy. Got it. One more thing if you don’t mind, how would the hosting work for these trustless masternode shares? Has a hosting provider...

Very interesting and an approach that I am likely to support. One question though, why is the DML scalable down to 10 Dash and the DHL only scalable down to 100 Dash. Aren’t they basically the same thing?

Those numbers were meant to be illustrative, not final. The actual numbers can, and should, be adjusted. In fact, I would welcome letting research and data speak when it comes to setting any new reward split.

Yeah, Ryan had something similar in his presentation but with 100 Dash as @qwizzie pointed out. These “mini-nodes” would just stake though. Like a saving amount. They would not vote or support IS, PS, or Evo — nor get those associated fees on Dash Platform. That stuff would be reserved for...

Yeah, I am definitely not sure about network constraints. And admittedly, I was thinking more about accessibility to these saving accounts than network load. I am not sure if an idea of this nature will get any traction in the community, but if it does we will need a dev’s input before going...

I am not sure what you mean by slippery slope. My idea doesn’t do anything to MNs or the required 1000 Dash collateral. That was kind of the point. MNs are working fine — let’s not touch that in any way. This idea is just shifting some portion of mining to staking BUT NOT using proof of stake...

My thoughts (and feelings) on this issue. Skip down to the bold to get to the idea if you don’t want to read my justifications. Interesting enough it is similar to the post above: Just made it through Ryan’s AMA on the podcast. Great work by @thedesertlynx and @Mark Mason. Also, kudos to Ryan...

From core dev @UdjinM6 on Discord: I am not sure how long mobile wallets and the like will require, but hopefully it is only a few days.

Sigh.... if this is the tact you are going to take then this is a pointless conversation. I will bow out here. The fact that the documentation was a non-issue is clear from looking at the numbers and the fact that said documentation came from DCG (and not the MNOs) is undeniable. If you...

I think it is pretty clear what was meant. @masternube I don't see how that statement can be honestly misconstrued to mean that DCG is suggesting that MNOs write their own documentation for the core wallet.

Who is suggesting that MNOs write the documentation for the core wallet? That’s just silly. There was plenty of documentation available for the v13 and v14 updates. I am glad to see that it is being continuously improved, but the docs were sufficient beforehand. Otherwise we would have far far...

Thanks for this splawik21. Guys just to reiterate. If you are having issues double check your configuration carefully, step-by-step. On Discord, if the problem wasn’t a non-updated node it was the above issue (bls operator key and related dash.conf misconfiguration). I know it seems like...

I see. However, as this is a v14 release thread I would rather keep this discussion to banning types just introduced to minimize confusion. Hopefully a dev can get back to you in the other thread.

No PoSe errors for me either. Looking at Dashninja, this seems to be the case for the vast majority of other masternodes as well. So I agree that rather than grabbing pitchforks — those having issues should take advantage of @codablock’s offer if they cannot troubleshoot the issue on their own...