[ANN] Krypton, KR - BaaS Corp & Open Source, Public Blockchain for Business/IoT - page 22.

Abiky

legendary

Activity: 3220

Merit: 1363

www.Crypto.Games: Multiple coins, multiple games

Quote from: covertress on August 26, 2016, 01:55:47 PM

*** Attention Krypton Community ***

Krypton is in the process of doing a minor (KVM) client upgrade (not a fork) to version 1.3.3 in order to solve a transaction anomaly identified by the explorer 2.0. Specifically, a transaction caching issue.

Both Yobit and Bittrex wallets will remain offline until the exchanges and KR mining pools have had the time to complete this upgrade.

We anticipate that this will happen by this evening. We will be doing a press release at the time the wallets reopen.

Thanks for the update. It is nice to the very active development for Krypton over the last days. We have everything we need to make the coin succeed together as a community. I'm glad to have invested into Krypton when it was worth nearly $0.02 USD. Now it is double than what I have invested initially and will continue to hold it for the long term.

Mariuszeq

newbie

Activity: 32

Merit: 0

Quote from: mikegi on August 27, 2016, 01:00:48 PM

I was about to ask where the latest source can be found but it appears that the latest source is now on github.

I suppose the bitbucket repo and OP are to be updated soon.

Anyway, it's nice to see the update!

Is this now the official version or is it being tested?

Looking at http://stats.krypton.rocks:8080/ I see two versions in use.

Gkr/v1.1.3-8376a53b

https://bitbucket.org/gkrypto/go-krypton/commits/all

Gkr/v1.3.3-88fe99f6

https://github.com/covertress/go-krypton

EDIT...

Quick note if you're building on Linux with make...

$ chmod 755 build/flags.sh build/env.sh build/test-global-coverage.sh

Thank you very much for info where to find latest version, I upgraded to 1.3.3.

mikegi

full member

Activity: 165

Merit: 100

I was about to ask where the latest source can be found but it appears that the latest source is now on github.

I suppose the bitbucket repo and OP are to be updated soon.

Anyway, it's nice to see the update!

Is this now the official version or is it being tested?

Looking at http://stats.krypton.rocks:8080/ I see two versions in use.

Gkr/v1.1.3-8376a53b

https://bitbucket.org/gkrypto/go-krypton/commits/all

Gkr/v1.3.3-88fe99f6

https://github.com/covertress/go-krypton

EDIT...

Quick note if you're building on Linux with make...

$ chmod 755 build/flags.sh build/env.sh build/test-global-coverage.sh

sweet bird

newbie

Activity: 28

Merit: 0

looks good, but yes, this will be a headache for newbies to crypto. I'm out unless there is an explanation, drop and swap purpose for
the currency other than money grab.

Mariuszeq

newbie

Activity: 32

Merit: 0

Hello,

In reply to:
http://bitcoinist.net/attack-krypton-dry-run-ethereum/

Dear @covertress, I kindly ask you to stop spreading lies that my pool was involved in 51% attack targeted at Krypton network.

Attack was performed 2016-08-24 around 20:27 CEST, when malicious miner (http://explorer.krypton.rocks/#/address/0x3476cac2670e87e237b738a54fdce381640e5c05) revealed his blockchain fork (174 blocks) that had more work and was longer about 59 blocks from the main chain. Blockchain reorganization took place and attacker's chain won. All work performed on Krypton network between 2016-08-24 19:25 CEST and 2016-08-24 20:27:52 CEST became invalid and lost. Here are logs:

Quote

I0824 20:22:02.927752 17396 chain_manager.go:661] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.919075ms. #897006 [0638c0e5 / 0638c0e5]
I0824 20:22:02.929125 17396 worker.go:540] commit new work on block 897007 with 0 txs & 0 uncles. Took 1.163303ms
I0824 20:22:10.698125 17396 worker.go:322] 🔨 Mined block (#897007 / e374f0ec). Wait 5 blocks for confirmation
I0824 20:22:10.699265 17396 worker.go:540] commit new work on block 897008 with 0 txs & 0 uncles. Took 1.086603ms
I0824 20:22:10.700370 17396 worker.go:540] commit new work on block 897008 with 0 txs & 0 uncles. Took 821.367µs
I0824 20:22:22.323058 17396 chain_manager.go:661] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.28223ms. #897008 [bfb9b057 / bfb9b057]
I0824 20:22:22.324629 17396 worker.go:540] commit new work on block 897009 with 0 txs & 0 uncles. Took 690.064µs
I0824 20:23:32.667818 17396 worker.go:322] 🔨 Mined block (#897009 / bc0a3d73). Wait 5 blocks for confirmation
I0824 20:23:32.669204 17396 worker.go:540] commit new work on block 897010 with 0 txs & 0 uncles. Took 1.352662ms
I0824 20:23:32.670084 17396 worker.go:540] commit new work on block 897010 with 0 txs & 0 uncles. Took 617.11µs
I0824 20:25:47.239858 17396 worker.go:322] 🔨 Mined block (#897010 / 97cbc156). Wait 5 blocks for confirmation
I0824 20:25:47.241160 17396 worker.go:540] commit new work on block 897011 with 0 txs & 0 uncles. Took 1.255617ms
I0824 20:25:47.242586 17396 worker.go:540] commit new work on block 897011 with 0 txs & 0 uncles. Took 749.347µs
I0824 20:26:43.195200 17396 chain_manager.go:661] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 4.085547ms. #896896 [b4d7f5ee / b4d7f5ee]
I0824 20:26:52.387011 17396 chain_manager.go:661] imported 163 block(s) (0 queued 0 ignored) including 2 txs in 124.566183ms. #897059 [54b7d48e / ec011e88]
I0824 20:26:52.391988 17396 worker.go:540] commit new work on block 897060 with 0 txs & 0 uncles. Took 2.066885ms
I0824 20:27:01.377154 17396 chain_manager.go:661] imported 2 block(s) (0 queued 0 ignored) including 0 txs in 4.206482ms. #897061 [e80e8665 / aba2f3b2]
I0824 20:27:01.378242 17396 worker.go:540] commit new work on block 897062 with 0 txs & 0 uncles. Took 1.0245ms
I0824 20:27:02.089515 17396 worker.go:322] 🔨 Mined block (#897062 / 98ada186). Wait 5 blocks for confirmation
I0824 20:27:02.090882 17396 worker.go:540] commit new work on block 897063 with 0 txs & 0 uncles. Took 1.336359ms
I0824 20:27:02.091924 17396 worker.go:540] commit new work on block 897063 with 0 txs & 0 uncles. Took 705.901µs
I0824 20:27:10.479073 17396 chain_manager.go:661] imported 4 block(s) (0 queued 0 ignored) including 0 txs in 6.02314ms. #897065 [93ad205e / bc578382]
I0824 20:27:10.495227 17396 worker.go:540] commit new work on block 897066 with 0 txs & 0 uncles. Took 15.936246ms
I0824 20:27:23.439962 17396 chain_manager.go:661] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.613651ms. #897066 [65c9f447 / 65c9f447]
I0824 20:27:23.441169 17396 worker.go:540] commit new work on block 897067 with 0 txs & 0 uncles. Took 1.138835ms
I0824 20:27:32.157618 17396 chain_manager.go:661] imported 1 block(s) (0 queued 0 ignored) including 1 txs in 3.732983ms. #897067 [a5480f99 / a5480f99]
I0824 20:27:32.158902 17396 worker.go:540] commit new work on block 897068 with 0 txs & 0 uncles. Took 1.09091ms
I0824 20:27:33.612168 17396 chain_manager.go:661] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.364303ms. #897068 [29af50e5 / 29af50e5]
I0824 20:27:33.613209 17396 worker.go:540] commit new work on block 897069 with 0 txs & 0 uncles. Took 694.962µs
I0824 20:27:48.267865 17396 chain_manager.go:661] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.922658ms. #897069 [92e5a537 / 92e5a537]
I0824 20:27:48.269666 17396 worker.go:540] commit new work on block 897070 with 0 txs & 0 uncles. Took 800.108µs
I0824 20:27:52.794347 17396 chain_manager.go:661] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.470168ms. #897070 [fda0e657 / fda0e657]
I0824 20:27:52.795641 17396 worker.go:540] commit new work on block 897071 with 0 txs & 0 uncles. Took 1.085599ms
I0824 20:29:16.227999 17396 worker.go:322] 🔨 Mined block (#897071 / 5d685e3e). Wait 5 blocks for confirmation
I0824 20:29:16.229691 17396 worker.go:540] commit new work on block 897072 with 0 txs & 0 uncles. Took 1.648644ms

Complete logs from Gkr:
http://pastebin.com/LzYrZxFA

As a result of attack my pool lost 87 valid blocks that became orphans. Logs:

