[ANN] [NAUT] Nautiluscoin - First Coin w/Stabilization Fund - Digishield

[CryptoLTD]

Latium coin. Looks quite good to me...

http://latium.cc/?a_aid=53b87c5c83d1e

How many formus are you going to spam this junk with, 1st VRC now here.. if it was so great.. I'de think people would know about it already, in one post you have done the exact opposite of your intended goal, and show everyone here, how desperate you are.

[1715587034]

1715587034

[1715587034]

1715587034

[1715587034]

1715587034

[asnghost]

Current Difficulty   2130  

That will take some time to find the next block, or some multipool needs to hit it.

Mining diff up to 2840. I really hope that proof of stake bug gets fixed really soon. My earlier statement looks potentially accurate, this keeps up with as long as blocks are taking to be solved, at the point of that bug being fixed "the next block" after review and fixing could really be the fork block.

http://nautinsight.buddylabsapps.com/ not showing any blocks and the high diff. What's going on?

[BTCrawl]

Current Difficulty   2130  

That will take some time to find the next block, or some multipool needs to hit it.

Mining diff up to 2840. I really hope that proof of stake bug gets fixed really soon. My earlier statement looks potentially accurate, this keeps up with as long as blocks are taking to be solved, at the point of that bug being fixed "the next block" after review and fixing could really be the fork block.

Why is the difficulty going up? It should drop off when things like this happens, as that's the whole point of Digishield 

[FlyingMongoose]

Current Difficulty   2130  

That will take some time to find the next block, or some multipool needs to hit it.

Mining diff up to 2840. I really hope that proof of stake bug gets fixed really soon. My earlier statement looks potentially accurate, this keeps up with as long as blocks are taking to be solved, at the point of that bug being fixed "the next block" after review and fixing could really be the fork block.

Why is the difficulty going up? It should drop off when things like this happens, as that's the whole point of Digishield  

It's been well established that Digishield is a bit buggy. But ultimately since Proof of Stake is just around the corner, Digishield fixing isn't as much a priority. However, I'm sure other coins that decide to make use of it will have the issue resolved.


Don't forget to donate to the Facebook advertisement campaign
NftgUJjAWDcbCHNpEQD2ASGG5PhP36yVuk

Don't forget to vote
http://www.btc38.com/trade/vote_for_trade.html
https://bter.com/voting
https://hitbtc.com/vote
https://www.swaphole.com/#!voting
https://www.cryptoaltex.com/index.php?page=newcoin
http://www.betbycoin.com/coinvotes/
http://www.coinwarz.com/voting

[Doging]

Why oh why can people not read back a couple of pages?

The answer to the PoS question that is (unbelievably) being asked every 3rd post, is somewhere in this thread.

I won't tell you how many pages to read back (I'll let that be a surprise. Hint: not many)

Why do you people keep asking the same question over and over again, when it has already been answered over and over??

What is wrong with you? 

Because we want POS now dammit. 

[BTCrawl]

Why oh why can people not read back a couple of pages?

The answer to the PoS question that is (unbelievably) being asked every 3rd post, is somewhere in this thread.

I won't tell you how many pages to read back (I'll let that be a surprise. Hint: not many)

Why do you people keep asking the same question over and over again, when it has already been answered over and over??

What is wrong with you? 

Because we want POS now dammit. 

On a positive note, this shows the level of confidence people have in this coin. Technical issues like these would normally cause panic and mass dumping, but everyone knows that it will be remedied soon so everyone (well, almost everyone) is taking it in stride 

[DigiByte]

Current Difficulty   2130  

That will take some time to find the next block, or some multipool needs to hit it.

Mining diff up to 2840. I really hope that proof of stake bug gets fixed really soon. My earlier statement looks potentially accurate, this keeps up with as long as blocks are taking to be solved, at the point of that bug being fixed "the next block" after review and fixing could really be the fork block.

Why is the difficulty going up? It should drop off when things like this happens, as that's the whole point of Digishield  

It's been well established that Digishield is a bit buggy. But ultimately since Proof of Stake is just around the corner, Digishield fixing isn't as much a priority. However, I'm sure other coins that decide to make use of it will have the issue resolved.


Don't forget to donate to the Facebook advertisement campaign
NftgUJjAWDcbCHNpEQD2ASGG5PhP36yVuk

Don't forget to vote
http://www.btc38.com/trade/vote_for_trade.html
https://bter.com/voting
https://hitbtc.com/vote
https://www.swaphole.com/#!voting
https://www.cryptoaltex.com/index.php?page=newcoin
http://www.betbycoin.com/coinvotes/
http://www.coinwarz.com/voting

DigiShield by itself is fine, especially with the amplitude DigiFilter applied. DigiShield + 0.9.1 Bitcoin core update + Scrypt ASICs is the problem. We are updating this in the next DigiByte update when we switch to multi-algo mining.

Bitcoin is actually having some issues as well since the 0.9.1 protocol update that no one is talking about and the Bitcoin core dev team is ignoring when you ask them.

Look at this chart to see the average Bitcoin block time is now around 8 Min instead of 10 Min since the 0.9.1 core update on April 8th: https://blockchain.info/charts/avg-confirmation-time

We are experiencing the same issue as NAUT. We are the only coins with 0.9.1 + DigiShield. We live and we learn, & we should of tested it better and it goes to show we cant rely on the Bitcoin core dev team to be perfect. The 0.9.1 core update was not around when we initially developed DigiShield.

Good news is much fewer coins are in circulation for the short term. DigiShield still prevents multi-pool attacks & too many coins being produced to quickly, but a bit sluggishly at the moment. We are very much looking toward the future success of both coins and we cant wait to see POS implemented for NAUT. Cheers!

[Doging]

Why oh why can people not read back a couple of pages?

The answer to the PoS question that is (unbelievably) being asked every 3rd post, is somewhere in this thread.

I won't tell you how many pages to read back (I'll let that be a surprise. Hint: not many)

Why do you people keep asking the same question over and over again, when it has already been answered over and over??

What is wrong with you? 

Because we want POS now dammit. 

On a positive note, this shows the level of confidence people have in this coin. Technical issues like these would normally cause panic and mass dumping, but everyone knows that it will be remedied soon so everyone (well, almost everyone) is taking it in stride 

I'd rather wait for an audited update than worry about the fork to be honest. As soon as the price spiked so did the hashrate and you can see the effect that has on the price so I can see why people are frustrated.

[BK_PHI]

Current Difficulty   2130  

That will take some time to find the next block, or some multipool needs to hit it.

Mining diff up to 2840. I really hope that proof of stake bug gets fixed really soon. My earlier statement looks potentially accurate, this keeps up with as long as blocks are taking to be solved, at the point of that bug being fixed "the next block" after review and fixing could really be the fork block.

Why is the difficulty going up? It should drop off when things like this happens, as that's the whole point of Digishield 

I talked to DigiShield - when we solved the stuck block and we had so much hash mining the next block was solved very quickly.  This made the difficulty soar.  It is very frustrating.

-BK

[cypz]

I talked to DigiShield - when we solved the stuck block and we had so much hash mining the next block was solved very quickly.  This made the difficulty soar.  It is very frustrating.

-BK

its frustrating for ppl wanting to send money but its not so bad really , theres no new coins entering the market, also many alt coins are taking a hit in the last 2 days. Sell offs have been all round but naut has faired quite well considering.

Can you drip feed us any new information on the status of POS implementation? i know everyone is asking every second post but anything will do =)

[hardcoreprime]

Daily Facebook Advertisement Update.  We have had 34 Website clicks and close to 12,000 impressions!



All donations will be added to the Facebook campaign and implemented at the end of the week.

NftgUJjAWDcbCHNpEQD2ASGG5PhP36yVuk

http://nautinsight.buddylabsapps.com/

Thanks, HCP

[BTCrawl]

Current Difficulty   2130  

That will take some time to find the next block, or some multipool needs to hit it.

Mining diff up to 2840. I really hope that proof of stake bug gets fixed really soon. My earlier statement looks potentially accurate, this keeps up with as long as blocks are taking to be solved, at the point of that bug being fixed "the next block" after review and fixing could really be the fork block.

Why is the difficulty going up? It should drop off when things like this happens, as that's the whole point of Digishield 

I talked to DigiShield - when we solved the stuck block and we had so much hash mining the next block was solved very quickly.  This made the difficulty soar.  It is very frustrating.

-BK

Thanks for the update

[PilotofBTC]

Current Difficulty   2130  

That will take some time to find the next block, or some multipool needs to hit it.

Mining diff up to 2840. I really hope that proof of stake bug gets fixed really soon. My earlier statement looks potentially accurate, this keeps up with as long as blocks are taking to be solved, at the point of that bug being fixed "the next block" after review and fixing could really be the fork block.

Why is the difficulty going up? It should drop off when things like this happens, as that's the whole point of Digishield  

It's been well established that Digishield is a bit buggy. But ultimately since Proof of Stake is just around the corner, Digishield fixing isn't as much a priority. However, I'm sure other coins that decide to make use of it will have the issue resolved.


Don't forget to donate to the Facebook advertisement campaign
NftgUJjAWDcbCHNpEQD2ASGG5PhP36yVuk

Don't forget to vote
http://www.btc38.com/trade/vote_for_trade.html
https://bter.com/voting
https://hitbtc.com/vote
https://www.swaphole.com/#!voting
https://www.cryptoaltex.com/index.php?page=newcoin
http://www.betbycoin.com/coinvotes/
http://www.coinwarz.com/voting

DigiShield by itself is fine, especially with the amplitude DigiFilter applied. DigiShield + 0.9.1 Bitcoin core update + Scrypt ASICs is the problem. We are updating this in the next DigiByte update when we switch to multi-algo mining.

Bitcoin is actually having some issues as well since the 0.9.1 protocol update that no one is talking about and the Bitcoin core dev team is ignoring when you ask them.

Look at this chart to see the average Bitcoin block time is now around 8 Min instead of 10 Min since the 0.9.1 core update on April 8th: https://blockchain.info/charts/avg-confirmation-time

We are experiencing the same issue as NAUT. We are the only coins with 0.9.1 + DigiShield. We live and we learn, & we should of tested it better and it goes to show we cant rely on the Bitcoin core dev team to be perfect. The 0.9.1 core update was not around when we initially developed DigiShield.

Good news is much fewer coins are in circulation for the short term. DigiShield still prevents multi-pool attacks & too many coins being produced to quickly, but a bit sluggishly at the moment. We are very much looking toward the future success of both coins and we cant wait to see POS implemented for NAUT. Cheers!

I'm glad to see you are defending your code and blaming a 3rd party. The bottom line is, as it is in the current version of NAUT the digisheild is much too aggressive. It ramps up much too quickly. It should take a rolling average of multiple blocks rather than just taking the current and last block into consideration. (at least that's what I assume it is doing, I haven't looked at the code).   

That said, all software has bugs. But, this issue has been plaguing NAUT since the beginning and no one did anything about it. Sound familiar to "0.9.1 protocol update that no one is talking about and the Bitcoin core dev team is ignoring when you ask them."?

>"DigiShield still prevents multi-pool attacks & too many coins being produced to quickly"

Yes, and it also prevents the ability to use the coin. If it takes hours to solve a block, that means transactions aren't taking place. With a coin that touts FAST block times to allow it to be used for commerce... well anyway.

I also will be very happy with PoS version is going and the block times are back to 40-60 seconds. I'm very willing to run the beta wallet to test PoS as well.

[IncreaseMyT]

I like mooning 

[IncreaseMyT]

Seems like it may finally be time to crack 50k

[BTCrawl]

>"DigiShield still prevents multi-pool attacks & too many coins being produced to quickly"

Yes, and it also prevents the ability to use the coin. If it takes hours to solve a block, that means transactions aren't taking place. With a coin that touts FAST block times to allow it to be used for commerce... well anyway.

Well, I suppose the positive thing here is that we'll at least end up with a much lower number of coins. In the end it's actually very positive for us early investors, so I can't be too mad about all this I feel a little bad for BK though, as he's mining at a loss to keep the network going. Still, I think we can turn that too into a positive as it shows how dedicated he is to make this coin a success. Once the switch to PoS happens and all the technical difficulties will be fixed, we'll be able to use this to show how legitimate Naut is People will feel comfortable to invest longterm knowing that this coin will be around for a long time. I mean, we already knew that but this will further reassure new investors.

[PilotofBTC]

>"DigiShield still prevents multi-pool attacks & too many coins being produced to quickly"

Yes, and it also prevents the ability to use the coin. If it takes hours to solve a block, that means transactions aren't taking place. With a coin that touts FAST block times to allow it to be used for commerce... well anyway.

Well, I suppose the positive thing here is that we'll at least end up with a much lower number of coins. In the end it's actually very positive for us early investors, so I can't be too mad about all this I feel a little bad for BK though, as he's mining at a loss to keep the network going. Still, I think we can turn that too into a positive as it shows how dedicated he is to make this coin a success. Once the switch to PoS happens and all the technical difficulties will be fixed, we'll be able to use this to show how legitimate Naut is People will feel comfortable to invest longterm knowing that this coin will be around for a long time. I mean, we already knew that but this will further reassure new investors.

I agree, bk spending his own cash to keep the blockchain moving is admirable. But, when you say "at a loss" I think that might be true based on the current prices the day he was mining the coin. But, in 6-12 months if the coin keeps charting as it has been, it will be a HUGE gain. So, lets not give him the Nobel Prize for altruism just yet.

[BTCrawl]

>"DigiShield still prevents multi-pool attacks & too many coins being produced to quickly"

Yes, and it also prevents the ability to use the coin. If it takes hours to solve a block, that means transactions aren't taking place. With a coin that touts FAST block times to allow it to be used for commerce... well anyway.

Well, I suppose the positive thing here is that we'll at least end up with a much lower number of coins. In the end it's actually very positive for us early investors, so I can't be too mad about all this I feel a little bad for BK though, as he's mining at a loss to keep the network going. Still, I think we can turn that too into a positive as it shows how dedicated he is to make this coin a success. Once the switch to PoS happens and all the technical difficulties will be fixed, we'll be able to use this to show how legitimate Naut is People will feel comfortable to invest longterm knowing that this coin will be around for a long time. I mean, we already knew that but this will further reassure new investors.

I agree, bk spending his own cash to keep the blockchain moving is admirable. But, when you say "at a loss" I think that might be true based on the current prices the day he was mining the coin. But, in 6-12 months if the coin keeps charting as it has been, it will be a HUGE gain. So, lets not give him the Nobel Prize for altruism just yet.

Let's certainly hope so

[FlyingMongoose]

>"DigiShield still prevents multi-pool attacks & too many coins being produced to quickly"

Yes, and it also prevents the ability to use the coin. If it takes hours to solve a block, that means transactions aren't taking place. With a coin that touts FAST block times to allow it to be used for commerce... well anyway.

Well, I suppose the positive thing here is that we'll at least end up with a much lower number of coins. In the end it's actually very positive for us early investors, so I can't be too mad about all this I feel a little bad for BK though, as he's mining at a loss to keep the network going. Still, I think we can turn that too into a positive as it shows how dedicated he is to make this coin a success. Once the switch to PoS happens and all the technical difficulties will be fixed, we'll be able to use this to show how legitimate Naut is People will feel comfortable to invest longterm knowing that this coin will be around for a long time. I mean, we already knew that but this will further reassure new investors.

I agree, bk spending his own cash to keep the blockchain moving is admirable. But, when you say "at a loss" I think that might be true based on the current prices the day he was mining the coin. But, in 6-12 months if the coin keeps charting as it has been, it will be a HUGE gain. So, lets not give him the Nobel Prize for altruism just yet.

Let's certainly hope so

We all do have a goal of earning here. I'm hoping at least part of the mining is going back into the NSF.

[PilotofBTC]

>"DigiShield still prevents multi-pool attacks & too many coins being produced to quickly"

Yes, and it also prevents the ability to use the coin. If it takes hours to solve a block, that means transactions aren't taking place. With a coin that touts FAST block times to allow it to be used for commerce... well anyway.

Well, I suppose the positive thing here is that we'll at least end up with a much lower number of coins. In the end it's actually very positive for us early investors, so I can't be too mad about all this I feel a little bad for BK though, as he's mining at a loss to keep the network going. Still, I think we can turn that too into a positive as it shows how dedicated he is to make this coin a success. Once the switch to PoS happens and all the technical difficulties will be fixed, we'll be able to use this to show how legitimate Naut is People will feel comfortable to invest longterm knowing that this coin will be around for a long time. I mean, we already knew that but this will further reassure new investors.

I agree, bk spending his own cash to keep the blockchain moving is admirable. But, when you say "at a loss" I think that might be true based on the current prices the day he was mining the coin. But, in 6-12 months if the coin keeps charting as it has been, it will be a HUGE gain. So, lets not give him the Nobel Prize for altruism just yet.

Let's certainly hope so

We all do have a goal of earning here. I'm hoping at least part of the mining is going back into the NSF.

If the BTC came from the NSF for the mining, then it should all go into the NSF. If it came from BK's pocket, then I think that is where the coins should go. Of course, if BK want's to donate it all to the NSF, more power to him.