na einfach mal die Transaktion lesen - das ist eine asset creation transaction, und die kostet eben so viel.

2.000 USD/Tag ist jetzt nicht gerade ein duenner Strohhalm..
Aber mit dem Kurs gebe ich Dir voellig recht, da ist noch etwas zu erwarten - und wie mit allen "Aktien"-Anlagen gilt: Abwarten, keine Panik-Verkaeufe, ueberhaupt verkaufen nur wenn das Geld gebraucht wird.

ops, my fault, didn't touch it for more than 2 years. The mjminer has an avx2 codepath, compiled it under a specific name and forgot about where it came from.

https://github.com/r-majere/mjminer
https://github.com/Mirkic7/mdcct
https://github.com/kartojal/dcct-gui

https://forums.burst-team.us/category/47/miner


I've been using dcct (and variants) since end of 2014, and it is totally stable.
The reason to switch from burstcoin's POCminer was the runtime memory demands and
configurability (for me; MAXDEADLINE, CACHESIZE).

I have a script interpreting the miner's output to get an idea about
the longterm performance (IO/s and runtime per thread, blocktimes, number and value of deadlines found, ..).

Oh, there are several;
dcct
mjminer
avx2miner
the java-based miner will mine w/o GPU if you don't configure the opencl "targets"

Just take a look into the forums.

problems, not really, it just takes some time;
withdrawals ~1 hour (fastest for me: 10 blocks),
deposits ~2 hours (fastest for me: 20 blocks).
So it fluctuates with the block creation time.

This may seem odd at first, but I see the positive thing: You have no private local data.

No wallet that may be lost due to a local crash, no need to have a "local wallet" at all.
You just need to guard your passphrase (private key), and unless you mine solo it doesn't need
to be stored on disk at all.
Moving all your funds over to a new account/passphrase is easy and costs just 1 Burst.
I guess most people mining solo have a dedicated passphrase for that (as its needed
on disk or at least in RAM for the miner process) and another for their funds.

This wallet-less design is one of the many features I like very much.

I'm solo mining, and since 1.2.6 came out my main burst client (that I mine against) was on a fork 4 times.
I run another named burst client to support the network, without local miners, it got forked once.

Interestingly, my database folders contain a " burst.mv.db" of 7 - 9 GBytes (9 right after syncing, shrinking to ~7 after a few hours).
The downloaded db.zip contains a "burst.h2.db" of ~3,5 GByte. I always sync from the network and pulled the file out of curiosity, and did not start a wallet with it yet.

Why the different naming and size ?

IMHO, criss-cross blacklisting the major pools is a bad idea.
A "fork" situation is quite normal and will be resolved quickly
(usually within minutes).

The time needed for that is a function of propagation time.

By blacklisting known major block creators from each other,
you _increase_ propagation time.

This leads to the situation that pools are on different forks
longer than necessary with undesired side effects.

When like 50% of overall hashpower comes from just 2,3,4
pools, these 2,3,4 machines should have each other on their
trusted peerlist. Maybe a code tweak to force them staying
interconnected would help. Blacklisting is the exact opposite
of what is needed here.

What is the reasoning for this blacklisting ?
(I could be wrong on that, though.)

yes, for more than a week.
The owner/donation account is BURST-ZKU3-PKQ3-YHBS-FBDD9

If you mean the drop between blocks 188k and 190k, that was bitladen taking ~2PiB offline.
The daily average network size (from my miner logfile) for the last week is

4.24366
4.68704
5.04738
4.45498
4.88276
4.369
4.18486

so there is no substantial change.

oh, and if someone searches for the original atcrowdfund.html and doesn't find it (like me)
on CIYAM's git, it can be found in dawallet's burstwindowswallet. Here is the raw file:


https://raw.githubusercontent.com/dawallet/burstwindowswallet/master/burst_1.2.3/html/ui/atcrowdfund.html


and the lotteries.. just in case..


https://raw.githubusercontent.com/dawallet/burstwindowswallet/master/burst_1.2.3/html/ui/atlotteries.html

exactly, the reward assignment is on the blockchain and continuing to mine against your local wallet will
mince blocks, but you won't get the reward since the pool doesn't see your deadlines.
So it is all or nothing. Or you replot some of your space with a new ID, and use that for poolmining.
Preferably with a single miner instance.

Is having multiple miner instances on a pool still a problem ?
(each miner instance will report it's own deadline, so the may come in 90,110,50,70,55, triggering a pool-specific
 penalty mechanism for overloading the computation on the pool server)

bitladen's last submission was on 22-01-2016 04:54:39 UTC.

Network size is currently around 4.6 PB. Happy mining !

I recently stopped mining the 300 TB SAN, just have 96 TB left in a SAS JBOD.


Anyone interested in 32TB Raid units ?
Infortrend Eonstor FC-Sata units, single or dual controller, 16x 2TB disks, ~150W,
located in germany, pick-up only.
I could pre-plot to spec, xfs,ext2,3,4,ufs,zfs,xsan,ntfs,  you name it.
1 PB available.
Just send an offer via PM and we work something out.



and another one, feel free to update your entries..

https://docs.google.com/spreadsheets/d/1uaXMLjLt90Ms1oRjcjz-eYPOkARtNS8JdrKFKOJdg4o/edit?pli=1#gid=0