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

[Fuzzbawls]

compiled the daemon on another machine, an amd fx 8 core.
it exits without errors:

2016-02-24 16:08:01 init message: Verifying wallet...
2016-02-24 16:08:01 CDBEnv::Open: LogDir=XXX ErrorFile=XXX
(end of the log)

no db.log nor wallet.dat is created

EDIT: on the same machine, there are three other wallets running fine.

Is this other machine running 15.10 as well?

Yes.

I spooled up an Ubuntu 15.10 instance today to test this myself. Nothing fancy going on, even using the distro-provided BDB. Daemon compiles fine (using the --with-incompatible-bdb) config flag and has been running all day.

I tried rebuilding from scratch, running the daemon with gen=0, no way.
It crashes without any hint. Not even segfault.

not sure what to tell ya man. I finally stopped my 15.10 instance about an hour ago because i just couldn't get it to NOT run.
everything on the instance was standard distro packages.

Edit: for reference, I myself typically DON'T rely on distro packages and instead compile dependencies myself, but thought I'd give the distro package route a try for this.

[1713512428]

1713512428

[1713512428]

1713512428

[1713512428]

1713512428

[1713512428]

1713512428

[1713512428]

1713512428

[pallas]

compiled the daemon on another machine, an amd fx 8 core.
it exits without errors:

2016-02-24 16:08:01 init message: Verifying wallet...
2016-02-24 16:08:01 CDBEnv::Open: LogDir=XXX ErrorFile=XXX
(end of the log)

no db.log nor wallet.dat is created

EDIT: on the same machine, there are three other wallets running fine.

Is this other machine running 15.10 as well?

Yes.

I spooled up an Ubuntu 15.10 instance today to test this myself. Nothing fancy going on, even using the distro-provided BDB. Daemon compiles fine (using the --with-incompatible-bdb) config flag and has been running all day.

I tried rebuilding from scratch, running the daemon with gen=0, no way.
It crashes without any hint. Not even segfault.

not sure what to tell ya man. I finally stopped my 15.10 instance about an hour ago because i just couldn't get it to NOT run.
everything on the instance was standard distro packages.

Edit: for reference, I myself typically DON'T rely on distro packages and instead compile dependencies myself, but thought I'd give the distro package route a try for this.

it crashes on:

dbenv->set_cachesize(0, 0x100000, 1);

it doesn't return from this function.

the previous call, set_lg_dir(), returns 0.

EDIT: hold on, I may have found the issue.

EDIT2: gotcha! I had a stale /usr/lib/libdb_cxx-4.8.so; even though "configure" detected libdb 5.3, for some reason it linked the old file, but the other libs where on 5.3, hence the crash.

[kaltun]

2 questions :
1: where can i find nodes to add?
2 is there paperwallet ?

[Fuzzbawls]

EDIT2: gotcha! I had a stale /usr/lib/libdb_cxx-4.8.so; even though "configure" detected libdb 5.3, for some reason it linked the old file, but the other libs where on 5.3, hence the crash.

HUZZAH! damn those pesky leftover libs (and...honestly...damn BDB all together anyways!)

[pallas]

EDIT2: gotcha! I had a stale /usr/lib/libdb_cxx-4.8.so; even though "configure" detected libdb 5.3, for some reason it linked the old file, but the other libs where on 5.3, hence the crash.

HUZZAH! damn those pesky leftover libs (and...honestly...damn BDB all together anyways!)

true, I remember having 3 or 4 versions of dbd on a single system because it was needed by programs.... :-)

now the bad news, after some minutes of mining:

    "hashespersec" : 3932160

and nothing is written on the log.

[Fuzzbawls]

now the bad news, after some minutes of mining:

    "hashespersec" : 3932160

and nothing is written on the log.

if you're polling gethashespersec or getmininginfo continuously it seems to be doing multiple calculations when it should be doing just one, this calculation is done at the time of issuing the getmininginfo or gethashespersec RPC functions and is only designed to be a generalized value.

Haven't had time yet to dig into the cause, but the output of those 2 RPC calls should reset on each iteration of the miner's work loop. Exact hashespersec values can be found in debug.log after each iteration like so:

Code:

