[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[Cocakiko]

Any one can mining ?. My mining can't mining at this time

[qiwoman2]

What's going on with BURST?
TEAM.US forum is down, Burstnation wallets don't work? How can I login to my online wallet? Anyone have a link to the online wallets/ I run an asset and can't even login.. there are no wallets that work.. 

[unsoindovo]

What's going on with BURST?
TEAM.US forum is down, Burstnation wallets don't work? How can I login to my online wallet? Anyone have a link to the online wallets/ I run an asset and can't even login.. there are no wallets that work.. 

we are under heavy attack since 2 days.
we hope all sops as soon as possible!

[IncludeBeer]

I'm re-syncing local wallet with new trusted peers, then switching to solo as soon as I can change the reward recipient.

It's important for miners to keep mining in order to clear this backlog of transactions the attack as created. I suggest anyone with >20tb to put in the effort and start solo mining.

[unsoindovo]

I'm re-syncing local wallet with new trusted peers, then switching to solo as soon as I can change the reward recipient.

It's important for miners to keep mining in order to clear this backlog of transactions the attack as created. I suggest anyone with >20tb to put in the effort and start solo mining.

but what about this?
"I'm re-syncing local wallet with new trusted peers"
there are an official list of Trusted peers?
can you share plz?

[cico76]

Attack seems over, mining seems working again 

I still continue supporting burst project, hope the best !

[unsoindovo]

Attack seems over, mining seems working again 

I still continue supporting burst project, hope the best !

i'm running my local burst wallet...
but blockchain download stucks at block 383589   19/07/2017 21:13:48
then in "Peers" i have just one peer,  128.171.156.20:8123, who is disconnected...
confused

[IncludeBeer]

I'm re-syncing local wallet with new trusted peers, then switching to solo as soon as I can change the reward recipient.

It's important for miners to keep mining in order to clear this backlog of transactions the attack as created. I suggest anyone with >20tb to put in the effort and start solo mining.

but what about this?
"I'm re-syncing local wallet with new trusted peers"
there are an official list of Trusted peers?
can you share plz?

In ./conf/nxt-default.properties, update the nxt.wellKnownPeers list:

Code:

# A list of well known peer addresses / host names, separated by '; '.
# If not set, a random selection of nxtcrypto.org and nxtbase.com nodes is used.
nxt.wellKnownPeers=83.250.186.91; 192.99.183.10; 70.119.104.149; 18.116.7.200; 211.222.98.243; 84.249.20.155; 81.184.125.16; 210.115.228.231; 88.222.9.72; 171.98.174.125; 162.248.78.98; 38.114.101.88; 38.114.101.87; 158.69.53.36; 176.9.25.254; 5.104.175.157; 76.121.196.154; 70.180.246.148; 171.100.184.6; 192.99.47.76; 5.9.124.68; 213.160.187.186; 1.179.201.220; 75.158.125.140; 59.120.184.135; 112.105.73.21; 160.36.130.180; 173.179.191.134; 178.136.98.153; 5.104.175.162; 212.43.86.74; 91.121.159.44; 203.59.236.69; 5.9.119.180; 70.95.197.163; 62.210.81.172; 88.99.249.245; 195.154.163.156; 89.179.240.131; 92.81.73.43; 178.63.87.215; 211.218.247.79; 71.166.55.129; 5.104.175.152; 164.106.37.6; 5.104.175.154; 162.236.93.205; 75.189.195.82; 5.104.175.134; 5.104.175.136; 5.104.175.138; 190.78.44.106; 176.24.198.205; 171.233.128.63; 137.248.121.73; 128.171.156.20; 84.17.23.54; 88.106.222.81; 204.45.61.2; 85.217.171.59; 184.161.232.180; 213.113.246.35; 38.114.101.90; 87.98.244.116; 199.189.85.178; 111.90.145.100; 218.38.28.183; 217.66.97.39; 5.104.175.11; 203.158.118.10; [2607:5300:60:524c:0:0:0:0]; 70.76.243.58; 74.139.77.215; 217.66.97.34; 151.80.42.137; 183.89.99.48; 45.32.107.157; 92.109.126.47; 176.9.118.214; 101.99.32.44; 62.75.187.160; 91.189.160.214; 217.66.97.41; 78.46.37.137; 103.251.107.78; 98.223.117.112; 95.165.143.249; 5.153.225.55; 109.190.100.208; 5.189.165.186; 213.136.69.222; 66.96.234.230; 81.94.202.156; 84.25.201.228; 94.142.234.173; 202.5.195.252; 121.99.231.47; 162.248.4.26; 178.113.203.215; 85.10.211.130; 192.161.209.104; 185.144.131.131; 89.14.109.186; 112.167.81.44; 158.129.212.236; 86.19.102.12; 211.104.175.60; 87.98.145.132; 128.171.53.34; 173.238.248.170; 5.104.175.110; 46.237.194.160; 89.244.174.96; 5.104.175.211; 37.120.185.33; 46.4.126.236; 136.243.70.45; 108.238.244.144; 5.104.175.214; 112.161.84.93; 80.122.157.25; 5.9.106.250; 185.157.21.85; 176.9.43.13; 67.68.14.47; 69.165.74.83; 5.135.177.9;

Also, to help other nodes in the network, add yourIP:8123 to the line nxt.myAddress=, so it looks like "nxt.myAddress=111.111.111.111:8123", and forward 8123 if behind a NAT. This is your public ipv4 address (or ipv6 if that's what you get from your isp). You can get it from simple google search: https://www.google.com/search?q=whatismyipaddress

[IncludeBeer]

Attack seems over, mining seems working again 

I still continue supporting burst project, hope the best !

Attack is definitely not over. There are still a couple day's worth of transactions the blockchain needs to process.

[unsoindovo]

I'm re-syncing local wallet with new trusted peers, then switching to solo as soon as I can change the reward recipient.

It's important for miners to keep mining in order to clear this backlog of transactions the attack as created. I suggest anyone with >20tb to put in the effort and start solo mining.

but what about this?
"I'm re-syncing local wallet with new trusted peers"
there are an official list of Trusted peers?
can you share plz?

In ./conf/nxt-default.properties, update the nxt.wellKnownPeers list:

Code:

# A list of well known peer addresses / host names, separated by '; '.
# If not set, a random selection of nxtcrypto.org and nxtbase.com nodes is used.
nxt.wellKnownPeers=83.250.186.91; 192.99.183.10; 70.119.104.149; 18.116.7.200; 211.222.98.243; 84.249.20.155; 81.184.125.16; 210.115.228.231; 88.222.9.72; 171.98.174.125; 162.248.78.98; 38.114.101.88; 38.114.101.87; 158.69.53.36; 176.9.25.254; 5.104.175.157; 76.121.196.154; 70.180.246.148; 171.100.184.6; 192.99.47.76; 5.9.124.68; 213.160.187.186; 1.179.201.220; 75.158.125.140; 59.120.184.135; 112.105.73.21; 160.36.130.180; 173.179.191.134; 178.136.98.153; 5.104.175.162; 212.43.86.74; 91.121.159.44; 203.59.236.69; 5.9.119.180; 70.95.197.163; 62.210.81.172; 88.99.249.245; 195.154.163.156; 89.179.240.131; 92.81.73.43; 178.63.87.215; 211.218.247.79; 71.166.55.129; 5.104.175.152; 164.106.37.6; 5.104.175.154; 162.236.93.205; 75.189.195.82; 5.104.175.134; 5.104.175.136; 5.104.175.138; 190.78.44.106; 176.24.198.205; 171.233.128.63; 137.248.121.73; 128.171.156.20; 84.17.23.54; 88.106.222.81; 204.45.61.2; 85.217.171.59; 184.161.232.180; 213.113.246.35; 38.114.101.90; 87.98.244.116; 199.189.85.178; 111.90.145.100; 218.38.28.183; 217.66.97.39; 5.104.175.11; 203.158.118.10; [2607:5300:60:524c:0:0:0:0]; 70.76.243.58; 74.139.77.215; 217.66.97.34; 151.80.42.137; 183.89.99.48; 45.32.107.157; 92.109.126.47; 176.9.118.214; 101.99.32.44; 62.75.187.160; 91.189.160.214; 217.66.97.41; 78.46.37.137; 103.251.107.78; 98.223.117.112; 95.165.143.249; 5.153.225.55; 109.190.100.208; 5.189.165.186; 213.136.69.222; 66.96.234.230; 81.94.202.156; 84.25.201.228; 94.142.234.173; 202.5.195.252; 121.99.231.47; 162.248.4.26; 178.113.203.215; 85.10.211.130; 192.161.209.104; 185.144.131.131; 89.14.109.186; 112.167.81.44; 158.129.212.236; 86.19.102.12; 211.104.175.60; 87.98.145.132; 128.171.53.34; 173.238.248.170; 5.104.175.110; 46.237.194.160; 89.244.174.96; 5.104.175.211; 37.120.185.33; 46.4.126.236; 136.243.70.45; 108.238.244.144; 5.104.175.214; 112.161.84.93; 80.122.157.25; 5.9.106.250; 185.157.21.85; 176.9.43.13; 67.68.14.47; 69.165.74.83; 5.135.177.9;

Also, to help other nodes in the network, add yourIP:8123 to the line nxt.myAddress=, so it looks like "nxt.myAddress=111.111.111.111:8123", and forward 8123 if behind a NAT. This is your public ipv4 address (or ipv6 if that's what you get from your isp). You can get it from simple google search: https://www.google.com/search?q=whatismyipaddress

thank you a lot for the tip!!
i hope this wil fix my local wallet and let it sync...
UPDATE...
it works like a charm :-)
thank you again

[cico76]

2017-07-22 22:52:49 INFO: Last block height: 384480
Firewall Port open.
Happy syncing... 

[unsoindovo]

2017-07-22 22:52:49 INFO: Last block height: 384480
Firewall Port open.
Happy syncing... 

great works!!!
I definitely resolved updating the list of peers.
now i can try to solo mining to see if all works fine

[seasonw]

So, what is the updates now? Any new fix to wallet or any plan from burst team (this time I really meant burst dev team, lol...)?

I think I was on different blockchain right now, mined burst does not show at burstcoin.biz block explorer... Or burstcoin.biz also in different blockchain 

[wilkas]

After running local wallet it shows following and then quits. Have edited trusted peers. What else can I do?

Code:

Initializing Burst server version 1.2.8
2017-07-23 04:59:36 INFO: nxt.enableStackTraces = "true"
2017-07-23 04:59:36 INFO: nxt.enableLogTraceback = "false"
2017-07-23 04:59:36 INFO: logging enabled
2017-07-23 04:59:36 INFO: nxt.disableGenerateBlocksThread not defined, assuming false
2017-07-23 04:59:36 INFO: nxt.dbCacheKB = "0"
2017-07-23 04:59:36 INFO: nxt.maxRollback = "1440"
2017-07-23 04:59:36 INFO: nxt.isTestnet = "false"
2017-07-23 04:59:36 INFO: nxt.isOffline = "false"
2017-07-23 04:59:36 INFO: nxt.dbUrl = "jdbc:h2:./burst_db/burst;DB_CLOSE_ON_EXIT=FALSE"
2017-07-23 04:59:36 INFO: nxt.maxDbConnections = "30"
2017-07-23 04:59:36 INFO: nxt.dbLoginTimeout = "70"
2017-07-23 04:59:36 INFO: nxt.dbDefaultLockTimeout = "60"

[cyberspacemonkey]

After running local wallet it shows following and then quits. Have edited trusted peers. What else can I do?

Code:

Initializing Burst server version 1.2.8
2017-07-23 04:59:36 INFO: nxt.enableStackTraces = "true"
2017-07-23 04:59:36 INFO: nxt.enableLogTraceback = "false"
2017-07-23 04:59:36 INFO: logging enabled
2017-07-23 04:59:36 INFO: nxt.disableGenerateBlocksThread not defined, assuming false
2017-07-23 04:59:36 INFO: nxt.dbCacheKB = "0"
2017-07-23 04:59:36 INFO: nxt.maxRollback = "1440"
2017-07-23 04:59:36 INFO: nxt.isTestnet = "false"
2017-07-23 04:59:36 INFO: nxt.isOffline = "false"
2017-07-23 04:59:36 INFO: nxt.dbUrl = "jdbc:h2:./burst_db/burst;DB_CLOSE_ON_EXIT=FALSE"
2017-07-23 04:59:36 INFO: nxt.maxDbConnections = "30"
2017-07-23 04:59:36 INFO: nxt.dbLoginTimeout = "70"
2017-07-23 04:59:36 INFO: nxt.dbDefaultLockTimeout = "60"

If you have the properties file configured right without any missing punctuation or anything like that which could cause wallet to crash, it sounds like you may have to delete the db and sync from scratch.

[wilkas]

It seems that moving db files to another folder has solved issue of wallet not starting. But now it'll take whole day to download blockchain again. How can I prevent this from hapenning again?

[cyberspacemonkey]

It seems that moving db files to another folder has solved issue of wallet not starting. But now it'll take whole day to download blockchain again. How can I prevent this from hapenning again?

My suggestion is to make a backup of the db once it's all caught up without any issues in case your wallet crashes in the future with new blocks, then you can just replace it with the one you backed up so you don't have to start from scratch.

[cico76]

Code:

Exception in thread "Thread-1" java.lang.NoClassDefFoundError: Could not initialize class nxt.db.Db
        at nxt.Nxt.shutdown(Nxt.java:179)
        at nxt.Nxt$1.run(Nxt.java:158)
        at java.lang.Thread.run(Thread.java:745)

Wallet crashed, no way to start again, null pointer inside blockchain.

Rebuilding from scratch ... 

Still don't understand the sense of this hacking attack.

Nice WE to the comunity.

[Trollollo]

Right now all people should update peers like it is described on previous page,and start solo mining.And do not forget to copy blockchain database once it is downloaded.

[unsoindovo]

Code:

Exception in thread "Thread-1" java.lang.NoClassDefFoundError: Could not initialize class nxt.db.Db
        at nxt.Nxt.shutdown(Nxt.java:179)
        at nxt.Nxt$1.run(Nxt.java:158)
        at java.lang.Thread.run(Thread.java:745)

Wallet crashed, no way to start again, null pointer inside blockchain.

Rebuilding from scratch ... 

Still don't understand the sense of this hacking attack.

Nice WE to the comunity.

i think crowetic got the right decision to go away.
Basically burst coin is attacked so frequently because the core have bug...
after dozens of attack, i think this is the only reason.