How To Multi Mine The Wallet(because the only pool sucks)1st go to %appdata%/ROICOIN/ Make a file called ROIcoin.conf Paste this in to it. rpcuser=mine
rpcpassword=miner
rpcallowip=0.0.0.0/0
rpcport=23110
rpcthreads=40
server=1
daemon=1
gen=0
miningaddress=RKJsmDd93RmE1zDKn7Vr3vSYF6fTGkWsiq
RPCport = 3377
addnode=85.143.174.214
addnode=138.197.172.223
addnode=165.227.10.125
addnode=159.203.91.200
addnode=99.198.174.212 Now save. Now download HODLminer by woolf http://cryptomining-blog.com/wp-content/download/hodlminer-wolf-2.zipOr any of the other miners you like.  Edit the bat file of the miner on the PC running the wallet to look like this. hodlminer.exe -o http://127.0.0.1:23110 -u mine -p miner -t 4 -q -D --coinbase-addr=RKJsmDd93RmE1zDKn7Vr3vSYF6fTGkWsiq -P And you are good to go on the PC running the wallet. To mine the wallet from a 2nd or 3rd PC all you have to do is find out the IP of the PC running the wallet. In my case its 192.168.0.4 So now download a miner to your other PC that you wish to mine from and edit the .bat file to look like this hodlminer.exe -o http://192.168.0.4:23110 -u mine -p miner -t 4 -q -D --coinbase-addr=RKJsmDd93RmE1zDKn7Vr3vSYF6fTGkWsiq -P That is all you need to do to mine with 1 computer or 50+. The computers just need to be on the same network as the computer running the wallet. Dont forget to change wallet key for your own and change the amount of threads "-t" I like most of you was getting a nice set of coins from the pool often. Now I get less than 20 a day with over 1KH so I have set this up and tested it. It works and I have mined 2 blocks today. I would like to point out that when solo mining you make blocks not hash them. So things are not going to look the same as when you are pool mining. If I helped you you can send me a coin to say thanks here RXd3GwmQA9wdTftDyzYuv29bzgKa4EwnJb Never done mining through longpoll before. I'm getting the following instead of hashrate. Is it correct? [2017-11-11 14:24:14] LONGPOLL pushed new work [2017-11-11 14:24:14] DEBUG: got new work in 18 ms [2017-11-11 14:24:21] DEBUG: got new work in 8 ms [2017-11-11 14:24:24] LONGPOLL pushed new work [2017-11-11 14:24:28] DEBUG: got new work in 9 ms [2017-11-11 14:24:42] LONGPOLL pushed new work [2017-11-11 14:24:42] DEBUG: got new work in 22 ms [2017-11-11 14:24:55] DEBUG: got new work in 8 ms |
|
|
|
ROI Coin is at Trade Satoshi but from what I understand they have a voting system for the coin to get listed. Any suggestions on how to best get through the voting system there would be greatly appreciated... https://tradesatoshi.com/VoteAlso I see a column for paid votes with Doge and a column for free votes. Does the coin have to get to the number spot to get listed? Also there is a timer running, when that timer runs out do all the coins reset and start over? the best thing you can do is to start a voting bounty like you give a fixed amount of ROI for each vote at least that's what most devs do I have seen this. I got 70 BCCS coins for voting FYI, TradeSatoshi has indicated on twitter that they will stop free votes after this round hence only way to get listed would be via paid votes. |
|
|
|
I don't think the pools is even paying out. It says block confirms are 360, yet there are 642 pending blocks.....
The blocks need 360 confirmations which is roughly 12 hours. The stats look fine to me. And I did get a 20 ROI payout yesterday from the pool. But as I posted earlier, that's roughly a 2/3 drop in payout for me. |
|
|
|
on pool this coin algo x11
Algo is clearly stated as hodl on pool website http://coinspool.cu.cc/tbsHave you gotten it mixed up with another coin? |
|
|
|
Probably that's because most of the small folks like me have given up  - either something is wrong with the pool or it's not at all profitable. I started mining 3 days back with my 150-200 h/s but have received only 1 payout of 20 ROIs that too on the 1st day only and zilch after that! Now I feel hopeless that I would receive anything!  Pool payouts have dropped considerably since it first started for me as well. Not sure if it is a result of the nicehash miner influx but it kind of happened after the pool fell to ddos attacks. Now getting roughly 0.1 ROI per block mined... 1 day of mining barely gets me to the minimum payout of 20 ROI. Which honestly speaking, doesn't seem to be a satisfactory payout for the time and hashrate put in. Am considering going back to solo mining and leaving it all in the hands of luck. |
|
|
|
FinBlock [FNBK] has derived a fork out of Ethereum blockchain to enable the following features :
Specifications
Hashing Algorithm: same as in Ethereum, keccak-256
Dev Language : Go, Java, NodeJs
Block time: 1 second
Type: PoW
Difficulty re-targets each block
ERC 20 compliant token to evolve into it’s own XDC01 standard with security and scalability
Fully Auditable
One coin is divisible down to 5 decimal places (divisible up to 10-5)
Total coins: 100,000,000 XDC
Features
Gerant Nodes/Master nodes for quick processing
Lite Nodes/Wallet
Multi-Sig Contracts
API connectivity to IoT devices
Lowest latency times up to a few seconds
Hybrid Public/Private architecture with connectivity to Ethereum and Bitcoin public blockchains
Thought it was supposed to be a fork from ethereum that is a COIN and is POW? So what's up with the ERC20 compliant token. Didn't notice that yesterday. Strange. Will definitely need clarification on this since a token should not be mineable. And 1 sec block time... That's going to be a lot of transactions in 1 minute. |
|
|
|
A shame that someone has cheated the system.  That is really a big change. Really a pity that it had to come to that. Would also be that the early supporter keep their old values or at least get a bonus.  That would be a nice sign to the first supporters of the project.  I think that's a good idea, we will look into it. Fortunately the individual in question wasn't able to withdraw his coins and we were able to handle it internally. Good job to the team for catching it early and stopping the trolls from exploiting the system. |
|
|
|
|
An ETH fork. Waiting to see how this develops. Joining airdrop.
|
|
|
|
hello I receive the rewards of the pool
Yeah. Pool's working fine once again and payments are prompt. No issue imo. And kudos goes to the pool dev for all the hard work. So thank you @elbandi |
|
|
|
Our system has been abused by what appears to be a single user commenting then deleting his comments over a multitude of accounts. We are in the process of banning these spam accounts. Withdrawals will be delayed by what will likely be several hours while we sort this out. Don't worry if you are a legitimate account you will receive your withdrawal. This week the forum reward system will receive the following changes: Auto signups will be disabled (already implemented), login daily reward will be reduced to 10 coins, comment daily reward will be reduced to 30 coins, signup reward will be removed and will no longer reward coins. Minimum amount for withdrawal will be set at 160 coins. The new system will require bitcointalk forum posting (anywhere on bitcointalk, not just our forum), and will require junior member status. If you are already in the program and are a newbie, you are grandfathered in and will still be able to participate. Most of the airdropped coins will come from the bitcointalk forums straight to your wallets. Bonus coins will be awarded to signature wearing supporters. We will release signup data for the new system later this week.
Is this applicable for everyone? It would be great that the early users are given the privilege still get the same amount of rewards since they are the early once who support the project. Given that there will no longer be any new signups for the website, the changes to bounty rewards will affect everyone. Or at least that is my understanding. To be honest, it would provide greater exposure for the dev and team to shift the focus away from participation on their website to this forum since it would mean greater exposure and hence help to spread the new of their project to more people. Imo, it's a good thing. And it helps that newbies who originally signed up to the website would be allowed to participate in the next bounty despite it requiring junior member status. |
|
|
|
Maybe it has something to do with the staking? I think you are also staking on long term deposits.
Considering the deposits were made within minutes of each other, there really shouldn't be any difference. But that's just my personal understanding. Hoping someone better would come along and enlighten me Bear with me I'm not always the best at explaining things but let me give it another shot. To make things "user friendly" we typically will describe "term deposits" in terms of a length of time such as a day, a week, 3 months, etc. This makes it quick and easy to relate to how long the term deposit is. So one might say I am going to term deposit 100 coins for a week, or I am going to term deposit 1000 coins for 2 months. Even the wallet interface is designed to be used in this fashion. So in terms of thinking about, talking about and even doing a term deposit our mind is on these time descriptions. Now the code is actually much different indeed. First thing to grasp is that the code can't think but rather executes a set of instructions. These instructions are static and unchanging. Whether the code executes once or 500 times whether yesterday afternoon or right now it does the same thing each and every time so that piece of the puzzle is static or even we could say carved in stone. Now let's start thinking like we are this code. The code is to execute a block on the blockchain every two minutes. The code also has the authority and ability to variate from that two minutes as it deems necessary. This occurs more specifically as the MIDAS algo monitors the ongoing and changing amount of network hashing power. As network hashing power goes up or down the MIDAS algo will respond and this response includes making adjustments to the difficulty level and even the block timing. This is necessary to provide additional blockchain security for the coin which is yet another discussion topic. Suffice it to say the 2 minute block timing is subject to not be 2 minutes. In fact you may even note an error being reported in the console for "getmininginfo" stating that the expected number of blocks in the expected timespan was off by some margin. Now let's start assembling these different pieces together. While we think of a term deposit as 1 day the code actually thinks of that as 24 hours x 60 minutes or then 1440 minutes divided by 2 minute block timing = 720 blocks - so then when you think 1 day the code thinks 720 blocks. Herein we begin to visualize discrepancies. This is because a day is unchanging at 1440 minutes but a sequence of 720 blocks may or may not be 1440 minutes because the 2 minute spacing interval is dynamic and ever changing. Now digging deeper. When you clickety-click doing up a term deposit the only thing the code can do is take a "snapshot in time" and then calculate and spit out an amount. While at the point in time this occurs it's accurate.. moving forward it becomes wrong. You see the code is shooting at a moving target with fixed parameters. The code is fixed and static and yet at the same time it is making calculations based on variables that are fluid and non-constant. Here is an analogy. The police officer shoots a speeding car with radar and the radar guns says the car is going 100. Assuming his gun is accurate at that snapshot in time the car was in fact going 100. A few hundred feet later the car slows down and is now going 80. The radar gun report of 100 is now no longer accurate because the speed of the car has changed since the radar gun took it's snapshot and calculated 100 mph. Rest assured there is no reason for alarm because you detect a mismatch between expressing lengths of time vs. a moving block chain whose timing will vary. If you prefer consider this option: When you do a term deposit stop using time elements and start using blocks. In other words term deposit 100 coins for 720 blocks or 1000 coins for 21600 blocks etc. Then you and the code will be on the same page but don't forget even if doing a term deposit in blocks quantity you are still going to face the fact that those blocks are not going to crack like a swiss watch at exactly 120 second intervals block after block. One other thing... as quoted, "Considering the deposits were made within minutes of each other, there really shouldn't be any difference." My response to that is "within minutes" matters and there can be a difference. Any of the variable components could potentially change within minutes thus creating different calculated outputs. I appreciate your digging into this coin and wanting to know it inside out. Be patient and bear with me and I'll always do my best to provide any information you desire. If this is still unclear let me know and also let me know which part of this doesn't click.... @DisasterFaster thanks. That was surprisingly clear and concise given the length of your reply So technically, the difference in interest rate is similar to the discrepancy in maturation date. Basically, it is an artefact caused by the code aka algo seeing the blockchain in terms of blocks while we as humans see it or rather, understand it, in terms of time. Thanks once again. And my apologies for having so many questions. I am naturally curious and have a tendency to want to get to the root of things  |
|
|
|
Maybe it has something to do with the staking? I think you are also staking on long term deposits.
Considering the deposits were made within minutes of each other, there really shouldn't be any difference. But that's just my personal understanding. Hoping someone better would come along and enlighten me |
|
|
|
I addressed nearly all of this very thoroughly in an earlier post. In short we do refer to a time span like days weeks, etc. for simplicity but in code speak the time line is in blocks. Blocks are set to 2 minutes however that is not carved in stone as the MIDAS algo will move block timing as it measures and then responds to changes in network hash rates. Nothing to be concerned with there. In terms of your mysterious deposits you will occasionally find that you receive a small bit of coin such as you experienced and this is normal. These are transaction processing payouts in most simple terms. I've got to shower and get out of here and will be able to provide a more lengthy explanation of all this things as soon as I have time. Or alternately maybe someone else can chime in before I get back to revisit this. Rest assured I want nobody to have concerns with term deposits or mysterious transactions
2)
This behavior I also see with holdcoin and europecoin, which both use same algorithm. I also don't understand what it means, but it is only an "optical problem" I think. All balances were correct in the past.
@DisasterFaster - thanks for the fast response. I thought that might be the issue. But for the micropayments, I'm more inclined to agree with @CryptoMarv that it is more an "optical" issue since these microtransactions do not affect our actual balance in any way. Kind of an afterimage from a "group" transaction. But I might be wrong. Is the difference in interest rate also indirectly a result of the "block timing" fluctuations we are currently experiencing? |
|
|
|
Deposits locked and HODL the same pattern, the longer the higher the return, I've started mining, hope to be able to produce generous returns.
I hope you mine a lot of coins and here is an accurate break down of term deposit ROI profits to take a look at: For a 1 week term deposit 100 coins becomes 102.116 coins for a gain of 2.116 or 2.12% For a 2 weeks term deposit 100 coins become 104.494 for a gain of 4.494 or 4.49% For a 3 weeks term deposit 100 coins become 107.127 for a gain of 7.127 or 7.13% For a 1 month term deposit 100 coins become 110.873 for a gain of 10.873 or 10.87% For a 3 months term deposit 100 coins become 145.391 for a gain of 45.391 or 45.39% For a 6 months term deposit 100 coins become 225.05 for a gain of 125.05 or 125.05% For a 1 year term deposit 100 coins become 526.379 for a gain of 426.379 or 426.38% Was looking through the posts and it seems nobody brought this up but there is something very strange going on with the term deposits. I can't post images so I'll just have to spell it out. I placed a few terms deposits to test out the system. According to my wallet, the 1 week deposit I placed on 8/11 was for a term of 7 days and would mature on 17/11. That's 9 days. Not 7. The 1 year deposit I placed on 8/11 was for a term of 365 days but the maturity date was stated as 20/2/2019. That's 15 months and change. And to complicate matters, the deposits are offering different terms upon maturity. Same amount deposited on same day and yet the return upon maturation is different. Granted, it is only a 2 coin difference but the rates are definitely not what was stated above. It's more in the region of 500% ++. Lastly, strange micro-transactions are appearing as received under transaction history but the address(es) do not belong to me and the amounts in these strange transactions are not reflected in my actual balance. Initially, I thought it was the transaction fee for the deposits. However, the amounts do not tally. (example: 79664b16f2a541e0fd9cdccb3e6ae23b7e5197f19694ab0e535d3d6120b1a3ad) - my desposit was for 20 ROI and the transaction fee I was charged was way lower than 3 ROI but both transactions appear in my transaction history. Appreciate if the dev or team could check to see if this is a bug and perhaps rectify it? TLDR:1) Maturation date of term deposit is displaying or calculated wrongly 2) Unrelated transactions (to other wallets) are appearing under wallet transactions |
|
|
|
I didn't receive 180 coins for my last two votes in tradesatoshi.com. I had sent PM for both the instances There was a change in bounty rules. Refer to the first post. Changes as below. Thecryptochat is running our tradesatoshi voting campaign now. Please vote for BITtask at . https://cryp.li/dC15 and get 180 coins per vote. Keep a screenshot of your vote in case of dispute. Fill up this form . https://cryp.li/yhFQ with the required information. Bounties will be paid when the campaign is over. |
|
|
|
|
Why do these people always do the same thing? Drop branding and "important" terms and expect people to drop all their hard-earned money on them?
|
|
|
|
IP changed, and it works for a few submission with accepted status, and then it failed again... Another machine with static IP still can't connect to pool yet.
I am using static ip but intermittent connection for me as well. It works for 2-3 minutes then connection refused again. |
|
|
|
our miners DDOS - pool So many, many miners Indeed... Still can't connect to the pool Dos handled. Pool works again. Elbandi No it isn't. Still getting the following: [2017-11-08 18:59:50] Stratum connection failed: Failed to connect to stratum.coinspool.cu.cc port 3042: Timed out [2017-11-08 18:59:50] ...retry after 30 seconds [2017-11-08 19:01:21] stratum_recv_line timed out [2017-11-08 19:01:21] ...retry after 30 seconds [2017-11-08 19:02:21] Stratum connection failed: Connection timed out after 30000 milliseconds [2017-11-08 19:02:21] ...retry after 30 seconds |
|
|
|
our miners DDOS - pool So many, many miners Indeed... Still can't connect to the pool |
|
|
|
Cant get solo mining to work with the .conf above, where do i need to put it? i have put it in the folder where the wallet is and also the mining program, still no better.
you need to put it in the roicoin folder. C: > Users > YOURUSER > APPDATA > Roaming > Roicoin |
|
|
|
|
Show Posts
