Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 654. (Read 2171095 times)

It is interesting, I compare today miners on my plots...
Can you PM me log-file? (if not solo)

Yep that sounds like a winner!

Ahha, why not issue an asset which is backed by fees from this automatic bittrex seller. Pays out monthly and then there's a buy wall as well....and as the month progresses the ask goes up to avoid abuse.....If we have a dev to implement the automated bittrex sender....this could actually work quite well.....The buy wall would also mean that people can withdraw whenever they want without losing interest.

It is interesting, I compare today miners on my plots...
Can you PM me log-file? (if not solo)

Pretty much like that, but if we use minimum held in the last month it gets people thinking long term. This would need a dev tho....kinda like the mgw for nxt....

@Blago: I just started trying out your miner today and I've found it reads my drives a lot faster than urays miner. However, in doing tests, I've noticed that it occasionally misses better deadlines/nonces.

I have ~5tb of plots across two drives with a 10,000 stagger size. Your miner gets through one drive (5x plots, ~1tb) in 8 seconds and the other drive (16x plots, ~4tb) in 30 seconds, which is awesome. However, during the long deadlines after it's complete, I've been firing up Uray's miner and letting it run (which takes approx 2 minutes to parse all the plots) and it occasionally finds a better deadline and submits it.

Twice in a row now I've had:


and it's complete. So I fire up uray's and let it run, and see this:

Any ideas on what might cause this? How is your miner missing blocks that uray's miner is finding?

Hmm What about have a monthly interest payout from the fees collected paid to all addresses who hold >=X burst for >=X length of time?

I'd rather have that 2% go as interest to all burst holders, so it takes the lowest amount of burst you've had in your account over a month, and rewards you based on that. How does that sound? Even better if the fee and reward were in burst.

What do you guys think about having an option built into the wallet that will automatically send coins to Bittrex or C-Cex as they come in from the pools and sell them for you at the market rate for BTC for a 2% fee?

That 2% fee of Bitcoin gets automatically added to a buy wall further down. Over time, the buy wall builds in size, the market rate increases, the miners receive more BTC for their coins, more miners come and mine etc.

Seems like a good way to boost the price over time and increase the size of the community. People are going to mine and dump anyway - may as well make it easier for them and take a little bit off the top for buy support - everyone wins.

i am considering burst now but its a close call with magi m7m algo

So I decided to start mining burst and give it a try. I setup some plots and everything and just need to activate my address. Unfortunately the faucets are dry and solo mining is not feasible with the amount of hdd space I have. If anyone can donate burst to BURST-VDAX-PNHT-A762-4ZTPF it would be greatly appreciated

This is a feature i need ! Is it something like i can set to auto transfer x amount of burst at a set time ? Miner could use this feature to auto send mined coin to exchange without having to physically open up the wallet and send the coin.

The past week has admittedly not been great for progress. I was originally planning on trying to quickly roll out subscriptions(reoccurring transactions), and then move onto other things. Most of subscriptions was implemented, however I halted it to reconsider some things when I realized that the initial implementation would make it way too easy and cheap for someone to set up payments that would rapidly send a few coins back and forth between 2 accounts forever, increasing processing load for the whole network. I spent a bit of time looking at java dht libraries to see if there was anything I liked that I could utilize instead of working from scratch. I ended up deciding that I'm best off making it myself. I also was taking a look at the android sdk to see about starting a fairly basic thin client. I had not used the android sdk before, and had a bit of a rough start, and made the mistake of trying(and failing repeatedly) to integrate zxing qr scanner into an app instead of calling the seperate app.

http://burstforum.com for starters and we have a GUI in the works with pretty much everything built in.

I was originally planning on trying to quickly roll out subscriptions(reoccurring transactions)

The point of dev1 was originally to get a pool running as quickly as possible, even though it was not a good setup. When dev1 was created and launched, reward assignment had not been made yet, so users had to generate plots to addresses held by the pool. This means that users mining there cannot use those plot files on other pools. Replotting with the newer and faster plotters likely isn't an issue for most, however enough users have expressed concern about wanting to continue using it as is that it doesn't make sense to force them off or alter things. Regarding your dev3 suggestion, I doubt most people would rather have me tinkering with pools instead of working on features, and graphics are not a strength of mine.

The past week has admittedly not been great for progress. I was originally planning on trying to quickly roll out subscriptions(reoccurring transactions), and then move onto other things. Most of subscriptions was implemented, however I halted it to reconsider some things when I realized that the initial implementation would make it way too easy and cheap for someone to set up payments that would rapidly send a few coins back and forth between 2 accounts forever, increasing processing load for the whole network. I spent a bit of time looking at java dht libraries to see if there was anything I liked that I could utilize instead of working from scratch. I ended up deciding that I'm best off making it myself. I also was taking a look at the android sdk to see about starting a fairly basic thin client. I had not used the android sdk before, and had a bit of a rough start, and made the mistake of trying(and failing repeatedly) to integrate zxing qr scanner into an app instead of calling the seperate app.