@crowetic
Ouch, sounds bad. Hope that you get the problem solved and your server back up and running again.
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 596. (Read 2171062 times)
November 04, 2014, 10:33:10 AM
November 04, 2014, 09:57:20 AM
server going for a quick restart. The replacement server is in the works I am speaking with a few people about it now.
edit: quick restart turned into something much worse.
Everyone should just mine somewhere else for the time being. I am fuckin pissed, I wish I would have had notice before our main server was taken down, I'm fuckin pissed.
Anyway, yea. I don't fuckin know how long it will take to fix.
edit 2: Going to try to get a VM up real quick to at least get something running right now...
edit 3: Got something up for now, it's synching the blockchain at the moment...
edit: quick restart turned into something much worse.
Everyone should just mine somewhere else for the time being. I am fuckin pissed, I wish I would have had notice before our main server was taken down, I'm fuckin pissed.
Anyway, yea. I don't fuckin know how long it will take to fix.
edit 2: Going to try to get a VM up real quick to at least get something running right now...
edit 3: Got something up for now, it's synching the blockchain at the moment...
November 04, 2014, 09:53:41 AM
Is there a minning proffit calculator anywhere?
But you can't count on them. Depends how many blocks your pool finds.
November 04, 2014, 09:31:23 AM
Is there a minning proffit calculator anywhere?
http://burstcoin.eu/calculator November 04, 2014, 09:29:13 AM
Is there a minning proffit calculator anywhere?
November 04, 2014, 09:27:58 AM
pool.burstcoin.io - not responding to miners. Updating daemon?
Edit: 8124 down, 80 works.
Edit: 8124 down, 80 works.
November 04, 2014, 08:34:00 AM
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?
Problem here is that we are not living in the same country nor the same continent.
November 04, 2014, 07:39:03 AM
Burst 1.1.5
Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8
sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7
Or github: https://github.com/BurstProject/burstcoin
Update 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.
Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8
sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7
Or github: https://github.com/BurstProject/burstcoin
Update 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?
November 04, 2014, 07:18:27 AM
Hi guys, I'm KeyShare from Italy!
I love BurstCoin and I think that it is the future of the cryptocurrencies. I've just bought 260k of it and right now I'm starting mining it for several days to gain other ones.
I think that we shold promote it so much better on the social networks..his FaceBook page has just 85 Likes..too few for his real importance!
On CoinGecko ranking, Burst has gone up for 9 positions, from 48st to 39st! We should go up and up again, so that everyone knows what is BurstCoin.
Dev work is massive and truly amazing, and if it keep going like this, I know that Burst price will fly high in the sky like never before..
So c'mon guys, let's promote BURST everywhere!
I love BurstCoin and I think that it is the future of the cryptocurrencies. I've just bought 260k of it and right now I'm starting mining it for several days to gain other ones.
I think that we shold promote it so much better on the social networks..his FaceBook page has just 85 Likes..too few for his real importance!
On CoinGecko ranking, Burst has gone up for 9 positions, from 48st to 39st! We should go up and up again, so that everyone knows what is BurstCoin.
Dev work is massive and truly amazing, and if it keep going like this, I know that Burst price will fly high in the sky like never before..
So c'mon guys, let's promote BURST everywhere!
November 04, 2014, 07:12:04 AM
Dunno what happened to you guys but the upgrade went flawlessly for me.
November 04, 2014, 05:37:17 AM
just tried to update (checkout from git), but I get an error after running compile.sh:
every other update worked fine...
edit: ok, looks like the conf has changed. I usually just copy my old conf over :/
Code:
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.(Db.java:81)
at nxt.Nxt$Init.(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.(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.(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 :/
November 04, 2014, 05:19:19 AM
got it..
localhost:8125 did not work anymore, but 127.0.0.1:8125 is working..
localhost:8125 did not work anymore, but 127.0.0.1:8125 is working..
November 04, 2014, 04:39:28 AM
November 04, 2014, 04: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..
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..
Code:
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"
November 04, 2014, 03:33:04 AM
Burst 1.1.5
Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8
sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7
Or github: https://github.com/BurstProject/burstcoin
Update 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.Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8
sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7
Or github: https://github.com/BurstProject/burstcoin
Update 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.
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.
November 04, 2014, 03:02:45 AM
First 10tb at a discount!!!
https://burstforum.com/index.php?threads/ann-hardcloud-cloud-mining-1-year-35.303/
https://burstforum.com/index.php?threads/ann-hardcloud-cloud-mining-1-year-35.303/
November 04, 2014, 02: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.
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.
November 04, 2014, 02:37:39 AM
Burst 1.1.5
Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8
sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7
Or github: https://github.com/BurstProject/burstcoin
Update 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.
Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8
sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7
Or github: https://github.com/BurstProject/burstcoin
Update 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?
November 04, 2014, 02:29:41 AM
Burst 1.1.5
Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8
sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7
Or github: https://github.com/BurstProject/burstcoin
Update 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.
Download: https://mega.co.nz/#!r9RywR4b!e0MqN4kXx1uiW5th8PBxiwjOfdNhjxjS52UqXwihGW8
sha256: 5b8a5e9d2ebcc35052a885b299764ed257346f3c849e92768bd5b725ad685ac7
Or github: https://github.com/BurstProject/burstcoin
Update 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?
November 04, 2014, 01:47:46 AM
Ok, I just invested 0.06. I hope to cash out at 0.6. 
Jump to: