[ANN][YAC] YACoin ongoing development

[Beave162]

...
To get more people/computers involved in YAC or any crypto-currency, including BTC, one needs to go after the biggest audience.  See http://www.netmarketshare.com/ and in "Market Share Reports" near the top, choose "Operating Systems", then "Desktop Share by Version".

OK, what wins with ~92% of all desktops connected to the internet?  That is what one should target!  That is why I did my videos (https://www.youtube.com/channel/UCytoaHvG3H1y9CnxZS819eQ), showing how easy it is to make a Windows version of YAC, BTC, etc.  Of course the latest version of BTC, roughly versions 9.x, 10.x, 11.x and any other *coin derived from them, now obscure the make file inside autogen machinery,  making it more difficult to tease out the minimum set of files needed to create a *coind.exe &/or *coin-qt.exe

I prefer to work with Bitcoin 0.8.6 and *coins derived from that version or older, since there was much less "confusion" about which version of gcc, which version of Qt, which version of levelDB, which version of OpenSSL (now there's a deep hole!), UPnP, QRencode,... and who knows how many more with the latest versions of Bitcoin?  Boost?, gcc?, Qt?, GMP, secp256k1, etc. etc. etc.

All with no specifications given about which version works, or doesn't, with which older or newer versions?  I tried making this argument on various bitcoin foums, but to no avail  I think there are just too many Linux geeks that are burned out looking at too many text mode screens!  I did that in the 1970s and 1980s in CPM/ZCPM and DOS (LOL).  Don't mind a good .bat file here and there to ease building a Windows gcc daemon or Qt version

Ron

I did not thank you yet for those videos - very helpful indeed. I am one of windows guys (but I strive to make portable code), and I must confess successfully compiling yacoin daemon under Visual Studio was a special event.
I hope the same will be possible with version 4.5.

Ron,
You may be the biggest motivator for me to help and promote YAC. I'm very glad you are a YAC stakeholder to say the least.

I see a multi-prong attack, if you will. I see YAC being able to bolster crypto as a whole and even compete with Bitcoin in reaching out to people by having
1) 'Cleaner', less convoluted code (as you refer to) to bring in coding enthusiasts
2) More user-friendly, easy-to-use mining tools as ThirtyBird has already done so much for to bring in blockchain transaction processors (aka miners)--not to mention feeleep with coinmine and now NineEleven stepping up too.
3) Old-fashioned promoting, marketing to get people to invest in YAC as a long-term commodity and eventually a full-fledged, accepted currency.

I think a fundamental backbone behind it all is the security of the network and associated expectations. I have thrown out the concept of a 2-min block time as a potential fix, but alenevaa is completely against it, Joe_Bauers is against it, and senj, ThirtyBird, old c coder seem to have no opinion either way, so it clearly won't happen. It was just an idea to throw out there, and it has been addressed sufficiently I think. This recent attack has shown that 1) someone or some persons have access to large (relative) amounts of resources and has an awareness/interest in YAC 2) YAC needs more stakeholders to mine more or just needs more miners in general. The attack is sort of a 'badge of honor' and a good sign that the 'strength through adversity' concept is at work as previous mentioned.

As very constructive points and playing devil's advocate, I'd expect that if I have 5%-10% of the entire network hashrate, I wouldn't have an orphan problem. I'd also expect that if the blockchain is full of PoW block after PoW block, it shouldn't take 40+ days for a 2000 YAC ("highest" priority if that means anything) input to stake. If I'm ignorant of certain details by saying that, those details are too complicated and/or not transparent enough.

senj, I understand your upcoming changes will address those expectations--thank you so much. And I'm very much looking forward to the new wallet release. I think many in crypto will be blown away by some of the features--Joe_Bauers, old c coder, Groko, senj.  

[1715262989]

1715262989

[1715262989]

1715262989

[1715262989]

1715262989

[1715262989]

1715262989

[1715262989]

1715262989

[NineEleven]

i need you help

