Topic: [ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties! - page 75. (Read 215829 times)
November 23, 2017, 02:02:12 PM
Will be rocket soon
November 22, 2017, 02:57:19 AM
I would like to start experimenting with new difficulty retarget algorithms. Do you have any preference? Classic choice is DGW3 but we are free to try anything, even something new. I have some ideas for a custom algo. Might also be good for marketing.
What is the retarget algo of cryptonite and why do you want to change it?
I prefer Kimoto Gravity Well, because I like coins with the retarget on every block. I don't like the calculation of diff on every x blocks because someone might use a lot of hash power and leave the diff at a hight level.
Cryptonite diff retarget is already on every block and of course we will only consider such algos for the future.
November 22, 2017, 02:56:18 AM
I would like to start experimenting with new difficulty retarget algorithms. Do you have any preference? Classic choice is DGW3 but we are free to try anything, even something new. I have some ideas for a custom algo. Might also be good for marketing.
Have you looked at BCH? They had pretty wild network hashrate fluctuations too. No idea if it is a good solution but worth a look at least.
More info here:
https://www.bitcoinabc.org/november
Yes I already had a look at that algo, it's a modified zawy v1b IIRC. It is a very good alternative.
November 22, 2017, 01:33:15 AM
I would like to start experimenting with new difficulty retarget algorithms. Do you have any preference? Classic choice is DGW3 but we are free to try anything, even something new. I have some ideas for a custom algo. Might also be good for marketing.
What is the retarget algo of cryptonite and why do you want to change it?
I prefer Kimoto Gravity Well, because I like coins with the retarget on every block. I don't like the calculation of diff on every x blocks because someone might use a lot of hash power and leave the diff at a hight level.
November 21, 2017, 03:00:41 PM
I would like to start experimenting with new difficulty retarget algorithms. Do you have any preference? Classic choice is DGW3 but we are free to try anything, even something new. I have some ideas for a custom algo. Might also be good for marketing.
Have you looked at BCH? They had pretty wild network hashrate fluctuations too. No idea if it is a good solution but worth a look at least.
More info here:
https://www.bitcoinabc.org/november
November 21, 2017, 12:40:29 PM
I would like to start experimenting with new difficulty retarget algorithms. Do you have any preference? Classic choice is DGW3 but we are free to try anything, even something new. I have some ideas for a custom algo. Might also be good for marketing.
Bitcore has good difficulty retarget algo lowering nicehash threat. November 21, 2017, 12:37:44 PM
People using the web wallet please retrieve your funds as the guy maintaining the service is going to close it soon.
I think it is better to move service somewhere.Otherwise later you can get very angry people who were on vacations, or elsewhere and lost their coins.
November 21, 2017, 12:25:31 PM
I would like to start experimenting with new difficulty retarget algorithms. Do you have any preference? Classic choice is DGW3 but we are free to try anything, even something new. I have some ideas for a custom algo. Might also be good for marketing.
November 21, 2017, 11:35:58 AM
People using the web wallet please retrieve your funds as the guy maintaining the service is going to close it soon.
November 21, 2017, 04:02:13 AM
by the way, mini-blockchain is a great solution for smartphone, as they say in Russian proverb - sawing Shura, sawing 
Absolutely agree
November 20, 2017, 05:42:08 PM
by the way, mini-blockchain is a great solution for smartphone, as they say in Russian proverb - sawing Shura, sawing
November 19, 2017, 10:46:12 AM
November 19, 2017, 09:40:12 AM
Trying to install the Linux wallet. Unfortunately, I run into a compilation error.
I googled the error message and the issue seems to be well-known with various cryptocurrency wallets - it is an incompatibility with OpenSSL 1.1+ (see here, for example, for Steem). I also found a Cryptonite pastebin with the same error.
It has already been fixed in Bitcoin, the Steem folks say it's this commit: https://github.com/bitcoin/bitcoin/commit/b58be132c994b6f9b25cb4a702186ef96104953f
The only workaround I found would be to downgrade to OpenSSL 1.0 - does somebody know another solution?
Code:
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h:56:24: error: invalid use of incomplete type ‘BIGNUM {aka struct bignum_st}’
class CBigNum : public BIGNUM
^~~~~~
In file included from /usr/include/openssl/crypto.h:31:0,
from allocators.h:15,
from serialize.h:9,
from netbase.h:13,
from addrman.h:8,
from addrman.cpp:5:
/usr/include/openssl/ossl_typ.h:80:16: note: forward declaration of ‘BIGNUM {aka struct bignum_st}’
typedef struct bignum_st BIGNUM;
^~~~~~~~~
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h: In constructor ‘CBigNum::CBigNum()’:
bignum.h:61:21: error: ‘BN_init’ was not declared in this scope
BN_init(this);
(and it continues a lot more ...)from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h:56:24: error: invalid use of incomplete type ‘BIGNUM {aka struct bignum_st}’
class CBigNum : public BIGNUM
^~~~~~
In file included from /usr/include/openssl/crypto.h:31:0,
from allocators.h:15,
from serialize.h:9,
from netbase.h:13,
from addrman.h:8,
from addrman.cpp:5:
/usr/include/openssl/ossl_typ.h:80:16: note: forward declaration of ‘BIGNUM {aka struct bignum_st}’
typedef struct bignum_st BIGNUM;
^~~~~~~~~
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h: In constructor ‘CBigNum::CBigNum()’:
bignum.h:61:21: error: ‘BN_init’ was not declared in this scope
BN_init(this);
I googled the error message and the issue seems to be well-known with various cryptocurrency wallets - it is an incompatibility with OpenSSL 1.1+ (see here, for example, for Steem). I also found a Cryptonite pastebin with the same error.
It has already been fixed in Bitcoin, the Steem folks say it's this commit: https://github.com/bitcoin/bitcoin/commit/b58be132c994b6f9b25cb4a702186ef96104953f
The only workaround I found would be to downgrade to OpenSSL 1.0 - does somebody know another solution?
Thanks, I will try to incorporate that patch into cryptonite, it should be a no brainer.
November 19, 2017, 09:27:05 AM
Trying to install the Linux wallet. Unfortunately, I run into a compilation error.
I googled the error message and the issue seems to be well-known with various cryptocurrency wallets - it is an incompatibility with OpenSSL 1.1+ (see here, for example, for Steem). I also found a Cryptonite pastebin with the same error.
It has already been fixed in Bitcoin, the Steem folks say it's this commit: https://github.com/bitcoin/bitcoin/commit/b58be132c994b6f9b25cb4a702186ef96104953f
The only workaround I found would be to downgrade to OpenSSL 1.0 - does somebody know another solution?
Code:
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h:56:24: error: invalid use of incomplete type ‘BIGNUM {aka struct bignum_st}’
class CBigNum : public BIGNUM
^~~~~~
In file included from /usr/include/openssl/crypto.h:31:0,
from allocators.h:15,
from serialize.h:9,
from netbase.h:13,
from addrman.h:8,
from addrman.cpp:5:
/usr/include/openssl/ossl_typ.h:80:16: note: forward declaration of ‘BIGNUM {aka struct bignum_st}’
typedef struct bignum_st BIGNUM;
^~~~~~~~~
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h: In constructor ‘CBigNum::CBigNum()’:
bignum.h:61:21: error: ‘BN_init’ was not declared in this scope
BN_init(this);
(and it continues a lot more ...)from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h:56:24: error: invalid use of incomplete type ‘BIGNUM {aka struct bignum_st}’
class CBigNum : public BIGNUM
^~~~~~
In file included from /usr/include/openssl/crypto.h:31:0,
from allocators.h:15,
from serialize.h:9,
from netbase.h:13,
from addrman.h:8,
from addrman.cpp:5:
/usr/include/openssl/ossl_typ.h:80:16: note: forward declaration of ‘BIGNUM {aka struct bignum_st}’
typedef struct bignum_st BIGNUM;
^~~~~~~~~
In file included from chainparams.h:9:0,
from protocol.h:13,
from addrman.h:9,
from addrman.cpp:5:
bignum.h: In constructor ‘CBigNum::CBigNum()’:
bignum.h:61:21: error: ‘BN_init’ was not declared in this scope
BN_init(this);
I googled the error message and the issue seems to be well-known with various cryptocurrency wallets - it is an incompatibility with OpenSSL 1.1+ (see here, for example, for Steem). I also found a Cryptonite pastebin with the same error.
It has already been fixed in Bitcoin, the Steem folks say it's this commit: https://github.com/bitcoin/bitcoin/commit/b58be132c994b6f9b25cb4a702186ef96104953f
The only workaround I found would be to downgrade to OpenSSL 1.0 - does somebody know another solution?
November 18, 2017, 12:44:07 PM
Here sometimes they write about problems with the wallet.
Do they really exist?
I bought coins several times on Nova, they came in successfully and very quickly
Do they really exist?
I bought coins several times on Nova, they came in successfully and very quickly
Once we had sync issues, but now I believe it is pretty stable. If someone is still having problems, please post the details.
November 18, 2017, 12:41:45 PM
Here sometimes they write about problems with the wallet.
Do they really exist?
I bought coins several times on Nova, they came in successfully and very quickly
Do they really exist?
I bought coins several times on Nova, they came in successfully and very quickly
November 18, 2017, 04:54:49 AM
Why do talking constantly to obtain the wallet to find subsequent prevent, this is actually the 3rd day and also the pocket book is not ready, this is one of the cause I get free from Antshares project at first since it is really frustrating to use their wallet and now almost thesame issue
Sorry I couldn't get what you mean. Could you please explain again? What is frustrating you?
Looks like ai generated text... Maybe a translator?
wtf, I had no idea that's a thing now ...
November 18, 2017, 02:22:51 AM
Why do talking constantly to obtain the wallet to find subsequent prevent, this is actually the 3rd day and also the pocket book is not ready, this is one of the cause I get free from Antshares project at first since it is really frustrating to use their wallet and now almost thesame issue
Sorry I couldn't get what you mean. Could you please explain again? What is frustrating you?
Looks like ai generated text... Maybe a translator?
November 18, 2017, 02:19:55 AM
Why do talking constantly to obtain the wallet to find subsequent prevent, this is actually the 3rd day and also the pocket book is not ready, this is one of the cause I get free from Antshares project at first since it is really frustrating to use their wallet and now almost thesame issue
Sorry I couldn't get what you mean. Could you please explain again? What is frustrating you?
Looks like ai generated text... Maybe a translator?
November 18, 2017, 12:56:55 AM
Why do talking constantly to obtain the wallet to find subsequent prevent, this is actually the 3rd day and also the pocket book is not ready, this is one of the cause I get free from Antshares project at first since it is really frustrating to use their wallet and now almost thesame issue
Sorry I couldn't get what you mean. Could you please explain again? What is frustrating you?
Jump to: