So, will the v2 work with the solo mining plots?
Yes, that's the point of v2.
Will you consider building a PR team to help you promote the coin more?
Not even sure where to start with that, but I'd rather wait until we have actual new features in addition to just new mining to do promotion.
Any plans to use the data in the plots for data storage?
If you have any ideas on how to actually do that, I'd be interested to know, but it's not a priority regardless.
How far off is the v2 pool being done?
Sounds logical with waiting to make sure all the new features are in place before a PR team.
As far as the data storage, I wouldn't know where to start since my programming skills are novice at most. Probably is possible and a fork would probably have to be done to implement it.
I'm hoping to release a new client update within the next 1-2 days that goes into affect 2-3 days after that, and I would expect to have the v2 pool ready to go by then, so 3-5 days.
The problem with data storage, is with the current system, anyone can generate the same plot given the address/nonce combination stored in the blockchain to verify things, but if you try to do data storage, not everyone can store a copy of all the data.
I think we might want to have data storage as an additional way to earn coins. so.. You can have plot files for mining as we have now, and you can also designate a directory and a max space limit , and then burstcoin will start using that directory for distributed data storage, paying you for usage somehow, directing burst coins from users to drive donators.
A good system would be super anonymous - you should not be able to figure out in any way what is on your drive, and it should not be possible to easily find out where the parts of a given file is stored
This would ensure it was not possible for someone to get into trouble because their storage directory happened to store something that someone found gave them the right to come after the one owning the drive.
You might want to add in support such that it was also not possible to find out who stored a given file in the first place.
it might be beneficial if stored files could either be private (only people with a code matcing the file can see it or read it) or public (discoverable in some kind of directory, all with the file ID can read it)
If BURST gets a really high price, the value of 1 burst might become too high to be used as a micro payment. a burst is alreday a cent these days. If it becomes a dollar, then transaction fee is way too high for many uses. What are the options available to avoid that problem when we run into it?