this error
2015-07-04 02:13:06 [Pool]   [yacoin] (Thread 1) We thought a block was found but it was rejected by the daemon, share data: {"job":"1","ip":"10.0.22.59","port":3032,"worker":"YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH","height":1125098,"blockReward":76320000,"difficulty":1,"shareDiff":"421.15416530","blockDiff":80.983556096,"blockDiffActual":0.001235711,"blockHash":"24fbc4370213e36f251dc2f1535f6eb9b1144c7b07f143be850d7b8ff35d12df"}

mens blosk is FOUND, is on the wallet but not in NOMP for payment
 
I have 4 block in the wallet

waht could be the problem?

[Qxw]

Please try

http://yac.erlog.pt:81/


I think everithing is working

I have turned on two small miners. Hashing works ok but we need more miners (minerd with i7 CPU and cudaminer with some Nvidia GPU.)
Settings are really easy for CPU miner (minerd) or cudaminer. I have not yet tested Yacminer with this pool (amd gpu).

But why this (difficulty)

Username:your yacoin wallet address
Password:anything (what ever)
Algorithm:scrypt-jane
URL (difficulty 4):stratum+tcp://193.136.97.30:3032

Why fixed difficult 4?   My opinion is that it is far too high but for yacminer users it can not be under 1 so this is why most pools (UTC, YAC) use fixed 1 for yacminers.
(or arrange least one port for fixed 1)

[markm]

Please try

http://yac.erlog.pt:81/


I think everithing is working

I have turned on two small miners. Hashing works ok but we need more miners (minerd with i7 CPU and cudaminer with some Nvidia GPU.)
Settings are really easy for CPU miner (minerd) or cudaminer. I have not yet tested Yacminer with this pool (amd gpu).

But why this (difficulty)

Username:your yacoin wallet address
Password:anything (what ever)
Algorithm:scrypt-jane
URL (difficulty 4):stratum+tcp://193.136.97.30:3032

Why fixed difficult 4?   My opinion is that it is far too high but for yacminer users it can not be under 1 so this is why most pools (UTC, YAC) use fixed 1 for yacminers.
(or arrange least one port for fixed 1)

Why does what you posted say "Algorithm:scrypt-jane", while the first post of this thread says "Proof of Work: Scrypt-N SHA-3" ?

What algorithm or algorithms does this coin actually use? Has it changed since the first post of the thread without that post being updated accordingly?

-MarkM-

[NineEleven]

My friends I was using an old version of nomp

Change to new version

let's see if this time is ok

[Qxw]

Please try

http://yac.erlog.pt:81/


I think everithing is working

I have turned on two small miners. Hashing works ok but we need more miners (minerd with i7 CPU and cudaminer with some Nvidia GPU.)
Settings are really easy for CPU miner (minerd) or cudaminer. I have not yet tested Yacminer with this pool (amd gpu).

But why this (difficulty)

Username:your yacoin wallet address
Password:anything (what ever)
Algorithm:scrypt-jane
URL (difficulty 4):stratum+tcp://193.136.97.30:3032

Why fixed difficult 4?   My opinion is that it is far too high but for yacminer users it can not be under 1 so this is why most pools (UTC, YAC) use fixed 1 for yacminers.
(or arrange least one port for fixed 1)

Why does what you posted say "Algorithm:scrypt-jane", while the first post of this thread says "Proof of Work: Scrypt-N SHA-3" ?

What algorithm or algorithms does this coin actually use? Has it changed since the first post of the thread without that post being updated accordingly?

-MarkM-

Mining software setting (used library, not exactly true algorithm).  (CPU), minerd: -x64-corei7 -a scrypt-jane .....
Or example with Nvidia GPU, cudaminer:  --algo=scrypt-jane:YAC .....

[Joe_Bauers]

have thrown out the concept of a 2-min block time as a potential fix, but alenevaa is completely against it, Joe_Bauers is against it, and senj, ThirtyBird, old c coder seem to have no opinion either way, so it clearly won't happen. It was just an idea to throw out there

