[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[bitladen]

If you're holding a coin obviously it seems like the right decision to reduce supply, it therefore increases the value of what you own (supply/demand). However if no one cares about what you have anymore you're essentially a bag holder, so it doesn't even matter what the supply and demand end up as. There wont be any demand because people will no longer care.

To begin, I think you're too stuck in the mainline bitcoin propaganda, I do know the theory, but as you can see, it's not really working out. Reason being, that some people care a lot less than others, due to the fact that they got their coins VERY inexpensively. It's a design flaw. As another user pointed out, the faster the reward is being scheduled to reduce, the more aggravated this is. However this exists even in bitcoin, but because the reward reduces a lot more slowly and hashrate is kind of stabilized, the coin still resists, it doesn't die like the others. Others (including BURST) have this scheduled too fast, I don't see them holding at this rate. In fact, we see them failing all the time.

Your proposal with freezing the reward is very good. You got a supporter already!

I am only holding 2.5M, while I have had 10% of the hashpower for a month. My 2.5M change nothing, even though it should. That's the point I'm trying to make here.

It'd be interesting to try for a prototype coin, but not for a established coin.

Of course I am talking about a prototype coin, I never said change burst, it's a bit late for that. But I got here because it seems I'm one of the main miners, and recently people have been talking about me, so I responded, and I also took the opportunity to bring my ideas to the community.

[burstcoin]

I'm not sure exactly where the limits are on Bitcoin's scripts, but it likely is able to handle at least the simple side of the previously described transfer. Monitoring btc's blockchain would introduce a ton of unwanted traffic, and would only assist in transfering between one coin instead of any.

I'm not sure this is what you want to hear, but as your average Joe miner, I still have no idea what ATs are and what they mean to me as a miner or a user of burst. Best I can tell, you can use them as fundraisers, but there is currently no way of actually looking at them or doing anything with them without a bunch of messing around (special scripts).

This is the main thing being worked on currently. I have a site I'm working on which has various AT tools, some simple, and some more advanced. It will have a AT creation tool which will allow you to choose templates and options and it will tell you what to plug into burst to make that AT. There is an AT examine tool which dumps the state of an AT and disassembles tje code so you can see what it does. On the more advances side, there's an in-browser version of the AT assembler, and an editor for creating AT interfaces. In a future update ATs will be able to have interface data attached to them so they can be interacted with without all the extra html file stuff that's currently used. I know the current toolchain is rather ugly for those without knowledge of the internals.

[bitladen]

This is the main thing being worked on currently. I have a site I'm working on which has various AT tools, some simple, and some more advanced. It will have a AT creation tool which will allow you to choose templates and options and it will tell you what to plug into burst to make that AT. There is an AT examine tool which dumps the state of an AT and disassembles tje code so you can see what it does. On the more advances side, there's an in-browser version of the AT assembler, and an editor for creating AT interfaces. In a future update ATs will be able to have interface data attached to them so they can be interacted with without all the extra html file stuff that's currently used. I know the current toolchain is rather ugly for those without knowledge of the internals.

This is interesting. AT assembler? What kind of code is this?

[bobafett]

Update and News: www.burstcoin.de

>> New Feature: German Linux Plot Optimization Guide is available

[burstcoin]

This is the main thing being worked on currently. I have a site I'm working on which has various AT tools, some simple, and some more advanced. It will have a AT creation tool which will allow you to choose templates and options and it will tell you what to plug into burst to make that AT. There is an AT examine tool which dumps the state of an AT and disassembles tje code so you can see what it does. On the more advances side, there's an in-browser version of the AT assembler, and an editor for creating AT interfaces. In a future update ATs will be able to have interface data attached to them so they can be interacted with without all the extra html file stuff that's currently used. I know the current toolchain is rather ugly for those without knowledge of the internals.

This is interesting. AT assembler? What kind of code is this?

It's assembly language for the AT vm.

Some examples can be found here, https://bitcointalk.org/index.php?topic=949438.msg10408276#msg10408276
and full specs are here http://ciyam.org/at/at.html and http://ciyam.org/at/at_api.html

[CIYAM]

This is interesting. AT assembler? What kind of code is this?

AT is a virtual CPU so they are "machine code" (a bit like the contents of an .exe for Windows).

The AT Assembler allows a higher level than writing raw machine code (which is just hex bytes) but lower level than languages such as C or Python.

It is envisioned that for the most part people will actually just use "templates" and not have to worry about writing "code" at all. You will select the appropriate template (let's say Crowdfund) then fill in some values (such as payout account, amount to raise and time limit to raise the funds) and the assembly (and machine code) will be generated for you automatically.

[Blago]

Using Blago Miner 1.150319,  For some reason my network drive plots are not getting recognized.  They where recognized in 1.4 version so not sure if I need to change anything in my config.  I can navigate to the network drive using explorer.
....

try share folder "plots" as network drive "Z:\"

[elproducto]

try share folder "plots" as network drive "Z:\"

Thanks for you help.  I tried what you recommended and got an error message "Debug Assertion Failed!".  I also tried with "Z:\\" and the miner starts but again the contents of Z: is not recognized.

https://i.imgur.com/eqI58hB.png

[bobafett]

you have Z:\, has to be Z:\\

[bensam1231]

I agree, Blago definitely needs a readme file. I swapped to the dev pool and had to look around for settings and I don't even know if found them all again.

Curiously, what is the best pool for a larger miner? I've tried dev before and urays. I haven't tried burst.ninja. What are peoples experience?

[crowetic]

I agree, Blago definitely needs a readme file. I swapped to the dev pool and had to look around for settings and I don't even know if found them all again.

Curiously, what is the best pool for a larger miner? I've tried dev before and urays. I haven't tried burst.ninja. What are peoples experience?

ninja pool is set to be friendly to larger miners and blockfinders (but yet also be friendly to smaller miners, and we're constantly changing how payouts work.)


We have a pretty solid setup right now which goes like this...


There are two pies, one that is historic share submissions calculated into percentages of input (power) to the pool. Based on lowest share submissions, a miner is placed with a percentage of the pool. This percentage is a ladder you can see on the stats. The Right pie, the historic pie, shows the historically best submitting miners.

The left pie, is the Current round pie, this shows the submissions and percentage distribution ladder for current round shares. A miner submits a great share, they get a much larger percentage in this pie, but also a submission of another great share would give that miner another larger percentage of the current round pie, and a good chunk of the reward. You can see the percentage distribution ladder on the stats there too...

The blend of the two pies that makes the total is 60% based on the Left (current round, current block) pie, and 40% based on the right (historically best submitting miners) pie.


We have a method of both changing the distribution ladders, and also the basis of payments on each pie. Everything is completely customizable.

The settings that we've got there currently I have had no complaints about, and block finder gets the most, followed by the second best submission for current round, then the larger boys get a more solid payout each block, and of course a lot more if they are the block finder, or have a share close to the block finder (in seconds)

We believe we have the best payout system, we like that it gives the lowest submissions a lot, while simulaneously providing solid payouts to our more supportive and larger guys.

I think it is a nice system. We always take the advice of our miners, and listen with open ears, if we think you've got a good suggestion, we will take it into account. we've got many other ideas for the pool as well.

Come give us a shot, if you don't like it, let me know what you don't like and we can take a change into consideration.

My goal is to make the most balanced and fair payout system in the BURST community.

We are also working on a new UI, so the rainbow will soon be no more. lol.



We have also a minimum payout (I think it is set to 300?) so no payouts under that are sent, to avoid unnecessary transaction fees. They are stored until you have enough to get a payout. If you decide to quit mining, after a set number of blocks (I believe that number is 500?) the system will pay you out regardless of balance.

[bensam1231]

As far as UI goes, Uray definitely has the best stats system. Although some bits are messing or hard to find. It also consumes a lot of CPU when you have his miner page open. That's really secondary to payouts though.

[bensam1231]

Also I may have found a bug with Blagos latest version. It's not showing confirmations from dev v2 even though the pool is giving me shares.

Come give us a shot, if you don't like it, let me know what you don't like and we can take a change into consideration.

Curiously, why doesn't it just tabulate the amount of space you hashed for a block and then do a proportional payout for it regardless of your deadlines? Since it's random, users have no control over their deadlines and can't really 'tweak' them. The only thing they can tweak is speed. How much you can hash within a given time frame is a good indicator of 'hashrate', since size alone doesn't determine how effective your Burst miner is. A block itself simply could be used for the time frame of hashing and the proportion of work for that block.

I don't know if pools can see how much storage someone has, but if they could this seems like the overall best method. Big miner or small it really shouldn't matter, it's all about the amount of work you can do. Block winner and second best deadlines shouldn't matter again as it's random and the whole reason for being on a pool is to average everything out.

You could add a 'historic' element in there too to prevent pool hoping, but that's really not a thing in Burst and it honestly doesn't matter. Someone hoping on the pool for five minutes is just as effective as someone hoping on for 10 days relatively speaking per block (as long as they stay for the full block).

[crowetic]

Also I may have found a bug with Blagos latest version. It's not showing confirmations from dev v2 even though the pool is giving me shares.

Come give us a shot, if you don't like it, let me know what you don't like and we can take a change into consideration.

Curiously, why doesn't it just tabulate the amount of space you hashed for a block and then do a proportional payout for it regardless of your deadlines? Since it's random, users have no control over their deadlines and can't really 'tweak' them. The only thing they can tweak is speed. How much you can hash within a given time frame is a good indicator of 'hashrate', since size alone doesn't determine how effective your Burst miner is. A block itself simply could be used for the time frame of hashing and the proportion of work for that block.

I don't know if pools can see how much storage someone has, but if they could this seems like the overall best method. Big miner or small it really shouldn't matter, it's all about the amount of work you can do. Block winner and second best deadlines shouldn't matter again as it's random and the whole reason for being on a pool is to average everything out.

You could add a 'historic' element in there too to prevent pool hoping, but that's really not a thing in Burst and it honestly doesn't matter. Someone hoping on the pool for five minutes is just as effective as someone hoping on for 10 days relatively speaking per block (as long as they stay for the full block).

It is not possible to see exact amount of size a miner has, our pool estimates and that is as good as it gets.

Basing payouts off a rough estimation is a bad plan. Right now we base payouts on how many good submissions and how many of the good submissions are lower numbers, and that is how it is paid out. I believe this to be the only fair way to pay miners in a BURST pool.

payment based on what you give, you get what you give. The better you do, the better the pool does, the more you get. The lower shares you submit, the more you get.

Basing payouts (even if we could estimate size perfectly) on size alone is simply not a good way to do things. What if a miner has a ton of space but can't read through it all correctly because they don't have a great processor, they should be paid more than someone who has less actual space but yet provides more useful share submissions to the pool?

I'm sorry, I just don't agree with this method of payout at all. Feel free to clarify if I'm not correct in your suggestion.

It is all about how much you give to the pool. When you base it off share submissions, and give the better shares a better pay, this is how it works, then the miners who consistently submit better shares, get a little extra bonus with the Historic pie, because they give more overall good work to the pool.

[Blago]

...
Let's just say, amongst many other bugs, that {char blago[50]; return blago;} is just not right. OK? I see Blago commented on me
Peace be upon you!

Found, fixed, thanks! 

[crazyearner]

Just had problem with miner crash out again




any idea what the cause of this is using blago miner

[go6ooo1212]

Just install Blagos miner 19.03.2015 edition - couple of posts above...

[mmmaybe]

Regarding anonymity and the refreshing discussion around bitladen today, do we have any contact with monero...? Have anyone approached them asking what they think about ATs in their setting?

[coinits]

Regarding anonymity and the refreshing discussion around bitladen today, do we have any contact with monero...? Have anyone approached them asking what they think about ATs in their setting?

fluffypony or smooth are your best bets.

[mmmaybe]

Probably, but I just want to know if such contacts have been taken before, and if not, if there is a special reason for it.

I think the odds are very, very low at them adopting AT, but it would be huge if they where interested.