Thanks dev. Received airdrop
|
|
|
Dev, stake time of YUP ?
|
|
|
it`s opened, i check it twice
unlock main wallet, and start MN again ?
|
|
|
DEV how to make it work?
Open port 1237 vps. Check it
|
|
|
yup-cli masternode status yup-cli masternode debug try it
|
|
|
Hope giro can fly to the moon soon
|
|
|
yeah, masternode still grow HOLD and it will fly
|
|
|
Too many conflicted transactions in masternode rewards today. What happend? What is the reason?
Notice in 1 hours when have conflicted. Total real reward is normal.
|
|
|
waiting Dev , will be listed
|
|
|
That’s why you need to duplicate your .exe and not just use 2 shortcut with diff datadir Duplicate your yup-qt.exe and rename it yup-qt2.exe and create a shortcut or a .bat for each .exe with the corresponding appdata folder
i said i run a shortcut bat, not from exe. if you set listen =1 , it alway user default port 1237 This is working for me with my config locally on win10 for now 18h without a single MISSING and time running is working too. This is my Masternode controller wallet: And i have a second wallet running (yup-qt2.exe datadir=(path of the second YUP folder in appdata) for the 2nd masternode but with empty masternode.conf and the yup configured like my tuto done, maybe set Masternode.conf first now i can do, thanks one more
|
|
|
That’s why you need to duplicate your .exe and not just use 2 shortcut with diff datadir Duplicate your yup-qt.exe and rename it yup-qt2.exe and create a shortcut or a .bat for each .exe with the corresponding appdata folder
i said i run a shortcut bat, not from exe. if you set listen =1 , it alway user default port 1237
|
|
|
Hi Dev,
somtimes my masternode get error: Status: missing.
and this is Masternode Debug:
Not capable masternode: Could not connect to my_ip:1237
If they are all run locally, you need to run 2 node (copy of yup-qt.exe renamed like yup-qt2.exe) with unique appdata folder (after making the first just copy your folder to YUP2) and in each yup.conf the masternode privkey and add in the second,third and so on (not on the first that act like controller) bind=127.0.0.1:(new masternode 2 port) and dont forget to add staking=0 on the masternode 2 yup.conf The first masternode act like a controller for the added masternode. Controller Masternode yup.conf in users/%USER%/appdata/roaming/YUP/ rpcuser=(user) rpcpassword=(password) rpcallowip=127.0.0.1 rpcport=(rpc masternode controller port) #---- listen=1 server=1 daemon=1 staking=1 (in this way you can mint the coin not locked on masternode) maxconnections=256 #-------------------- masternode=1 masternodeprivkey=(masternode controller privkey) externalip=(fix_ip):(open_port masternode controller) alertnotify=echo %s | mail -s "YUP Alert" (your_mail)
addnode=69.180.58.29 addnode=128.68.210.180 addnode=31.132.225.0 addnode=77.2.30.196 addnode=14.164.203.3 addnode=104.229.188.243 addnode=162.211.173.18 addnode=213.55.176.212 addnode=31.148.219.41 addnode=188.113.136.160 addnode=98.234.11.108 addnode=162.211.173.18 addnode=189.75.112.86 addnode=97.98.56.138 addnode=77.2.18.205 addnode=219.111.162.87
Controller Masternode masternode.conf in users/%USER%/appdata/roaming/YUP/ alias1 (fix_ip):(open_port masternode controller) (masternode controller privkey) (tx_hash masternode controller) (tx_id masternode controller) alias2 (fix_ip):(open_port masternode controller) (masternode 2 privkey) (tx_hash masternode 2) (tx_id masternode 2)
Added Masternode yup.conf users/%USER%/appdata/roaming/YUP2/ #---- rpcuser=(user) rpcpassword=(password) rpcallowip=127.0.0.1 rpcport=(rpc masternode 2 port) #---- listen=1 server=1 daemon=1 staking=0 maxconnections=256 #-------------------- masternode=1 masternodeprivkey=(masternode 2 privkey) externalip=(same than masternode controller fix ip:port) bind=127.0.0.1:(new masternode 2 open port) alertnotify=echo %s | mail -s "YUP Alert" (your_mail)
addnode=69.180.58.29 addnode=128.68.210.180 addnode=31.132.225.0 addnode=77.2.30.196 addnode=14.164.203.3 addnode=104.229.188.243 addnode=162.211.173.18 addnode=213.55.176.212 addnode=31.148.219.41 addnode=188.113.136.160 addnode=98.234.11.108 addnode=162.211.173.18 addnode=189.75.112.86 addnode=97.98.56.138 addnode=77.2.18.205 addnode=219.111.162.87
For the added masternode you must empty the masternode.conf in the users/%USER%/appdata/YUP2/ you can now launch your masternode controller through a shortcut with yup-qt.exe datadir=(path of your appdata folder) and launch added masternode with yup-qt2.exe datadir=(path of your appdata folder) i try before, but error ( yup core already running ) , i use data yup on another folder .
|
|
|
Listen to a friend said, now masternode near 50, each block of the reward has dropped to 32 YUP.I want to know is it float?Along with the increase in the number of masternode, corresponding reward less and less?
SeeSaw Reward Mechanism The SeeSaw mechanism assures a healthy balance of stakers and Masternodes on the network by incentivising one or the other more based on the current network need. If there are not enough stakers a higher percentage of the block reward will be given to them than Masternodes, and vice versa until the appropriate balance is once again achieved. Ideally 1/3 of the coins in existence should be locked up in Masternodes, this allows for 1/3 of the coins to be staking, and 1/3 of the coins to be providing liquidity to the market and circulating among users. That seems about right, but could be altered if need be to promote a healthy network. If 1/3 of the coins are in Masternodes the block reward would be equally split between the staker and Masternode.
|
|
|
Sir bond is a member of slark. Confirm with dev
|
|
|
Had sent pm. Wish i could have airdrop
|
|
|
|