Please keep the ideas coming! That was also my point for birdvox's ideas. We need to have more of an open discussing on updates to YAC, rather than just "that idea sucks, we're not doing it!"


Anyway, regarding the 2-minute block time change, that idea sucks, we're not doing it!  No, but really, if someone has more hashing power than the majority of the network, a block time change is irrelevant.
The fix, as mentioned before is to have more pools, miners and stakers. It looks like that has actually happened over the past 2 days, and +1 * ∞ to NineEleven for starting a new pool!

Also, I just saw your Yacoin caps, they look great! Will certainly help on the promotion side.

[Beave162]

Please keep the ideas coming! That was also my point for birdvox's ideas. We need to have more of an open discussing on updates to YAC, rather than just "that idea sucks, we're not doing it!"  

I have new and improved YAC Hats and a promotional price for them. However, I am putting it on hold until 1) I feel more comfortable that any idea of ANY change in the block reward will not occur with YAC ever. 2) There is a wallet release date at the very least--assuming of course changes to affect the blockchain will not occur until a much later block reward to avoid the very real possibility of separate forks. I also won't be pointing any mining power to YAC until I am more comfortable.

I say that not even as a criticism. I want to indicate to potential, future stakeholders that current stakeholders are completely vested in the basic fundamentals that were laid out since inception of the coin.

Changes to the block rewards is pure and simple centralized manipulation, which crypto was created to protest to begin with. At least the recent attack--which is in itself a form of centralized manipulation--takes resources, and it will ultimately take resources to completely prevent such an occurrence in the future. With that said, I think the recent disturbance in the network has highlighted weaknesses in the blockchain trust mechanism, which senj is addressing.

I think it would be a great idea to discuss an increasing block reward structure on a different thread for a new coin. I will join in on that discussion, and of course, I'm always open to support any scrypt-chacha coin with hash power. I do absolutely love that birdvox wants to do something *most* people would find counter-intuitive. Question everything, especially 'popular' opinion!

Anyway, regarding the 2-minute block time change, that idea sucks, we're not doing it!  No, but really, if someone has more hashing power than the majority of the network, a block time change is irrelevant.

As I've said, I think the idea has been sufficiently vetted enough to know it won't be implemented.

But for intellectual honesty sake, let's be resourceful and refer to other discussions instead of 'reinventing the wheel'
https://bitcointalk.org/index.php?topic=232297.0
https://bitcointalk.org/index.php?topic=211535.40

If I find a block, it takes a few seconds (perhaps 10s of seconds?) to get to you and propagate the network and by that time, I already have a headstart on the next PoW block. That affect is multiplied when I come in at a large hashrate and reduce the block time to 50 seconds or even lower. Also, we should consider that even at 1-minute average expected block time, blocks can be found much quicker than that.

I thought a huge purpose of PoS was for network security. I like the idea that someone could 'selfish mine' all they want, but they still have to wait for a PoS block to propagate the network before the PoW block gets added. Right now, it seems PoW is building on top of PoW and is keeping PoS blocks out. It isn't that there aren't enough PoS inputs because I see my PoS inputs not getting accepted all the time. I understand senj will fix this issue. I understand PoW blocks should eventually be separated by 2 minutes on average anyway with a healthy PoS network.

[NineEleven]

it seems UNOMP is broken for scriptjane


https://github.com/UNOMP/unified-node-open-mining-portal/issues/50

Tomorow i will look into de c code to try to fix myself

[Beave162]

Please try

http://yac.erlog.pt:81/


I think everithing is working

I have turned on two small miners. Hashing works ok but we need more miners (minerd with i7 CPU and cudaminer with some Nvidia GPU.)
Settings are really easy for CPU miner (minerd) or cudaminer. I have not yet tested Yacminer with this pool (amd gpu).

But why this (difficulty)

Username:your yacoin wallet address
Password:anything (what ever)
Algorithm:scrypt-jane
URL (difficulty 4):stratum+tcp://193.136.97.30:3032

Why fixed difficult 4?   My opinion is that it is far too high but for yacminer users it can not be under 1 so this is why most pools (UTC, YAC) use fixed 1 for yacminers.
(or arrange least one port for fixed 1)

Why does what you posted say "Algorithm:scrypt-jane", while the first post of this thread says "Proof of Work: Scrypt-N SHA-3" ?

What algorithm or algorithms does this coin actually use? Has it changed since the first post of the thread without that post being updated accordingly?

-MarkM-

Hasn't changed at all since it was introduced. Putting a name to a coin's algorithm just isn't as straightforward as one would think.

Note that scrypt-jane isn't a hashing algorithm, it's a generic scrypt library that supports many different variations of scrypt, including scrypt+salsa20/8 as used by Litecoin.  I've noticed quite a few people refer to the scrypt variant used by YAC as "scrypt-jane", but that's actually wrong.

So what's the name for it? We shall give it a name, scrypt-chacha?

That's probably the closest option at this point.  In that scenario, scrypt-salsa would accurately refer to the algorithm used by Litecoin, and scrypt-chacha would accurately refer to the algorithm used by YAC.  It's not perfect, as it describes the choice of mixing algorithm but not the choice of hash.  But until someone does something strange like create an altcoin that uses chacha20/8 combined with SHA256 instead of Keccak512, I think "scrypt-chacha" is probably concise enough for now.

So, unless anyone has a different idea, let's indeed call it scrypt-chacha and correct people that call it scrypt-jane (since that's not correct regardless what we decide it should be called!). 

[Qxw]

it seems UNOMP is broken for scriptjane


https://github.com/UNOMP/unified-node-open-mining-portal/issues/50

Tomorow i will look into de c code to try to fix myself

I have used 3 workers, 1 i7 CPU (around same hashing power what one 750Ti when N=17) and one rig with Nvidia 3x750Ti  and one rig with Radeon (4x r7 240  4G)

Radeon rig reported 4 blocks (possible also Nvidia rig but this I,m not sure because cudaminer poor information on the screen) but in pool statistics nothing, not founded, not orphans, just 0.

[NineEleven]

i'm i doing something wrong?

i'm getting this

2015-07-04 13:02:56 [Pool]   [yacoin] (Thread 2) We thought a block was found but it was rejected by the daemon, share data: {"job":"38b","ip":"10.0.21.233","port":3032,"worker":"YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH","height":1125546,"blockReward":76820000,"difficulty":4,"shareDiff":"332.99139015","blockDiff":77.870137344,"blockDiffActual":0.001188204,"blockHash":"43f1025bf8ad1154eff917edb39978040b520cd6d2196ac123c6956a392276a9"}


but some block are in the wallet and already confirmed

my config files

config.json

{
    "logLevel": "debug",
    "logColors": true,

    "cliPort": 17117,

    "clustering": {
        "enabled": true,
        "forks": "auto"
    },

    "defaultPoolConfigs": {
        "blockRefreshInterval": 1000,
        "jobRebroadcastTimeout": 55,
        "connectionTimeout": 600,
        "emitInvalidBlockHashes": false,
        "validateWorkerUsername": true,
        "tcpProxyProtocol": false,
        "banning": {
            "enabled": true,
            "time": 600,
            "invalidPercent": 50,
            "checkThreshold": 500,
            "purgeInterval": 300
        },
        "redis": {
            "host": "127.0.0.1",
            "port": 6379,
            "db": 0,
            "password": ""
        }
    },

    "website": {
        "enabled": true,
        "host": "0.0.0.0",
        "siteTitle": "UNOMP",
        "port": 81,
        "stratumHost": "193.136.97.30",
        "stats": {
            "updateInterval": 60,
            "historicalRetention": 43200,
            "hashrateWindow": 300,
            "graphColors": ["#058DC7", "#50B432", "#ED561B", "#DDDF00", "#24CBE5", "#64E572",
            "#FF9655", "#FFF263", "#6AF9C4"]
        },
        "adminCenter": {
            "enabled": true,
            "password": "********"
        }
    },
    "redis": {
        "host": "127.0.0.1",
        "port": 6379,
        "db": 0,
        "password": ""
    },

    "switching": {
        "switch1": {
            "enabled": false,
            "algorithm": "sha256",
            "ports": {
                "3333": {
                    "diff": 10,
                    "varDiff": {
                        "minDiff": 16,
                        "maxDiff": 512,
                        "targetTime": 15,
                        "retargetTime": 90,
                        "variancePercent": 30
                    }
                }
            }
        },
        "switch2": {
            "enabled": false,
            "algorithm": "scrypt",
            "ports": {
                "4444": {
                    "diff": 10,
                    "varDiff": {
                        "minDiff": 16,
                        "maxDiff": 512,
                        "targetTime": 15,
                        "retargetTime": 90,
                        "variancePercent": 30
                    }
                }
            }
        },
        "switch3": {
            "enabled": false,
            "algorithm": "x11",
            "ports": {
                "5555": {
                    "diff": 0.001,
                    "varDiff": {
                        "minDiff": 0.001,
                        "maxDiff": 1,
                        "targetTime": 15,
                        "retargetTime": 60,
                        "variancePercent": 30
                    }
                }
            }
        }
    },

    "profitSwitch": {
        "enabled": false,
        "updateInterval": 600,
        "depth": 0.90,
        "usePoloniex": true,
        "useCryptsy": true,
        "useBittrex": true
    }
}




yacoin.json ( pool_configs dir)

{
    "enabled": true,
    "coin": "yacoin.json",




    "address": "YLURyDUfPowAgDnvuFnkXA1PxTNPqWQGWU",

    "rewardRecipients": {
        "YEFnVt3f6YTtYyxEVEJFx2NUNri9UsZGpL": 1.5 ,
        "22851477d63a085dbc2398c8430af1c09e7343f6": 0.1
    },




"auxes": [
      
    ],




    "paymentProcessing": {
        "enabled": true,
        "paymentInterval": 600,
        "minimumPayment": 100,

        "daemon": {

            "host": "127.0.0.1",
            "port": 6455,
            "user": "pool",
            "password": "******"



        }
    },
    "ports": {
        
        "3032": {
            "diff": 1,
            "varDiff": {
                "minDiff": 1,
                "maxDiff": 64,
                "targetTime": 15,
                "retargetTime": 90,
                "variancePercent": 30
            }
        }
        
    },

    "daemons": [
        {
           "host": "127.0.0.1",
            "port": 6455,
            "user": "pool",
            "password": "testeYac35T"





        }
    ],

    "p2p": {
        "enabled": false,
        "host": "127.0.0.1",
        "port": 19333,
        "disableTransactions": false
    },

    "mposMode": {
        "enabled": false,
        "host": "127.0.0.1",
        "port": 3306,
        "user": "me",
        "password": "mypass",
        "database": "ltc",
        "checkPassword": false,
        "autoCreateWorker": false
    }

}



I dont have changed anything else

[NineEleven]

it seems UNOMP is broken for scriptjane


https://github.com/UNOMP/unified-node-open-mining-portal/issues/50

Tomorow i will look into de c code to try to fix myself

I have used 3 workers, 1 i7 CPU (around same hashing power what one 750Ti when N=17) and one rig with Nvidia 3x750Ti  and one rig with Radeon (4x r7 240  4G)

Radeon rig reported 4 blocks (possible also Nvidia rig but this I,m not sure because cudaminer poor information on the screen) but in pool statistics nothing, not founded, not orphans, just 0.

we have 12 blocks
8 orphan 4 confirmed
but for every block i get this on the cnsole.log

