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

19 to go....

use this german guide and convert it with google translator

https://docs.google.com/document/d/1y0DNKX-tid-zUKronoivbXdC6vEzZpLh136dxizsnTM/mobilebasic

please help vith unix mine with you pool

i use pocminer_pool

what config i will use?

now have
[WARN] [05/17/2015 20:18:10.348] [default-akka.actor.default-dispatcher-4] [akka://default/user/$a/$b] null

Next 20 Miners will get 5000 Burst after one week activity.

Its not "local" wallet. Any reason for use this new wallet and advantages from it?

SSL added to Burst City's wallet!

Instead of:

http://wallet.burst.city:8125

use:

https://wallet.burst.city:8125

(i.e. use HTTPS instead of HTTP)

Surfbar idea is very nice , will try it immediately...

I tried it, works fine.

Due to low burst price you can now earn much easier burst than before. Simply by using the surfbar at http://burstcoin.eu/surfbar
Give it a try and get some burst

during the last couple of days several people send me a pm regarding the mysql blockchain copy i work on so i decided to make the access to it public.

the intended use for it is to have access to blockchain data within a mysql database to develop applications based on it.
since this tool currently is a php script which populates a mysql database with blockchain data by api queries to the wallet a normal user may not have any use for it since web developers get enabled to create content based on blockchain data in their known development environment  

here you get the mysql schema dump: http://pastebin.com/8f8ML2jE
here you get the php script to populuate the database with: http://pastebin.com/Kx7uyH7G

in the schema dump you may require to adjust the security definer if your mysql instance does not know the user root (on windows).
in the php script you have to adjust the db login variables to match to your database and maybe set the wallet address which is currently assumed to run on localhost.

if everything works like expected the php script console output shall look like this if startet:

wallet blockchain height: 99696
we start at block: 99690
tx ids: 17 block: 99691 scoop: 2976 target: 1573200 reward: 6302 miner: BURST-L2V2-AXNC-VW9G-9XBWM time: 24123845
tx ids: 8 block: 99692 scoop: 1053 target: 1497780 reward: 6302 miner: BURST-42JY-E6TZ-885E-AZ9HK time: 24124043
tx ids: 4 block: 99693 scoop: 1532 target: 1555930 reward: 6302 miner: BURST-3N7E-CX8T-K6AM-D6Q4N time: 24124285
tx ids: 1 block: 99694 scoop: 2652 target: 1685443 reward: 6302 miner: BURST-XWEZ-N5EH-ZBFU-3QBUD time: 24125064
tx ids: 0 block: 99695 scoop: 2636 target: 1718812 reward: 6302 miner: BURST-5YBX-W97K-PEHB-C4XPX time: 24125119

you may run the php script at any time but should make sure it gets only startet once.
at the moment there is no fork detection included.
so if your wallet runs on a fork and you have forked data in your db you have to manually truncate the tables above a certain height after switching back to the main chain. if anyone has a simple idea how to detect forks i can add this feature.

Now 46 Miners. I still need more miners. Give the pool a try!

Thank you for the explanation

Not correct!
As more nonces you send in, as more CHANCES you get to get an reward. It does not matter if the nonces are coming from one or multiple machines.

Compare it with a lottery ticket. As more lottery ticket you buy as more chances you get to be a winner.

In the pool each ticket is honoured, better said, the best ticket of each user is counted. So, if you have 100 miners, each one send in its nonces, but only the best will be counted. For 100 miners therefore a max of totally 100 tickets will be counted. The pool mined reward will be higher for 100 tickets, than just for 1 ticket, except you got the jackpot.

Now 46 Miners. Thank you all! I updated the Miner under howto mit the change in minerconfig "UseFastRcv" : false as blago recommend a few posts before.

this is a really interesting usecase about which i haven't thought in detail yet.

since the db already knows the timestamp of all blocks and has indexed access to all transactions including their types it should not be too complex to analyze the described actions which are visible on the blockchain.

for assets there may be some additional information required (like the used account for dividend payouts) but with some additional coding this sounds absolutely possible.

regarding a detailed mining pool analysis i am not sure because the blockchain does know nothing about submitted nonces.
a report would be limited to what a pool payed out and how many blocks with set reward recipient were mined (in total or for a specific miner and timeframe).
this analyis can already be done with the data the database already knows about (for performance reasons maybe some cached results may be useful).

i will send you a pm with further information regarding this analysis methods and which queries have to be developed.
 

i think we are near the end...

just look at the long term trend...

i think it is clear..

although I hope that will soon change anything.

A single machine is better, because you're working off the nonces in the files. The more nonces you have, the larger the rewards.

hello,

i think there is no difference between both systems.

but im not 100% sure, so maybe someone with more knowledge than me can reply.

btw i think you are new into burst communuty, so welcome!

Hello friends,
it is better to benefit from a series of different machines in a pool 3x connection to the pool or the proxy miter in the pool connected only once?

Can this be used to analyse assets in an automated way ? Or Mining-Pools ?

There are mining-related assets with variable proceeds that are totally opaque - if the issuer doesn't publish any calculations, and even then, it is impossible to verify the validity and performance.

Same is true (mostly) for (most) pools.

Having an automated reporting system would allow us to actually verify such complex things as a mining pool performance and asset performance.