I can't understand what I am doing wrong, but I can't start mining in cluster  What miner do you use? Also I don't understand which wallet address I must use. As it was written in maxente example --coinbase-addr=your roi adress I have registered to coinbase.com, but there is no Roi wallet. Must I use my original ROIcoin wallet address? Sorry for my childish questions. I am newbie in crypto  First of all it would be really helpful if you could specify: 1) what OS you are running (Windows or Linux) 2) what CPU(s) you are using. In general you DON'T need to register anywhere for solo-cluster mining and you DON'T need a wallet on your mining machine. However you DO need a lot of patience to wait for a block hit.  You only need to have a ROI wallet and for starters choose a certain receiving address of your wallet. The syntax to start (without CPU-specifics) would then be [miner-executable] -a hodl -o https://roi.hopto.org:23110 -u mine -p miner -t [number-of-threads] --coinbase-addr=[your-ROI-receiving-address] For everything in brackets just insert your specific values (without the brackets). This should get you started. For all the other settings we can only help you if you are more specific about your system. GOOD LUCK! |
|
|
|
There is a new upcoming exchange where you can vote for Coins. I submitted a voting for BiblePay, if you also want to vote, here you go: http://quantadex.com/vote/414/biblepayI think you have to register to upvote, so if you don't mind, please register using this link (25$ gift for new users + 10$ for me as referral bonus): https://quantadex.com/?ID=r1kgkRqa8OoZAnd please don't forget to leave a comment explaining why BBP is awesome etc.  Gogo guys, please vote and leave a comment for BBP! Right now we are on par with the scam coin "JesusCoin", we gotta surpass them! Nice pictures from Cameroon One! |
|
|
|
Hello all! I need some advice how to start mining
pool reject shares as i understood reson is- CPID_HAS_NO_MAGNITUDE
and i try to mine via boinc and i can't understand how to rise up magintude
client say
Task weight 100
utxo weight 980
magnitude 0
Hi. Your problem is that you aren't staking enough coins to get paid. You need to stake at least 1 BBP/RAC to get some magnitude, which means you need close to 30k BBP in you controller wallet. You can check "exec totalrac", which gives you a UTXO (staking) target (with some over-estimation) to get full payment. Please take a look at the "reward chart" here: https://wiki.biblepay.org/Distributed_Computing |
|
|
|
There is a new upcoming exchange where you can vote for Coins. I submitted a voting for BiblePay, if you also want to vote, here you go: http://quantadex.com/vote/414/biblepayI think you have to register to upvote, so if you don't mind, please register using this link (25$ gift for new users + 10$ for me as referral bonus): https://quantadex.com/?ID=r1kgkRqa8OoZAnd please don't forget to leave a comment explaining why BBP is awesome etc. |
|
|
|
|
Is there a problem with the cluster-pool? I constantly get the following error:
HTTP request failed; connection timed out after 30000 milliseconds
json_rpc_call failed, retry after 30 seconds
Anyone else having this problem? I'm running hodlminer (compiled on this machine) on Ubuntu 16.04 LTS.
|
|
|
|
Anyone here still mining in the cluster with some results ?
I started today with an old server (2x Xeon L5640) and so far I have found 1 block, so in general it works, but if it's consistent/effective I don't know yet. Thanks for sharing, with this old server what are your hash rate ? If I understood things right from people writing about the solo-cluster mining (and the cluster-page itself) then the hash rate in this case is irrelevant; the only thing that counts is the number of instances you are running. So since I have 24 virtual cores I'm running 24 instances on there; I think the hashrate of each thread is maybe 20 H/s or something like that.  Alot of things have changed on the cluster since I 1st made it. If I was you I would look to be putting instances of 200+ on the cluster (I have tested this and works well). I cant say now if lower instances are better. More instances will give you a better chance but you still need hash power to find a block. I would never tell someone with a old laptop core duo doing 20hs to mine the cluster. You still have to remember that there is only 720 blocks a day and there is alot of miners mining. You can see here a miner https://roi-coin-blockexplorer.roi-coin.com/address/RDUcvrHrKBu4wVMSntYvmAbjxTdnBbft1z who seems to mine the cluster alot. I dont know the hash rate or what he/she is mining with or how the miner has it set up. It may be one instance it may be more. As I have said befor I have not had the time to test the output of the cluster in terms of instances vs 1 instance with speed. If you had 1KH I would say 4 instances depending on the rest of your hardware. I my self have tested like this and got 2 blocks in a hour or so and then stopped because I need to use my server for other things at the min I have alot of work on and lots of projects to do GUI for the cluster being one of them all going well. Again the cluster is ment for miners who like to play the Crypto Lotto. Dont mine the cluster if you wish to have a stream of coins day to day because there is alot of miners on roi and only 720 blocks a day. If there is 1500 miners and each one gets a advrage of 30 shares a block thats 30 in 45000 chance of winning. Then if we add instances in to the math it gets silly say a adv of 3 instances each thats 90 in 135000 chance of getting the winning nounce. Looking at that you may understand why I have made the cluster to help solo miners because the odds of finding a block are massive. But by no means is my math 100% its just off the top of my head going on the things I know without trolling though a mass of api stats. One thing I can say is when mining the cluster use a diff address on each instance (on the same computer) this helps to stop dupe shares. You sould do this on pools too. Ah thank you for clearing that up a little. Indeed I haven't found a single block over night, so maybe I will play around with these settings a little bit, let's see what I come up with. |
|
|
|
Anyone here still mining in the cluster with some results ?
I started today with an old server (2x Xeon L5640) and so far I have found 1 block, so in general it works, but if it's consistent/effective I don't know yet. Thanks for sharing, with this old server what are your hash rate ? If I understood things right from people writing about the solo-cluster mining (and the cluster-page itself) then the hash rate in this case is irrelevant; the only thing that counts is the number of instances you are running. So since I have 24 virtual cores I'm running 24 instances on there; I think the hashrate of each thread is maybe 20 H/s or something like that. |
|
|
|
Anyone here still mining in the cluster with some results ?
I started today with an old server (2x Xeon L5640) and so far I have found 1 block, so in general it works, but if it's consistent/effective I don't know yet. |
|
|
|
I don't want to look a gift horse in the mouth, but I appear to be getting a...surprisingly large number of block rewards today from the pool. Like, nearly constant. Why would it be just me?
I think you are the guy that keeps solving the heat mined blocks as soon as they are over 15 minutes old. Right...but unless I'm the only guy mining, why would it always be me that solves the block? You would imagine the same distribution of rewards, just spaced out, right? Like, if there were 50 people mining with similar power, than we should each have a 1/50 chance of getting the block reward. I've got to be missing something here, just can't figure out what. do getmininginfo and see if u are on a pool. you could be like me the other day, and be solo mining a "fork" and not really be earning coins. No, he's definitely on the pool getting every single block so far. @Nox: I think there's definitely something wrong, since you are also the only user who has a "Hashes per second" value and no "CPID_HAS_NO_MAGNITUDE" in the leaderboard, which you "shouldn't" have today. I'm king of the world! What's even more strange: judging by the block history you are NOT the miner who found all the blocks, however you keep getting every reward of every block, which is approx. 1/5 of the whole output today. oO Congratz dude! |
|
|
|
You can point clients to your own wallet. But you will be working on mining the full block on your own. On the cluster we now only mine empty blocks that give you 120 coins for your time Roi coin is the only coin in the world of Crypto coins that you can do this on.     Its the only coin out there that has a true cluster to solo mine on. Others just use a pool set to pay the finder for the block and steal a % from the finder. We give you all the block and take the confirming the txs out of the block for you so you dont have to find the hash for the block and confirm the txs. We let the pools do the confirming of TXs. Not only is ROI a game changer for the coins, wallet and the devs but its also a game changer in the ways it can be mined. We removed the TXs to make solo mining easy vs mining on your own wallet. So with this update, what is best option to mine in this cluster, open more instances (for a max. 400h/s open 4 instances) or one instance is ok ? I have not had chance to do the big work at the min in regards to leaving miners on it and giving each instance its own address. If you are running 2 or more instances you should use a diff payment address on each one. This helps to stop dupe shares. Ah, that is nice to know. I know I don't have the slightest clue about how all of this works, but am I right to assume that this also is in effect for multiple PCs? For example, if someone has 3 PCs with a hexacore CPU each, then if he wants to direct every thread to solo-cluster-mining he needs 18 payment addresses? That sounds like a lot of work to set up. |
|
|
|
I don't want to look a gift horse in the mouth, but I appear to be getting a...surprisingly large number of block rewards today from the pool. Like, nearly constant. Why would it be just me?
I think you are the guy that keeps solving the heat mined blocks as soon as they are over 15 minutes old. Right...but unless I'm the only guy mining, why would it always be me that solves the block? You would imagine the same distribution of rewards, just spaced out, right? Like, if there were 50 people mining with similar power, than we should each have a 1/50 chance of getting the block reward. I've got to be missing something here, just can't figure out what. do getmininginfo and see if u are on a pool. you could be like me the other day, and be solo mining a "fork" and not really be earning coins. No, he's definitely on the pool getting every single block so far. @Nox: I think there's definitely something wrong, since you are also the only user who has a "Hashes per second" value and no "CPID_HAS_NO_MAGNITUDE" in the leaderboard, which you "shouldn't" have today. |
|
|
|
If there was no PODC payment today, magnitude is 0, and we are not able mine until next PODC payment. Am I right?
If yes, can we change this rule to check weekly magnitude? thanks.
Yes, this "failed once - no more mining" rule is too harsh. I wrote that some time ago, but apparently it is not so easy to change it to a "check last n magnitudes and take average value". Although I'm not sure why this would be such a problem, since the client gives a "weekly magnitude" anyways in getboincinfo, so the value is already implemented... |
|
|
|
Ah wow, over night I also hit a block. So for me (mathematically spoken) the block hitting quota increased infinitely. Thanks to all who are working on such a beautiful coin and the best of luck to you! |
|
|
|
I (also) have a strange problem with the daemon: My "heat" miners are 3 Raspberry Pi and 1 ASUS tinker board, all running Ubuntu 16.04 LTS (ARM version). Since today (not sure if it's connected to some update, it might be...) the Pis work but the tinker board always shows "blocks: 0". [...]
Well, that was easy... I copied a wallet.dat from a Pi to the tinker board and it immediately started syncing. Strangely enough when I copied the whole core folder from the same Pi to the tinker it didn't work... |
|
|
|
I (also) have a strange problem with the daemon: My "heat" miners are 3 Raspberry Pi and 1 ASUS tinker board, all running Ubuntu 16.04 LTS (ARM version). Since today (not sure if it's connected to some update, it might be...) the Pis work but the tinker board always shows "blocks: 0". Here is the complete getinfo output: {
"version": 1010203,
"protocolversion": 70717,
"walletversion": 61000,
"wallet_fullversion": "1.1.2.3",
"balance": 0.00000000,
"privatesend_balance": 0.00000000,
"retirement_balance": 0,
"blocks": 0,
"timeoffset": 0,
"connections": 0,
"proxy": "",
"difficulty": 4.656542373906925e-10,
"testnet": false,
"keypoololdest": 1524517371,
"keypoolsize": 1001,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
}
What I've tried so far: cleaning the core folder and starting again; starting with -reindex; completely purging the biblepayd package and reinstalling from scratch; pasting the core folder from a Pi over the tinker core folder; "making" the whole biblepay installation from the git source code on the tinker board. None of these has worked so far, it just won't do pretty much anything. The daemon process is running, but nothing happens. The debug.log also doesn't show any errors etc. Any ideas? Edit: And another, totally unrelated question ( ): How come the user in front of me in the PODC ranking has 100% stake weight with a RAC of 43k and a stake balance of 780k? Shouldn't he stake at least 820k for the 19-20 BBP/RAC range? |
|
|
|
Cluster Node update: The cluster now ONLY mines new EMPTY blocks. In a bid to make Solo Mining easy we have now removed all network transactions from the cluster. So mining the cluster you just work to find the block. No more working to find the block and then working to confirm each network TX. This is a 1st for any coin and is "Unique" to ROIcoin can not be done on any other coin. 1st network block mined on the new cluster. As you can see it holds 0 network TX's https://roi-coin-blockexplorer.roi-coin.com/block/0000000ede24b424d4cb2dedde46a9af53ab313a7079a35d596342556589a595Could you roughly estimate how much this increases the chances of finding a block by cluster-soloing? I tried this a couple of weeks ago with my Xeon 1230v3 (4 instances) but didn't have any luck for several days... |
|
|
|
Well, that sucks... I updated both my controller wallets (Windows x64) to 1122 on Thursday and I never had any problems, no chain stuck, , no errors whatsoever, everything synced without hesitation. However I didn't get any payouts on the last superblock. :/ Moreover, since I didn't receive any payout my heat-miners are useless because my CPID has no magnitude from the last payment. Maybe it would be a good idea to soften this rule, say perhaps look at the average magnitude from the last 5 superblocks and if it's >0 then allow heat-mining... Would be nice if we could get behind what caused this and prevent it from happening again today. I myself am at a wedding so I won't be here again until sometime tomorrow. |
|
|
|
I really don't understand why you wrote all this West, as it doesn't take into account the Snap-to-Grid IT requirement in the actual PODC protocol.
It's sort of confusing everyone, as it's alluding to "a possible change" in the protocol, when we already voted the protocol in.
The UTXO requirement is 20 bbp per RAC. The UTXO breaks chart rounds up to the nearest 10%. Lower than 5% rounds DOWN to zero %.
The only potential recommendation I have is to ask Jaap if he wants to create a 2nd chart in percentages, so people have a chart with a larger scale (maybe they understand percentages better than static BBP amounts per break, thats up to him).
I'm not sure you understood the problem people have with the current rules: There was a vote for how much there should be staked to get full PODC reward. The vote came down to " (at least) 20 BBP per RAC" for full reward (meaning 100%). This voting result should be the corner stone (the anchor) of every "grid" that is applied to determine the amount of payout. Right now people can stake "only" 91% of the 20BBP/RAC and nevertheless receive the full payout (contrary to the voting result). So west tried to come up with some ways to circumvent this dilemma. Don't get me wrong, I myself don't want it to change right now because last time I checked I also was only staking something around 93%. |
|
|
|
I think there may be an issue...
Ran exec testvote earlier, and it came back an error "Invalid object type 0Governanceobject is not valid - "
Tried again a few mins ago, and it crashed the wallet.
wallet ver 1.1.1.9
I think you cannot execute this directly after the superblock, since there is nothing to vote on then. Right now it works fine for me (windows and linux wallets, current versions). |
|
|
|
After upgrading my sancatuaries got the following error while running ************************ EXCEPTION: NSt8ios_base7failureB5cxx11E
String length limit exceeded: iostream
error biblepay in ProcessMessages() But its still running the daemon and trying to complete the mnsync, which it did... Restarting it I did not get the error (yet). I saw this error on my 1.1.1.7 sanc so we should be OK. Ill look into it. Every now-and-then this exact error pops up on my heat-mining ARMs, so it's not a masternode-issue (just in case this helps to figure out what it's caused by). BTW: nice work on the alternative wallet-design. Really looks nice and clean, especially the loading-image (which I see for quite a long time, especially on my old laptop). |
|
|
|
|
Show Posts