2015-07-04 05:23:58 [Pool]   [yacoin] (Thread 2) We thought a block was found but it was rejected by the daemon, share data: {"job":"d8","ip":"91.154.39.160","port":3032,"worker":"Y16jSqBD95tCGBWurYfdchFPSy6PKaPWp9","height":1125180,"blockReward":76590000,"difficulty":4,"shareDiff":"505.45273988","blockDiff":79.250259968,"blockDiffActual":0.001209263,"blockHash":"77d3fdb27b8c99fa73616f550bacce683527776dc5beb281519e94700dfa5bab"}


I'm try to understand why

i' so sory for this

i reallly whant this to star working correctly, because yac need some pools running

[feeleep]

it seems UNOMP is broken for scriptjane


https://github.com/UNOMP/unified-node-open-mining-portal/issues/50

Tomorow i will look into de c code to try to fix myself

I have used 3 workers, 1 i7 CPU (around same hashing power what one 750Ti when N=17) and one rig with Nvidia 3x750Ti  and one rig with Radeon (4x r7 240  4G)

Radeon rig reported 4 blocks (possible also Nvidia rig but this I,m not sure because cudaminer poor information on the screen) but in pool statistics nothing, not founded, not orphans, just 0.

we have 12 blocks
8 orphan 4 confirmed
but for every block i get this on the cnsole.log

2015-07-04 05:23:58 [Pool]   [yacoin] (Thread 2) We thought a block was found but it was rejected by the daemon, share data: {"job":"d8","ip":"91.154.39.160","port":3032,"worker":"Y16jSqBD95tCGBWurYfdchFPSy6PKaPWp9","height":1125180,"blockReward":76590000,"difficulty":4,"shareDiff":"505.45273988","blockDiff":79.250259968,"blockDiffActual":0.001209263,"blockHash":"77d3fdb27b8c99fa73616f550bacce683527776dc5beb281519e94700dfa5bab"}


I'm try to understand why

i' so sory for this

i reallly whant this to star working correctly, because yac need some pools running

Hi - try without any fees set up... I dont remember correctly but not sure if this is possible with YAC how UNOMP handles this.

[Qxw]

it seems UNOMP is broken for scriptjane


https://github.com/UNOMP/unified-node-open-mining-portal/issues/50

Tomorow i will look into de c code to try to fix myself

I have used 3 workers, 1 i7 CPU (around same hashing power what one 750Ti when N=17) and one rig with Nvidia 3x750Ti  and one rig with Radeon (4x r7 240  4G)

Radeon rig reported 4 blocks (possible also Nvidia rig but this I,m not sure because cudaminer poor information on the screen) but in pool statistics nothing, not founded, not orphans, just 0.

i reallly whant this to star working correctly, because yac need some pools running

Yes!

Lets hope you find solutions. I will keep one CPU mining in this pool just for small piece of  help to your work for diagnose problems.

 

[feeleep]

Hi Guys,

I tried to stake for last two days and all (sic!) blocks were rejected by network...

So I decided to use this period to clean up pool database a bit - I am processing withdrawals now (set up 1 YAC as threshold) and will be closing pool for maintenance at the end of July. If you have any YAC left on my pool please login and withdraw till 31 July otherwise I will consider remaining coins as donation.

cheers,
feeleep

[NineEleven]

it seems UNOMP is broken for scriptjane


https://github.com/UNOMP/unified-node-open-mining-portal/issues/50

Tomorow i will look into de c code to try to fix myself

I have used 3 workers, 1 i7 CPU (around same hashing power what one 750Ti when N=17) and one rig with Nvidia 3x750Ti  and one rig with Radeon (4x r7 240  4G)

Radeon rig reported 4 blocks (possible also Nvidia rig but this I,m not sure because cudaminer poor information on the screen) but in pool statistics nothing, not founded, not orphans, just 0.

we have 12 blocks
8 orphan 4 confirmed
but for every block i get this on the cnsole.log

