Topic: [ANN] Ħ [HODL] 5% Interest. No Staking Req. Term Deposits 10%. Solo Mining. - page 236. (Read 472878 times)
February 29, 2016, 08:20:13 AM
only solo mining? when will the CPU/GPU miner available?
February 29, 2016, 08:14:34 AM
THE POOL WILL BE TO START?
February 29, 2016, 08:02:30 AM
DIFFICULT
February 29, 2016, 07:50:35 AM
when the exchange get?
What length a piece of string is?
You can buy and sell in the Marketplace. https://bitcointalk.org/index.php?board=161.0
February 29, 2016, 07:43:07 AM
No problem. I'll do a 'make clean' first next time I update.
February 29, 2016, 07:38:03 AM
I had another one last night. Did a 'git pull', recompiled and then 'make install'. There was a library that wouldn't copy over the earlier version, I guess something to do with the attributes set when it was first installed. Might need to check the makefile and see what's going on there.
Name of the library was really long, something like blahblahbitcoinconsensus.a
Still seems to be working because I got a few acorns today.
Name of the library was really long, something like blahblahbitcoinconsensus.a
Still seems to be working because I got a few acorns today.
You shouldn't really be trying to compile new stuff on top of old stuff at this point (or any point).
Clean up first
February 29, 2016, 07:26:28 AM
I had another one last night. Did a 'git pull', recompiled and then 'make install'. There was a library that wouldn't copy over the earlier version, I guess something to do with the attributes set when it was first installed. Might need to check the makefile and see what's going on there.
Name of the library was really long, something like blahblahbitcoinconsensus.a
Still seems to be working because I got a few acorns today.
Name of the library was really long, something like blahblahbitcoinconsensus.a
Still seems to be working because I got a few acorns today.
February 29, 2016, 07:21:20 AM
getting a lot of:
SOMEFILE.h:41:147: warning: missing terminating " character
#define COPYRIGHT_STR "2009-" STRINGIZE(COPYRIGHT_YEAR) " The Bitcoin Core Developers, 2015-" STRINGIZE(COPYRIGHT_YEAR) " The HOdlcoin Developers""
when compiling.
a stale double quote?
SOMEFILE.h:41:147: warning: missing terminating " character
#define COPYRIGHT_STR "2009-" STRINGIZE(COPYRIGHT_YEAR) " The Bitcoin Core Developers, 2015-" STRINGIZE(COPYRIGHT_YEAR) " The HOdlcoin Developers""
when compiling.
a stale double quote?
thanks for the catch.
February 29, 2016, 07:05:38 AM
getting a lot of:
SOMEFILE.h:41:147: warning: missing terminating " character
#define COPYRIGHT_STR "2009-" STRINGIZE(COPYRIGHT_YEAR) " The Bitcoin Core Developers, 2015-" STRINGIZE(COPYRIGHT_YEAR) " The HOdlcoin Developers""
when compiling.
a stale double quote?
SOMEFILE.h:41:147: warning: missing terminating " character
#define COPYRIGHT_STR "2009-" STRINGIZE(COPYRIGHT_YEAR) " The Bitcoin Core Developers, 2015-" STRINGIZE(COPYRIGHT_YEAR) " The HOdlcoin Developers""
when compiling.
a stale double quote?
February 29, 2016, 04:34:49 AM
Just want to say thanks to everybody who's reported a problem. Of course we prefer lots of details with bug reports, but even just a vague outline is more helpful than nothing at all. Fuzzbawls has been working really hard to polish up all the rough edges that have been reported and I think the next release will impress.
really looling forward to the next version.... February 29, 2016, 04:29:37 AM
Now here is a valid spendable Transaction... I just picked a random block that was generated...
Hah! That was one of mine, I recognised the mining address instantly.
February 29, 2016, 04:22:49 AM
Just want to say thanks to everybody who's reported a problem. Of course we prefer lots of details with bug reports, but even just a vague outline is more helpful than nothing at all. Fuzzbawls has been working really hard to polish up all the rough edges that have been reported and I think the next release will impress.
Here's another one for you:
"Choose previously used address" button on the Deposit page returns an empty list.
February 29, 2016, 04:14:51 AM
Bug report: Wallet.
Mined HOdl don't show up in the Pending balance.
Mined HOdl don't show up in the Pending balance.
of course not, they show up as "Immature"
Just checked that theory, it doesn't seem to be the case.
Four Linux servers are sending newly mined coin to one address on my laptop. When they arrive they are flagged as mined coins, but neither Pending Balance nor Immature Balance is altered.
Until cleared to be spent I "believe" they should be in Pending Balance since they're not HOdl'ed yet.
February 29, 2016, 03:58:35 AM
We're seeing a lot of HODL being burnt up at an address here -
http://www.presstab.pw/phpexplorer/HODL/address.php?address=3QJmnh
We're calling these roasted nuts. (The nut being the smallest unit of HODL, like the satoshi)
Looks like someone is mining to an invalid address . . . maybe not setting miningaddress properly, or miningaddress="".
There's over 6000 HODL roasted on the open blockchain so far, that's nearly 1% of current supply. So if you're mining to a single address, I want to remind you to take a moment to quietly check your nuts, and readjust them if anything is out of place.
It seems like there is a space between 3QJmnh and the rest of the address.http://www.presstab.pw/phpexplorer/HODL/address.php?address=3QJmnh
We're calling these roasted nuts. (The nut being the smallest unit of HODL, like the satoshi)
Looks like someone is mining to an invalid address . . . maybe not setting miningaddress properly, or miningaddress="".
There's over 6000 HODL roasted on the open blockchain so far, that's nearly 1% of current supply. So if you're mining to a single address, I want to remind you to take a moment to quietly check your nuts, and readjust them if anything is out of place.
Here is one of his generated blocks
Code:
[hex] => 01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff050241390101ffffffff0100f2052a010000000000000000
[txid] => bebb9cb6fc54f76f28eb49bd5e11cccaff5598bf2deca7ba1e0eb0b65f8dbc63
[version] => 1
[locktime] => 0
[vin] => Array
(
[0] => Array
(
[coinbase] => 0241390101
[sequence] => 4294967295
)
)
[vout] => Array
(
[0] => Array
(
[value] => 50.00000000
[n] => 0
[scriptPubKey] => Array
(
[asm] =>
[hex] =>
[type] => nonstandard
)
)
)
[blockhash] => 000001177cb248564ddf85ec98bccd7c1e0a015293d96cd8a5b43994f2c20ec6
[confirmations] => 41
[time] => 1456713877
[blocktime] => 1456713877
This is a non-spendable Transaction look at
Code:
[asm] => [hex] =>
Code:
[reqSigs] => 1
its also missing an address.. all of this is missing and there should be an address after the ">"
Code:
[addresses] => Array
(
[0] =>address goes here
)
Now here is a valid spendable Transaction... I just picked a random block that was generated...
Code:
[hex] => 01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff0502af390104ffffffff0100f2052a010000001976a914511135eaa4d5861c71366b220b7eb773da59d24288ac00000000
[txid] => 5874a40522c98cf9057615ee5b4da19b308004d497ab4398de7fbc040dd98a7a
[version] => 1
[locktime] => 0
[vin] => Array
(
[0] => Array
(
[coinbase] => 02af390104
[sequence] => 4294967295
)
)
[vout] => Array
(
[0] => Array
(
[value] => 50.00000000
[n] => 0
[scriptPubKey] => Array
(
[asm] => OP_DUP OP_HASH160 511135eaa4d5861c71366b220b7eb773da59d242 OP_EQUALVERIFY OP_CHECKSIG
[hex] => 76a914511135eaa4d5861c71366b220b7eb773da59d24288ac
[reqSigs] => 1
[type] => pubkeyhash
[addresses] => Array
(
[0] => HDumjhNR6hJvtuitgxE765gHdax8AQUMGw
)
)
)
)
[blockhash] => 00000127e9ccb94fbf4b537d8d33891673df8f4de49f6f811398a6c070dfb125
[confirmations] => 1
[time] => 1456731827
[blocktime] => 1456731827
"3QJmnh" is just how presstab is displaying it.. here look at the tekyexplorer.. its listed like this "Output Modifier"
http://www.tekyexplorer.xyz/hodl/address.php?address=Output%20Modifier
February 29, 2016, 03:37:13 AM
We're seeing a lot of HODL being burnt up at an address here -
http://www.presstab.pw/phpexplorer/HODL/address.php?address=3QJmnh
We're calling these roasted nuts. (The nut being the smallest unit of HODL, like the satoshi)
Looks like someone is mining to an invalid address . . . maybe not setting miningaddress properly, or miningaddress="".
There's over 6000 HODL roasted on the open blockchain so far, that's nearly 1% of current supply. So if you're mining to a single address, I want to remind you to take a moment to quietly check your nuts, and readjust them if anything is out of place.
It seems like there is a space between 3QJmnh and the rest of the address. http://www.presstab.pw/phpexplorer/HODL/address.php?address=3QJmnh
We're calling these roasted nuts. (The nut being the smallest unit of HODL, like the satoshi)
Looks like someone is mining to an invalid address . . . maybe not setting miningaddress properly, or miningaddress="".
There's over 6000 HODL roasted on the open blockchain so far, that's nearly 1% of current supply. So if you're mining to a single address, I want to remind you to take a moment to quietly check your nuts, and readjust them if anything is out of place.
February 29, 2016, 03:35:11 AM
We're seeing a lot of HODL being burnt up at an address here -
http://www.presstab.pw/phpexplorer/HODL/address.php?address=3QJmnh
We're calling these roasted nuts. (The nut being the smallest unit of HODL, like the satoshi)
Looks like someone is mining to an invalid address . . . maybe not setting miningaddress properly, or miningaddress="".
There's over 6000 HODL roasted on the open blockchain so far, that's nearly 1% of current supply. So if you're mining to a single address, I want to remind you to take a moment to quietly check your nuts, and readjust them if anything is out of place.
http://www.presstab.pw/phpexplorer/HODL/address.php?address=3QJmnh
We're calling these roasted nuts. (The nut being the smallest unit of HODL, like the satoshi)
Looks like someone is mining to an invalid address . . . maybe not setting miningaddress properly, or miningaddress="".
There's over 6000 HODL roasted on the open blockchain so far, that's nearly 1% of current supply. So if you're mining to a single address, I want to remind you to take a moment to quietly check your nuts, and readjust them if anything is out of place.
February 29, 2016, 03:14:54 AM
We're seeing a lot of HODL being burnt up at an address here -
http://www.presstab.pw/phpexplorer/HODL/address.php?address=3QJmnh
We're calling these roasted nuts. (The nut being the smallest unit of HODL, like the satoshi)
Looks like someone is mining to an invalid address . . . maybe not setting miningaddress properly, or miningaddress="".
There's over 6000 HODL roasted on the open blockchain so far, that's nearly 1% of current supply. So if you're mining to a single address, I want to remind you to take a moment to quietly check your nuts, and readjust them if anything is out of place.
http://www.presstab.pw/phpexplorer/HODL/address.php?address=3QJmnh
We're calling these roasted nuts. (The nut being the smallest unit of HODL, like the satoshi)
Looks like someone is mining to an invalid address . . . maybe not setting miningaddress properly, or miningaddress="".
There's over 6000 HODL roasted on the open blockchain so far, that's nearly 1% of current supply. So if you're mining to a single address, I want to remind you to take a moment to quietly check your nuts, and readjust them if anything is out of place.
February 29, 2016, 03:04:10 AM
Just want to say thanks to everybody who's reported a problem. Of course we prefer lots of details with bug reports, but even just a vague outline is more helpful than nothing at all. Fuzzbawls has been working really hard to polish up all the rough edges that have been reported and I think the next release will impress.
Not sure if this has been brought to your attention but on a windows machine when trying to use 25% or more of the available RAM by the use of ""minermemory=" in the configuration file I get the Microsoft visual C++ Runtime Library error, "This application has requested the Runtime to terminate it in an unusual way." then the wallet crashes. I have tried this on two separate windows computers. Not a huge deal as I have had more success using all cpu threads on a single gig of memory, but it seems noteworthy.
32bit windows wallet doesn't care if you're running 64bit Windows OS with > 2gb ram...the client itself can't address more than what is limited by the 32bit architecture. That doesn't mean it won't REQUEST more memory if a user explicitely asks for more, but as you have seen, this results in an error.
February 29, 2016, 02:54:25 AM
Just want to say thanks to everybody who's reported a problem. Of course we prefer lots of details with bug reports, but even just a vague outline is more helpful than nothing at all. Fuzzbawls has been working really hard to polish up all the rough edges that have been reported and I think the next release will impress.
Not sure if this has been brought to your attention but on a windows machine when trying to use 25% or more of the available RAM by the use of ""minermemory=" in the configuration file I get the Microsoft visual C++ Runtime Library error, "This application has requested the Runtime to terminate it in an unusual way." then the wallet crashes. I have tried this on two separate windows computers. Not a huge deal as I have had more success using all cpu threads on a single gig of memory, but it seems noteworthy.
Thanks, yes we got that one - Windows seems to be running into a 2GB limit - so 2 is the max usuable on minermemory for now. This might be improved with the next release. However, as you note, it can be better to run a lot of threads on a single GB of memory.
February 29, 2016, 02:45:56 AM
Just want to say thanks to everybody who's reported a problem. Of course we prefer lots of details with bug reports, but even just a vague outline is more helpful than nothing at all. Fuzzbawls has been working really hard to polish up all the rough edges that have been reported and I think the next release will impress.
Not sure if this has been brought to your attention but on a windows machine when trying to use 25% or more of the available RAM by the use of ""minermemory=" in the configuration file I get the Microsoft visual C++ Runtime Library error, "This application has requested the Runtime to terminate it in an unusual way." then the wallet crashes. I have tried this on two separate windows computers. Not a huge deal as I have had more success using all cpu threads on a single gig of memory, but it seems noteworthy.
Jump to: