[ANN] NeosCoin [NEOS] - with Arbitrush, Multi-Algo, In-wallet trading & More

[ocminer]

I've started a Blake Pool but we yet need a miner for it, since the original BlakeCoin uses SHA2() and this one uses SHA2(SHA2()) there is currently none available.

[BitBD]

Back again to NEOS. ( Old account banned)

[suchnekky]

Ah its always the same with icos, all the ico investors want to get out straight away, it  a day or two to get rid of them then its straight up from there

[ocminer]

Back again to NEOS. ( Old account banned)

What? Why banned?

[Hatch]

Why are none of the X11's working? Grrr!
 

[BitBD]

Back again to NEOS. ( Old account banned)

What? Why banned?

I may commented on VIP/Legendary board by mistake.

[RedZeppelin]

I am surprised so many people are mining with such a low block reward right now. 

Aye we kind of messed up the difficulty there - but hey its only 12,836,768 atm
Any bets on how long block 386 will take!?

[Mrboot]

I am surprised so many people are mining with such a low block reward right now. 

Aye we kind of messed up the difficulty there - but hey its only 12,836,768 atm
Any bets on how long block 386 will take!?

386 is done btw were can you see current diff ?

[RedZeppelin]

I am surprised so many people are mining with such a low block reward right now.  

Aye we kind of messed up the difficulty there - but hey its only 12,836,768 atm
Any bets on how long block 386 will take!?

386 is done btw were can you see current diff ?

If block 386 is done then both coinminers and kickasspools are stuck..

From kickasspools UI:

General Statistics
Pool Hash Rate   5.545 TH/s
Pool Efficiency   99.37%
Current Active Workers   17
Current Difficulty   12,836,767.97459487
Est. Next Difficulty   0.00000000 (Change in 1 Blocks)
Est. Avg. Time per Round (Network)   15314860732562 hours 32 minutes 8 seconds
Est. Avg. Time per Round (Pool)   2 hours 45 minutes 43 seconds
Est. Shares this Round   12,836,768 (done: 250.48%)
Next Network Block   387    (Current: 386)
Last Block Found   204
Time Since Last Block   11 hours 32 minutes 22 seconds

& coinminers:

General Statistics
Pool Hash Rate   0.005 TH/s
Pool Efficiency   99.13%
Current Active Workers   1
Current Difficulty   12,836,767.97459487
Est. Next Difficulty   0.00000000 (Change in 1 Blocks)
Est. Avg. Time per Round (Network)   15314860732562 hours 32 minutes 8 seconds
Est. Avg. Time per Round (Pool)   3342 hours 54 minutes 29 seconds
Est. Shares this Round   12,836,768 (done: 19.76%)
Next Network Block   387    (Current: 386)
Last Block Found   211
Time Since Last Block   11 hours 22 minutes 13 seconds

edit: both just moved on to 387..

[Mrboot]

Only watched that one

Block
390
Diff
77.032
Miners
0

Hash-harder

[ereborltc]

as long as twoturtles keeps this up I am never selling my neos coins! 

[Mrboot]

as long as twoturtles keeps this up I am never selling my neos coins! 

+1 im holding like crazy aswell i can see it go everywere

[RedZeppelin]

Only watched that one

Block
390
Diff
77.032
Miners
0

Hash-harder

SHA and X11 working on different difficultys, if the SHA difficulty only re-adjust +/-25% the next time the SHA part of the blockchain find a block and not when a block is
found in general we might be in for a looooong wait..  Must be a design flaw, needs a hotfix asap or it might just brutally killed SHA mining of Neoscoin.


