|
CryptoSiD
|
 |
August 14, 2015, 06:14:51 PM |
|
SuchPool now running 0.12.0.44
|
|
|
|
|
emmo
Newbie
 Offline
Activity: 53
Merit: 0
|
|
August 14, 2015, 06:15:11 PM |
|
64bit lnx version ?
|
|
|
|
|
GilAlexander
Member
Offline
Activity: 68
Merit: 10
|
|
August 14, 2015, 06:15:28 PM |
|
|
|
|
|
|
qwizzie
Legendary
Offline
Activity: 2548
Merit: 1245
|
|
August 14, 2015, 06:15:46 PM |
|
SuchPool now running 0.12.0.44
damn yr fast  thanks |
Learn from the past, set detailed and vivid goals for the future and live in the only moment of time over which you have any control : now
|
|
|
emmo
Newbie
Offline
Activity: 53
Merit: 0
|
|
August 14, 2015, 06:18:24 PM |
|
Thx,-reindex on both side or only local wallet(del mncache and peers) ?
|
|
|
|
|
|
CryptoSiD
|
|
August 14, 2015, 06:18:31 PM |
|
SuchPool now running 0.12.0.44
damn yr fast thanks Was waiting for this:) |
|
|
|
|
|
CryptoSiD
|
|
August 14, 2015, 06:19:00 PM |
|
Thx,-reindex on both side or only local wallet(del mncache and peers) ?
Gotta reindex every wallet else dash just stop |
|
|
|
|
|
spatula
|
|
August 14, 2015, 06:19:11 PM |
|
Please don't use download links on bitcointalk.... use official site ONLY. Malware is often pushed by scammers this way. |
|
|
|
|
Macno
Legendary
Offline
Activity: 984
Merit: 1000
|
|
August 14, 2015, 06:20:00 PM |
|
Are there currently known issues with the Android wallet? Trying to send some Dash to directbet, but 2 tx are still unconfirmed after 15 mins (1 with InstantX, one without).
Perfect timing for my little betting problem... Congrats for V12! |
|
|
|
|
qwizzie
Legendary
Offline
Activity: 2548
Merit: 1245
|
|
August 14, 2015, 06:21:20 PM |
|
https://dashtalk.org/threads/v12-release.5888/#post-63280from tungfa : Win64 installer is on now
Evan just updated
Available on official site to download (both the windows 64bit installer and the windows 64bit zip file)
|
Learn from the past, set detailed and vivid goals for the future and live in the only moment of time over which you have any control : now
|
|
|
|
Kienbui
|
|
August 14, 2015, 06:24:01 PM |
|
Exciting! It takes long time of waiting for this release. Thanks and congratulation Evan and the dev team! |
|
|
|
|
GhostPlayer
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
August 14, 2015, 06:30:22 PM |
|
Hahahaha!! Brilliant! Seriously, for how long have you been holding onto that gif? |
|
|
|
|
|
minersday
|
|
August 14, 2015, 06:38:26 PM |
|
Oh yeah V12  |
|
|
|
|
|
kadrek
|
|
August 14, 2015, 06:38:50 PM |
|
I'm updating to V12 and started dashd on my VPS and then after a short while I got the message "You need to rebuild the database using -reindex to change -txindex. Do you want to rebuild the block database now?" I entered "yes" and now it's just printing a bunch of y's. Is this normal? I also tried to do ./dashd getinfo but it said something about RPC calls or something not being supported anymore and to use dash-cli? How do I do ./dashd getinfo now? Sorry for the newb questions  Edit: I'm using the 64 bit version if it matters. |
SWIPE │ │ │ Monetizing mobile engagement data, on the blockchain [ SWIPE . WHITEPAPER ] TELEGRAM TWITTER MEDIUM REDDIT |
|
|
Lebubar
Legendary
Offline
Activity: 1288
Merit: 1000
|
|
August 14, 2015, 06:49:36 PM |
|
I'm updating to V12 and started dashd on my VPS and then after a short while I got the message "You need to rebuild the database using -reindex to change -txindex. Do you want to rebuild the block database now?" I entered "yes" and now it's just printing a bunch of y's. Is this normal? I also tried to do ./dashd getinfo but it said something about RPC calls or something not being supported anymore and to use dash-cli? How do I do ./dashd getinfo now? Sorry for the newb questions Edit: I'm using the 64 bit version if it matters. I'm at work, so don't have the exact syntax but, all command are now execute through dash-cli and not directly with the deamon. so it should be something like : dash-cli getinfo. Also apparently better to re-index directly while execute the new version (and remove peer.dat) (same not sure if still exist and can't verify right now): ./dahsd --reindex |
|
|
|
|
|
kadrek
|
|
August 14, 2015, 06:51:02 PM |
|
I'm updating to V12 and started dashd on my VPS and then after a short while I got the message "You need to rebuild the database using -reindex to change -txindex. Do you want to rebuild the block database now?" I entered "yes" and now it's just printing a bunch of y's. Is this normal? I also tried to do ./dashd getinfo but it said something about RPC calls or something not being supported anymore and to use dash-cli? How do I do ./dashd getinfo now? Sorry for the newb questions Edit: I'm using the 64 bit version if it matters. I'm at work, so don't have the exact syntax but, all command are now execute through dash-cli and not directly with the deamon. so it should be something like : dash-cli getinfo. Also apparently better to re-index directly while execute the new version (and remove peer.dat) (same not sure if still exist and can't verify right now): ./dahsd --reindex Hmm, okay thanks. It's still printing a seemingly endless stream of y's and I don't know how to stop it lol. Would rebooting it be a good idea? Edit: Would it just be "rm ./dashd/peers.dat" to delete it? |
SWIPE │ │ │ Monetizing mobile engagement data, on the blockchain [ SWIPE . WHITEPAPER ] TELEGRAM TWITTER MEDIUM REDDIT |
|
|
Minotaur26
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
August 14, 2015, 06:54:38 PM |
|
Hahahaha!! Brilliant! Seriously, for how long have you been holding onto that gif?  |
|
|
|
|
TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
August 14, 2015, 06:55:43 PM |
|
We're definitely open to improving the pool distribution if anyone has ideas. However, PoS is incompatible with anything that uses masternode quorums. The quorums are chosen based off of the proof-of-work hash, so if we were to switch to a proof-of-stake model, we would end up with less secure hashes and other issues that would have to be addressed. That would allow an attacker to pick the masternodes that approve a transaction lock for example, something that we definitely want to avoid.
I have a weird idea, and no idea if it's possible: What if the wallet used to mine (there is always a wallet, no?) checked to see if the hash on it was below 50% (or 40, whatever) of total hashrate. And if it isn't, it would be blocked from competing for a block? If pools ended up with wasted hash due to not watching their hash rate %, I think they'd invent a way to keep their hashrate down fast. But as for Dash, we just have to block >50% hashrate wallets from winning blocks. make any sense? |
Another proud lifetime Dash Foundation member  My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d |
|
|
TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
August 14, 2015, 06:59:24 PM |
|
Hahahaha!! Brilliant! Seriously, for how long have you been holding onto that gif? Oh WOW, I just had my crankshaft replaced and it's so cool to see how it works! Gonna save that one (but I only have 4 cylinders, LOL) |
Another proud lifetime Dash Foundation member My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d |
|
|
coins101
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
August 14, 2015, 07:00:07 PM |
|
We're definitely open to improving the pool distribution if anyone has ideas. However, PoS is incompatible with anything that uses masternode quorums. The quorums are chosen based off of the proof-of-work hash, so if we were to switch to a proof-of-stake model, we would end up with less secure hashes and other issues that would have to be addressed. That would allow an attacker to pick the masternodes that approve a transaction lock for example, something that we definitely want to avoid.
I have a weird idea, and no idea if it's possible: What if the wallet used to mine (there is always a wallet, no?) checked to see if the hash on it was below 50% (or 40, whatever) of total hashrate. And if it isn't, it would be blocked from competing for a block? If pools ended up with wasted hash due to not watching their hash rate %, I think they'd invent a way to keep their hashrate down fast. But as for Dash, we just have to block >50% hashrate wallets from winning blocks. make any sense? Nice idea. But it probably breaks every principle of decentralization. Keep scratching that head though, you're probably on to something. |
|
|
|
|
|
