Search results

Hi! Please don't bring that kind of "dropbox" in the dash evolution. This will open any sort of new attacks, using files. And this will divert from being a currency to something else.. And the technology is something very very last year, mean the file drive thing.. if you have to make a case...

A Tricky Path to Quantum-Safe Encryption: https://www.quantamagazine.org/20150908-quantum-safe-encryption/ So, bitcoin will go down the drain after quantum computer surface, what about X11 it's more tricky cause of the multiple algorithms? and check out the quantum-secure cryptography picture...

I would love the update to be built into dashd... so just a command like dashd update-binaries --iamsure =D

Seems like nmarley said earlier the same thing...

If I am not completely mistaken, the latest bootstrap file is already reindexed?, just start the daemon up.

Morning, I would recommend to update to .46, compile from source.

have you tried getting the bootstrap? https://github.com/UdjinM6/dash-bootstrap

I would recommend the people who are having problems to compile the .46-version from the source (it's been committed to master source) what I have observed it working on my masternodes (half-a-day), lower CPU/MEM/Net-usage, without the sawing of these we saw earlier.. edit: seems like 11.5%...

Do you have mem usage graph?

Do you have mem usage graph?

There's really something happening after two days of running masternodes. I don't have the problem because I host the nodes myself and enough resources and nobody's throttling them. CPU after two day's of .45 release: Memory after two day's of .45 release: From masternode top -H, command...

You need to have 32-bit libraries installed on your 64-bit system. That's why it says the error you are seeing.

This version works perfectly! Yes, looking very good now!

hmm binaries are at 120044.. should be 120045?

Opened an issue to github repo...

Don't know if it's from BOOST_FOREACH doing the dseep looping, maybe wait/sleep has to be in there?

and when it's not hogging all the CPU it's doing this (same process thread, dash-msghand): utex(0x7f615b513d94, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 34140473, {1439662667, 559634671}, ffffffff) = -1 ETIMEDOUT (Connection timed out) futex(0x7f615b513d68, FUTEX_WAKE_PRIVATE, 1) = 0...

and from another masternode same CPU hogging: sendto(29, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0;\6\316I\2362\33w\366o0S"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140 sendto(23, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0;\6\316I\2362\33w\366o0S"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) =...

The CPU hogging dashd thread is, please fix it, if possible: from top -H: 21921 xxxxx 22 2 908200 179908 36092 R 58.1 8.8 49:39.70 dash-msghand getting messages like this, continious flood, like screen is scrolling as fast as it can.. strace -p 21921: endto(39...

--- dash-cli masternode status "status" : 4, "notCapableReason" : "Could not find suitable coins!" and not showing up on masternode list... Seems like it's very much dependent when you give the masternode start command, like start the cold wallet, wait for it to start (dash-cli getinfo and see...