2015-07-04 05:23:58 [Pool]   [yacoin] (Thread 2) We thought a block was found but it was rejected by the daemon, share data: {"job":"d8","ip":"91.154.39.160","port":3032,"worker":"Y16jSqBD95tCGBWurYfdchFPSy6PKaPWp9","height":1125180,"blockReward":76590000,"difficulty":4,"shareDiff":"505.45273988","blockDiff":79.250259968,"blockDiffActual":0.001209263,"blockHash":"77d3fdb27b8c99fa73616f550bacce683527776dc5beb281519e94700dfa5bab"}


I'm try to understand why

i' so sory for this

i reallly whant this to star working correctly, because yac need some pools running

Hi - try without any fees set up... I dont remember correctly but not sure if this is possible with YAC how UNOMP handles this.

OK
removing thee fees and restart

[NineEleven]

2015-07-05 12:03:43 [Switching]   [Setup] (Thread 4) Loading last proxy state from redis
2015-07-05 12:03:43 [Pool]   [yacoin] (Thread 4) Share processing setup with redis (127.0.0.1:6379)
2015-07-05 12:03:43 [Pool]   [yacoin] (Thread 4) No rewardRecipients have been setup which means no fees will be taken
2015-07-05 12:03:43 [Pool]   [yacoin] (Thread 4) Stratum Pool Server Started for yacoin [YAC] {scrypt-jane}
2015-07-05 12:03:43 [Switching]   [Setup] (scrypt-jane) Setting proxy difficulties after pool start
2015-07-05 12:03:43 [Pool]   [yacoin] (Thread 4) Authorized YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH: [10.0.24.63]
2015-07-05 12:03:43 [Pool]   [yacoin] (Thread 2) Authorized YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH: [10.0.21.105]
2015-07-05 12:03:43 [Pool]   [yacoin] (Thread 4) Authorized YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH: [10.0.21.205]
2015-07-05 12:03:43 [Pool]   [yacoin] (Thread 1) Authorized YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH: [10.0.21.233]
2015-07-05 12:03:43 [Pool]   [yacoin] (Thread 3) Authorized YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH: [10.0.22.217]
2015-07-05 12:03:52 [Pool]   [yacoin] (Thread 4) Authorized YKL5qhpF6e9ZW7HWkD7TpVZ1NAYFstpxmH: [193.136.99.101]
2015-07-05 12:03:53 [Pool]   [yacoin] (Thread 2) Authorized YAwYcLVDFZ3GW2XYPWnL3Sg6mehsZMSnUq:test2 [213.250.30.129]

[NineEleven]

I have a few coins confiermed
tomorow i will spilt the among the users who are helping me by keeping the miners working

Tahnk you and best regards

[NineEleven]

it seems UNOMP is broken for scriptjane


https://github.com/UNOMP/unified-node-open-mining-portal/issues/50

Tomorow i will look into de c code to try to fix myself

I have used 3 workers, 1 i7 CPU (around same hashing power what one 750Ti when N=17) and one rig with Nvidia 3x750Ti  and one rig with Radeon (4x r7 240  4G)

Radeon rig reported 4 blocks (possible also Nvidia rig but this I,m not sure because cudaminer poor information on the screen) but in pool statistics nothing, not founded, not orphans, just 0.

we have 12 blocks
8 orphan 4 confirmed
but for every block i get this on the cnsole.log

2015-07-04 05:23:58 [Pool]   [yacoin] (Thread 2) We thought a block was found but it was rejected by the daemon, share data: {"job":"d8","ip":"91.154.39.160","port":3032,"worker":"Y16jSqBD95tCGBWurYfdchFPSy6PKaPWp9","height":1125180,"blockReward":76590000,"difficulty":4,"shareDiff":"505.45273988","blockDiff":79.250259968,"blockDiffActual":0.001209263,"blockHash":"77d3fdb27b8c99fa73616f550bacce683527776dc5beb281519e94700dfa5bab"}


I'm try to understand why

i' so sory for this

i reallly whant this to star working correctly, because yac need some pools running

Hi - try without any fees set up... I dont remember correctly but not sure if this is possible with YAC how UNOMP handles this.

Waht stratum are you using? is NOMP ?