{
"blocks" : 394,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487, <<should adjust +/-25% each block have not moved in alot of blocks..
"difficulty_x11" : 36.36177637,
"difficulty_blake" : 25.24213824,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
 

Only Blake part of chain is finding blocks and re-adjust difficulty each block at the moment.
Wow such anticipation, such hype, such fail..

Twoturtles can you confirm this is working as intended!?


{
"blocks" : 401,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 36.36177637,
"difficulty_blake" : 66.36665717,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 1,
"testnet" : false
}
 

{
"blocks" : 402,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 36.36177637,
"difficulty_blake" : 88.48887623,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 1,
"testnet" : false
}

[Mrboot]

Only watched that one

Block
390
Diff
77.032
Miners
0

Hash-harder

SHA and X11 working on different difficultys, if the SHA difficulty only re-adjust +/-25% the next time the SHA part of the blockchain find a block and not when a block is
found in general we might be in for a looooong wait..  Must be a design flaw, needs a hotfix asap or it might just brutally killed SHA mining of Neoscoin.


{
"blocks" : 394,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487, <<should adjust +/-25% each block have not moved in alot of blocks..
"difficulty_x11" : 36.36177637,
"difficulty_blake" : 25.24213824,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
 

edit: Only Blake part of chain finding blocks and re-adjust difficulty each block.
Wow such anticipation, such hype, such fail..
Twoturtles can you confirm this is working as intended!?


{
"blocks" : 401,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 36.36177637,
"difficulty_blake" : 66.36665717,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 1,
"testnet" : false
}
 

He Will , dont worry also there are a extra low reward each block almost all coin might have some small prob at start.

Not saying thats the prob. with neos i think its going awesome , ppl still buying at ipo price , and getting stronger and stronger

[RedZeppelin]

Only watched that one

Block
390
Diff
77.032
Miners
0

Hash-harder

SHA and X11 working on different difficultys, if the SHA difficulty only re-adjust +/-25% the next time the SHA part of the blockchain find a block and not when a block is
found in general we might be in for a looooong wait..  Must be a design flaw, needs a hotfix asap or it might just brutally killed SHA mining of Neoscoin.


{
"blocks" : 394,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487, <<should adjust +/-25% each block have not moved in alot of blocks..
"difficulty_x11" : 36.36177637,
"difficulty_blake" : 25.24213824,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
 

edit: Only Blake part of chain finding blocks and re-adjust difficulty each block.
Wow such anticipation, such hype, such fail..
Twoturtles can you confirm this is working as intended!?


{
"blocks" : 401,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 36.36177637,
"difficulty_blake" : 66.36665717,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 1,
"testnet" : false
}
 

He Will , dont worry also there are a extra low reward each block almost all coin might have some small prob at start.

Not saying thats the prob. with neos i think its going awesome , ppl still buying at ipo price , and getting stronger and stronger

He will what!? How do you know!? Do you have any clue what you actually just commented?
Yes yes - we all know about the low reward atm, but that does not fix the issue i just pointed out it is just plain damage control at the moment.


{
"blocks" : 403,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 36.36177637,
"difficulty_blake" : 117.98558318,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 2,
"testnet" : false
}
 

Still only Blake part of chain re-adjust each block.
SHA part of chain will most likely never find a block at current difficulty and current hashrate..
Well it might eventually but i wont because no one will be running their miners pointed at the SHA part for that long.

edit: X11 got lucky..


{
"blocks" : 405,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 29.08944632,
"difficulty_blake" : 157.31447968,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
 

[Mrboot]

Uhm he will , was pointed on the fact that he will confirm it , he is really active !

And if there is any problem he will Fix it, Thats a fact.

Just dont spread over reacted fud yet wait for a response.

[RedZeppelin]

Uhm he will , was pointed on the fact that he will confirm it , he is really active !

And if there is any problem he will Fix it, Thats a fact.

Just dont spread over reacted fud yet wait for a response.

It is not FUD it is a fact at the moment.
Main 2 questions is when we will see a fix and why the developers did not forsee this happening..

How long you think it will take before the current miners at kickasspool throws in the towel and we have 12.8 million in difficulty and almost 0 hashrate!?
Willl it be fixed before we hit block 1001!?
edit: seems it will because the blockchain is no longer moving.


{
"blocks" : 416,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 29.08944632,
"difficulty_blake" : 3724.78278252,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
 

edit:

give Blake a few more blocks and....


{
"blocks" : 418,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 29.08944632,
"difficulty_blake" : 6621.84435303,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
 

[twoturtles]

Uhm he will , was pointed on the fact that he will confirm it , he is really active !

And if there is any problem he will Fix it, Thats a fact.

Just dont spread over reacted fud yet wait for a response.

It is not FUD it is a fact at the moment.
Main 2 questions is when we will see a fix and why the developers did not forsee this happening..

How long you think it will take before the current miners at kickasspool throws in the towel and we have 12.8 million in difficulty and almost 0 hashrate!?
Willl it be fixed before we hit block 1001!?
edit: seems it will because the blockchain is no longer moving.


{
"blocks" : 416,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 29.08944632,
"difficulty_blake" : 3724.78278252,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
 

edit:

give Blake a few more blocks and....


{
"blocks" : 418,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 12836767.97459487,
"difficulty_sha256d" : 12836767.97459487,
"difficulty_x11" : 29.08944632,
"difficulty_blake" : 6621.84435303,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
 

We're taking a look into it and I'll give everyone and update shortly.

      Regards,

syntaks

[twoturtles]

Also, "such anticipation, such hype, such fail.." - more like you're angry that the full block rewards haven't kicked in yet and you have to wait.  Don't be rude.  Thanks.

     Regards,

syntaks

[RedZeppelin]

Also, "such anticipation, such hype, such fail.." - more like you're angry that the full block rewards haven't kicked in yet and you have to wait.  Don't be rude.  Thanks.

     Regards,

syntaks

Well sometimes irony dont do well in writing

Honestly when basic problems like this is not sorted pre-launch how is the rest of things supposed to hold up?
This have happend with multi-algo coins before i honestly did not think this dev team would step into the same sinkhole..

SHA difficulty have been up there since block 211 or something like that, you guys are already 12 hours late almost looking into it..