[ANN][ROI] ROI Coin | CPU Only Solo Mining | 15% POS | 18.07% Term Deposit

[Resar]

I have spoken to the pool operator and he assures me that payments are being made. Minimum payout on the pool is 20 ROI.

The pool is still very unstable though. I've just tried mining on it for another half an hour. I had multiple disconnects from the pool and my wallet address never showed up in the stats even though I was submitting shares.

[1713245230]

1713245230

[1713245230]

1713245230

[1713245230]

1713245230

[DisasterFaster]

I have spoken to the pool operator and he assures me that payments are being made. Minimum payout on the pool is 20 ROI.

The pool is still very unstable though. I've just tried mining on it for another half an hour. I had multiple disconnects from the pool and my wallet address never showed up in the stats even though I was submitting shares.

I've got two people here at BCT who say they are working on setting up pools. I don't know if or when they will be ready as I can't monitor their activities.

With all the pool discussion here in the treads I think the dev team needs to have a serious discussion about us running our own pool in house. This would give us more control. Not saying we could do a better job but we'll try hard and yeah our hands are pretty full as it is. I just spoke with a top notch dev who has had a great deal of experience helping with development on HOdl coin. It may be that he is willing to contribute you never know... I'm waiting for a response as I type.

[EDIT] New dev just got back with me and he's all in! Oh YEAH - (me does little dance)...

A few details:

• System integrator IRL, mostly building VMware appliances and doing product evals
• Linux guy, works mostly with CentOS/Ubuntu/Debian OS
• Been contributing to Hodlcoin and EuropeCoin (and now ROI of course)

Feel free to give him a warm welcome to the team...

[Resar]

I think the dev team needs to have a serious discussion about us running our own pool in house.

I think that would be a great move as it will show that the Dev team has nothing to do with the current pool, which will hopefully stop some of the FUD that's appearing in this thread.
This coin has a lot of promise and the Dev team are working their asses off on it. It would be a shame if it's reputation was tainted by pool difficulties.

[xoma11]

tomorrow I will stop the mine and I want to see how much pool I will be paid.
recall the average speed of 15 KH today

[cryptoRX]

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

[CryptoMarv]

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.

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

1)
I think this could be a problem of the instable pool. When blocks are found in the regular rythmus perhaps you will see the correct enddate. But perhaps something other is wrong.

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.

[Sikkan666]

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.

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

Dev explained earlier that it's based on blocks and not a set date regarding to 1).

Therefore it Will probably be a bit off depending on how Many blocks are solved at the term deposit time.

Thats my guess atleast but dev can probably give details

[DisasterFaster]

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.

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

[cryptoRX]

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?

[CapacabanaBitch]

Let us take the opportunity to invest in this great project. In addition to a promising and necessary branch in the new times, the Team is committed to take us very far with

[RinceWind84]

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?

Maybe it has something to do with the staking? I think you are also staking on long term deposits.

[cryptoRX]

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   

[RinceWind84]

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   

Let us hope so

[monalito]

  any other pool better then coinspool ??

[dudu24]

What is the total supply?

[DisasterFaster]

  any other pool better then coinspool ??

Not just yet but it's in the works.

[DisasterFaster]

What is the total supply?

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

[DisasterFaster]

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

[cryptoRX]

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 

[Resar]

@DisasterFaster

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