TestNet Update - v12.0.29 - TESTNET ONLY!
eduffield
- Implement planned hard forks, August 24, 2015
- Masternode inv messages / save seen in mncache
- only take newest votes
- Fixed budget syncing issues / forking issues / syncing issues …
- Budgets now store the seen objects locally so they're not overwritten when saving/loading to check validity of budget.dat
- Added safer sync "failure" mode, that will retry an hour later if the sync fails for some reason. This will stop the client from thinking it has budget data and rejecting blocks when they're valid.
- protocol bump
- version bump
UdjinM6
- more info for masternode count output/rpcconsole dialog
- include lastPing in mnb hash calculation
We're getting pretty close to having something stable for mainnet. Please update if you're helping out testing!
https://dashtalk.org/threads/v12-testing-thread.5484/page-87#post-60851
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 2012. (Read 9723748 times)
July 25, 2015, 03:38:31 PM
July 25, 2015, 03:22:49 PM
Mike Tyson Bitcoin ATM
Coming August 2015
http://www.miketysonbitcoin.com/
https://twitter.com/MikeTyson/status/624986928690036737
Mike Tyson’s fastest knock out in the ring was 30 seconds.
The Mike Tyson Bitcoin ATM can turn your cash into bitcoin in under 20 seconds.
Coming August 2015
http://www.miketysonbitcoin.com/
https://twitter.com/MikeTyson/status/624986928690036737
Mike Tyson’s fastest knock out in the ring was 30 seconds.
The Mike Tyson Bitcoin ATM can turn your cash into bitcoin in under 20 seconds.
July 25, 2015, 10:23:05 AM
hello, can anyone give me a list of tor onion nodes to add to the conf?
thanks
addnode=xx.xx.x.x.x
bumpthanks
addnode=xx.xx.x.x.x
wrwx2dy7jyh32o53.onion
July 25, 2015, 03:58:56 AM
...Trillions marketcap...
I love that part...Lol 
July 25, 2015, 03:55:26 AM
Good news,
Bitcoin's "current managers" are going to turn it from "currency application" (Dollar, Euro, ... competitor) to "transaction application" (competitor to SWIFT, GooglePay, ApplePay and hundreds others) - (Phase 4) THE FIVE PHASES OF BITCOIN
So it will be easy for Dash to win place of "Best Cryptocurrency = Digital Cash" (with Trillions marketcap), and let Bitcoin compete with other "Best smart-contract service-provider and other non-currency application" (with Billions market cap).
Bitcoin's "current managers" are going to turn it from "currency application" (Dollar, Euro, ... competitor) to "transaction application" (competitor to SWIFT, GooglePay, ApplePay and hundreds others) - (Phase 4) THE FIVE PHASES OF BITCOIN
So it will be easy for Dash to win place of "Best Cryptocurrency = Digital Cash" (with Trillions marketcap), and let Bitcoin compete with other "Best smart-contract service-provider and other non-currency application" (with Billions market cap).
July 25, 2015, 03:53:19 AM
Hey, this could work. Rotating tires with EMdrives in the rims! Excellent, I'll take 5!
July 25, 2015, 03:20:21 AM
New Testnet Version 
v0.12.0.28
- InstantX works 100% of the time now
- DarkSend is super fast
- We are running 100% with no reference node
- We fixed lots of small consensus issues with InstantX/DS/Masternode Payments
https://dashtalk.org/threads/v12-testing-thread.5484/
We're getting pretty close to having a solid v12 release.
Thank you and the team for the hard work! v0.12.0.28- InstantX works 100% of the time now
- DarkSend is super fast
- We are running 100% with no reference node
- We fixed lots of small consensus issues with InstantX/DS/Masternode Payments
https://dashtalk.org/threads/v12-testing-thread.5484/
We're getting pretty close to having a solid v12 release.
July 25, 2015, 12:23:25 AM
i already posted this on dashtalk forum but maybe someone knows a fix to my problem in here :
After rebooting two of my server instances in order to perform network updates on them, one of my instances shows
POS_ERROR when trying to masternode list grep IP it. The other had no problem after restarting ./dashd
The one with the POS_ERROR still has POS score 0 on dashninja.pl but i'm getting worried now.
I checked firewall and its still has port 9999 open, anything else i can do ?
After rebooting two of my server instances in order to perform network updates on them, one of my instances shows
POS_ERROR when trying to masternode list grep IP it. The other had no problem after restarting ./dashd
The one with the POS_ERROR still has POS score 0 on dashninja.pl but i'm getting worried now.
I checked firewall and its still has port 9999 open, anything else i can do ?
I had that same issue but it was on my Pi
corrupted card
Re-imaged the card
all good
Never could figure out what the issue was - I can only assume: corrupted card
sorry - I know that's not gonna help -ugh
You can also try deleting blocks/chainstate then syncing from scratch (or from a bootstrap). I think the issue is usually related to corruption of some sort.
okay, the "delete everything but wallet.dat and dash.conf and letting it sync from bootstrap" did it for me. it now shows ENABLED in both PUTTY and in your masternode status list.
thanks for the advice and for the https://www.dashpay.io/binaries/masternodes.txt link, its a very usefull link
Everyone who has late MN payments or just want to reassure themself should check that masternode status list to see if their masternode is enabled in there. The masternodes are mentioned there per transaction id of your 1000 dash vin, so copy the transaction id of your own 1000 vin from your cold wallet, open the link and then press CTRL F and paste the transaction id in there. If it shows "ENABLED" your masternode is scheduled for payment,
if it shows POS_ERROR you have a problem with that masternode. Try to do then what i did (delete blockchain and sync from bootstrap).
Dash Bootstrap can be found here : https://github.com/UdjinM6/dash-bootstrap
July 24, 2015, 11:26:56 PM
New Testnet Version v0.12.0.28
- InstantX works 100% of the time now
- DarkSend is super fast
- We are running 100% with no reference node
- We fixed lots of small consensus issues with InstantX/DS/Masternode Payments
https://dashtalk.org/threads/v12-testing-thread.5484/
We're getting pretty close to having a solid v12 release.
v0.12.0.28- InstantX works 100% of the time now
- DarkSend is super fast
- We are running 100% with no reference node
- We fixed lots of small consensus issues with InstantX/DS/Masternode Payments
https://dashtalk.org/threads/v12-testing-thread.5484/
We're getting pretty close to having a solid v12 release.
July 24, 2015, 07:37:16 PM
New Testnet Version v0.12.0.28
- InstantX works 100% of the time now
- DarkSend is super fast
- We are running 100% with no reference node
- We fixed lots of small consensus issues with InstantX/DS/Masternode Payments
https://dashtalk.org/threads/v12-testing-thread.5484/
We're getting pretty close to having a solid v12 release.
v0.12.0.28- InstantX works 100% of the time now
- DarkSend is super fast
- We are running 100% with no reference node
- We fixed lots of small consensus issues with InstantX/DS/Masternode Payments
https://dashtalk.org/threads/v12-testing-thread.5484/
We're getting pretty close to having a solid v12 release.
The fully decentralised masternode payment system is a big leap forward, it consolidates the paid full node operation concept. Thanks for all the hard work, onwards and upwards.
July 24, 2015, 07:32:18 PM
New Testnet Version v0.12.0.28
- InstantX works 100% of the time now
- DarkSend is super fast
- We are running 100% with no reference node
- We fixed lots of small consensus issues with InstantX/DS/Masternode Payments
https://dashtalk.org/threads/v12-testing-thread.5484/
We're getting pretty close to having a solid v12 release.
v0.12.0.28- InstantX works 100% of the time now
- DarkSend is super fast
- We are running 100% with no reference node
- We fixed lots of small consensus issues with InstantX/DS/Masternode Payments
https://dashtalk.org/threads/v12-testing-thread.5484/
We're getting pretty close to having a solid v12 release.
July 24, 2015, 07:06:00 PM
Peter Todd is a professional cryptographer and computer scientist.
PT has no reason to "fear" Dash. But he does have a duty to point out the fraud when he sees your cargo cult selling "snake oil,"1 "bad crypto,"2 and "bamboo runways."3
Citations:
1. Peter Todd calls dash snake oil.
2. Peter Todd calls dash "bad crypto."
3. Peter Todd calls dash's instant-x fake.
PT has no reason to "fear" Dash. But he does have a duty to point out the fraud when he sees your cargo cult selling "snake oil,"1 "bad crypto,"2 and "bamboo runways."3
Citations:
1. Peter Todd calls dash snake oil.
2. Peter Todd calls dash "bad crypto."
3. Peter Todd calls dash's instant-x fake.
...and not a monetary analyst which is why he can't tell a bookkeeping system apart from a new form of electronic base monetary media.
I think he just didn't understand the quorum system's security model, which is very complicated. That's OK, the nice thing is DarkSend, InstantX and the governance system will work whether he understands them or not. It's more of a complement that what we're working on is so different/novel than Bitcoin that the developers themselves have no idea how it functions.
"Very complicated" is our first clue that your security model sucks, and the second is your assumption Peter Todd cannot understand complexity.
Security in obscurity and trusted third party quorum are not acceptable practices. Same goes for centralized reference nodes, etc.
Granted, building cargo cult-like bamboo copies of Green and Stealth addresses is very "different/novel than Bitcoin."
July 24, 2015, 06:56:35 PM
i already posted this on dashtalk forum but maybe someone knows a fix to my problem in here :
After rebooting two of my server instances in order to perform network updates on them, one of my instances shows
POS_ERROR when trying to masternode list grep IP it. The other had no problem after restarting ./dashd
The one with the POS_ERROR still has POS score 0 on dashninja.pl but i'm getting worried now.
I checked firewall and its still has port 9999 open, anything else i can do ?
After rebooting two of my server instances in order to perform network updates on them, one of my instances shows
POS_ERROR when trying to masternode list grep IP it. The other had no problem after restarting ./dashd
The one with the POS_ERROR still has POS score 0 on dashninja.pl but i'm getting worried now.
I checked firewall and its still has port 9999 open, anything else i can do ?
I had that same issue but it was on my Pi
corrupted card
Re-imaged the card
all good
Never could figure out what the issue was - I can only assume: corrupted card
sorry - I know that's not gonna help -ugh
You can also try deleting blocks/chainstate then syncing from scratch (or from a bootstrap). I think the issue is usually related to corruption of some sort.
July 24, 2015, 06:52:47 PM
Peter Todd is a professional cryptographer and computer scientist.
...and not a monetary analyst which is why he can't tell a bookkeeping system apart from a new form of electronic base monetary media.
I think he just didn't understand the masternode quorum system's security model, it's not very complicated but it's a brand new model compared to the blockchain. That's OK, the nice thing is DarkSend, InstantX and the governance system will work whether he understands them or not. It took years for the general public to understand that Bitcoin wasn't a scam/breakable, it will probably take the same amount of time. I'm going to start doing a lot more presentations and videos about how all of this works to educate, hopefully that helps.
July 24, 2015, 06:48:59 PM
@eduffield
Ive been having issues running dashd over tor, i thing it is maybe due to a lack of tor compatible seednodes
my config is:
yet i cant connect to other nodes
Ive been having issues running dashd over tor, i thing it is maybe due to a lack of tor compatible seednodes
my config is:
Code:
proxy=127.0.0.1:9050
yet i cant connect to other nodes
July 24, 2015, 06:47:25 PM
I looked at the soon-to-be-removed reference node and everything looks OK.
I thought the centralized reference node was already gone.
Will its removal be a smooth process, or an unworkable disaster like the time you tried to implement masternode blinding?
July 24, 2015, 06:17:38 PM
Two of my nodes have not been payed in 8 days now 
with proof of service score of 0
am I just unlucky
with proof of service score of 0am I just unlucky
I looked at the soon-to-be-removed reference node and everything looks OK. The next version of the software has a much improved implementation of the payment system ,so we shouldn't have these issues anymore (plus it's 100% decentralized
).I've made what the reference node sees available at the following link: https://www.dashpay.io/binaries/masternodes.txt
The goal is to get on this list and not have a POS ERROR. If you have a POS ERROR, there's something wrong with your network connection / on a blockchain fork / etc. If you're not on the list at all, try stopping your masternode for a couple hours, then restarting it. If that doesn't work, try moving the money to a new vin.
The link is updated every minute, so it should be accurate
July 24, 2015, 06:12:22 PM
i already posted this on dashtalk forum but maybe someone knows a fix to my problem in here :
After rebooting two of my server instances in order to perform network updates on them, one of my instances shows
POS_ERROR when trying to masternode list grep IP it. The other had no problem after restarting ./dashd
The one with the POS_ERROR still has POS score 0 on dashninja.pl but i'm getting worried now.
I checked firewall and its still has port 9999 open, anything else i can do ?
After rebooting two of my server instances in order to perform network updates on them, one of my instances shows
POS_ERROR when trying to masternode list grep IP it. The other had no problem after restarting ./dashd
The one with the POS_ERROR still has POS score 0 on dashninja.pl but i'm getting worried now.
I checked firewall and its still has port 9999 open, anything else i can do ?
If nothing else changed, you're still using the same keys, then someone could have missed you while your were down. If that is the case, it should resolve in a short time. Keep an eye on your PoSe score, if it stays the same or drops, you should be fine. Unless you have a super high score like 4+ I would just keep an eye on it as it should soon drop??
July 24, 2015, 04:47:11 PM
hello, can anyone give me a list of tor onion nodes to add to the conf?
thanks
addnode=xx.xx.x.x.x
bump thanks
addnode=xx.xx.x.x.x
July 24, 2015, 04:10:22 PM
i already posted this on dashtalk forum but maybe someone knows a fix to my problem in here :
After rebooting two of my server instances in order to perform network updates on them, one of my instances shows
POS_ERROR when trying to masternode list grep IP it. The other had no problem after restarting ./dashd
The one with the POS_ERROR still has POS score 0 on dashninja.pl but i'm getting worried now.
I checked firewall and its still has port 9999 open, anything else i can do ?
After rebooting two of my server instances in order to perform network updates on them, one of my instances shows
POS_ERROR when trying to masternode list grep IP it. The other had no problem after restarting ./dashd
The one with the POS_ERROR still has POS score 0 on dashninja.pl but i'm getting worried now.
I checked firewall and its still has port 9999 open, anything else i can do ?
Jump to: