Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 147. (Read 409641 times)

or a bunch of FPGAs they have to be somewhere.

or he has asic :p

wow this icaras dude on the pool must really believe in blc, he's got 40gh/s on it! thats gotta be like 15 7970s

no problem 

BlueDragon747, thanks for explaining the time zone thing, makes sense now. 

As humans we have time zones but to computers its all system time and the wallet uses this to set its clock(global time stamp) your wallet or the other nodes are then checked to be only so many minutes out from your system time

why is it used?

its designed as an anti cheat/hack method to stop people from forging time stamps and submitting large chains etc.. (supposed to be only for time advancement but seems to effect negative time zones too)

why does it show more in newer coins?

smaller networks more time difference between nodes

e.g if a guy in South America had a wallet and I was the only node here in the UK then the direct time difference would be larger than if I had 100 nodes between him and me as the time difference between nodes would be less

best thing to do is set your timezone to UTC/GMT on the machine hosting the wallet (true for any coin based on Bitcoin)

In other news I have finished my EU pool and it will be released this weekend had some issues with the pymysql library locking/crashing mysql so have swapped it for cymysql and hope that fixes the issue, need to make some changes to the install script if cymysql is working fine as it was a pain to get it installed in python3  

Edit:
One thing I did not mention for the mining orphans I think this is an issue with negative timestamp received, when other nodes get your block they are checking for a later timestamp than the previous block, a few other things going on as well but it makes sense to have a time window for a machine but for us we want daylight unless we have been up all night programming

it doesn't have to do exclusively with solo mining. even if the wallet is just running it may stop
updating the blockchain. i 've seen this with other scrypt coins too!

How much is the cryptsy bribe these days?

Are you solo Mining? This seems to happen if your PC is not on UTC time and you solo mine.

You can join a pool or set timezone on you PC to UTC/0GMT or set a timer to turn Wallet off then back on every 2 hrs or so.

I'm having a problem, my wallet won't update automatically. So I have to restart my computer or close & reopen the wallet to update the wallet.

looks like no one really uses that exchange yet, but any exchange is better than none to start with. From their twitter it seems the site only went live within the past few days. However I've listed some blc for sale there just in case. It looks like a good site though, I'm glad it's open source. If we all start using it to trade blakecoin, perhaps we can give openex some credibility.

Not quite such a good job. I've now worked out why my initial 1.15x bitstream was broken. I was using an experimental 4 core pipeline instead of the 2 core pipeline (the offsets are different since the nonce is distributed by LSB rather than MSB). My fault, its been a while since I worked on the verilog and I just copied what I thought was current rather than taking the actual code used from the github, so I used work-in-progress rather than verified code. I've updated the github now, the 1.15x and 1.15y pipelines should now be identical.

I think you are doing a terrific job!

I forgot to mention that in order to run N builds in parallel on the same machine you have to add this machine N times to the host file (on Linux). You can use "localhost".

Thanks. I'm just an amateur hacker on ISE, so any advice from the pro's is most welcome

Hal7's 1.15x bitstream is now hosted on dropbox (link to README)

BLC on exchange.

https://openex.pw/index.php?page=trade&market=6

You can configure the number of parallel runs in SmartXplorer in the "Launch SmartXplorer" dialog:

- On Windows: set the "Number of parallel runs on this machine"
- On Linux: for each run, add a host to host list file

See http://www.xilinx.com/support/documentation/sw_manuals/xilinx14_7/ise_c_using_smartxplorer.htm, "To Run SmartXplorer from Project Navigator", items 3 and 4.

The constraints could do with a bit of expert attention. I changed it from Stefan's original code at around the time I dropped the second PLL. It just made more sense to me to constrain the DCM output rather then the osc input, that way its easier to tweak the clock value to optimize the FMAX (the DCM multiplier is dynamically configured at runtime). The general procedure I use is to gradually increase TS_clk while tweaking the PAR -t parameter for multiple builds until I get fed up with the entire procedure. I suppose SmartExplorer would be the professional approach to this, but it seems to be designed for use with a farm of build machines (the one time I tried it, it fired off four parallel builds and thrashed my poor little machine).

I've posted some code up on the github (link). The bitstream I created upthread used a modified version (delete core M2, remove the phase switch logic) but these are fairly trivial changes (I ought to configure it with `ifdef but this was just a quick'n'dirty hack to get something built in a sensible timeframe).

Best of luck with ISE, you'll need it 

I have another pool working but needs some tweaks to the mpos front end as all the dashboard graphs and hash rates are not displayed correctly but shares and payouts are working

I have also done/tweaked some install/run scripts for ubuntu 12.04 which helps running a private/public pool

hope to have some releases for this weekend, if I am not about as much over next few days its just me finishing this work off 

There should be a api method sendmany. You can check the bitcoin api documentation for the format. Its also listed when typing "help" into the debug console. I am assuming it works.

Thanks for hints. Indeed select logic is different, and three or four other lines need small changes.

I've succesfully compiled cgminer 3.1.1 with your patched sources under Debian 6, good work!:) ; it can detect and work with 1.15x board, but of course it is doing HW only because of original ztex bitstream... but it sends work:). I've started doing changes to original 1.15d4 verilog code. Wasn't so hard and even synthezises. But how did you constrained TIMESPEC clk PERIOD? From where did you get 100MHz 50%? NET fxclk_in is driven by 48MHz from Cypress FX2.

Now waiting to implement design.. hours or days with Smartxplorer...
tuned: resource sharing off, register duplication on, equvalent register removal off, register balancing yes