[ANN] Ħ [HODL] No Staking, 1% Standard Interest per Day, 750% APR For HOdlers

[baileys2611]

Soooo...I'm guessing that coins caught in a transfer from a wallet that is syncing ok to Coinexchange wallet (which is offline ATM) will come good when they sync up ok?

[optiminer]

There is a segfault in the hodl daemon when the period gets negative which makes it crash:

Code:

Thread 1015 "bitcoin-msghand" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffcf8998700 (LWP 1795)]
getBonusForAmount (periods=periods@entry=-88680, theAmount=theAmount@entry=6150503) at primitives/transaction.cpp:169
169      CBigNum rate256(bonusTable[periods]);
(gdb) bt
#0  getBonusForAmount (periods=periods@entry=-88680, theAmount=theAmount@entry=6150503) at primitives/transaction.cpp:169
#1  0x0000555555748698 in GetInterest (nValue=6150503, outputBlockHeight=262619, valuationHeight=<optimized out>, maturationBlock=173939)
    at primitives/transaction.cpp:245
#2  0x0000555555749ee0 in CTxOut::GetValueWithInterest (this=this@entry=0x7ffcf8995c40, outputBlockHeight=<optimized out>, 
    valuationHeight=<optimized out>) at primitives/transaction.cpp:155
#3  0x00005555555f0413 in ConnectBlock (block=..., state=..., pindex=pindex@entry=0x7fffe40075a0, view=..., fJustCheck=fJustCheck@entry=false)
    at main.cpp:1945

I fixed this by capping the period at 0 if it is negative for the daemon at hodl.optiminer.pl. Would be nice to have an official fix.

[titchbwfc]

I time locked 50 hodlcoin for a month and it says it will mature in -50 days?
anyone know how to fix that?
 

I'm not sure how to unlock before maturation or if you even can.  I think the hodl time is based on blocks rather than time, it lists the date as a general reference.  Going from 30 to 50 doesn't sound right though, maybe you had a typo?  I'm just learning too so i'm sure there are others who can answer this.

hmmm I transferred some hodl and the anomaly disappeared ... weird things are afoot in the circle K

[jokimabraham]

So here's a question from a non-dev-type (me).  We were rolling along on Version 1 of the wallet/miner.  We hard-forked to Version 2.  We now want to un-fork (or fork again if that is more appropriate).  If we changed nothing in terms of the bug fix or optimizations (for the moment), could we not simply use Version 1 again? And if that's possible, would the bug fix and optimizations be able to be put in to the wallet later without it being a dramatic fork?

Interesting - you could try running version 1 to see if it accepts the current chain - if it does, it may well be possible to use it.

I installed Ver 1 but it just sits with "No block source available, 51 weeks behind"

As part of the previous fork, v1 clients were no longer allowed on the network. Mainly to reduce overhead in rejecting invalid blocks.

many many rejections are in the way and many re changing are necessary here.

[eule]

Soooo...I'm guessing that coins caught in a transfer from a wallet that is syncing ok to Coinexchange wallet (which is offline ATM) will come good when they sync up ok?

I hope so. Coinexchange now displays this warning when trying to deposit: "Warning: The wallet appears to be offline currently. Please wait until the wallet is online to deposit funds.", wasn't there yesterday.

Hopefully the fix by optiminer will be implemented soon, even nicer would be a fix of the underlying problem:

There is a segfault in the hodl daemon when the period gets negative which makes it crash:

Code:

Thread 1015 "bitcoin-msghand" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffcf8998700 (LWP 1795)]
getBonusForAmount (periods=periods@entry=-88680, theAmount=theAmount@entry=6150503) at primitives/transaction.cpp:169
169      CBigNum rate256(bonusTable[periods]);
(gdb) bt
#0  getBonusForAmount (periods=periods@entry=-88680, theAmount=theAmount@entry=6150503) at primitives/transaction.cpp:169
#1  0x0000555555748698 in GetInterest (nValue=6150503, outputBlockHeight=262619, valuationHeight=<optimized out>, maturationBlock=173939)
    at primitives/transaction.cpp:245
#2  0x0000555555749ee0 in CTxOut::GetValueWithInterest (this=this@entry=0x7ffcf8995c40, outputBlockHeight=<optimized out>, 
    valuationHeight=<optimized out>) at primitives/transaction.cpp:155
#3  0x00005555555f0413 in ConnectBlock (block=..., state=..., pindex=pindex@entry=0x7fffe40075a0, view=..., fJustCheck=fJustCheck@entry=false)
    at main.cpp:1945

I fixed this by capping the period at 0 if it is negative for the daemon at hodl.optiminer.pl. Would be nice to have an official fix.

[FreeTrade]

There is a segfault in the hodl daemon when the period gets negative which makes it crash:

Code:

Thread 1015 "bitcoin-msghand" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffcf8998700 (LWP 1795)]
getBonusForAmount (periods=periods@entry=-88680, theAmount=theAmount@entry=6150503) at primitives/transaction.cpp:169
169      CBigNum rate256(bonusTable[periods]);
(gdb) bt
#0  getBonusForAmount (periods=periods@entry=-88680, theAmount=theAmount@entry=6150503) at primitives/transaction.cpp:169
#1  0x0000555555748698 in GetInterest (nValue=6150503, outputBlockHeight=262619, valuationHeight=<optimized out>, maturationBlock=173939)
    at primitives/transaction.cpp:245
#2  0x0000555555749ee0 in CTxOut::GetValueWithInterest (this=this@entry=0x7ffcf8995c40, outputBlockHeight=<optimized out>, 
    valuationHeight=<optimized out>) at primitives/transaction.cpp:155
#3  0x00005555555f0413 in ConnectBlock (block=..., state=..., pindex=pindex@entry=0x7fffe40075a0, view=..., fJustCheck=fJustCheck@entry=false)
    at main.cpp:1945

I fixed this by capping the period at 0 if it is negative for the daemon at hodl.optiminer.pl. Would be nice to have an official fix.

Thanks, I'm going to take a look at that right away.

[FreeTrade]

Here's the latest -

What I think happened was that a user tried HOdling before his chain was up to date. This transaction had a maturation block that was already in the past and when miners tried to process that transaction, it caused them to crash rather than just add the transaction with 0 interest.

I've included an emergency fix in the master branch that should fix this issue, although it's a little bit difficult to fully test. I recommend immediately updating while we look at issuing a point release.

Thanks to everyone for reporting the problem and especially Optiminer for the specific bug report and fix.

[DisasterFaster]

This morning I did a Hodl transfer of 650 coins from one wallet to another wallet and the transaction processed although a bit slowly. I then did a second transfer for 900 coins from a different wallet but I reused the same sending address and something went terribly wrong. On the sending wallet it shows the transaction completely verified and finished but the problem is the receiving wallet does not show the transaction at all. It's as if the coins have vanished into thin air since they are now gone from the sending wallet and yet nonexistent on the receiving wallet.

Any suggestions on this and I'm guessing this is related to the issues I saw being reported here in the forum this morning...

[peres]

Here's the latest -

What I think happened was that a user tried HOdling before his chain was up to date. This transaction had a maturation block that was already in the past and when miners tried to process that transaction, it caused them to crash rather than just add the transaction with 0 interest.

I've included an emergency fix in the master branch that should fix this issue, although it's a little bit difficult to fully test. I recommend immediately updating while we look at issuing a point release.

Thanks to everyone for reporting the problem and especially Optiminer for the specific bug report and fix.

Hello Freetrade
I am fortunate to have some HODL coins which have been hodled for nearly a year now. I am having a problem updating my wallet. It says synchronising with the network for about half an hour - I can see from the comments that there is some kind of a problem. Should we just keep trying until it is fixed? Thanks Perry

[Jayjay04]

is there a new wallet for the fix ?

[spmjnkbx]

So can we expect all of the pool mining transactions that have occurred the last several hours to just suddenly all go through once this is fixed?

[lpedretti]

I have reindexed and still no block source.

[titchbwfc]

Here's the latest -

What I think happened was that a user tried HOdling before his chain was up to date. This transaction had a maturation block that was already in the past and when miners tried to process that transaction, it caused them to crash rather than just add the transaction with 0 interest.

I've included an emergency fix in the master branch that should fix this issue, although it's a little bit difficult to fully test. I recommend immediately updating while we look at issuing a point release.

Thanks to everyone for reporting the problem and especially Optiminer for the specific bug report and fix.

think that was me then with my weird negative hodl...oopsy

[baileys2611]

Dafuq?? I mined over a thousand HOdl last night before sleep.  They were immature. Now this morrning the new balance is 300 and I'm still mining, finding blocks but they are not maturing and disappearing from the list of blocks on the wallet.

WTH is going on? Is someone playing silly buggers with this and if so then what a stuupid thing to do.  Good way to de-value the coin (again) guys!!

[jeremyf327]

I backed up my wallet...thank goodness...and now need to restore. Anyone know the steps to do that? I am on a Mac. Not sure how to apply this backup .dat file. Using version 3.0 obviously.

[DisasterFaster]

I backed up my wallet...thank goodness...and now need to restore. Anyone know the steps to do that? I am on a Mac. Not sure how to apply this backup .dat file. Using version 3.0 obviously.

If it were me I wouldn't do anything just yet until we hear from the developer on this issue and it's repair. I've had thousands and thousands of HOdl coins disappear today I mean literally vanish from the wallet and I also had a good sized HOdl coin transfer fail and those coins vanished also. Past that I've had a quantity of freshly mined coins never appear in the wallet as in the immature section or transaction section.

With all that being said, all of your coins should literally be stored in the blockchain and so my hope is that once this issue gets sorted out everyone's HOdl coins will appear/reappear as if nothing ever happened....

I'm pretty confident the issue is being worked on and will be resolved fairly soon

[bkbirge]

Same here, overnight solo mining had a couple hundred, looked fine this morning, then came home from work and 0 balance. Glad I checked here first, will just be patient, hopefully a fix is in soon.

[wisebc]

I can put together a 32 bit windows binary .exe for testing if that would be helpful (I'm not set up for 64 bit builds), it would include the fixes for sorting, but would be unsuitable for mining.

https://drive.google.com/open?id=0B-5Ax5kejTpMNDFUWGZNeGhnTVE

Here it is.

No good for mining, but you can use this to sort your HOdlings and run an empty wallet for your mining.

If you are having trouble with your wallet, I would suggest loading a copy of your wallet up on this version of the software.  It's missing the mining optimizations but between this and the regular 3.0 (which has always crashed and hung for me due to the number of hodlings I have in play) this unk version is stable and is showing all my transactions correctly.  The one machine I have that is using the regular 3.0 is missing all kinds of hodling and transfer transactions.

[DisasterFaster]

I can put together a 32 bit windows binary .exe for testing if that would be helpful (I'm not set up for 64 bit builds), it would include the fixes for sorting, but would be unsuitable for mining.

https://drive.google.com/open?id=0B-5Ax5kejTpMNDFUWGZNeGhnTVE

Here it is.

No good for mining, but you can use this to sort your HOdlings and run an empty wallet for your mining.

If you are having trouble with your wallet, I would suggest loading a copy of your wallet up on this version of the software.  It's missing the mining optimizations but between this and the regular 3.0 (which has always crashed and hung for me due to the number of hodlings I have in play) this unk version is stable and is showing all my transactions correctly.  The one machine I have that is using the regular 3.0 is missing all kinds of hodling and transfer transactions.

@wisebc I'm curious if you go to your transaction table and look at those failed transfers do you have an X in the far left column and when you mouse over it says "conflicted"

[baileys2611]

Yep, I do.  Does that mean it's gawn?