I would expect the price of MEOW to rally as soon as the Whales get the amount of coins they wanted. Its just crazy how easy it is to manipulate an entire market!

So the perceived overall/network (not personal) advantage of transparent forging (as opposed to secret forging) is that the speeding up of the confirmations due to knowing where to send transaction details to trumps the headache for the common man of trying to disentangle the technical stuff required to "lease" their CPU power to a "hub" and the consequences of most naive users not bothering to lease (due to ignorance, laziness, don't-have-to-do-this-for-any-other-crypto-ness)? This seems like a serious barrier to entry for the (future) common user. How would grandma know to do any of this shit when she just wants to use the NXT crypto like she uses her Bitcoins (this is me imagining the future)? It seems by not being part of a leased pool she may be subject to a DDoS at worst (her turn to forge is up and some bad actor is blasting her IP) and at best will never get any "forging" interest (because she is not part of a hub).

If I am correct, don't the NXT devs see this as a (serious) barrier to adoption? I have a background in psychology/usability/user experience so these "common man's experience" scenarios I ask about are how I approach a lot of new technology. The fact that there is a technical solution to an issue does not mean the issue disappears (e.g. protecting accounts with passwords).

Not trying to be combative or annoying, just trying to understand.

So it sounds like everyone(?) is behind this "umbrella" of protection from a hub. Who owns a hub? Is the forging based then on the "hub level" IP? Do people choose which hub to be a part of or is it proximity based or...? Very new to this, so hope these aren't old questions (I'm familiar with traditional cryptos, just not his one).

But most people with NXT will not have that... so how does this play out in the wild? 99 DDoS attacks on random victims who have NXT on their cell phone (and were supposed to forge the next block) and then the 100th is a hub so protected and the block gets forged? Also, what happens to the transactions that are being sent to DDoS IP addresses during the DDoS (or is that a non-issue due to the block never being forged with that IP)?

There was a comment in this thread from a while back that got buried due to the poster being kind of a dick about the answer he got, but it was the reason I read through the whole thread to begin with, so I hope to get some clarification here...

Regarding transparent mining, and the ability to know the source of the next forged block: If a bad agent wants to attack the system, knowing the IP of the forger(s) seems like a ripe place for continuous DDOS attacks against unprotected victims. The prior answer was "forgers can use the Tor network" but that seems like a huge stretch to adoption as 99% of people don't know what that means much less how to set that up. Is that the real answer to this issue (assuming it is an "issue" to begin with)?

Thanks in advance.

my wallet just synced. did you download the latest wallet?

This.

I was thinking about multipools today... they are motivated by a few things: Profit and Speed. Low diff + lots of hashrate provide both of these things when a coin is getting some traction. I would argue that the SPEED factor plays in quite heavily - they want to get in and get out, dump and roll on (once the diff is increased due to their hashrate blowing up the algo).

The KGW adjusts the diff to make it harder to speed mine and leave a coin hanging on the re-diff. But what about one other aspect - what if a mined coin needed a "cooling off period" or some such other thing that made them unable to use for X blocks that would translate to hours (or even days) when first mined? Once they "matured" they could be spent as usual, but at first they are unobtainable or unredeemable. I'm guessing even a small delay in "usability" would make the multipools run for the hills. Example: Once you mine a coin, those coins are unusable for 120 blocks. If a multipool did a hit and run (without the KGW to fix) the coin left high and dry would also screw the mined coins because they would be in limbo for 120 blocks (and since the multipool had rolled off, the confirm time would be really long... further screwing their hit and run profits). Patient, devoted miners wouldn't care much, just mine and spend as normal, but the hit and run folks wouldn't touch the coin due to its tardy method of payout.

Does this exist? Is it possible with the current infrastructure (just curious). Even a "cool off" of 30 blocks could mean the multipools ignore the coin as "unminable" within their motives.

You are depositing MEOW to sell? My point is that nobody can sell right now unless the MEOW are in the system.