Pages:
Author

Topic: [ANN] Forknote - create your own Cryptonote network - page 7. (Read 36722 times)

eeX
hero member
Activity: 961
Merit: 500
Soldo.IN [SLD]
Thanks
slb
hero member
Activity: 598
Merit: 501
hello slb,

could you explain options below?

MIN_MIXIN
MANDATORY_MIXIN_BLOCK_VERSION
MIXIN_START_HEIGHT
BUGGED_ZAWY_DIFFICULTY_BLOCK_INDEX

BUGGED_ZAWY_DIFFICULTY_BLOCK_INDEX:   used only by coins adopted bugged ZAWY_DIFFICULTY_BLOCK_INDEX
MANDATORY_MIXIN_BLOCK_VERSION:   Enforce minimum mixin MIN_MIXIN on blockchain level, after block with major version bigger than [this value]
MIN_MIXIN:   minimum mixin amount. Not enforced by default on blockchain level
MIXIN_START_HEIGHT:    minimum block height of the used outputs for mixin

Also, those were added in the preview version:
ZAWY_DIFFICULTY_BLOCK_INDEX   Activates Zawy difficulty after certain block height
ZAWY_DIFFICULTY_DIFFICULTY_BLOCK_VERSION   Activates Zawy difficulty after block major version
ZAWY_DIFFICULTY_V2   ‘1’ if the coin uses Zawy difficulty. Active if the block major version is >=2


Description of all available parameters can be found here:
http://forknote.net/documentation/daemon/#blockchain-options
eeX
hero member
Activity: 961
Merit: 500
Soldo.IN [SLD]
hello slb,

could you explain options below?

MIN_MIXIN
MANDATORY_MIXIN_BLOCK_VERSION
MIXIN_START_HEIGHT
BUGGED_ZAWY_DIFFICULTY_BLOCK_INDEX
slb
hero member
Activity: 598
Merit: 501
Hello,

Forknote 2.1.1 is released:
https://github.com/forknote/forknote/releases/tag/2.1.1

Changes:
* Core changed to Bytecoin 2.1.1
* Added *MIN_MIXIN* option
* Added *MANDATORY_MIXIN_BLOCK_VERSION* option
* Added *MIXIN_START_HEIGHT* option
* Added *BUGGED_ZAWY_DIFFICULTY_BLOCK_INDEX* option in order to fix bug in

In this version you can protect your coins from replay attack. If you have old Dashcoin or Quazarcoin wallet, you can use it safely on both "Double spendings patched" and Minergate networks. You must upgrade your configs with the newest ones:
https://github.com/forknote/configs
member
Activity: 186
Merit: 10
Hello:

Since the last from 2.1.0 to 2.1.1 I cannot compile them from source.
I already downloaded the compiled version to upgrade the pools, however, if I try to compile the version from source (automated process I made) it just fail with this error.
I think it is something related to Makefile rule.

make[3]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[3]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[3]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[4]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/external/rocksdb'
  GEN      util/build_version.cc
make[4]: *** No rule to make target 'util/scoped_arena_iterator.h', needed by 'db/column_family.o'.  Stop.
make[4]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/external/rocksdb'
external/CMakeFiles/rocksdb.dir/build.make:57: recipe for target 'external/CMakeFiles/rocksdb' failed
make[3]: *** [external/CMakeFiles/rocksdb] Error 2
make[3]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
CMakeFiles/Makefile2:126: recipe for target 'external/CMakeFiles/rocksdb.dir/all' failed
make[2]: *** [external/CMakeFiles/rocksdb.dir/all] Error 2
make[2]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
Makefile:94: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
Makefile:20: recipe for target 'build-release' failed
make: *** [build-release] Error 2


OS?  The only difference in the core is rocksdb version update

Yes, I know. The error is on rocksdb.
Ubuntu 16.04 (Xenial).

Thanks @slb
It seems that it is solved.
Problem: git pull
Solution: delete the whole folder and git clone again. After that, compilations works PERFECTLY!

Tnx.-
member
Activity: 186
Merit: 10
Hello:

Since the last from 2.1.0 to 2.1.1 I cannot compile them from source.
I already downloaded the compiled version to upgrade the pools, however, if I try to compile the version from source (automated process I made) it just fail with this error.
I think it is something related to Makefile rule.

make[3]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[3]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[3]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[4]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/external/rocksdb'
  GEN      util/build_version.cc
make[4]: *** No rule to make target 'util/scoped_arena_iterator.h', needed by 'db/column_family.o'.  Stop.
make[4]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/external/rocksdb'
external/CMakeFiles/rocksdb.dir/build.make:57: recipe for target 'external/CMakeFiles/rocksdb' failed
make[3]: *** [external/CMakeFiles/rocksdb] Error 2
make[3]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
CMakeFiles/Makefile2:126: recipe for target 'external/CMakeFiles/rocksdb.dir/all' failed
make[2]: *** [external/CMakeFiles/rocksdb.dir/all] Error 2
make[2]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
Makefile:94: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
Makefile:20: recipe for target 'build-release' failed
make: *** [build-release] Error 2


OS?  The only difference in the core is rocksdb version update

Yes, I know. The error is on rocksdb.
Ubuntu 16.04 (Xenial).

Thanks @slb
slb
hero member
Activity: 598
Merit: 501
Hello:

Since the last from 2.1.0 to 2.1.1 I cannot compile them from source.
I already downloaded the compiled version to upgrade the pools, however, if I try to compile the version from source (automated process I made) it just fail with this error.
I think it is something related to Makefile rule.

make[3]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[3]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[3]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[4]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/external/rocksdb'
  GEN      util/build_version.cc
make[4]: *** No rule to make target 'util/scoped_arena_iterator.h', needed by 'db/column_family.o'.  Stop.
make[4]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/external/rocksdb'
external/CMakeFiles/rocksdb.dir/build.make:57: recipe for target 'external/CMakeFiles/rocksdb' failed
make[3]: *** [external/CMakeFiles/rocksdb] Error 2
make[3]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
CMakeFiles/Makefile2:126: recipe for target 'external/CMakeFiles/rocksdb.dir/all' failed
make[2]: *** [external/CMakeFiles/rocksdb.dir/all] Error 2
make[2]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
Makefile:94: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
Makefile:20: recipe for target 'build-release' failed
make: *** [build-release] Error 2


OS?  The only difference in the core is rocksdb version update
member
Activity: 186
Merit: 10
Hello:

Since the last from 2.1.0 to 2.1.1 I cannot compile them from source.
I already downloaded the compiled version to upgrade the pools, however, if I try to compile the version from source (automated process I made) it just fail with this error.
I think it is something related to Makefile rule.

make[3]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[3]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[3]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
make[4]: Entering directory '/home/escavo/cryptos/cryptonote/forknote/external/rocksdb'
  GEN      util/build_version.cc
make[4]: *** No rule to make target 'util/scoped_arena_iterator.h', needed by 'db/column_family.o'.  Stop.
make[4]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/external/rocksdb'
external/CMakeFiles/rocksdb.dir/build.make:57: recipe for target 'external/CMakeFiles/rocksdb' failed
make[3]: *** [external/CMakeFiles/rocksdb] Error 2
make[3]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
CMakeFiles/Makefile2:126: recipe for target 'external/CMakeFiles/rocksdb.dir/all' failed
make[2]: *** [external/CMakeFiles/rocksdb.dir/all] Error 2
make[2]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
Makefile:94: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/escavo/cryptos/cryptonote/forknote/build/release'
Makefile:20: recipe for target 'build-release' failed
make: *** [build-release] Error 2
eeX
hero member
Activity: 961
Merit: 500
Soldo.IN [SLD]
configs doesn't matter, just coins itself...
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
what with a coin QuazarCoin?
Was there a fork there?
What is the current configuration file forknote use?

Here you may find the latest Quazarcoin config, based on Forknote.
https://github.com/forknote/configs

Remember there are 2 QCN at this moment, the one running on Minergate's  (with the bug descripted by @slb and discover by Monero's team which is a bug con cryptonote protocol, if my mind don't fail) so you cannot send QCN from one blockchain to another. Take care.
HitBTC said they are going to support the major hashrate QCN network so by now, Minergate's is the major one.