Quote

2016/08/24 20:27:19 Orphaned block 896992:0xbf7badd404a6d0ad
2016/08/24 20:27:19 Orphaned block 896993:0xb81e1a6c1be84211
2016/08/24 20:27:19 Orphaned block 896994:0x202d35f005193aa5
2016/08/24 20:27:19 Orphaned block 896996:0x3cb8064c1bd03817
2016/08/24 20:27:19 Orphaned block 896999:0x579e60d81497f676
2016/08/24 20:27:19 Orphaned block 897000:0xf82e5a8c08a479b1
2016/08/24 20:27:19 Orphaned block 897007:0x72ea7b4806713ccc
2016/08/24 20:27:19 Orphaned block 897009:0x56da07745fc4d7b2
2016/08/24 20:27:19 Orphaned block 897010:0x17c3de7876247239
2016/08/24 20:27:19 Immature 0 blocks, 0 uncles, 9 orphans
2016/08/24 20:27:19 Inserted 9 orphaned blocks to backend
2016/08/24 20:27:19 IMMATURE SESSION: revenue 0.00000000, miners profit 0.00000000, pool profit: 0.00000000
2016/08/24 20:27:19 Mature block 896895 with 0 tx, hash: 0x4e88daae
2016/08/24 20:27:19 Orphaned block 896897:0x6d521a4807ceec24
2016/08/24 20:27:19 Orphaned block 896898:0xdf7a84a81025e5a3
2016/08/24 20:27:19 Orphaned block 896901:0x45378ce00d48902a
2016/08/24 20:27:19 Orphaned block 896902:0x1ed639c022286b0e
2016/08/24 20:27:19 Orphaned block 896903:0x3a66740816c11031
2016/08/24 20:27:19 Orphaned block 896904:0x362e4de836836cb2
2016/08/24 20:27:19 Orphaned block 896905:0x0861abd826260b71
2016/08/24 20:27:19 Orphaned block 896906:0xf2fae6aa0f1dec9a
2016/08/24 20:27:19 Orphaned block 896908:0xc1bd5970092f52c4
2016/08/24 20:27:19 Orphaned block 896909:0x20b6c0a01bcdd4d4
2016/08/24 20:27:19 Orphaned block 896910:0x6d09a0f1bdbd472c
2016/08/24 20:27:19 Orphaned block 896912:0x32b60287765a461d
2016/08/24 20:27:19 Orphaned block 896913:0xc2b8f9c40ac4e7e4
2016/08/24 20:27:19 Orphaned block 896914:0xa1bdb23004af7d6a
2016/08/24 20:27:19 Orphaned block 896916:0xb83cadb00de09fcf
2016/08/24 20:27:19 Orphaned block 896918:0xe02ba5d0228b051f
2016/08/24 20:27:19 Orphaned block 896919:0x5ac8bfc86d7cf4d0
2016/08/24 20:27:19 Orphaned block 896923:0x7b44fca127b3422b
2016/08/24 20:27:19 Orphaned block 896924:0xa4bb8990211b3b6f
2016/08/24 20:27:19 Orphaned block 896925:0xc843868026770194
2016/08/24 20:27:19 Orphaned block 896926:0x5708e1f023f11ab3
2016/08/24 20:27:19 Orphaned block 896927:0x5d9f788864f7015f
2016/08/24 20:27:19 Orphaned block 896928:0xcbadaa5011645913
2016/08/24 20:27:19 Orphaned block 896930:0xde7db5040533db28
2016/08/24 20:27:19 Orphaned block 896932:0xafe4faa04d79263a
2016/08/24 20:27:19 Orphaned block 896934:0x124b8cf405695581
2016/08/24 20:27:19 Orphaned block 896937:0x971ce1880dd4e223
2016/08/24 20:27:19 Orphaned block 896938:0xc879026018ea9141
2016/08/24 20:27:19 Orphaned block 896939:0x31336480072f19ba
2016/08/24 20:27:19 Orphaned block 896940:0x278d0d40342460f6
2016/08/24 20:27:19 Orphaned block 896941:0x85fa3d7898c256a8
2016/08/24 20:27:19 Orphaned block 896942:0x52585c941b80b80e
2016/08/24 20:27:19 Orphaned block 896945:0x766e011d628f33b3
2016/08/24 20:27:19 Orphaned block 896946:0x46becb587f2e99f3
2016/08/24 20:27:19 Unlocked 1 blocks, 0 uncles, 34 orphans
2016/08/24 20:27:19 Inserted 34 orphaned blocks to backend

