Come on people, join http://burstpool.ddns.net
29 miners away from 100. The 100th will get 5000 BURST welcoming bonus!
29 miners away from 100. The 100th will get 5000 BURST welcoming bonus!
So who is the winner ? Or this is a scam for more miner ?
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 725. (Read 2171056 times)
September 25, 2014, 10:09:58 PM
So who is the winner ? Or this is a scam for more miner ?
September 25, 2014, 09:55:25 PM
WARNING THE OWNER OF THIS WALLET (or any public wallet) CAN VIEW YOUR PRIVATE KEYS IF YOU SUBMIT THEM THERE!
September 25, 2014, 09:25:26 PM
any news about ongoing development?
September 25, 2014, 09:24:30 PM
I made my burst thing on my vps public, so try going here
172.245.214.105:8125
172.245.214.105:8125
Inviting people to enter their burst passphrase on an unencrypted connection to your naked IP address is begging for all sorts of trouble. Someone catches it in flight, their burst gets stolen, you get the blame.
converting to https now
September 25, 2014, 09:11:30 PM
I made my burst thing on my vps public, so try going here
172.245.214.105:8125
172.245.214.105:8125
Inviting people to enter their burst passphrase on an unencrypted connection to your naked IP address is begging for all sorts of trouble. Someone catches it in flight, their burst gets stolen, you get the blame.
September 25, 2014, 08:57:17 PM
Native C++ Miner Update 1.1 R4
binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64
and also, github automatically give the project website : http://uraymeiviar.github.io/burst-miner/
binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64
- capable to read large stagger plot, with manual limit option on memory usage
- Fix thread race condition, which reported to less nonce read
- add option of buffer size (MB) in mining.conf to limit memory usage
and also, github automatically give the project website : http://uraymeiviar.github.io/burst-miner/
This miner reading speed is much slower than java miner.
I tried using java and C ++.
Java took less than a min to complete reading the plot whereas C ++ miner took 2.5 - 3 mins.
Everything else looks great for C ++ miner except the plot reading.
Anyone having the same problem ?
September 25, 2014, 08:51:25 PM
dev, this isn't working:
http://127.0.0.1:8125/burst?requestType=getRewardRecipient(BURST-xxxx-xxxx-xxxx-xxxxx) <--- with either acount in rs format or numeric
it returns
{"errorCode":1,"errorDescription":"Incorrect request"}
and sometimes
{
"errorCode": 3,
"errorDescription": "\"account\" not specified"
}
try this instead:http://127.0.0.1:8125/burst?requestType=getRewardRecipient(BURST-xxxx-xxxx-xxxx-xxxxx) <--- with either acount in rs format or numeric
it returns
{"errorCode":1,"errorDescription":"Incorrect request"}
and sometimes
{
"errorCode": 3,
"errorDescription": "\"account\" not specified"
}
http://127.0.0.1:8125/burst?requestType=getRewardRecipient&account={NumericalAccountID}
thx
September 25, 2014, 08:46:09 PM
dev, this isn't working:
http://127.0.0.1:8125/burst?requestType=getRewardRecipient(BURST-xxxx-xxxx-xxxx-xxxxx) <--- with either acount in rs format or numeric
it returns
{"errorCode":1,"errorDescription":"Incorrect request"}
and sometimes
{
"errorCode": 3,
"errorDescription": "\"account\" not specified"
}
try this instead:http://127.0.0.1:8125/burst?requestType=getRewardRecipient(BURST-xxxx-xxxx-xxxx-xxxxx) <--- with either acount in rs format or numeric
it returns
{"errorCode":1,"errorDescription":"Incorrect request"}
and sometimes
{
"errorCode": 3,
"errorDescription": "\"account\" not specified"
}
http://127.0.0.1:8125/burst?requestType=getRewardRecipient&account={NumericalAccountID}
September 25, 2014, 08:42:34 PM
Did a fresh download but still does nothing when I enter my (or any passphrase) ... 
September 25, 2014, 08:41:17 PM
Client v1.1.2 "could not generate Reed Solomon address"
Any ideas how to fix? Getting this for multiple addresses. Win7 32bit, chrome.
Any ideas how to fix? Getting this for multiple addresses. Win7 32bit, chrome.
Anyone???
had the same problem , contacted the dev and he kindly explained me taht this problem happens when , migrating from older walled , our browser cache disturbs the wallet. erase your browser cache and it should solve the issues like it did for me !
regards
Bingo, thank you!
September 25, 2014, 08:15:42 PM
dev, this isn't working:
http://127.0.0.1:8125/burst?requestType=getRewardRecipient(BURST-xxxx-xxxx-xxxx-xxxxx) <--- with either acount in rs format or numeric
it returns
{"errorCode":1,"errorDescription":"Incorrect request"}
and sometimes
{
"errorCode": 3,
"errorDescription": "\"account\" not specified"
}
http://127.0.0.1:8125/burst?requestType=getRewardRecipient(BURST-xxxx-xxxx-xxxx-xxxxx) <--- with either acount in rs format or numeric
it returns
{"errorCode":1,"errorDescription":"Incorrect request"}
and sometimes
{
"errorCode": 3,
"errorDescription": "\"account\" not specified"
}
September 25, 2014, 06:45:50 PM
Alright I have a issue. Last night when switching from ahci to ide mode one of my raid 0 array drives crashed. My burst account and all was on there but that's not really the problem. I installed the burst client again but when I enter my passphrase on the web UI (or any passphrase) nothing happens. Just reloads the page asking for passphrase.... The blockchain seems to have downloaded again and the wallet run opens fine just like always....
Try redownloading.
September 25, 2014, 06:42:15 PM
Alright I have a issue. Last night when switching from ahci to ide mode one of my raid 0 array drives crashed. My burst account and all was on there but that's not really the problem. I installed the burst client again but when I enter my passphrase on the web UI (or any passphrase) nothing happens. Just reloads the page asking for passphrase.... The blockchain seems to have downloaded again and the wallet run opens fine just like always....
September 25, 2014, 06:30:21 PM
Bittrex wants to see at least 0.1 BTC of volume and BURST had much more than this so I doubt its being delisted.. would be nice to hear something from them about it
September 25, 2014, 06:18:39 PM
Native C++ Miner Update 1.1 R4
binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64
binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64
- capable to read large stagger plot, with manual limit option on memory usage
- Fix thread race condition, which reported to less nonce read
- add option of buffer size (MB) in mining.conf to limit memory usage
Thanks
September 25, 2014, 06:12:22 PM
Bittrex don't delist coins without 1 week alert. 
Do the exchanges send email notification prior to delisting? I could easily see myself missing a 1w window, otherwise.
September 25, 2014, 06:09:23 PM
Well then you're a fool because BURST has had its big pop up in price, and it'll never get to even 500 satoshis again.
Yeah, man. BTC never went anywhere after it crashed from $32 to $1.
...price is showing some real strength on C-Cex.
A rise of 20s on basically no volume is not real strength. It's going to take a while.
September 25, 2014, 06:02:25 PM
Thanks for developing this miner. It is much quicker and leaner than the Java equivalent. However, I've found quite a few anomalies while using it. I've posted 4 bug reports to Github. Wonder what your opinion on those reports is...?
Native C++ Miner Update 1.1 R4
binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64
binaries and source available here : https://github.com/uraymeiviar/burst-miner/releases
for osx, linux64 and win64
- capable to read large stagger plot, with manual limit option on memory usage
- Fix thread race condition, which reported to less nonce read
- add option of buffer size (MB) in mining.conf to limit memory usage
September 25, 2014, 05:17:34 PM
Looks like a pump is going on poloniex
That's not a pump...
it's crazy when even this miniscule buy pressure influences the markets so much. If we had more miners we could make a bigger difference, but alas.
I fixed the problems that had the payout stuck (stupid bittrex requiring the withdraw message - at least the pool didn't lose any coins)
(Quoting an old post... as it is semi-relevant)
Looks like there hasn't been a payout in a few days now, again.
Is the pool running on manual payouts? or is there something else going on?
Jump to: