Glad you were able to open yours. I got an out of memory failure
V12 Testing Thread
- Thread starter eduffield
- Start date
moli there is no real way of getting rid of flare's proposals in current system so basically he succeeded in attacking the network that way imo (which is nice, at least way better if someone would succeed in mainnet 
). Testnet is basically overloaded and that means that we need to implement it in another way. I had a talk with Evan and I think he is on it.
Anyway thanks for you efforts but I guess until next version client is half-dead because it tries to process such proposals over and over again.
PS. I need to test some other things so currently I just completely ignore his proposals by this dirty cheat in my code
If you can compile then that should help you (kill budget.dat also), otherwise just wait for the next version.
). Testnet is basically overloaded and that means that we need to implement it in another way. I had a talk with Evan and I think he is on it.Anyway thanks for you efforts but I guess until next version client is half-dead because it tries to process such proposals over and over again.
PS. I need to test some other things so currently I just completely ignore his proposals by this dirty cheat in my code
Code:
diff --git a/src/masternode-budget.cpp b/src/masternode-budget.cpp
index 2f619bd..cdd20f3 100644
--- a/src/masternode-budget.cpp
+++ b/src/masternode-budget.cpp
@@ -430,6 +430,8 @@ void CBudgetManager::AddProposal(CBudgetProposal& budgetProposal)
return;
}
+ if(budgetProposal.GetName().find("flare") != string::npos) return; // LOL :D
+
if(mapProposals.count(budgetProposal.GetHash()) && mapProposals[budgetProposal.GetHash()].vin != budgetProposal.vin) {
//this budget proposal must have went invalid, so update the vin to the new one
LogPrintf("CBudgetManager::AddProposal -- updated vin of invalid budget proposal %s (%s to %s)\n",
moli
Well-known member
Great, flare, thanks a lot! :tongue::grin:moli there is no real way of getting rid of flare's proposals in current system so basically he succeeded in attacking the network that way imo (which is nice, at least way better if someone would succeed in mainnet
Anyway thanks for you efforts but I guess until next version client is half-dead because it tries to process such proposals over and over again.
PS. I need to test some other things so currently I just completely ignore his proposals by this dirty cheat in my code
If you can compile then that should help you (kill budget.dat also), otherwise just wait for the next version.Code:diff --git a/src/masternode-budget.cpp b/src/masternode-budget.cpp index 2f619bd..cdd20f3 100644 --- a/src/masternode-budget.cpp +++ b/src/masternode-budget.cpp @@ -430,6 +430,8 @@ void CBudgetManager::AddProposal(CBudgetProposal& budgetProposal) return; } + if(budgetProposal.GetName().find("flare") != string::npos) return; // LOL :D + if(mapProposals.count(budgetProposal.GetHash()) && mapProposals[budgetProposal.GetHash()].vin != budgetProposal.vin) { //this budget proposal must have went invalid, so update the vin to the new one LogPrintf("CBudgetManager::AddProposal -- updated vin of invalid budget proposal %s (%s to %s)\n",
But yes I agree, I'm glad we found this out on Testnet... Wallets can't sync properly.. After a shutdown if i want to restart them i have to delete mncache.dat, budget.dat, and peers.dat every single time. The "flare zombies" don't seem to go away.. lol
flare
Well-known member
You are welcome :grin:
moli
Well-known member
LOL.... Are we going to get a new Testnet? You know, this is fun. Evan broke Testnet once, now you did it too. Soon it should be Udjin's turn, and then Crowning's turn... lol... :grin:
flare
Well-known member
We have to wait for the next version, there is currently no way to get rid of my 15.000 proposals, they even survive a protocol bump afaik.
moli
Well-known member
15,000 proposals???!!!!! How could you manage to send that many? lol.... I thought maybe you got only a few hundred proposals.. (Only around 121 proposals to down vote on the list Evan posted.)
flare
Well-known member
Make it 25,000 - i was young and needed the money
Code:
ubuntu@install:~$ dash-cli mnbudget show | grep { | wc -l
25437moli
Well-known member
ROFL......Make it 25,000 - i was young and needed the money
Code:ubuntu@install:~$ dash-cli mnbudget show | grep { | wc -l 25437
TaoOfSatoshi
Well-known member
It's fun to break things....
Great, I'm keeping my eye out here each time I sit down
If I may be annoying, I have a request :
Can we please have a way to see how many DASH were not mined but rather have potential to be mined for the payments of approved projects? This way everyone can see what is being spent and what is still available. It helps in making decisions. Thanks
As it is, I just can't tell if people are able to get projects paid even after we've exceeded the allotted block rewards.
I'm also curious how projects will work out if, say the first three projects were approved, and it takes up most of the 10% allowed, but in comes a 4th project that gets the highest votes, thereby kicking off one or more of the other 3 projects from payment status (if we are really implementing a voting hierarchy for green lighted projects) This could ruin projects already started and cause all kinds of disruption. Is there a fail-safe to keep this from happening?
Can we please have a way to see how many DASH were not mined but rather have potential to be mined for the payments of approved projects? This way everyone can see what is being spent and what is still available. It helps in making decisions. Thanks
As it is, I just can't tell if people are able to get projects paid even after we've exceeded the allotted block rewards.
I'm also curious how projects will work out if, say the first three projects were approved, and it takes up most of the 10% allowed, but in comes a 4th project that gets the highest votes, thereby kicking off one or more of the other 3 projects from payment status (if we are really implementing a voting hierarchy for green lighted projects) This could ruin projects already started and cause all kinds of disruption. Is there a fail-safe to keep this from happening?
Last edited by a moderator:
Slowly cleaning todo list :smile:
Try also to break your masternode.conf like you did it before https://dashtalk.org/threads/reuben...allet-guide-start-many.4034/page-3#post-59209
https://github.com/dashpay/dash/pull/420 :wink:
moli
Well-known member
Thanks so much! Will try to add more to your todo list for you! lol
Btw, Udjin, it seems flare 's proposals are gone? I've had that wallet running all night and it's not grinding my computer cpu, dash-qt.exe is running almost at 0% on the windows task manager.... Something is not right, it's too quiet, seems too nice... I'm going to miss these "flare zombies".... lol....
EDIT: When i shut down the wallet it shut down fast, not laggy like before... It seems back to normal now.. Where/how did all these "flare proposals" disappear? lol
Last edited by a moderator:
flare
Well-known member
Maybe the code which should have removed the "inavalid" proposals was finally working - with a delay of 3 days
moli
Well-known member
UdjinM6 eduffield flare - Testnet hasn't found a new block the last two hours, being stuck at block 82128:
http://test.explorer.darkcoin.qa/chain/tDarkcoin
http://test.insight.dash.siampm.com/
http://test.explorer.darkcoin.qa/chain/tDarkcoin
http://test.insight.dash.siampm.com/