@DavinciJ15: I think it's better switch to the default client until there is an update so that there is a synchronized switch to merged mining.
Topic: [20 gh] NMCBit pool 3% fee prop 6.6% PPS - page 25. (Read 63693 times)
Sorry, I deleted my previous post.
@DavinciJ15: I think it's better switch to the default client until there is an update so that there is a synchronized switch to merged mining.
@DavinciJ15: I think it's better switch to the default client until there is an update so that there is a synchronized switch to merged mining.
So,
The attack has been called off because people came together. Our Davinci is a "hero" according to the attacker....
We now have a forked chain,
what are we gonna do
Start with the real merged-mining or see everyone lose interest in mining NameCoins again and wait till Christmas 2013
before the difficulty comes down ?
Plan of action
Brat
The attack has been called off because people came together. Our Davinci is a "hero" according to the attacker....
We now have a forked chain,
what are we gonna do
Start with the real merged-mining or see everyone lose interest in mining NameCoins again and wait till Christmas 2013
before the difficulty comes down ?Plan of action
Brat
NodeMaster and slush told me that they got doublec to agree and it made sense to me, the only way to get hashing power is to pay bitcoins so forking the block chain seems right, we can deal with the fallout later.
Does this mean NodeMasters EUNameCoin pool and Slush support this and are our fork as well ?
I wasn't even aware Slush was close to implementing merged mining
But that does that mean you forked the chain ?
Your namecoind software is useless you need a new version.
One that does not exit yet. Currently the version people are supposed to be upgrading to is 0.3.24.62
and any version from .60 to .62 would work together and support the last dot-bit official changes.
https://github.com/vinced/namecoin/ for the source, or if you trust my binaries
http://www.wuala.com/jbw9/pub/Bitcoin/namecoin/nc0.3.24.62/
And how will that stop the 51% attack from taking place. There's still not nearly enough hashing power to prevent that. Only adaption by a few large pools will be able to.
People want bitcoins not namecoins so it's easier to offer bitcoins when all namecoin pools are mining them.
I was the only one offering bitcoins while mining namecoins but if all pools can offer bitcoins we have a better chance as I'm not the only one hashing with 100% of the power. I was for a while the only one finding blocks on the namecoin network.
[/quote]
It may be easier, but you have now in effect attacked the current main namecoins branch.
Getting really confusing now
I've spent the last hour reading the Dot-BIT forum and it seems there's not a real coordinated effort to step up to the challenge....
you are right none of the namecoin developers are speaking to the pool operators, they have ignored my PM as if they are to busy to speak to me. That is ridiculous since the community is to small for this kind of behavior on their part.
BTW:
However what we did was not good it means anyone who traded in namecoins on the primary chain in the last 12 hrs will have their trades invalidated on our chain. If the developers do not go along with our changes this will get UGLY.
Davinci
[/quote]
It means more then just that, it means either everyone trading and mining on the official client gets screwed, or you guys do.... I hope they don't agree to let to rogue pools force their way over people using the official client.
I talked to doublec between those posts, seems they lied to you then. He did not change.
BTW, there are more then 3 pools.
OH BOY! This is going to get UGLY.
Here are the changes to my client I manually changed 3.24.62 as the code base was better. I ignored the lockins on this diff and used 3.24.62 lockins...
Code:
diff -ur namecoin/src/namecoin.cpp namecoin-0.3.24.61.18950-mergedmine-REAL/src/src/namecoin.cpp
--- namecoin/src/namecoin.cpp 2011-09-13 15:14:55.000000000 +0200
+++ namecoin-0.3.24.61.18950-mergedmine-REAL/src/src/namecoin.cpp 2011-09-13 12:29:00.000000000 +0200
@@ -95,7 +95,8 @@
{
if (fTestNet)
return 0;
- return 19200;
+// return 19200;
+ return 18950;
}
string GetAlertPubkey1()
@@ -1685,11 +1686,17 @@
int CNamecoinHooks::LockinHeight()
{
- return 0;
+ if (fTestNet)
+ return 0;
+
+ return 18938;
}
bool CNamecoinHooks::Lockin(int nHeight, uint256 hash)
{
+ if (!fTestNet)
+ if ((nHeight == 18938 && hash != uint256("0x0000000000001610e3ea22652e56fe457f207ee49deb7cbb3035a885cf4d61b1")))
+ return false;
return true;
}
Only in namecoin-0.3.24.61.18950-mergedmine-REAL/src/src: namecoind
diff -ur namecoin/src/rpc.cpp namecoin-0.3.24.61.18950-mergedmine-REAL/src/src/rpc.cpp
--- namecoin/src/rpc.cpp 2011-09-13 15:14:55.000000000 +0200
+++ namecoin-0.3.24.61.18950-mergedmine-REAL/src/src/rpc.cpp 2011-09-13 12:29:00.000000000 +0200
@@ -454,6 +454,7 @@
obj.push_back(Pair("keypoololdest", (boost::int64_t)pwalletMain->GetOldestKeyPoolTime()));
obj.push_back(Pair("paytxfee", ValueFromAmount(nTransactionFee)));
obj.push_back(Pair("errors", GetWarnings("statusbar")));
+ obj.push_back(Pair("merged-mine", 18950 ));
return obj;
}
So where do we go from here?
...told me that they got doublec to agree and it made sense to me, the only way to get hashing power is to pay bitcoins so forking the block chain seems right, we can deal with the fallout later.
I agreed that it would be good to start early and was willing to do so as long as the namebit people were involved and the time traveling attack was fixed. This is what I sent in an email to someone who contacted me about it:Quote
I'd like to see the namebit.org people involved in any reduction in
the block count. Contact 'bougyman' or 'manveru' in #namebit or see
contact details on namebit.org.
It'd also be good to get a fix for ArtForz's Geist Geld attack
otherwise a >51% attacker can generate namecoins much faster than
normal and keep difficulty low. They can do this during merged mining
'for free' because they're earning bitcoins at the same time:
https://bitcointalksearch.org/topic/possible-way-to-make-a-very-profitable-50-plus-ish-attack-for-pools-43692
the block count. Contact 'bougyman' or 'manveru' in #namebit or see
contact details on namebit.org.
It'd also be good to get a fix for ArtForz's Geist Geld attack
otherwise a >51% attacker can generate namecoins much faster than
normal and keep difficulty low. They can do this during merged mining
'for free' because they're earning bitcoins at the same time:
https://bitcointalksearch.org/topic/possible-way-to-make-a-very-profitable-50-plus-ish-attack-for-pools-43692
I never heard back from vinced so did not update to the new block number for merged mining.
But that does that mean you forked the chain ?
Your namecoind software is useless you need a new version.
And how will that stop the 51% attack from taking place. There's still not nearly enough hashing power to prevent that. Only adaption by a few large pools will be able to.
People want bitcoins not namecoins so it's easier to offer bitcoins when all namecoin pools are mining them.
I was the only one offering bitcoins while mining namecoins but if all pools can offer bitcoins we have a better chance as I'm not the only one hashing with 100% of the power. I was for a while the only one finding blocks on the namecoin network.
Getting really confusing now
I've spent the last hour reading the Dot-BIT forum and it seems there's not a real coordinated effort to step up to the challenge....
you are right none of the namecoin developers are speaking to the pool operators, they have ignored my PM as if they are to busy to speak to me. That is ridiculous since the community is to small for this kind of behavior on their part.
BTW:
However what we did was not good it means anyone who traded in namecoins on the primary chain in the last 12 hrs will have their trades invalidated on our chain. If the developers do not go along with our changes this will get UGLY.
Davinci
Good to see the pool is back up !!!
Let's go save NameCoin
Let's go save NameCoin
I am not sure just what DavinciJ15 thinks he is doing now, but he mentioned in irc he enabled merged mining already, prematurely to what the official client was set for. He also has on his newspage
Sept 14 Merged mining right now but no payment method for both.
Sept 14 New block chain created Pool Down for updates.
Since he has created his own fork of the namecoins chain at this point, mining here is attacking namecoins, not defending it now.
Is it a mistake?
Time will tell.
Since your blocks are going to be rejected by the official client, it seems a mistake to me to have forked namecoin. Did you get doublec to go along with this as well? That would surprise me.
NodeMaster and slush told me that they got doublec to agree and it made sense to me, the only way to get hashing power is to pay bitcoins so forking the block chain seems right, we can deal with the fallout later.
I talked to doublec between those posts, seems they lied to you then. He did not change.
BTW, there are more then 3 pools.
Good to see the pool is back up !!!
Let's go save NameCoin
Let's go save NameCoin
I am not sure just what DavinciJ15 thinks he is doing now, but he mentioned in irc he enabled merged mining already, prematurely to what the official client was set for. He also has on his newspage
Sept 14 Merged mining right now but no payment method for both.
Sept 14 New block chain created Pool Down for updates.
Since he has created his own fork of the namecoins chain at this point, mining here is attacking namecoins, not defending it now.
Is it a mistake?
Time will tell.
Since your blocks are going to be rejected by the official client, it seems a mistake to me to have forked namecoin. Did you get doublec to go along with this as well? That would surprise me.
NodeMaster and slush told me that they got doublec to agree and it made sense to me, the only way to get hashing power is to pay bitcoins so forking the block chain seems right, we can deal with the fallout later.
Good to see the pool is back up !!!
Let's go save NameCoin
Let's go save NameCoin
I am not sure just what DavinciJ15 thinks he is doing now, but he mentioned in irc he enabled merged mining already, prematurely to what the official client was set for. He also has on his newspage
Sept 14 Merged mining right now but no payment method for both.
Sept 14 New block chain created Pool Down for updates.
Since he has created his own fork of the namecoins chain at this point, mining here is attacking namecoins, not defending it now.
Is it a mistake?
Time will tell.
Since your blocks are going to be rejected by the official client, it seems a mistake to me to have forked namecoin. Did you get doublec to go along with this as well? That would surprise me.
Doesn't this pool have more than 51% of the hash-rate ? Doesn't that mean that this fork will be THE original chain before long ? Or is that too much of a doomsday scenario ?
BTW I really don't believe Davinci wants to do something sinister and dark here
Good to see the pool is back up !!!
Let's go save NameCoin
Let's go save NameCoin
I am not sure just what DavinciJ15 thinks he is doing now, but he mentioned in irc he enabled merged mining already, prematurely to what the official client was set for. He also has on his newspage
Sept 14 Merged mining right now but no payment method for both.
Sept 14 New block chain created Pool Down for updates.
Since he has created his own fork of the namecoins chain at this point, mining here is attacking namecoins, not defending it now.
Is it a mistake?
Time will tell.
But that does that mean you forked the chain ?
And how will that stop the 51% attack from taking place. There's still not nearly enough hashing power to prevent that. Only adaption by a few large pools will be able to.
Getting really confusing now
I've spent the last hour reading the Dot-BIT forum and it seems there's not a real coordinated effort to step up to the challenge....
Brat
Good to see the pool is back up !!!
Let's go save NameCoin
Let's go save NameCoin
I am not sure just what DavinciJ15 thinks he is doing now, but he mentioned in irc he enabled merged mining already, prematurely to what the official client was set for. He also has on his newspage
Sept 14 Merged mining right now but no payment method for both.
Sept 14 New block chain created Pool Down for updates.
Since he has created his own fork of the namecoins chain at this point, mining here is attacking namecoins, not defending it now.
Is it a mistake?
Time will tell.
Since your blocks are going to be rejected by the official client, it seems a mistake to me to have forked namecoin. Did you get doublec to go along with this as well? That would surprise me.
Good to see the pool is back up !!!
Let's go save NameCoin
Let's go save NameCoin
I am not sure just what DavinciJ15 thinks he is doing now, but he mentioned in irc he enabled merged mining already, prematurely to what the official client was set for. He also has on his newspage
Sept 14 Merged mining right now but no payment method for both.
Sept 14 New block chain created Pool Down for updates.
Since he has created his own fork of the namecoins chain at this point, mining here is attacking namecoins, not defending it now.
Is it a mistake?
Time will tell.
Good to see the pool is back up !!!
Let's go save NameCoin
Let's go save NameCoin
I am not sure just what DavinciJ15 thinks he is doing now, but he mentioned in irc he enabled merged mining already, prematurely to what the official client was set for. He also has on his newspage
Sept 14 Merged mining right now but no payment method for both.
Sept 14 New block chain created Pool Down for updates.
Since he has created his own fork of the namecoins chain at this point, mining here is attacking namecoins, not defending it now.
Good to see the pool is back up !!!
Let's go save NameCoin
Let's go save NameCoin
In unrelated news...
It's time to load the boat on silver!
Sell your gold plow into silver. NOW.
It's time to load the boat on silver!
Sell your gold plow into silver. NOW.
Value: 6.26E-5000BTC
lol :|
lol :|
DavinciJ15, if you have some money to throw at the protection of the Namecoin network, you could place a bet on one of the Bitcoin betting sites that the attack will be _successful_. Then you invite people to bet against you and encourage them to tilt the chances in their favor by contributing hashing power. Additional plus for you: if the attack succeeds anyway, you get to keep your bounty.
I don't know what is a reliable betting site these days, but I have seen one existing bet here already: http://betsofbitco.in/item?id=101 .
I don't know what is a reliable betting site these days, but I have seen one existing bet here already: http://betsofbitco.in/item?id=101 .
Jump to: