[YAC]: YaCoin Information Thread

[rbdrbd]

All updated.

[1714153276]

1714153276

[fishboy]

Please add this faucet:
http://yac-faucet.tk/

nice faucet very unique

[bitdwarf]

I've written a throttling script for Linux to tune down yacoin-qt when core temperature is too high:

Thread: http://yacointalk.com/index.php/topic,34.0.html

Code:

Code:

#!/bin/bash
while true
do
	t=$(sensors|grep Core|awk '{print $3}'|cut -b2,3|awk '{if (NR==1) print $1}');
	brake=$(ps -e|grep cpulimit);
	if [[ $t > 65 && ! $brake ]]; then
		cpulimit -e yacoin-qt -l 99 -b > /dev/null 2>&1;
		echo "Temperature is $t. Throttling down...";
		sleep 15;
	elif [[ $t < 65 && $brake ]]; then
		killall cpulimit;
		echo "Temperature is $t. Throttling up...";
		sleep 5;
	else
		sleep 3;
	fi
done

You may need to install first cpulimit.

When you finish it with Ctrl+C it may leave cpulimit running, you'll have to kill it afterwards.

Modifications are welcome.

[biaka]

Please add this faucet:
http://yac-faucet.tk/

Done~

[jomay]

I was under the impression PPCoin's PoS was not really working yet, and that nobody else had done any development on it...

Update after reading some code:

• Nfactor is only used for memory allocation size - so it has no actual effect on the implementation; in other words, N is not dynamic
• The code is quite messy, and even something as simple as the memory allocator is broken (it pretty much ignores the size of the allocation request)

I think this one gets a "scamcoin" classification...

Luke-Jr, interesting comment. I had a brief go at the code as well, but can't confirm your findings. Maybe you were a bit quick shouting "scamcoin", eh?

• Yes, the scrypt codebase is ugly. #define's and #ifdefs everywhere. Is this a copy of the original scrypt?
• The scrypt romix code in scrypt-jane-romix-template.h (function called SCRYPT_ROMIX_FN) does use N (i.e. Nfactor) looping from 1 to N, in addition to increasing the mem size by N. I don't know enough about the underlying crypto, but I believe complexity scales at least by O(N²).
• The allocate and free methods are totally fine. You have tripped over an #ifdef:
  

Code:

#if defined(SCRYPT_TEST_SPEED)
// jomay: I left out the test code - this is the one you've read.
// It works fine in practice as well, but makes the scrypt() function non re-entrant.
#else
// jomay: here goes the real deal - fully functional, no mem leak, fine.
static scrypt_aligned_alloc scrypt_alloc(uint64_t size) {
    static const size_t max_alloc = (size_t)-1;
    scrypt_aligned_alloc aa;
    size += (SCRYPT_BLOCK_BYTES - 1);
    if (size > max_alloc)
        scrypt_fatal_error("scrypt: not enough address space on this CPU to allocate required memory");
    aa.mem = (uint8_t *)malloc((size_t)size);
    aa.ptr = (uint8_t *)(((size_t)aa.mem + (SCRYPT_BLOCK_BYTES - 1)) & ~(SCRYPT_BLOCK_BYTES - 1));
    if (!aa.mem)
        scrypt_fatal_error("scrypt: out of memory");
    return aa;
}

static void scrypt_free(scrypt_aligned_alloc *aa) {
    free(aa->mem);
}
#endif

[/li][/list]

[saudibull]

A lot of pumpin and dumpin going on at bter...

[Luke-Jr]

I was under the impression PPCoin's PoS was not really working yet, and that nobody else had done any development on it...

Update after reading some code:

• Nfactor is only used for memory allocation size - so it has no actual effect on the implementation; in other words, N is not dynamic
• The code is quite messy, and even something as simple as the memory allocator is broken (it pretty much ignores the size of the allocation request)

I think this one gets a "scamcoin" classification...

Luke-Jr, interesting comment. I had a brief go at the code as well, but can't confirm your findings. Maybe you were a bit quick shouting "scamcoin", eh?

• Yes, the scrypt codebase is ugly. #define's and #ifdefs everywhere. Is this a copy of the original scrypt?
• The scrypt romix code in scrypt-jane-romix-template.h (function called SCRYPT_ROMIX_FN) does use N (i.e. Nfactor) looping from 1 to N, in addition to increasing the mem size by N. I don't know enough about the underlying crypto, but I believe complexity scales at least by O(N²).
• The allocate and free methods are totally fine. You have tripped over an #ifdef:
  

Code:

#if defined(SCRYPT_TEST_SPEED)
// jomay: I left out the test code - this is the one you've read.
// It works fine in practice as well, but makes the scrypt() function non re-entrant.
#else
// jomay: here goes the real deal - fully functional, no mem leak, fine.
static scrypt_aligned_alloc scrypt_alloc(uint64_t size) {
    static const size_t max_alloc = (size_t)-1;
    scrypt_aligned_alloc aa;
    size += (SCRYPT_BLOCK_BYTES - 1);
    if (size > max_alloc)
        scrypt_fatal_error("scrypt: not enough address space on this CPU to allocate required memory");
    aa.mem = (uint8_t *)malloc((size_t)size);
    aa.ptr = (uint8_t *)(((size_t)aa.mem + (SCRYPT_BLOCK_BYTES - 1)) & ~(SCRYPT_BLOCK_BYTES - 1));
    if (!aa.mem)
        scrypt_fatal_error("scrypt: out of memory");
    return aa;
}

static void scrypt_free(scrypt_aligned_alloc *aa) {
    free(aa->mem);
}
#endif

This isn't the code I saw (yacoin's github master branch).
Where did it come from?

[jomay]

I was under the impression PPCoin's PoS was not really working yet, and that nobody else had done any development on it...

Update after reading some code:

• Nfactor is only used for memory allocation size - so it has no actual effect on the implementation; in other words, N is not dynamic
• The code is quite messy, and even something as simple as the memory allocator is broken (it pretty much ignores the size of the allocation request)

I think this one gets a "scamcoin" classification...

Luke-Jr, interesting comment. I had a brief go at the code as well, but can't confirm your findings. Maybe you were a bit quick shouting "scamcoin", eh?

• Yes, the scrypt codebase is ugly. #define's and #ifdefs everywhere. Is this a copy of the original scrypt?
• The scrypt romix code in scrypt-jane-romix-template.h (function called SCRYPT_ROMIX_FN) does use N (i.e. Nfactor) looping from 1 to N, in addition to increasing the mem size by N. I don't know enough about the underlying crypto, but I believe complexity scales at least by O(N²).
• The allocate and free methods are totally fine. You have tripped over an #ifdef:
  

Code:

#if defined(SCRYPT_TEST_SPEED)
// jomay: I left out the test code - this is the one you've read.
// It works fine in practice as well, but makes the scrypt() function non re-entrant.
#else
// jomay: here goes the real deal - fully functional, no mem leak, fine.
static scrypt_aligned_alloc scrypt_alloc(uint64_t size) {
    static const size_t max_alloc = (size_t)-1;
    scrypt_aligned_alloc aa;
    size += (SCRYPT_BLOCK_BYTES - 1);
    if (size > max_alloc)
        scrypt_fatal_error("scrypt: not enough address space on this CPU to allocate required memory");
    aa.mem = (uint8_t *)malloc((size_t)size);
    aa.ptr = (uint8_t *)(((size_t)aa.mem + (SCRYPT_BLOCK_BYTES - 1)) & ~(SCRYPT_BLOCK_BYTES - 1));
    if (!aa.mem)
        scrypt_fatal_error("scrypt: out of memory");
    return aa;
}

static void scrypt_free(scrypt_aligned_alloc *aa) {
    free(aa->mem);
}
#endif

This isn't the code I saw (yacoin's github master branch).
Where did it come from?

YACoins scrypt-jane master branch: https://github.com/pocopoco/yacoin/blob/master/src/scrypt-jane/

scrypt_alloc is at lines 86-129. As clearly stated above, the posted code simply leaves out the SCRYPT_TEST_SPEED #ifdef branch: https://github.com/pocopoco/yacoin/blob/master/src/scrypt-jane/scrypt-jane.c

SCRYPT_ROMIX_FN is defined here: https://github.com/pocopoco/yacoin/blob/master/src/scrypt-jane/code/scrypt-jane-romix-template.h

Where did you look at?

[Shevek]

Yet Another cryptocoin that does not address the main problem of bitcoin: the recentralization via pools.

A lot of effort to discourage GPUs and ASICs, but pools are still an option.

Bad, bad, bad...

[sairon]

Yet Another cryptocoin that does not address the main problem of bitcoin: the recentralization via pools.

A lot of effort to discourage GPUs and ASICs, but pools are still an option.

Bad, bad, bad...

I don't see any problem with pools, especially if it's p2pool.

[frediiii]

I don't see any problem with pools

in a world without profit and greed I wouldn't see a problem as well...

[ehmdjii]

is there a mining pool that works over port 80?

[Shevek]

Yet Another cryptocoin that does not address the main problem of bitcoin: the recentralization via pools.

A lot of effort to discourage GPUs and ASICs, but pools are still an option.

Bad, bad, bad...

I don't see any problem with pools,

Pools are ways to recentralize a distributed network. Instead of a lot of independent nodes, you have a few of important nodes, easily attackable.

See what happens in BTC with BTCGuild and later with DeepBit.

especially if it's p2pool.

A significative advance of YAC would have been a reward system that internally acts as p2pool does. If p2pool is only an option among others (these eventually more attractive because of less variance), it is no advance towards avoiding recentralization.

[Luke-Jr]

Yet Another cryptocoin that does not address the main problem of bitcoin: the recentralization via pools.

A lot of effort to discourage GPUs and ASICs, but pools are still an option.

Bad, bad, bad...

And how would you fix that? There is no way to prevent 3rd parties from pointing hashpower to one node and use that node as miner connected to network.

Something similar to p2pool (but not exactly) could be integrated to Bitcoin in such a way that it makes centralized pooling infeasable.

[Shevek]

Yet Another cryptocoin that does not address the main problem of bitcoin: the recentralization via pools.

A lot of effort to discourage GPUs and ASICs, but pools are still an option.

Bad, bad, bad...

And how would you fix that? There is no way to prevent 3rd parties from pointing hashpower to one node and use that node as miner connected to network.

I follow this subforum, with the hope a new cryptocurrency comes with a solution to this matter, which would be IMHO a major break in crytocurrency development. But no chance...

In fact, I have my own ideas on how design a new CC with PoW where parallelization AND pools are severely discouraged. Perhaps in other thread.

Any sort of pool is centralization point. If I connect to P2Pool, my miner depends on data sent by that pool so I don't see where is the "improved decentralization" part of story.

You didn't catch the idea behind p2pool, did you? p2pool is a network of nodes, not a central server to where you call for getwork and send shares.

[rbdrbd]

OP updated. Added pool http://yac.ltcoin.net

[relm9]

OP updated. Added pool http://yac.ltcoin.net

No, no, no, don't do it! Guy behind the pool is a proven scammer!

Yep, I remember his FTC pool that never paid out.

[rbdrbd]

OP updated. Added pool http://yac.ltcoin.net

No, no, no, don't do it! Guy behind the pool is a proven scammer!

Yep, I remember his FTC pool that never paid out.

Thanks, I removed this pool. Also added the first p2pool.

[cebb]

Where can i find Network hashrate for YAcoin?

[leadnor]

I have to say I ran yac.ltc pool for a day and he did manage to pay me out.