Topic: Burst Power Network [Pre-Announcement] (Read 1718 times)

Just might do that.

You should come join our chat at https://alttech.chat sometimes it helps to see if feedback is available in realtime

Perhaps you could recruit some testers over there

Well, the particulars are being hashed out.  The basics are each server having 10 1 TB pre-plotted drives.  Those will be rent-able at $10 per month each.  I really need some people to hit our pool because we are testing it and need to know that it can handle the stress.

So you renting out hashing power ?? Good idea dude !! I think I will buy some from you but I also have great interest in this coin and plan to buy something like 10 hdds of 3tb big . I am still thinking about it. I think buying a few at a time is good for now even one to start with then use that profit to add on, I will assume this is your plan too and you need the backing of customers money to expand. Makes sense. Could start a site maybe even share hashpower ? I don't know dude think about it.

Ok, testing for the Burst Power Network Mining Pool has begun.  The temp address is http://burstpowernetwork.ml and I believe all of the links are good on there, I am in and out of the office.  The balance has not updated as we are moving Burst around to cover the payouts, so if there is an issue with that it will be fixed when the next won block hits.


So...set your reward payout to BURST-76BN-JADZ-JVLB-GCDV4 your miner pointed to burstpowernetwork.ml:8124 and lets get this going!  Thanks, I will take care of your guys as the week progresses.  

BURST POWER NETWORK

Well, local testing for the mining pool is a strange thing.  You literally have three different possible places where an issue can be and tracking is next to nothing.  For those that are thinking about doing a pool themselves for Burst here are a few things that we figured out that seem to appear no where that we could find on the web.  I will tell you the one issue that we have still not been able to fix when we get to that part of setup.

The whole system is comprised of the Burst Wallet and the mining pool software.  The wallet that we are using is one of the latest builds and has a little GUI built in so that helps make things go easier.  The dl link is https://github.com/burst-team/burstcoin/releases.  It is a simple unzip to where you are going to have the files.  If you have Burst, then you likely have this already.  The db download that lessens the amount of time to sync can be downloaded from https://cloud.crowetic.com/s/6anamQ3PVfaFxlO/download.  This can go into the db folder in your wallet folder, you can find it.  Once that is in place, make sure the wallet has synced and all that good stuff.  Light touches on those things because we assume you have already done it.

http://download1594.mediafire.com/j00bbs9abnog/pcd6shyarj5hs64/Burst-Pool.rar

That should be the link for the pool.  The folder will be named burst-pool-master or similar.  You can extract the folder to where ever, I keep the wallet and the pool in separate folders but together in a Burst folder with the Uray miner folder.  Now, before touching the pool, Google and install node.js.  Pretty quick and easy.  Then go into the pool folder and set up the conf file.  Since you have the wallet installed, you should be running Java and you should have the Java exe in your PATH, if not Google that and fix it.

Note.....a trick to modifying JS files without using bulky IDE's is to open something like Wordpad and then tell it to open the file you want to edit.  Once Java has been installed, some JS and Java files will just autorun no matter what you do if you open them from the file side, from within a text editor is easier.  There's directions to setting up that file, so have at it.  Personally, I used the burst team online wallet to view my details, just quicker.  By default, the pool will host a page on port 80, if that is a conflict, change it.

Now, your wallet should be running and synced, if you just started Burst, give it a few and when localhost:8125 shows properly in your browser it is time.  You want to start the mining pool from within a command prompt.  An easy way is to open the folder, go to file....and you will see command prompt.  That starts it off right from that folder.  Once the command prompt is up type "node burst-pool.js".  If you get an unrecognized command error, make sure that node is in the PATH.  You should see things moving along and a message soon that the server has started.  If so, go to http://localhost in your browser and you will recognize the UI.

A note, even after doing a proper conf file in the pool, the website template needs to be tweaked with your address and URL, that is not automatic.  

Now, here's where out issue hit.  We keep seeing an API error in the website when it tries to get the pools balance.  First we fiddled with the pool and it seems that the issue is in the wallet/daemon, not the pool.  First, after reading the nxt config in the wallet folder, I found that the API location was listed as html/ui and there was no NXT folder there.  So, I copied the NXT folder from the src folder, just outside of the wallet and put it there.  That is no right.  The reference is meant to be handed to Java and the NXT folder is right where it should be, in the src folder.  The address references in the pool config are worded funny, so I modded those values and still nothing.  I have gone to http://localhost:8125/test which lets you play with the API calls and that is all good.  All in all, there is the daemon running, which is actually NXT, since Burst is a child, Java, JS, and Jetty.  I am not familiar with Jetty.  The pool works, per se, it moves along and has pretty accurate seeming info.  I even mined to it and that worked, but payments will likely get hooked on that balance issue.  The best I can figure is that the address and key info in the pool config is wrong.  There are fields for the pools private keys and for a key that mentioned RS.  These have to be right, as the private key is the passphrase for the pool wallet and since they mentioned RS, that means the address starting with BURST.  

poolPublic and  poolFeePaymentAddr are a little more tricky.  If you look at your wallet address info, pool public is the label used for the long string address, all numbers.  The second field is an odd inclusion.  I do not know why, by default, they would assume a different wallet would handle fees.  For this one I used the short all numeric address, not sure that is right. I was looking and just realized that pvtkey and passphrase may not be the same.     Wish us luck...



Edit....solved....the time we had the wallet offline for implementation caused it to need about ten minutes to sync, once it was synced the balance info completes.

yeah, well, that would mean we would have to get this software running, lol

They are not needed for the plots to be seen, but they give the user the ability to mine directly from the plots.  I wonder if each hard drive could mine to a private pool the site controls and that pool could then be pointed to an outside pool so that the outside pool sees those pooled miners from your site as one entity.

ok guys, this is why we start early.  we are having issues getting the pool server software running properly.....it starts and even connects partially with the wallet background, but there are some API calls that are having issues.   we are working to get everything the way it needs to be.

Yeah, have not had the chance to try it yet.  All I know is that looking at the config for the mining pool there is a line near the top for a redirection.

Regarding the first part -> acting as one miner towards one of the existing pools.

It might be worth your while, depending on how much space you plot, to consider having your pool going solo. For the sake of decentralization .

I bring this up as I am unsure how much time would such a "pass through" to an existing pool take. Since all of your miners would essentially be local, thus eliminating latency, you should be able to pull it off in short enough time to avoid missing out on short deadlines.

We are putting the server into action tonight or early tomorrow.  Initially it will simply be the mining pool for stress testing.  Started a small ICO through Burst, you can go to those through your wallet and search for "BurstPowerNetwork" no spaces or simply help by funding address  BURST-76BN-JADZ-JVLB-GCDV4

Please note your TX id and PM me because we intend for each 1000  Burst to represent ten shares.

This is simply a stage 1 preliminary road map.  More for us to keep a visual track record and to have it archived here.

for the most part, they are unnecessary.  they are the same files that are in the burst download.  you should download the uray miner......http://burstcoin.biz/download/11-uray-burst-miner-(win-x64)

a couple pointers....

1. If you use the wallet to make your plots, make sure that you are logged in under the same address that you will mine from.  Otherwise you will get an error when mining.  If you find that you have plots from another address, then simply rename the first portion with your numeric address.

2. Make sure you set the reward to the right pool and wait the 4 confirmations.  http://127.0.0.1:8125/rewardassignment.html there is no need to freak out about putting your passphrase in, the URL is your local wallet.  If it will not load, then start the wallet, wait 10 mins and try again.  Use the bottom part of the form, your passphrase and the address of the pool you are going to mine.  While you wait for the 4 confirmations, set up the conf file in the folder with the Uray miner you just d'led.  Just fill in the URL in the top part and check the port, usually 8124. Then update the paths to your plots.  This is a pain on some miners.  Use the "\" slash and not the other.  Also, do not put "http://" on the URL.

3. Once you have the 4 confirmation, hit the pool website and fire up Uray's miner.  You will see each plot get parsed and read.  You will see a series of deadlines, but these are not good yet.  The miner will submit the best dl, you will see a success message, but still not in there yet.  The last message you should see about a dl is the "Confirmed" line.  That means that the pool accepted your deadline.  Multiple deadlines may be accepted and you will rank and be rewarded based on your best.

Here's the trick.  There are three states to getting paid.  First you mined a deadline into the pool.  The constantly updating box accepted it, you see your address and two numbers.  The first can be your payout, but wait.  Next block comes along, you submit new deadline and accepted.  After a couple blocks, the "All Round" box should show you and two numbers.  The first is, again, a potential payout.  BUT, these pools are not paying by the shift!  The one I use pays every 100 blocks or another criteria.  If I mine blocks 1 -90 and then stop mining, on block 90 my payout share may be listed as 200, but with each round that I am not there, it drops, a lot.  You are getting paid for your shares of the overall pie.  Like I said, the site I use it is 100 blocks.  You can come in late and do ok, but if you leave your numbers start dropping.  This is why it is bad to pool jump.  Start mining and stay there until the payout at least.  It looks complex and can be, but it is not that bad.

I was looking at Burst last night and found that when plotting, there are files that are placed above the plotted folder.

Well, first step would be to examine the flowchart found in the old BURST OP here https://bitcointalksearch.org/topic/annburst-burst-efficient-hdd-mining-new-123-fork-block-92000-731923 perhaps some things will be clearer then.

If you look closely at what data is used during mining you will find that all miners will mine the exact same set of deadlines for a given block height if they use the same plot to mine. This is what enables you to "move plots around".

You might wanna talk to Crowetic about that, he thought about establishing trust at great lengths.

AFAIK he still hasn't launched his cloud mining thingamajing

Some competition might be good for the both of you

that was my first thought.....i just don't want the software to take ownership of the drive is all

That is actually very cool.  I wonder if, rather than not using the drive space allocation functions of OpenVZ for nearly nothing, if you could use it to put files on the plotted drives that refer to the clients.

Honestly, I am not sure.  I do not think so.  I am not positive what data is held in that "plot".  I do know that if you are mining and get disconnected, reconnect quickly and the same block is there, you get the exact same set of deadlines.  Honestly, though it takes about the same amount of time to plot a drive as to move move those big chunks.