Topic: [ANN] [SHA256]+[CPU] MediterraneanCoin (MED) - REUSE your ERUPTER!! - page 103. (Read 227779 times)

Oh, so its not just the little stuff? So this could get as silly as other SHA coins are atm?

10 connections, you mean? well, it is not operating at full, but it should allow to sync your blockchain.

Not related to your question: what kind of ASIC are you using?

ummmmm I got 10, is it normal?

I think that every ASIC hardware can be used but it needs some additional setup. Here's a guide for CUBE miner, I'm sure you can easily adapt it for Antminer: http://altcoins.com/mediterraneancoin-med-blockerupter-cube-mining.html

Can an AntMiner be used for this?

what is you MediterraneanCoin address?

how many connections does your wallet have currently?

some additional nodes could help:

162.243.18.169
95.85.43.185
162.243.224.22
162.243.222.173

*hybrid

Kinda slow catching up to the chain

yes, as it is, it seems that the chip BTC hardware implementation would not be so dangerous to HybridScryptHash256 PoW.

 

Well at least we know now that there won't be any major hashrate disruptions through massive use of that chip.

it looks like that this hybrid hashing chip supports Scrypt for LTC, its PoW uses Scrypt in a single configuration (1024,1,1) while HybridScryptHash256 needs many more Scrypt configurations.

So the LTC implementation part of the chip would be surely not compatible with HybridScryptHash256.
Instead, the BTC hardware could by integrated quite well.

It could be interesting to develop a hybrid hardware, a BTC chip + a very fast ARM/RISC dedicated to Scrypt on the same die; this could be very interesting.

No, we have not yet partnered up with some chip developers. Do you have links?

Will you developers support this hybrid hashing chip? Any chance you already partnered up with chip developers? Are you actualy
chip developers as well as altcoin developers?

https://bitcointalksearch.org/topic/gridseed-gc3355-hybrid-scryptsha256-asic-355268

hi,
regarding the win32 build, the installer is part of the automatic gitian build; there is an error with the icons (from litecoin tree) and that is being fixed, so the next builds will have this aspect corrected.

We choose to go with the gitian builds because it's a very good build process and safe for the end-users since it can be replicated by anyone; the resulting binaries obtained with the gitian build should be exactly the same, bit for bit.

You are right, the resulting archive with the installer is quite large; in the future we might separate the installer from the rest in order to save some space. Also there is an issue with the naming of the installer (it is not being updated correctly during the gitian build), we will have to look into that.


Regarding how networkhashps is calculated, the function calculates the average in the same way as Litecoin does;

basically it does this:

    uint256 workDiff = pb->nChainWork - pb0->nChainWork;
    int64 timeDiff = maxTime - minTime;

    return (boost::int64_t)(workDiff.getdouble() / timeDiff);

simplifying a lot what the code does,  pb is (usually) the current block, and pb0 is the block we want to compare to (its index calculated by the formula 'lookup = pb->nHeight % 2016 + 1' that is the time diff of about 1.4 days in case of constant difficulty ).


also the rpc command for getting the networkhash supports two optional parameters:

getnetworkhashps [blocks] [height]

so one can calculate the networkhashps specifying from which block (height) you want to start the estimate, and then of how many blocks you want to go back.

BTW, there is MED giveaway still going on at https://bitcointalksearch.org/topic/giveaway-med-altcoin-using-unique-hybrid-sha256-scrypt-hashing-398948 so if major miners feel like
sending some coins to newcomers that would be great. You can find people addresses on giveaway thread, some are not
valid and thus will make your address field in MED wallet turn red upon attempting to send coins. I've sent coins to almost
everyone who asked for them and received 200 MED from developers (that is still more coins than spread out over giveaway)
so there is no need to send any coins to me.

Thanks in advance!

I've upgraded the wallet, it is working fine. Question I have is why you are adding setup for wallet to archive? It makes archive
noticably bigger but question is if anyone is actualy using setup to install MED wallet. Also, judging by file name it seems that
it installs older version of MED wallet (mediterraneancoin-0.8.5.1-win32-setup.exe).


What formula are you using to calculate approximate hashrate? The one I'm using is (diff * 2^32 / 60) and it says that hashrate
was around 100 GHash. Command getmininginfo returns similar number:

16:20:39

getmininginfo

16:20:39

{
"blocks" : 9030,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1395.64443691,
"errors" : "",
"networkhashps" : 98762175563,
"pooledtx" : 0,
"testnet" : false
}

hi all,

we have been mining successfully with a modified bfgminer for supporting MediterraneanCoin and HybridScryptHash256 PoW, it seems to work well, as the modified cgminer.

Source code is available here: https://github.com/mrtexaznl/bfgminer


under Linux Debian with USB Block Erupters, we use a command like this:

sudo ./bfgminer --submit-stale -o http://localhost:8080 -u admin -p password -Q 0 -S all

I haven't seen a java exception error since compiling the mediterraneancoind from the new github repository. Looks good!

For historical purposes, I'm seeing the following stats as of 10:50pm CST:

Difficulty: 1435.93694438,
Blocks: 8440,
Network speed: 121.805 gh/s

hi all,
we have uploaded on github a new gitian build for both linux and win32:

https://github.com/mrtexaznl/mediterraneancoin/releases/tag/v0.8.5.1-1

https://github.com/mrtexaznl/mediterraneancoin/releases/download/v0.8.5.1-1/medcoin-linux-v0.8.5.1-1.tgz

https://github.com/mrtexaznl/mediterraneancoin/releases/download/v0.8.5.1-1/medcoin-win32-v0.8.5.1-1.tgz

this should reduce the number of java exceptions (caused by wallet-qt blocking when receiving long getblocks requests from peer).

Been mining with one BE for past few days, first 24 hours i was finding a block every 2-3 hours, now its gone up to average 3-5 hours.  Its something interesting to try and if not for MED, my BE would be just lying around doing nothing.

I had some of those errors earlier, i found restarting proxy/cgminer seem fix it temporarily,  also I found more blocks when my computer was idle so better results probably if u used a separate laptop etc for it so CPU is not being shared with other stuff. 

using the the win7/32 bit versions/cgminer that were posted on website for this.