Complete logs from pool block unlocker:
http://pastebin.com/carHv0S2

I am also concerned about the development of the project. From where I can get go-krypton 1.3.3? I see that some of the pools already use it. Is it a version for the chosen ones?

viverra

full member

Activity: 126

Merit: 100

I don't want to offend anyone, but I think you need to change the logo. this looks childish

covertress

hero member

Activity: 694

Merit: 500

Bitcoinist runs a news story on the 51% Attack Cool

Attack On Krypton a ‘Dry Run’ For Ethereum?

http://bitcoinist.net/attack-krypton-dry-run-ethereum/

I'd like to thank Team Krypton for the professional manner in which this attack was handled. Everyone from devs to miners worked in concert to quickly identify and mitigate this novel attack vector. You have my deepest admiration. It is my pleasure to work with you. - Stephanie Kent

covertress

hero member

Activity: 694

Merit: 500

Quote from: vella85 on August 27, 2016, 05:16:12 AM

I think the dev team handled it well and took the correct measures to insure all of us was safe while they were working on the upgrades. And now the price has rebounded back up to 30,000 sats. Well done dev and thanks covertress for keeping us all informed during the process. This is why I love this coin and invested into KR because we have one of the best devs in crypto land and of course covertress.

Thank you very much, vella85.

Krypton-Dev spent several sleepless nights, dedicating 100% of his not-at-work hours towards this successful upgrade. I'm sure he will appreciate your message.

vella85

hero member

Activity: 1862

Merit: 590

I think the dev team handled it well and took the correct measures to insure all of us was safe while they were working on the upgrades. And now the price has rebounded back up to 30,000 sats. Well done dev and thanks covertress for keeping us all informed during the process. This is why I love this coin and invested into KR because we have one of the best devs in crypto land and of course covertress.

frostminer

hero member

Activity: 742

Merit: 505

Quote from: amalgal on August 26, 2016, 09:06:52 PM

oh no the same problem like it was with eth .
Dao 2.0 or KR classic Cry

wallets are not working at both exchanges ,price drop 35% Shocked

Its not all like that, at all.
Wallets were disabled to avoid abuse while upgrading.

covertress

hero member

Activity: 694

Merit: 500

KRYPTON RECOVERS FROM A NEW TYPE OF 51% NETWORK ATTACK

http://cryptohustle.com/krypton-recovers-from-a-new-type-of-51-network-attack

This type of attack can happen to any Ethereum-based coin with low network hashing power.

amalgal

hero member

Activity: 560

Merit: 501

oh no the same problem like it was with eth .
Dao 2.0 or KR classic Cry

wallets are not working at both exchanges ,price drop 35% Shocked

Lock_n_Load

newbie

Activity: 10

Merit: 0

Cryptohustle has 25% of the info correct and the other 75% is inaccurate. I am not sure how that article was compiled but I hope he corrects it before he does any additional harm.

Mariuszeq

newbie

Activity: 32

Merit: 0

Hello,

In response to:
http://cryptohustle.com/krypton-recovers-from-a-new-type-of-51-network-attack
https://www.linkedin.com/pulse/krypton-recovers-from-new-type-51-network-attack-stephanie-kent?published=t

I strongly deny that kr.4miners.net had any connection with the 51% attack on Krypton network.

I double checked the logs and there is no trace of any security breaches on main and backup pool servers. Gkr instances was manually compiled from latest code (https://bitbucket.org/gkrypto/go-krypton). Code was not modified in any way and nodes run without interruption. Hashrate jumps over 51% alot of times since pool start (alternating with suprnova), and it's pretty common with low network hashrate coins. Of course, this is not desirable, but we make every effort to keep our servers secure for such cases.

Best regards,
4miners.net

abitserious

newbie

Activity: 9

Merit: 0

Quote from: covertress on August 26, 2016, 01:55:47 PM

*** Attention Krypton Community ***

Krypton is in the process of doing a minor (KVM) client upgrade (not a fork) to version 1.3.3 in order to solve a transaction anomaly identified by the explorer 2.0. Specifically, a transaction caching issue.

Both Yobit and Bittrex wallets will remain offline until the exchanges and KR mining pools have had the time to complete this upgrade.

We anticipate that this will happen by this evening. We will be doing a press release at the time the wallets reopen.

Thank You for the updates I knew we invested in the right dev team KR ROCKS

amacar2

legendary

Activity: 1120

Merit: 1008

CryptoTalk.Org - Get Paid for every Post!

@covertress thanks for this update, this may clear the confusion/fear/doubt trader were having during bittrex KR wallet maintainance. Someone who sold so much KR recently dumping market hard on bittrex soon gonna regret. Grin

covertress

hero member

Activity: 694

Merit: 500

*** Attention Krypton Community ***

Krypton is in the process of doing a minor (KVM) client upgrade (not a fork) to version 1.3.3 in order to solve a transaction anomaly identified by the explorer 2.0. Specifically, a transaction caching issue.

Both Yobit and Bittrex wallets will remain offline until the exchanges and KR mining pools have had the time to complete this upgrade.

We anticipate that this will happen by this evening. We will be doing a press release at the time the wallets reopen.

Mariuszeq

newbie

Activity: 32

Merit: 0

Quote from: frostminer on August 25, 2016, 09:45:37 AM

Quote from: Atomjuice on August 25, 2016, 09:32:58 AM

The reason is simple: suprnova is not a reliable pool..I've been mining various coins on it..it has so many 'issues'...so, people go to '4 miners' because it's a great stable pool...we pay a lot for our equipment, who wants to waste it hashing on an unproductive pool??

Then i can inform u that 4miners cloned miners-zones software .. and are pretty unkown and new.

Quote from: abitserious on August 25, 2016, 10:20:29 AM

Quote from: Atomjuice on August 25, 2016, 09:32:58 AM

The reason is simple: suprnova is not a reliable pool..I've been mining various coins on it..it has so many 'issues'...so, people go to '4 miners' because it's a great stable pool...we pay a lot for our equipment, who wants to waste it hashing on an unproductive pool??

This pool is a clone 100% copied and stolen NO ONE SHOULD TRUST 4 miner

We didn't steal anything. We run modified version of https://github.com/sammy007/open-ethereum-pool which is licensed under GPLv3. We even left the original footer and dev donation address.
And each one pool was once unknown and new...

gigabyted

hero member

Activity: 906

Merit: 500

Quote from: ocminer on August 25, 2016, 09:41:01 AM

Quote from: Atomjuice on August 25, 2016, 09:32:58 AM

The reason is simple: suprnova is not a reliable pool..I've been mining various coins on it..it has so many 'issues'...so, people go to '4 miners' because it's a great stable pool...we pay a lot for our equipment, who wants to waste it hashing on an unproductive pool??

Interesting, what are the issues ? Actually I'm doing pools and crypto since 2012, I'm available 24x7, I even have a support chan in IRC or via Twitter.. I pay bounties for bugs, I pay bonuses, I even pay coins after rounds have completed if there were any issues.

I've never heard of any "issues" and the KR pool is running for quite a long time now.

Beside of that, I'm developing my stratums, by frontend and backend myself and I don't rely on any other developers who open source pool's backend software so I'm certainly aware what's currently going on in the background. I can see attacks on stratums, because I've developed stratums, I know how a fake share attacks works because I'm writing counter measures against it.. Or double share attacks, fake blocks etc.. Even IF such an attack sucessfully happens, I pay afterwards and reimburse the miners...

EDIT: Oh and btw there already was an "issue" which fast fixed quickly after it was reported and all users got a decent 20% bonus on their balances. I'm not doing this as my dayjob but I certainly serious in what I'm doing.

Lol this is funny i know ocminer and ive been mining at suprnova since like 3 years now, one of the best pools around and all that time i never heard of 4 miners....

BTW: Hi ocminer, long time no see

Atomjuice

member

Activity: 103

Merit: 10

Thanks for the reply...I'm in Jiangsu Province...Nanjing -Changzhou-Suzhou area...Nanjing would be best as it's the provincial capital where I live...I knew much of what you said...but it was a bit amusing and surprising to hear that 'job not done' is 'skipped' by some pools to make you feel good..lol...but I wonder if 'job not done' could also be related to the speed of my recent connection? I will have a high speed dedicated line in the next few days..right now I have a el cheapo landlord who got 20m internet split between an entire apartment complex..so I sometimes am running at 1 mb/s..lol...but I didn't think mining depended too much on internet speed...but this is super slow. So,..there you have it..thanks for your reply..a lot of well explained information there..thank you.

Topic: [ANN] Krypton, KR - BaaS Corp & Open Source, Public Blockchain for Business/IoT - page 22. (Read 167834 times)