hash: 0001455b2ea2505716ba29340ce1020291262750aa356223d5fef69c450217da collisions:1026 gethash:0001455b2ea2505716ba29340ce1020291262750aa356223d5fef69c450217da ba:151318 bb:2232995626 nonce:9158
target: 000001c609000000000000000000000000000000000000000000000000000000
2016-02-25 10:35:53 Hashes Per Second=26 (total seconds=409 hashes=10923)

[FreeTrade]

2 questions :
1: where can i find nodes to add?
2 is there paperwallet ?

Hey there. Solid range of nodes should be built in and connected to automically within a few minutes of starting up the software.

No paper wallet yet.

[FreeTrade]

drink some vodka and squirrel come to you  

BTW need some pool... in solo too hard to mine Hodl  

Thanks for this. Looks like we got ourselves an official beverage.

[RidgyDidge]

Is there an updated wallet with the Squirrel logo out yet ?

[TheInfidel]

My luck with mining this has fallen down below one block a day now, getting difficult.
Earning nice interest on the ones I have though.
Has there been any progress made on getting this on an exchange yet?

[meyer]

how can I sell some HODL?

[pallas]

how can I sell some HODL?

try here:
https://bitcointalk.org/index.php?topic=1372878.0

[meyer]

how can I sell some HODL?

try here:
https://bitcointalk.org/index.php?topic=1372878.0

thx

[theboccet]

I have 67h/s on a 4 threads and 8Gb memory.HOdlcoin-qt.exe -gen=1 -minermemory=2 -genproclimit=4 just split my hashrate in two 32h/s with 2Gb miner memory on a windows server  
is there something that i've missed?

[joehoebot]

I have 67h/s on a 4 threads and 8Gb memory.HOdlcoin-qt.exe -gen=1 -minermemory=2 -genproclimit=4 just split my hashrate in two 32h/s with 2Gb miner memory on a windows server  
is there something that i've missed?

how many virtual cores on the server?  is it just 4?

[theboccet]

I have 67h/s on a 4 threads and 8Gb memory.HOdlcoin-qt.exe -gen=1 -minermemory=2 -genproclimit=4 just split my hashrate in two 32h/s with 2Gb miner memory on a windows server  
is there something that i've missed?

how many virtual cores on the server?  is it just 4?

yup just 4

[joehoebot]

I have 67h/s on a 4 threads and 8Gb memory.HOdlcoin-qt.exe -gen=1 -minermemory=2 -genproclimit=4 just split my hashrate in two 32h/s with 2Gb miner memory on a windows server  
is there something that i've missed?

how many virtual cores on the server?  is it just 4?

yup just 4

there is an explanation post a few pages back. let me see if I can find it.

[Laamadeus]

I have 67h/s on a 4 threads and 8Gb memory.HOdlcoin-qt.exe -gen=1 -minermemory=2 -genproclimit=4 just split my hashrate in two 32h/s with 2Gb miner memory on a windows server  
is there something that i've missed?

how many virtual cores on the server?  is it just 4?

yup just 4

there is an explanation post a few pages back. let me see if I can find it.

You can multiply your hashrate to miningmemory, so your hashrate is actually 64h/s.

[Belligerent Fool]

I have 67h/s on a 4 threads and 8Gb memory.HOdlcoin-qt.exe -gen=1 -minermemory=2 -genproclimit=4 just split my hashrate in two 32h/s with 2Gb miner memory on a windows server  
is there something that i've missed?

how many virtual cores on the server?  is it just 4?

yup just 4

there is an explanation post a few pages back. let me see if I can find it.

You can multiply your hashrate to miningmemory, so your hashrate is actually 64h/s.

That's worse then the 67H/s he got from using just standard settings without doubling anything.

[Laamadeus]

I have 67h/s on a 4 threads and 8Gb memory.HOdlcoin-qt.exe -gen=1 -minermemory=2 -genproclimit=4 just split my hashrate in two 32h/s with 2Gb miner memory on a windows server  
is there something that i've missed?

how many virtual cores on the server?  is it just 4?

yup just 4

there is an explanation post a few pages back. let me see if I can find it.

You can multiply your hashrate to miningmemory, so your hashrate is actually 64h/s.

That's worse then the 67H/s he got from using just standard settings without doubling anything.

Yes it is.