why you did you not use a script to cycle tor circuits with random realistic time offsets depending on the country origin if you wanted to get a coin voted in without having access to real random ips?

lets hope that people who voted this way are not involved to the vcash development if they do things such "stupid" 

has the ether-dao drama (http://www.coindesk.com/dao-attacked-code-issue-leads-60-million-ether-theft) any influence to the beta launch since ether got voted onto 2nd place so far?

Burst offers much more real world usecases than most people think of today.
Thinking BURST is cheap to mine is an illusion since BTC was also cheap to mine at some point in history.

One of the main advantages I see is that there are almost no running costs to keep the network secure.
This in combination with the offered features that have been developed on top of NXT makes BURST technically suitable for many all day usecases.

In terms of exchange rates I do not want to set a price but if you think of a service like slack offers and for which would be payed with BURST in a decentralized environment you can easily create a demand for the coin. If you say the price is set to what a miner with 2tb capacity can mine in a month and compare it to the smallest payed slack account these 10k burst have a value around 6.5$. Running a dedicated 2tb drive 24/7 for mining gets you your investment back within a year while having the next years for free.

If you play with these numbers it means to me that the mid term low settles somewhere where it has been a year ago.
For me the history has shown that everything takes a moment longer compared to other coins but finally it happens.

I would love to see BURST on the list (https://bitcointalk.org/index.php?topic=1323657.0) 

I am not sure if it is a good idea to submit deadlines from different miner instances for one account since higher deadlines may cause a penalty on pool side if one of the other miners already submitted a lower deadline.

anyone knows if there exists some sort of proxy for such setups?

if there exists none a total capacity above 50 tb should also be fine to mine solo with.

I do not really care for the past as long as it does not influence the future too hard but for me a hack is actively modifying the behaviour of a system. New to me is that mcxnow had wallet nodes on the 1.8 chain running.
If so the 1.8 hardfork influenced the the wallets exchange backend unintenionally which is no hack. If this has been the case I call it a design flaw of the exchange backend since it trusted the wallet node too much.
However, if I hardfork a coin which I maintain I would make really sure that all system relevant entities have moved to the new chain before I broadcast the magic message to the network to invalidate the old chain.
did doge had such mechanics on the 1.7 chain or has it them even on the current?
if not this is what you have to expect from almost any copyclones you invest into in the cryptoscene today.
 

c++ code makes it possible to control the whole system since there is no 3rd party code for databases, webservers and libraries in the exchange backend used.
having to rely on 3rd party code makes it simple to attack the site if a 0-day exploit is found for any package.
finding a 0-day for custom code is almost impossible since you have no access to the source to analyse it in depth to find useful attack vectors.

beside of security it runs much faster than anything else and can be optimized for requirements like thousands of transactions per second or in memory data verification.

I absolutely cannot understand why people think or communicate that mcxnow felt scammy.

I can only remember one unplanned maintance downtime for which was stated after an analysis that it has been caused by a memory fragmentation issue which triggered the ai to take the site automatically down before trades could be made.

Once there has been a planned downtime with a date set from which on the coins will not be accessable until the site is up again. I left most of my coins in the exchange and after the site was up again all my coins were still there.

One thing which people who do not understand what they trade may refer as "scam" to is the fact that the doge developers decided to switch to a new hardfork without making sure that the backend infastructure the community has built upon their coin is ready for the switch. As those traders realized what they traded and wanted to switch to the hardfork it was not possible since the users created a own ecosystem in the original doge chain which has been independant to the new hardfork (yes, people mined in that chain to trade coins on mcxnow).
Like no other exchange does mcxnow always showed the current blockchain height of the hot wallets live and everybody could see wether the site is in sync or not.

If the codebase is as stable as it was the new site will really become important for the whole crypto scene since there is absolutely nothing comparable for high frequency trades and trade execution time. I cannot remember any successful ddos attack since the main exchange is hidden behind proxies.

quick and dirty, would be better to have some commas replaced by points but this requires more time (changed words are underlined; mod the reply out when not needed anymore):

BURST has been launched in August 2014, so much happened the first year. However, the main developer
BurstDev (burstcoin on https://bitcointalk.org) slowly disappeared from the Dev-areas of BURST without
leaving much notice. Even though miners stayed loyal, something has to be done to keep up the
development!


It sounds more dramatic than it was. Day by day, people started to understand something had to be
done. A new (with some guys from the early days) a DevTeam had to be created. At an early stage
crowetic was pro-active, working to create what was needed with some other guys.

One important step to this, although if it seemed small, was building a new Announcement Thread (ANN) at
https://bitcointalk.org.
1 The old one had grown to over 1,200 pages; to be fair, it did have an enormous
amount of knowledge but it is totally unorganized and therefore it is very hard to find what you are looking for. In
addition, the Devs at the time were also unable to edit the Opening Post (OP) of the old thread, making
it quickly outdated. The new thread is a great success with less spam and relevant posts. The old thread
became like a reference library to new.

Behind the scenes, work to recruit new, improved and dedicated developers for BURST took some time.
However, today, the DevTeam was presented at the new ANN-thread at https://bitcointalk.org. Let’s
present them, some new, some familiar and some old faces (or should we say “nicks”).


As you all know, DCCT has been with us since the very beginning of the BURST, and has done some
amazing things for the coin, community and software, including one of the best miners ever for linux. He
is now helping us by becoming the official core dev, the main developer for BURST.


fuse (fusecavator, would like to be known as 'fuse') and vbcs are truly awesome. Fuse came to us with
some great topics, and has already implemented his suggested changes into the code, and these will be
put into the next release of the BURST wallet. vbcs, as you all know, has been around since day one as
well. He is happy since a Crowdfunding started for him was a success and he agreed to work with
BURST continually as part of the team. We are very lucky to have him as he is a fantastic developer. Fuse,
though new, is also a fantastic Dev and we've grown already tremendously fond of him, we know that
these two will make wonderful things together! We're truly honored to have them!



page 1 is reviewed 

clepto.design is a personal friend of crowetic, who helped him to get his company started which will be posting
a temporary page soon on clepto.design. We've decided he will be a tremendous help with graphics.
We thank him for what he has done so far which people will see shortly. we know he will be a great
asset in the future!


daWallet has already proven himself to be a massively beneficial member to the BURST team, and has
been extremely valuable and trustworthy. he has made BURST MUCH easier to use with his Windows
GUI, and continually released updates. He is also currently working on ANDROID DEVELOPMENT!


daWallet / Kleinstein / kartojal - We haven't seen Klein or Kart around for some time, but we do believe
they are not gone, and we do know that daWallet has a small team under him that will also do
mobile development and android stuff.


luxe has proven himself to be extremely valuable with his GPU miner release and much more, he is also
currently helping dcct with core dev. We are extremely proud to have him on our team. We think he will
continue to prove himself as a fantastic dev and great asset to the team!

As luxe already has been discussed, it’s time for Blago. He has been around for quite some time and
has proven himself not only to be the most awesome of miner developer, but also, the most Russian! We love
Blago and are very pleased to have him as part of our team - Thank you Blago!

In the context of BURST development, there are more, random Devs, who we haven't seen in a while
but believe will still be part of the team. cryo, googs, catbref, and cheester to name a few. Above is
the active team above. We also have a lawyer, a CPA, and a marketing master which we will remain
nameless for the moment.


Stay tuned to BURST, the hard-disk minable crypto not far to celebrate two years of low-energy, secure,
decentralized and suitable mining! For the future, we have much more to enjoy – wait & see.

thats all for now but more revising may be good

I am still not sure wether I have mentioned this design idea in the old announcement thread or not.
Regarding the pool situation I think the time has come to think about a sort of distributed pool design which is only coordinated from a central instance.

Most of the amount of work a pool has to do is to verify the received shares to calculate the reslulting deadlines.
Set the fact that miners can do this work instead of the pool there has only to be some sort of verification.

If we look at the pool like a p2p network it is possible to let miners verify the shares for other miners before the pool actually verifies them on its own.
This design requires to add some additional logic into the miners for the pool but may cut down the cpu costs for verifying shares in time to almost 0 since the pool servers would only require to test the submitted share deadlines which have a chance to mine the block (the others get verified by the miners of the pool).

I know this requires some coding and testing but in the end this enables to scale almost as much as bandwidth allows.

To explain this design a bit more in detail you can think of these behaviours as examples:

minerA finds a deadline and submits it to the pool --> the pool dispatches this for verification to 3 random miners --> the random miners decline or confirm and the deadline gets accepted

minerA finds a deadline and submits it to the pool --> the pool dispatches this for verification to 3 random miners --> a timeout (eg. 20 seconds) happens without answer and the pool verifies the deadline on its own

minerA submits a deadline which could find a block --> the pool verifies it on its own and submits the block to the network


the main development which is required would be to design the backend, a protocol to transmit the workloads and the miner integration.

most of this should already exist and only the distributed deadline verification would have to be added.

The nice part of this design is that the miners may also receive a stake of the pool fees for the verification work they do.
I have not played with numbers yet but this means that even small miners can benefit from large miners and it allows to count in even high deadlines (eg. <50m seconds).

with usb i would split up the drives to several ports since if one drive on a bus times out it freezes all others.
depending on the setup you want (external usb drives with own psus) it may be cheaper and maybe more reliable to put some sata controllers into the rig and connect them to the systems psu (http://www.newegg.com/Product/Product.aspx?Item=N82E16816124070).

The address BURST-R8SQ-TUEM-DTHQ-7ATA3 is the poloniex hot wallet.
Not sure wether the 40TB & 100TB represent the correct numbers since the network size is an estimation based on the time blocks required to be found using a low number of blocks in the calculation to adjust fast.
Someone with a medium sized gpu mining farm could have added a couple of drives to the rigs easily consuming only additional 20-30 watts per rig.

Either you run 40 GPU mining rigs as individual and attach to each rig four 4-8TB USB or internal drives or there are 40 people with rigs doing so.
Both sums quickly up to a PB. Since you built the rigs for GPU mining with fast GPUs you can plot all disks simultanously ith one card which yields at least 32k nonces per minute or in total approximately 50 TB unoptimized plots per hour in this scenario.
Thinking about easter based holidays in many countries maybe someone or many decided to use these free days to setup the rigs.

All this results in plotting a PB within a day and another to optimize the plots.

Regarding the costs of this PB it may sum up to about 140-250 BTC (4/6tb http://www.newegg.com/Product/Product.aspx?Item=N82E16822178783&ignorebbr=1) at current rates and represents almost 1/5 to 1/3 of the current marketcap burst has.

I think storing "useful" data within the plots is something which requires drastical bandwidth usage.
In the past this discussion lasted over several pages in the original announce thread with these results if i remember correctly:
-plots may store user data after a redesign of the mining algorythm and coin design
-the miners would require much bandwidth to serve the files
-there was no consensus about how many copies of the data shall exist and how many should be assumed as secure if you want to access your files later
-there are other coins focusing to act as cloud storage provider

i think if you really want to only store data simply use mega and encrypt your stuff. this has for me the same reliance as a crypto coin archiving your files. 

I am not quite sure what you want.
shall this be a tradebot for the asset exchange or a simple set of shellscripts like those?
order.sh asset_id amount price buy|sell account_secret
cancel_order.sh order_id account_secret
show_active_order.sh account_id

The most straight forward thing you can do is to CPU plot using the dcct tools.
On Linux it is much simpler to plot than on Windows since you have shellscript.

If you can use the boot or a spare ssd for plotting the optimization would be much faster.
after the plot is optimized you move it to your storage location.
best way to do it is to create a scriptfile with all plots which shall be created.
each plot is then created and optimized afterwards like this (replace all marked parameters "xxx" with yours):
 
nice ./plotavx2 -k "replace with your numeric account id" -x 2 -d plots -s 1 -n 524288 -m 16384 -a -t 8
./optimizefiles.sh
nice ./plotavx2 -k "replace with your numeric account id" -x 2 -d plots -s "1+524288" -n 524288 -m 16384 -a -t 8
./optimizefiles.sh
nice ./plotavx2 -k "replace with your numeric account id" -x 2 -d plots -s "1+524288+524288" -n 524288 -m 16384 -a -t 8
./optimizefiles.sh


a simple optimize script i used is this (it optimizes all files in the ./plots folder and then moves it to the target location; adjust the paths if needed):

files=`find ./plots|grep _`
for i in $files; do
   ./optimize -m 4096 $i
   touch done/$i
done
mv plots/* /mnt/burst/plots/

for mining you then simply add each plotfile storage location to the miner command.

I hope this helps and is not too "technical" 

thanks for this link to the document. it is new to me.

the authors of the document assume that it is possible to only compute a specific scoop of a plot since they base their whole information on the only available flow chart which exists ("...a miner can initially compute and store only the value x4096." --- http://burstcoin.info/assets/img/flow.png )

they either intentionally or due to the simplifications in the flow chart came to the conclusion that the scoop datafile content for a account-nonce combination represents a single shabal hash.
the implementation requires to compute all 4096 scoops as a block and then these get cut into 64 byte blocks which are read during the mining.

i have done my own analysis some time back (based on the c plotter sourcecode) and came to the conclusion that even the most efficient asics result in higher running costs than mining from at this time available storage devices.

grinding is basically not possible since there is no merkle root and transactions have no influence on the generated blocks.

in future asics may support the plotting and mining process like gpus do today in large rigs.

who cares about how a consesus algorythm is labeled as long as it works?

since proof of work can only kept decentralized as long as cheap compute resources are available to the masses it is a public secret that decentralized PoW has failed.
i think BURSTs PoC (proof of capacity) algo is worth to look closer at because it removed the PoW and PoS design flaws (long term secure affordable decentralization).

since the algo is based on precomputed data comparable to rainbow tables there is no way to develop special centralized hardware like asics for it (in terms of running costs as capacity replacement).
for the decentralization this means everyone can buy regular hdds in the next shop around the corner or use spare capacity.
compared to PoW there are almost "no" running costs.

the coin exists for over a year now and instead of having a whitepaper it has a over 1000 pages long bitcointalk thread here:
https://bitcointalk.org/index.php?topic=731923.0

everything depends on how market cap is measured.
you can only measure market cap when it is possible to directly convert the coin into dollars.
even if this is possible you cannot simply sum up what the current price tag is. you would have to estimate how the coins ecosystem reacts to big conversions.
this means you cannot simply sum up the coins in existence and multiply it by the average exchange rate.
another big point in terms of market cap is how people rely on services based on the coin.
if there exists a healthy ecosystem the coin can handle huge coin to dollar conversions simply because people also swap from dollar to coin.
to bring all this into a relation to archive some sort of "normalized" market cap is only as estimation possible.
in other words it means there does not exist anything like a marketcap of a coin which can be compared to another.