Thank you, vbcs for doing such a great job in creating a ATcrowdfunding.
[---]
[---]
Couldn't say it better
How about putting some more into to the crowdfunding case so it gets it filled...? 
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 414. (Read 2171065 times)
February 12, 2015, 05:35:26 PM
Couldn't say it better
How about putting some more into to the crowdfunding case so it gets it filled...? February 12, 2015, 05:32:48 PM
Yeah burst.ga seems to be down :/
February 12, 2015, 03:37:20 PM
About burst.ga mining pool
There were a few teething issues, some brought to light once the larger load of miners connected.
Fixes have been put live as of this morning (my time) so you should see much quicker stats page startup.
Payments are flowing out okay.
Payment calculation has changed from the previous uray pool code. It is now:
So even tiny miners can win up to 3,500 Burst if they happen to strike lucky with their nonce and win the current block.
Big miners consistently win Burst by way of the historic shares.
The pool doesn't start generating payouts until about 5 blocks after a win just to make sure the pool REALLY won the block. (Sometimes network propagation delays allow another remote miner to actually get the block first).
Payouts are then shoved into a queue.
About another 5 blocks later payouts are tested to see if they have been confirmed or lost, in which case they are queued again. (Payouts can get lost if sent during a block changeover, for example).
Stats webpage is available at both http://burst.ga/ and http://burst.ga:8124/
Miners can use http://burst.ga:8124/
Blago miners need to have useFastRcv set to false. Symptoms of you needing to do this look like:
Pool only accepts deadlines less than 30 days. For Blago's miner you could add a line to your config like this: (not at the end - note trailing comma!)
If you submit a bad deadline then you're likely to get a 400 Bad Request response but there will be an error message to go with that.
400 Bad Request responses are also sent out for other reasons - check your logs!
There were a few teething issues, some brought to light once the larger load of miners connected.
Fixes have been put live as of this morning (my time) so you should see much quicker stats page startup.
Payments are flowing out okay.
Payment calculation has changed from the previous uray pool code. It is now:
- 50% of block reward is paid out as per "current shares" for that block
- 50% of block reward is paid out as per "historic shares" for that block
So even tiny miners can win up to 3,500 Burst if they happen to strike lucky with their nonce and win the current block.
Big miners consistently win Burst by way of the historic shares.
The pool doesn't start generating payouts until about 5 blocks after a win just to make sure the pool REALLY won the block. (Sometimes network propagation delays allow another remote miner to actually get the block first).
Payouts are then shoved into a queue.
About another 5 blocks later payouts are tested to see if they have been confirmed or lost, in which case they are queued again. (Payouts can get lost if sent during a block changeover, for example).
Stats webpage is available at both http://burst.ga/ and http://burst.ga:8124/
Miners can use http://burst.ga:8124/
Blago miners need to have useFastRcv set to false. Symptoms of you needing to do this look like:
Code:
04:33:39 *Count packets of response: 1
04:33:39 *! error parsing (1) message from server
Pool only accepts deadlines less than 30 days. For Blago's miner you could add a line to your config like this: (not at the end - note trailing comma!)
Code:
"TargetDeadline": 2592000,
If you submit a bad deadline then you're likely to get a 400 Bad Request response but there will be an error message to go with that.
400 Bad Request responses are also sent out for other reasons - check your logs!
Thank you cat.
Also, to add to this... Of the 2% fee, I'm donating quite a bit by way of the ByteEnt asset (announcement most likely later today with details on asset, etc.) to the amazing BURST development team. I will also be donating quite a bit to the BURST core PR team. ByteEnterprises is dedicated to BURST's success, and will do anything we can to see it come to fruition.
(edit: I was just informed that the fees currently don't even cover transaction fees fully in the new code, I am going to be having it worked so that it will be 2% AFTER transaction fees, so that I'll be able to donate more to development. ByteEnt asset will be based on a lot more than just pool fees, so there will be more donation anyway, but I would like the pools to contribute as well.)
If anyone has any suggestions on changes to the pool, etc. Just let me know!
Also, if there is anyone who is good with front end designing, and would like to try their hand at making the pool look prettier, please message me with a copy to catbref and we can discuss what is required and what you would be given for the assistance.
Thank you and happy mining! Hope you enjoy the newest coded pools on the BURST market!
Oh, one last thing... Our pools are able to accept ANY miner, there is no need to figure out whether you need this or this miner, ANY miner software will work on the pool. If you run into any problems, let us know and we'll make it work, we're dedicated to making the pools work with ALL burst mining programs!
Is the site down and being fixed as showing no response on website and can not access.
February 12, 2015, 03:34:50 PM
lol what the heck only just turned 1 system on and starting rest up and poof lol
Where is that 192.168.0.2 in your screenshot coming from? Thats a local address - nothing to do with the pool. There's something very misconfigured on your miner.
H.
I have a local machine connected too as I have multipul rigs running. One is with pools details on and then my other machine connects to 1st machine to combine total network across 1 account
February 12, 2015, 03:04:17 PM
If I'm pool mining do I also need to have the wallet client running whilst mining?
or is it okay to close it, after the payment reward recipient has been set?
Thank you
or is it okay to close it, after the payment reward recipient has been set?
Thank you
remeber!
this is NXT style coin!
so you do not have the classic wallet.dat file who is your digital wallet!!!
but your coin are stored on the blockchain... on the cloud...
you can see who wallet it is just a web page.
You login with your passphrase... and the node give you your balance!
February 12, 2015, 02:11:21 PM
Wallet is only required when you want to receive coins or do solo mining.
You can receive without your wallet being running. Your coins are always on the block-chain. You can check your address on a block explorer and confirm that you have received them. Your pass phrase is all that is required to send coins, this can be done from a locally synced database ("wallet") or from an online database ("wallet"). Of course, local is more secure, since you are not pasting your pass-phrase into a website that may or may-not be mischievous.
February 12, 2015, 01:10:23 PM
Wallet is only required when you want to receive coins or do solo mining.
February 12, 2015, 01:04:28 PM
If I'm pool mining do I also need to have the wallet client running whilst mining?
or is it okay to close it, after the payment reward recipient has been set?
Thank you
or is it okay to close it, after the payment reward recipient has been set?
Thank you
You don't need the wallet while pool mining.
February 12, 2015, 12:30:41 PM
If I'm pool mining do I also need to have the wallet client running whilst mining?
or is it okay to close it, after the payment reward recipient has been set?
Thank you
or is it okay to close it, after the payment reward recipient has been set?
Thank you
February 12, 2015, 11:42:26 AM
Does anyone know how to make Blagos miner 'error out' faster on fast blocks? When a fastblock happens and if the previous mine hasn't completed, the miner will just sit there anywhere from 0-30 seconds playing with itself before it realizes it should move on. I've been watching this happen like clockwork over the past week or so, precious mine time is lost on the new block. If there are two fast blocks in a row, it may be even skip the middle one completely.
February 12, 2015, 10:16:19 AM
About burst.ga mining pool
There were a few teething issues, some brought to light once the larger load of miners connected.
Fixes have been put live as of this morning (my time) so you should see much quicker stats page startup.
Payments are flowing out okay.
Payment calculation has changed from the previous uray pool code. It is now:
So even tiny miners can win up to 3,500 Burst if they happen to strike lucky with their nonce and win the current block.
Big miners consistently win Burst by way of the historic shares.
The pool doesn't start generating payouts until about 5 blocks after a win just to make sure the pool REALLY won the block. (Sometimes network propagation delays allow another remote miner to actually get the block first).
Payouts are then shoved into a queue.
About another 5 blocks later payouts are tested to see if they have been confirmed or lost, in which case they are queued again. (Payouts can get lost if sent during a block changeover, for example).
Stats webpage is available at both http://burst.ga/ and http://burst.ga:8124/
Miners can use http://burst.ga:8124/
Blago miners need to have useFastRcv set to false. Symptoms of you needing to do this look like:
Pool only accepts deadlines less than 30 days. For Blago's miner you could add a line to your config like this: (not at the end - note trailing comma!)
If you submit a bad deadline then you're likely to get a 400 Bad Request response but there will be an error message to go with that.
400 Bad Request responses are also sent out for other reasons - check your logs!
There were a few teething issues, some brought to light once the larger load of miners connected.
Fixes have been put live as of this morning (my time) so you should see much quicker stats page startup.
Payments are flowing out okay.
Payment calculation has changed from the previous uray pool code. It is now:
- 50% of block reward is paid out as per "current shares" for that block
- 50% of block reward is paid out as per "historic shares" for that block
So even tiny miners can win up to 3,500 Burst if they happen to strike lucky with their nonce and win the current block.
Big miners consistently win Burst by way of the historic shares.
The pool doesn't start generating payouts until about 5 blocks after a win just to make sure the pool REALLY won the block. (Sometimes network propagation delays allow another remote miner to actually get the block first).
Payouts are then shoved into a queue.
About another 5 blocks later payouts are tested to see if they have been confirmed or lost, in which case they are queued again. (Payouts can get lost if sent during a block changeover, for example).
Stats webpage is available at both http://burst.ga/ and http://burst.ga:8124/
Miners can use http://burst.ga:8124/
Blago miners need to have useFastRcv set to false. Symptoms of you needing to do this look like:
Code:
04:33:39 *Count packets of response: 1
04:33:39 *! error parsing (1) message from server
04:33:39 *! error parsing (1) message from server
Pool only accepts deadlines less than 30 days. For Blago's miner you could add a line to your config like this: (not at the end - note trailing comma!)
Code:
"TargetDeadline": 2592000,
If you submit a bad deadline then you're likely to get a 400 Bad Request response but there will be an error message to go with that.
400 Bad Request responses are also sent out for other reasons - check your logs!
Thank you cat.
Also, to add to this... Of the 2% fee, I'm donating quite a bit by way of the ByteEnt asset (announcement most likely later today with details on asset, etc.) to the amazing BURST development team. I will also be donating quite a bit to the BURST core PR team. ByteEnterprises is dedicated to BURST's success, and will do anything we can to see it come to fruition.
(edit: I was just informed that the fees currently don't even cover transaction fees fully in the new code, I am going to be having it worked so that it will be 2% AFTER transaction fees, so that I'll be able to donate more to development. ByteEnt asset will be based on a lot more than just pool fees, so there will be more donation anyway, but I would like the pools to contribute as well.)
If anyone has any suggestions on changes to the pool, etc. Just let me know!
Also, if there is anyone who is good with front end designing, and would like to try their hand at making the pool look prettier, please message me with a copy to catbref and we can discuss what is required and what you would be given for the assistance.
Thank you and happy mining! Hope you enjoy the newest coded pools on the BURST market!
Oh, one last thing... Our pools are able to accept ANY miner, there is no need to figure out whether you need this or this miner, ANY miner software will work on the pool. If you run into any problems, let us know and we'll make it work, we're dedicated to making the pools work with ALL burst mining programs!
February 12, 2015, 09:53:41 AM
About burst.ga mining pool
There were a few teething issues, some brought to light once the larger load of miners connected.
Fixes have been put live as of this morning (my time) so you should see much quicker stats page startup.
Payments are flowing out okay.
Payment calculation has changed from the previous uray pool code. It is now:
So even tiny miners can win up to 3,500 Burst if they happen to strike lucky with their nonce and win the current block.
Big miners consistently win Burst by way of the historic shares.
The pool doesn't start generating payouts until about 5 blocks after a win just to make sure the pool REALLY won the block. (Sometimes network propagation delays allow another remote miner to actually get the block first).
Payouts are then shoved into a queue.
About another 5 blocks later payouts are tested to see if they have been confirmed or lost, in which case they are queued again. (Payouts can get lost if sent during a block changeover, for example).
Stats webpage is available at both http://burst.ga/ and http://burst.ga:8124/
Miners can use http://burst.ga:8124/
Blago miners need to have useFastRcv set to false. Symptoms of you needing to do this look like:
Pool only accepts deadlines less than 30 days. For Blago's miner you could add a line to your config like this: (not at the end - note trailing comma!)
If you submit a bad deadline then you're likely to get a 400 Bad Request response but there will be an error message to go with that.
400 Bad Request responses are also sent out for other reasons - check your logs!
There were a few teething issues, some brought to light once the larger load of miners connected.
Fixes have been put live as of this morning (my time) so you should see much quicker stats page startup.
Payments are flowing out okay.
Payment calculation has changed from the previous uray pool code. It is now:
- 50% of block reward is paid out as per "current shares" for that block
- 50% of block reward is paid out as per "historic shares" for that block
So even tiny miners can win up to 3,500 Burst if they happen to strike lucky with their nonce and win the current block.
Big miners consistently win Burst by way of the historic shares.
The pool doesn't start generating payouts until about 5 blocks after a win just to make sure the pool REALLY won the block. (Sometimes network propagation delays allow another remote miner to actually get the block first).
Payouts are then shoved into a queue.
About another 5 blocks later payouts are tested to see if they have been confirmed or lost, in which case they are queued again. (Payouts can get lost if sent during a block changeover, for example).
Stats webpage is available at both http://burst.ga/ and http://burst.ga:8124/
Miners can use http://burst.ga:8124/
Blago miners need to have useFastRcv set to false. Symptoms of you needing to do this look like:
Code:
04:33:39 *Count packets of response: 1
04:33:39 *! error parsing (1) message from server
04:33:39 *! error parsing (1) message from server
Pool only accepts deadlines less than 30 days. For Blago's miner you could add a line to your config like this: (not at the end - note trailing comma!)
Code:
"TargetDeadline": 2592000,
If you submit a bad deadline then you're likely to get a 400 Bad Request response but there will be an error message to go with that.
400 Bad Request responses are also sent out for other reasons - check your logs!
February 12, 2015, 06:00:12 AM
February 12, 2015, 05:54:15 AM
Is ok now
Hi, i appreciate some help. I'm new to burst.
When i try to accessed the wallet interface at http://localhost:8125 via Chrome or firefox i get this error: ERR_CONNECTION_REFUSED
what is wrong and what can i do right?
tyvm
Do you have any proxies configured? Are localhost connections permitted on your pc?When i try to accessed the wallet interface at http://localhost:8125 via Chrome or firefox i get this error: ERR_CONNECTION_REFUSED
what is wrong and what can i do right?
tyvm
I presume your wallet is running.
I went to LAN settings (in Chrome : Tools-> Options-> Under the hood -> Change Proxy setting -> LAN Setting)
There is be a checkbox for "Bypass proxy server for local address"
I ticked the checkbox.
Still same error!
Is there another solution??
Are you running a mac by any chance? Is your wallet running (i.e. did you start the run.bat)?
February 12, 2015, 05:32:39 AM
Hi, i appreciate some help. I'm new to burst.
When i try to accessed the wallet interface at http://localhost:8125 via Chrome or firefox i get this error: ERR_CONNECTION_REFUSED
what is wrong and what can i do right?
tyvm
Do you have any proxies configured? Are localhost connections permitted on your pc?When i try to accessed the wallet interface at http://localhost:8125 via Chrome or firefox i get this error: ERR_CONNECTION_REFUSED
what is wrong and what can i do right?
tyvm
I presume your wallet is running.
I went to LAN settings (in Chrome : Tools-> Options-> Under the hood -> Change Proxy setting -> LAN Setting)
There is be a checkbox for "Bypass proxy server for local address"
I ticked the checkbox.
Still same error!
Is there another solution??
February 12, 2015, 05:02:24 AM
Thank you, vbcs for doing such a great job in creating a ATcrowdfunding.
I got some questions and suggestions:
1. "Funding" is not a "Donation", so I expect to pay back a funded project. There is no terms set yet of how much interest, what time frame to pay back. Sure, an interest of -100% is a donation!
2. How can I see WHO has pledged so far? Which api can I use for that? So that I can follow up with these people by private messages.
3. Why would somebody fund a project, when they "hide" behind a Creator BURST account? We need a recommendation system.
4. There is no Withdraw or Edit function, e.g. if I want to change the description. Maybe we suggest to use a description link to be free of edit function and withdraw is the a normal expire.
5. I assume that this will pickup and more crowdfunding cases will emerge. Maybe a list of Funding cases and a click for more information would be better. E.g., ordered by highest % already funded and ordered by blocks to go, so that projects soon to be due and nearly reached project's target will be seen first to get easier funded.
6. How can we promote our funding case? Right now it is a title and a description. We would need a "link" to the promoted funding case, like we have an asset-id.
(I followed your asking, and pledged towards the development!)
I got some questions and suggestions:
1. "Funding" is not a "Donation", so I expect to pay back a funded project. There is no terms set yet of how much interest, what time frame to pay back. Sure, an interest of -100% is a donation!
2. How can I see WHO has pledged so far? Which api can I use for that? So that I can follow up with these people by private messages.
3. Why would somebody fund a project, when they "hide" behind a Creator BURST account? We need a recommendation system.
4. There is no Withdraw or Edit function, e.g. if I want to change the description. Maybe we suggest to use a description link to be free of edit function and withdraw is the a normal expire.
5. I assume that this will pickup and more crowdfunding cases will emerge. Maybe a list of Funding cases and a click for more information would be better. E.g., ordered by highest % already funded and ordered by blocks to go, so that projects soon to be due and nearly reached project's target will be seen first to get easier funded.
6. How can we promote our funding case? Right now it is a title and a description. We would need a "link" to the promoted funding case, like we have an asset-id.
(I followed your asking, and pledged towards the development!)
You should be aware that one important property of the ATs is that they are trustless and decentralized. Beeing able to modify something on the code of the AT after you have deployed it, then automatically.you loose that property. Maybe beeing able to change just the description does not affect that, but I dont think is a very important feature at the moment to implement it. Also i dont understand the withdraw option? What you mean? If someone sends pledges to the project he cannot undo the pledges, the only way to get his money back is if the projevt is not fully funded.
February 12, 2015, 04:04:18 AM
Hi guys. (reward recipients for each pool is top left corner, they are two completely separate pools.)
Yes, I will be keeping both pools.
burst.ga will eventually be setup with slightly different payout system (unless we decide the way it is is good.) Originally we were going to setup burst.ga with a payout system that's better for smaller guys, or medium guys, and burstcoining pool will be for larger miners...
yes, burstcoining is still the tester pool, but it's getting same updates pushed to it that burst.ga is...
burst.ga's server is a little faster, but it's also got a lot of miners connected to it.
The only issue currently I believe is that the UI doesn't come up super fast, but the nonces are still submitted, counted, and payouts are all good. The pool's server went from 100% usage on old pool with new blocks, to less than 50%! cat's code is great!
We still have a few things to work out, and I'm sure that more issues will arise, but cat is active daily and constanty working on things for me.
please let me know if you encounter any issues, and I will have them resolved post haste!
edit: also, just so everyone knows I have pledged to donate 200k+ to the crowdfund AT devfund. I will be doing so shortly. (at the latest by end day tomorrow)
Yes, I will be keeping both pools.
burst.ga will eventually be setup with slightly different payout system (unless we decide the way it is is good.) Originally we were going to setup burst.ga with a payout system that's better for smaller guys, or medium guys, and burstcoining pool will be for larger miners...
yes, burstcoining is still the tester pool, but it's getting same updates pushed to it that burst.ga is...
burst.ga's server is a little faster, but it's also got a lot of miners connected to it.
The only issue currently I believe is that the UI doesn't come up super fast, but the nonces are still submitted, counted, and payouts are all good. The pool's server went from 100% usage on old pool with new blocks, to less than 50%! cat's code is great!
We still have a few things to work out, and I'm sure that more issues will arise, but cat is active daily and constanty working on things for me.
please let me know if you encounter any issues, and I will have them resolved post haste!
edit: also, just so everyone knows I have pledged to donate 200k+ to the crowdfund AT devfund. I will be doing so shortly. (at the latest by end day tomorrow)
Hi crowetic,
Mining was smooth for the past days until the updates yesterday. Here's my problem.
- For some time I'm getting "receiving confirmation failed" and "get mining info failed" on debug=true.
- After few hours I get sdl:42 vs cdl:29 -- that's like 13 missed DL confirmation.
Seems not normal to me...
What part of Blago's miner settings should I keep in mind?
Thanks!
February 12, 2015, 03:31:33 AM
Hello,
How/where do I know if uray's pools are updated to latest wallet ?
Thanks
How/where do I know if uray's pools are updated to latest wallet ?
Thanks
February 11, 2015, 10:49:55 PM
Hi guys. (reward recipients for each pool is top left corner, they are two completely separate pools.)
Yes, I will be keeping both pools.
burst.ga will eventually be setup with slightly different payout system (unless we decide the way it is is good.) Originally we were going to setup burst.ga with a payout system that's better for smaller guys, or medium guys, and burstcoining pool will be for larger miners...
yes, burstcoining is still the tester pool, but it's getting same updates pushed to it that burst.ga is...
burst.ga's server is a little faster, but it's also got a lot of miners connected to it.
The only issue currently I believe is that the UI doesn't come up super fast, but the nonces are still submitted, counted, and payouts are all good. The pool's server went from 100% usage on old pool with new blocks, to less than 50%! cat's code is great!
We still have a few things to work out, and I'm sure that more issues will arise, but cat is active daily and constanty working on things for me.
please let me know if you encounter any issues, and I will have them resolved post haste!
edit: also, just so everyone knows I have pledged to donate 200k+ to the crowdfund AT devfund. I will be doing so shortly. (at the latest by end day tomorrow)
Yes, I will be keeping both pools.
burst.ga will eventually be setup with slightly different payout system (unless we decide the way it is is good.) Originally we were going to setup burst.ga with a payout system that's better for smaller guys, or medium guys, and burstcoining pool will be for larger miners...
yes, burstcoining is still the tester pool, but it's getting same updates pushed to it that burst.ga is...
burst.ga's server is a little faster, but it's also got a lot of miners connected to it.
The only issue currently I believe is that the UI doesn't come up super fast, but the nonces are still submitted, counted, and payouts are all good. The pool's server went from 100% usage on old pool with new blocks, to less than 50%! cat's code is great!
We still have a few things to work out, and I'm sure that more issues will arise, but cat is active daily and constanty working on things for me.
please let me know if you encounter any issues, and I will have them resolved post haste!
edit: also, just so everyone knows I have pledged to donate 200k+ to the crowdfund AT devfund. I will be doing so shortly. (at the latest by end day tomorrow)
February 11, 2015, 10:16:37 PM
lol what the heck only just turned 1 system on and starting rest up and poof lol
Where is that 192.168.0.2 in your screenshot coming from? Thats a local address - nothing to do with the pool. There's something very misconfigured on your miner.
H.
Jump to: