Topic: [ANN][ROI] ROI Coin | CPU Only Solo Mining Hybrid | 15% POS | 593% Term Deposit - page 157. (Read 107962 times)

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

I suppose it depends on your CPU. Yesterday I saw i7 3770's get 0-4 blocks in 24 hours. I also saw i7 6700, Ryzen 1800X and Intel 6950X do even better. I've also noted days where weaker CPU did better than stronger CPU due to the luck factor.

I wouldn't call an i7 3770 a high end item but at the same time many pc's out there have substantially less hashing power than the high 200's it can dish out. I would say maybe something in the range of an i7 3770 might be about the lowest cpu power that could solo mine a block or more a day at the moment. As hash goes even higher this is subject to watch the bar get raised higher.

hello I receive the rewards of the pool

This other altcoin using cpu mining and gpu in wallet  with pool > https://imgur.com/a/EguSn

It's a 20 ROI minimum payout.

Does anybody knows what is the minimum limit of ROI coin before coinspool pay you ? How much coin you have to mining before they pay you ? 

We only have 1 pool to mine? it looks like kinda pointless to mine with CPU if people already mining with nice hash.

I have a sad box, but it gets free A/C, so it runs at a paltry 80 +/- H/s.  Even with the AES flag... Managed 1 block Wednesday morning.  I leave this box up, so I can get a feel for how the solo mining is going.  I am not discouraged, but it takes patience.

I don't know what kind of streaming income can be achieved from a pool.

I think part of the reason it got lucky is I opened up the box, not as an official Node.  Just opened the FW ports, enabled DMZ port forwarding on the router to the IP of the computer to TCP port 3377, to see what would happen.  So I have a few incoming and outgoing connections processing the chain.  The wallets are setup to find each other.

I do not recommend doing this on any computer that contains data, the port is wide open to the internet.

Thank you!  You get an A+ for reading the forums.  

Yes, the term deposits are "worded" in time periods.  However, time is governed by the blockchain.  While coded for two minutes, does not run at exactly two minutes.  This is, as pointed out, due to MIDAS and its reactions to the swings in net hash rates.

I believe today is day 5 of the live coin.  Net hash is still climbing, and swinging with the pool issues.  Until the network stabilizes at a consistent hash rate, there will be oscillations in the block frequency.

While "annoying" it is the best protection mechanism that will allow the coin to survive most attacks.  It just does not know the difference between growth, pool swings and such vs. an attack.

To clarify about the blocks vs. time periods.  The algo calculates 2 minutes per block and uses that as the multiplier to give the actual maturation block.  Since it knows, lets say, 5040 blocks is one week of blocks at two minutes each, it stamps that future block as the maturation block, but adjusts the displayed time interval as the block chain slows or speeds up.  Very adaptive. For longer periods of time, you will see this up a day, than back to current day on occasion.

If runnign hodlminer.exe gives higher hash rate than wallet use the pool.
https://github.com/madzebra/hodlminer-binary/blob/master/hodlminer.exe

Can you guys take the MadZepra bynary, run 'hodlminer.exe --benchmark -q' for 5 minutes and calculate the average hash rate.

I'll add benchmark results to this file http://hodlcoin.oo.fi:8080/cpus/CPU_vs_Hash_rate.xls

Don't take my opinion as gold it's just my opinion...

With that much hash I would begin trying to solo mine for a day or three. See what happens. I think you can get a block or two a day. If the solo seems okay with you run it until it stops producing.

If your solo mining test run does nothing then by all means jump in the pool!

That sounds great! I had good vibes with the pool dev from the very beginning. You know I've trusted people at BTC and have sent hunks of BTC to people I didn't even know. So far I've never been burned or scammed once. However plenty of people have been in on very bad experiences with crypto and I understand skepticism and caution.

The dev team pool discussion ended up with we would like to see about 3 or possibly more independent pools and an in house pool based at our website. All of that is in the works as I type. If anyone has suggestions on this I'd love to hear it.

You just expressed a very concise and clear description in your tread. Don't apologize for questions. A lot goes into a coin and you have a vested interest to know what you're getting into. The more you understand the coin the more you will love or hate it but either way knowledge is power. I'm neck deep in this coin and don't mind supporting it with whatever info I can offer. I don't know everything but if I can't answer a question I'll work to get an answer and if I answer something wrong I'll learn from that which is all good. Frankly, I'm totally blown away with what I've seen happen since going live Sunday morning wow...

Is it better to mine solo or use the pool if I have about 350 h/s power? Thoughts from the group?

@DisasterFaster

coinspool.cu.cc seems to be completely stable again and work stats are showing pending balances.

@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 

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....

1 billion but don't be mislead by that.

The 1 billion is a literal number right in the code as total coin supply. Now with that being said, this does not account for POS and term deposit which will add an additional amount of coins. Because we can't know the future and how many people will stake/term deposit these are unknown variables which in terms makes it impossible to specify an exact total coin supply.

Here are a couple of other tidbit ROI coin facts that might interest you:

The POW (mining) is set to run for 30 years.
The POW block reward of 120 coins does not reduce/no halving
The 8% POS does not change/no halving
The Term Deposit %'s do not change/no halving

Not just yet but it's in the works.

What is the total supply?