[ANN] [CPU mining] Yenten v2.0.1 [YTN] [YescryptR16] [Exchange avilable]

[pochy123]

HELLO, HOW TO DOWNLOAD THE WALLET
IS AGON LINK ??

[1715062383]

1715062383

[1715062383]

1715062383

[1715062383]

1715062383

[1715062383]

1715062383

[1715062383]

1715062383

[cryptonomicon25]

Nice to see a coin where it is worthwhile to mine with a cpu.
What are the blockrewards after the first block? Still 50 YTN?

50 YTN until halving at block 800,000. Current block is 888 and difficulty is 0.0035.

[minodow]

How many threads is best for mining this coin? Im using ryzen 1700.

[cryptonomicon25]

How many threads is best for mining this coin? Im using ryzen 1700.

All of them.

[ttyttg]

Personally, it sounds strange, weird with me. Is CPUs really more efficient than GPUs, particularly with Yenten coin. Are you serious, devs?

[Xeon_Xeon]

I'm giving this a try on Ubuntu 17.10.

[hankrules]

You guys think the dev is going to come back?

[samsungvina19]

You guys think the dev is going to come back?

i think he so busy real work , this is new algo i will follow it

[cryptonomicon25]

Question. How do you unlock your wallet since there is no unlock option?

Are you using yenten-qt? If so, go to Help > Debug window > Console and enter

Code:

walletpassphrase [YOUR PASSWORD] [TIME IN SECONDS YOU WANT TO UNLOCK FOR]

There's really no reason to unlock though unless you are trying to export your private keys or send many separate transactions at once.

[Xeon_Xeon]

Finally got this up and running on Linux mining through the console. I tried minerd but didn't see the point since I'm getting the same hashrate through the console. This is probably a stupid question, but I've never mined solo before, how do I tell when I've mined a block?

Any tips on running in Linux?

I'm on Ubuntu 17.10 64bit.

I compiled and ran ./yentend

@LinuxBeast:~/yenten/yenten/src$ ./yentend
Error: To use the "-server" option, you must set a rpcpassword in the configuration file:
/home/me/.yenten/yenten.conf
It is recommended you use the following random password:
rpcuser=xxxxxxxx
rpcpassword=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "Yenten Alert" admin@foo.com

So I created a yenten.conf file in /home/me/.yenten/ using tips earlier in this thread.

daemon=1
server=1
gen=1
port=9981
rpcport=9982
rpcuser=xxxxxxxxxx
rpcpassword=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Addnode=133.130.66.167:9981
Addnode=52.3.229.122:9981

And the ran ./yentend again.

And get this output "Yenten server starting" but it runs all cores at %100 immediately so i'm assuming something went wrong since I have not tried to mine yet, or is it mining and using the "rpcpassword=" as the mining username.

Been up since early this am and i'm getting sleepy and cant think straight and I know i'm missing something simple.

So i'm stuck and going to bed and will dive in again tomorrow after work.

 

[cryptonomicon25]

Any tips on running in Linux?

I'm on Ubuntu 17.10 64bit.

I compiled and ran ./yentend

@LinuxBeast:~/yenten/yenten/src$ ./yentend
Error: To use the "-server" option, you must set a rpcpassword in the configuration file:
/home/me/.yenten/yenten.conf
It is recommended you use the following random password:
rpcuser=xxxxxxxx
rpcpassword=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "Yenten Alert" admin@foo.com

So I created a yenten.conf file in /home/me/.yenten/ using tips earlier in this thread.

daemon=1
server=1
gen=1
port=9981
rpcport=9982
rpcuser=xxxxxxxxxx
rpcpassword=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Addnode=133.130.66.167:9981
Addnode=52.3.229.122:9981

And the ran ./yentend again.

And get this output "Yenten server starting" but it runs all cores at %100 immediately so i'm assuming something went wrong since I have not tried to mine yet, or is it mining and using the "rpcpassword=" as the mining username.

Been up since early this am and i'm getting sleepy and cant think straight and I know i'm missing something simple.

So i'm stuck and going to bed and will dive in again tomorrow after work.

You've set gen=1 which automatically starts mining when you run the daemon, so delete that line and you should be good.

[tiger2monkey]

Very unique algorithms / project - CPU mining, no GPU and no ASIC mining. So it will be true decentralized. Hope no ASIC will be developed in the future. Other alt coins may follow and use this algorithm.

[savetytdpbl]

Yenten is promising project, at least with me. It simply due to I dont have GPU rigs, so I have to mine with CPU. There are so little coins, which can be mined with CPUs, in the crypto world. Thanks for the great project.

[doktor1897]

how to start mining with this algo? are we still able to do solo mining on our computers? I am very interested to try it

[marcelocoin]

at this time what would be the best algorithm and best coin to mine in CPU would be interesting, good luck in your project.

[nguli]

hey dev, any airdrop or bounty campaign?

[cryptonomicon25]

how to start mining with this algo? are we still able to do solo mining on our computers? I am very interested to try it

Download the Yenten release from here: https://github.com/conan-equal-newone/yenten/releases
Create file yenten.conf in the folder where the yentend is located and enter this information:

daemon=1
server=1
port=9981
rpcport=9982
rpcuser=username
rpcpassword=password
addnode=133.130.66.167
addnode=52.3.229.122

Start the yenten-qt and navigate to Help > Debug window > Console
Type "setgenerate true" in the console which will start the mining
Check your hashrate with the command "getmininginfo"

I've found 6 blocks mining solo with 5 year old computers.

[ir.hn]

update:

don't worry about 1 thread per 2mb cache, just keep increasing the threads until you still get all the threads firing at around the same time and the sum of the threads kH/s is the max

Windows 10:
i5 3230M @2.6
3 threads sum .24 khash/s

i5 2400 @3.2
3 threads sum .33 khash/s

Windows 7:
via quadcore c4650 @2.0
3 threads sum .15 khash/s

Anyone tried GPU's yet?

[JC1DA]

Anyone knows the criteria to get better hashrate? More number of cores? I realized that old hardware and new hardware didn't have significant differences.

[Crikien]

This seems like an interesting project!  I never tried mining something when CPU was still viable.  Hopefully this remains resistant..