Topic: [LAUNCH CANCELLED] - page 6. (Read 10669 times)

Thanks. I do see those so I am mining.

I just seen under that "hashpersec":0 and thought I wasn't doing anything.

EDIT: Why does my cpu load not change? Usually th cores run 99-100%

Hello sunny,

You do realize what is going on here right? I've been trying to mine this for a few hours and have put a few things together. Consider:

1) I can't connect to the node you posted. Whenever I do connect, I immediately get disconnected. Ok, maybe there are too many connections (wow, very popular coin!)
2) primer- posts a "super node", 144.76.139.178:21316. I add it to my node list and the daemon immediately starts downloading blocks. Looks like his node is great!
3) Yet, if there are so many connections (CogPrimus posted that he had 997 peers), where are all the peers? I am only connected to the "super node" and maybe sometimes one other node.
4) Yet here are a bunch of us posting hashrates and clearly mining.
Conclusion: primer-'s super node is not well-behaved: it isn't giving us each other's peer info.

Further:

5) All of us are complaining about stale blocks. I've generated 5 or 6 blocks yet each one except the first has been a stale block.
6) Yet the blocks aren't being generated *that* quickly. Only one every 10-40 seconds. Someone is putting a lot of computing power here, which is fine, that is how PoW works, but the hash power isn't as if 997 separate parties were immediately interested in the coin! It is extremely unlikely that the stale would all be naturally orphaned.
7) Also, every once in awhile I get a burst of 5-6 blocks all at once.
Keep that in mind and take into account that just about everyone is connected to that "super node" only ("144.76.139.178:21316")

Conclusion? Someone is DOSing ShinyCoin!

Step 1: Flood the legitimate seed node with thousands of connections so that nobody can connect to it.
Step 2: Post a helpful "super node" for everybody to connect to.
Step 3: Don't advertise peers from the super node.
Step 4: When anyone sends you a block they mine, discard it.
Step 5: When you mine a block, send it to the seed node and propagate it to the network.
Step 5b: If someone mines a few blocks in a row, keep mining until you have enough ready to overpower them, then propagate yours all at once.
Result: You are the only one generating any coins!

At some point you can then stop DOSing the seed node, the network carries on, and you have a nice few hundred thousand shiny coins to play with if anything comes of the alt coin.

I strongly recommend addressing this by re-launching the coin, with multiple nodes, and a way to protect against this kind of attack.

Cheers

setgenerate true -1

then you can type

getmininginfo


and if you see generate: true
then you're mining
genproclimit: -1
that means you're using as much as you can... 1 is sufficient though since it seems its not optimized


Right now we need a pool

I have tried "setgenerate true" and "setgenerate true -1" and still cant get the cpu mining. Is there something I am missing. I looked in the appdata debug but can't find it in there also.

Thanks

holy jeebus, 1.7gb ram just during the sync process?

addnode=46.28.206.41:7701
addnode=144.76.139.178:21316
addnode=144.76.139.178:22222
addnode=144.76.139.178:22223
addnode=144.76.139.178:22224
addnode=144.76.139.178:22225

sync is too slow...
half hour only block 166...
Look this time block is more than 700...

Dev could make a quick and dirty hack to reduce the chance of forks by duplicating the shinyhash function to allow the mining thread to use the duplicated lock so that processblock doesn't get stalled.

  addnode=144.76.139.178:21316

can get some nodes?

Don't know what this means but here it is: height=551  powheight=551  trust=552  moneysupply=110200.00  posmint=0.00

im on block 700

I must be blind as a bat because I don't see my speed in the log in appdata.

is the dev in the thread?

there may be a fork... what is everyone's block height, and what nodes is evryone using..

the LOCK(cs_hash) in ShinyHash causes massive slowdowns when mining.

I see the hashrate in the debug.log,
But the CPU occupy only 13%
Anything wrong,and the thread "shinycoin-qt.exe*32" take 13% of CPU 1,718,000 rem

BTW,the command execution is so slowly,is it same slowly in linux version?

definitely...

op should start by changing name of thread to "ANN"

Interesting...  I'm mining it, found a couple blocks.  The promotion certainly needs some work though.

Seems like a threading problem with the daemon, CPU usage is the same no matter how many miner threads are spawned.  Maybe the hashing function isn't thread-safe so it's mutexed?