It seems the firewall mess up. Should be fix now, good thing we have multiple ports for redundancy. If this happens again try 8080, 8880 or 2052. Just added 2052.
@tate-a Would you consider updating your support for dymaxium on the following website?
This post is deleted!
I've been running the wallet for a while, 1.3.6CG. 1.2.9 has stopped working a while ago. I need to find a better pool code, ninja v2 runs just okay. Ninja v3 runs like shit, when I try to set it up.
@tate-a , Why does 1.2.9 not work. I have 8 of them running and one is driving a pool?
@Tate-A Glad to hear! I think they will be releasing the new pool code pretty soon. I think some may already have it.
@rds 1.2.9 is outdated my friend. Please upgrade. Especially if you are running a pool. You have been around a while so I would expect you know whats going on. If not read up on the burst advancements!
@crutsy , I do know what's goin on but I'm too lazy to upgrade. Everything is working fine.
@rds It won't be in the near future if you don't upgrade...
What pool are you running? Will you be supporting dymaxium? If so you need to upgrade.
@crutsy , i run a private pool. when it stops working i will have to upgrade. So far I thought the fork won't be for quite awhile.
@rds Got ya. You could start now and show some support tho
gpedro last edited by
@rds After 2.0.0 release being launched, the 1.2.9 wallets and everything older than that will not be able to connect to any 2.0.0 nodes, they will only be able to connect to the 1.3.6 nodes...
If 85% of the network runs the 2.0.0 after the release (the minimum needed to have signalling consensus for dymaxion) you will only be able to connect to 15% of the network meaning you will be forking a lot...
With this being said, if you operate a pool (even a private one), you should at least be with 1.3.6cg by now... If you don't, you will reach a point where you will catch some good downtime with your pool...
rds last edited by rds
@gpedro , where is the official "new wallet". I don't want all the wrapper stuff, just the wallet. I'll give it a try on one of my machines.
Can the new wallet be configured for different ports? I run 1.2.9 on 8105, 8110, 8115, 8120, 8125, and 8130.
@rds yep - I'm running the online ones on 2053 and 2083 - but anything CF supports would be fine for me
gpedro last edited by
@rds here: https://github.com/PoC-Consortium/burstcoin
I would recommend migrating to the Mariadb database since it's the most stable although has the configuration a bit harder so if you try and can't get it, my easiest suggestion is that you launch it for the first time with qBundle and the configuration will be very easy, from that point on use it without qbundle if you want the lighter and raw view
If your miners are on port 8124 please switch them to 8080, 8880 or 2052 asp. We are going to be upgrading the pool to a new pool code in about a day. We will see how it does. Can you please spread the word to any fellow miners that is mining the this pool. Thank you for your patience. I hope the new code performs better than this old Ninja v2 code. I will force the play out on Ninja v2 when we do the upgrad. The rest of the miners that have been mining on the correct ports ( 8080, 8880 or 2052 ) will not have to do anything. Please make sure you are not forcing a deadline you have specified in the miner, the deadline is going back to 6 months. Right now we have the deadline set to 3 months because Ninja v2 can not handle it. And when we have upgraded when you are viewing the pools interface from your web browser you do not have to specified any ports. Do not try to mine on port 80. Will also have to build a new server that support AVX2, one vary nice feacher of this code is it support multiple wallets for redundancy. For a temporary time I'm going to hosting this on a PC with 6 cores, may move back to Ninja if that is not possible. In till we get a server in a datacenter. If its okay with you guys if I use the funds saved for pool over pay, to cover the cost of the new server. Then set fee to 0.5% until funds are recovered.
CPU: i7-7820X ( 8 Cores @ 3.60GHz, turbo 4.30GHz )
RAM: ADATA AX4U2400316G16-DBG ( 32GB 2 x 16GB 2666MHz )
Storage: 2x WD Black M.2 ( NVMe 512GB, Read 2050MB/s, Write 800MB/s RAID 1 )
Motherboard: MSI X299M GAMING PRO CARBON
PSU: CORSAIR SF Series SF600
Cooler: CORSAIR Hydro Series H105 Extreme
GPU: GIGABYTE GTX 1050 Ti GV-N105TWF2OC-4GD ( For wallet acceleration, on hand )
Cases: Thanks to DirtyD for donating a case
Miners that are mining on port 8124:
Sorry for downtime to day, we had the firewall lock up. It seems that somebody has attacked us, they were making thousands of page request per second. Why ever cloud flare did not stop it.
Payout should be fixed now.
Hi guys how, it been going?
Tate A last edited by Tate A
Love that progress bar.
Somebody was hitting the pool the other day, seems to be fixed now. Happy bursting!
- Type: GoPool/PoCC
- Mining URL: Pool.BurstCoin.ml
- Mining Ports: 8080, 8880 or 2052
- Set recipient:
BURST-85W6-5P5V-7VLZ-GZJEF or 16623383385195351940
- Fee: 00.00%
- Deadline Limit: 12 Months
- Payout: 250 Burst or set your payout, 50/50%
- DDoS Protection: CloudFlare + UTM
- Asset ID: 14111531369712118954 ( Ran by the BurstCoin.ml's Miner )
You can now set your payout! Send unencrypted Arbitrary Message from your mining wallet to BURST-85W6-5P5V-7VLZ-GZJEF to change your payment thresholds/intervals, will use one Burst for network fee.
now = Will send payment every time a block is found if you have a positive balance, but will use one Burst for network fee. Not recommended because of network fee.
daily = Forces a daily payout if you have a positive balance at the time, when the payment is made.
weekly = Forces a weekly payout if you have a positive balance at the time, when the payment is made.
0 = Reset to pool's defaults (the number zero)
If you need any help let me know. I'll try to help ASP!!
The asset is ran by a GPU rig miner, paid monthly.
Asset Name: v2Pool
Asset ID: 14111531369712118954