Posts made by coinotron

Thanks.
What about network, is it still split into different chains?
Is it safe to transfer coins ?

Can anyone say what is current status?
What client is safe to use ?
How to check whether wallet is on main chain ?

@ghostlander said:

@GMC You may also restart with -disablesafemode and continue until we finish the investigation.

That didn’t help. Now I’m reindexing using wallet 9.5

Hi

It seems that something wrong is going on. My pool wallets keep logging this error in their log files:

2016-03-04 09:46:23 InvalidChainFound: invalid block=289590e2a28db3907e353a889c0b001d7fb0c167f48e37feea25a9f46621e829 height=1114789 log2_work=57.940279 date=2016-03-04 09:46:12
2016-03-04 09:46:23 InvalidChainFound: current best=944a95ddacb5b567448ee450b0f0f4c328e4cfff92c7ad2f255d199ef53e0641 height=1114310 log2_work=57.94026 date=2016-03-04 01:18:53
2016-03-04 09:46:23 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.

test test

Same case here. Sending payout from coinotron to btc-e more than 15 hours ago, still no sign of it. No response from btc-e yet.

I don’t know if the problem lies with coinotron or btc-e though. Coinotron admin said the payout has been sent, but when i checked http://explorer.feathercoin.com/address/6tJ5N4S4pNGLqKNGqf3tc5KX8h6KQFfHQc there’s no new transaction there.

Coinotron does said that the official blockchain explorer need to catch up? Could anyone shed some light on this? Because i check on explorer.feathercoin.com i can see the latest block there. So whats exactly is needed to catch up when it’s already updated??

Right now, i’m only burning electricity, and cant see any result.

Yesterday explorer.feathercoin.com suddenly stopped showing new blocks. Today it works ok.

Please check out that address again. Now block explorer shows your payout.

I think you must ask btc-e what happened to that transaction.

We 've found 13 Neoscrypt blocks:

http://coinotron.com

Feathercoin 0.8.7.0 released. The NeoScrypt Update.

Our FTC pool will be switched to Neoscrypt mining after block 432000. Please update your wallet and miners. Scrypt miners won’t work. Links to miners supporting Neoscrypt you will find on our Help page.

[Pool] ---- Coinotron ---- 2FA, DDOS protection

We are proud to present to you world’s first multi-coin mining pool.

Stratum mining is available in the following pools:

LTC and DOGE merged mining = coinotron.com:3334
LTC and DOGE merged mining ( ASIC miners, share diff. 8192 ) = coinotron.com:3834
FTC = coinotron.com:3337
PPC = coinotron.com:3338
VTC = coinotron.com:3340
DRK = coinotron.com:3341

You can mine here

-litecoins ( PPS, RBPPS. PPLNS )
-feathercoins( RBPPS )
-ppcoins ( PPS, RBPPS )
-DOGE (RBPPS)
-vertcoins(RBPPS)
-darkcoins (RBPPS, PPLNS)

Reward system: http://coinotron.com/coinotron/AccountServlet?action=home

All shares submitted in PPS mode are rewarded with constant rate:

Payout per Share = (1 - Pool share) * 50 LTC * Share difficulty / (65536 * Current LTC Difficulty)

Share difficulty - how many times more difficult are current shares than base difficulty shares.
Base share difficulty = 1, base shares have (on average ) 65536 hashes.
65536 is the average number of shares of difficulty 1 in a block of difficulty 1

Coinotron advantages:

• security is our priority, user passwords are hashed and salted,
• we offer two-factor authentication ( Google Authenticator ),
• our servers are DDOS protected,
• website is protected against brute force and dictionary attacks,
• automatic payouts,
• simple api,
• Stratum support in all pools

How can you join us?
1. Register here: http://www.coinotron.com/coinotron/AccountServlet?action=register
2. Create worker(s)
3. Configure your mining application to point to our server - examples: http://www.coinotron.com/coinotron/AccountServlet?action=help
4. Start mining

IMPORTANT
For security reasons we introduced some limitations into registration process.

• Username and password must have at least 8 characters
• You should enter your real email address. It is the only way to unblock your account if you forgot password.

Coinotron.com

Coinotron will be switched to neoscrypt mining on block 43200

Coinotron will be switched to neoscrypt mining on block 43200

Coinotron has updated FTC client to 0.6.4.4

I’ve found it in my pool code which is based on original Slush’s stratum pool. viperaus fork on github is also affected. Probably it is present in all Slush’s stratum forks.

Whether getwork pools are affected or not I don’t know. It all depends on implementation.

[quote name=“sheepson” post=“22194” timestamp=“1374225485”]
Alright! so Coinotron is running again?

And after the attack the operator should change the setting back?
[/quote]

Coinotron is running and solving blocks.
Regarding going back to prev version after attack - I’m not sure.
I must check out how ftc client does its verifications. They are actually more complicated than this one line I quoted.

Hi

I’m operator of Coinotron pool.

I think I found vulnerability in the pool server stratum implementation which someone is actively using to block FTC pools.
Vulnerability causes pool to stop accepting any shares submitted by miners!
It is caused by different ways of verifying block time.

Featherclient does it like this :

[code]// Check timestamp
if (GetBlockTime() > GetAdjustedTime() + 2 * 60 * 60)
return error(“CheckBlock() : block timestamp too far in the future”); [/code]

While stratum pool:

[code]if ntime > (self.timestamper.time() + 1000):[/code]

[url=https://github.com/viperaus/stratum-mining/commit/e760f30fa44dc58f4a478e87c444f10e83bebae3]https://github.com/viperaus/stratum-mining/commit/e760f30fa44dc58f4a478e87c444f10e83bebae3[/url]

1. Attacker is producing blocks with timestamps shifted 2 hours to the future
2. Getblocktemplate RPC used by all pools returns Block Templates with ntime shifted over 1 hour to the future.
3. Miners are submitting their shares with ntime based on Block Templates from the pool.
4. Pool doesn’t accept those shares because share ntime > (self.timestamper.time() + 1000)

Quick fix is to change 1000 to 7200 in pool’s stratum code.

hi