Does anybody work on a mobile wallet app?
Why don't u give it a shot? Get one of your devs to go for it.
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 382. (Read 2170648 times)
February 28, 2015, 01:20:39 AM
Why don't u give it a shot? Get one of your devs to go for it.
February 28, 2015, 12:10:56 AM
Does anybody work on a mobile wallet app?
February 27, 2015, 11:08:08 PM
At the moment I cannot reach mining.tompool.org:82
Is it just me or is the site not reachable.
The last Current Block was shown with 71547
while mininghere.com:8001 shows 71734
BTW, how can I figure out what time Block 71547 was handled (just to know how long the site was not reachable)?
Is it just me or is the site not reachable.
The last Current Block was shown with 71547
while mininghere.com:8001 shows 71734
BTW, how can I figure out what time Block 71547 was handled (just to know how long the site was not reachable)?
February 27, 2015, 07:12:09 PM
Is anybody interested in a Daily Joke subscription?
February 27, 2015, 06:53:33 PM
Our subscription project Zodiac passed the last days' tests!
Daily Horoscope as subscription:
Aquarius BURST-7L8Y-72ZX-LFXS-EM5G5
Aries BURST-QSWP-KVXE-CH4H-4Y72D
Cancer BURST-42ZD-YBNF-B82N-4LFFE
Capricorn BURST-RBDA-7VVS-ACP8-772KB
Gemini BURST-82ZJ-BQA9-7F7Z-EXQG7
Leo BURST-AFCL-8H35-HXCQ-986JZ
Libra BURST-QNWB-YCCS-7CU7-CF4P7
Pisces BURST-R9PF-W7G7-CAX7-AZGKR
Sagittarius BURST-RQ54-ZVTT-XFED-456PR
Scorpio BURST-7EEH-9ZCD-CHF8-FQBPU
Taurus BURST-TWSX-SYWB-RPQD-CENSW
Virgo BURST-KW5D-EAQ2-VC6U-8P5XZ
Subscription cost 10 Bursts and it should be setup for daily (24x3600 seconds =) 86,400 seconds
How to subscribe:
1. open your wallet
2. click on the tab Transaction and sub tab Subscriptions (at the left hand menu)
3. click on the button Create Subscription (at the right upper corner)
4. enter the BURST address from above for your Zodiac sign
5. use as amount 10 BURST
6. click on the button Create Subscription
The IFs:
If you use an amount lower than 10 BURSTs, the daily amounts will be counted as donation.
THANK YOU!
If you use as amount 10 BURSTs, the system will send you daily at this time of the day a message with your subscribed Zodiac message.
If you use an amount more than 10 BURSTs, the system will count the amount above 10 BURSTs as donation.
THANK YOU!
If you use another seconds amount then 86,400 seconds, then the subscription will be shorter or longer. You may receive multiple times the same message, or missing some day's message.
You can cancel any time!
How it works.
Whenever the system finds an incoming amount of 10 or more BURSTs then it will send the message of the day out to the subscriber.
Remember, mining reward is getting less every month by 5%. Transaction fee is therefore important to keep the miners going. Participate in this/any BURST project.
Daily Horoscope as subscription:
Aquarius BURST-7L8Y-72ZX-LFXS-EM5G5
Aries BURST-QSWP-KVXE-CH4H-4Y72D
Cancer BURST-42ZD-YBNF-B82N-4LFFE
Capricorn BURST-RBDA-7VVS-ACP8-772KB
Gemini BURST-82ZJ-BQA9-7F7Z-EXQG7
Leo BURST-AFCL-8H35-HXCQ-986JZ
Libra BURST-QNWB-YCCS-7CU7-CF4P7
Pisces BURST-R9PF-W7G7-CAX7-AZGKR
Sagittarius BURST-RQ54-ZVTT-XFED-456PR
Scorpio BURST-7EEH-9ZCD-CHF8-FQBPU
Taurus BURST-TWSX-SYWB-RPQD-CENSW
Virgo BURST-KW5D-EAQ2-VC6U-8P5XZ
Subscription cost 10 Bursts and it should be setup for daily (24x3600 seconds =) 86,400 seconds
How to subscribe:
1. open your wallet
2. click on the tab Transaction and sub tab Subscriptions (at the left hand menu)
3. click on the button Create Subscription (at the right upper corner)
4. enter the BURST address from above for your Zodiac sign
5. use as amount 10 BURST
6. click on the button Create Subscription
The IFs:
If you use an amount lower than 10 BURSTs, the daily amounts will be counted as donation.
THANK YOU!
If you use as amount 10 BURSTs, the system will send you daily at this time of the day a message with your subscribed Zodiac message.
If you use an amount more than 10 BURSTs, the system will count the amount above 10 BURSTs as donation.
THANK YOU!
If you use another seconds amount then 86,400 seconds, then the subscription will be shorter or longer. You may receive multiple times the same message, or missing some day's message.
You can cancel any time!
How it works.
Whenever the system finds an incoming amount of 10 or more BURSTs then it will send the message of the day out to the subscriber.
Remember, mining reward is getting less every month by 5%. Transaction fee is therefore important to keep the miners going. Participate in this/any BURST project.
February 27, 2015, 06:43:46 PM
Maybe plots could at least store the Blockchain in a future version ?
You have no idea how much I want that....The ultimate trim!!!
Everybody, watch out for this asset: Petabyte
Sell order from issuer @179k Burst....which equates to $81USD/TB...If anyone thinks that they'll ROI at that price....well, ur not. Don't know how Elmit is selling this...obviously the buyers are idiots and don't research anything.
Asset Issuer offers for 180,000 and 180,100 (That is the line where it says "Asset Issuer") that was a fair price at the time:
170 US$ a 4 TB hard disk at 0.00000080 to 0.00000100 Burst/BTC and 250 US$/BTC
It pays also dividends! Didn't you notice your payout of about 17,000 Bursts. Not bad for your proposed price of 18,000 Bursts per 1 TB hard disk space.
We CALCULATE the asset price. And with all assets (or stock) the market dictates the trading price.
Therefore:
Do you have BURSTs in your wallet? How much interests do you get? If none, then buy assets:
Open your wallet, click on Asset Exchange
Add Asset with the ID: 14668748687827404894
Buy assets, as you can afford it.
Relax and get paid as we mine for you.
... but sure you can just watch your wallet.
February 27, 2015, 06:35:24 PM
Hehe, I also have a good connection:
And mr. GenTarkin, password section is for your Burst wallet passphrase. It is 100% required!
K, I put my passphrase there, same error.And mr. GenTarkin, password section is for your Burst wallet passphrase. It is 100% required!
Nevermind, apparently names cant have anything but letters and numbers lol... not even _ is alloewd
February 27, 2015, 06:25:20 PM
*sign* just changed back to give it another try, and the response time of the server is very bad, including timeouts etc...
I really like the frontend, but can you maybe get someone who is able to setup a stable unix server? there are under 50 miners on the server and it looks like the backend is already burning.
I begin to hate that 4 confirmation thing when switching pools...
Cat is a most capable Linux/Unix dev. Dunno about speed...this thing barely touches server resources...50 miners? Try 250!! Are you sure that you're on BURST.NINJA?
Obviously he is on the new "FRONTEND", it is the only pool which looks like the old tv test page, ... hehehehe
I also think that a *nix server is much better suitable than Windows.
Our pool keeps all on Linux, even my desktop is Linux.
February 27, 2015, 06:20:50 PM
Maybe plots could at least store the Blockchain in a future version ?
You have no idea how much I want that....The ultimate trim!!!
Everybody, watch out for this asset: Petabyte
Sell order from issuer @179k Burst....which equates to $81USD/TB...If anyone thinks that they'll ROI at that price....well, ur not. Don't know how Elmit is selling this...obviously the buyers are idiots and don't research anything.
Interesting!
Petabyte keeps it's value. YOU got even some! So you must be very happy! If you think it is not worth it, then sell it!!! or transfer it with your proposed 18,000
February 27, 2015, 05:45:10 PM
Hehe, I also have a good connection:
And mr. GenTarkin, password section is for your Burst wallet passphrase. It is 100% required!
K, I put my passphrase there, same error. And mr. GenTarkin, password section is for your Burst wallet passphrase. It is 100% required!
February 27, 2015, 05:42:09 PM
Im trying to create a crowdsource through the AT interface. It just says 'error sending transaction' ... what could be wrong?
Also what is the password field used for? (error happens whether I put one or not)
Also what is the password field used for? (error happens whether I put one or not)
To create a CF you need to have a burst account and have at least some bursts to cover the ATs creation fees (less than 10 bursts). Also name is not allowed to have spaces.
I meet all those requirements =)
February 27, 2015, 05:25:02 PM
Hehe, I also have a good connection:
And mr. GenTarkin, password section is for your Burst wallet passphrase. It is 100% required!
And mr. GenTarkin, password section is for your Burst wallet passphrase. It is 100% required!
February 27, 2015, 04:57:50 PM
Say I wanted to give mining Burst a try, would I need to use an internal HDD, or would an external USB-harddrive of 1 or 2 TB also do?
USB2.0 is a bit slow for Burst Mining , use USB3.0 or SATA connection! And if the external HDD is USB 2.0... you can always dissemble the external case and use it as internal! 
I have an external USB 3 HDD of 1 TB, so might look into it this weekend. Internal HDD only got around 100 GB of free space, so I guess that's not worth trying
. February 27, 2015, 04:51:36 PM
Say I wanted to give mining Burst a try, would I need to use an internal HDD, or would an external USB-harddrive of 1 or 2 TB also do?
USB2.0 is a bit slow for Burst Mining , use USB3.0 or SATA connection! And if the external HDD is USB 2.0... you can always dissemble the external case and use it as internal! EDIT: DaWallet i PM'd you a few days ago, can you response me?
February 27, 2015, 04:00:28 PM
No drops for me either:
Code:
Reply from 192.198.95.54: bytes=32 time=63ms TTL=46
Reply from 192.198.95.54: bytes=32 time=56ms TTL=46
Reply from 192.198.95.54: bytes=32 time=62ms TTL=46
Reply from 192.198.95.54: bytes=32 time=53ms TTL=46
Reply from 192.198.95.54: bytes=32 time=58ms TTL=46
Ping statistics for 192.198.95.54:
Packets: Sent = 769, Received = 769, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 153ms, Average = 57ms
Reply from 192.198.95.54: bytes=32 time=56ms TTL=46
Reply from 192.198.95.54: bytes=32 time=62ms TTL=46
Reply from 192.198.95.54: bytes=32 time=53ms TTL=46
Reply from 192.198.95.54: bytes=32 time=58ms TTL=46
Ping statistics for 192.198.95.54:
Packets: Sent = 769, Received = 769, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 153ms, Average = 57ms
February 27, 2015, 03:54:33 PM
*sign* just changed back to give it another try, and the response time of the server is very bad, including timeouts etc...
I really like the frontend, but can you maybe get someone who is able to setup a stable unix server? there are under 50 miners on the server and it looks like the backend is already burning.
I begin to hate that 4 confirmation thing when switching pools...
Cat is a most capable Linux/Unix dev. Dunno about speed...this thing barely touches server resources...50 miners? Try 250!! Are you sure that you're on BURST.NINJA?
yes, I'm @ burst.ninja (192.198.95.54) and there are timeouts all over the place. With the 50 miners, I was refering to:
Code:
Miners Responded 34
Edit:
Code:
PING burst.ninja (192.198.95.54) 56(84) bytes of data.
64 bytes from 192.198.95.54: icmp_seq=4 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=7 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=9 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=14 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=16 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=23 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=25 ttl=51 time=150 ms
--- burst.ninja ping statistics ---
26 packets transmitted, 7 received, 73% packet loss, time 25123ms
64 bytes from 192.198.95.54: icmp_seq=4 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=7 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=9 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=14 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=16 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=23 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=25 ttl=51 time=150 ms
--- burst.ninja ping statistics ---
26 packets transmitted, 7 received, 73% packet loss, time 25123ms
Code:
PING burst.poolto.be (5.9.23.116) 56(84) bytes of data.
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=1 ttl=56 time=37.3 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=2 ttl=56 time=40.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=3 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=4 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=5 ttl=56 time=37.9 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=6 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=7 ttl=56 time=38.4 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=8 ttl=56 time=38.8 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=9 ttl=56 time=39.5 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=10 ttl=56 time=39.8 ms
--- burst.poolto.be ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=1 ttl=56 time=37.3 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=2 ttl=56 time=40.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=3 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=4 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=5 ttl=56 time=37.9 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=6 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=7 ttl=56 time=38.4 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=8 ttl=56 time=38.8 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=9 ttl=56 time=39.5 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=10 ttl=56 time=39.8 ms
--- burst.poolto.be ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
if i'm the only one with problems it might be the connection from my location to your server :/
Code:
u0_a100@mako:/ $ ping 192.198.95.54
PING 192.198.95.54 (192.198.95.54) 56(84) bytes of data.
64 bytes from 192.198.95.54: icmp_seq=1 ttl=46 time=138 ms
64 bytes from 192.198.95.54: icmp_seq=2 ttl=46 time=141 ms
64 bytes from 192.198.95.54: icmp_seq=3 ttl=46 time=141 ms
64 bytes from 192.198.95.54: icmp_seq=4 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=5 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=6 ttl=46 time=143 ms
64 bytes from 192.198.95.54: icmp_seq=7 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=8 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=9 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=10 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=11 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=12 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=13 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=14 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=15 ttl=46 time=139 ms
64 bytes from 192.198.95.54: icmp_seq=16 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=17 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=18 ttl=46 time=144 ms
64 bytes from 192.198.95.54: icmp_seq=19 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=20 ttl=46 time=143 ms
64 bytes from 192.198.95.54: icmp_seq=21 ttl=46 time=144 ms
64 bytes from 192.198.95.54: icmp_seq=22 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=23 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=24 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=25 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=26 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=27 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=28 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=29 ttl=46 time=143 ms
^C
--- 192.198.95.54 ping statistics ---
29 packets transmitted, 29 received, 0% packet loss, time 28066ms
rtt min/avg/max/mdev = 138.764/143.860/146.728/2.109 ms
PING 192.198.95.54 (192.198.95.54) 56(84) bytes of data.
64 bytes from 192.198.95.54: icmp_seq=1 ttl=46 time=138 ms
64 bytes from 192.198.95.54: icmp_seq=2 ttl=46 time=141 ms
64 bytes from 192.198.95.54: icmp_seq=3 ttl=46 time=141 ms
64 bytes from 192.198.95.54: icmp_seq=4 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=5 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=6 ttl=46 time=143 ms
64 bytes from 192.198.95.54: icmp_seq=7 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=8 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=9 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=10 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=11 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=12 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=13 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=14 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=15 ttl=46 time=139 ms
64 bytes from 192.198.95.54: icmp_seq=16 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=17 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=18 ttl=46 time=144 ms
64 bytes from 192.198.95.54: icmp_seq=19 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=20 ttl=46 time=143 ms
64 bytes from 192.198.95.54: icmp_seq=21 ttl=46 time=144 ms
64 bytes from 192.198.95.54: icmp_seq=22 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=23 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=24 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=25 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=26 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=27 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=28 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=29 ttl=46 time=143 ms
^C
--- 192.198.95.54 ping statistics ---
29 packets transmitted, 29 received, 0% packet loss, time 28066ms
rtt min/avg/max/mdev = 138.764/143.860/146.728/2.109 ms
No timeout for me on 3 try.
February 27, 2015, 03:25:17 PM
Im trying to create a crowdsource through the AT interface. It just says 'error sending transaction' ... what could be wrong?
Also what is the password field used for? (error happens whether I put one or not)
Also what is the password field used for? (error happens whether I put one or not)
To create a CF you need to have a burst account and have at least some bursts to cover the ATs creation fees (less than 10 bursts). Also name is not allowed to have spaces.
February 27, 2015, 03:21:07 PM
Im trying to create a crowdsource through the AT interface. It just says 'error sending transaction' ... what could be wrong?
Also what is the password field used for? (error happens whether I put one or not)
Also what is the password field used for? (error happens whether I put one or not)
February 27, 2015, 03:16:39 PM
*sign* just changed back to give it another try, and the response time of the server is very bad, including timeouts etc...
I really like the frontend, but can you maybe get someone who is able to setup a stable unix server? there are under 50 miners on the server and it looks like the backend is already burning.
I begin to hate that 4 confirmation thing when switching pools...
Cat is a most capable Linux/Unix dev. Dunno about speed...this thing barely touches server resources...50 miners? Try 250!! Are you sure that you're on BURST.NINJA?
yes, I'm @ burst.ninja (192.198.95.54) and there are timeouts all over the place. With the 50 miners, I was refering to:
Code:
Miners Responded 34
Edit:
Code:
PING burst.ninja (192.198.95.54) 56(84) bytes of data.
64 bytes from 192.198.95.54: icmp_seq=4 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=7 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=9 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=14 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=16 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=23 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=25 ttl=51 time=150 ms
--- burst.ninja ping statistics ---
26 packets transmitted, 7 received, 73% packet loss, time 25123ms
64 bytes from 192.198.95.54: icmp_seq=4 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=7 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=9 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=14 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=16 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=23 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=25 ttl=51 time=150 ms
--- burst.ninja ping statistics ---
26 packets transmitted, 7 received, 73% packet loss, time 25123ms
Code:
PING burst.poolto.be (5.9.23.116) 56(84) bytes of data.
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=1 ttl=56 time=37.3 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=2 ttl=56 time=40.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=3 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=4 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=5 ttl=56 time=37.9 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=6 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=7 ttl=56 time=38.4 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=8 ttl=56 time=38.8 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=9 ttl=56 time=39.5 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=10 ttl=56 time=39.8 ms
--- burst.poolto.be ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=1 ttl=56 time=37.3 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=2 ttl=56 time=40.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=3 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=4 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=5 ttl=56 time=37.9 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=6 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=7 ttl=56 time=38.4 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=8 ttl=56 time=38.8 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=9 ttl=56 time=39.5 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=10 ttl=56 time=39.8 ms
--- burst.poolto.be ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
if i'm the only one with problems it might be the connection from my location to your server :/
February 27, 2015, 03:12:08 PM
*sign* just changed back to give it another try, and the response time of the server is very bad, including timeouts etc...
I really like the frontend, but can you maybe get someone who is able to setup a stable unix server? there are under 50 miners on the server and it looks like the backend is already burning.
I begin to hate that 4 confirmation thing when switching pools...
Cat is a most capable Linux/Unix dev. Dunno about speed...this thing barely touches server resources...50 miners? Try 250!! Are you sure that you're on BURST.NINJA?
Jump to: