coinits
Legendary
 Offline
Activity: 1582
Merit: 1019
011110000110110101110010
|
 |
November 04, 2014, 01:57:27 AM |
|
Nice progress being made with the coin. debating to get 60TH of hdd space n see where it leads me to maybe not worth it or maybe worth if prices on hdds come down some more. Nice to see burst finaly over 100 satoshi lets see 1k next  some one just bought 10 BTC worth of burst in a hurry, instead of creating buy support.. I was expecting that. "someone" just did a giant pull request and comitted it to the source repository.. When that happened i was thinking, heh, someone will probably front run the next version and buy some burst... and it happened.. i'm just mining, so this is a tip for those that might know how to follow a git repo. Let's just agree that dev is NOT asleep and that lots of interesting stuff is coming up sooner or later. Sometimes i wonder if we only have one dev, or an anonymous team behind the dev persona - cause the activity is huge.. on the other hand, more devs would probably look different on github (more branches and merging) Anyone who knows how to program & want to make a good buck, go invest $10K in burst, then start actively developing burst, and commit some good pull requests.. news that the dev team has grown will make your $10K investment double or more in no time. (of course you need to be a pretty good dev to begin with) Soon burst mining will yield not so much burst coins, lower supply should raise the price if we can keep demand up, and with this and future feature sets, i see no way for demand to go but higher. way higher.. almost noone ever head of burst, we're still pretty stealthy considering the unique feature set. yeah thats true, watch github burst repo, because dev is alive and kicking as always Link? |
Jump you fuckers! | The thing about smart motherfuckers is they sound like crazy motherfuckers to dumb motherfuckers. | My sig space for rent for 0.01 btc per week.
|
|
|
|
|
|
|
|
The trust scores you see are subjective; they will change depending on who you have in your trust list. |
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
uray
|
|
November 04, 2014, 01:59:28 AM |
|
Nice progress being made with the coin. debating to get 60TH of hdd space n see where it leads me to maybe not worth it or maybe worth if prices on hdds come down some more. Nice to see burst finaly over 100 satoshi lets see 1k next some one just bought 10 BTC worth of burst in a hurry, instead of creating buy support.. I was expecting that. "someone" just did a giant pull request and comitted it to the source repository.. When that happened i was thinking, heh, someone will probably front run the next version and buy some burst... and it happened.. i'm just mining, so this is a tip for those that might know how to follow a git repo. Let's just agree that dev is NOT asleep and that lots of interesting stuff is coming up sooner or later. Sometimes i wonder if we only have one dev, or an anonymous team behind the dev persona - cause the activity is huge.. on the other hand, more devs would probably look different on github (more branches and merging) Anyone who knows how to program & want to make a good buck, go invest $10K in burst, then start actively developing burst, and commit some good pull requests.. news that the dev team has grown will make your $10K investment double or more in no time. (of course you need to be a pretty good dev to begin with) Soon burst mining will yield not so much burst coins, lower supply should raise the price if we can keep demand up, and with this and future feature sets, i see no way for demand to go but higher. way higher.. almost noone ever head of burst, we're still pretty stealthy considering the unique feature set. yeah thats true, watch github burst repo, because dev is alive and kicking as always Link? I won't tell you, its secret ... HAHAHAHA LOL |
|
|
|
|
|
BTCMILLIONAIRE
|
|
November 04, 2014, 02:02:39 AM |
|
Nice progress being made with the coin. debating to get 60TH of hdd space n see where it leads me to maybe not worth it or maybe worth if prices on hdds come down some more. Nice to see burst finaly over 100 satoshi lets see 1k next some one just bought 10 BTC worth of burst in a hurry, instead of creating buy support.. it was moi  |
|
|
|
|
|
burstcoin (OP)
|
|
November 04, 2014, 03:08:03 AM |
|
Burst 1.1.5Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7 Or github: https://github.com/BurstProject/burstcoinUpdate is required for all users. Hard fork will be triggered at least 4-5 days from now, depends on how fast people update. If using an existing copy of the blockchain, first startup will take several minutes. Short summary: Updated to latest Nxt(1.3.2) Added subscriptions(reoccurring payments)(more details will be given when enabled) Escrow updated to use result transactions instead of just adding to balance. Longer story: This release took far longer than I intended it to. Subscriptions turned out to be more of a challenge than expected, and about when I had a first release candidate, nxt 1.3.0 was released. Nxt 1.3.0 was a massive restructuring which I considered a necessary update since it was to fix scalability issues I already knew would need to be addressed at some point, however it broke compatibility with a lot of my code. Rather than debugging subscriptions, then updating, and debugging it again, I went straight to updating to Nxt 1.3.0, which required me to re-write most of the subscription, escrow, and reward recipient assignment code. Nxt 1.3.1 and 1.3.2 were also released fairly shortly after, and their updates went a lot more smoothly. Re-testing everything took some time, and I ended up re-factoring subscriptions a few times to ensure everything was done consistently. Next plans: I'm going to be postponing the last part of advanced transactions for now, and starting on BurstID(more details will be given later), and maybe some of the DHT code.
|
BURST-QHCJ-9HB5-PTGC-5Q8J9
|
|
|
|
BurstBurst
|
|
November 04, 2014, 03:54:20 AM |
|
Great. Updating now ... Burst 1.1.5Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7 Or github: https://github.com/BurstProject/burstcoinUpdate is required for all users. Hard fork will be triggered at least 4-5 days from now, depends on how fast people update. If using an existing copy of the blockchain, first startup will take several minutes. Short summary: Updated to latest Nxt(1.3.2) Added subscriptions(reoccurring payments)(more details will be given when enabled) Escrow updated to use result transactions instead of just adding to balance. Longer story: This release took far longer than I intended it to. Subscriptions turned out to be more of a challenge than expected, and about when I had a first release candidate, nxt 1.3.0 was released. Nxt 1.3.0 was a massive restructuring which I considered a necessary update since it was to fix scalability issues I already knew would need to be addressed at some point, however it broke compatibility with a lot of my code. Rather than debugging subscriptions, then updating, and debugging it again, I went straight to updating to Nxt 1.3.0, which required me to re-write most of the subscription, escrow, and reward recipient assignment code. Nxt 1.3.1 and 1.3.2 were also released fairly shortly after, and their updates went a lot more smoothly. Re-testing everything took some time, and I ended up re-factoring subscriptions a few times to ensure everything was done consistently. Next plans: I'm going to be postponing the last part of advanced transactions for now, and starting on BurstID(more details will be given later), and maybe some of the DHT code. |
|
|
|
|
|
numbertech
|
|
November 04, 2014, 05:53:28 AM |
|
Sound Good. Burst 1.1.5Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7 Or github: https://github.com/BurstProject/burstcoinUpdate is required for all users. Hard fork will be triggered at least 4-5 days from now, depends on how fast people update. If using an existing copy of the blockchain, first startup will take several minutes. Short summary: Updated to latest Nxt(1.3.2) Added subscriptions(reoccurring payments)(more details will be given when enabled) Escrow updated to use result transactions instead of just adding to balance. Longer story: This release took far longer than I intended it to. Subscriptions turned out to be more of a challenge than expected, and about when I had a first release candidate, nxt 1.3.0 was released. Nxt 1.3.0 was a massive restructuring which I considered a necessary update since it was to fix scalability issues I already knew would need to be addressed at some point, however it broke compatibility with a lot of my code. Rather than debugging subscriptions, then updating, and debugging it again, I went straight to updating to Nxt 1.3.0, which required me to re-write most of the subscription, escrow, and reward recipient assignment code. Nxt 1.3.1 and 1.3.2 were also released fairly shortly after, and their updates went a lot more smoothly. Re-testing everything took some time, and I ended up re-factoring subscriptions a few times to ensure everything was done consistently. Next plans: I'm going to be postponing the last part of advanced transactions for now, and starting on BurstID(more details will be given later), and maybe some of the DHT code. |
|
|
|
|
|
Irontiga
|
|
November 04, 2014, 06:07:04 AM |
|
Sound Good.
Lol, if you guys have ever tried using api etc. you would know that this is MASSIVE!!! |
|
|
|
|
|
BTCMILLIONAIRE
|
|
November 04, 2014, 06:11:52 AM |
|
This is HUGE  Price should skyrocket |
|
|
|
|
SirEGB
Member
Offline
Activity: 142
Merit: 10
|
|
November 04, 2014, 06:24:01 AM |
|
This is HUGE Price should skyrocket I would hope so but if it does then it should happen a few days after.  |
|
|
|
|
e1ghtSpace
Legendary
Offline
Activity: 1526
Merit: 1001
Crypto since 2014
|
|
November 04, 2014, 06:47:46 AM |
|
Ok, I just invested 0.06. I hope to cash out at 0.6. |
|
|
|
|
|
Moonbyte1984
|
|
November 04, 2014, 07:29:41 AM |
|
Burst 1.1.5Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7 Or github: https://github.com/BurstProject/burstcoinUpdate is required for all users. Hard fork will be triggered at least 4-5 days from now, depends on how fast people update. If using an existing copy of the blockchain, first startup will take several minutes. Short summary: Updated to latest Nxt(1.3.2) Added subscriptions(reoccurring payments)(more details will be given when enabled) Escrow updated to use result transactions instead of just adding to balance. Longer story: This release took far longer than I intended it to. Subscriptions turned out to be more of a challenge than expected, and about when I had a first release candidate, nxt 1.3.0 was released. Nxt 1.3.0 was a massive restructuring which I considered a necessary update since it was to fix scalability issues I already knew would need to be addressed at some point, however it broke compatibility with a lot of my code. Rather than debugging subscriptions, then updating, and debugging it again, I went straight to updating to Nxt 1.3.0, which required me to re-write most of the subscription, escrow, and reward recipient assignment code. Nxt 1.3.1 and 1.3.2 were also released fairly shortly after, and their updates went a lot more smoothly. Re-testing everything took some time, and I ended up re-factoring subscriptions a few times to ensure everything was done consistently. Next plans: I'm going to be postponing the last part of advanced transactions for now, and starting on BurstID(more details will be given later), and maybe some of the DHT code. How you can trigger hard fork manual? I was think that exactly point of time programmed directly in code of new wallet. You have another way to set start of new fork? |
|
|
|
|
unsoindovo
Legendary
Offline
Activity: 1932
Merit: 1042
https://locktrip.com/?refId=40964
|
|
November 04, 2014, 07:37:39 AM |
|
Burst 1.1.5Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7 Or github: https://github.com/BurstProject/burstcoinUpdate is required for all users. Hard fork will be triggered at least 4-5 days from now, depends on how fast people update. If using an existing copy of the blockchain, first startup will take several minutes. Short summary: Updated to latest Nxt(1.3.2) Added subscriptions(reoccurring payments)(more details will be given when enabled) Escrow updated to use result transactions instead of just adding to balance. Longer story: This release took far longer than I intended it to. Subscriptions turned out to be more of a challenge than expected, and about when I had a first release candidate, nxt 1.3.0 was released. Nxt 1.3.0 was a massive restructuring which I considered a necessary update since it was to fix scalability issues I already knew would need to be addressed at some point, however it broke compatibility with a lot of my code. Rather than debugging subscriptions, then updating, and debugging it again, I went straight to updating to Nxt 1.3.0, which required me to re-write most of the subscription, escrow, and reward recipient assignment code. Nxt 1.3.1 and 1.3.2 were also released fairly shortly after, and their updates went a lot more smoothly. Re-testing everything took some time, and I ended up re-factoring subscriptions a few times to ensure everything was done consistently. Next plans: I'm going to be postponing the last part of advanced transactions for now, and starting on BurstID(more details will be given later), and maybe some of the DHT code. Good job dev. I follow constantly you git hub update. I see your hard work. But i want to propose something new. What about the possibility to open a simple burstShop with computer hardware? Maybe starting with a few part like some hdd or cpu, And increment part type step by step. I remember the really good idea of kimoshop... But for kimo the thinks are gone wrong for dev error. But i repeat....i thin it is a good idea. I hope someone can do it!!!! Maybe with opensource platform like magento. What do you think about? |
|
|
|
|
Moonbyte1984
|
|
November 04, 2014, 07:48:12 AM |
|
Dev.
I think first to do is "stand alone" wallet like NXT. I understand that it only html wrap of java engine, but for users it much better to use.
Early I tired to explain to newbie how to use Burst wallet. It is very serios thing to improve distribution of Burst, but easy to make.
|
|
|
|
|
|
|
|
callmejack
|
|
November 04, 2014, 08:33:04 AM |
|
Burst 1.1.5Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7 Or github: https://github.com/BurstProject/burstcoinUpdate is required for all users. Hard fork will be triggered at least 4-5 days from now, depends on how fast people update. If using an existing copy of the blockchain, first startup will take several minutes. Short summary: Updated to latest Nxt(1.3.2) Added subscriptions(reoccurring payments)(more details will be given when enabled) Escrow updated to use result transactions instead of just adding to balance. Longer story: This release took far longer than I intended it to. Subscriptions turned out to be more of a challenge than expected, and about when I had a first release candidate, nxt 1.3.0 was released. Nxt 1.3.0 was a massive restructuring which I considered a necessary update since it was to fix scalability issues I already knew would need to be addressed at some point, however it broke compatibility with a lot of my code. Rather than debugging subscriptions, then updating, and debugging it again, I went straight to updating to Nxt 1.3.0, which required me to re-write most of the subscription, escrow, and reward recipient assignment code. Nxt 1.3.1 and 1.3.2 were also released fairly shortly after, and their updates went a lot more smoothly. Re-testing everything took some time, and I ended up re-factoring subscriptions a few times to ensure everything was done consistently. Next plans: I'm going to be postponing the last part of advanced transactions for now, and starting on BurstID(more details will be given later), and maybe some of the DHT code. a git based update worked like always really smooth for me. great work. i have realized that the sort order of my forged blocks starts with the oldest first. is there a simple way to show the newest first (like it was) to be able to see the latest forged blocks (the ui only shows 100 blocks)? i have'nt checked the java code yet and i don't know if the sort got removed for performance reasons. |
|
|
|
MaSch242
Newbie
Offline
Activity: 12
Merit: 0
|
|
November 04, 2014, 09:09:46 AM |
|
i can not login after the update. burst is up and running, accepting solo-mining connections, but i can't login message: 'Could not connect to server.' browser cache cleared, tried different browser.. 2014-11-04 10:03:12 INFO: nxt.enableStackTraces = "true"
2014-11-04 10:03:12 INFO: nxt.enableLogTraceback = "false"
2014-11-04 10:03:12 INFO: logging enabled
2014-11-04 10:03:12 INFO: nxt.dbCacheKB = "0"
2014-11-04 10:03:12 INFO: nxt.maxRollback = "1440"
2014-11-04 10:03:12 INFO: nxt.isTestnet = "false"
2014-11-04 10:03:12 INFO: nxt.isOffline = "false"
2014-11-04 10:03:12 INFO: nxt.dbUrl = "jdbc:h2:burst_db/burst;DB_CLOSE_ON_EXIT=FALSE"
2014-11-04 10:03:12 FINE: Database jdbc url set to: jdbc:h2:burst_db/burst;DB_CLOSE_ON_EXIT=FALSE;CACHE_SIZE=60416
2014-11-04 10:03:12 INFO: nxt.maxDbConnections = "30"
2014-11-04 10:03:12 INFO: nxt.dbLoginTimeout = "70"
2014-11-04 10:03:12 INFO: nxt.dbDefaultLockTimeout = "60"
2014-11-04 10:03:13 INFO: nxt.enableTransactionRebroadcasting = "true"
2014-11-04 10:03:13 INFO: nxt.testUnconfirmedTransactions not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.trimDerivedTables = "true"
2014-11-04 10:03:13 INFO: nxt.forceScan = "false"
2014-11-04 10:03:13 INFO: nxt.forceValidate = "false"
2014-11-04 10:03:13 INFO: nxt.disableGetMoreBlocksThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disableProcessTransactionsThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disableRemoveUnconfirmedTransactionsThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disableRebroadcastTransactionsThread not defined, assuming false
2014-11-04 10:03:13 FINE: Database connection pool current size: 1
2014-11-04 10:03:13 INFO: Database update may take a while if needed, current db version 143...
2014-11-04 10:03:13 INFO: nxt.myPlatform = "PC"
2014-11-04 10:03:13 INFO: nxt.myAddress not defined
2014-11-04 10:03:13 INFO: nxt.peerServerPort = "8123"
2014-11-04 10:03:13 INFO: nxt.shareMyAddress = "true"
2014-11-04 10:03:13 INFO: nxt.myHallmark not defined
2014-11-04 10:03:13 FINE: My peer info:
{"shareAddress":true,"platform":"PC","application":"NRS","version":"1.1.5"}
2014-11-04 10:03:13 INFO: nxt.wellKnownPeers = "198.199.103.145; 178.62.39.204; burst.cryptoport.io; 192.155.252.202; 37.58.107.74; 119.81.165.138; 119.81.44.170; 119.81.44.171"
2014-11-04 10:03:13 INFO: nxt.knownBlacklistedPeers not defined
2014-11-04 10:03:13 INFO: nxt.maxNumberOfConnectedPublicPeers = "20"
2014-11-04 10:03:13 INFO: nxt.connectTimeout = "4000"
2014-11-04 10:03:13 INFO: nxt.readTimeout = "8000"
2014-11-04 10:03:13 INFO: nxt.enableHallmarkProtection = "false"
2014-11-04 10:03:13 INFO: nxt.pushThreshold = "0"
2014-11-04 10:03:13 INFO: nxt.pullThreshold = "0"
2014-11-04 10:03:13 INFO: nxt.blacklistingPeriod = "600000"
2014-11-04 10:03:13 INFO: nxt.communicationLoggingMask = "0"
2014-11-04 10:03:13 INFO: nxt.sendToPeersLimit = "10"
2014-11-04 10:03:13 INFO: nxt.usePeersDb = "true"
2014-11-04 10:03:13 INFO: nxt.savePeers = "true"
2014-11-04 10:03:13 INFO: nxt.getMorePeers = "true"
2014-11-04 10:03:13 INFO: nxt.dumpPeersVersion not defined
2014-11-04 10:03:13 INFO: nxt.disablePeerConnectingThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disablePeerUnBlacklistingThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disableGetMorePeersThread not defined, assuming false
2014-11-04 10:03:13 INFO: Logging initialized @704ms
2014-11-04 10:03:13 INFO: nxt.peerServerHost = "0.0.0.0"
2014-11-04 10:03:13 INFO: nxt.peerServerIdleTimeout = "30000"
2014-11-04 10:03:13 INFO: nxt.enablePeerServerGZIPFilter = "true"
2014-11-04 10:03:13 INFO: nxt.enablePeerServerDoSFilter = "true"
2014-11-04 10:03:13 INFO: nxt.peerServerDoSFilter.maxRequestsPerSec = "30"
2014-11-04 10:03:13 INFO: nxt.peerServerDoSFilter.delayMs = "1000"
2014-11-04 10:03:13 INFO: nxt.peerServerDoSFilter.maxRequestMs = "300000"
2014-11-04 10:03:13 INFO: nxt.disableGenerateBlocksThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.enableDebugAPI = "false"
2014-11-04 10:03:13 INFO: nxt.allowedBotHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1]; ************************"
2014-11-04 10:03:13 INFO: nxt.enableAPIServer = "true"
2014-11-04 10:03:13 INFO: nxt.apiServerPort = "8125"
2014-11-04 10:03:13 INFO: nxt.apiServerHost = "0.0.0.0"
2014-11-04 10:03:13 INFO: nxt.apiSSL = "false"
2014-11-04 10:03:13 INFO: nxt.apiServerIdleTimeout = "30000"
2014-11-04 10:03:13 INFO: nxt.apiResourceBase = "html/ui"
2014-11-04 10:03:13 INFO: nxt.javadocResourceBase = "html/doc"
2014-11-04 10:03:13 INFO: nxt.enableAPIServerGZIPFilter = "false"
2014-11-04 10:03:13 INFO: nxt.apiServerCORS = "false"
2014-11-04 10:03:13 INFO: nxt.allowedUserHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2014-11-04 10:03:13 INFO: nxt.enableUIServer = "false"
2014-11-04 10:03:13 INFO: User interface server not enabled
2014-11-04 10:03:13 INFO: nxt.debugTraceQuote = """
2014-11-04 10:03:13 INFO: nxt.debugTraceSeparator = " "
2014-11-04 10:03:13 INFO: nxt.debugLogUnconfirmed = "false"
2014-11-04 10:03:13 INFO: nxt.debugTraceAccounts not defined
2014-11-04 10:03:13 INFO: nxt.debugTraceLog = "nxt-trace.csv"
2014-11-04 10:03:13 FINE: Running 2 tasks...
2014-11-04 10:03:13 FINE: Loading known peers from the database...
2014-11-04 10:03:13 INFO: Genesis block already in database
2014-11-04 10:03:13 FINE: Database connection pool current size: 2
2014-11-04 10:03:14 INFO: Last block height: 30354
2014-11-04 10:03:14 FINE: Running 2 final tasks...
2014-11-04 10:03:14 INFO: jetty-9.2.3.v20140905
2014-11-04 10:03:14 INFO: jetty-9.2.3.v20140905
2014-11-04 10:03:14 INFO: Started o.e.j.s.h.ContextHandler@183a41c{/doc,null,AVAILABLE}
2014-11-04 10:03:14 INFO: Started o.e.j.s.ServletContextHandler@b785fe{/,null,AVAILABLE}
2014-11-04 10:03:14 INFO: Started ServerConnector@f63387{HTTP/1.1}{0.0.0.0:8125}
2014-11-04 10:03:14 INFO: Started ServerConnector@6343c4{HTTP/1.1}{0.0.0.0:8123}
2014-11-04 10:03:14 INFO: Started @1874ms
2014-11-04 10:03:14 INFO: Started @1874ms
2014-11-04 10:03:14 INFO: Started API server at 0.0.0.0:8125
2014-11-04 10:03:14 INFO: Started peer networking server at 0.0.0.0:8123
2014-11-04 10:03:14 FINE: Starting 8 background jobs
2014-11-04 10:03:14 FINE: Starting 2 delayed tasks
2014-11-04 10:03:14 INFO: Initialization took 1 seconds
2014-11-04 10:03:14 INFO: Burst server 1.1.5 started successfully.
2014-11-04 10:03:14 FINE: Known peers: 302
2014-11-04 10:03:14 INFO: nxt.apiServerEnforcePOST = "true"
|
|
|
|
|
|
callmejack
|
|
November 04, 2014, 09:39:28 AM |
|
i can not login after the update. burst is up and running, accepting solo-mining connections, but i can't login message: 'Could not connect to server.' browser cache cleared, tried different browser.. 2014-11-04 10:03:12 INFO: nxt.enableStackTraces = "true"
2014-11-04 10:03:12 INFO: nxt.enableLogTraceback = "false"
2014-11-04 10:03:12 INFO: logging enabled
2014-11-04 10:03:12 INFO: nxt.dbCacheKB = "0"
2014-11-04 10:03:12 INFO: nxt.maxRollback = "1440"
2014-11-04 10:03:12 INFO: nxt.isTestnet = "false"
2014-11-04 10:03:12 INFO: nxt.isOffline = "false"
2014-11-04 10:03:12 INFO: nxt.dbUrl = "jdbc:h2:burst_db/burst;DB_CLOSE_ON_EXIT=FALSE"
2014-11-04 10:03:12 FINE: Database jdbc url set to: jdbc:h2:burst_db/burst;DB_CLOSE_ON_EXIT=FALSE;CACHE_SIZE=60416
2014-11-04 10:03:12 INFO: nxt.maxDbConnections = "30"
2014-11-04 10:03:12 INFO: nxt.dbLoginTimeout = "70"
2014-11-04 10:03:12 INFO: nxt.dbDefaultLockTimeout = "60"
2014-11-04 10:03:13 INFO: nxt.enableTransactionRebroadcasting = "true"
2014-11-04 10:03:13 INFO: nxt.testUnconfirmedTransactions not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.trimDerivedTables = "true"
2014-11-04 10:03:13 INFO: nxt.forceScan = "false"
2014-11-04 10:03:13 INFO: nxt.forceValidate = "false"
2014-11-04 10:03:13 INFO: nxt.disableGetMoreBlocksThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disableProcessTransactionsThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disableRemoveUnconfirmedTransactionsThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disableRebroadcastTransactionsThread not defined, assuming false
2014-11-04 10:03:13 FINE: Database connection pool current size: 1
2014-11-04 10:03:13 INFO: Database update may take a while if needed, current db version 143...
2014-11-04 10:03:13 INFO: nxt.myPlatform = "PC"
2014-11-04 10:03:13 INFO: nxt.myAddress not defined
2014-11-04 10:03:13 INFO: nxt.peerServerPort = "8123"
2014-11-04 10:03:13 INFO: nxt.shareMyAddress = "true"
2014-11-04 10:03:13 INFO: nxt.myHallmark not defined
2014-11-04 10:03:13 FINE: My peer info:
{"shareAddress":true,"platform":"PC","application":"NRS","version":"1.1.5"}
2014-11-04 10:03:13 INFO: nxt.wellKnownPeers = "198.199.103.145; 178.62.39.204; burst.cryptoport.io; 192.155.252.202; 37.58.107.74; 119.81.165.138; 119.81.44.170; 119.81.44.171"
2014-11-04 10:03:13 INFO: nxt.knownBlacklistedPeers not defined
2014-11-04 10:03:13 INFO: nxt.maxNumberOfConnectedPublicPeers = "20"
2014-11-04 10:03:13 INFO: nxt.connectTimeout = "4000"
2014-11-04 10:03:13 INFO: nxt.readTimeout = "8000"
2014-11-04 10:03:13 INFO: nxt.enableHallmarkProtection = "false"
2014-11-04 10:03:13 INFO: nxt.pushThreshold = "0"
2014-11-04 10:03:13 INFO: nxt.pullThreshold = "0"
2014-11-04 10:03:13 INFO: nxt.blacklistingPeriod = "600000"
2014-11-04 10:03:13 INFO: nxt.communicationLoggingMask = "0"
2014-11-04 10:03:13 INFO: nxt.sendToPeersLimit = "10"
2014-11-04 10:03:13 INFO: nxt.usePeersDb = "true"
2014-11-04 10:03:13 INFO: nxt.savePeers = "true"
2014-11-04 10:03:13 INFO: nxt.getMorePeers = "true"
2014-11-04 10:03:13 INFO: nxt.dumpPeersVersion not defined
2014-11-04 10:03:13 INFO: nxt.disablePeerConnectingThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disablePeerUnBlacklistingThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.disableGetMorePeersThread not defined, assuming false
2014-11-04 10:03:13 INFO: Logging initialized @704ms
2014-11-04 10:03:13 INFO: nxt.peerServerHost = "0.0.0.0"
2014-11-04 10:03:13 INFO: nxt.peerServerIdleTimeout = "30000"
2014-11-04 10:03:13 INFO: nxt.enablePeerServerGZIPFilter = "true"
2014-11-04 10:03:13 INFO: nxt.enablePeerServerDoSFilter = "true"
2014-11-04 10:03:13 INFO: nxt.peerServerDoSFilter.maxRequestsPerSec = "30"
2014-11-04 10:03:13 INFO: nxt.peerServerDoSFilter.delayMs = "1000"
2014-11-04 10:03:13 INFO: nxt.peerServerDoSFilter.maxRequestMs = "300000"
2014-11-04 10:03:13 INFO: nxt.disableGenerateBlocksThread not defined, assuming false
2014-11-04 10:03:13 INFO: nxt.enableDebugAPI = "false"
2014-11-04 10:03:13 INFO: nxt.allowedBotHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1]; ************************"
2014-11-04 10:03:13 INFO: nxt.enableAPIServer = "true"
2014-11-04 10:03:13 INFO: nxt.apiServerPort = "8125"
2014-11-04 10:03:13 INFO: nxt.apiServerHost = "0.0.0.0"
2014-11-04 10:03:13 INFO: nxt.apiSSL = "false"
2014-11-04 10:03:13 INFO: nxt.apiServerIdleTimeout = "30000"
2014-11-04 10:03:13 INFO: nxt.apiResourceBase = "html/ui"
2014-11-04 10:03:13 INFO: nxt.javadocResourceBase = "html/doc"
2014-11-04 10:03:13 INFO: nxt.enableAPIServerGZIPFilter = "false"
2014-11-04 10:03:13 INFO: nxt.apiServerCORS = "false"
2014-11-04 10:03:13 INFO: nxt.allowedUserHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2014-11-04 10:03:13 INFO: nxt.enableUIServer = "false"
2014-11-04 10:03:13 INFO: User interface server not enabled
2014-11-04 10:03:13 INFO: nxt.debugTraceQuote = """
2014-11-04 10:03:13 INFO: nxt.debugTraceSeparator = " "
2014-11-04 10:03:13 INFO: nxt.debugLogUnconfirmed = "false"
2014-11-04 10:03:13 INFO: nxt.debugTraceAccounts not defined
2014-11-04 10:03:13 INFO: nxt.debugTraceLog = "nxt-trace.csv"
2014-11-04 10:03:13 FINE: Running 2 tasks...
2014-11-04 10:03:13 FINE: Loading known peers from the database...
2014-11-04 10:03:13 INFO: Genesis block already in database
2014-11-04 10:03:13 FINE: Database connection pool current size: 2
2014-11-04 10:03:14 INFO: Last block height: 30354
2014-11-04 10:03:14 FINE: Running 2 final tasks...
2014-11-04 10:03:14 INFO: jetty-9.2.3.v20140905
2014-11-04 10:03:14 INFO: jetty-9.2.3.v20140905
2014-11-04 10:03:14 INFO: Started o.e.j.s.h.ContextHandler@183a41c{/doc,null,AVAILABLE}
2014-11-04 10:03:14 INFO: Started o.e.j.s.ServletContextHandler@b785fe{/,null,AVAILABLE}
2014-11-04 10:03:14 INFO: Started ServerConnector@f63387{HTTP/1.1}{0.0.0.0:8125}
2014-11-04 10:03:14 INFO: Started ServerConnector@6343c4{HTTP/1.1}{0.0.0.0:8123}
2014-11-04 10:03:14 INFO: Started @1874ms
2014-11-04 10:03:14 INFO: Started @1874ms
2014-11-04 10:03:14 INFO: Started API server at 0.0.0.0:8125
2014-11-04 10:03:14 INFO: Started peer networking server at 0.0.0.0:8123
2014-11-04 10:03:14 FINE: Starting 8 background jobs
2014-11-04 10:03:14 FINE: Starting 2 delayed tasks
2014-11-04 10:03:14 INFO: Initialization took 1 seconds
2014-11-04 10:03:14 INFO: Burst server 1.1.5 started successfully.
2014-11-04 10:03:14 FINE: Known peers: 302
2014-11-04 10:03:14 INFO: nxt.apiServerEnforcePOST = "true"
try to add ip addresses into the line with nxt.apiServerHost= for me it works with this: nxt.apiServerHost=0.0.0.0 |
|
|
|
MaSch242
Newbie
Offline
Activity: 12
Merit: 0
|
|
November 04, 2014, 10:19:19 AM |
|
got it..
localhost:8125 did not work anymore, but 127.0.0.1:8125 is working..
|
|
|
|
|
ltcnim
Legendary
Offline
Activity: 914
Merit: 1001
|
|
November 04, 2014, 10:37:17 AM
Last edit: November 04, 2014, 10:58:23 AM by ltcnim |
|
just tried to update (checkout from git), but I get an error after running compile.sh: Initializing Burst server version 1.1.5
2014-11-04 11:33:00 INFO: nxt.enableStackTraces = "true"
2014-11-04 11:33:00 INFO: nxt.enableLogTraceback = "false"
2014-11-04 11:33:00 INFO: logging enabled
2014-11-04 11:33:00 INFO: nxt.dbCacheKB = "0"
2014-11-04 11:33:00 INFO: nxt.maxRollback not defined, assuming 0
Exception in thread "main" java.lang.ExceptionInInitializerError
at nxt.db.Db.<clinit>(Db.java:81)
at nxt.Nxt$Init.<clinit>(Nxt.java:169)
at nxt.Nxt.init(Nxt.java:149)
at nxt.Nxt.main(Nxt.java:140)
Caused by: java.lang.RuntimeException: nxt.maxRollback must be at least 1440
at nxt.Constants.<clinit>(Constants.java:30)
... 4 more
2014-11-04 11:33:00 INFO: Shutting down...
2014-11-04 11:33:00 INFO: nxt.enableDebugAPI not defined, assuming false
2014-11-04 11:33:00 INFO: nxt.allowedBotHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1]; xxx.xxx.xxx.xxx;"
2014-11-04 11:33:00 INFO: nxt.enableAPIServer = "true"
Exception in thread "Thread-0" java.lang.NoClassDefFoundError: Could not initialize class nxt.Constants
at nxt.http.API.<clinit>(API.java:49)
at nxt.Nxt.shutdown(Nxt.java:154)
at nxt.Nxt$1.run(Nxt.java:137)
at java.lang.Thread.run(Thread.java:745) every other update worked fine... edit: ok, looks like the conf has changed. I usually just copy my old conf over :/ |
|
|
|
coinits
Legendary
Offline
Activity: 1582
Merit: 1019
011110000110110101110010
|
|
November 04, 2014, 12:12:04 PM |
|
Dunno what happened to you guys but the upgrade went flawlessly for me.
|
Jump you fuckers! | The thing about smart motherfuckers is they sound like crazy motherfuckers to dumb motherfuckers. | My sig space for rent for 0.01 btc per week.
|
|
|
|
