also crowning's Masternode Payments site shows Payment Enforcement Status: 'On' since 2015-05-19-01:35:01 .. appearently MN payment enforcement was off and put back on today ?
My ISP had some hickups last night at that time, I guess my payment-daemon wasn't able to get the current enforcement status and therefore reported it as "Off" for some time. I changed my script to ignore downtimes. |
|
|
|
I had to re-boot the server where my voting daemon (v0.11.2.23 of course) runs, and for reasons only Evan knows it's now stuck at 43 YEA, 0 NAY and 2557 ABSTAIN. I think I'll have to look into that code soon... |
|
|
|
Does this mean that Dash version 0.11.2.23 will include the automatic backup function and will also include all fixes & additions incorporated into the Master branche on github after 11th of april 2015 (when Dash version 0.11.2.22 was released) ? If so we need perhaps a bit more documentation about this update.
i do not think that is in there this is only for the voting system , as not mandatory update i just downloaded version 0.11.2.23 and automatic backups are definetely in there, therefore we should have more information about this new update as it implements more than only the voting revision. For example this new update installs a backup folder and creates a backup file automatically upon start of wallet (see Tools, Show Automatic Backups) Right now the only documentation is here: I'm about half a planet away from my development box at the moment, but when I'm back home I'll write some official documentation. tx crowning that would be great ! please post that on DCT as well that i can find it and use on the social media pages happy travels  |
|
|
|
Can someone explain me, what I have to do on which wallet cold/remote to vote with a single MN?
2 possibilities: - Open the wallet which holds the 1000 DASH, open the debug console there and type "masternode vote yea" (or masternode vote nay)
- Go to the computer which is running your Masternode daemon itself (most probably at some hosting service), open a shell and type "dashd masternode vote yea" (or nay)
(of course don't type the quotes) This is the most general case. In cases where you customized your setup (e.g. to a different path than the default Dash-folder) you will have to ask more specific questions here. |
|
|
|
I just downloaded windows zip file of the .23 wallet from Dashpay.io, or what I thought was Dashpay.io anyway, and when I run the dash-qt.exe in the 64 bit folder I get a message that says "Windows protected your PC." "Windows SmartScreen prevented an unrecognized app from starting. Running this app may put your PC at risk." When I click "more info" it says the publisher is unknown. I'm using windows 8.1 64-bit and have always used the 64-bit version of the wallet with no issues. My unzipped wallet is 28,113 KB, is that the same as some of you guys?
Download a tool which can create MD5 or SHA-256 hashes for files, like http://code.kliu.org/hashcheck/ or something similar. Create the hash (it's saved in a new file) and check against the ones provided here: https://www.dashpay.io/downloads/If they are identical, you're fine. If not, DON'T RUN/EXECUTE THAT FILE.Delete it, someone has changed it. |
|
|
|
While masternode list votes shows all the nodes, these are not working:
dashd masternode list votes | grep -c YEA
dashd masternode list votes | grep -c NAY
dashd masternode list votes | grep -c ABSTAIN
What am I doing wrong?
They don't work for me either, and I updated, so..........? I thought this chart: http://178.254.18.153/~pub/Dash/masternode_payments_stats.html would show the vote, but it doesn't. Maybe that could be included? Look again....yes, down there. Just for you, my dear. Because you're the coolest Tante around here  |
|
|
|
Does this mean that Dash version 0.11.2.23 will include the automatic backup function and will also include all fixes & additions incorporated into the Master branche on github after 11th of april 2015 (when Dash version 0.11.2.22 was released) ? If so we need perhaps a bit more documentation about this update.
i do not think that is in there this is only for the voting system , as not mandatory update i just downloaded version 0.11.2.23 and automatic backups are definetely in there, therefore we should have more information about this new update as it implements more than only the voting revision. For example this new update installs a backup folder and creates a backup file automatically upon start of wallet (see Tools, Show Automatic Backups) Right now the only documentation is here: I'm about half a planet away from my development box at the moment, but when I'm back home I'll write some official documentation. |
|
|
|
So sorry, but last time there are a lot of announcements and a little of implementations.
Even when we are in the lucky situation to have more developers than almost every other crypto-currency, the number of developers is limited and a day has just 24 hours. Feel free to join development (after all, it's open source), or if you know a good developer with some spare time send him or her here: https://dashtalk.org/threads/core-developer-contest-and-sponsor-program.4358/ |
|
|
|
Whats the latest masternode count looking like chaps?
 |
|
|
|
Hi, I just noticed that I have some pretty huge bills from amazon.aws on my masternode: more than 20$ on january and ferbuary, with tome pretty huge out data transfert: more than 150 gigas in one month.
Is that amount of data strange just for one masternode?
Mine do on average about 1.25 GB incoming and 1.30 GB outgoing traffic per day...you do the maths. |
|
|
|
best to check the size of your debug.log weekly and delete the debug.log if its getting too big or run dashd with the -printtoconsole commandline option, this will stop the debug.log from getting created but then you will not build up any debug info... your choice.
Oh lovely! Good work Just start your wallet/daemon always with the option "-shrinkdebugfile" and it will take care of this. |
|
|
|
tl:dr - masternodes are ingenious, BUT large investors will make profits that small investors can't, hence the inequality of darkcoin distribution will widen.
I 100% agree on the decentralization, spread your Masternodes out to more VPS/Masternode providers. I disagree on the inequality part, even if you just own 100 DASH you can put them into one of those excellent Masternode pooling services and gain percentage wise exactly the same (..as long as the service costs don't eat your earnings). |
|
|
|
I have a group of dev's that have been working on a service for over a year and just not getting around to growing the integration. I've reached out Evan about the service and haven't heard back. People say they want it easy but then they actually have to make the steps to become easy. From my first day in crypto I HATED public keys. They will always be the #1 turnoff for anyone. As soon as they see them, they turn off and move on. Its just too confusing. Before the great INET, we had BBS's and those BBSs had telephone numbers. No one remembered the number but they remembered the name. DNS for websites did the same and buying a domain name was might more expensive than today. Now take that and apply it to crypto. (Did I mention I HATE public keys.)
I think the idea in itself is great, but there are a couple of things I don't know how to weight them - So far I was completely happy when someone sends me his/her pubkey and I put a name on it in my wallet. But others my want more of course
- It's centralized. As long as it's not widely used (with servers and mirrors for MY domain instead of one instance having it all) that's a weak point. Servers get DDOSed/hacked/whatnot and you'd have a lot of problems.
- It kind of contradicts the "anonymous" part of Dash
But again, don't get me wrong, I think it's a cool idea. Make it P2P (e.g. each wallet serves it's own names or something like this. Or delegate it to Masternodes) and it would be perfect. |
|
|
|
Anyone have a number on MN bandwidth monthly usage, give or take ?
About 10 GB in and 10 GB out each month. Mine use between 25 GB and 40 GB (In and Out each) per month. No idea why yours need less, maybe your network connection is slower (mine have Gbit network connections). |
|
|
|
If it's up to $500 a coin, I think I'd have to liquidate at least one MN and get a new roof, new doors and windows, new car for hubby, etc... LOL. I do have my price! Then again, dollars and euros may collapse in a year for all we know! (doubtful, but I wouldn't care, I ain't got none, LOL)
If 1 DASH would be $500 right now, each of your Masternodes would give you about $225 PER DAY. I wouldn't sell! |
|
|
|
[...] Since the masternode reward will continue to climb monthly until 60%, it's only going to get worse if these new coins continue to roll into new masternodes getting compounded. For instance, at 580 masternodes currently, the entity is generating ~286 coins a day (0.494/Dash per node daily)... that means over the course of just one month, that entity can bring online another 8 masternodes (and that's just today's figures which doesn't factor in increasing rewards and compounding from new nodes). It's not hard to see how over many months that the entity will continue to increase it's coin supply ownership and composition of total masternodes.
Percentage wise it stays the same (580/(# of Masternodes) * 100) because others also get rewards and create new Masternodes. |
|
|
|
Nope, this isn't/wasn't a Litecoin-feature. Back in my Litecoin-days I wrote an external shell-script which first made a backup of wallet.dat and then started the wallet itself. This isn't exactly end-user-friendly, so I decided Dash needs something integrated into the wallet itself. |
|
|
|
Hi everybody,
Is there any news about master node blinding?
[...]
We're going to delay the implementation of masternode blinding because there's two separate mobile wallets that are in the process of implementing Darksend and the reference implementation needs to be super stable during this period of time. Once we have the mobile wallets done (which should have Darksend and InstantX support) we can move back to improving Darksend.
[...]
It's on hold right now. |
|
|
|
i thought evan said we had a week before v17 stopped getting paid. also we are only at 35% and i thought we needed 80-90% before enforcement kicked out old versions. http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.htmlshows enforcement has been 'On' since 2015-04-04-02:35:02. it's all very confusing and needs to be clarified. The page above is correct because it asks the Dash-Daemon, and the network should know BTW, the second enforcement is switched OFF some people start cheating and don't pay Masternodes any more. So, as long as everything's green here: https://dashninja.pl/blocks.html#blocksdetail you can be 100% sure that it's ON. |
|
|
|
|
Show Posts