there are 2 configs, one year has not been updated. does the exchange support it?
member
Activity: 186
Merit: 10
what with a coin QuazarCoin?
Was there a fork there?
What is the current configuration file forknote use?

Here you may find the latest Quazarcoin config, based on Forknote.
https://github.com/forknote/configs

Remember there are 2 QCN at this moment, the one running on Minergate's  (with the bug descripted by @slb and discover by Monero's team which is a bug con cryptonote protocol, if my mind don't fail) so you cannot send QCN from one blockchain to another. Take care.
HitBTC said they are going to support the major hashrate QCN network so by now, Minergate's is the major one.
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
what with a coin QuazarCoin?
Was there a fork there?
What is the current configuration file forknote use?
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
can not send coins

Code:
2017-Sep-01 21:13:30.874389 ERROR   Error: Internal node error

how to fix?
Where do you got this message? Any additional error with log_level 3?
Last version forknote, Dinastycoin.
Maybe the wallet is corrupted. Try to recover from backup
How Gb blockchain dashcoin?
Free 14 GB, synchronization block 680 000, later corrupted, no free space, free 6 Gb.
slb
hero member
Activity: 598
Merit: 501
Last release Forknote, Dashcoin.
Synchronizatoin stop in 690424 block.

Code:
2017-Sep-03 15:56:43.059218 INFO    SYNCHRONIZATION started
2017-Sep-03 15:56:51.886312 ERROR   push block 6e8e5cb81e15f3e49d4418f4fc2a463b3a01291cfcc9e8337cb64dba94c0f118 write failed: Internal error
2017-Sep-03 15:56:51.886855 WARNING [45.76.34.101:7610 OUT] Exception in connectionHandler: Internal error
2017-Sep-03 15:57:01.290379 INFO    [88.99.172.92:29080 OUT] Sync data returned unknown top block: 690424 -> 786872 [96448 blocks (133 days) behind]

Help me, please!
What error are you getting with log level 3?
slb
hero member
Activity: 598
Merit: 501
can not send coins

Code:
2017-Sep-01 21:13:30.874389 ERROR   Error: Internal node error

how to fix?
Where do you got this message? Any additional error with log_level 3?
Last version forknote, Dinastycoin.
Maybe the wallet is corrupted. Try to recover from backup
member
Activity: 186
Merit: 10
bytecoin show new release.

BTW slb, are you going to add GUI wallet to forknote apps?

@eeX: You won me!. I was thinking since last 2 weeks about it.  Cheesy
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
Last release Forknote, Dashcoin.
Synchronizatoin stop in 690424 block.

Code:
2017-Sep-03 15:56:43.059218 INFO    SYNCHRONIZATION started
2017-Sep-03 15:56:51.886312 ERROR   push block 6e8e5cb81e15f3e49d4418f4fc2a463b3a01291cfcc9e8337cb64dba94c0f118 write failed: Internal error
2017-Sep-03 15:56:51.886855 WARNING [45.76.34.101:7610 OUT] Exception in connectionHandler: Internal error
2017-Sep-03 15:57:01.290379 INFO    [88.99.172.92:29080 OUT] Sync data returned unknown top block: 690424 -> 786872 [96448 blocks (133 days) behind]

Help me, please!
eeX
hero member
Activity: 961
Merit: 500
Soldo.IN [SLD]
bytecoin show new release.

BTW slb, are you going to add GUI wallet to forknote apps?
legendary
Activity: 2744
Merit: 1387
Ukrainians will resist
can not send coins

Code:
2017-Sep-01 21:13:30.874389 ERROR   Error: Internal node error

how to fix?
Where do you got this message? Any additional error with log_level 3?
Last version forknote, Dinastycoin.
slb
hero member
Activity: 598
Merit: 501
can not send coins

Code:
2017-Sep-01 21:13:30.874389 ERROR   Error: Internal node error

how to fix?
Where do you got this message? Any additional error with log_level 3?
Pages:
Jump to: