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

Just to let you know, I'm still getting the same issue with the new wallet, however when mining on the pool I'm getting a long query time so I think there may be a network problem somewhere at my end. New wallet appears fine apart from that.

hey kramble & BD, thanks for your help, i finally got the icarus sorted out. after seeing the pic of the circuit board from your dlc9 BD, i realized the one i had was definitely a total knockoff so i got an official dlc10. boundary scan worked flawlessly after that, so a word of advice for other people interested in fpgas, dont skimp on the programmer cable ;-) but there was one more roadblock, i was using version 14.2 of ise which turns out to have a bug where it doesnt detect the spi prom correctly. after updating to version 14.7 of ise everything worked as it should. the upside to having these obstacles happening was that i ended up learning way more about fpgas and jtag than necessary while troubleshooting :-) ill be incorporating what i learned into the next update to my Blakecoin Introduction.

Thank you for playing, your withdrawal was processed.

I forgot to mention, if you kill a target who's wallet is empty or does not have enough coin to take you will not receive any coin, and they will not lose any coins and will not go negative wallet.

If you see the error in chat:
There was an error loading your wallet, please try re-connecting to the server.

Reconnect to the server and if it still fails, call an admin with the /calladmin command.

Definitely, big things like that should come first

Can't wait for the FPS!

BLC is a great hidden gem right now

this is perfect thanks for adding this  


sent some donations hope it helps keep things running  

I am now applying a patch to the explorers on CCE (www.cryptocoinexplorer.com).

I have applied it the Blakecoin explorer.

Quick rundown of changes:

The "block" webpage now accepts both block height and block-hash in the URL.

Examples:

http://blc.cryptocoinexplorer.com/block/96537

http://blc.cryptocoinexplorer.com/block/00000000000424f9b55dd2a45d4a0d6d66677eda4feb364420f04aecd696668b

Both the block webpage and block API will now trim much of the redundant address and transaction information. The block webpage will merge duplicate addresses that are next to each other in a single transaction and present a sum of the values. The block API now trims out duplicate transaction entries.

Miner_fee flag added. This flag determines if fee value is shown with coinbase value to accommodate chains that destroy fees instead of passing them to the block finder.

Hopefully this is the end of the immediate technical needs. I hope to get started on cosmetic issues next.  

That is awesome.. I call Long Hall in the office map

Awesome looks cool I remember playing dust quite a bit

Speaking of games, I've launched a Blakecoin based Counter-Strike 1.6 server.
The traditional CS currency system has been replaced. When a new user enters the server they are given 1 BLC to get started. The server supports the depositing and withdrawal of Blakecoins. Blakecoins deposited are placed into the players wallet in the game. Players may set a BLC withdrawal address in game, and request withdrawals to that address. There are currently bots running around with fat wallets and low difficulty settings. The bots leave the server when enough players have joined (set to 8 currently). When only 2 players remain alive on oppossing teams dead players are presented with a menu which allows them to bet BLC on which player will win the round. There is also a bounty system, where players can place a BLC bounty on another players head. The person who kills the target first will receive the bounty.

Currently bonuses are given out to players who complete game objectives, such as:
1 BLC bonus for planting the bomb
1 BLC bonus for the bomb exploding
2 BLC bonus for defusing the bomb

A variety of other bonuses are enabled from time to time, such as a bonus for the first,second, and third killer in the round. Round Win bonuses, etc...

When you kill a player you receive 1 BLC, the victim LOSES 1 BLC.
When you kill a player with a headshot you receive 2 BLC, the victim LOSES 2 BLC.
When you kill a player with an HE Grenade you receive 2 BLC, the victim LOSES 2 BLC.
When you kill a player with a knife you receive 3 BLC, the victim LOSES 3 BLC.
If you are killed you LOSE coins per the above. The coins are taken from your wallet balance. You have been warned Of course, this also opens up the possibility to profit from game play.

Owners of Counter-Strike 1.6 can test the server: 207.210.117.83:27015
Helpful commands:
blc_help
rank
/guns
/bounty
/calladmin

Screenshot, Blakecoin logo's added to a few maps. Some original BLC logos and some by bzyzny (nice work).

Please note, no coins are actually stored on the server at that IP

the next thing on my list after the merge mining pools are release this coming weekend is to concentrate on the MMO games and to get the information for the FPS public with some videos of the game play, other things like website are secondary and minor compared with the main goals of why I made BLC is the first place 

"Already has planned use for Blakecoin as a currency storage between MMO systems with prototypes in development"  

Awesome thank you, everything working fine so far. Going to send a couple BLC just to test it out. I've been looking at the site/logo a lot lately and i think it could use a bit of sprucing up. Is there any plans for that? I'd gladly help with some other behind the scenes small tasks if you want

I see what you are saying. Actually it would not be that hard to implement, I was under the thought that somebody using the website and not the API would be much more likely to have a height then a blockhash.

I will implement it in the next patch.

I think its good just saying when input into MPOS which currently uses the blockhash and not the height to call the link to the block e.g http://blc.cryptocoinexplorer.com/api/blockhash/ and http://blc.cryptocoinexplorer.com/api/block/ unformatted output vs http://blc.cryptocoinexplorer.com/block/ which is formatted it would be perfect if you could add a formatted version for the blockhash as well if you see what I mean?

here is the old CCE calls I was using in MPOS
http://blc.cryptocoinexplorer.com/block/
http://blc.cryptocoinexplorer.com/tx/

like I said I need to change the calls to fit your api its good work though and I do like it  

The API output was improved and made uniform a couple of patches ago. There have been a number of improvements since then.

For example:
http://blc.cryptocoinexplorer.com/api/block/96175

Returns:



http://blc.cryptocoinexplorer.com/api/blockhash/00000000000296d92dd664ee090056c50d0e0b8c5825741a259061b92e634b6e

Returns:


I have been pulling all-niters to get the API patched up and in proper working order. I hope it meets with expectations.  

great work 

I noticed when using /api/blockhash/ the returned result is unformated compared with /block/ also the default MPOS does not handle the /api/tx/ well guess I need to make some changes to MPOS to handle this new api 

FYI:

The testing phase of CCE3 is complete and CCE3 is now in production on www.cryptocoinexplorer.com.

This means the testing address blake.cryptocoinexplorer.com is no longer valid and the main address blc.cryptocoinexplorer.com is the active address.

I started a new CCE thread when the conversion took place and locked all the old threads. The current CCE thread is: https://bitcointalksearch.org/topic/cryptocoinexplorer-one-of-the-original-alt-coin-explorer-sites-584847

CCE3 has a very efficient and easy to use API. Instructions can be found here: http://www.cryptocoinexplorer.com/api.html

BlueDragon747 has a key to use the new developers message box feature not seen on any other explorer site.

If you have not been on CCE lately, give it a look, many things have changed over the last few weeks.  

yes the pool is working but needs another patch to Photon and to make sure the block explorer and exchanges have updated before I go public

settings for pool will be as follows:

fixed diff 32 shares (avoids mpos graph bug)
fixed 1.5% fees for both coins
PPLNS payout for both coins

*not going to rush any release as its best to make sure everyone is on new version before merge mining due to the needed patches

I do appreciate everyone's patience with this it has taken quite a while to get right so far and I found more bugs than I initially expected  

Thanks, will try and let you know how it goes.

Any update on merged mining?

sounds like the boost bug, 0.8.9.0 was built with boost 1.54 and it has a known network connection bug in the library

here is a qt build I did on the weekend with boost 1.55 and openssl 1.0.1g
http://blakecoin.org/Blakecoin-0.8.9-WIN-boost-1.55.7z

backup you wallet beforehand and please report any issues

Edit:
if you are still getting the issue after then it might just be hash flooding e.g too many diff 1 shares for wallet to solve

best thing to do in this case is to either split the solo mining between several wallets or use Eloipool as a private pool e.g no front end or db