Topic: [ANN][LimecoinX Rebrand to BitSend] - page 28. (Read 110652 times)
I need help in maintaining the prices of about 1300-1500
_______________________________________________________________________________ ______________________________LIMX Short View
LIMX_International_Digital_Network
X11 POW - Masternoder POS Darksend - InstantX Slow Distribution - No blockhalving 100 Years Mining Exchanges: Bittrex Cryptopia Coingather Cointopay LIMX FACTS RPC PORT: 8800 P2P PORT: 8886 ROAMING FOLDER: limecoinx CONFIG NAME: limecoinx.conf CURRENT CLIENT: v0.11.2.33 small pump  Next goal - Synergy Cool. I think it would be a good idea for your team to dump your LIMX and take profits right now. Synergy looks interesting. Thanks for the tip!
First page of trex and price very nice
small pump
Next goal - Synergy Bittrex 1000 Sat and 890 $ Dollar ...Nice. seems like things are moving, good future ahead  It cranked up too fast. I was trying to buy at those ridiculously low prices and I was only a few steps ahead of the market. I guess this coin couldn't be kept a secret. Bittrex 1000 Sat and 890 $ Dollar ...Nice. seems like things are moving, good future ahead
Bittrex 1000 Sat and 890 $ Dollar ...Nice.
specify different ports in the limecoinx.conf (port=xxxx) for each wallet instance. This will allow you to run several wallets at the same time, without port conflicts. The important part being that you DO NOT CHANGE the port on the masternodeaddr you leave it as 8886. Thank you very much, I did not know that port=xxxx was allowed to differ from masternodeaddr port. Problem solved  Quote The ReferencNode worked correct. This address caused it 5.9.86.18:8886 He redirected the regular payments. The Vincode is always different. So u admitted that mnode 5.9.86.18:8886 is ok In next post u say Quote 2015-07-19 17:44:02 Misbehaving: 5.9.86.18:8886 (80 -> 100) BAN THRESHOLD EXCEEDED Does it mean 80% of the masternodes is controlled by misbehaving peer? Hard to say. I wonder how he operates his Nodes. Quote The ReferencNode worked correct. This address caused it 5.9.86.18:8886 He redirected the regular payments. The Vincode is always different. So u admitted that mnode 5.9.86.18:8886 is ok In next post u say Quote 2015-07-19 17:44:02 Misbehaving: 5.9.86.18:8886 (80 -> 100) BAN THRESHOLD EXCEEDED Does it mean 80% of the masternodes is controlled by misbehaving peer?
Thank u for ur reply.
How many diffrent vins u see here? 2015-07-18 23:44:33 mnw - winning vote - Vin CTxIn(COutPoint(6f9fe76d2ee90368e6cc621576820fcbd315291b0664df84e60ce9a66b0f533d, 0), scriptSig=) Addr iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc Height 108659 bestHeight 108649 23:44:41 mnw - winning vote - Vin CTxIn(COutPoint(6f9fe76d2ee90368e6cc621576820fcbd315291b0664df84e60ce9a66b0f533d, 0), scriptSig=) Addr iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc Height 108660 bestHeight 108650 23:44:50 mnw - winning vote - Vin CTxIn(COutPoint(6f9fe76d2ee90368e6cc621576820fcbd315291b0664df84e60ce9a66b0f533d, 0), scriptSig=) Addr iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc Height 108661 bestHeight 108651 23:45:03 mnw - winning vote - Vin CTxIn(COutPoint(6f9fe76d2ee90368e6cc621576820fcbd315291b0664df84e60ce9a66b0f533d, 0), scriptSig=) Addr iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc Height 108662 bestHeight 108652 23:45:07 mnw - winning vote - Vin CTxIn(COutPoint(6f9fe76d2ee90368e6cc621576820fcbd315291b0664df84e60ce9a66b0f533d, 0), scriptSig=) Addr iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc Height 108663 bestHeight 108653 23:45:30 mnw - winning vote - Vin CTxIn(COutPoint(6f9fe76d2ee90368e6cc621576820fcbd315291b0664df84e60ce9a66b0f533d, 0), scriptSig=) Addr iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc Height 108664 bestHeight 108654 23:45:36 mnw - winning vote - Vin CTxIn(COutPoint(6f9fe76d2ee90368e6cc621576820fcbd315291b0664df84e60ce9a66b0f533d, 0), scriptSig=) Addr iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc Height 108665 bestHeight 108656 23:45:36 mnw - winning vote - Vin CTxIn(COutPoint(6f9fe76d2ee90368e6cc621576820fcbd315291b0664df84e60ce9a66b0f533d, 0), scriptSig=) Addr iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc Height 108666 bestHeight 108656 I see one vin did 8 next ones blocks. And all of these blocks were "created" in minute, don't u find it surprising? shouldn't take ~40 minutes for it ? "108692" : "i5ujxsxr69ByAPni9ZrRSDgaLoj5uXePr9", "108693" : "i9rUL1rvZ2fRcCfYZ2wHNY7Ep9gZj5yngf", "108694" : "iQrGmW1ceSvsWWRPumKo31kPzD5Xn9BBmm", "108695" : "i6WCzou9NeZwfKZX77kQBhrYjuJToyceUz", "108696" : "iL3MGoBMrgThuvqj1es5nhVTWVrvZqpTso", "108697" : "iQZfv297r2SJt3R4WmPQ8nJSN4wPdfxEYV", "108698" : "iEmQd5Lzfgc2nE6MwjsoWtNej4fhJxgTiP", "108699" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108700" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108701" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", Code: 2015-07-19 12:45:25 mnw - winning vote - Vin CTxIn(COutPoint(af50f7a29ebf1c0c3a6a5ffa5e59061184367c7875f1ccb90f1db9b921abefba, 0), scriptSig=) Addr iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg Height 108788 bestHeight 108798 The ReferencNode worked correct. This address caused it 5.9.86.18:8886 He redirected the regular payments. The Vincode is always different. Vin CTxIn(COutPoint(e02397c7f5624af17b5f298465207b72d13409c39955f29b76174dde938d2fe7, 0) https://bchain.info/LIMX/addr/i9mVUL6nqLywtKsHzSd2tEDVNC96gGkjqS "5.9.86.18:8886" : "iSLUTAfBBbqL7Le6GX97CAKTQvPKw2zh7p", "5.9.86.18:8886" : "iKhJYH2P9AWo8TickmNQNpVPbySHfdbznt", "5.9.86.18:8886" : "iCST5UbKn8gJj6UUvzU689pnTv8YHofpvD", "5.9.86.18:8886" : "iKByMDeCVXXdxTYye1gNGbwwYxNPhJF6w7", "5.9.86.18:8886" : "iE1UjRCznjaLCtXWwNYAJdnuWGjERJJ89h", "5.9.86.18:8886" : "iMiuBXs8ERenTzzqb18g8UHDhE5G115Fgy", "5.9.86.18:8886" : "i8AzLSGJ77xdAstvEQ1acgMpxHpN4gbm7k", "5.9.86.18:8886" : "i8ExaPhpp2GntvBSGEnP4XW16faS4H1NgJ", "5.9.86.18:8886" : "iDhkR52W4PRpHgRx71W7UNC5e6mvwzMWC6", "5.9.86.18:8886" : "i8jCpL8VLsts93NAYCMU2ZruaM7BwMe849", "5.9.86.18:8886" : "iJwchEA2HFc2fonWS1cJz1ATNUHRaVtUU8", "5.9.86.18:8886" : "i9HMwq1XWTGAWLpuwLNrbABsF9mZscS3jp", "5.9.86.18:8886" : "iJvW56gpiLMpVyRyGKYdAVUonXjtDfLUFx", "5.9.86.18:8886" : "i9mVUL6nqLywtKsHzSd2tEDVNC96gGkjqS", "5.9.86.18:8886" : "i3t3VVirGg2m2yuBeABUA42PXKvyKM8oMd", "5.9.86.18:8886" : "iBW6CR5xsRR3ed9tBP9bpwNdndDdR2geaJ", "5.9.86.18:8886" : "iE9ydERjDXM55zTqAi1wwT2MuHfRrHFkCM", "5.9.86.18:8886" : "i6r7yooSTmWVV9CZjS5uatMyN6GL3XvXHA", "5.9.86.18:8886" : "iBhNM1vH1ZVJC3fKjdYVY1jw8vmZgs8hnr", "5.9.86.18:8886" : "iCEz993dA6KGCr7QfWGUe7Ut36L4RmTXss", "5.9.86.18:8886" : "iQ7GAeWj85MHTYCybtmPjLYLsb8rXBnE8q", "5.9.86.18:8886" : "i9qe8wVBgf83bjFx8QJvbdkq7QTCXwqwrC", "5.9.86.18:8886" : "iSdBqum673VFHykrFccgQxQrUuvUeGb5WS", "5.9.86.18:8886" : "iLZECirkyzwcscz8fgDk2bvF4oG76cjvtF", "5.9.86.18:8886" : "i6ycj7fGY83WSSzgSEhFxbbr4aYcu8jxia",
"108692" : "i5ujxsxr69ByAPni9ZrRSDgaLoj5uXePr9",
"108693" : "i9rUL1rvZ2fRcCfYZ2wHNY7Ep9gZj5yngf", "108694" : "iQrGmW1ceSvsWWRPumKo31kPzD5Xn9BBmm", "108695" : "i6WCzou9NeZwfKZX77kQBhrYjuJToyceUz", "108696" : "iL3MGoBMrgThuvqj1es5nhVTWVrvZqpTso", "108697" : "iQZfv297r2SJt3R4WmPQ8nJSN4wPdfxEYV", "108698" : "iEmQd5Lzfgc2nE6MwjsoWtNej4fhJxgTiP", "108699" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108700" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108701" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108702" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108703" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108704" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108705" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108706" : "i7yevaizwAGsaq9zQcSkkmnd4CyBqeye9J", "108707" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108708" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108709" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108710" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108711" : "iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc", "108712" : "iKmAdRuGQzrEyrzUwruC3GGFZ1KEuif4Tk", "108716" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108717" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108718" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108719" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108720" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108721" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108722" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108723" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108724" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108725" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108726" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108727" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108728" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108729" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108730" : "i3p8JkYTsV1kMhbB7uJyWAJLKA8GTqihRT", "108731" : "i9GTc8TUYzJSxTr6s95p3W2zvRQyfWM5uB", "108732" : "iQG2EUwaqcr4sfHitjSDMQjLZKrnDNRWBV", "108733" : "iRq2aPu3Egah4qduUctqjUATCTd1hC5DMh", "108743" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108744" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108745" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108746" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108747" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108748" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108749" : "i7yevaizwAGsaq9zQcSkkmnd4CyBqeye9J", "108750" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108751" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108752" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108753" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108754" : "iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc", "108755" : "iKmAdRuGQzrEyrzUwruC3GGFZ1KEuif4Tk", "108756" : "iMZLzbPfREN5aVzJCecoaL4TYQryaxsWZ1", "108757" : "i68EP9VRC2z24SJw48XKojjtbvJko88KBV", "108758" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108759" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108760" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108761" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108762" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", "108763" : "iDesPWn1Myj1EkJA42SBg4t4LZzG8vVjmg", If you are using a windows VPS (Amazon in my case) you just specify different ports, but you still run the masternode on 8886. This is what my second Masternode config looks like rpcuser=USERNAME rpcpassword=PASSWORD maxconnections=256 rpcport=8887 port=8887 masternode=1 masternodeprivkey=PRIVGENKEY masternodeaddr=YOUR_IP:8886 The important part being that you DO NOT CHANGE the port on the masternodeaddr you leave it as 8886. You are running this from a second datadir of course, but masternode start command works just fine without port issues, and has been on my AWS for the last couple of weeks. I have never used a hot-cold wallet so I dont know anything in that respect, but this is how I run two MN's on one Windows server. Hope I am not being extremely redundant, Just trying to help out. Shouldn't your port be the same as your masternode port? If you are running multiple masternode, just change the rpcport and your privkey of course. -tb- Code: "108581" : "iJUKwYzjdXCWVpznRwxP9dgg21uEN17gJc", If you are using a windows VPS (Amazon in my case) you just specify different ports, but you still run the masternode on 8886. This is what my second Masternode config looks like rpcuser=USERNAME rpcpassword=PASSWORD maxconnections=256 rpcport=8887 port=8887 masternode=1 masternodeprivkey=PRIVGENKEY masternodeaddr=YOUR_IP:8886 The important part being that you DO NOT CHANGE the port on the masternodeaddr you leave it as 8886. You are running this from a second datadir of course, but masternode start command works just fine without port issues, and has been on my AWS for the last couple of weeks. I have never used a hot-cold wallet so I dont know anything in that respect, but this is how I run two MN's on one Windows server. Hope I am not being extremely redundant, Just trying to help out. This works?  Im going to try this later this evening
If you are using a windows VPS (Amazon in my case) you just specify different ports, but you still run the masternode on 8886. This is what my second Masternode config looks like
rpcuser=USERNAME rpcpassword=PASSWORD maxconnections=256 rpcport=8887 port=8887 masternode=1 masternodeprivkey=PRIVGENKEY masternodeaddr=YOUR_IP:8886 The important part being that you DO NOT CHANGE the port on the masternodeaddr you leave it as 8886. You are running this from a second datadir of course, but masternode start command works just fine without port issues, and has been on my AWS for the last couple of weeks. I have never used a hot-cold wallet so I dont know anything in that respect, but this is how I run two MN's on one Windows server. Hope I am not being extremely redundant, Just trying to help out. I think i get how to setup the local machine, including the multiwallet. Im at a loss however on the remote machine. But what i seem to read everywhere is a 1 vps = 1 node setup, which to me seems more than expensive once nodecount picks up. Looking at this thread i read instances where multiple nodes are run from a single adres:port(multiwallet my guess). So my question would be, is it only possible to run single nodes on single VPS's? Or can multiple nodes be installed on a single server without having to resort to VM? Truly saying, I am sure 1 vps = 1 node is the correct approach when it comes to network stability. But practically several wallets could be run from the same vps. Even in case of LIMX, where the port is fixed, that is possible: you can use different data dirs for each instance on the vps, and specify different ports in the limecoinx.conf (port=xxxx) for each wallet instance. This will allow you to run several wallets at the same time, without port conflicts. Now, you cannot actually start MN on that vps, just because it will complain about the wrong port. To be able to start those MNs, you have to use "hot wallet - cold wallet" method (where you keep the actual coins in the remote machine, and operate the MN from there, while running MN with empty wallet on a vps). On the "cold" wallet (on remote machine), you can specify 8886 in the limecoinx.conf, so it will allow you to start MN. Jump to:
|
