Skip to content

A client that listens to yaps-server updates and manages miners

License

Notifications You must be signed in to change notification settings

serdaroquai/yaps-client

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

41 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

#Installation

#1. send a /subscribe message to @YapsNotificationBot using TelegramWeb(easier to copy paste). It will return a token and a userId, note them down later to place in your properties file.
#2. Create a base folder (D:\minerwatch) and copy yaps-client-0.1.0.jar
#3. Copy the miner softwares you will use under your base folder. (Don't forget to add anti virus exclusions if necessary)
#4. Prepare an application.properties file. You can find a sample file below, save it in your base folder.
#5. Don't forget to fill "token" and "userId" fields using step 1. If you have more than one mining rig, make sure each yaps-client installation uses a different rigId.
#6. Make a windows shortcut to start yaps-client (C:\ProgramData\Oracle\Java\javapath\java.exe -jar "D:\minerwatch\yaps-client-0.1.0.jar"). Also don't forget to set the "Start in" property of the shortcut to your base folder where yaps-client-0.1.0.jar sits. ("D:\minerwatch")
#7. Copy the shortcut you have created to your windows start folder. (C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup)


#-------------------------------------
#Sample application.properties file (should be in the same folder with your jar)
#-------------------------------------

# which port this client should run on
server.port=8090

# where the logs are to be stored
logging.file=logs/server.log

# if you want to use a custom yaps-server instance you can un-comment below and change the url otherwise leave it as it is
#remote.url=ws://yaps.serdarbaykan.com:8090/pokerNight

#token received from yaps telegram bot during subscription
login.token=123456789XYZ 

#user id received from yaps telegram bot during subscription
login.userId=1234

#id of your rig, name it as you please (max 16 charaters)
login.rigId=Rig1

# Require 25% profit threshold for switching in first 30 seconds, after 30 seconds decreaes to 5%. 
# Customize as you please. This is to prevent too much switching too soon
threshold.0=0.25
threshold.30=0.05

# only strategy so far, no need to change
strategy.name=highestCurrentEstimate

# Initial delay period before start mining after yaps-client starts
# This is useful to prevent drawing too much power during a restart before MSI afterburner or such kicks in
minerStart.initialDelay=45000

# your GPU hashrate benchmarks per algorithm in kiloHash 
# Below are some reference values for a 1080 TI with +100 core clock %80 power
hashrateMap.X17=17770
hashrateMap.PHI1612=31650
hashrateMap.Lyra2REv2=67460
hashrateMap.NeoScrypt=1780
hashrateMap.NIST5=76590
hashrateMap.Skein=869470
hashrateMap.Xevan=4960
hashrateMap.X11Gost=19650
hashrateMap.Timetravel=38150
hashrateMap.Bitcore=25020
hashrateMap.Blake2s=6650000

# Your wallet address
wallet.address = <yourBtcAddress>

# Configuration of your miner softwares
# you can use placeholders for variables like ${wallet.address} as seen below in order to reduce duplication 
minerMap.X17.algo=X17
minerMap.X17.path=D:\\minerwatch\\miner\\palginmod_1.1_x64_X17\\ccminer.exe -a x17 -o stratum+tcp://x17.mine.ahashpool.com:3737 -u ${wallet.address} -p c=BTC,ID=${login.rigId}
minerMap.X17.kill=ccminer.exe

minerMap.PHI1612.algo=PHI1612
minerMap.PHI1612.path=D:\\minerwatch\\miner\\ccminer-phi-1.0_PHI1612\\ccminer.exe -a phi -o stratum+tcp://phi.mine.ahashpool.com:8333 -u ${wallet.address} -p c=BTC,ID=${login.rigId}
minerMap.PHI1612.kill=ccminer.exe

minerMap.Lyra2REv2.algo=Lyra2REv2
minerMap.Lyra2REv2.path=D:\\minerwatch\\miner\\excavator_Lyra2REv2\\excavator.exe -c D:\\minerwatch\\miner\\excavator_Lyra2REv2\\awesome.json
minerMap.Lyra2REv2.kill=excavator.exe

About

A client that listens to yaps-server updates and manages miners

Resources

License

Stars

Watchers

Forks

Packages

No packages published